Today, I will talk about the solution adopted for managing the energy meters from the manufacturer Carlo Gavazzi, which we discussed in the previous article. This solution is the UWP 4.0 Monitoring and Control Gateway, developed by the same manufacturer, Carlo Gavazzi. This solution was the most suitable due to the time required for system integration and testing. Since it is from the same manufacturer, all the meters and devices developed have the libraries, or drivers if you prefer, included in the Gateway, making integration almost instantaneous.
Although it has the libraries for Carlo Gavazzi devices, it is possible to integrate any other device that communicates via Modbus RS485. The difference is that if the library doesn't exist, it will have to be built from scratch. Knowing the memory addressing table of the device and understanding which units or quantities those memory positions represent allows the creation of the libraries, although this is a time-consuming task.
Carlo Gavazzi Meters - Because Efficiency Starts Here!
All technical details and specifications are found in the UWP_4.0_DS_ENG PDF file that I have attached at the end of this article for those interested in learning more about the Gateway.
The First Contact with the UWP 4.0 Gateway
Regarding the UWP 4.0 Gateway, this was the first time I programmed it, and I didn't find it complicated at all. It has an embedded web server where we can program the entire management interface for the client, create custom dashboards, reports, graphs, schedule tasks, and more.
As for the system's parameterization, it's necessary to use the UWP IDE version 9 programming software, which I will attach at the end of this article. The software's organization is very intuitive, and the project organization is tree-based, where the areas containing the devices are branched out, whether they are meters, actuators, sensors, etc.
The programming can be transferred to the Gateway via USB port or through the Ethernet network. In my case, I did it through Ethernet since the Gateway was located in the Reception's Electrical Panel of the Hotel, which is not very convenient for connecting a notebook and programming in front of the clients. Since it was a structured Ethernet network, I programmed the Gateway in the Datacenter, comfortably at a desk and away from unwanted noise.
Inserting the EM111, EM330, and EM340 Meters into the Project
To add the meters, go to "Module Manager," search for the devices in the template list, and click the + symbol to add them to the project. After adding them, go to "Save and Home" to exit the "Module Manager" and return to the project.
On the main project page, the new meters are listed, and you need to drag and drop them into the respective areas.
Addressing the Devices
This part is very important; without proper addressing, the system won't communicate with the meters. Now, all the parameterizations made in the meters must match in the UWP Gateway programming for everything to work.
Compiling and Uploading the Project to the UWP 4.0 Gateway
After the entire project has been parameterized and validated without errors, it is possible to upload the programming to the Gateway and view in real-time the information collected by the meters.
Client Interface
Once compiled and uploaded to the Gateway, you can access the web server through the IP defined in the UWP 4.0 programming software. When accessing the client interface, you can see that in the creation of dashboards and reports, all entities related to the meters are present: Single and three-phase voltages, Currents, Active Powers, Reactive Powers, Apparent Powers, Frequencies, and Power Factors. These dashboards are customizable, and each user can personalize them according to their preferences.
Problem Encountered and Its Solution
One interesting aspect of this Gateway, for debugging purposes, was the ability to see in real-time the packets being transmitted and identify any failed packets due to communication issues.
Solution? We connected the LiyCy cable shielded to the ground to isolate electromagnetic interference in the cable itself. This significantly improved communication and reduced failed packets.
Conclusion
The entire process of learning, parameterization and delivering the final system to the client was productive and enriching.
Technical Documentation and Software
Developer's Website
