This topic will be used to post changes in calamp protocol implementation. The following devices are supported CalAmp LMU-200 CalAmp LMU-300 CalAmp LMU-400 CalAmp LMU-600 CalAmp LMU-700 CalAmp LMU-800 CalAmp LMU-900 CalAmp LMU-1100 CalAmp LMU-1200 CalAmp LMU-2030 CalAmp LMU-2130 CalAmp LMU-2600 CalAmp LMU-2720 CalAmp LMU-2820 CalAmp LMU-3035 CalAmp LMU-3640 CalAmp LMU-4200 CalAmp LMU-4220 CalAmp LMU-4230 CalAmp LMU-4233 CalAmp LMU-4520 CalAmp ATU-620 CalAmp TTU-720 CalAmp TTU-1200 CalAmp TTU-2830 CalAmp TTU-3640

Command update. We added custom command for sending messages with type 4, 5, 6, 7. You need to select the command type and insert HEX data into the command body. The header of the data is generated automatically up to the "Sequence number" field. The rest of the data must be generated by the user. As an example, we can use the command to request a current position: 80010700000A00000000000000. The header is "8001070000" <80> // Options header <01> // Service type: 1 - Acknowledged request <07> // Message Type: 7 - Unit Request Message <00 00> // Sequence Number: The remaining data must be inserted as the command body: 0A00000000000000. 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 Changing the indexing of the accumulator# parameter. The change will affect formats 0 - Standard Accumulator Reporting and 3 - Enhanced Accumulator Reporting (alternative 256-bit) data structures. At the moment, the parameter index starts from 1, will be changed to 0. Changes will take place in 2 weeks(15.03.2023) from today (01.03.2023). If you need more time, please contact us flespi team.

[Changelog] calamp protocol

namo

This topic will be used to post changes in calamp protocol implementation.

The following devices are supported

namo

Parameter network.roaming.status is renamed into gsm.network.roaming.status for calamp protocol.
For the sake of backward compatibility both old and new parameters are registered now.
Old parameter will be removed in a week, 06-Jul-2021.

namo

namo
Old parameter network.roaming.status is removed.

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

CalAmp protocol is updated: added engine.ignition.status parameter that comes from the bit0 of Inputs byte of the Event Report (Type 2), User Message (Type 4), App Message (Type 5) and Locate Report (Type 8) and Mini Event Report (Type 10).

⚠️ Important note: All 8 bits of the Inputs byte was historically registered into din parameter. Since bit0 of the Inputs byte in now registered separately into engine.ignition.parameter, then only the rest of bits (1-7) will be registered into din parameter. This change will be installed in a week, 05-Sep-2022, so that you have time to prepare.
For example,
Inputs byte 0x9D = 157 = 0x10011101 now is registered as two parameters:

engine.ignition.status=true
din=157

After the update is installed at 05-Sep-2022, it will be registered as parameters:

engine.ignition.status=true
din=78

If you have any questions regarding the upcoming update, please contact us in chat

namo

The update namo is installed: din parameters is now registered from bits 1-7 of Inputs byte

EvgenyShatilo

Command update. We added custom command for sending messages with type 4, 5, 6, 7. You need to select the command type and insert HEX data into the command body. The header of the data is generated automatically up to the "Sequence number" field. The rest of the data must be generated by the user. As an example, we can use the command to request a current position: 80010700000A00000000000000.

The header is "8001070000"
<80> // Options header
<01> // Service type: 1 - Acknowledged request
<07> // Message Type: 7 - Unit Request Message
<00 00> // Sequence Number:
The remaining data must be inserted as the command body: 0A00000000000000.

Changing the indexing of the accumulator# parameter.
The change will affect formats 0 - Standard Accumulator Reporting and 3 - Enhanced Accumulator Reporting (alternative 256-bit) data structures. At the moment, the parameter index starts from 1, will be changed to 0. Changes will take place in 2 weeks(15.03.2023) from today (01.03.2023). If you need more time, please contact us flespi team.

EvgenyShatilo

Changing the indexing of the accumulator# parameter.
Added a new temporary parameter "accumulator.shift" which has a state of false. On March 15, 2023, as mentioned earlier in the previous post by EvgenyShatilo, accumulator parameter indexing will change. The state of the "accumulator.shift" parameter will be changed to true. The parameter can be used in a plugin that will prevent index shift.

Plugin code is attached:

{
  "configuration": {
    "code": "if optional .accumulator.shift == true:\n\trepeat[64, counter=$i, from=0]:\n\t\tformat[\"accumulator.%d\", $i] ==> $old_name\n\t\tformat[\"accumulator.%d\", $i + 1] ==> $new_name\n\t\tmove optional {$old_name} ==> #param[$new_name]"
  },
  "item_type": 11,
  "name": "accumulator shift",
  "type_id": 1
}

The "accumulator.shift" parameter will be removed on 03/22/2023, i.e. one week after the index change. If you need more time, please let the flespi team know.

EvgenyShatilo

Changing the indexing of the accumulator# parameter.
changing the indexing of accumulator parameters were applied in accordance with the previously agreed conditions:
EvgenyShatilo

EvgenyShatilo

Changing the indexing of the accumulator# parameter.
Temporary accumulator.shift parameter has been removed.

EvgenyShatilo

Changing the indexing of the accumulator# parameter. (Preparing)
The change will affect formats 1 - Enhanced Accumulator Reporting (32-bit) and 2 - Enhanced Accumulator Reporting (256-bit) data structures. At the moment, the parameter index starts from 1, will be changed to 0. The changes will be applied in 1 week (14.06.2023) from today (07.06.2023). If you need more time, please contact us flespi team.

Important note!
In order for the change to happen without harm to users we added new temporary parameter "accumulator.shift" which has a state of false. The parameter can be used in the plugin that is attached below.
The plugin is designed in such a way that it will start working when the parameter indexing changes are put into operation and accumulator.shift is set to true. The essence of the plugin's work is that the indexing of parameters does not change, that is, even when the reference point is 0, the plugin will automatically change the parameter index to +1, so by using this plugin, the user will not notice the changes.
The temporary parameter "accumulator.shift" will be removed one more week after the changes are applied (21.06.2023), if you need more time, please let us know.

Code of the plugin

{
  "configuration": {
    "code": "if optional .accumulator.shift == true:\n\trepeat[64, counter=$i, from=0]:\n\t\tformat[\"accumulator.%d\", $i] ==> $old_name\n\t\tformat[\"accumulator.%d\", $i + 1] ==> $new_name\n\t\tmove optional {$old_name} ==> #param[$new_name]"
  },
  "item_type": 11,
  "name": "accumulator shift",
  "type_id": 1
}

EvgenyShatilo

Changing the indexing of the accumulator# parameter. (installed)

Changes with battery indexing have been applied. Indexing of parameters now starts from 0 for accumulator types 1,2.
Parameter accumulator.shift now has state is true, will be removed a week later (21.06.2023), if you need more time, please let us know.

Code of the plugin. Remind

{
  "configuration": {
    "code": "if optional .accumulator.shift == true:\n\trepeat[256, counter=$i, from=0]:\n\t\tformat[\"accumulator.%d\", $i] ==> $old_name\n\t\tformat[\"accumulator.%d\", $i + 1] ==> $new_name\n\t\tmove optional {$old_name} ==> #param[$new_name]"
  },
  "item_type": 11,
  "name": "accumulator shift",
  "type_id": 1
}

EvgenyShatilo

Changing the indexing of the accumulator# parameter. (final)
All changes have been applied. The temporary accumulator.shift parameter has been removed.

EvgenyShatilo

Hot fix! Changing parameter names.
We fixed a situation where the values of the "message type" and "event code" parameters were mixed up. A new parameter has been added which is a message type value - message.type.enum. The parameter that is intended for the event code event.enum has remained unchanged and now it contains only event codes.

baja

packet sequence number is now stored in event.seqnum
sequence number divided by 1000000 added to timestamp to form timestamp.key parameter, which is treated as unique key in flespi timeseries database, so the messages with the same timestamp won't be merged

baja

parameters user.message.route and user.message.id added to the following message types:

namo

Calamp protocol is updated: fixed parsing of Fix Status byte.
Now bits are parsed into the following flespi parameters:

Bit 0 – Predicted - position.predicted.status, boolean
Bit 1 – Differentially Corrected - position.corrected.status, boolean
Bit 2 – Last Known - position.last.known.status, boolean
Bit 3 – Invalid Fix - see note below
Bit 4 – 2D Fix - position.2dfix.status, boolean
Bit 5 – Historic - message.buffered.status, boolean
Bit 6 – Invalid Time - see note below

Note: if either Bit 3 or Bit 6 is 1, then position.valid=false parameter is registered, otherwise - position.valid=true

And also parameter gnss.status is renamed into gnss.antenna.status status, and it's boolean logic is reverted so that:
gnss.antenna.status=true - means that GNSS antenna operates correctly
gnss.antenna.status=false - there is an error associated with GNSS antenna

Old parameter gnss.status will be registered for two more weeks (until 16-May-2024) along with a new parameter gnss.antenna.status, so that you have enough time to adjust your flespi-based applications.

baja

Bugfix in message type 6:
The packet now is considered as command response, thus it finalizes the previously sent command. Also the message with the only parameter message.type.enum=6 is no longer stored for this packet.

EvgenyShatilo

Changed parsing of the Mini Event Report message (Type 10) data structure:

Inverted logic has been applied to the position.valid parameter, now 0-true, 1-false, previously it was the other way around, which always applied position.valid=false for a correctly working device with proper signal reception.