Not able to read modbus data from energy meter

[MrBong]

I am having  Elite secure 440 energy meter, I am not getting Modbus data in plant Aveva Scada. I am getting in modscan or modpoll but not in Scada. Please guide further.

I am attaching the modbus list of energy meter.

[olivier_vallee]

Hi @MrBong,

Can you confirm what protocol you are using in Plant SCADA? Is it Modnet (TCP/IP) or Modbus (Serial)?

The most common issue is the Device ID setting, which should be entered into the Plant SCADA, Unit Address field (Plant SCADA Studio > Topology > I/O Devices > Address). This usually defaults to 1.

The other most common issue is relating to the device itself, especially this compact power meters or IEDs is the address range they support. By default the Modnet (and I think Modbus) driver will try to read register 400001 before bringing the unit online. If this address space doesn't exist, the driver won't come online. See the drive help on how to modify this default startup read address.

If you still can't get this worked out, maybe get Wireshark and scan the packets (if TCP/IP) for your Modscan or Modpoll, then compare it to what Plant SCADA is sending on the wire.

If you are still stuck, report back with more info and I will try some more suggestions. Alternatively, you can contact AVEVA Support and get some syslog.dat file and driver reported errors ready so they can troubleshoot it more with you.

Kind regards
Olivier

[MrBong]

@olivier_vallee It is Modbus TCP/IP and I have entered Device ID correct, which I have configured in multi function meter. I am getting data of L&T WL4410 and WL4420 multifunction meter in Plant Scada. But not getting data of Elite secure 440. Both meter are in one loop.

I have attached the Modbus address list of both energy meter.

[olivier_vallee]

Hi @MrBong,

Please note that MODNET30 variant is designed to work with TSX Premium and M340 PLCs. This might not be the appropriate variant to communicate with this device. Have you tried setting the protocol to MODNET or one of the other variants like MODNET1?

I'd recommend the following:

1. Using Modscan or Modpoll tool, can you read register 400001?

2. If yes, can you also read 125 contiguous registers in the device? This is how many registers the Modnet driver can attempt to read in one block request. Some smaller devices have non-contiguous address space.

3. Setup a new project, with a single I/O Device and single variable tag. See if this works.

4. If step 3 doesn't work, then use Wireshark to scan the network to see what modbus TCPIP messages the Modscan or Modpoll tools send. Then do the same with your basic AVEVA Plant SCADA and Modnet driver project.

5. Finally if all else fails, set driver logging (see MODNET help for how to do that). Contact AVEVA Support and provide them with the log files and details of your device.

[MrBong]

I have tried all variants Modnet but none of them giving data.

1) I am getting data of L&T WL4410 and WL4420 multifunction meter  in Modscan and Modpoll, Which is starting from 40101 and i have put 400100, Then i am getting data in scada. But the elite secure 440 starting address is 40100, Which i am getting modsan & modpoll, but when i doing same process it is not showing data for any parameters.

2) I have done setting up new project also but same issue.

[MrBong]

@olivier_vallee Modbus address of device is 40108 for RY volt,40110 for YB volt and 40112 for BR volt. 

What should i assign to get the value in scada?

[olivier_vallee]

I recommend you contact SE or AVEVA Customer Support to troubleshoot this issue.