Cellocator protocol is updated: Event code 8 (MultiSense Added) and Event code 9 (MultiSense Removed) of Module 28 (General Status Event) are supported.
The following flespi parameters are registered for these events:
The following settings are added for Cellocator CelloTrack Nano device, Actions tab:
Cellocator protocol is updated: Module 1 - DTC Event of Message Type 11 is supported.
The following flespi parameters are registered for this module:
Event code 17: Tag mode MultiSense raw data of Module 28 of Message type 11 is supported for CelloTrack Nano device. The following parameters are registered:
Module 46 - 2G/3G/4G Cell-ID of Message Type 11 is supported for Cellocator protocol.
The following flespi parameters are registered for this module:
For the neighbor cells, if any, the same parameters are registered additionally with indexes starting from 1.
Cellocator protocol is updated: now position parameters are copied into all messages for different modules of Message Type 11.
New settings are added for Cellocator Cello IQ: Dallas Key 2 and Dallas Key 3, Miscellaneous tab:
Module 90: Primary Battery Fuel Gauge Status is supported for Message type 11 of Cellocator protocols. The following flespi parameters are registered for this module:
The update is applicable for Cellocator CelloTrack 10Y
Cellocator protocol updated: added Module 35 EDR Crash Attributes and Module 43 Calibration Matrix Response of CSA (Cellocator Safety Application) OTA Protocol
Mapping to flespi parameters is the following:
Module 35
Module 43
Cellocator protocol is updated as a part of big refactoring process. The following changes are introduced.
Modules 46: 2G/3G/4G Cell-ID, 70: Driver Behavior Event and 75: Driver Behavior Maneuver Extended Data will not be registered a separate message any more, instead all parameters that come for these modules will be registered into one message for each packet received from device.
Below is a layout of modules values into flespi parameters.
Module 70: Driver Behavior Event
Module 75: Driver Behavior Maneuver Extended Data
Module 46: 2G/3G/4G Cell-ID: see parameters layout in this post namo
Below is a layout of values of MultiSense modules of message type 11 into flespi parameters for Cellocator CelloTrack Nano
Module 40: Measurement Readings
"sensor.readings": [
{
"timestamp": 1636952492,
"value": 41.8
},
{
"timestamp": 1636952552,
"value": 41.9
},
{
"timestamp": 1636952612,
"value": 42
},
...
]Module 42: Nano Inherent Sensors
Module 44: MultiSense Additional Information
Below is a layout of values of MultiSense module 28 of message type 11 into flespi parameters.
Applicable for Cellocator CelloTrack Nano
Module 28: General Status Event
Since this module can contian several events, parameters event.category and event.enum are registered with indices staring with 1 and increasing by 1 for the second and subsequest events (if present). If module 28 contains only one event - only one pair of parameters will be registered: event.category and event.enum without indexes.
The other parameters depend on the event.category and event.enum value.
event.enum=1 (event.category=1): Impact
event.enum=3 (event.category=1): Man Down
event.enum=4 (event.category=1): Package Open/Closed
event.enum=7 (event.category=1): MultiSense Provisioning
event.enum=8 (event.category=1): MultiSense Added
event.enum=9 (event.category=1): MultiSense Removed
event.enum=10 (event.category=1): Work-ID/Activation
event.enum=13 (event.category=1): Guest MultiSense raw data
event.enum=15 (event.category=1): MultiSense Door/Window Open/Close
event.enum=16 (event.category=1): Free-fall
event.enum=17 (event.category=1): Tag mode MultiSense raw data
event.enum=18 (event.category=1): Sudden Pressure Change
event.enum=21 (event.category=1): No MultiSense received
event.enum=23 (event.category=1): MultiSense button pressed event
Cellocator protocol is going to be updated tomorrow, as a part of big refactoring of the protocol implementation. Upgrade will affect the following Modules of Message Type 11:
Modules will not be registered as separate messages any more, instead all parameters that come for these modules will be registered into one message for each packet received from device. Also, the message will contain several boolean parameters that denote the modules contained, e.g. for the packet that carries modules 40, 42 and 44 in it, the message will contain parameters:
"module.id.40": true,
"module.id.42": true,
"module.id.44": true,Posts namo and namo describe the mapping of Modules bytes into flespi parameters, that will be introduced with the tomorrows update.
The update is applicable for Cellocator CelloTrack Nano
Module 38 J1939 DTC Appeared/Disappeared of Message type 11 is supported.
This module is sent by Cellocator Cello CAN iQ device.
The layout of bytes of the module to flespi parameters is below:
Here is an example of Cellocator message that is registered for a Cellocator CelloTrack Nano packet that contains Module 28 General Status Event and Module 42 Nano Inherent Sensors.
{
"channel.id": 111,
"device.battery.level": 71,
"device.firmware.version": "34p",
"device.illuminance": 0,
"device.pressure.altitude": -42.1,
"device.temperature": 38.4,
"device.temperature.valid": false,
"device.x.acceleration": 0.011,
"device.y.acceleration": -0.03025,
"device.z.acceleration": -0.991,
"event.category": 1,
"event.enum": 13,
"gps.mode.1": 4,
"gps.mode.2": 2,
"gsm.signal.dbm": -77,
"hardware.version.enum": 122,
"ident": "2338333",
"measurement.source.13": 252,
"message.buffered.status": true,
"message.type": "11",
"module.id.28": true,
"module.id.42": true,
"peer": "127.0.0.1:43944",
"position.altitude": -30.2,
"position.direction": 250.726331,
"position.hdop": 1,
"position.latitude": 25.738857,
"position.longitude": -80.262057,
"position.satellites": 6,
"position.speed": 2,
"private.status": false,
"protocol.id": 9,
"sensor.battery.voltage.252": 2.926,
"sensor.group.id.252": 2,
"sensor.humidity.252": 33.1,
"sensor.humidity.alert.252": false,
"sensor.illuminance.252": 23,
"sensor.mac.address.252": "481ABBBBDDDD",
"sensor.report.reason.252": 6,
"sensor.rssi.252": -35,
"sensor.temperature.252": 30.6,
"sensor.temperature.alert.252": false,
"sensor.x.acceleration.252": 0,
"sensor.y.acceleration.252": -0.064,
"sensor.z.acceleration.252": -0.32,
"server.timestamp": 1638959705.789526,
"time.valid.status": true,
"timestamp": 1636582654
}Parameter message.type=11 shows that this is a modular message, and parameters module.id.28=true and module.id.42=true show that this message contains modules 28 and 42.
According to this post namo, for Module 42 you should expect parameters device.battery.level, device.illuminance, device.pressure.altitude etc to be present in the JSON message.
As for Module 28, you should first read event.category and event.enum parameters, as the set of parameters to be contained in the JSON message depends on the type of event received.
The message in my example has event.enum=13 and event.category=1 parameters, hence this is a Guest MultiSense raw data event. The list of parameters to be expected for this event can be found in this post namo.
Parameter measurement.source.13=252 (or 0xFC) tells you that this is an event from Guest MultiSense. Then parameters sensor.battery.voltage.252, sensor.group.id.252, sensor.humidity.252 etc with MultiSense related information should be expected in the JSON message.
Cellocator protocol updated: added Module 63 Crash Maneuver Statistics of CSA (Cellocator Safety Application) OTA Protocol
Mapping to flespi parameters is the following:
Module 63
Parameter maneuver.type.enum of Cellocator protocol is replaced by the parameter maneuver.type.
New parameter maneuver.type is a numeric value that comes from Maneuver Type byte of CSA (Cellocator Safety Application) OTA Protocol modules.
Old parameter maneuver.type.enum will be removed in a week, 29-Dec-2021.
Cellocator protocol is updated: added system parameter timestamp.key.
Integer part of its value is a message timestamp, and the fractional part is a sequence number of the message.
The parameter is used to distinguish between two messages with the same timestamp of seconds granularity.
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).
