Are you running a modbus simulator on the same computer?
Have you tried stopping line 1.
Line 1 and Line 8 are both using same database and settings.
Might be conflicting.
I do not know much, only just stared using Rapid scada with my modbus devices this week.
Hi Pieter, Line 1 is configed work as Modbus Master: it will send request and read answer from device. Line 8 is configed as Modbus Slave: it will passsive receive request from another device or software and answer the request. That is my understand, I don’t know it is correct in Rapid Scada or not.
Could you explain the idea what you are going to implement?
Even if you switch operating mode to Slave, the existing Modbus driver works as master. Slave means that Communicator waits for incoming connection, TCP slave (TCP server) not Modbus slave.
I intend to read data of device from my software and maping data to Modbus communicator. If Rapid Scada suport Modbus Slave, I can write data directly use modbus protocol. But with Rapid Scada as TCP server, I still can’t open tcp connection with Local tcp port 502, error:The network connection was refused by the server.