editor, translation-admin, translator
4,754
edits
Changes
Created page with "Протокол Modbus TCP"
<languages/>
==ModBus TCP Plugin installation & configuration==
<ol>
<li>Make sure you have ModBus TCP licenses
<br>[[file:newmodbus1.png|700px|link=]]<br>
</li>
<li>Make sure you have the latest versions of LT Setup, LT Server, ModBus TCP plugin installed
<br>[[file:newmodbus2.png|700px|link=]]<br>
</li>
<li>Configure plugin before enabling.
<br>[[file:newmodbus3.png|700px|link=]]<br>
<br>[[file:newmodbus4.png|700px|link=]]<br>
<br>[[file:newmodbus5.png|700px|link=]]<br>
'''IP''' - IP address of a ModBus TCP device, make sure that you can ping this device<br>
'''Port''' - 502 it is default port in most cases, but check documentation of your ModBus TCP device<br>
'''Master/Slave''' - this option means that you add a Master device or Slave device<br>
</li>
<li>Enable plugin.
<br>[[file:newmodbus6.png|700px|link=]]<br>
</li>
</ol>
==Examples==
<ol>
<li>
<li>Go to Scripts page and create Blockly script
<br>[[file:newmodbus7.png|700px|link=]]<br>
</li>
<li>Add ModBus block from Other tab
<br>[[file:newmodbus8.png|700px|link=]]<br>
</li>
<li>Choose ModBus TCP com-port from dropdown list and fill other fields. Save script and try it.
<br>[[file:newmodbus9.png|700px|link=]]<br>
</li>
</ol>
==Logs==
Starting Service of MODBUS TCP plugin for Larnitech system...
Started Service of MODBUS TCP plugin for Larnitech system.
Compiled: Jul 7 2021 13:59:57
INF: Settings:
INF: debug yes '''- Debug mode is enabled'''
INF: modbus-devices 192.168.1.110:502:0
INF: Modbus 192.168.1.110:502:0 thread created
INF: Modbus 192.168.1.110:502:0 thread started
DEBUG: Modbus client: connected to 192.168.1.110:502:0''' - Plugin connected to the device'''
DEBUG: Modbus client: waiting for messages for 192.168.1.110:502:0
DEBUG: Add message 01050011FF00 to 192.168.1.110:502:0 queue
DEBUG: Modbus thread unlocked for 192.168.1.110:502:0
DEBUG: Modbus client: send packet to 192.168.1.110:502:0 0x01050011FF00''' - Send ‘ON’ to first coil'''
DEBUG: Modbus client: confirmation from 192.168.1.110:502:0 0x01050011FF00 '''- Right feedback from the device'''
DEBUG: Modbus client: waiting for messages for 192.168.1.110:502:0
DEBUG: Add message 010500110000 to 192.168.1.110:502:0 queue
DEBUG: Modbus thread unlocked for 192.168.1.110:502:0
DEBUG: Modbus client: send packet to 192.168.1.110:502:0 0x010500110000''' - Send ‘OFF’ to first coil'''
DEBUG: Modbus client: confirmation from 192.168.1.110:502:0 0x010500110000''' - Right feedback from the device'''
DEBUG: Modbus client: waiting for messages for 192.168.1.110:502:0
==ModBus TCP Plugin installation & configuration==
<ol>
<li>Make sure you have ModBus TCP licenses
<br>[[file:newmodbus1.png|700px|link=]]<br>
</li>
<li>Make sure you have the latest versions of LT Setup, LT Server, ModBus TCP plugin installed
<br>[[file:newmodbus2.png|700px|link=]]<br>
</li>
<li>Configure plugin before enabling.
<br>[[file:newmodbus3.png|700px|link=]]<br>
<br>[[file:newmodbus4.png|700px|link=]]<br>
<br>[[file:newmodbus5.png|700px|link=]]<br>
'''IP''' - IP address of a ModBus TCP device, make sure that you can ping this device<br>
'''Port''' - 502 it is default port in most cases, but check documentation of your ModBus TCP device<br>
'''Master/Slave''' - this option means that you add a Master device or Slave device<br>
</li>
<li>Enable plugin.
<br>[[file:newmodbus6.png|700px|link=]]<br>
</li>
</ol>
==Examples==
<ol>
<li>
<li>Go to Scripts page and create Blockly script
<br>[[file:newmodbus7.png|700px|link=]]<br>
</li>
<li>Add ModBus block from Other tab
<br>[[file:newmodbus8.png|700px|link=]]<br>
</li>
<li>Choose ModBus TCP com-port from dropdown list and fill other fields. Save script and try it.
<br>[[file:newmodbus9.png|700px|link=]]<br>
</li>
</ol>
==Logs==
Starting Service of MODBUS TCP plugin for Larnitech system...
Started Service of MODBUS TCP plugin for Larnitech system.
Compiled: Jul 7 2021 13:59:57
INF: Settings:
INF: debug yes '''- Debug mode is enabled'''
INF: modbus-devices 192.168.1.110:502:0
INF: Modbus 192.168.1.110:502:0 thread created
INF: Modbus 192.168.1.110:502:0 thread started
DEBUG: Modbus client: connected to 192.168.1.110:502:0''' - Plugin connected to the device'''
DEBUG: Modbus client: waiting for messages for 192.168.1.110:502:0
DEBUG: Add message 01050011FF00 to 192.168.1.110:502:0 queue
DEBUG: Modbus thread unlocked for 192.168.1.110:502:0
DEBUG: Modbus client: send packet to 192.168.1.110:502:0 0x01050011FF00''' - Send ‘ON’ to first coil'''
DEBUG: Modbus client: confirmation from 192.168.1.110:502:0 0x01050011FF00 '''- Right feedback from the device'''
DEBUG: Modbus client: waiting for messages for 192.168.1.110:502:0
DEBUG: Add message 010500110000 to 192.168.1.110:502:0 queue
DEBUG: Modbus thread unlocked for 192.168.1.110:502:0
DEBUG: Modbus client: send packet to 192.168.1.110:502:0 0x010500110000''' - Send ‘OFF’ to first coil'''
DEBUG: Modbus client: confirmation from 192.168.1.110:502:0 0x010500110000''' - Right feedback from the device'''
DEBUG: Modbus client: waiting for messages for 192.168.1.110:502:0