RUTX11 Data to Server

From Wiki Knowledge Base | Teltonika Networks
This is the approved revision of this page, as well as being the most recent.
Main Page > RUTX Routers > RUTX11 > RUTX11 Manual > RUTX11 WebUI > RUTX11 Services section > RUTX11 Data to Server

The information in this page is updated in accordance with firmware version RUTX_R_00.02.03.1

Summary[edit | edit source]

Data to Server function provides you with the possibility to set up senders that transfer data collected from Modbus slaves or Bluetooth devices to remote servers.

If you're having trouble finding this page or some of the parameters described here on your device's WebUI, you should turn on "Advanced WebUI" mode. You can do that by clicking the "Basic" button under "Mode", which is located at the top-right corner of the WebUI.

Networking rutx manual webui basic advanced mode v1.gif

Data senders[edit | edit source]

To add a new data sender, click the Add button:

Networking rutx manual data to server data senders v1.png

Configure data sender[edit | edit source]


When you add a new data sender, you will be redirected to its configuration window. The figure below is an example of that window and the table below provides information on the fields that it contains:

Networking rutx manual data to server advanced sender settings v1.png

General[edit | edit source]

Field Value Description
Enabled off | on; default: off Enables or disables data sender.
Name string; default: none Name of the data sender. Used for easier data senders management purposes only (optional).
Data source Modbus data | Bluetooth data; default: Bluetooth data Source of the data to be sent to server.
Protocol HTTP(S) | MQTT; default: HTTP(S) Protocol used for sending the data to server.
JSON format string; default: {"TS": "%t", "D": "%d", "data": %a} You can fully customize JSON segment.
Possible Modbus values:
  • Date (Linux timestamp) - %t
  • Date (Day/Month/Year Hour:Minute:Second) - %d
  • Modbus slave ID - %i
  • Modbus slave IP - %p
  • Start register - %s
  • Register data (JSON object) - %a

Possible Bluetooth values:

  • Date (Linux timestamp) - %t
  • Date (Day/Month/Year Hour:Minute:Second) - %d
  • Modbus slave ID - %i
  • Modbus slave IP - %p
  • Start register - %s
  • Register data (JSON object) - %a
Segment count integer [1..10]; default: 1 Max segment count in one JSON string sent to server.
URL/Host/Connection string string; default: none URL for HTTP(S); Host for MQTT; Connection string for Azure MQTT.
Period integer [1..86400]; default: 60 Interval for sending the collected data to server (in seconds, 1-86400)
Data filtering All data | By slave ID | By slave IP; default: All data Choose which data this sender will send to server.
By slave ID: Slave ID integer [1..255]; default: none Data will be sent to server only from slave device with this modbus ID (1-255).
By slave IP: Slave IP ip; default: none Data will be sent to server from slave device with this IP address only (Modbus TCP slaves only).
Retry on fail off | on; default: off In case of a failed attempt, retry to send the same data to server later (Retry until successful).


Protocol HTTP(S)[edit | edit source]

Field Value Description
Custom Header string; default: none Allows to add custom headers to the HTTP requests.
Use TLS off | on; default: off Enables the use of TSL certificates.
On: TLS type Certificate based; default: Certificate based Select type of TLS.
On: A File .ca file; default: none Certificate authority is an entity that issues digital certificates. A digital certificate certifies the ownership of a public key by the named subject of the certificate.
On: Client Certificate .crt file; default: none Certificate file is a type of digital certificate that is used by client systems to make authenticated requests to a remote server. If client certificate is not needed, leave both client certificate and client key fields empty.
On: Private Key .key file; default: none File containing private key for this client. This file needs to be not encrypted.


Protocol MQTT[edit | edit source]

Field Value Description
Port integer [0..65535]; default: 1883 Port number for connecting to MQTT.
Keepalive integer [1..640]; default: 60 MQTT Keepalive period in seconds.
Topic string; default: none MQTT topic to be used for publishing the data.
QoS integer [0..2]; default: 0 MQTT Quality of Service. Allowed values:
  • 0 - when we prefer that the message will not arrive at all rather than arrive twice,
  • 1 - when we want the message to arrive at least once but don't care if it arrives twice (or more),
  • 2 - when we want the message to arrive exactly once. A higher QoS value means a slower transfer.
Use TLS off | on; default: off Enables the use of TSL certificates.
On: TLS type Certificate based | Pre-shared key based; default: Certificate based Select type of TLS.
Certificate based: CA File .ca file; default: none Certificate authority is an entity that issues digital certificates. A digital certificate certifies the ownership of a public key by the named subject of the certificate.
Certificate based: Client Certificate .crt file; default: none Certificate file is a type of digital certificate that is used by client systems to make authenticated requests to a remote server. If client certificate is not needed, leave both client certificate and client key fields empty.
Certificate based: Private Key .key file; default: none File containing private key for this client. This file needs to be not encrypted.
Pre-shared key based: Pre-Shared-Key string; default: none The pre-shared-key in hex format with no leading "0x".
Pre-shared key based: Identity string; default: none The identity of this client. May be used as the username depending on the server settings.
Use Credentials off | on; default: off Enables use of username and password for authentication.
On: Username string; default: none Username used in authentication.
On: Password string; default: none Password used in authentication.

Note: these tables have coloring schemes to indicate which fields can be seen with different configuration.