[Changelog] squarell protocol

namo

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

namo

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

namo

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

namo

Squarell protocol is updated: Telltale messages are supported.

namo

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

EvgenyShatilo

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.

EvgenyShatilo

Settings update: tab INFO added readonly setting $PortDiag.

EvgenyShatilo

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.

EvgenyShatilo

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.

EvgenyShatilo

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.