Hi Nik,
Please check the wiring, RS485 must be connected on Tx, RTS and D Gnd pin.
If you have long wire (above 20 metres), 100 ohms termination resistor is required.
Preferably you do this troubleshooting via command interface DeTransfer since it is easier to check one line of code than the entire program at once.
Turn ON MODBUS diagnostic by sending P56=4 to the logger, check for sensor response.
Diagnostic example:
Modbus TX >SS: 11 033fff0002fabf (8)
Modbus timeout
dataTaker 80 E124 - Modbus transaction failed
1MODBUS NotYetSet
The above example indicates no connection to the sensor.
Modbus TX >SS: 01 0400a30001c1e8 (8)
Modbus RX <SS: 01 840182c0 (5)
Modbus master - slave reported exception: EX_ILLEGAL_FUNCTION = 0x01
The above example indicates target register is not avaiilable
Then if you still failed to get the reading, labelling standard might be the issue (A, B, +, -, inverting, non inverting) so please swap the wire.
Best regards,
Rudy Gunawan
Hi Nik,
Please check the wiring, RS485 must be connected on Tx, RTS and D Gnd pin.
If you have long wire (above 20 metres), 100 ohms termination resistor is required.
Preferably you do this troubleshooting via command interface DeTransfer since it is easier to check one line of code than the entire program at once.
Turn ON MODBUS diagnostic by sending P56=4 to the logger, check for sensor response.
Diagnostic example:
Modbus TX >SS: 11 033fff0002fabf (8)
Modbus timeout
dataTaker 80 E124 - Modbus transaction failed
1MODBUS NotYetSet
The above example indicates no connection to the sensor.
Modbus TX >SS: 01 0400a30001c1e8 (8)
Modbus RX <SS: 01 840182c0 (5)
Modbus master - slave reported exception: EX_ILLEGAL_FUNCTION = 0x01
The above example indicates target register is not avaiilable
Then if you still failed to get the reading, labelling standard might be the issue (A, B, +, -, inverting, non inverting) so please swap the wire.
Best regards,
Rudy Gunawan