Teltonika FM9xx Config Help
Edit: Sorry that's supposed to be FMB9xx not FM9xx
Are you sure server gets records every 10 seconds or it just gets a batch of 6 records every 60 seconds?
Hi Anton,
In the GUI, when I select the device and in the State window I see the time change as frequently as 10s, then maybe another 10s later another change and the tracker\vehicle icon moves.
From that I am assuming that the server is getting a record as frequently as 10s.
It could be getting a batch of 6 every 60s and the behaviour of the GUI is making me think otherwise. But in this case, I would expect to see a few jumps or a larger jump as the batch is processed/decoded (if that makes sense).
From Teltonika's docs - it would seem that Min Period, Min Distance Min Angle Min Speed Delta all dictate how often a record is created in the device and Send Period dictates how often what is saved is sent. So I am expecting (mostly) batches of records.
Thanks
Dibs
I've seen the a few entries in the log where the HEX field is significantly larger than most of the others (3 or 4 times larger). I'm assuming those are where the device has sent a batch of records. But they are in the minority - most entries in the log have a HEX field of a similar size.
Any suggestions\thoughts?
Thanks
Dibs
This is for anyone that is analyzing the traccar log and is using a Teltonika device. The traccar log with have entries such as
2020-08-05 18:41:58 INFO: [a6378b17: teltonika < 1.1.3.4] HEX: Short_string *device sends IMEI
2020-08-05 18:41:58 INFO: [a6378b17: teltonika > 1.1.3.4] HEX: 01 *Server acknowledgement
2020-08-05 18:41:59 INFO: [a6378b17: teltonika < 1.1.3.4] HEX: Very_Long_String *device sends Payload *
2020-08-05 18:41:59 INFO: [a6378b17: teltonika > 1.1.3.4] HEX: 00000004 *server confirms nbr of packets
2020-08-05 18:44:23 INFO: [a6378b17: teltonika < 1.1.3.4] HEX: Long_string *device sends Payload
2020-08-05 18:44:23 INFO: [a6378b17: teltonika > 1.1.3.4] HEX: 00000001 *server confirms nbr of packets
2020-08-05 18:44:39 INFO: [a5378b17: teltonika < 1.1.3.4] HEX: long_String *device sends Payload
2020-08-05 18:44:39 INFO: [a6378b17: teltonika > 1.1.3.4] HEX: 00000001 *server confirms nbr of packetsThe explanation is at the end of the line after the *. The initial pair of lines - the sending of the IMEI by the device and it's acknowledgement only happens when the device opens the initial connection - the setting is in
GPRS - Record Settings - Open Link Timeout
if you are using the Teltonika configurator. Or Parameter ID = 1000 if you aren't in which case sending a Custom Command of
getparam 1000
should return the current value and another Custom Command of
setparam 1000:300
should set it to the default value. There are no leading spaces in front of the command (not for GPRS Custom Commands).
In my case - it does look like Send Period is being overridden by Min Distance, Min Angle & Min Speed Delta. My contact at Teltonika seems to believe that's how it should work, totally at odds with their published documentation.
The only way I can seem to get it close to how I want is set Min Saved Records to 3.
I'll update the post when\if I get any further or more info from my contact at Teltonika (they've asked for a copy of the config file from the Configurator, so hopefully they'll come back with some answers.) The device is on firmware - 03.25.15.Rev02 - which is 1 from the most current. The issue may be affecting all FMB series devices (or at least ones with this firmware level).
HIH Someone
Dibs
hi, did you manage to fix the problem?
I have very similar problem with device Teltonika FMB003
It doesn't matter what value I put in the "send_period" parameter (it is set to 1s), the device keeps sending data in 30s intervals.
Here is sample from traccar server log:
2024-09-05 19:30:41 INFO: [T76555670: teltonika < XXX_MY_IP_ADDRESS_XXX] XXX_LONG_STRING_XXXX
2024-09-05 19:30:41 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:17:31, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:30:41 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:17:33, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:30:41 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:17:40, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:30:41 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:17:47, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:30:41 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:17:53, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:30:41 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:18:00, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:30:41 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:18:02, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:30:41 INFO: [T76555670: teltonika > XXX_MY_IP_ADDRESS_XXX] 00000007
2024-09-05 19:31:11 INFO: [T76555670: teltonika < XXX_MY_IP_ADDRESS_XXX] XXX_LONG_STRING_XXXX
2024-09-05 19:31:11 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:18:08, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:31:11 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:18:13, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:31:11 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:18:20, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:31:11 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:18:25, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:31:11 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:18:32, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:31:11 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:18:38, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:31:11 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:18:45, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:31:11 INFO: [T76555670: teltonika > XXX_MY_IP_ADDRESS_XXX] 00000007
2024-09-05 19:31:42 INFO: [T76555670: teltonika < XXX_MY_IP_ADDRESS_XXX] XXX_LONG_STRING_XXXX
2024-09-05 19:31:42 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:18:52, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:31:42 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:18:59, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:31:42 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:19:07, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:31:42 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:19:12, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:31:42 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:19:14, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:31:42 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:19:16, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:31:42 INFO: [T76555670] id: XXX_DEVIDE_ID_XXX, time: 2024-09-05 19:19:17, lat: XXXX, lon: XXXX, speed: XXXX, course: XXXX
2024-09-05 19:31:42 INFO: [T76555670: teltonika > XXX_MY_IP_ADDRESS_XXX] 00000007Here is a sample of selected settings parameters:
System/ System Settings
- Data Protocol: Codec 8 Extended
GPRS/records Setting:
- Open Link Timeout: 60
- Response Timeout: 5
- Network Ping Timeout: 0
- Sort by: Oldest
- ACK Type: AVL
Data Acquisition/ Moving (Home, Roaming, Unknown - the same)
- Min Period: 300
- Min Distance: 100
- Min Angle: 10
- Min Speed Delta: 10
- Min Saved Records: 1
- Send Period: 1
Thanks.
@Marus - try changing the value for "Min Saved Records". I ended up using a value of 3.
@Dibbs - Thanks a lot. I changed "Min Saved Records" to 3. Hope it will be better.
Hi,
I've recently added a Teltonika FM900 (same as FM920 but no internal battery) to my server. Works fine - i.e. connects and displays. I've gone with the default config interms of the Data Acquisition settings with minor changes:
Moving
From reading their documentation, I was under the impression that the tracker would generate records based on values of Min Angle, Min Distance, etc (and save them) but send it's records to the server based on the value of Send Period.
Looking at the server\Interface - I seem to be getting records every 10s or so but based on the value of Send Period, I was expecting them every 60s.
Can anyone shed any light on the config of Teltonika devices?
Thanks in advance
Dibs