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

EvgenyShatilo

Tacho functionality update: fixed the problem of parsing the tacho file and generating the full file name.

EvgenyShatilo

Tacho functionality update:

Fixed the problem of prematurely sending a command to load tacho data when the previous one was not yet completed. Improved control and stability of loading. Reason: the first generation tacho in some cases can respond to server communication commands for a long time, due to which the server tried to repeat the loading.
Fixed parsing of the plate number value for GEN.2 tacho. Where there could be a space between groups of characters. For example, "AAA 1111", the space will be removed "AAA111". This solves the problem of the file path, when some systems can incorrectly process file names in which there are spaces, and also standardizes the use of the number.
Added parsing of the plate number for GEN.1 tacho. Previously absent. was: M_20250806_1752__W1XXX111555666777.DDD became M_20250806_1752_AAA111_W1XXX111555666777
Improved parsing of text fields of the file that relate to driver identification, for driver card data. First of all, this concerns the driver's first and last name.

EvgenyShatilo

Tacho functionality update: Fixed file name formatting.

fixed a problem where an incomplete file name was registered, for example: DRIVERNAME_DRIVERID00000000001.ddd instead of the full name: "C_20250820_1023_S_LASTNAME_DRIVERID00000000001.ddd". The problem was that if the driver has a double last name or if the last name is written in a file as a double last name, for example "SURENAME/SURENAME", the server cut the file name to the "/" character because such a character is not allowed in a file name and is prohibited in most versions of operating systems, such as MacOS and Linux, and is not always correctly detected in Windiws. Now such a symbol is cut at the parser level, so if the driver has a double surname, the full file name will look like this: "C_20250820_1023_S_SURENAMESURENAME_DRIVERID00000000001.ddd".
The problem of registering an incorrect extension for the regions of France and Spain has been fixed. Despite the correct definition of the driver's region in the file, the extension was always ddd. Previously it was: V_0001_E_20250812_1235.ddd, now it is: V_0001_E_20250812_1235.tgd.
Fixed the problem of an empty name in a correctly formatted file name, for example: C_20250819_1001___XXX0000003X00001.ddd, will now be C_20250819_1001_S_SURENAME_XXX0000003X00001.ddd. The problem was related to the fact that the fields with the driver's first/last name unloaded from different tachograph standards have an internal flag that specifies the presence and validity of the name, which is now processed correctly.
Added additional check for file extension (ddd, tgd, v1b, c1b), it will always be in lower case so that it is equally well processed by different operating systems and applications.

EvgenyShatilo

Tacho functionality update: Fixed file name formatting.

Changed parsing of driver's surname depending on region: "A", "AND", "B", "CH", "D", "DK", "E", "F", "FL", "UK", "I", "IRL", "L", "N", "NL", "P", "RSM", "S", "V". Symbol mismatch corrected.
Fixed name format for France. Now file name parameters are separated by underscore "_" to improve readability and the ability to automatically parse the file name, because parameters can have floating value sizes. For example, state number does not contain a fixed number of characters, etc.
Before:
VU file: FXX-NNN-ZZ2508011746.V1B Driver file: FXX-NNN-ZZ2508011746.C1B
After:
VU file: F_XX-NNN-ZZ_2508011746.V1B Driver file: F_XX-NNN-ZZ_2508011746.C1B

EvgenyShatilo

Tacho functionality udpate. Fixed encoding parsing error, more details here.

EvgenyShatilo

Tacho functionality udpate: improve processing errors and tracker behavior.

EvgenyShatilo

Tacho functionality udpate: added ignition check for automatic upload tacho data.
The protocol has three ignition sources: #virtual.engine.ignition.status, #config.engine.ignition.status, and #can.engine.ignition.status. The tracker can send all three simultaneously. The protocol checks telemetry parameters and their last update time.

Conditions:

If none of the parameters exist, the interval check is performed by default, for each message.
If at least one of the parameters is present and the last update time is no older than 2 days, its value will be used.
If three parameters are present, they will be checked against the update time (2 days) and will be used in descending order of priority (CAN, config, virtual).

EvgenyShatilo

Tacho functionality udpate: request_tachograph_file command changes.

The command now has the ability to request a detailed memory file.
- Select specific files within the tachograph's memory (overview, activity, speed details, technical data, events, and faults).
- Activity data can be specified for a specific time interval from and to. Or, the last N days from the current time can be specified.
The command structure has changed, but this does not affect previously generated API requests.
- Parameters for requesting driver data have not changed: {"type":"driver1"}
- Parameters of the form: {"type":"memory"} will work, since the new parameters are optional and have default values.
- What it looks like now: {"activity":{"days":90},"detailed_speed":true,"events_faults":true,"overview":true,"technical_data":true,"type":"memory"}
- This is what the from/to time interval looks like: {"activity":{"from":1761589095,"to":1761761895},"detailed_speed":true,"events_faults":true,"overview":true,"technical_data":true,"type":"memory"}
By default, all parameters are enabled and the data interval is requested for the last 90 days.

namo

Ruptela protocol is updated:

parsing of BLE MAC addresses is refactored
added id for MAC only type of beacons in ble.beacons array

EvgenyShatilo

Tacho functionality udpate: Improved tachograph file parsing, thereby correcting errors in generating the correct file name.

EvgenyShatilo

Tacho functionality udpate: now partial parsing of a file is registered in the file's meta data.
Example:
{"command_id":1762522256318151,"content":{"VehicleIdentificationNumber":["WDB123456789TEST1"],"VehicleRegistrationIdentification":[{"vehicleRegistrationNation":"DE","vehicleRegistrationNumber":"AB 1234 CD"}],"VuDownloadActivityData":[{"companyOrWorkshopName":"Test Logistics GmbH","downloadingTime":1762000000,"fullCardNumber":{"cardIssuingMemberState":"DE","cardNumber":"000000000TEST001","cardType":4}}]},"plate_number":"AB1234CD","region":"DE","type":"tacho","vin":"WDB123456789TEST1"}

namo

Ruptela protocol is updated: implemented parsing of IO IDs 292-351, 727, 728, 742, 965 - 968, 1152, 1153, 1187 - 1189

EvgenyShatilo

Tacho functionality udpate: Improved tacho file parsing. Support for more data and fixing inaccuracies. Gradually standardizing towards a uniform format.

EvgenyShatilo

Tacho functionality udpate:

Added generation of a default file name in case something went wrong with parsing or data sent by the tracker, examples: "M_20250922_1535.ddd", "C_20250922_1535.ddd"
Improved file parsing.
Minor bug fixes.

EvgenyShatilo

Tacho functionality udpate: improve tacho file parsing.