Modbus TCP Master MQTT Gateway: Difference between revisions
(test) |
m (test) |
||
| Line 1: | Line 1: | ||
==Summary== | ==Summary== | ||
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. | 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. | ||
[[File:Networking Topology MQTT MODBUS flespi configuration v1.png|center|frameless|800x800px]] | |||
==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 | |||
[[File:Networking MQTT MODBUS flespi configuration slave1 v1.png|border|center|1171x1171px]] | |||
Revision as of 15:21, 8 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
