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 also had the same issue after an upgrade to the latest version.
It cost me hours until I recognized, that the Modbus Salave only is in the 'Running' state if an active connection is established to the slave!
If no Modbus Master is connected to the slave, the slave will remain in the 'Not Running' state.
Also check the 'Status Page' of the Modbus Slave and check the Connections, Request and Exception counter.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There is no program in the PI, I just set the Modbus parameters and assign it to a variable.
Here are some screenshots.
https://imgur.com/92mEhDR
https://imgur.com/OTDfwmA
https://imgur.com/X5l3npd
https://imgur.com/LpD4MIl
https://imgur.com/znaBrc2
https://imgur.com/7ef7cvi
more posts ...
Hi,
first:
try to do this without device application.
(add new Project / Standard Project)
Increase the timeout on the slave.
For more diagnosis add the slave device to the watch window. (name in the device tree)
BR
Edwin
I also had the same issue after an upgrade to the latest version.
It cost me hours until I recognized, that the Modbus Salave only is in the 'Running' state if an active connection is established to the slave!
If no Modbus Master is connected to the slave, the slave will remain in the 'Not Running' state.
Also check the 'Status Page' of the Modbus Slave and check the Connections, Request and Exception counter.