Here’s what more than 2,500 business decision-makers around the world say.Download the report
...with the Facility Hero app in hand! Discover how you can optimize your maintenance efforts today.Learn more
Access tailored services, 24/7 self-service and expert help. Anywhere, anytime, any project.Discover now
Everything you need to know about our IoT technology backbone.Learn more
Welcome to the Schneider Electric Global Website×
For example an M340 communicating to 60 Modbus devices via a TSXETG100 (ATVs, SoftStarters, etc) using the Ethernet IO Scanner. Everything is working fine when all slave devices are present. If 1-2 slave devices are missing, the communication is slower. If 3-4 are missing the communication gets even slower. At 5 or more slave devices missing, the IO Scanner is no longer updating.
This is a common issue when using IO Scanner to communicate to Modbus slave devices via an TSXETG100. If there are 60 device configured in the IO Devices, The requests are sent all at once on the Ethernet side but on the serial side the first request must be received before going to the second one.
There are a few things that can be done to make the communication work more efficiently.
1) Reduce the Slave Time-out on the TSXETG100. The default is 3 seconds. A lower time-out value will force the IO Scanner go to the next device should that device be not present.
2) Use the IO Scanner Device Control bit to turn off communication to slave device. When the bit is ON, the IO Scanner will not attempt to communicate to the slave device.
If a BMX NOE 01x0 module is configured in rack 0, slot 3
%IW0.3.0.1 device 1 - 15
%IW0.3.0.2 device 16 - 31
%IW0.3.0.3 device 32 - 47
%IW0.3.0.4 device 48 - 64