Repeat reading in the event of a reading/writing conflict
If a process variable is first accessed for writing within a cycle (e.g. from the application) and the variable server then receives an asynchronous value change from the communication component, this value change is not automatically forwarded to the application or the server components involved. By activating the parameter Repeat read in case of write/read conflict, a new read request is explicitly sent to the communication component after a write request has been processed.
|
Setting |
Description of the |
|---|---|
|
|
After writing the new process variable value, a new read request is automatically sent to the communication component. |
|
|
No new read request is sent after the new process variable value has been written. |
Parameters for module: