My ODBII tracker, sending tk103 data have a bug where the GPS location on alerts is off by a factor 100, leaving the speeding car in the Atlantic ocean south of Ghana, west of Guinea. Here are two packets, one normal, and one speed alarm.
(I have formatted the hex-decoded messages, the spaces and underscores are not there, the underscores are because the editor won't print multiple spaces)
(087073199030 BR00__191005 A 5520.0536N 01043.1019E 110.7 223220 284.83 11000000 L000450AB)
(087073199030 BO015_191005 A 0055.3436N 00010.6498E 069.5 223440 266.75 11000000 L000450AB)
Where would I go to hack a fix; I presume it has to be local, unless you want to add a TK103_ALARM_COORDINATE_FIX flag to the distribution-
You can use max speed filtering to filter those invalid locations.
I could, but I rather fix the decoding, so I still get the coordinates when the alarm fires. If I set up the max speed filtering, it will also discard the alarm, I think.
Then just modify the decoder class.
My ODBII tracker, sending tk103 data have a bug where the GPS location on alerts is off by a factor 100, leaving the speeding car in the Atlantic ocean south of Ghana, west of Guinea. Here are two packets, one normal, and one speed alarm.
(I have formatted the hex-decoded messages, the spaces and underscores are not there, the underscores are because the editor won't print multiple spaces)
Where would I go to hack a fix; I presume it has to be local, unless you want to add a TK103_ALARM_COORDINATE_FIX flag to the distribution-