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

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

[Changelog] assistant-telematics protocol

bird

AVT110 / AVT111 tachograph updates:

Tacho Check Information is now decoded into readable parameters: tacho.kline.bus.state, tacho.communication.state, tacho.download.state (each with a matching .enum), covering K-Line bus, tachograph communication, and remote DDD download states. The raw tacho.check.info.bitmask remains available.
+CMI (CAN Module Information) report is now parsed into vehicle.model.id, vehicle.model.name and can.connection.state.
Bugfix: AT@TCO tachograph operations (check interfaces, inquiry model/status, etc.) now complete correctly instead of retrying and being canceled.

bird

AVT110 / AVT111 tachograph: a failed tachograph authorization (for example an expired or mismatched company card) is now reported as an authentication error with the device's reply result and error code, instead of the download appearing to stall silently. A successful authorization is unchanged.

EvgenyShatilo

assistant-telematics: tachograph remote download improvements:

request_tachograph_file command now fails with a detailed error description based on the CAN-Logistic extended error code instead of a generic message, e.g. Tachograph error 0x02: No communication with tachograph. Switch the ignition on and try again. or Tachograph error 0x6E: Authentication error. Check that the company card is not expired.
Device Status and File State In Memory bytes are now decoded into new human-readable parameters: tacho.state (e.g. authentication in progress), tacho.state.error.code + tacho.state.error (e.g. no answer from tachograph (wrongly connected wires or CAN-C is off in tachograph)), and tacho.file.state (e.g. tachograph file is in memory, card slot 1 file is in memory).

namo

Assistant-telematics protocol is updated: fixed parsing of zero values of GNSS UTC Time field for +DFI report.
The fix is applicable for AVT110 and AVT111 device types.

bird

Fixed can.vehicle.mileage precision for AVT110/AVT111 devices - the value is now reported as a clean decimal (e.g. 302812.1 km) instead of a floating-point artifact (302812.10000000003).

bird

Tachograph: automatic card T protocol switching on authentication failure. When a remote tachograph card authentication fails with an error that can be caused by the card using the other ISO 7816 T protocol (T=0 / T=1) - no ATR response, APDU error, authentication error, or an error during the authorization process - the next authentication attempt is opened with the alternate T protocol. This requires Tacho Bridge App 0.8.0-alpha.4 or newer to take effect; older Tacho Bridge App versions are unaffected.

bird

AVT110 — new configuration settings added:

GSM Jamming Alarm (AT@JAM) — jamming detection thresholds
Regular Report Setting (AT@RRS) — Fixed Mileage report mode and mileage threshold
Movement Alarm (AT@MOV) — motion threshold, durations, and motion event report
Ignition Settings (AT@IGN) — now includes Output1 ignition-on restrict (Limit Outputs Mask)
CAN Module Setting (AT@CMS) — CAN speed/engine-speed limits and acceleration/braking thresholds
CAN Alarm Setting (AT@CAS) — CAN alarm mode, debounce, and per-input alarm mask (central lock, doors, trunk, hood)

bird

AVT110: CAN Advanced Information Mask 1 and 2 are now supported — CAN advanced PID values are reported as can.data.frame indexed by PID number (1-63), in HEX.

AVT110: ECL Trigger State Mask 1 and 2 are now supported, reported as ecl.trigger.bitmask.1 and ecl.trigger.bitmask.2.

AVT50: the ECL trigger mask moves from ecl.trigger.bitmask to ecl.trigger.bitmask.1. Both parameters are registered now; on 2026-08-26 the unindexed parameter will be removed.

bird

AVT110 — new BLE settings added:

BLE Broadcast Setting (AT@BBS) — configure BLE broadcast working mode, transparent data interval/length, and report target.
BLE Transparent Transmission (AT@TRB) — send data from the server to the BLE master connected to the tracker.

namo

Assistant-telematics protocol is updated: the following CANBUS Info Alarm Events are supported:

17 Electric Car Start Charging
18 Electric Car Keep Charging
19 Electric Car Stop Charging

The update is applicable for AVT110 device type.

namo

Assistant-telematics protocol is updated: Upgrade code field under the Upgrade Information Mask in RPT report is now stored into flespi parameters firmware.update.code and upgrade.status.name.