Just be sure to wait at least 0. While in terminal ls /dev: make sure USB device are ttyUSB1īut if power reset on raspberrypi than we have issues on ttyUSB0 and ttyUSB1, its been swapped. With many Modbus slaves you also need to be careful not to poll the slaves too quickly but the WattNode is more robust than most slaves are in this regard. Modbus_Slave_COM_Port -> In General tab, set the tri-plc device id and setup the Modbus channel and Modbus Mapping. Modbus_MASTER_COM_Port-> In General tab, enable Auto-restart communication and rest leave as default Modbus_COM_1->Serial Port Configuration:
Next, set up the Modbus Master in CODESYS to pull data from Tri-PLC
#Modbus poll slave software
In PC, use any Modbus Master software to pull data. While in terminal ls /dev: make sure USB device are ttyUSB0 Modbus Poll (64-Bit) is a Modbus simulator designed primarily to help developers of Modbus slave devices or others that want to test and simulate the Modbus protocol. In raspberry pi setting at: etc/CODESYSControl.cfg Modbus_Serial_Device-> and the rest up to your setting Make sure the connection setting are correct and manage to read data from raspberry pi.
#Modbus poll slave serial
Serial port setup : COM 1 / 9600 / 8 / None / 1Īfter trying all the chances and went through most of the forums on Modbus communication, finally, manage to resolve. I did use USB dongle (USB-RS485) 2 units for both communications. While setup Modbus slave on same raspberry pi shows successful but while trying pulling data via pc with using Modbus Poll, an error message shows "Timeout" and "Insufficient bytes received", one after one.
Raspberry pi as master, I do manage pull data from TRI plc on Modbus RTU without any error. I did setup raspberry pi 3B+ on Codesys with the interface to TRI plc via RS485.
0 kommentar(er)
