<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to Modbus Slave Device issue </title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/334a0645a0/" rel="alternate"/><link href="https://forge.codesys.com/forge/talk/Engineering/thread/334a0645a0/feed.atom" rel="self"/><id>https://forge.codesys.com/forge/talk/Engineering/thread/334a0645a0/</id><updated>2020-07-07T19:16:29.190000Z</updated><subtitle>Recent posts to Modbus Slave Device issue </subtitle><entry><title>Modbus Slave Device issue </title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/334a0645a0/?limit=25#1d4f" rel="alternate"/><published>2020-07-07T19:16:29.190000Z</published><updated>2020-07-07T19:16:29.190000Z</updated><author><name>i-campbell</name><uri>https://forge.codesys.com/u/i-campbell/</uri></author><id>https://forge.codesys.com6d557a4c64aa027f3e1737fb9e4bbc7b86e87cee</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Can you make node red use address 0xFF? Or 0x00?&lt;br/&gt;
&lt;a href="https://modbus.org/specs.php" rel="nofollow"&gt;https://modbus.org/specs.php&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Modbus TCP&lt;br/&gt;
"On TCP/IP, the MODBUS server is addressed using its IP address; therefore, the &lt;br/&gt;
MODBUS Unit Identifier is useless. The value 0xFF has to be used."&lt;br/&gt;
0x00 is the broadcast address, so also works.&lt;/p&gt;
&lt;/blockquote&gt;&lt;/div&gt;</summary></entry><entry><title>Modbus Slave Device issue </title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/334a0645a0/?limit=25#8d15" rel="alternate"/><published>2020-07-07T18:56:33.154000Z</published><updated>2020-07-07T18:56:33.154000Z</updated><author><name>PrivSPS</name><uri>https://forge.codesys.com/u/elektr-freak/</uri></author><id>https://forge.codesys.com49ebde158e1b4ad9adea0e4b3f2d4c3d23557ec1</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hello again,&lt;/p&gt;
&lt;p&gt;does nobody has the same issue or has information on this.&lt;/p&gt;
&lt;p&gt;thanks&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Modbus Slave Device issue </title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/334a0645a0/?limit=25#f35a" rel="alternate"/><published>2020-06-11T14:29:57.152000Z</published><updated>2020-06-11T14:29:57.152000Z</updated><author><name>PrivSPS</name><uri>https://forge.codesys.com/u/elektr-freak/</uri></author><id>https://forge.codesys.com854eaeb58e4c79ba10772776190731814f4fe539</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi all,&lt;/p&gt;
&lt;p&gt;I found an issue withe the modbus slave device in Codesys 3.5.16 and the Codesys Control for Rasberry 3.5.16.0.&lt;br/&gt;
I currently connect with a nodered modbus master to collect and push data from/to the Codesys Raspberry SPS. The Codesys Raspbery is controlling an old Wago 841.&lt;/p&gt;
&lt;p&gt;That means Codesys is master for the Wago and Slave for the nodered.&lt;/p&gt;
&lt;p&gt;After updating from Codesys 3.5.15 to 3.5.16 the slave doesn't work anymore. I have not been able to add the Unit-ID, because the box is no more longer available. The Master is working fine.&lt;/p&gt;
&lt;p&gt;I now imported the old ModbusTCP Slave Device Version 3.5.15 into the Device Manager and added this as new slave device into my project (updating the existing device to old version doen't work). Now I'm able to add the Unit-ID and everything works now fine.&lt;/p&gt;
&lt;p&gt;Does anybody know if this is a Bug or if it is wanted?&lt;/p&gt;
&lt;p&gt;thanks&lt;br/&gt;
regards&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>