<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to How to use Application Trigger in Modbus TCP Server</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/ded298ec00/" rel="alternate"/><link href="https://forge.codesys.com/forge/talk/Engineering/thread/ded298ec00/feed.atom" rel="self"/><id>https://forge.codesys.com/forge/talk/Engineering/thread/ded298ec00/</id><updated>2024-07-01T10:02:24.518000Z</updated><subtitle>Recent posts to How to use Application Trigger in Modbus TCP Server</subtitle><entry><title>How to use Application Trigger in Modbus TCP Server</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/ded298ec00/?limit=25#0ebb" rel="alternate"/><published>2024-07-01T10:02:24.518000Z</published><updated>2024-07-01T10:02:24.518000Z</updated><author><name>hwopereis</name><uri>https://forge.codesys.com/u/hwopereis/</uri></author><id>https://forge.codesys.com1dce2ae5cb9a56dee68ff2560fa5b1fa5afde90c</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;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. &lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>How to use Application Trigger in Modbus TCP Server</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/ded298ec00/?limit=25#a20d" rel="alternate"/><published>2024-07-01T09:06:04.013000Z</published><updated>2024-07-01T09:06:04.013000Z</updated><author><name>hwopereis</name><uri>https://forge.codesys.com/u/hwopereis/</uri></author><id>https://forge.codesys.com56eb3a0b1deacf44672023d41ffb4d27d05bad31</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;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. &lt;/p&gt;
&lt;p&gt;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 &lt;/p&gt;
&lt;p&gt;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. &lt;/p&gt;
&lt;p&gt;Does anybody know how to implement the trigger behavior for the Modbus TCP client? In particular, I struggle to find the exact "trigger" variable. &lt;/p&gt;
&lt;p&gt;I'm running Modbus Client version 4.4.0.0&lt;/p&gt;
&lt;p&gt;Thanks in advance!&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>