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

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