Modbus timing and timeouts
Posted: 14 Feb 2019, 09:38
Hi all,
i try to configure a revolutionPi3 to read RS485 High performance soil and subtrates moisture sensor but without success.
I configured the modbus rtu master in pictory as usual ... image below ...
the piTest always fail with 110 error:
piTest -r Modbus_Action_Status_1
1 Byte-Value of Modbus_Action_Status_1: 110 dez (=6e hex)
1 Byte-Value of Modbus_Action_Status_1: 110 dez (=6e hex)
1 Byte-Value of Modbus_Action_Status_1: 110 dez (=6e hex)
1 Byte-Value of Modbus_Action_Status_1: 110 dez (=6e hex)
1 Byte-Value of Modbus_Action_Status_1: 110 dez (=6e hex)
The strange thing is that with QmodBus installed on Raspberry i successful connect and read register... image below...
The register 15 is the sensor board temperature ... the read value is correct
Any suggestion ?
i try to configure a revolutionPi3 to read RS485 High performance soil and subtrates moisture sensor but without success.
I configured the modbus rtu master in pictory as usual ... image below ...
the piTest always fail with 110 error:
piTest -r Modbus_Action_Status_1
1 Byte-Value of Modbus_Action_Status_1: 110 dez (=6e hex)
1 Byte-Value of Modbus_Action_Status_1: 110 dez (=6e hex)
1 Byte-Value of Modbus_Action_Status_1: 110 dez (=6e hex)
1 Byte-Value of Modbus_Action_Status_1: 110 dez (=6e hex)
1 Byte-Value of Modbus_Action_Status_1: 110 dez (=6e hex)
The strange thing is that with QmodBus installed on Raspberry i successful connect and read register... image below...
The register 15 is the sensor board temperature ... the read value is correct
Any suggestion ?