8/8/2025 2:43 AM | |
Joined: 3/28/2010 Last visit: 8/28/2025 Posts: 1169 Rating:
|
What is SDM? What is the Modbus client that is creating the polls and getting the data? What reason do you have to "change the slave ID of an mfm meter" once the network is established and running? What exactly happens when one meter is turned off? Do downstream meters fail to reply? Do all meters fail to reply? What else happens? |
8/8/2025 7:36 AM | |
Joined: 9/7/2024 Last visit: 8/8/2025 Posts: 2 Rating:
|
|
8/10/2025 6:10 PM | |
Joined: 3/28/2010 Last visit: 8/28/2025 Posts: 1169 Rating:
|
It sounds like a meter needs to be taken out of service for some reason and the way that is accomplished is to change the server/slave node ID so that the server will never reply to a poll. Be aware that many brands of meters will not 'see' serial setting or Modbus changes until power is cycled to the meter. It appears that Modscan client software continues to read data from the other meters after the server node ID change, but the RTU does not continue to read data from the other meters, due to 'connection' issues. Any Modbus client will have a setting for 'time-out' that determines how long the client waits for the reply from the server. Once that time expires, it depends on the client as to what happens next. Some clients just go on to the next server poll, some retry a poll to the server that did not reply, some flag the server as faulty, whatever, depends on the client configuration/programming. But the successful polling of remaining active servers should not be totally inhibited by connection issues. If the RTU's Modbus polling routine is programmed, rather than 'configured' by selecting choices, then check the programming for time-out actions. If the RTU's Modbus polling routine is configured by selecting choices, and the RTU is acting up, then you'll probably need support from Siemens. |
Follow us on