Difference between revisions of "Help with Server FAQ"
Thiagojuca (talk | contribs) |
Thiagojuca (talk | contribs) |
||
Line 2: | Line 2: | ||
{| class="wikitable" | {| class="wikitable" | ||
|+ | |+ | ||
+ | {| class="wikitable mw-collapsible" | ||
+ | |+ | ||
+ | !'''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?''' | ||
+ | |- | ||
+ | |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] | ||
+ | # 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]] | ||
+ | # 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. | ||
+ | |} | ||
!QUESTION | !QUESTION | ||
!ANSWER | !ANSWER |
Revision as of 20:22, 31 January 2024
Here are some tips for solving the most common issues setting up Server.
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? |
---|
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]
|
- 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: https://wiki.teltonika-gps.com/view/Fleet_Management_platforms
- 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.
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
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.
Below we have a couple of examples of packets send using the Codec8 and TCP protocols with the proper response:
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
[SP1]There should be question and answer regarding what needs to be evaluated first before starting to develop server
Answer:
Hardware specifications and network specifications should depend on how many devices client wants to support on his platform + future scaling and also what is the use case. For example, live tracking needs a quick network as well as fast processing of data.