<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to RisingEdge trigger on ModBus Slave</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/3919a5a403/" rel="alternate"/><link href="https://forge.codesys.com/forge/talk/Engineering/thread/3919a5a403/feed.atom" rel="self"/><id>https://forge.codesys.com/forge/talk/Engineering/thread/3919a5a403/</id><updated>2020-02-27T14:01:37.798000Z</updated><subtitle>Recent posts to RisingEdge trigger on ModBus Slave</subtitle><entry><title>RisingEdge trigger on ModBus Slave</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/3919a5a403/?limit=25#360b" rel="alternate"/><published>2020-02-27T14:01:37.798000Z</published><updated>2020-02-27T14:01:37.798000Z</updated><author><name>PhilipLykov</name><uri>https://forge.codesys.com/u/philiplykov/</uri></author><id>https://forge.codesys.com091f4689773f764e3a4d8088657e9263672a2d2e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;dFx hat geschrieben:&lt;/strong&gt;&lt;br/&gt;
Is it modbus TCP or RTU ?&lt;br/&gt;
Screenshot of localisation the edged bit you are talking about ?&lt;br/&gt;
BTW, communications are almost always async. If so, then, most of the time, data is buffered before any send/receive. So planning to do some treatment on data to spare a communication cycle feels wrong.&lt;br/&gt;
If you run TCP, cycle time should not be a problem. I will assume you run RTU modbus. Then, you may want to do some priorities in your data. For exemple, ON/OFF orders, may be send at each cycle, while setpoints could be sent once every 10 cycle.&lt;br/&gt;
One more tip, Don't forget to group your requests : doing a read on 2 words is faster than doing 2 reads on 1 word. Meaning you may want to use a block read, with not used data in it, just because it is faster than doing several reads.&lt;br/&gt;
Same tip applies to bits.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;I speak about ModBus RTU in standard realization in Codesys as native device. There is an option for ModBus Slave Channel: write on rising edge trigger.&lt;br/&gt;
So my question is how this trigger works internally in Codesys.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>RisingEdge trigger on ModBus Slave</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/3919a5a403/?limit=25#2edf" rel="alternate"/><published>2020-02-27T14:01:36.959000Z</published><updated>2020-02-27T14:01:36.959000Z</updated><author><name>dFx</name><uri>https://forge.codesys.com/u/dfx/</uri></author><id>https://forge.codesys.comdb0335673145a724f05803d37ddebf5ca7044d93</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Is it modbus TCP or RTU ?&lt;br/&gt;
Screenshot of localisation the edged bit you are talking about ?&lt;/p&gt;
&lt;p&gt;BTW, communications are almost always async. If so, then, most of the time, data is buffered before any send/receive. So planning to do some treatment on data to spare a communication cycle feels wrong.&lt;/p&gt;
&lt;p&gt;If you run TCP, cycle time should not be a problem. I will assume you run RTU modbus. Then, you may want to do some priorities in your data. For exemple, ON/OFF orders, may be send at each cycle, while setpoints could be sent once every 10 cycle.&lt;br/&gt;
One more tip, Don't forget to group your requests : doing a read on 2 words is faster than doing 2 reads on 1 word. Meaning you may want to use a block read, with not used data in it, just because it is faster than doing several reads.&lt;br/&gt;
Same tip applies to bits.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>RisingEdge trigger on ModBus Slave</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/3919a5a403/?limit=25#4ece" rel="alternate"/><published>2020-02-27T14:01:36.683000Z</published><updated>2020-02-27T14:01:36.683000Z</updated><author><name>PhilipLykov</name><uri>https://forge.codesys.com/u/philiplykov/</uri></author><id>https://forge.codesys.com0ad498c9d50dc25e42713de8287e74e3b638da48</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;So nobody knows? &lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>RisingEdge trigger on ModBus Slave</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/3919a5a403/?limit=25#5649" rel="alternate"/><published>2020-02-27T14:01:36.396000Z</published><updated>2020-02-27T14:01:36.396000Z</updated><author><name>PhilipLykov</name><uri>https://forge.codesys.com/u/philiplykov/</uri></author><id>https://forge.codesys.comca7c9f847e9374337fa5ef638af069a9fe8410e6</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Could somebody please describe at what moment the rising edge mechanism detecting its states in context of writing by rising edge trigger to ModBus Slave device? &lt;br/&gt;
At the end of each cycle? So I have to lost one second cycle to write something? &lt;br/&gt;
Is it possible to reset the trigger automatically just after detection moment and before the main app cycle?&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>