Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure
Metering & Power Quality
Schneider Electric support forum about Power Meters (ION, PowerTag, PowerLogic) and Power Quality from design, implementation to troubleshooting and more.
Link copied. Please paste this link to share this article on your social media post.
I have several PM5300s and it has been years since I initially set them up and now I have a new SCADA system to read them.
1. Are there firmware updates for these devices?
2. I cannot get the modbus driver to read them. I have tried some simple modbus/tcp tools, but can't seem to read registers. I am assuming it is just the standard port 502.
3. Do I need a device ID or any other designator?
GDB
Link copied. Please paste this link to share this article on your social media post.
Hello @geoffrybrown
1. Have a look at https://www.se.com/ca/en/product-range/61281-powerlogic-pm5000-power-meters/#software-and-firmware the firmware for your meter type, note that PM5300 have a number of different versions, PM5310, PM5330, PM5331, PM5341 etc. Be sure to use the correct firmware version for your meter type.
2/3. For the PM5320 and PM5340, the Modbus TCP device ID is 255. https://www.se.com/ca/en/faqs/FA341569/
Regards,
Charles
Link copied. Please paste this link to share this article on your social media post.
1- As always you can check the SE website for the latest firmware version. For example, the PM5320 and PM5340, which are Ethernet-based:
2- Inside the firmware package, you will find the latest Modbus Map that needs to be used in 3rd party software or any standard Modbus reader. Correct, the default Modbus TCP port is 502.
3- If you are polling Modbus data via TCP, the device ID is 255.
Best Regards,
-Mehran
L3 Expert Advanced Metering
Link copied. Please paste this link to share this article on your social media post.
You're welcome.
Here is the list of DLF-3000 Error Codes that could occur during firmware upgrade when communicating with devices through an Ethernet/Gateway:
https://www.se.com/ca/en/faqs/FA232730/
515: MODBUS + gateway path unavailable
Please make sure the device is accessible to the PC where DLF is running and port 502 is open.
Best Regards,
-Mehran
L3 Expert Advanced metering
Link copied. Please paste this link to share this article on your social media post.
Hello @geoffrybrown
1. Have a look at https://www.se.com/ca/en/product-range/61281-powerlogic-pm5000-power-meters/#software-and-firmware the firmware for your meter type, note that PM5300 have a number of different versions, PM5310, PM5330, PM5331, PM5341 etc. Be sure to use the correct firmware version for your meter type.
2/3. For the PM5320 and PM5340, the Modbus TCP device ID is 255. https://www.se.com/ca/en/faqs/FA341569/
Regards,
Charles
Link copied. Please paste this link to share this article on your social media post.
1- As always you can check the SE website for the latest firmware version. For example, the PM5320 and PM5340, which are Ethernet-based:
2- Inside the firmware package, you will find the latest Modbus Map that needs to be used in 3rd party software or any standard Modbus reader. Correct, the default Modbus TCP port is 502.
3- If you are polling Modbus data via TCP, the device ID is 255.
Best Regards,
-Mehran
L3 Expert Advanced Metering
Link copied. Please paste this link to share this article on your social media post.
Thank you both for your help. So I was able to use the Modbus Tester to validate and was able to get Ignition to talk to it. However, there has always been network issues with these devices and in looking through the firmware notes, I saw that there was an update to the ethenet stack. So I wanted to update.
I went and found the DLF-3000 software and the 2.4 update from the Schneider site. However, when I ran to connect, I got a Device Error = 515 and I haven't been able to find anywhere where it says what that was. I finally broke down and called Schneider today and they didn't know what that error was either and they said they would get back to me.
Link copied. Please paste this link to share this article on your social media post.
You're welcome.
Here is the list of DLF-3000 Error Codes that could occur during firmware upgrade when communicating with devices through an Ethernet/Gateway:
https://www.se.com/ca/en/faqs/FA232730/
515: MODBUS + gateway path unavailable
Please make sure the device is accessible to the PC where DLF is running and port 502 is open.
Best Regards,
-Mehran
L3 Expert Advanced metering
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Do you observe the same behavior after power cycling the meter?
The image shows the meter type as PM5300 series. There is a FAQ regarding 'PM53XX Meter Front Display Freezing and Communication Loss' that could help but I would recommend contacting the local tech support team for further assistance and investigations.
Best Regards,
-Mehran
L3 Expert Advanced metering
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.
With achievable small steps, users progress and continually feel satisfaction in task accomplishment.
Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.
of