New protocol is supported in flespi telematics hub: Squarell This is a changelog topic for the Squarell protocol. The list of supported Squarell devices Squarell REMOTE

Squarell protocol updated: implemented parsing of $FMS8 , $FMS10 and $FMS12 messages

Squarell protocol is updated: parsing of double values in $FMS1 message is fixed.

Squarell protocol is updated: Telltale messages are supported.

Squarell protocol is updated. Several configuration settings are added on Tracking tab:

New settings have been added: Getting extended device information . Tab: INFO . Under the hood, this setting executes the $ExtendedVersion command. The setting contains the following fields: Product code, serial number, DCF name, Versions of HW, SW, FW, DDF, GDS, and Product profile. A profile verification mechanism has been added. If the tachograph function is deactivated, a warning will be displayed in the 'device data processing warning' log, containing the following: " Tachograph functionality is disabled. To activate it, you need to update the product profile of the device. Please contact the manufacturer " The TACHO tab has been added. Settings for the following commands: $TachoK , $SetTachoK , $ReqRTDCAN for controlling the tachograph communication bus width and other settings.

Settings update: tab INFO added readonly setting $PortDiag.

Fix parsing of the vehicle.vin parameter in the $fms2 packet. Now, if the parameter contains an invalid value like 0xFF0xFF0xFF0xFF..., the parameter will not be registered.

Parser improvement: Improved $Telltale parsing, which is sometimes returns only one parameter instead of three. Temporarily enabled registration of the #tacho.driver.card.status ($FMS3) and #vehicle.vin ($FMS2) parameters to prevent the parser from breaking. While downloading tachograph data, a packet containing invalid data may arrive, which breaks the parser and interrupts the download.

Added registration of the #engine.ignition.status parameter. This parameter depends on the $POWERON and $SHUTDOWN tracker events. The ignition status is changed only by sending these two events. There are no other flags or bitmasks that convey the ignition status in regular messages.

[Changelog] squarell protocol

EvgenyShatilo

Fixed parsing of the $Telltale package, as it may contain a 'floating' number of parameters.

EvgenyShatilo

Added the ability to download tachograph data!

Company card setup for remote tachograph authentication here.
General guide: Using Tachograph functionality

Added functionality:

Download driver card data
Detailed download of tachograph memory data. (Ability to specify a specific time interval and select the required data types)
Automatic download via the device configuration in the panel.

Recommendations for connection and configuration:

The physical connection is quite sensitive and must be made according to all manufacturer's instructions and specifications.
The tracker profile must be updated to 017-700. Profile updates can ONLY be performed remotely by the manufacturer. A special request must be made. You can check the current profile in the COMMAND & SETTINGS > INFO > Extended device info tab. The "Product profile of the device" field.
Tachograph data such as driver card numbers, activity status, etc. can only be retrieved when connected to the K-line physical bus.
It is necessary to use the correct Kbaud value for communication between the tracker and the tachograph. By default, the tachograph uses 250. You can also check this in the settings: COMMAND & SETTINGS > TACHO > Request CAN Bus Kbaud value.
When using the "Request tachograph file" command to download tachograph memory data, a limitation of the last 70 days is set from the time the command was sent. The value can be adjusted manually, but at your own risk, as if the value exceeds 79.9 days, the tachograph can often respond with an error that occurs in the tracker's firmware.
The tachograph data download command will not be executed if the ignition is off. This is controlled by the #engine.ignition.status parameter, which regulates the tracker with different types of messages. A message similar to the following will also be logged: "Ignition is OFF. Unable to start the tachograph data download process."

EvgenyShatilo

Tacho functionality udpate:

Improved tacho file parsing.
Fixed memory file naming.
Added parsed file data to meta > content.

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.

EvgenyShatilo

Tacho functionality update: сorrections have been made to the logging process of downloading tachograph data.

EvgenyShatilo

Tacho functionality update:

fixed parsing of the tacho file when saving content, and also fixed the formation of the name for the tacho memory.
Improved stability of uploading data.

EvgenyShatilo

Tacho functionality udpate: Updated automatic download mechanism. More details here.

EvgenyShatilo

Tacho functionality bug fix. Fixed a bug in the automatic download configuration related to the download interval. For some devices, this value could be ignored, and downloading file types specified in the configuration could be repeated every 20-30 minutes, regardless of the interval setting. The issue has now been fixed, and the system is operating normally.

EvgenyShatilo

Tacho functionality udpate: Added ignition check before sending a command when using the automatic scheduler. The server monitors the #engine.ignition.status telemetry parameter, which the tracker periodically sends as an event in $SHUTDOWN,IGNITION packets, which is logged as
false ==> #engine.ignition.status, as well as $POWERON,IGNITION, which is logged as true ==> #engine.ignition.status

EvgenyShatilo

Tacho functionality update: Improved timeout mechanism between sending commands when using the automatic download scheduler.