Navtelecom protocol has advanced level of support in flespi telematics hub. The following devices are supported at the moment: Navtelecom Smart S-2330 Navtelecom Smart S-2332 Navtelecom Smart S-2333 Navtelecom Smart S-2413 Navtelecom Smart S-2420 EASY Navtelecom Smart S-2421 EASY+ Navtelecom Smart S-2422 MID Navtelecom Smart S-2423 MID+ Navtelecom Smart S-2425 COMPLEX Navtelecom Smart S-2430 Navtelecom Smart S-2433 Navtelecom Smart S-2435 Navtelecom Signal S-2550 Navtelecom Signal S-2551 Navtelecom Signal S-4651 Updates of navtelecom protocol will be posted in this topic.

Settings are supported for Navtelecom Smart S-242X devices - now you can use Universal device configurator for these devices.

Navtelecom protocol updated: parameter can.liquid.sensor.fuel.volume is renamed to can.fuel.volume For backward compatibility both parameters are registered for now. Old parameter will be removed 25 Nov 2019.

namo Navtelecom protocol updated: can.liquid.sensor.fuel.volume parameter is removed

Navtelecom FLEX protocol is updated - device state field parsing is improved: bit 0: if 1, test.mode.status=true parameter is registered bit 1: if 1, alarm.mode.status=true parameter is registered bit 2: if 1, alarm.event=true parameter is registered bits 3 и 4: are registered as parameter operating.mode.enum with possible values 0 - 3 - working mode according to the Navtelecom protocol documentation

Announcement: Commands identify and version will be deleted from Navtelecom protocol in a week, 11-Jun-2020. Please, use custom command instead, see examples here

Navtelecom protocol update is planned for tomorrow 2020-09-16, 12:00 UTC - parsing will be switched to new parsing engine. This is an internal process, no changes in devices' work are expected.

namo Navtelecom protocol updated to new parsing engine.

Navtelecom protocol updated - some new flex bits supported: flex bit 201 value is stored into can.security.bitmask parameter flex bit 203 value is stored into can.indicators.bitmask parameter flex bit 204 value is stored into can.mil.bitmask (1 byte) and can.dtc (4 bytes) parameters

Navtelecom protocol updated: fixed parsing of timestamp for NTCB protocol. This affects devices that send data as telemetry message structures F6.

Navtelecom protocol updated: added boolean parameter enfgine.ignition.status , and it's value corresponds to bit0 status of FLEX field 29 ( Current states of digital inputs 1 - 8 ) - din parameter in flespi. This will be convenient for those users who connect in1 to engine ignition as it's recommended by the manufacturer.

[Changelog] navtelecom protocol

namo

New settings added for Navtelecom Smart S-24XX devices, Actions tab:

RFU Connect - force device to connect to remote firmware upgrade service
Version - request device's model and firmware version, response is stored in device.model.enum flespi parameter
ICCID - request device's SIM ICCID, response is stored in gsm.sim.iccid flespi parameter
Calibrate Accelerometer - to manage device's embedded accelerometer calibration. Device replies with several messages containing accelerometer calibration status, which is stored in accelerometer.calibration.state flespi parameter

namo

The following settings for configuration and connection to Device Remote Control (DRC) service are added for Navtelecom Smart S-24XX devices:

DRC Service on Configuration tab:
DRC Connect, DRC Disconnect on Actions tab:

namo

New parameters are supported for Navteletcom protocol: 1-byte, 2-bytes, 4-bytes and 8-bytes user-defined values. Mapping to flespi parameters is the following:

flex ids 207 - 222 User-defined 1 byte parameters - sensor.uint8.value.1 - sensor.uint8.value.16
flex ids 223 - 237 User-defined 2 bytes parameters - sensor.uint16.value.1 - sensor.uint16.value.15
flex ids 238 - 252 User-defined 4 bytes parameters - sensor.uint32.value.1 - sensor.uint32.value.15
flex ids 253 - 255 User-defined 8 bytes parameters - sensor.uint64.value.1 - sensor.uint64.value.3

namo

New device supported: Navtelecom Signal S-4651

namo

Navtelecom protocol updated, parameters tyre.pressure and tyre.temperature are renamed to
tire.pressure and tire.temperature
Old parameters will be registered until 05-Jan-2022 together with the new ones. Old parameters will be removed 05-Jan-2022.

namo

New device type is added: Navtelecom Smart S-2413

namo

New settings added for devices Smart S-2333, Smart S-2433 and Smart S-2435:
Additinal Server 1 and Additional Server 2, Connectivity tab

baja

The protocol will be affected by the change in type of parameters gsm.mcc and gsm.mnc to be installed in 2 weeks - May 23rd, 2022: both parameters that now have type "string" will be stored as "number". The possible leading zeroes in MNC will be ignored (e.g. the value "01" will be stored as 1).

namo

Navtelecom protocol updated: the following parameters are renamed:

liquid.sensor.fuel.volume.1 - liquid.sensor.fuel.volume.16 are renamed into rs485.lls.value.1 - rs485.lls.value.16 correspondingly
liquid.sensor.fuel.temperature.1 - liquid.sensor.fuel.temperature.16_ are renamed into rs485.lls.temperature.1 - rs485.lls.temperature.16 correspondingly
rs485.fuel.sensor.frequency.1 - rs485.fuel.sensor.frequency.16 are renamed into rs485.lls.frequency.1 - rs485.lls.frequency.16 correspondingly
liquid.sensor.fuel.volume is renamed into rs232.lls.value
liquid.sensor.fuel.temperature is renamed into rs232.lls.temperature

For backward compatibility, both old and new parameters will be registered until 13-Jun-2022.
13-Jun-2022 we will remove old parameters. Please make sure you code is fully transfered to the new parameters names until the mentioned date.

namo

namo
Navtelecom protocol is updated: old parameters are removed after renaming.

baja

custom command can be sent via SMS using text parameter now.

custom command will be remastered in 1 week January 4th: You will be able to send it using anyOf rule: binary command payload may be sent inside hex field as hex-formatted string, text command may be sent using text field.

baja

baja update installed

YuryAheichyk

The protocol will be affected by the change in parameter can.dtc to be installed in 2 weeks - Mar 15th, 2024: the parameter can.dtc is currently of string type and will be converted to type array with separate DTC codes.

Added parameter can.dtc.array as an example of future implementation of can.dtc

YuryAheichyk

YuryAheichyk changes have been applied, the can.dtc parameter type changed to array

baja

parameter renaming announcement which will happen in a week (May 22):
parameter device.model.enum will be renamed to device.model

YuryAheichyk

Fixed Input/Output - Line2 setting response parsing