Gosafe protocol is supported in flespi telematics hub. Supported devices are below Gosafe G6S Gosafe G3SC Gosafe G3A Gosafe G3C Gosafe G6C Gosafe G737 Gosafe G1S Gosafe G1C Gosafe G1C-Mini Gosafe G1C Easy install GOsafe G2C

Gosafe protocol updated: parsing of the following Event IDs is added for Event data (ETD) field: 0: Tow - flespi parameter towing.alarm.status 1: Idle - - flespi parameters idle.status and idle.status.duration 2: Parking - flespi parameter movement.status 3: Speed - flespi parameter overspeeding.status 4: GSM jamming - flespi parameter gsm.jamming.alarm.status 5: Geo-fence - flespi parameter geofence.alarm 8: Harsh brake - flespi parameters harsh.braking.event and brake.acceleration 9: Harsh accelerate - flespi parameters harsh.acceleration.event and absolute.acceleration 10: Harsh turn - flespi parameters harsh.cornering.event and turn.acceleration 11: Front-end collision - flespi parameter front.collision.event 12: Rear-end collision - flespi parameter rear.collision.event 13: Turnover - flespi parameter turnover.event

Gosafe protocol updated: fixed parsing of GPS data > GPS fix flag and valid satellite number fields for HEX protocol added parsing of Event 55 Hardware malfunction for ASCII protocol. The following parameters are registered: hardware.malfunction.alert=true hardware.fault.code

[Changelog] gosafe protocol

namo

Gosafe protocol is supported in flespi telematics hub.

Gosafe

Supported devices are below

namo

Gosafe protocol is updated: IBC data type is supported. Parameter ibutton.code is registered for this data type.

baja

integer parameter position.fix.type showing if the position is 2D (value = 1), 3D (value = 2) or not fixed (value = 0) added

namo

Gosafe protocol updated: event data block ETD supported for ASCII protocol format.

baja

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

baja Parameter can.vehicle.vin removed

namo

Gosafe protocol updated: added parsing of OBD data and Fuel data fields for ASCII protocol.

namo

Gosafe protocol updated: parsing of the following Event IDs is added for Event data (ETD) field:

0: Tow - flespi parameter towing.alarm.status
1: Idle - - flespi parameters idle.status and idle.status.duration
2: Parking - flespi parameter movement.status
3: Speed - flespi parameter overspeeding.status
4: GSM jamming - flespi parameter gsm.jamming.alarm.status
5: Geo-fence - flespi parameter geofence.alarm
8: Harsh brake - flespi parameters harsh.braking.event and brake.acceleration
9: Harsh accelerate - flespi parameters harsh.acceleration.event and absolute.acceleration
10: Harsh turn - flespi parameters harsh.cornering.event and turn.acceleration
11: Front-end collision - flespi parameter front.collision.event
12: Rear-end collision - flespi parameter rear.collision.event
13: Turnover - flespi parameter turnover.event

baja

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).

namo

Gosafe protocol updated:

fixed parsing of GPS data > GPS fix flag and valid satellite number fields for HEX protocol
added parsing of Event 55 Hardware malfunction for ASCII protocol. The following parameters are registered:
- hardware.malfunction.alert=true
- hardware.fault.code

namo

Gosafe protocol updated: protocol implementation refactored. No changes in parser behavior are expected.

YuryAheichyk

New devices added:

YuryAheichyk

YuryAheichyk Added Custom command for new devices

namo

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

namo old parameter is removed after renaming

namo

Gosafe protocol is updated: fixed parsing of GSM data.

YuryAheichyk

Fixed parsing of terminal registration (0x0100) for GoSafe G1C/G2C devices when VIN field contains leading null bytes.

YuryAheichyk

Custom command support enabled for G-series (ASCII) and Prime series devices

shal

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.

bird

Integrated new devices into Gosafe: G7616, G610, G602, G717.

Bugfix: events 11, 14, 15 were incorrectly mapped — event 11 now correctly produces vehicle.collision.alarm (was harsh.cornering.event), event 14 produces ibutton.connected.status (was external.powersource.voltage.status), event 15 ETD produces gsm.sim.balance (was backup.battery.voltage)

New parameters from DTT DeviceStatus bits 0-1: external.powersource.voltage.status, backup.battery.voltage.status. New event mappings: events 16/17 (external power/backup battery with ETD voltage), event 20 (sleep.mode.status), event 11 ETD (x.acceleration, y.acceleration)

G717-specific: events 29/30/31 (plug.alarm, unplug.alarm, trip.type, sos.alarm), DTT bits 16-18 (engine.ignition.status)