How to read voltage from Entes MPR-47SE via Modbus TCP

[eem.ferhat (dmr)]

Hello everyone, I have a device (Entes MPR-47SE) that I want to communicate with using Modbus TCP_any. I want to read voltage data from the device, but I can’t. The device’s IP address is 192.168.5.80 255.255.255.0
Can you help me?

[alexander.hefner]

Hi,

it’s hard to say from the screenshots why it’s not working.
I assume there’s something misconfigured, so:

• please check the fieldbus logger for any entries
• please check the IO mapping pages of the master and slave in online mode to see the informations on the master and slave diagnosis datapoints

Most often the connection fails because of:

• wrong IP settings / device not reachable
• wrong unit identifier setting
• wrong register setup

Here’s a summary what next steps to do / check:

MODBUS TCP on X20 CP1584 PLC

Hi, 1: Network diagnostics To check the network settings or the network connection to another network participant, it is possible to send a ping from the B&R controller. The AsICMP library is available for this purpose and includes an example: [image] [image] If the other party cannot be reached via a ping, the Ethernet settings and the network must be checked. 2: Modbus TCP Client diagnostics If you configure a Modbus TCP master, a Modbus client is activated in the operating system. Th…

And here’s another post, where for example the unit identifier setup was the cause:

Modbus TCP/IP PLC as master and Arduino as a Slave

Hello, I have a problem. I’m working on a university project. My task is to create a device for reading RFID cards for employees at a company site. I am building the RFID card reader using an Arduino UNO with an RC522 RFID module and an Ethernet shield. As the master, I am using a B&R 5PP520 PLC. My problem is that both the slave and master connect to a computer via the Modbus TCP/IP protocol, but they do not maintain a connection with each other. I have attached a screenshot showing the status…

Best regards!

[eem.ferhat (dmr)]

Thank you. I managed to read it. It was due to the Error Unit identifier.