PowerLogic T300 - Can't read Modbus TCP/IP data from PowerLogic P3

[Hoang_Phu]

I can read successfully in Modbus tester and Scada system but I can't read Easergy T300. What am I doing wrong or missing? I have Virtual input 5 activated on the Easergy P3 relay.

[Karthik.P]

Dear Hoang Phu

The configuration on P3 device is correct. 

Many of the Modbus master tools has codes implemented with zero. So, you need to reduce the registry number by one. For eg. If you registry one is 40358, then in the Modbus master tool you need to enter 40357

Regards

Karthik.P

[Hoang_Phu]

Thanks for the reply @Karthik.P 

I tried the method you suggested. I checked the register as 3459 and 3457. if the register was wrong, then one of the virtual inputs must have been read. That's why I thought that my connection settings might be wrong and asked you all. Or do I need to set a mask? Since the value I'm reading contains 0 and 1 values, I don't think I need to set a mask.

[Karthik.P]

Dear Hoang Phu

Since it is ethernet connection, I don't think there will be as mistake in the connections. However, you can share the connection details to us to verify.

You are correct that there is no need for any masking. 

Some of the tools has Modbus implementation that starts from 0. So, it is common practice that we reduce the modbus register number by 1 and enter the reduced value into the SCADA system. For eg: The registry value of P3 device is 40358 which corresponds to virtual input 5 and in your SCADA system you need to enter the registry value as 40357. 

If you have tried the above and still not working, then I can connect on remote and support you

Regards

Karthik.P