Gosafe protocol is supported in flespi telematics hub.
Gosafe protocol is updated: IBC data type is supported. Parameter ibutton.code is registered for this data type.
integer parameter position.fix.type showing if the position is 2D (value = 1), 3D (value = 2) or not fixed (value = 0) added
Gosafe protocol updated: event data block ETD supported for ASCII protocol format.
Parameter can.vehicle.vin will be renamed to vehicle.vin Both parameters will be registered for 2 weeks until 10 March, 2020. Then can.vehicle.vin will be removed
baja Parameter can.vehicle.vin removed
Gosafe protocol updated: added parsing of OBD data and Fuel data fields for ASCII protocol.
Gosafe protocol updated: parsing of the following Event IDs is added for Event data (ETD) field:
The protocol will be affected by the change in type of parameters gsm.mcc and gsm.mnc to be installed in 2 weeks - May 23rd, 2022: both parameters that now have type "string" will be stored as "number". The possible leading zeroes in MNC will be ignored (e.g. the value "01" will be stored as 1).
Gosafe protocol updated:
Gosafe protocol updated: protocol implementation refactored. No changes in parser behavior are expected.
New devices added:
YuryAheichyk Added Custom command for new devices
Gosafe protocol updated: parameter can.monitor.status (number) is replaced with the parameter can.dtc.cleared.monitor.state (string, HEX format). Both old and new parameters will be registered until 12-Aug-2025.
namo old parameter is removed after renaming
Gosafe protocol is updated: fixed parsing of GSM data.
Fixed parsing of terminal registration (0x0100) for GoSafe G1C/G2C devices when VIN field contains leading null bytes.
Custom command support enabled for G-series (ASCII) and Prime series devices
New packet is supported for G1C devices: JT808 0x0900 upstream data passthrough with collision data (GPS positions and G-sensor acceleration samples). New parameters: crash.event, crash.timestamp, crash.position.seqnum, acceleration.array.
