[Changelog] positioning-universal protocol

omol

We've added Positioning Universal protocol implementation.

The list of supported devices:
FJ1500LA
FJ1500LS
FJ1500MG
FJ2050LA
FJ2050LS
FJ2050LV
FJ2500LA
FJ2500LS
FJ970MW
TM97MW
TM97MA
FJ1510MA
FJ1510LW
FJ1600MW
FJ1600LW
FJ2100MW
TM94MW

namo

Positioning-universal protocol is updated: Sending of acknowledgements for Location Messages now solely depends on the value of Ack Indicator bit.

omol

Positioning Universal protocol has been updated. Fixed custom fields 0-26 parsing: now they are parsed as unsigned integers.

omol

Some Positioning Universal event IDs now also are saved as standard flespi parameters:

2 (Ignition Off) and 4 (Ignition On) is saved as engine.ignition.status (false and true correspondingly)
22 (Power On) and 23 (Power Off): power.on.status (true and false)
30 (GPS Acquired) and 101 (GPS Lost): gps.sattelites.status (true and false)
32 (Crash): crash.event with value true
33 (Hard Acceleration): harsh.acceleration.event with value true
34 (Hard Brake): harsh.braking.event with value true
35 (Hard Left): harsh.turn.left.event with value true
36 (Hard Right): harsh.turn.right.event with value true
52 (Low Battery): battery.low.alarm with value true
104 (Vibration Wake): vibration.alarm with value true
118 (Tow): towing.event with value true
206 (Speed Above Alert) and 207 (Speed Below Alert): overspeeding.status (true and false)
208 (Turn by Turn Alert): harsh.cornering.event with value true
210 (Panic Off) and 211 (Panic On): alarm.panic.status (false and true)
212 (Privacy Off) and 213 (Privacy On): private.status (false and true)

omol

Support of OBDII reports has been updated in Positioning Universal protocol:

DTC data codes are stored in can.dtc.array field as JSON objects with code property set to the parsed value
OBD PIDs are saved as unsigned integers according to the following mapping:
- PID00 in obd.pid00 field
- PID20 in obd.pid20 field
- PID40 in obd.pid40 field
- PID60 in obd.pid60 field
- PID80 in obd.pid80 field
- PIDA0 in obd.pidA0 field

omol

Positioning Universal protocol has been updated: if minor map specifies both absolute and delta values for timestamp, latitude and longitude, then absolute values are ignored and only deltas are used.

omol

Positioning Universal protocol has been updated: zero-length extended fields parsing error has been fixed.

omol

Positioning Universal protocol has been updated: Device/Ignition state field is now parsed as a bitmap value.

omol

Positioning Universal protocol has been updated: DTC data field of unexpected length (not a multiple of 5) is not chopped into items of can.dtc.array parameter but saved as is in can.dtc parameter.

YuryAheichyk

The protocol will be affected by the change in parameter can.dtc and can.dtc.array to be installed in 2 weeks - Mar 15th, 2024: the parameter can.dtc is currently of string type and will be converted to type array with separate DTC codes, can.dtc.array parameter will be removed.

Added parameter can.dtc.new as an example of future implementation of can.dtc

YuryAheichyk

YuryAheichyk changes have been applied, the can.dtc parameter type changed to array

baja

New models added:

YuryAheichyk

The OBDII DTC codes registration is planned to be changed. Currently, error codes are stored in the can.dtc parameter as an array of strings. To unify with other diagnostic protocol types, errors will be stored as an array of objects.

The changes will be applied in 2 weeks, on May 8, 2025.

For reference, two additional parameters have been added:

can.dtc.strings - contains errors in the current format (will be removed in 1 month, on May 24, 2025)
can.dtc.objects - contains errors in the new format (will be removed in 2 weeks, on May 8, 2025)

can.dtc.strings example:
["P0020","U0001"]
can.dtc.objects example:
[{"standard":"OBDII","code":"P0020"},{"standard":"OBDII","code":"U001"}]