flespi telematics hub supports ruptela protocol. The list of supported devices Ruptela FM-Plug4 Ruptela FM-Tco4 HCV Ruptela FM-Tco4 LCV Ruptela FM-Pro4 Ruptela FM-Eco4 Ruptela FM-Eco4 light Ruptela FM-Pro3 Ruptela FM-Eco3 Ruptela FM-Tco3 Ruptela FM-Eco4+ S Ruptela FM-Eco4+ T Ruptela FM-Eco4+ E T Ruptela FM-Eco4 light T Ruptela FM-Eco4 light+ T Ruptela FM-Eco4+ 3G E T Ruptela FM-Eco4+ 3G T Ruptela FM-Eco4+ light 3G T Ruptela FM-Eco4+ 3G E RS T Ruptela FM-Eco4 light+ 3G RS T Ruptela HCV5 Ruptela LCV5 Ruptela PRO5 Ruptela Trace5 Ruptela Plug5 Ruptela HCV5 Lite Ruptela PRO5 Lite Ruptela Eco5 Ruptela Eco5 Lite Ruptela Eco5 Lite+ Ruptela Eco5 BM Ruptela Smart5 Ruptela Asset5

Ruptela protocol updated: ident parsing fixed. Now idents always consist of 15 digits ( IMEI of device).

IO_ID 481: CAN Fuel level 2 is supported for ruptela protocol.

IO_ID 626: CAN DTC Indication lights is supported for ruptela protocol

IO_ID 141: ECO normal speed distance is supported as segment.normal.speed.distance parameter IO_ID 142: ECO cruise control distance is supported as segment.cruise.control.distance parameter IO_ID 143: ECO cornering counter is supported as segment.cruise.control.distance parameter for ruptela protocol

The following IO_IDs are supported for ruptela protocol: IO_ID 584: G Peak X - max.x.acceleration IO_ID 585: G Peak Y - max.y.acceleration IO_ID 586: G Peak Z - max.z.acceleration

Ruptela protocol updated: parameter can.liquid.sensor.fuel.volume (IO_ID 205) is renamed to can.fuel.volume For backward compatibility both parameters are registered for now. Old parameter will be removed 25 Nov 2019.

Settings added: secondary server for connectivity card Eco-driving over speeding limit (as a wrapper for setcfg/getcfg ParameterID 400)

Settings added: econnect - to force device for a single connection to specified IP:port data_sending - Enable/Disable, Min records, Period, Link timeout - configuration group data_collection - Enable/Disable, Logging interval, Time without engine, Engine detection - configuration group coefficients - for Distance, Time with engine and Radial - configuration group

namo Ruptela protocol updated: can.liquid.sensor.fuel.volume parameter is removed

Constant link, keep-alive and heartbeat setting added for connection profiles Parsing of IO IDs 104 - 106, 123 - 125, 152 - 154 for vehicle.vin corrected. Contact us if you note some misparsing for vehicle.vin parameter.

[Changelog] ruptela protocol

bird

Fixed handling of the coords / SMS-via-GPRS command reply: a short non-conformant reply (missing the trailing state field) no longer drops the device connection — it is returned as the command result and a warning is logged. Conformant replies are unchanged.

bird

Major auto-upload scheduler changes

The tachograph auto-upload scheduler has been substantially reworked to fix duplicate commands and retry timing.

Fixed duplicate request_tachograph_file commands. Because command enqueueing is asynchronous, a device could receive several copies of the same request in quick succession (up to 3 within one second on production) before the first was registered. Each scheduled request is now stamped the moment it's enqueued, so subsequent packets in that window no longer enqueue duplicates.
Unified retry-by-timeout. Lost commands, expired sessions and offline company cards now all recover through a single retry timeout rather than separate stuck-state handling. Requests also self-expire from the device queue, so stale copies don't pile up across reconnects.
Smarter scheduling. While one file type is being uploaded, other due types wait their turn instead of triggering extra requests, and the company-card availability check runs once per attempt instead of on every packet.
Fixed a scheduler stall. A missing card-in-slot status parameter no longer blocks retries (it previously stalled scheduling on devices that don't report that parameter).

Significant under-the-hood improvements accompany these changes. No configuration changes are required, and scheduler behavior is now more correct without affecting normal protocol operation.

EvgenyShatilo

Standardization of tacho parameters:
A new parameter, #tacho.driver.card.code[index=N], has been added, which duplicates the value of #tacho.fms.driver.id[index=N]. This new parameter is standard for all protocols, so the old FMS parameter will be removed on August 3, 2026.

EvgenyShatilo

Standardization of tacho parameters:
Added registration of new parameters in accordance with other tacho protocols:

#tacho.driver.work.state.enum[index=N]
#tacho.driver.work.state[index=N] (0 ==> "rest", 1 ==> "available", 2 ==> "work", 3 ==> "drive", 6 ==> "error", 7 ==> "not available", error ==> "unexpected tacho work state value %s")
which duplicate the #tacho.fms.driver.status.enum parameter, which will be removed on August 3, 2026.

bird

Fixed unit conversion (minutes to seconds) for TCO_CAN tachograph durations (total driving time, current activity duration, continuous driving time, break time) on ruptela tachograph devices. These four values were previously reported 60x too small.

bird

Bugfix for tachograph devices: a smart-card data announcement received with no active upload session is now answered with a card-reject acknowledgement instead of a device reset. This stops affected devices from rebooting and reconnecting in a loop when they have pending card data left over from an interrupted download.

EvgenyShatilo

Tacho update: fixed auto-download loop and file type mix-up on slow driver card downloads
On some devices (noticed on HCV5 Lite a driver card download takes 12-15 minutes, while the tacho session tolerated only 10 minutes of silence. The session expired mid-download and the scheduler issued the next command while the tachograph was still busy - causing a download loop and files stored
under the wrong type. Now the session survives up to 15 minutes of silence, so slow but alive downloads complete normally.

bird

Tachograph: automatic card T protocol switching on authentication failure. When a remote tachograph card authentication fails, the next authentication attempt is opened with the alternate ISO 7816 T protocol (T=0 / T=1), since the wrong card T protocol is a known cause of authentication errors. Errors that occur after file transfer has started are not affected. This requires Tacho Bridge App 0.8.0-alpha.4 or newer to take effect; older Tacho Bridge App versions are unaffected.

EvgenyShatilo

Tacho update: fixed connection drop with internal error when a tracker reconnects in the middle of a tachograph file upload and tries to continue sending file data. Since a partially uploaded file cannot be resumed, such data fragments are now rejected with negative ACK, so the tracker discards the pending data and uploads the whole file from scratch on the next request.

bird

Fixed parsing of the tachograph End of Last Daily Rest Period field (TCO_CAN, IO 871/872) for HCV5 Lite devices: a far-future date in this field (beyond the representable timestamp range) is now skipped instead of dropping the connection, so affected devices stay connected and continue reporting.

EvgenyShatilo

Tachograph update: fixed duplicated file requests when the tachograph is slow to answer the authorization. The upload session now outlives the tracker's own authorization timeout, is prolonged only by tachograph packets, and the command lock is restored correctly after a reconnect. Every scheduled attempt used to be sent twice on such devices, with a spurious "authorization task already created" entry in the tachograph log.

EvgenyShatilo

Tacho update:

Tachograph file download is collected on the server side and survives connection loss: after a reconnect the download continues without a new tachograph authentication.
VU (memory) file: when the tracker offers to resume after a link break, the server answers with the last received packet and the tracker continues from the next one instead of starting over.
Card file: after a reconnect the tracker re-sends the file from the beginning (card data has no packet index), the server no longer rejects it.
VU file is checked against the CRC16 announced by the tracker; on mismatch the file is not saved and the command fails with an explicit reason.
A data packet for a download the server has no start of is rejected, the command fails at once instead of waiting for the session timeout.

bird

Fixed parsing of tachograph parameters for HCV5, HCV5 Lite, FM-Tco4 HCV and Pro5 devices:

tacho.driver.daily.limit.exceed.number.1 and .2 are split per driver, one byte each
driver 2 working state (IO 216) is registered as can.tacho.driver.activity.enum.2
error and not-available values are filtered from tacho.position.speed, can.tacho.position.speed, can.wheel.speed, tacho.driver.card.code.N and tacho.fms.driver.id.N

EvgenyShatilo

Tachograph live activity parameters standardization

To make tachograph data consistent across all flespi protocols, we introduced unified live driver activity parameters (per card slot, .1 / .2):

tacho.driver.activity.state.enum - current activity: 0 - rest, 1 - work, 2 - drive, 3 - available, 4 - not available, 5 - error
tacho.driver.activity.state - the same as text: rest / work / drive / available / not available / error
tacho.driver.activity.duration - current activity duration, seconds

The new activity parameters are reported both from the TCO driver state (IO 159 / 160) and from the CAN tacho driver working state (IO 215 / 216).

The following parameters are deprecated and will be removed on 01.11.2026:

tacho.driver.work.state.enum -> tacho.driver.activity.state.enum (attention: enum values differ from the old ones)
tacho.driver.work.state -> tacho.driver.activity.state
tacho.driver.current.activity.duration -> tacho.driver.activity.duration
can.tacho.driver.activity.enum -> tacho.driver.activity.state.enum (attention: enum values differ from the old ones)

Please update your expressions, calculators, plugins and streams before the removal date.

EvgenyShatilo

tacho changes: Internal refactoring of tachograph download handling. No functional changes.