flespi telematics hub supports maxtrack protocol. The list of supported devices Maxtrack MXT-100 Maxtrack MXT-101 Maxtrack MXT-120 Maxtrack MXT-130 Maxtrack MXT-140 Maxtrack MXT-141 Maxtrack MXT-150 Maxtrack MXT-151 Maxtrack MXT-160

Maxtrack protocol is updated. The following changes occurred: for MXT-130 and MXT-160 devices - parameter battery.status is renamed to battery.state[text] . for the rest devices parameter batery.status is rеnamed to battery.connected.status[boolean] Both old and new parameters are registered now. Old parameters will be removed 17-feb-2020.

[Changelog] maxtrack protocol

baja

flespi telematics hub supports maxtrack protocol.

Maxtrack

The list of supported devices

namo

Maxtrack protocol is updated. The following changes occurred:

for MXT-130 and MXT-160 devices - parameter battery.status is renamed to battery.state[text].
for the rest devices parameter batery.status is rеnamed to battery.connected.status[boolean]

Both old and new parameters are registered now. Old parameters will be removed 17-feb-2020.

namo

namo
Old parameters removed.

namo

Parameter renaming in maxtrack protocol: engine.ignition.state.enum parameter is renamed into ignition.state.
Both parameters will be registered during one week. 17-Apr-2020 old parameter engine.ignition.state.enum will be removed.

namo

namo
Maxtrack protocol updated: old parameter engine.ignition.state.enum is removed after renaming.

baja

New parameters parsing added for Maxtrack protobuf devices:
Events:
configuration.change.event
battery.fail.event
power.state.enum
ignition.event
input.active.event
output.active.event
configuration.change.event
gnss.state.enum
alarm.panic.status
external.powersource.status
gnss.antenna.status
battery.fail.event
gsm.jamming.alarm.status
sleep.mode.status
alarm.mode.status
battery.low.status
Device details:
product.model.enum
battery.level
battery.voltage
power.state.enum
device.temperature
device.uptime
device.lifetime
battery.use.duration
reboot.reason.enum
last.reboot.id
vehicle.battery.state
Connectivity block:
wifi.status
zigbee.status
gsm.jamming.event
gsm.sim.status
gsm.module.status
gsm.module.status
gsm.network.roaming.status
gsm.network.status
gsm.network.status
gsm.mcc
gsm.mnc
gsm.lac
gsm.cellid
gsm.signal.dbm
gsm.timing.advance
Ignition calibration block:
ignition.calibration.automatic
ignition.calibration.timestamp
ignition.calibration.min.detected
ignition.calibration.max.detected
ignition.calibration.min.used
ignition.calibration.max.used
ignition.calibration.voltage

baja

Maxtrack protobuf part bugfix: parameter extnav.position.speed renamed to position.speed

baja

Maxtrack binary protocol GPS rollover issue fixed: If timestamp of the message received is less then current time for 619315200 seconds with +/- 24 hours then timestamp is shifted by GPS epoch seconds forward.

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).