Difference between revisions of "Help with Server FAQ"

From Wiki Knowledge Base | Teltonika GPS
Line 5: Line 5:
 
|<strong>What are the pre-requisites for deploying devices on my server?</strong>
 
|<strong>What are the pre-requisites for deploying devices on my server?</strong>
 
|-
 
|-
−
|To develop the platform, it is required to have some sort of information/technical skills, such as device Data Sending Protocols, device data sending parameters, basic concepts of network communications, open and test IP and ports and how to parse the data received using source codes or the provide protocols.
+
|To develop the platform, below are the requirements:
 +
 
 +
#Hardware Knowledge: It can be found on our Teltonika WIKI: https://wiki.teltonika-gps.com/view/Main_Page
 +
#Network Protocols: TCP/IP and UDP are the basic protocols supported by our devices. MQTT is also supported.
 +
#Knowledge about programming language is an asset, where Python, C#, JAVA can be used for Backend. MySQL can be used for the database.
 +
#Skillsket for Socket Programming is an asset to develop a server.
 +
#Security: Teltonika device support TLS Encryption which can be implemented on the server side.
 
|}
 
|}
  
Line 12: Line 18:
 
|<strong>What are the supported Network Protocols for Teltonika devices which I need to implement on my server</strong>
 
|<strong>What are the supported Network Protocols for Teltonika devices which I need to implement on my server</strong>
 
|-
 
|-
−
|Currently, the Teltonika devices works with 03 different protocols for Data Sending; TCP, UDP, and MQTT. Please keep a note that MQTT is supported only via AWS server or a custom server which should be implemented based on the AWS protocols.
+
|Currently, the Teltonika devices works with 03 different protocols for Data Sending; TCP, UDP, and MQTT. Please keep a note that MQTT is supported only via AWS server or a custom server which should be implemented based on the AWS protocols. More information on MQTT ( based on AWS ) can be found here: https://wiki.teltonika-gps.com/view/Getting_Started_with_AWS_IoT_Core.
−
|}
 
−
 
 
−
=='''Data Sending'''==
 
−
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
−
|<strong>What are the data sending protocols that I must implement on my server?</strong>
 
−
|-
 
−
|All the Teltonika devices work on the Codec protocols. More information on the protocols can be found here: https://wiki.teltonika-gps.com/view/Teltonika_Data_Sending_Protocols.
 
 
|}
 
|}
  
Line 46: Line 45:
 
For example, IMEI 356307042441013 would be sent as 000F333536333037303432343431303133. First two bytes denote IMEI length. In this case 0x000F means, that IMEI is 15 bytes long.
 
For example, IMEI 356307042441013 would be sent as 000F333536333037303432343431303133. First two bytes denote IMEI length. In this case 0x000F means, that IMEI is 15 bytes long.
  
−
After receiving IMEI, server should determine if it would accept data from this module. If yes, server will reply to module 01, if not - 00. Note that confirmation should be sent as binary packet. I.e. 1 byte 0x01 or 0x00. Then module starts to send first AVL data packet. After server receives packet and parses it, server must report to module number of data received as integer (four bytes). If sent data number and reported by server doesnā€™t match module resends sent data.
+
After receiving IMEI, server should determine if it would accept data from this module. If yes, server will reply to module 01, if not - 00. Note that confirmation should be sent as binary packet. I.e. 1 byte 0x01 or 0x00. Then module starts to send first AVL data packet. After server receives packet and parses it, server must report to module number of data received as integer (four bytes). If sent data number and reported by server doesn’t match module resends sent data.
 
|}
 
|}
  
Line 82: Line 81:
 
#First, the Teltonika device opens the GPRS session and sends AVL data to the server (refer to device protocols).  
 
#First, the Teltonika device opens the GPRS session and sends AVL data to the server (refer to device protocols).  
 
#Once all records are sent and the correct sent data array acknowledgment is received by the device then GPRS commands in Hex can be sent to the device.
 
#Once all records are sent and the correct sent data array acknowledgment is received by the device then GPRS commands in Hex can be sent to the device.
−
#The ACK (acknowledgment of IMEI from server) is a one-byte constant 0x01. The acknowledgment of each data array sent from the device is four bytes integer ā€“ a number of received records.
+
#The ACK (acknowledgment of IMEI from server) is a one-byte constant 0x01. The acknowledgment of each data array sent from the device is four bytes integer – a number of received records.
 
Detailed information on the protocol can be found here: https://wiki.teltonika-gps.com/view/Teltonika_Data_Sending_Protocols#Codec_12
 
Detailed information on the protocol can be found here: https://wiki.teltonika-gps.com/view/Teltonika_Data_Sending_Protocols#Codec_12
 
|}
 
|}

Revision as of 17:51, 12 February 2024

Server Related Questions and Tips.

Pre-Requisites for server implementation

Server Requirements

Documentation

Implementation

Communication with server

Troubleshooting Data

Common Mistakes

ACK Requirements

Communication over GPRS

RAW Data Example

Retrieved from "https://wiki.teltonika-gps.com/index.php?title=Help_with_Server_FAQ&oldid=95905"