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

YuryAheichyk

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

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

YuryAheichyk

Added driver.id parameter obtained from IO 760 and IO 761.
custom.param.760 and custom.param761 parameters will be removed in a 2 weeks - 20-Jun-2025

YuryAheichyk

YuryAheichyk changes applied, custom.param.760, custom.param.761 parameters removed

EvgenyShatilo

Tacho functionality update:

Added automatic file upload. Can be configured in the device configuration.
Added upload file type to each log related to tacho activity.
Improved upload stability.

EvgenyShatilo

Tacho functionality update:
Improved the auto upload mechanism. Now before sending a command to load a file, the server will check whether the company's card is online, if not, then the timeout will be increased by 5 minutes. Previously, if the card was offline, this could lead to the accumulation of a large number of tacho commands in the queue.

EvgenyShatilo

Fixed parsing of the #tacho.fms.driver.id parameter, which could cause a parsing error.

EvgenyShatilo

Tacho functionality update: Improved automatic download management mechanism.

EvgenyShatilo

Tacho functionality update:

FIxed issue where the tracker could send data for a card that requires authorization in the middle of downloading a file, which could lead to a disruption of the download process and an error.
Improved stability of file downloading.
Added display of additional tachograph operation states in the log message "Tachograph specific status"

EvgenyShatilo

Tacho functionality update: added registration of tachograph file metadata in the saved file that will be finalized. NOTE: parameters will be added only if the corresponding data was provided by the tracker or correctly parsed from the uploaded file.
List of the parameters:

plate_number - vehicle registration number
region - vehicle registration region.
vin - vehicle VIN number
driver_first_name - driver's first name
driver_last_name - driver's last name
driver_id - driver card identifier

EvgenyShatilo

Tacho functionality update: fixed a parsing error during tachograph data loading that could block normal operation of the device. The problem was related to the device not receiving a correct response from the server.

EvgenyShatilo

Tacho functionality update: the case when the device sends tacho data after the tacho process was rejected by the server is covered. Now such tracker behavior will not cause a parser error.

EvgenyShatilo

Tacho functionality update:

Added logging of all specific tachograph codes if something goes wrong. Will be registered as a log 340: tacho communication (Tachograph specific status):
command_sub_id : 3 command_sub_id_description : "APDU packet in the data field" packet_status : 2 packet_status_description : "Error"
Fixed an issue with authentication of some versions of Stoneridge models with the server.

EvgenyShatilo

Tacho functionality update: minor bug fixes. Improved stability.

EvgenyShatilo

Tacho functionality update: fixed an issue that could cause uploaded files to be incomplete or corrupted.