Modbus TCP Master MQTT Gateway: Difference between revisions
m (adjusted image size) |
m (image test 1) |
||
| Line 12: | Line 12: | ||
# Press '''Save & Apply''' | # Press '''Save & Apply''' | ||
[[File:Networking MQTT MODBUS flespi configuration slave1 v1.png|border | [[File:Networking MQTT MODBUS flespi configuration slave1 v1.png|border|1120x1120px|*In this config LAN port is used so “Allow Remote Access” is not needed Modbus TCP Slave RUT955 is now configured. | ||
]] | |alt=|left]] | ||
''*In this config LAN port is used so “Allow Remote Access” is not needed'' | ''*In this config LAN port is used so “Allow Remote Access” is not needed'' | ||
| Line 32: | Line 32: | ||
#Press Test button in Request Configuration Testing to see if Slave device respond to requests, response similar to image below should be shown. | #Press Test button in Request Configuration Testing to see if Slave device respond to requests, response similar to image below should be shown. | ||
#Press Save & Apply | #Press Save & Apply | ||
[[File:Networking MQTT MODBUS flespi configuration master add v1.png|border| | [[File:Networking MQTT MODBUS flespi configuration master add v1.png|border|1136x1136px|alt=|left]] | ||
[[File:Networking MQTT MODBUS flespi configuration master afteradd step 234567 v1.png|border|left|736x736px]] | [[File:Networking MQTT MODBUS flespi configuration master afteradd step 234567 v1.png|border|left|736x736px]] | ||
[[File:Networking MQTT MODBUS flespi configuration master req config8up v1.png|border|1111x1111px|alt=|left]] | |||
[[File:Networking MQTT MODBUS flespi configuration master req testing v1.png|1109x1109px|alt=|border|left]] | |||
==Configuring Flespi.io MQTT Broker== | |||
Revision as of 12:02, 11 July 2022
Pages with broken file links > Modbus TCP Master MQTT GatewaySummary
In this guide Modbus TCP master MQTT Gateway function will be configured with two different types of MQTT Brokers. First using third party MQTT Broker services (in this example Flespi.io). Second using RUT240 router as MQTT Broker. Two RUT955 routers will be used as Modbus TCP Master and Slave, and PC acts as MQTT Publisher and Subscriber.
Configuring RUT955 Modbus TCP Slave
Go to Services > Modbus > Modbus TCP Slave:
- Check Enable
- Enter port that will be used, in this example 502 will be used
- Enter device ID
- Press Save & Apply
*In this config LAN port is used so “Allow Remote Access” is not needed
Modbus TCP Slave RUT955 is now configured.
Configuring RUT955 Modbus TCP Master
Go to Services > Modbus > Modbus TCP Master
- Press Add
- Check Enable
- Enter name for slave device
- Slave ID must match with previously configured Slave device ID
- Enter IP address of Modbus TCP Slave device
- Chose same Port as in Slave device - 502
- Enter Period in seconds, how often requests will be sent to Slave device
- Enter new request name and press Add in Requests configurations
- Choose Data type and Function, enter First register/coil/input to be read or written and Register count. You can name each individual configuration, and then select enable on configurations that you want to use. In this example, register to get WAN IP address of the slave device is used.
- Press Test button in Request Configuration Testing to see if Slave device respond to requests, response similar to image below should be shown.
- Press Save & Apply
