<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to Modbus TCP Slave Unit Id</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/37d49fd1e7/" rel="alternate"/><link href="https://forge.codesys.com/forge/talk/Engineering/thread/37d49fd1e7/feed.atom" rel="self"/><id>https://forge.codesys.com/forge/talk/Engineering/thread/37d49fd1e7/</id><updated>2021-08-27T05:05:09.385000Z</updated><subtitle>Recent posts to Modbus TCP Slave Unit Id</subtitle><entry><title>Modbus TCP Slave Unit Id</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/37d49fd1e7/?limit=25#c914" rel="alternate"/><published>2021-08-27T05:05:09.385000Z</published><updated>2021-08-27T05:05:09.385000Z</updated><author><name>i-campbell</name><uri>https://forge.codesys.com/u/i-campbell/</uri></author><id>https://forge.codesys.comec7850957f6f6914bc3fde8581fe78d52336e061</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The Modbus TCP Spec at modbus.org says 0xFF should be used to address the device, and other addresses are for gateway architectures.&lt;br/&gt;
I will see if there is a workaround.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Modbus TCP Slave Unit Id</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/37d49fd1e7/?limit=25#b2e9" rel="alternate"/><published>2021-08-27T05:00:09.964000Z</published><updated>2021-08-27T05:00:09.964000Z</updated><author><name>i-campbell</name><uri>https://forge.codesys.com/u/i-campbell/</uri></author><id>https://forge.codesys.com2ebc2eb2977340c65763896475918816e77f82b0</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;right click the modbus tcp slave, add device, add a "modbus slave, com port". here you can set the unit id.&lt;/p&gt;
&lt;p&gt;You could suggest an improvement to the PLC Manufacturer, that they use 0xFF as a slave ID, when the PLC is not acting as a modbus gateway. You could link them to the Modbus TCP spec at modbus.org where it explains this. That is, unless there is a TCP-Serial gateway in your architecture.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Modbus TCP Slave Unit Id</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/37d49fd1e7/?limit=25#181b" rel="alternate"/><published>2021-08-27T04:24:11.697000Z</published><updated>2021-08-27T04:24:11.697000Z</updated><author><name>ashwinsekar</name><uri>https://forge.codesys.com/u/ashwinsekar/</uri></author><id>https://forge.codesys.comc37d74be82ac19b563c3395c91afedc7350ac815</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi,&lt;br/&gt;
I am trying to setup a modbus tcp communication between &lt;strong&gt;Control Win x64&lt;/strong&gt;(Server) and a PLC(Client),&lt;br/&gt;
The slave id of the PLC can be set only between 1 -247,&lt;/p&gt;
&lt;p&gt;I am able to read values using modscan from Control Win x64 setting the device ID to 255,&lt;/p&gt;
&lt;p&gt;Is it possible to change the Slave id of the modbus server any value between 1 to 247?&lt;/p&gt;
&lt;p&gt;I am using Codesys 3.5.16.20&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>