Line 1: |
Line 1: |
− | Here are some tips for solving the most common issues setting up Server.
| + | Server Related Questions and Tips. |
| | | |
− | =='''Data Interpretation'''== | + | =='''Pre-Requisites for server implementation'''== |
| {| class="wikitable mw-collapsible mw-collapsed" role="presentation" | | {| class="wikitable mw-collapsible mw-collapsed" role="presentation" |
− | |<strong>Where can I find a simple and understandable description of the data sent from the device to the server, along with an explanation? I need to understand what the server sees, how it is written, and what the specific values mean.</strong> | + | |<strong>What are the pre-requisites for deploying devices on my server?</strong> |
| |- | | |- |
− | |In the link below you can find a full explanation of the Teltonika protocols with details about Codec 8 and Codec 8 extended protocols, used for data sending, and Codec 12 for sending GPRS commands: https://wiki.teltonika-gps.com/view/Teltonika_Data_Sending_Protocols | + | |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. |
− | Each device I/O parameter has its unique ID, which is called AVL ID. If you want to decode the data easily you can try to use the device Data Sending Parameters ID page to learn about the AVL parameters and how to decode it: https://wiki.teltonika-gps.com/view/FMB920_Teltonika_Data_Sending_Parameters_ID
| |
| |} | | |} |
| | | |
− | =='''Data Functionality/Workflow'''== | + | =='''Server Requirements'''== |
| {| class="wikitable mw-collapsible mw-collapsed" role="presentation" | | {| class="wikitable mw-collapsible mw-collapsed" role="presentation" |
− | |<strong>After creating my server, I started to receive the same message from the device for multiple times. Should I respond to it? If yes, whats the format of the response? | + | |<strong>What are the supported Network Protocols for Teltonika devices which I need to implement on my server</strong> |
− | </strong> | |
| |- | | |- |
− | |First, when module connects to server, module sends its IMEI. First comes short identifying number of bytes written and then goes IMEI as text (bytes). | + | |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. |
− | 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.
| + | =='''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. |
| |} | | |} |
| | | |
− | =='''Implementation'''== | + | =='''Documentation'''== |
| {| class="wikitable mw-collapsible mw-collapsed" role="presentation" | | {| class="wikitable mw-collapsible mw-collapsed" role="presentation" |
− | |<strong>I tried to implement my server but I couldn’t create a tool to listen to the data sent by the device. Does Teltonika have any tools to help in receiving the packets? And to parse the data received? If yes, where I can find it?</strong> | + | |<strong>Does Teltonika offer any homologation or server implementation documents which we can use to see how the data is sent, received, and parsed?</strong> |
| |- | | |- |
− | |Yes, Teltonika has a TCP and UDP listeners that makes part of the Teltonika Parser Pack. In the Parser Pack you can also find the Teltonika Parser to decode the data received by the listeners. You can find the download link of the parser pack here: https://wiki.teltonika-gps.com/view/Universal_Device_Test_Guide#Protocols_implementation | + | |Regarding the documents/sources, here's what we offer: |
| + | # The wiki link on data sending protocols: https://wiki.teltonika-gps.com/view/Teltonika_Data_Sending_Protocols |
| + | # The parsing toolkit containing the TCP/UDP Listener, source code and other related documents. It can be downloaded from here: https://wiki.teltonika-gps.com/view/Universal_Device_Test_Guide#Protocols_implementation |
| |} | | |} |
| | | |
− | =='''Reading Records'''== | + | =='''Implementation'''== |
| {| class="wikitable mw-collapsible mw-collapsed" role="presentation" | | {| class="wikitable mw-collapsible mw-collapsed" role="presentation" |
− | |<strong>After implement my own server I started to receive a packet with multiple records, how can I know which record was generated first? | + | |<strong>Is there any ID/Value available corresponding to the paramters that Teltonika devices offer? </strong> |
− | </strong> | |
| |- | | |- |
− | |When you receive a packet with multiple records in the same Data Packet you can use the Timestamp to know when the record was generated. | + | |Yes, there are several parameters that you can get from our devices and the AVL IDs corresponding to each one of them can be found here: https://wiki.teltonika-gps.com/view/FMM130_Teltonika_Data_Sending_Parameters_ID. |
| |} | | |} |
| | | |
− | =='''Documentation'''== | + | =='''Communication with server'''== |
| {| class="wikitable mw-collapsible mw-collapsed" role="presentation" | | {| class="wikitable mw-collapsible mw-collapsed" role="presentation" |
− | |<strong>I want to receive the data generated by the Teltonika device, does Teltonika have any server or service for this purpose? In case not, Are there any recommendations on how to proceed to receive the data?</strong> | + | |<strong>How does device communicate with the server? |
| + | </strong> |
| |- | | |- |
− | |As we are a Hardware manufacturer we don’t count on a server or service that you can use to see the data generated by your device. So we can offer different solutions for you to reach your goals. [SP1] | + | |First, when module connects to server, module sends its IMEI. First comes short identifying number of bytes written and then goes IMEI as text (bytes). |
− | # You can use an existing Fleet Management platform, a Telematics API Platform, or a Cloud Computing platform. There are a lot of options, but you can find a list with some of the compatible platforms/services here: [[Fleet Management platforms|https://wiki.teltonika-gps.com/view/Fleet_Management_platforms]]
| + | 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. |
− | # You can develop your platform to receive and parse the data generated by the device. To develop your platform you should have some knowledge about programming and networks.
| + | |
| + | 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. |
| |} | | |} |
| | | |
− | =='''PRE-Requisite knowledge/skills'''== | + | =='''Troubleshooting Data'''== |
| {| class="wikitable mw-collapsible mw-collapsed" role="presentation" | | {| class="wikitable mw-collapsible mw-collapsed" role="presentation" |
− | |<strong>I want to develop a Vehicle Tracking System using your GPS Tracker. So, my question is what are the required knowledge/skills to set up my server for sending/receiving data to the Teltonika tracker? I am confused about how to set up my server to send and receive the data from the device</strong> | + | |<strong>How to know if the device is sending the data to server or not? And how to know if the server is accepting the data from device or not? |
| + | </strong> |
| |- | | |- |
− | |To develop your platform first you must be aware of some sort of information/tech skills, such as device Data Sending Protocols, device data sending parameters, basic concepts of network communications, such as communication protocols, open and test IP and ports and how to parse the data received using source codes or the provide protocols. | + | | |
| + | #We can always check the Device Status->GSM info page on the Teltonika Configurator. If device' GPRS status is "Activated" and Sent Records count is above zero and the Sent Records count is increasing that means device is sending data to the server. Thereafter, the server has to accept the data and send back response. |
| + | #If the server has the Codec 8 protocol integerated properly, it will send the response in HEX as number of records received by server. On Teltonika Configurator under Status->GSM info, we can check the "Received Data", Socket and Last server Response time to confirm when was the last connection happened with server and its response hour. |
| |} | | |} |
| | | |
− | =='''Server Requirements/Supported Network Protocols'''== | + | =='''Common Mistakes'''== |
| {| class="wikitable mw-collapsible mw-collapsed" role="presentation" | | {| class="wikitable mw-collapsible mw-collapsed" role="presentation" |
− | |<strong>I want to develop a Vehicle Tracking System using your GPS Tracker. So, my question is what are the required knowledge/skills to set up my server for sending/receiving data to the Teltonika tracker? I am confused about how to set up my server to send and receive the data from the device</strong> | + | |<strong>I am getting the error on the server side saying"Protocol Mismatch". What could possible be wrong in this case?</strong> |
| |- | | |- |
− | |Currently, the Teltonika devices works with 03 different protocols for Data Sending; TCP, UDP, and MQTT. You can open a TCP or a UDP port on your PC to receive the data sent by your device. You can make sure that the port is open using external websites like canyouseeme (https://www.canyouseeme.org), port checker (https://portchecker.co/) and others. If you’re unable to open ports, you can use external tools such as ngrok (https://ngrok.com/) to virtually route the ports. | + | |This is because of mismatch in the selection of Network Protocol on the device and server side. It is possible that on the Device, TCP is selected and on the server side its UDP or vice-versa. Since the structure for both the protocols is different, this mismatch can restrict establishing a connection on the server. |
| |} | | |} |
| | | |
− | =='''Troubleshooting Data'''== | + | =='''ACK Requirements'''== |
| {| class="wikitable mw-collapsible mw-collapsed" role="presentation" | | {| class="wikitable mw-collapsible mw-collapsed" role="presentation" |
− | |<strong>I have done the IMEI acknowledgment part by sending 01 to the device upon reception of IMEI. Now, having a bit of difficulty in sending the number of data packets received on the server from the FMX device. What exactly should I do to properly respond to the device? | + | |<strong>How can we know if the acknowledgment is required on the server or not? Can we change this setting?</strong> |
− | </strong> | |
| |- | | |- |
− | |After receiving the AVL packet from the device you should respond with the number of records is in the packet, which is present in the payload and presented as Number of Data 1 and/ or Number of Data 2. | + | |Acknowledgment is made depending upon the "Record Settings": |
− | Below we have a couple of examples of packets send using the Codec8 and TCP protocols with the proper response:
| + | #If ACK Type, TCP/IP is selected then Server Acknowledgement is not required |
− | | + | #If ACK Type, AVL is selected then the Server must respond with the Acknowledgement. |
− | 1) RAW with 01 record:
| |
− | | |
− | Received data in the hexadecimal stream:
| |
− | | |
− | 000000000000003608010000016B40D8EA30010000000000000000000000000000000
| |
− | | |
− | 105021503010101425E0F01F10000601A014E0000000000000000010000C7CF
| |
− | | |
− | As the Number of Data 1 and 2 shows the value 1, the server should respond:
| |
− | | |
− | 00000001
| |
− | | |
− | 2) RAW with 02 records
| |
− | | |
− | Received data in the hexadecimal stream:
| |
− | | |
− | 000000000000004308020000016B40D57B48010000000000000000000000000000000
| |
− | | |
− | 1010101000000000000016B40D5C198010000000000000000000000000000000 101010101000000020000252C
| |
− | | |
− | As the Number of Data 1 and 2 shows the value 2, the server should respond:
| |
− | | |
− | 00000002
| |
| |} | | |} |
| | | |
− | =='''Common Mistakes'''== | + | =='''Communication over GPRS '''== |
| {| class="wikitable mw-collapsible mw-collapsed" role="presentation" | | {| class="wikitable mw-collapsible mw-collapsed" role="presentation" |
− | |<strong>I’m using the Parser tools to decode the records sent by the device to my server but the Parser says “ Corrupted Data Inserted”. What should I’m doing wrong?</strong> | + | |<strong>How can my device communicate over GPRS messages?</strong> |
| |- | | |- |
− | |First, be sure that you're trying to decode using the proper protocol. I mean, if you configured the device to send messages using UDP to your server you must select UDP in the Parser, if you set the device to send the records using the TCP Protocol you must select the TCP in Parser. | + | |We have few CODEC protocols supporting GPRS communication: Codec 12,13,14,15. However the functionality basics remains the same and is explained below for Codec 12. |
| + | #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. |
| + | #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 |
| |} | | |} |
| | | |