flespi now works with Assistant Telematics devices. The list of supported models: ATL100 AVT110 AVT111 AVT131 AVT20 AVT50 ABT110

Assistant Telematics protocol updated: fixed parsing of can.fuel.level parameter

Added Electric CAN Data parsing

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"}]

Added BLE data parsing from AVT20 devices

YuryAheichyk changes applied, can.dtc array contain objects now. For reference, two additional parameters added: can.dtc.strings - contains errors in the old format (will be removed on May 24, 2025 ) can.dtc.objects - contains errors in the new format (will be removed on May 24, 2025 ) can.dtc.strings example: ["P0020","U0001"] can.dtc.objects example: [{"standard":"OBDII","code":"P0020"},{"standard":"OBDII","code":"U001"}]

YuryAheichyk changes applied, can.dtc.strings and can.dtc.objects parameters removed

timestamp parameter is now taken from the Generated time field. position.timestamp - from the GNSS UTC time . send.timestamp parameter removed.

Bugfix: parameter position.timestamp now stored in timestamp. Using position.timestamp instead of timestamp broker the consistency of the track build using messages that came in a batch in one packet.

Added BLE Ranging Distance parameter parsing from ATL100

[Changelog] assistant-telematics protocol

namo

Assistant-telematics protocol is updated: Bits 26-20 of CAN information Mask 2 (RPT report) are supported.

YuryAheichyk

Added UART1 Information data block parsing

namo

Assistant-telematics protocol is updated: parsing of BLE MAC addresses is refactored.

YuryAheichyk

Fixed Network type data parsing from ATL100 devices according to the protocol version 1.06

baja

Indexed parameters tire.pressure, tire.temperature and tire.underpressure.status parsing added
together with parameter gsm.network.type string parameter added gsm.network.type.enum with numeric representation (raw value sent by the device)

YuryAheichyk

Fixed can.vehicle.mileage parameter parsing, the wrong divisor was used when converting from Hm to Km

baja

New device type supported: ABT110

baja

New parameters added for AVT11X devices: configuration.command.id, configuration.update.result, configuration.download.url - support for Data mask bit 22 (Upgrade Config Information Mask)

shal

New parameters added for crash data: crash.events.number, self.calibration.state, x.acceleration, y.acceleration, z.acceleration.

New parameters added for tachograph common event: tacho.reply.result, tacho.state.bitmask, tacho.file.state.bitmask, tacho.error.code, tacho.stored.error.code, tacho.apdu.hex, tacho.producer, tacho.model, tacho.driver.time.state.enum, tacho.can1.state, tacho.can2.state, tacho.check.info.bitmask.

Event Type 24 (CAN bus Info Event) and Event Type 25 (Tachograph Common Event) now produce event.name parameter with descriptive event reason.

bird

ABT110: Fixed neighbor cell parsing to use 11-byte format per v1.03 specification (MCC + MNC + LAC + CellID + CSQ). New parameters: gsm.mcc and gsm.mnc for neighbor cells.

New Event Types supported for ABT110 and other device families:

Event Type 8 (Light Alarm): light.alarm, event.name — ABT110 uses nibble composite (Front/Rear + Enter/Quit)
Event Type 9 (Built-in Temperature Alarm): temperature.high.alarm, temperature.low.alarm
Event Type 11 (Upgrade Firmware): event.name with states for MCU, CAN, Network Module, BOOT
Event Type 31 (External Humidity Alarm): humidity.alarm, event.name — nibble composite
Event Type 32 (Jamming Alarm): gsm.jamming.event
Event Type 36 (RF433 Alarm): event.name
Event Type 42 (External Distance Alarm, ABT110): distance.alarm, event.name — nibble composite

Event Type 0 (Terminal Power): added states 6-11 (key on/off, watchdog on/off, upgrade firmware, PING interval)
Event Type 1 (Regular Report): added states 1 (RTO Request Position) and 2 (SOS Button Alarm) with sos.alarm

Unknown event types now generate unsupported warnings for future implementation.

bird

New Event Types supported:

Event Type 6 (Flight Mode) for ATL100: event.name with states Auto/Manual Enter, Auto/Timeout Quit
Event Type 10 (Humidity Alarm) for ATL100: humidity.alarm, event.name
Event Type 26 (Tachograph DDD File Upload): event.name with states Start/Success/Failed
Event Type 33 (Tilt Alarm) for AVT50: tilt.event

Event Types 4 (Free Fall), 5 (Tilt), 20 (G-Sensor Self-Calibration), 27 (Output Alarm), 28 (Delta AIS), 34 (BLE iBeacon Info) are now recognized and no longer generate unsupported warnings.

Unknown event types on non-matching device families now generate unsupported warnings for future implementation.

bird

New tachograph parameters added for AVT110/AVT111 devices:

tacho.performance — tachograph information bitmask (driver working states, card info, motion/direction/overspeed)
tacho.overspeed.status — tachograph overspeed signal
tacho.motion.status — tachograph vehicle motion signal
tacho.driving.direction — tachograph driving direction (0=forward, 1=reverse)
29 indexed tacho.driver.* parameters for Driver 1 and Driver 2 working time: remaining drive time, rest periods, daily/weekly driving durations, compensations, cumulative break/driving time, and more