Hi Anton,
I was looking at the stops report of my vehicle (on my server) and it reported 17 engine hours. When I investigated, it was concluded that the device reported the ACC Off event but it wasn't recorded in positions (not sure how it was missed). Below is the log where it was reported
2017-11-18 22:31:52 INFO: [AD000B9E] connected
2017-11-18 22:31:54 INFO: [55A699E0] connected
2017-11-18 22:31:55 DEBUG: [BDC0B0A0: 5001 < 103.7.79.231] HEX: 696d65693a3836383638333032383734393332372c616363206f66662c3137313131393031333135322c2c4c2c2c2c64342c2c383932392c2c2c3b
2017-11-18 22:31:55 INFO: [BDC0B0A0] id: 868683028749327, time: 2017-11-18 22:29:50, lat: 24.85001, lon: 67.00845, speed: 2.9, course: 182.1
2017-11-18 22:31:55 DEBUG: [BDC0B0A0: 5001 < 103.7.79.231] HEX: 3836383638333032383734393332373b
2017-11-18 22:31:55 DEBUG: [BDC0B0A0: 5001 > 103.7.79.231] HEX: 4f4e
2017-11-18 22:31:55 INFO: [377B67FE] connected
2017-11-18 22:31:56 DEBUG: [7B753904: 5001 < 37.111.128.123] HEX: 3335393731303034373838323933323b
I included a few lines before and after. the report is at 2017-11-18 22:31:55 (3rd Line). But in the image from route report here clearly shows this location missing and in next (by time) position it shows ignition "Yes". Can you please help rectifying this issue?
regards,
Salman
Digged in and found the problem. I have a filter <entry key='filter.invalid'>true</entry> in my config file and this event report is with "L" validity flag that means no GPS data. That is why it was filtered out. So if I remove above filter, it will start processing these locations but wouldn't that start messing the distance etc stuff? Is there a way that could only filter the location data and keep using the events/alarms?
In the next release there will be an option to exclude alarms from filtering.
Wow that would be really great. Thanks Anton.
Hi Anton,
I was looking at the stops report of my vehicle (on my server) and it reported 17 engine hours. When I investigated, it was concluded that the device reported the ACC Off event but it wasn't recorded in positions (not sure how it was missed). Below is the log where it was reported
I included a few lines before and after. the report is at 2017-11-18 22:31:55 (3rd Line). But in the image from route report here clearly shows this location missing and in next (by time) position it shows ignition "Yes". Can you please help rectifying this issue?
regards,
Salman