Sir, We already test this scenario with TCP/IP and it works well. But when we change to RS485 sersenport, we encountered problem when doing a test MODBUS connection with RS485 sersenport and RS485-to-USB Adapter to PC.  And the Mbpoll settings to initiate the MODBUS RTU call is  The settings on the DT script is 'Z=RS485- 'Y=RS485+ 'DGND=GND PROFILE SERSEN_PORT FUNCTION="MODBUS" PROFILE SERSEN_PORT BPS="9600" PROFILE SERSEN_PORT DATA_BITS="8" PROFILE SERSEN_PORT STOP_BITS="1" PROFILE SERSEN_PORT PARITY="NONE" PROFILE SERSEN_PORT FLOW="NONE" PROFILE SERSEN_PORT MODE="RS485" PROFILE MODBUS_SERVER SERSEN_ADDRESS="1" and we set CV to the modbus SETMODBUS 6CV MBF SETMODBUS 8CV MBF SETMODBUS 10CV MBF SETMODBUS 12CV MBF SETMODBUS 14CV MBF SETMODBUS 16CV MBF SETMODBUS 18CV MBF SETMODBUS 20CV MBF SETMODBUS 24CV MBF SETMODBUS 26CV MBF SETMODBUS 28CV MBF SETMODBUS 30CV MBF SETMODBUS 32CV MBF SETMODBUS 34CV MBF SETMODBUS 36CV MBF SETMODBUS 38CV MBF SETMODBUS 40CV MBF SETMODBUS 44CV MBF SETMODBUS 46CV MBF SETMODBUS 48CV MBF SETMODBUS 50CV MBF SETMODBUS 52CV MBF SETMODBUS 54CV MBF SETMODBUS 56CV MBF So please help us what we need to do to to take the MODBUS data via RS485 sersenport. -Thanks

Hi trisari, Please try with a smaller quantity of 10 rather than starting with 60. There is a possibility a restriction of the response length. Please use the new discourse forum for future questions. Best regards, dataTaker Expert