Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
I found an issue withe the modbus slave device in Codesys 3.5.16 and the Codesys Control for Rasberry 3.5.16.0.
I currently connect with a nodered modbus master to collect and push data from/to the Codesys Raspberry SPS. The Codesys Raspbery is controlling an old Wago 841.
That means Codesys is master for the Wago and Slave for the nodered.
After updating from Codesys 3.5.15 to 3.5.16 the slave doesn't work anymore. I have not been able to add the Unit-ID, because the box is no more longer available. The Master is working fine.
I now imported the old ModbusTCP Slave Device Version 3.5.15 into the Device Manager and added this as new slave device into my project (updating the existing device to old version doen't work). Now I'm able to add the Unit-ID and everything works now fine.
Does anybody know if this is a Bug or if it is wanted?
thanks
regards
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"On TCP/IP, the MODBUS server is addressed using its IP address; therefore, the
MODBUS Unit Identifier is useless. The value 0xFF has to be used."
0x00 is the broadcast address, so also works.
Last edit: i-campbell 2020-07-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
I found an issue withe the modbus slave device in Codesys 3.5.16 and the Codesys Control for Rasberry 3.5.16.0.
I currently connect with a nodered modbus master to collect and push data from/to the Codesys Raspberry SPS. The Codesys Raspbery is controlling an old Wago 841.
That means Codesys is master for the Wago and Slave for the nodered.
After updating from Codesys 3.5.15 to 3.5.16 the slave doesn't work anymore. I have not been able to add the Unit-ID, because the box is no more longer available. The Master is working fine.
I now imported the old ModbusTCP Slave Device Version 3.5.15 into the Device Manager and added this as new slave device into my project (updating the existing device to old version doen't work). Now I'm able to add the Unit-ID and everything works now fine.
Does anybody know if this is a Bug or if it is wanted?
thanks
regards
more posts ...
Hello again,
does nobody has the same issue or has information on this.
thanks
Can you make node red use address 0xFF? Or 0x00?
https://modbus.org/specs.php
"On TCP/IP, the MODBUS server is addressed using its IP address; therefore, the
MODBUS Unit Identifier is useless. The value 0xFF has to be used."
0x00 is the broadcast address, so also works.
Last edit: i-campbell 2020-07-07