MODBUS TCP MASTER with RevPI Connect
Posted: 12 Apr 2019, 10:19
Hello, I'm working on a project with a RevPI Connect, I'm using it to drive a JVL MOTOR Mac800 (by MODBUS TCP).
I implemented a TCP Master in Pictory. And I wrote my own C++ code to get RevPi var.. (using piTest example)..
My project was working properly with my old configuration (RevPI Core 3).
Now I did the same thing with my RevPI Connect, but ........ impossible to get it work.
On my JVL Motor => there is a LED that shows is MODBUS connection is OK, and => it's ok.. (green led).
It's seems that the MODBUS TCP MASTER on revpi does not work because variables are all empty (0).
Here is the output of a simple program, (only for debug purpose) ==>
Found 4 devices:
Address: 0 module type: 105 (0x69) unknown moduletype V1.0
Module is present
input offset: 202 length: 6
output offset: 208 length: 5
Address: 31 module type: 96 (0x60) RevPi DIO V1.3
Module is present
input offset: 89 length: 70
output offset: 159 length: 18
Address: 30 module type: 103 (0x67) RevPi AIO V1.3
Module is present
input offset: 0 length: 20
output offset: 20 length: 4
Address: 64 module type: 24579 (0x6003) ModbusTCP Master Adapter V0.0
Module is present
input offset: 213 length: 101
output offset: 314 length: 73
Modbus_Master_Status : 0x00 0x02
Modbus_Action_Status_1 : 0x03 0xff
Modbus_Action_Status_2 : 0xff 0xff
Modbus_Action_Status_3 : 0xff 0xff
Modbus_Action_Status_4 : 0xff 0xff
Modbus_Action_Status_5 : 0xff 0xff
Modbus_Action_Status_6 : 0xff 0xff
Modbus_Action_Status_7 : 0xff 0xff
Modbus_Action_Status_8 : 0xff 0xff
Modbus_Action_Status_9 : 0xff 0xff
Modbus_Action_Status_10 : 0xff 0xff
Modbus_Action_Status_11 : 0xff 0xff
Modbus_Action_Status_12 : 0xff 0xff
Modbus_Action_Status_13 : 0xff 0xff
Modbus_Action_Status_14 : 0xff 0xff
Modbus_Action_Status_15 : 0xff 0xff
Modbus_Action_Status_16 : 0xff 0xff
Modbus_Action_Status_17 : 0xff 0xff
Modbus_Action_Status_18 : 0xff 0xff
Modbus_Action_Status_19 : 0xff 0xff
Modbus_Action_Status_20 : 0xff 0xff
Modbus_Action_Status_21 : 0xff 0xff
Modbus_Action_Status_22 : 0xff 0xff
Modbus_Action_Status_23 : 0xff 0xff
Modbus_Action_Status_24 : 0xff 0xff
Modbus_Action_Status_25 : 0xff 0xff
Modbus_Action_Status_26 : 0xff 0xff
Modbus_Action_Status_27 : 0xff 0xff
Modbus_Action_Status_28 : 0xff 0xff
Modbus_Action_Status_29 : 0xff 0xff
Modbus_Action_Status_30 : 0xff 0xff
Modbus_Action_Status_31 : 0xff 0xff
Modbus_Action_Status_32 : 0xff 0x00
As you can see there is the value 0x02 in Modbus_Master_Status... But this value is not documented here ==> https://revolution.kunbus.com/tutorials ... verwenden/
You can see too that there is ==> Modbus_Action_Status_1 : 0x03 0xff
I cannot understand why....
Could you help me ?
I implemented a TCP Master in Pictory. And I wrote my own C++ code to get RevPi var.. (using piTest example)..
My project was working properly with my old configuration (RevPI Core 3).
Now I did the same thing with my RevPI Connect, but ........ impossible to get it work.
On my JVL Motor => there is a LED that shows is MODBUS connection is OK, and => it's ok.. (green led).
It's seems that the MODBUS TCP MASTER on revpi does not work because variables are all empty (0).
Here is the output of a simple program, (only for debug purpose) ==>
Found 4 devices:
Address: 0 module type: 105 (0x69) unknown moduletype V1.0
Module is present
input offset: 202 length: 6
output offset: 208 length: 5
Address: 31 module type: 96 (0x60) RevPi DIO V1.3
Module is present
input offset: 89 length: 70
output offset: 159 length: 18
Address: 30 module type: 103 (0x67) RevPi AIO V1.3
Module is present
input offset: 0 length: 20
output offset: 20 length: 4
Address: 64 module type: 24579 (0x6003) ModbusTCP Master Adapter V0.0
Module is present
input offset: 213 length: 101
output offset: 314 length: 73
Modbus_Master_Status : 0x00 0x02
Modbus_Action_Status_1 : 0x03 0xff
Modbus_Action_Status_2 : 0xff 0xff
Modbus_Action_Status_3 : 0xff 0xff
Modbus_Action_Status_4 : 0xff 0xff
Modbus_Action_Status_5 : 0xff 0xff
Modbus_Action_Status_6 : 0xff 0xff
Modbus_Action_Status_7 : 0xff 0xff
Modbus_Action_Status_8 : 0xff 0xff
Modbus_Action_Status_9 : 0xff 0xff
Modbus_Action_Status_10 : 0xff 0xff
Modbus_Action_Status_11 : 0xff 0xff
Modbus_Action_Status_12 : 0xff 0xff
Modbus_Action_Status_13 : 0xff 0xff
Modbus_Action_Status_14 : 0xff 0xff
Modbus_Action_Status_15 : 0xff 0xff
Modbus_Action_Status_16 : 0xff 0xff
Modbus_Action_Status_17 : 0xff 0xff
Modbus_Action_Status_18 : 0xff 0xff
Modbus_Action_Status_19 : 0xff 0xff
Modbus_Action_Status_20 : 0xff 0xff
Modbus_Action_Status_21 : 0xff 0xff
Modbus_Action_Status_22 : 0xff 0xff
Modbus_Action_Status_23 : 0xff 0xff
Modbus_Action_Status_24 : 0xff 0xff
Modbus_Action_Status_25 : 0xff 0xff
Modbus_Action_Status_26 : 0xff 0xff
Modbus_Action_Status_27 : 0xff 0xff
Modbus_Action_Status_28 : 0xff 0xff
Modbus_Action_Status_29 : 0xff 0xff
Modbus_Action_Status_30 : 0xff 0xff
Modbus_Action_Status_31 : 0xff 0xff
Modbus_Action_Status_32 : 0xff 0x00
As you can see there is the value 0x02 in Modbus_Master_Status... But this value is not documented here ==> https://revolution.kunbus.com/tutorials ... verwenden/
You can see too that there is ==> Modbus_Action_Status_1 : 0x03 0xff
I cannot understand why....
Could you help me ?