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

Added Beacon record version #2 of Command 38/138 – Beacon Data Sending via GPRS data parsing

baja

serial_port command added for Ruptela devices. It is command 114 Transparent Channel data under the hood

you need to specify only data and port_id, all other will be compiled by flespi

baja

parameter renaming announcement which will happen in a week (May 22):
parameter total.idle.seconds will be renamed to total.idle.time

namo

Ruptela protocol is updated: IO IDs 420 - 480 Mobileye J-1939 Output Protocol are supported.

baja

namo parameter names for Mobileye slightly renamed. The current version can be easily tracked at Message Parameters tool:

baja

Bugfix in "Connection data" setting: protocol field (was numeric 0/1) has now string type with values "TCP" or "UDP".

EvgenyShatilo

Added the ability to remotely download data from a tachograph.

What you need to do to download the file:

Download the Tacho Bridge Application from our repository on github.
Configure according to the instructions.
Send a command to download the file.
Provided that the tachograph and tracker are configured correctly, authentication will be successful and the file will be uploaded to the server.

EvgenyShatilo

Improvements to Tachograph Functionality:

The ability to specify a time frame when loading data from the tachograph memory has been removed.
Improved server behavior if the card for authentication is not connected or the card number is not specified in the device configuration.
- If the card number is missing in the device configuration, the command will be rejected and the event "The company card configuration field is not specified in the device settings. The tachograph operation cannot be started." will be registered in the device logs
- If the configuration is completed, but the device is not connected to the server, the server will make 3 attempts to access the card with an interval of 60 seconds, then the command will also be rejected. An unsuccessful request to the card will register an event in the log of the following type: "The Company card '4220000000000000' is not online. The tachograph operation cannot be started. Request attempt 1/3".
  If the card connects to the server at this time, a command will be sent to the device and the file will start downloading.

EvgenyShatilo

Improvements to Tachograph Functionality:

Increased control over the command and improved stability of file download.
Fixed a bug that sometimes appeared when re-downloading a file in the same connection.
Changed the command scheme:
before: {"name":"request_tachograph_file","properties":{"tachograph_file_type":"1"}
after: {"name":"request_tachograph_file","properties":{"type":"driver1"}
Possible variations of the type:
```
"driver1" - Driver slot 1
"driver2" - Driver slot 2
"memory" - Tachograph memory
```
Changed file name saving. Now it is more consistent with tachograph regulations.
Before: 2024-11-25_16-37-10+0000.ddd
After: M_20241127_1242__.DDD - tacho memory, C_20241127_0949__.DDD - driver card file.
Card number and driver name are temporarily not used.
Correction of server behavior in case the company card is offline.

baja

New device types added:

baja

Parsing updated. IDs 1201 to 1220 are now stored to parameters manual.can.1 to manual.can.20. As the values are taken from 8 byte fields, and JSON is limited with 53 bits, the values are duplicated in text HEX represented parameters manual.can.hex.1 to manual.can.hex.20.
Parameter names used previously (custom.param.1201 to custom.param.1220) will be removed in 2 weeks on February 3rd 2025.

baja

baja custom.param.1201 to custom.param.1220 removed

EvgenyShatilo

New device types added:

Ruptela Smart5

EvgenyShatilo

Changed the Dynamic identification packet setting:

Fixed the problem with displaying the parameters. It might not work for some models.
Updated the list of models for displaying it.

namo

Ruptela protocol is updated: IO_IDs 860-870, 874, 875, 1146, 1147 are supported.
Corresponding custom parameters will be removed in two weeks 2025-03-27.
Be sure to finish transition of your application to the new parameters by that date.

namo

Ruptela protocol updated: custom parameters for implemented IO_IDs are removed after transition period.
namo

YuryAheichyk

Removed outdated params:

accident.din
accident.overspeeding.status
accident.extreme.braking.status
accident.harsh.breaking.status
accident.harsh.acceleration.status

Fixed IO 201 value registration, it's now registered as can.adblue.level

EvgenyShatilo

Tacho functionality update.

The configuration scheme has been changed. Now the configuration that relates to the tachograph is packed into an object that have to be activated before use. The company card number input field is mandatory.
Important:

The tachograph configuration has been migrated to the new scheme on the server side.
The Automatic file request option is not yet available for use and is undergoing active testing. Will be updated later.

EvgenyShatilo

Added new Action settings for Plug5:

Add Authorized ID (Add peripheral (iButton, RFID, or magnetic card) ID, that is allowed to unblock or register)
Delete Authorized ID (Delete peripheral (iButton, RFID, or magnetic card) ID, that is allowed to unblock or register)
Get GPS (Get current GPS status and coordinates)

EvgenyShatilo

Added new Tracking & Profile 1-4 settings for Plug5:
Tracking:

ECO-drive: Overspeeding limit
ECO-drive: Braking limit
ECO-drive: Harsh acceleration limit
ECO-drive: Cornering limit
Eco-drive: Idling
Set odometer value

Profile 1-4:

Data sending
Data collection
Coefficients
Constant link, keep alive and heartbeat