When I have many devices on a network that a CoDeSys runtime is interacting with, it seems the programming connection that allows me to online monitor takes a very low priority and often gets timed out or disconnected. Even if my laptop is connected through the non-codesys port of the SVRX, it appears the codesys gateway itself is getting bogged down and boots my monitoring connection at the slightest hint of strain on the network. Performance wise, the CPU is able to handle the functionality of the project fine, it just seems to disconnect my laptop connection. The more devices the project is connecting to, the more unstable my ālogged inā monitoring connection seems to be. (Iāve had this same issue with other implementations of onboard codesys as well)
My current project Iām integrating with 13 Modbus/TCP devices and 7 Eth/IP devices.
Is there a way to boost the priority of the laptop connection so that my monitoring efforts are treated as higher priority than the peripheral connections? Is it my laptop port or my computers CoDeSys gateway that is the culprit or is it the CoDeSys runtime thatās disconnecting me? Is there a way to track it?
Can you please let us know what version of our CODESYS firmware is running on your cMT-SVRX-820? This information can be found within the CODESYS tab of the webserver.
Iām not on site with the project today, Iāll be back with it tomorrow. Iāll check then and let you know.
I have this from the CoDeSys IDE that I still have open on my laptop:
I just noticed the target version is still 10.30, is there a 15.50 version? The latest CoDeSys package doesnāt seem to offer any newer version to update to.
Unfortunately, this information provided by CODESYS is not as helpful. However, please check the firmware version of CODESYS when on-site and if older than the latest version, 20240703, please backup your CODESYS project and update the CODESYS firmware.
The latest firmware version increases the number of communication / programming channels to 16 which might help to resolve this issue.
Thanks Brendon, I believe Iāve already updated the firmware in order to get the Ethernet IP Scanner object to function (the firmware from the factory didnāt have the required license), but Iāll confirm tomorrow.
Can you elaborate on what you meant by channels? Is this similar to parallel sockets the CPU can maintain? I know the protocols each support some X amount of devices each, (E/IP and Mod/TCP each get 32? Or is that a summed limit of 32 between the two?), but I think this isnāt what youāre referring to, right?
The āchannelsā relate to the maximum number of connections that can be made using the CODESYS IDE or the CODESYS driver within EasyBuilder Pro. This is separate from the limitations set for device count which is 32 for both Modbus TCP/IP and EtherNet/IP slaves.
Just an update, the one SVRX that was more finicky was indeed on an older version of CoDeSys, updating the build to the latest greatly improved stability.
