Ask our Experts
Didn't find what you are looking for? Ask our experts!
New Community Ranking System
Our Community ranking system has recently been updated. You may notice changes in user rankings and receive system messages or notifications. If you have questions about how the new ranking works, please refer to the announcement post for more details (click here).
Schneider Electric support forum about Power Meters (ION, PowerTag, PowerLogic) and Power Quality from design, implementation to troubleshooting and more.
Search in
Please select a country to continue with beta search.
Link copied. Please paste this link to share this article on your social media post.
Olá, senhores.
Estou com problema com um medidor ION 7400 no qual o módulo modbus salave não está funcionando corretamente.
Por exemplo, estou lendo os dados de tensão corretamente como este mostrado na imagem abaixo:
E a leitura do shortbus e no modbuspoll é idêntica porem diferente do valor real medido pelo medidor, que pode ser confirmado na imagem anterior e nas imagens abaixo:
Existe um método de restauração de fabricação de um medidor ion 7400??? Ou outra forma de resolver esses problemas????????
Agradeço sua atenção!
Link copied. Please paste this link to share this article on your social media post.
Hi @darkenwald
In Modbus TCP for ION meters, the Unit ID (or Slave ID) is used as a routing indicator rather than a physical address. The reason ID 255 works while ID 1 fails is due to the meter’s Modbus Gateway setting.
The reason ID 255 works is that when the 'Gateway' is enabled, Unit ID 255 is reserved for the local device (the meter itself). Requests sent to ID 1(or any ID other than 255) are assumed to target a downstream serial device connected to the meter’s RS-485 port. If no mapping exists, the meter returns a Modbus exception.
When 'Gateway' is disabled, the meter stops routing and responds to any Unit ID (1, 100, 255, etc.) with its own data.
In order to poll the meter with the desired Unit ID, you need to disable the gateway, in ION Setup (Advanced Mode):
Best Regards,
-Mehran
L3 Expert Advanced metering
Link copied. Please paste this link to share this article on your social media post.
Hi @darkenwald,
Do you have any other Modbus Slave Modules in your meter? Please check the base address of your Modbus Slave Module to ensure you are reading the correct addresses.
Additionally, when reading Modbus TCP, set the device ID to 255 and verify the readings.
I tested a similar setup, and the registers have the correct values.
Regards,
JD
Link copied. Please paste this link to share this article on your social media post.
Ola, realizei o teste e os dados vinheram corretamente, como mostra a imagem abaixo:
Agora qual o procedimento para normalizar a leitura no ID=1 ???
Link copied. Please paste this link to share this article on your social media post.
Hi @darkenwald
In Modbus TCP for ION meters, the Unit ID (or Slave ID) is used as a routing indicator rather than a physical address. The reason ID 255 works while ID 1 fails is due to the meter’s Modbus Gateway setting.
The reason ID 255 works is that when the 'Gateway' is enabled, Unit ID 255 is reserved for the local device (the meter itself). Requests sent to ID 1(or any ID other than 255) are assumed to target a downstream serial device connected to the meter’s RS-485 port. If no mapping exists, the meter returns a Modbus exception.
When 'Gateway' is disabled, the meter stops routing and responds to any Unit ID (1, 100, 255, etc.) with its own data.
In order to poll the meter with the desired Unit ID, you need to disable the gateway, in ION Setup (Advanced Mode):
Best Regards,
-Mehran
L3 Expert Advanced metering
You’ve reached the end of your document
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.