flespi telematics hub supports cellocator protocol. The list of supported devices Cellocator CelloTrack Cellocator CelloTrack Nano Cellocator CelloTrack 10Y Cellocator CelloTrack Solar Cellocator Cello CAN iQ Cellocator Cello IQ Cellocator CR-200 Cellocator CR-300 Cellocator CR-400 Cellocator Cello-F Cellocator MiniTrack

cellocator protocol updated: Sub Data type 0x16 - Fleet End of Trip Report - is supported for message type 9.

Cellocator protocol updated: Parsing of odometer value has changed and now works as follows: if device is registered and has current value of Odometer Unit setting - odometer reading is converted to km and stored as vehicle.mileage parameter otherwise - odometer reading is registered as vehicle.odometer parameter with unit unspecified (the unit may be miles, kilometers or 100 meters, configured in the device) Odometer Unit setting is supported for CR-300 devices:

The following modules are supported for Message Type 11 of Cellocator protocol: Module 25: Trigger Event ID Module 2: Variables Dump List Applicable for Cellocator Cello CAN iQ . These modules are sent as parts of the Cello-CANiQ Trigger event message. They identify the trigger Event ID and the Cello-CANiQ variables list attached to the event. The variable dump list is a programmable list of CAN variables selected when the user builds the CAN triggering. Please refer to “Cello-CANiQ Integration Manual” for more details.

Module 41 Legacy (Type-0) Encapsulated Message module supported for Message Type 11 of Cellocator protocol.

cellocator protocol updated: Sub Data type 0x19 - 1-Wire sensors data - is supported for message type 9.

Cellocator protocol updated: Sub Data type 0x0D Compressed Vector Change Report is added for Message Type 9.

Cellocator protocol updated: MCGP protocol message type 11 parsing refactored. Besides other changes, the following parameters are renamed: sensor.temperature.1 is renamed to sensor.temperature sensor.humidity.1 is renamed to sensor.humidity This parameters are registered for Module 40 Measurement Readings . Both old and new parameters are registered now. Old parameters will be removed 31-jan-2020.

Output state change setting is supported for CR-300 devices:

namo Cellocator protocol updated: old parameters removed after renaming.

Programming command (message type 1) added for cellocator protocol. It allows to configure the cellocator devices.

[Changelog] cellocator protocol

namo

namo
Cellocator protocol switch to the new parsing engine is postponed till the next Thursday, 3-Sep-2020 12:00 UTC.

namo

namo
Cellocator protocol is updated to new parsing engine

namo

Commands of Cellocator protocol are refactored. The following changes was introduced:

New command Generic Command - custom_message_type_0 is implemented.
This command is to be used instead of status, reset, track_time, engine_stop commands which will be removed in a week, 3-Sep-2020. Examples may be found here.

New command Modular Message Request - custom_message_type_9 is implemented.
This command is to be used instead of firmware, can, location commands which will be removed in a week, 3-Sep-2020. Examples may be found here.

New command Programming Command - custom_message_type_1 is implemented. This command is a replacement for prog_cmd command which will be removed in a week, 3-Sep-2020. Examples may be found here.

namo

namo
Cellocator protocol updated:
commands status, reset, track_time, engine_stop, firmware, can, location and prog_cmd are removed.

namo

New settings added for Cellocator CR-300 device: Request Position and Request Connect to Server, Actions tab:

namo

Cellocator protocol updated: added parsing of Message Type 11 > Module 28 > Events:

1 - Impact
16 - Free-fall

Parameter acceleration.rms is registered for these events: acceleration RMS value of (X²+Y²+Z²), where each of the axes is in 250µg units.

namo

namo
One more Module 28 event is supported for Message type 11 for cellocator protocol:

Event 15 MultiSense Door/Window Open/Close - flespi parameter door.open.status

namo

Cellocator protocol updated: added parsing of Message Type 11 > Module 28 > Events:

3 - Man Down - flespi parameter mandown.alarm.status=true is registered for this event
11 - Check-In
18 - Sudden Pressure Change - flespi parameter altitude.difference is registered for this event (value is in meters)
19 - Check-out by timeout event
20 - Check-out by user event
23 - MultiSense button pressed event - flespi parameter button.pressed.event=true

namo

namo
Cellocator protocol updated: added parsing of one more Message Type 11 > Module 28 event:

21 - No MultiSense received

Time elapsed from the last reception of sensor value is stored into flespi parameter sensor.reading.fix.age

namo

The list of supported devices for Cellocator protocol has been extended to include the following ones:

namo

Some changes in parameters are introduced for Cellocator protocol:

parameters din and dout are deprecated and will be removed in a week, 30-Mar-2021 at 9:00 UTC approx.
parameters device.io.bitmask.1 - device.io.bitmask.4 are registered instead, containing 1st - 4th Bytes of Device's I/O Status accordingly

namo

namo
Cellocator protocol is updated: deprecated parameters are removed.

namo

Cellocator protocol updated: added new modules of Message type 11:

Module 70: Driver Behavior Event
Module 75: Driver Behavior Maneuver Extended Data

namo

Cellocator protocol is updated: Event Code 13 (Guest MultiSense raw data) of Module 28 (General Status Event) is supported.
The following flespi parameters are registered:

sensor.rssi.1 - byte 10 RSSI, dBm
sensor.mac.address - bytes 11-16 MAC Address
sensor.battery.voltage.1 - bytes 18-19 Battery Level, V
sensor.temperature - bytes 26-27 Temperature, Celsius degrees
sensor.humidity - bytes 28-29 Humidity, %
sensor.illumination - bytes 30-31 Light Level, lux
sensor.x.acceleration - bytes 33-34 Last measured X acceleration, g
sensor.y.acceleration - bytes 35-36 Last measured Y acceleration, g
sensor.z.acceleration - bytes 37-38 Last measured Z acceleration, g
sensor.battery.voltage.2 - bytes 39-40 Battery Level, V
temperature.alert - bit 2 of byte 41, Temp Alert
himidity.alert - bit 6 of byte 41, Humidity Alert
sensor.rssi.2 - byte 42 RSSI, dBm

namo

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:

sensor.mac.address - MAC Address
sensor.battery.level - Battery level, %
sensor.rssi - Last RSSI value (SR-RF) (Signed, dBm units)

namo

The following settings are added for Cellocator CelloTrack Nano device, Actions tab:

Request Position
Request SIM ICCID
Connect to Server
Reset Unit

namo

Cellocator protocol is updated: Module 1 - DTC Event of Message Type 11 is supported.
The following flespi parameters are registered for this module:

moduel.id=1 signifying that Module 1 DTC Event is received from the device
can.dtc.number - Number of DTCs received by Mode 3
can.dtc (indexed parameter, optional) - Mode 3 DTCs
can.pending.dtc (indexed parameter, optional) - Mode 7 DTCs

namo

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:

byte 10: RSSI - sensor.rssi, dBm
bytes 11 - 16: MAC Address - sensor.mac.address
bytes 18,19, bits 0-13: Battery Level - sensor.battery.voltage, volts
byte 25, bits 5-7: Zone # - sensor.zone

namo

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:

bytes 10,11: Serving Cell MCC - gsm.mcc
bytes 12,13: Serving Cell MNC - gsm.mnc
bytes 14,15: Serving Cell LAC / TAC - gsm.lac
bytes 16 - 22: Serving Cell Global Cell ID - gsm.cellid
bytes 23, 24: Serving Cell PSC / Physical Cell ID - gsm.pcid
byte 25: Serving Cell Reference Signal Received Power, dBm - network.signal.rsrp
byte 26: Serving Cell Access Technology: 2G=0, 3G=2, 4G=7 - gsm.network.type

For the neighbor cells, if any, the same parameters are registered additionally with indexes starting from 1.

namo

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

Calibration Status - calibration.status: true - calibration is in progress, false - calibration is finished
Engine - engine.ignition.status: true - ignition is On, false - ignition is OFF
Driver ID - driver.id
Event Reason 2 - Accident (Crash) event:
-- crash.event=true will always present for Accident (Crash) event
-- Crash Orientation- crash.direction.enum
-- Roll - rollover.alarm.status: true - roll detected, false - roll not detected
-- Parking - crash.movement.status: true - crash while driving, false - crash while parking
Event Reason 5 - Calibration event:
-- Calibration Status - calibration.state.enum
-- Calibration Step - calibration.step
-- Calibration Phase - calibration.phase
Event Reason 6 - Harsh Acceleration:
-- harsh.acceleration.event=true will be registered for this event
Event Reason 7 - Harsh Braking:
-- harsh.braking.event=true will be registered for this event
Event Reason 8 - Harsh Turn:
-- harsh.turn.event=true will be registered for this event
-- harsh.turn.right.event=true will be registered for right turn detected
-- harsh.turn.left.event=true will be registered for left turn detected
Event Reason 9 - Over Speeding:
-- overspeeding.event: true - for Over Speeding Start event, false for - Over Speeding Stop event.

Module 75: Driver Behavior Maneuver Extended Data

Maneuver Type: depending on the value one of the following parameters will ve registered:
-- maneuver.harsh.acceleration.event=true
-- maneuver.harsh.braking.event=true
-- maneuver.harsh.turn.right.event=true
-- maneuver.harsh.turn.left.event=true
-- maneuver.overspeeding.event=true
Maneuver Start Longitude - maneuver.start.longitude ,degrees
Maneuver Start Latitude - maneuver.start.latitude, degrees
Maneuver Stop Longitude - maneuver.stop.longitude, degrees, registered only for over speeding event
Maneuver Stop Latitude - maneuver.stop.latitude, degrees, registered only for over speeding event
Maneuver Start GPS Fix - maneuver.start.position.valid: true - GPS fix is valid, false - no GPS fix
Maneuver Start time and date - maneuver.start.timestamp, seconds
Maneuver Stop GPS Fix - maneuver.stop.position.valid: true - GPS fix is valid, false - no GPS fix, registered only for over speeding event
Maneuver Stop time and date - maneuver.stop.timestamp, seconds, registered only for over speeding event
Maneuver Duration - maneuver.duration, seconds
Max X Acceleration - maneuver.max.x.acceleration, g
Max Y Acceleration - maneuver.max.y.acceleration, g
Max Speed - maneuver.max.speed, km/h
Turn Direction Change - maneuver.harsh.turn.angle, degrees

Module 46: 2G/3G/4G Cell-ID: see parameters layout in this post namo

namo

Cellocator protocol is updated: now position parameters are copied into all messages for different modules of Message Type 11.