Dear Friends! Most of you probably already know that flespi telematics hub supports atrack protocol. The following devices are supported: ATrack AX7 ATrack AX9 ATrack AX11 ATrack AK1 ATrack AK7S ATrack AK11 ATrack AL7 ATrack AL11 ATrack AP1 ATrack AU7 ATrack AS1 ATrack AS3 ATrack AS11 ATrack AT5i ATrack AY5i ATrack AK500 ATrack AL300 ATrack AS500 ATrack AX300 ATrack AK300 ATrack AK7 ATrack AL1 ATrack AS300 ATrack AS700 ATrack AX100

Atrack protocol updated - added new custom fields are supported for both binary and text protocol format: %GN - 10Hz G sensor data - flespi parameter acceleration.array (g) %EH - Engine hour - flespi parameter engine.motorhours (hours) %EO - Odometer - flespi paramter vehicle.mileage (kilometers)

Atrack protocol updated - several new event/status parameters are supported: %HA - Vehicle harsh acceleration event status - parameter harsh.acceleration.event %HB - Vehicle harsh brake event status - parameter harsh.braking.event %HC - Vehicle harsh cornering event status - parameter harsh.cornering.event %OC - OBD-II connect status - parameter obd.connected.status %CS - Server connection status - parameter server.connection.status %CR - GSM registration status - parameter gsm.home.network.event %RO - Roaming status - parameter gsm.roaming.network.event %PF - Preferred Network status - parameter gsm.preferred.network.status %GF1 - %GF32 - Geofence event status - parameters geofence.status.1 - geofence.status.32 %IP - Impact event status - parameter impact.event %PL - Main power low event status - parameter main.power.low.status %SF - GPS fix status - parameter gnss.fix.status %BT - Bluetooth connection status - parameter bluetooth.connected.status

ATrack protocol updated: added parsing of iBeacon , Eddystone and ELA BLE accessories from %BC custom field. Parameters are stored as ble.beacons json array, for example: "ble.beacons": [ { "battery.voltage": 3.273, "id": "AC233F222111", "rssi": -39, "temperature": 6.4, "tx.power": -24 }, { "battery.voltage": 32.768, "id": "FA5292222111", "rssi": -46, "temperature": 0, "tx.power": -23 }, { "battery.voltage": 32.768, "id": "CED3D8222111", "rssi": -43, "temperature": 0, "tx.power": -23 } ] if("undefined"!==typeof hljs)hljs._ha();else if("undefined"===typeof hljsLoading){hljsLoading=1;var a=document.getElementsByTagName("head")[0],e=document.createElement("link");e.type="text/css";e.rel="stylesheet";e.href="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.7.0/styles/default.min.css";a.appendChild(e);e=document.createElement("script");e.type="text/javascript";e.onload=function(){var d={},f=0;hljs._hb=function(b){b.removeAttribute("data-hljs");var c=b.innerHTML;c in d?b.innerHTML=d[c]:(7

[Changelog] atrack protocol

namo

New Custom info fields supported for User Define Report in atrack protocol:
%CG - GPRS status
%GP - GPS status
Applicable for AT5 and AU7 devices

baja

device ATrack AK11 added

namo

Atrack protocol updated - added new custom fields are supported for both binary and text protocol format:

%GN - 10Hz G sensor data - flespi parameter acceleration.array (g)
%EH - Engine hour - flespi parameter engine.motorhours (hours)
%EO - Odometer - flespi paramter vehicle.mileage (kilometers)

namo

Atrack protocol updated - several new event/status parameters are supported:

%HA - Vehicle harsh acceleration event status - parameter harsh.acceleration.event
%HB - Vehicle harsh brake event status - parameter harsh.braking.event
%HC - Vehicle harsh cornering event status - parameter harsh.cornering.event
%OC - OBD-II connect status - parameter obd.connected.status
%CS - Server connection status - parameter server.connection.status
%CR - GSM registration status - parameter gsm.home.network.event
%RO - Roaming status - parameter gsm.roaming.network.event
%PF - Preferred Network status - parameter gsm.preferred.network.status
%GF1 - %GF32 - Geofence event status - parameters geofence.status.1 - geofence.status.32
%IP - Impact event status - parameter impact.event
%PL - Main power low event status - parameter main.power.low.status
%SF - GPS fix status - parameter gnss.fix.status
%BT - Bluetooth connection status - parameter bluetooth.connected.status

namo

Atrack protocol updated: Report ID field is now parsed as report.reason parameter.

namo

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

namo

namo
Atrack protocol updated

namo

New device types added for Atrack protocol: AL11, AS11 and AX11.

namo

ATrack protocol updated: added parsing of iBeacon, Eddystone and ELA BLE accessories from %BC custom field.
Parameters are stored as ble.beacons json array, for example:

"ble.beacons": [
    {
        "battery.voltage": 3.273,
        "id": "AC233F222111",
        "rssi": -39,
        "temperature": 6.4,
        "tx.power": -24
    },
    {
        "battery.voltage": 32.768,
        "id": "FA5292222111",
        "rssi": -46,
        "temperature": 0,
        "tx.power": -23
    },
    {
        "battery.voltage": 32.768,
        "id": "CED3D8222111",
        "rssi": -43,
        "temperature": 0,
        "tx.power": -23
    }
]

baja

Atrack protocol custom "at" channel level command now returns response
"Vehicle odometer" (ODOM command) setting added
"Device info" (INFO command) read-only setting added

kial

"Position Report Format" (AT$FORM) setting added
"J1939 Information Format" (AT$FMSC) setting added to AK11 device type
"J1708 Information Format" (AT$1708) setting added to AK11 device type

kial

Here is the purpose of adding the settings mentioned in kial

All ATrack devices have a configurable position message format. Such a configuration can be set and requested by the AT$FORM=... command. The ATrack AK11 devices have additional configuration params related to CAN data: AT$FMSC and AT$1708.
So, the platform needs to know such configuration params set on the device to correctly parse all incoming packets from it.

Previously we were sending AT$FORM, AT$FMSC, and AT$1708 requests on every TCP connection after successful ATrack device login.

But most of the ATrack devices have static AT$FORM, AT$FMSC and AT$1708 configuration - users usually set it on the device once, and change it not too often. So we decided to cache such a configuration if the user has a corresponding flespi device instance.

That change resulted in the following:

the flespi platform will ask the tracking device for such a configuration only once and will no more waste device's traffic asking it on every connection
users got a REST API and a handy UI to see, change, or cleanup cached configuration in the flespi device instance at the Settings tab (or using SetBox tool)
when users change AT$FORM, AT$FMSC, or AT$1708 configuration format not through the flespi device instance (or SetBox) but through SMS or USB - they should clean up the cached configuration value in the flespi device instance, so the configuration request will be sent on the next device connection

namo

kial
"J1939 Information Format" (AT$FMSC) and "J1708 Information Format" (AT$1708) settings supported for ATrack AX11 device.

namo

Atrack protocol is updated: Seq. ID field, that was skipped previously, is now stored as event.seqnum flespi parameter.

namo

Atrack protocol is updated: %DC (Distance traveled since DTC codes cleared, km) custom field is supported. It's value is registered into flespi parameter can.dtc.cleared.mileage.
This change is applicable to ATrack AX11 device model.

namo

Atrack protocol is updated - the following J1708 CAN data fields are added:

ZO1 - Brake Stroke Status - flespi parameter can.j1708.brake.stroke.state
ZO2 - Attention/Warning Indicator Lamps Status - flespi parameter can.j1708.mil.state
ZO3 - ABS Control Status - flespi parameter can.j1708.abs.state
ZO4 - Throttle Position - flespi parameter can.j1708.throttle.pedal.level, %
ZO5 - Parking Brake Switch Status - flespi parameter can.j1708.parking.brake.state
ZO6 - Road Speed - flespi parameter can.j1708.vehicle.speed, km/h
ZO7 - Cruise Control Status - flespi parameter can.j1708.cruise.control.state
ZO8 - Percent Accelerator Pedal Position - flespi parameter can.j1708.accelerator.pedal.level, %
ZO9 - Percent Engine Load - flespi parameter can.j1708.engine.load, %
ZO10 - Fuel Level - flespi parameter can.j1708.fuel.level, %
ZO11 - Engine Oil Pressure - flespi parameter can.j1708.engine.oil.pressure, kPa
ZO12 - Boost Pressure - flespi parameter can.j1708.boost.pressure, kPa
ZO13 - Intake Manifold Temperature - flespi parameter can.j1708.intake.manifold.temperature, Celsius
ZO14 - Engine Coolant Temperature - flespi parameter can.j1708.engine.coolant.temperature, Celsius
ZO15 - Brake Application Pressure - flespi parameter can.j1708.brake.pressure, kPa
ZO16 - Brake Primary Pressure - flespi parameter can.j1708.brake.primary.pressure, kPa
ZO17 - Brake Secondary Pressure - flespi parameter can.j1708.brake.secondary.pressure, kPa

The update is applicable for ATrack AK11 device.

namo

New custom fields are added for Atrack protocol:

ES - OBD Speed (km/h) - flespi parameter can.vehicle.speed
GR - LTE reference signal received power (RSRP) - flespi parameter network.signal.rsrp

namo

New custom fields are added for Atrack protocol:

ZH1 - Cargo Weight - flespi parameter can.j1708.cargo.weight, N
ZH2 - Fuel Rate (Instantaneous) - flespi parameter can.j1708.fuel.rate, 10e-6L/s
ZH3 - Engine Speed - flespi parameter can.j1708.engine.rpm, rpm
ZL1 - Total Fuel Used - flespi parameter can.j1708.fuel.used, liters
ZL2 - Total Vehicle Distance - flespi parameter can.j1708.vehicle.mileage, km
ZL3 - Total Vehicle Hours - flespi parameter can.j1708.vehicle.motorhours, hour
ZL4 - Total Engine Hours - flespi parameter can.j1708.engine.motorhours, hour
ZL5 - Total Idle Hours - flespi parameter can.j1708.idle.motorhours, hour
ZL6 - Total Idle Fuel Used - flespi parameter can.j1708.fuel.used.idle, liters

namo

Output Control settings are added for ATrack AK11, ATrack AK7V and ATrack AK7S devices, INPUT/OUTPUT tab:

namo

ATrack protocol updated: parsing of the following J1939 custom data fields is fixed:

%JH8 Service distance - flespi parameters can.service.mileage - offset -160635km was missing, now it's applied
%JH10 Ambient Air Temperature - flespi parameter can.ambient.air.temperature - offset -273°C was missing, now it's applied