Application Note: How to Show Parameters from drive.web Savvy on C-MORE HMI?

You can read this post on LinkedIn as well.

Introduction:

In the spirit of Austin Kleon's wisdom that "You don't have to be a genius!" in the book SHOW YOUR WORK. I am here to share my experiences and newfound knowledge as a full-time Electrical Engineer. Join me as we explore my first project, where I encountered a PLC (Programmable Logic Controller) controlled machine, a C-MORE touch panel HMI, and the intriguing puzzle of their arrangement. Together, we will navigate the challenges and triumphs of modifying the setup, configuring parameters, and establishing communication. So, let's dive in!

Section 1: Unveiling the Setup

Upon closer inspection, an unconventional arrangement revealed itself—a PLC-controlled machine with a mixture of local and remote I/O modules, programmed in DirectSOFT, and a C-MORE touch panel HMI, all connected through a switch. An eyebrow raises, and a realization dawns: the Ethernet cable should connect the HMI panel directly to the switch, bypassing the PLC. Let the modifications begin!

Before

After

Section 2: Smarty DW210 and PL Series DC Drives

With the revised configuration, we introduce the Smarty dw210 connected to port 2 and several PL series DC drives from Bardac Drives into the mix. While I can't showcase their figures here because of copyright, you get the idea.

Section 3: Parameter Discovery

In our quest to monitor specific parameters on our C-MORE HMI, we delve into drive.web Savvy. We focus on parameter 5032) Output and its representation on the HMI, but first, a challenge presents itself. We must subtract one from the parameter and convert it from decimal to octal expression, aligning with the peculiarities of DirectSOFT PLC's octal input requirement.

The subtraction happens because "Register 1 is Address 0." (Source: Modbus 101 - Introduction to Modbus) The key here is that drive.web Savvy reads in decimal expression but DirectSOFT PLC reads in octal expression.

We subtract one from 5032 first then convert it from decimal expression to octal expression.

Section 4: DirectLogic 205 Datasheet Deliberation

Consulting the DirectLogic 205 datasheet becomes essential as we explore the Control Relays PLC range and V-Memory range. Here, we declare the necessary spaces for reading and writing data within DirectSOFT, ensuring seamless communication.

Section 5: Documentation and Workspace Creation

To keep the knowledge alive, I document the highlighted Target parameter for future reference.

Additionally, we create a workspace for the operation, taking inspiration from the ECRX function description. (Please look ECRX function description for details.)

Section 6: Failure Handling and Error Reporting

Preparing for potential run-time failures, we define a "Good" bit to indicate successful operation and an "Error" bit to signal any issues that may arise along the way.

Section 7: Configuring the ECRX Function Block

Finding the appropriate rung, we insert the ECRX function block into our program, ensuring the smooth flow of data. Our diligent efforts begin to bear fruit.

Section 8: Tag Database Management

To establish a seamless connection between DirectSOFT and the C-MORE HMI, we must specify parameter 5032) Output and its location within the Tag Name Database of C-MORE.

Section 9: Uploading the Program and Visualizing the Data

With our program uploaded to both DirectLogic 205 and the C-MORE HMI, we witness the magic unfold. The red rectangle on our HMI displays the coveted data, with Target 5032) Output taking center stage.

Section 10: Customization and Animation

Adding a personal touch, we empower ourselves to tweak the default color theme, ensuring a visual experience that resonates with our preferences. Additionally, the option to incorporate animation further enriches the presentation of real-time status.

Section 11: Inspiration

Throughout this transformative journey, an inspiration played a pivotal role. Here, I share an inspiring video that helped me overcome obstacles and find solutions, further emphasizing the power of collective knowledge.

Conclusion:

Dear fellow explorers of control engineering, by unraveling the complexities of PLC communication, we have proven that one doesn't need to be a genius to succeed. Armed with curiosity, resilience, and a dash of humor, we can navigate the intricacies of our projects and share our experiences with others. So, let us continue to show our work and inspire future generations of engineers.