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 the trigger behavior for the Modbus TCP client? In particular, I struggle to find the exact "trigger" variable.
I'm running Modbus Client version 4.4.0.0
Thanks in advance!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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 the trigger behavior for the Modbus TCP client? In particular, I struggle to find the exact "trigger" variable.
I'm running Modbus Client version 4.4.0.0
Thanks in advance!
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.