Difference between revisions of "Template:Networking rutXxx manual data to server"

From Wiki Knowledge Base | Teltonika GPS
Line 43: Line 43:
 
     <tr>
 
     <tr>
 
       <td>Protocol</td>
 
       <td>Protocol</td>
       <td></td>
+
       <td>Default: '''HTTP(S)'''</td>
       <td></td>
+
       <td>Protocol used for sending the data to server. Available options:
 +
 
 +
* '''HTTP(S)'''
 +
* '''MQTT'''
 +
</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>JSON format</td>
 
       <td>JSON format</td>
       <td></td>
+
       <td>Default: '''{"TS":"%t", "D":"%d","MAC":"%m","DT":"%b"}'''</td>
       <td></td>
+
       <td>You can fully customize JSON segment</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Segment count</td>
 
       <td>Segment count</td>
       <td></td>
+
       <td>Default: '''1'''</td>
       <td></td>
+
       <td>Max segment count in one JSON string sent to server. Available options:
 +
 
 +
* '''1'''
 +
* '''2'''
 +
* '''3'''
 +
* '''4'''
 +
* '''5'''
 +
* '''6'''
 +
* '''7'''
 +
* '''8'''
 +
* '''9'''
 +
* '''10'''
 +
</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>

Revision as of 19:01, 7 February 2020

Summary

123

Data senders

[[File:{{{file_status}}}]]

123

Data sender settings


123

[[File:{{{file_status}}}]]

Field Value Description
Enabled off | on; default: off Check to enable data sender
Name Default: Name of the data sender. Used for easier data senders management purposes only (optional)
Data source Default: Bluetooth data Source of the data to be sent to server. Available options:
  • Bluetooth data
  • Modbus data
Protocol Default: HTTP(S) Protocol used for sending the data to server. Available options:
  • HTTP(S)
  • MQTT
JSON format Default: {"TS":"%t", "D":"%d","MAC":"%m","DT":"%b"} You can fully customize JSON segment
Segment count Default: 1 Max segment count in one JSON string sent to server. Available options:
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
URL/Host/Connection string
Period
Data filtering
Retry on fail
Custom header