baja Parsing changes: IDs 45 to 48 parsed as counter.din.hours.1 to counter.din.hours.4 are now stored in hours (previously stored raw value in seconds) new parsing for IDs 577 to 580 to parameters counter.din.cumulative.hours.1 to counter.din.cumulative.hours.4 . Raw value in seconds is also converted to hours.
YuryAheichyk Improved parsing of J1939 and J1708 DTC codes in the Command 9/109 – Diagnostic Trouble Codes report
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
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 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.
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.
