I'm now circumventing the problem by creating a separate TCP client for all Write actions. Upon registering a changed variable, I enable this client, until the change is processed.
Hi, I'm currently reading and writing several registers with a Modbus TCP server as a subdevice of a Modbus TCP Client. If I read and write cyclically, there are no issues. The problem is this: I see there is also the option to write by "Application", which I would like to use. However, I don't know With the Modbus RTU client, I see there is a trigger variable, xTrigger, to trigger the writing tasks. However, I can't find any such trigger for the Modbus TCP Client. Does anybody know how to implement...
Only logged in to agree with the above. So counter intuitive. Why does an associated action force the variable when the step it is associated to is not active? Makes no sense at all, is terrible to debug and costs a lot of time. Such as shame.
Hi, I'm experiencing this problem as well. Did the suggested combination resolve your issues in the end? If not, I can stop my efforts rolling back to these versions. I'm trying to get CC for RPi 4.8.0.0 installed on the device, but I can't find it after installing it through the packet manager.