8,290
edits
Changes
no edit summary
Teltonika Networks devices comes with our created [https://wiki.teltonika-networks.com/view/Firmware_Downloads firmware], therefore no additional development or scripting is required for this unit to support OpenRemote.
Teltonika Networks devices comes with our created [https://wiki.teltonika-networks.com/view/Firmware_Downloads firmware], therefore no additional development or scripting is required for this unit to support OpenRemote.
=Setting up OpenRemote=
=Setting up OpenRemote manager=
Refer to the online OpenRemote documentation at [https://github.com/openremote/openremote#quickstart Quckstart]. Follow the steps in the section <b>Quickstart</b> to create your own environment with full access.
Refer to the online OpenRemote documentation at [https://github.com/openremote/openremote#quickstart Quckstart]. Follow the steps in the section <b>Quickstart</b> to create your own environment with full access.
<br><b>NOTE</b>: In examples, port <code>1883</code> was used for MQTT protocol. To use this port you need to add it to your <code>docker-compose</code> file.<br>
<br><b>NOTE</b>: In examples, port <code>1883</code> was used for MQTT protocol. To use this port you need to add it to your <code>docker-compose</code> file.<br>
[[File:Networking_rutos_configuration_examples_openremote_001.png|border|class=tlt-border]]
[[File:Networking_rutos_configuration_examples_openremote_001.png|border|class=tlt-border]]
=OpenRemote as MQTT broker and subscriber=
===Create a service user===
===Create a service user===
# Select the Thing asset type, give it a friendly name and click 'Add'.
# Select the Thing asset type, give it a friendly name and click 'Add'.
#:[[File:Networking_rutos_configuration_examples_openremote_007.png|border|class=tlt-border]]
#:[[File:Networking_rutos_configuration_examples_openremote_007.png|border|class=tlt-border]]
# Add new attribute in the Edit asset mode:
# Add new attribute in the Edit asset mode and save configuration:
#:*type: Custom Attribute
#:*type: Custom Attribute
#:*name: writeAttribute
#:*name: writeAttribute
#:[[File:Networking_rutos_configuration_examples_openremote_008.png|border|class=tlt-border]]
#:[[File:Networking_rutos_configuration_examples_openremote_008.png|border|class=tlt-border]]
#:[[File:Networking_rutos_configuration_examples_openremote_009.png|border|class=tlt-border]]
#:[[File:Networking_rutos_configuration_examples_openremote_009.png|border|class=tlt-border]]
=RUT as MQTT Publisher=
===What data do you want to publish?===
Depending on your RUT model, you can have the following options of data sources to send over MQTT:
*Bluetooth
*Wifi scanner
*MODBUS
===Publishing Bluetooth/Wifi scanner/Modbus data===
Before sending data from those sources to the MQTT Broker, the router needs to know what data from each source to send:
*For Bluetooth, first you have to pair the device you want to get data from
*For WiFi scanner data, you have to enable the wifi scanner functionality first
*For MODBUS data, you need to set what data from what MODBUS slave the router has to get
If you need any help on setting up each functionality, the Teltonika Wiki has topics for each one of them: [[RUTX11 Bluetooth|Bluetooth]], [[RUTX11 Wireless|WiFi Scanner]], [[RUTX11 Modbus|MODBUS]]
===Example: Publishing RUT MODBUS to OpenRemote manager using MQTT===
In this example the RUT device will act as MODBUS TCP Master and MODBUS TCP Slave, so the device will make requests (Master) and answer to himself (Slave). The received reply, will be sent over MQTT. You can also send data from another MODBUS Slave devices connected to the router.
====Enabling MODBUS TCP Slave====
Enabling the MODBUS Slave option on the router allows it to answer any requests coming from a MODBUS Master. To do that, go to the router configuration page→Services→MODBUS→MODBUS TCP Slave. Then clock the "Enable" slider and save.
[[File:Networking_rutos_configuration_examples_openremote_010.png|border|class=tlt-border]]
=== Enabling MODBUS TCP Master ===
Enabling the MODBUS Master option on the router allows it to make specific requests to any slave in the MODBUS network. To do that, go to the router configuration page→Services→MODBUS→MODBUS TCP Master. Click on the "Add" button, and do the following configuration on the page:
[[File:Networking_rutos_configuration_examples_openremote_011.png|border|class=tlt-border]]
'''"Name"''' : Any name
'''"Slave ID"''' : The slave ID you've set on the slave configuration, by default its 1
'''"IP address"''' : The LAN IP address of the router, by default its 192.168.1.1
'''"Port"''' : 502
'''"Period"''' : 20
'''"Timeout"''' : 5
Then scroll down the page a bit, on the "Add new request" section, give any name to your request and click on the "Add" button. Then do the following configuration
[[File:Networking_rutos_configuration_examples_openremote_012.png|border|class=tlt-border]]
'''"Data type"''' : Data type of the data you are going to receive, in this case, the router reports its device name using ASCII
'''"Function"''' : MODBUS Protocol function, in this case, we are going to Read holding registers
'''"First register number"''' : Depends on your MODBUS device, in this case, its 2
'''"Register count / Values"''' : Depends on your MODBUS device, in this case, its 2
Save and apply settings.
=== Configuring Data to Server ===
Go to the router configuration page→Services→[https://wiki.teltonika-networks.com/view/Data_to_Server Data to server]. Click on the "Add" button, and the configuration is basically the same as described on the "Publishing Bluetooth/Wifi scanner/Modbus data" section of this article, just change the data source to "MODBUS data" and format the data as you wish. You should have something similar to this.
[[File:Networking rutos configuration examples AWS 017.png|border|class=tlt-border]]
=== Checking if it works ===
Then, you can use the AWS MQTT test client to check if your setup works, if everything was setup correctly, you should see something like this.
[[File:Networking rutos configuration examples AWS 018.png|border|class=tlt-border]]
