Hi to all
I bought some of the new FMB003 gps tracker hoping to have a direct access to OEM OBD data (mileage and fuel level) as hardware manifacture report, but until now i have trouble to get those data. National vendor who is giving assistance are just a man in the middle, quite useless and teltonika have some obscure policy (like not give the supported veicole list for example ... firmware) that are not really helping.
So as last resource, I open this thread for collecting useful data and experiences for this hardware in conjunction with traccar.
Actual knowledge:
For OEM OBD data sending, periphals:
- have to be configured for using "codec 8 Extended" (configurator, system button, system settings window)
- in OBD II section, "General OBD settings":Enable, "OBD VIN Settings":Auto
- in OBD II section, OBD II window, set "OEM Total Mileage" and "OEM Fuel Level" prority at last to "low"
FMB003 Links:
Actual state and troubleshooting (Firmware 03.25.17 - Traccar 4.12):
Periphals are sending gps data to traccar but there is no way to read io389 and io390. Other io, like io200, or io60, are ok.
tc_positions table
Example records
1726011 teltonika 18 2021-04-01 06:42:05.84 2021-04-01 06:41:49 2021-04-01 06:41:49 t 42,9443316 12,7020183 221 6,479484 80 {"priority":0,"sat":17,"event":0,"ignition":true,"motion":true,"workMode":1,"rssi":3,"io200":0,"gpsStatus":1,"io32":40,"pdop":0.8,"hdop":0.5,"power":14.728,"io24":12,"battery":4.051,"io68":0,"io43":0,"distance":4.24,"totalDistance":998564.65,"hours":88032990} 0 null
1726012 teltonika 18 2021-04-01 06:42:23.119 2021-04-01 06:42:14 2021-04-01 06:42:14 t 42,9445016 12,70329 225 13,498925 134 {"priority":0,"sat":15,"event":0,"ignition":true,"motion":true,"workMode":1,"rssi":3,"io200":0,"gpsStatus":1,"io32":42,"pdop":0.8,"hdop":0.6000000000000001,"power":14.522,"io24":25,"battery":4.041,"io68":0,"io43":0,"distance":101.27,"totalDistance":998661.68,"hours":88057990} 0 null
traccar.log
Log example
2021-04-01 06:42:39 INFO: [7bf87d77] id: 354017119848196, time: 2021-04-01 06:42:36, lat: 42.94335, lon: 12.70523, speed: 18.4, course: 129.0
2021-04-01 06:42:50 INFO: [7bf87d77: teltonika < 83.224.141.182] HEX: 000000000000005a8e01000001788bbda970000792c7bc19988a1000dc009e1100200000000e000700ef0100f00100500100150300c80000450100202e000$
2021-04-01 06:42:50 INFO: [7bf87d77: teltonika > 83.224.141.182] HEX: 00000001
2021-04-01 06:42:50 INFO: [7bf87d77] id: 354017119848196, time: 2021-04-01 06:42:46, lat: 42.94272, lon: 12.70599, speed: 17.3, course: 158.0
2021-04-01 06:43:32 INFO: [7bf87d77: teltonika < 83.224.141.182] HEX: 00000000000002648e07000001788bbe2288000792f25019984ef300e0009310000e0000000e000700ef0100f00100500100150300c800004501002030000$
2021-04-01 06:43:32 INFO: [7bf87d77: teltonika < 83.224.141.182] HEX: 0100500100150300c800004501002030000700b5000900b60006004238e60018001200430fd000440000002b0000000000000000000001788bbddc3800079$
2021-04-01 06:43:32 INFO: [7bf87d77: teltonika > 83.224.141.182] HEX: 00000007
2021-04-01 06:43:32 INFO: [7bf87d77] id: 354017119848196, time: 2021-04-01 06:43:17, lat: 42.94121, lon: 12.70708, speed: 7.6, course: 147.0
2021-04-01 06:43:32 INFO: [7bf87d77] id: 354017119848196, time: 2021-04-01 06:43:16, lat: 42.94124, lon: 12.70705, speed: 7.6, course: 123.0
2021-04-01 06:43:32 INFO: [7bf87d77] id: 354017119848196, time: 2021-04-01 06:43:15, lat: 42.94126, lon: 12.70701, speed: 7.6, course: 100.0
2021-04-01 06:43:32 INFO: [7bf87d77] id: 354017119848196, time: 2021-04-01 06:43:12, lat: 42.94122, lon: 12.70681, speed: 11.3, course: 79.0
2021-04-01 06:43:32 INFO: [7bf87d77] id: 354017119848196, time: 2021-04-01 06:43:09, lat: 42.94118, lon: 12.70654, speed: 8.6, course: 105.0
2021-04-01 06:43:32 INFO: [7bf87d77] id: 354017119848196, time: 2021-04-01 06:43:07, lat: 42.94117, lon: 12.70639, speed: 9.7, course: 148.0
2021-04-01 06:43:32 INFO: [7bf87d77] id: 354017119848196, time: 2021-04-01 06:42:59, lat: 42.94168, lon: 12.70626, speed: 17.3, course: 178.0
2021-04-01 06:43:34 INFO: [7bf87d77: teltonika < 83.224.141.182] HEX: 000000000000005a8e01000001788bbe2a58000792f37b19984b9000e000a70f00120000000e000700ef0100f00100500100150300c800004501002030000$
2021-04-01 06:43:34 INFO: [7bf87d77: teltonika > 83.224.141.182] HEX: 00000001
2021-04-01 06:43:34 INFO: [7bf87d77] id: 354017119848196, time: 2021-04-01 06:43:19, lat: 42.94112, lon: 12.70711, speed: 9.7, course: 167.0
2021-04-01 06:43:51 INFO: [7bf87d77: teltonika < 83.224.141.182] HEX: 000000000000005a8e01000001788bbe97b8000792f7a619980bd400e000bc0f000e0000000e000700ef0100f00100500100150400c800004501002032000$
2021-04-01 06:43:51 INFO: [7bf87d77: teltonika > 83.224.141.182] HEX: 00000001
2021-04-01 06:43:51 INFO: [7bf87d77] id: 354017119848196, time: 2021-04-01 06:43:47, lat: 42.93949, lon: 12.70722, speed: 7.6, course: 188.0
Hi to all
I bought some of the new FMB003 gps tracker hoping to have a direct access to OEM OBD data (mileage and fuel level) as hardware manifacture report, but until now i have trouble to get those data. National vendor who is giving assistance are just a man in the middle, quite useless and teltonika have some obscure policy (like not give the supported veicole list for example ... firmware) that are not really helping.
So as last resource, I open this thread for collecting useful data and experiences for this hardware in conjunction with traccar.
Actual knowledge:
For OEM OBD data sending, periphals:
FMB003 Links:
Actual state and troubleshooting (Firmware 03.25.17 - Traccar 4.12):
Periphals are sending gps data to traccar but there is no way to read io389 and io390. Other io, like io200, or io60, are ok.
tc_positions table
Example records
traccar.log
Log example