Skip to main content

Firmware Release Notes

v03.08.26 (Current Public Release)​

Released 28 March 2024

  • Self Test - Corrected an issue where incorrect GPRS signal value caused a test failure.

v03.08.25

Internal (branched) release. Public-facing FW versions will skip this number and continue from v03.08.26

  • GPRS Module serial bridge mode - Updates to the special testing feature, allowing AT commands to be issued directly to the UBlox GSM module for testing purposes.

v03.08.24

  • GPRS Network Restoration - GPS modes with frequent GNSS access (e.g. every 10 seconds) previously delayed network reconnection. This has been resolved to ensure reliable network restoration.

v03.08.23

Internal (branched) release. Public-facing FW versions will skip this number and continue from v03.08.24

  • GPRS Module Factory Reset - A special testing feature facilitates the factory reset of the GPRS module. Intended for testing purposes only.

** v03.08.22**

Internal (branched) release. Public-facing FW versions will skip this number and continue from v03.08.24

  • GPRS Module serial bridge mode - A special testing feature allows AT commands to be issued directly to the UBlox SARA module for testing purposes.

v03.08.21

  • GNSS Failure - A bug where the GNSS data stream failed in Iridium Only mode, due to the GPS being in a 'hot' state and subsequently entering hibernation, has been fixed.
  • GPRS Socket Closure - The socket closure time after packet transmission has been reduced to approximately 1-2 seconds (previously 30 seconds), enhancing the alignment of packet transmission with packet generation at high frequencies and thereby reducing perceived latency at the server end.
  • Tracking Suspend - Tracking suspensions will now be terminated if the tracker is deactivated, addressing the previous issue where they persisted even after reactivation.

v03.08.20

Internal (branched) release. Public-facing FW versions will skip this number and continue from v03.08.21

  • GNSS Watchdog - The system now detects prolonged, unintended absences of GNSS data and attempts recovery by disabling and then re-enabling the GNSS function within the GPRS module.

v03.08.19

  • GPRS Command Response Timeout - The system now power cycles the module if a command response is not received, and includes a test command in the power cycle procedure to differentiate between a lost response and an unresponsive module.

v03.08.18

  • GPRS and GNSS Failure - A bug causing data overrun and preventing GPRS and GNSS services from resuming at fast transmit frequencies has been corrected.
  • Manual Registration Failure - The issue where manual scanning mode failed to start upon tracker reset has been fixed; toggling the GPRS configuration can resolve this.
  • GPRS Registration Improvements - GPRS Registration modes have been redefined to include a "Normal Mode" with interleaved auto and manual registration attempts, and a "Scanning Mode" with continuous manual registration. The new RAT priority is set to improve registration efficiency, with a focus on LTE and GPRS.

v03.08.17

  • Option For GSM Manual Registration - The tracker now offers a manual registration option, allowing for greater flexibility in network selection compared to the default auto registration. The APN setting is expanded to include a 'manual' field for specifying this option and additional criteria for network selection are defined, including a preference for 4G networks.

v03.08.16​

Released 11 October 2023

  • Supply Voltage Report - Now supported in Burst Mode transmissions. Supply Voltage can only be reported by specific RockFLEET board types. Not all RockFLEET devices are capable of voltage monitoring.

v03.08.15

Internal (branched) release. Public-facing FW versions will skip this number and continue from v03.08.16

v03.08.14

  • GPRS Connection Failure - Improved socket management will improve connectivity in environments with poor signal. A watchdog reset has been implemented to prevent trackers from being stuck on incomplete network connections.
  • Polyfence - Improved performance of polyfence behaviour for trackers registering an elevation value below sea level.

v03.08.13

  • Supply Voltage Reporting - Supply Voltage can now be optionally reported in Burst Mode. Supply Voltage can only be reported by specific RockFLEET board types. Not all RockFLEET devices are capable of voltage monitoring.
  • Burst Mode - Compact, no fix burst packet now assigned MO_5 type. (Previously erroneously assigned MO_50).
  • Burst Mode - Bug fix preventing burst mode from creating an additional delta at midnight UTC.

v03.08.12​

Released 12 June 2023

  • GNSS/Cellular Services - Bug fix resulting in improved performance of GNSS/Cellular services management.

v03.08.11

This release only affects a specific board type, not all RockFLEET devices are capable of voltage monitoring

  • Supply Voltage Reporting - The supply voltage can now be optionally reported.

v03.08.10​

  • GSM Transmission Failures - Improved GPRS module handling in the case of relatively rare issues that lead to or arise after a module command failure and the ensuing timeout period and module restart that the failure causes.

v03.08.09

  • IMEI for GSM Only Boards - For boards configured without Iridium modems, the IMEI is now retrieved from the cellular module IMEI whenever an IMEI is required.

v03.08.08

  • Magnet Reset - Improved reliability of magnet reset alert generation.

  • SBD Signal Loss Monitoring - The robustness of signal loss event has been improved:
    -- The signal sampling window has been increased to 10 minutes (from 5 minutes) with 30-second sample period, ie 20 samples.
    -- A successful transmission at any time will restart the sampling window.
    -- If the current/last reported signal status is 'present' then 20 consecutive negative samples will trigger a signal 'lost' event.
    -- If the current/last reported signal status is 'lost' then 5 positive samples anywhere within the sampling window will trigger a signal 'present' event and restart the sampling window.
    The SBD signal loss feature is suppressed if the tracker is configured to have no iridium functionality (GSM only).

  • Self-Test - For a tracker configured with no Iridium functionality, all Iridium related subtests are now suppressed and do not influence the overall self-test result.

v03.08.07

  • Alerts for Tracker Reset Type - An MO_18 generic alert packet (MO_38 for no fix) will now be generated for certain types of tracker reset:-
    -- Magnet (Tigershark) or hardware (Griffin) = Event ID 20
    -- Watchdog = Event ID 21
    Alerts are not generated for power cycle resets or software restarts.

  • Power Mode & GPRS Strategy Options - Using the OTA packet protocol, the power mode and GPRS Strategy options must now be accessed via configuration record 2 (new) instead of record 6 (previous).

v03.08.06​

  • GSM: Server/Tracker Connection Monitoring - Improved strategy for monitoring a server-terminated connection, reducing the risk of failed transmissions.
  • GSM: Combined GPS/GPRS Module - Trackers do not require a GSM SIM card to function in Iridium-only mode

v03.08.05

  • GSM: Network Loss Detection - Further improvements to network status monitoring

v03.08.04

  • GSM: Network Loss Detection - Improved monitoring of network loss to reduce possible failures during transmission
  • GSM: Failover to Iridium Threshold - Improved failover strategy resulting in greater success in transmission over cellular. This change also introduces two GPRS Preferred strategies:
    • Preferred Strategy 1 (TX Speed Bias) - Favours on-time delivery of packets at the expense of cellular success.
    • Preferred Strategy 2 (Cost Bias) - Favours cellular success at the expense of the possible later delivery of packets.

v03.08.03

  • Large Log File Upload - Improved logfile uploader. Larger logfiles are now split into multiple smaller files and uploaded individually.
  • GSM Server Backup Address - Secondary and tertiary server addresses can be updated via the RockCONNECT app

v03.08.02

  • Network Registration - Mobile settings can now be applied to match the profile of a preferred operator/geographical region (MNO). The prefered order of network selection can also be defined, e.g. LTE Cat M1, NB-IoT, GPRS etc.
  • Bluetooth Performance - Improved Bluetooth advertising following a disconnection
  • Burst Position Accuracy - Improved performance of Burst Mode resulting in greater accuracy of burst fix positions

v03.08.01

  • Self-Test - Updated self-test routine for 4G/LTE boards

v03.08.00​

📘 Version number change with cumulative release - v03.08.00

Release v03.08.00 combines and unifies updates to 4G/LTE and non 4G/LTE RockFLEET/RockAIR platforms through versions v03.05.00-v03.07.02. Both hardware platforms continue in parallel from v03.08.##

  • 4G/LTE Boards – Firmware Download OTA - Firmware download OTA capability added to 4G/LTE boards. This is equivalent to the v03.07.## release for the current 3G boards.

v03.07.02

  • Firmware Download OTA - Corrected file paths for OTA firmware download.

V03.07.01

  • Firmware Download OTA - Removed test file paths for OTA firmware download.

v03.07.00

  • **Firmware Download OTA ** - Files can now be downloaded from the releases manager to a GPRS-enabled tracker OTA (via the mobile network). Typically, these files would be installable firmware but can be any file compatible with the SD card flash filing system. Files that the tracker recognises will be installed/processed.
    Note: The OTA file download endpoints are set to a test URL – internal testing only.

v03.06.04

  • 4G/LTE Transmit Length Failure - Corrected issue which caused longer messages (over 127 bytes) to fail.

v03.06.03

  • 4G/LTE Error Handling - Corrected handling of certain module command errors. Unimportant errors are now selectively ignored leaving those that cannot to be actioned.

v03.06.02

  • 4G/LTE Response Failure - Corrected responses to status notifications prevent module restarts.
  • LTE Module Power Status - Module no longer remains powered following self-test/deactivation

V03.06.01

  • 4G/LTE Compatibility
    GNSS module is now restarted following a GPRS failure and restart.
    Improved filtering of USB external power supply.

V03.06.00

  • 4G/LTE Boards - Support added for 4G/LTE compatible boards (RockFLEET v2.E, RockAIR v1.F) in addition to existing GPRS boards.

V03.05.00

  • Battery Management IC - An option is now provided for future PCBs to function without the battery management IC (STC3115) present. If STC3115 is not detected battery management is effected via a battery circuit already present on the PCB. A PCB with the battery fuel gauge device missing will however fail self-test.

v03.04.30​

Lost Watch Me Requests
Corrected: A 'Watch Me' stop request was not generated during deactivation following the cancellation of the 'Watch Me' deactivation warning.

Note: Deactivation is paused while 'Watch Me' mode is active.

v03.04.29​

Auto Select Power Mode Indication (RockFLEET ONLY)
Updated LED indications representing different power mode configurations to include Auto Power Mode Selection.

v03.04.28​

Auto Power Mode Selection
An additional 'Auto Select' power mode configuration is now available so that the power mode option list is now as follows:-

  • Unlimited
  • Limited
  • Unlimited+Activate
  • AutoSelect (New)

When the new 'Auto Select' option is chosen then the tracker will select 'Unlimited' power mode behaviour if external power is present or 'Limited' power mode behaviour if it is not.

For information, Unlimited/Limited selection directly controls various system features, including the following:-

  • GPS hot/cold
  • Iridium hot/cold (for ring detect/not detect)
  • Serial API enabled/Disabled
  • Signal Loss enabled/disabled
  • Transmission retry continuous/progressive delay algorithm

Firmware Resetting
Corrected: Firmware resets were found to be happening due to system timeout. These resets caused the usual power-up/activation reports to be generated but generally caused no fatal consequences.

v03.04.27​

Corrected: Firmware installation issue introduced in v03.04.25

v03.04.26​

Auto SOG Deactivation
Corrected: If power was removed then deactivation always occurred after a 1-minute timeout.
The timeout is now only initiated and maintained while there is no GPS fix available. If an occasional fix is obtained during the timeout period then if it has ‘slow’ speed the timeout will continue unaffected otherwise (it has ‘fast’ speed) the timeout will be reset for another full minute. Note: If GPS fixes are available continuously then deactivation can now only occur (following power removal) if the speed transitions from ‘fast’ to ‘slow’ and remains so for at least 5 seconds.

v03.04.25​

Continuous GPRS Registration Failure
Some instances of continuous registration failure have been observed where only a tracker restart (GRPS module reset) has resolved the issue. A 1-hour timeout is now introduced after which an automatic tracker restart is forced if GPRS registration failure has been continuous.

Incorrect Activated LED Status (RockAIR ONLY)
Corrected: If external power is removed just at the moment of activating the tracker via the activation button then it could happen that a 'deactivated' rather than an 'activated' LED status is presented.

Text Message Transmission Confirmation Using the App
Previously text messages were confirmed to the App as 'sent' as soon as they were placed in an internal transmission queue. If the actual transmission failed then the messages could remain unsent although the App believed otherwise. Confirmation of 'sent' to the App is now delayed until actual transmission of a message is detected so that 'sent' status on the App should more closely reflect reality.

v03.04.24​

Signal Loss Alerts
Signal loss alert transmissions now include a standard position block including GPS fix element or else a standard reduced version if no fix is available.

Signal Loss Polling
Signal loss 'Lost' and 'Present/Restored' state change now occurs when a signal strength trend is deemed to have been properly established over time. Previously, switching between states would be delayed or even prevented by occasional noisy poll results.

v03.04.23​

Signal Loss Alerts
A signal loss monitoring option is introduced that can be switched on/off via the OTA configuration command.

The feature will only be active if an unlimited power configuration mode is selected.

When enabled the feature monitors both the GPS and Iridium signals and creates and transmits generic alert packets if the signal status for either transitions from present to not present or vice versa.
(Note: alert packets are instead queued for later transmission if signal loss prevails).

A signal is deemed lost when not present continuously for 5 minutes.

Transmit Rate Context Switching
Corrected an issue where the SBD TX rate was not selected in certain scenarios.

v03.04.19​

Released 20 January 2021

Reported SOG
Standard Packets now support a SOG range of 0-1023 knots.
NOTE: Compact Packets remain limited to 0-511 knots.

Away From Home
The AFH feature no longer requires external power.
An alert transmission will now be triggered whenever the AFH fence boundary is crossed.

Battery Low Power Cut Off
With a battery only, tracker operations will now be allowed to continue until the battery power is exhausted. Application of external power will reset the tracker back to normal operations.

Serial API Message Deletion
Sent message deletion no longer requires user action. Messages are now purged immediately at the end of every transmission.
In support of this change, the response to the R7+STAT command becomes:
0 = not sent
1 = sent
2 = (this response has been removed)

Serial API Message Database Full When Transmission Failure
ERROR 2
An error code has been introduced and will be returned in response to any R7+WH… or R7+WB… message commands if the database is full.

Serial API Message Database Protocol Anomalies
ERROR 3
This error code is introduced to indicate rejection of a message command when the submitted ID is a duplicate of one already in the DB and not yet sent.

Serial API GPS Errors

  • Corrected: A negative altitude was formatted as a large positive number.
  • Corrected: Speed and HDOP values below 1.0 were formatted without a leading zero and decimal point, e.g. 0.5 would be formatted as 5.
  • Corrected: Removing the external power during GPS streaming to the serial port caused a reset of the tracker.

Serial API Changes

  • The serial API feature can be enabled but its functionality may not be active on the serial port (paused) depending on system state. Whenever functionality does become active then an unsolicited message will now be issued to the serial port as a prompt for external equipment. The message will include the current firmware version, for example:- "Version 03.04.16".
  • Serial API functionality will now be paused in limited power configuration and when deactivated (previously it was paused if battery power only was supplied).
  • GPS streaming will be turned off whenever the API is paused. If the API subsequently restarts then GPS streaming will need to be commanded to turn on again if it is required - it will not resume automatically.

v03.04.13​

Released 1 September 2020

New Behaviour

New Serial API Commands:

R7+GPS,STREAM=n
New command.
This switches GPS streaming to the external terminal on/off ( n=1 on, n=0 off ).

Whilst streaming other API commands will be serviced as normal.

R7+VERSION
New command.
This returns the firmware version.

** R7+WH | WHNC | WHP | WHNCP | WB | WBNC | WBP | WBNCP**
New command option added.
An option for a message ID to be provided from the terminal is now supported.
For example:- R7+WHP=This is a message,ID=123.
If the ID field is not provided then the tracker will assign its own ID as previously.

The advantage for the terminal in providing its own ID is that it can detect if the tracker fails to create a message since the tracker must return the assigned ID in its response. Previously the terminal could not guarantee which of the messages it had sent coincided with a particular response (especially if protocol failure had occurred).

R7+STAT
Additional response codes.
The response to this command is now extended as follows:-
0 – not sent
1 – sent
2 – doesn’t exist (presumed deleted or else it was never created)

Previously a ‘sent’ result indicated that the message had been placed in the queue for transmission. It did not necessarily mean that the message had actually left the tracker, i.e. it could be a false positive. This is now corrected so that only messages that have left the tracker will be indicated as ‘sent’ (in rare scenarios this indication could now temporarily be a false negative). Generally, this will now mean that if a message is indicated as 'sent' then it will also have been received by the server (allowing for any normal transmission delays).

If a message has left the tracker (only) then it will now be deleted after a status request for it has been executed.

v03.03.15-03.03.23 (Cumulative internal release v03.04.12)​

📘 Version Number Change

Internal release v03.04.12 combines and unifies updates to the platform through firmware versions v03.03.15-v03.03.23. ie, the only difference between v03.04.12 and v03.03.23 is the version number itself.

Change to Existing Behaviour

LED Power Optimisation: In order to eliminate unnecessary battery usage, there is no longer an LED (flick) indication when the tracker is hibernating.

LED Behaviour Change: LED now indicates tracker Power Mode configuration:-

LED CharacteristicsMeaning
Colour: REDTracker is in Power Mode: LIMITED
Colour: GREENTracker is in Power Mode: UNLIMITED
State: SOLIDTracker is connected to external power
State: FLASHINGTracker is not connected to external power
  • There is a mandatory indicate period during which the selected LED indication is maintained continuously. This period is defined as being from the request that triggers the building and transmission of a data packet through to its completion.
  • Outside the mandatory indicate period the selected LED indication will be maintained for unlimited power mode (green LED) but terminated for limited power mode (red LED).
  • There is no power mode indication after the tracker is deactivated.

Note: Internal release v03.04.12 combines and unifies updates to RockFLEET/RockAIR platform through versions v03.03.15-03.03.23. Both hardware platforms continue in parallel from v03.04.##

v03.03.23

  • Burst Context Transitions - Corrected: If the burst settings are adjusted via a context change (i.e. a sos alert) then it could happen that the fix rate remained at the old context value. This arose if the alert was triggered just as a burst TX period was completed and a new one begun.

v03.03.22

  • GPRS Improvements - Improvements to GPRS performance in marginal signal areas.

  • LED Hibernation Current - Corrected: The LED flick (every 10s) also switched on the SD card at the same time. This caused additional hibernation current that pushed daily battery consumption up to around 5% whereas otherwise it would be around 1%.

v03.03.21

  • Transmission Frequency Switching - Improvements to context switching when going between Iridium and Cellular.

v03.03.20

  • GPRS Failure Switching Time - The GPRS module is no longer power cycled following a communication error unless the error is then established to be a failure to respond to any communication whatsoever. Instead, any error (e.g. timeout) is tolerated to allow the module to retry any procedure it might have been attempting.

v03.03.18

  • GPRS Timeouts - Corrected an issue where insufficient response time was allowed for some GPRS commands resulting in unnecessary timeouts.
  • Log Upload - Corrected: Available upload slots in a day log file began at 01:00 rather than 00:00
  • Burst TX Rate Context Switching - Corrected: The burst fix rate can also change if there is an automatic context switch between Iridium and GPRS when each selects a different burst fix value.
  • Distress/Routine Burst Settings - Corrected: If both distress and regular modes used burst settings then the correct setting was not always chosen when switching between the modes.
  • CSV Headers - Corrected: Occasionally the header line for a CSV file was omitted.

v03.03.17

  • SD Card Reformatting - If a corrupted card is detected then an attempt to reformat is made following a system reset.

v03.03.16

  • Auto-deactivation when No GPS fix - 60 second timeout added to a deactivation session. A deactivation, when triggered in Unlimited+Auto power mode, will now time out after 60 seconds when a GPS fix cannot be established.
  • **Watchdog improvements **- A restart following a watchdog reset will now always allow the tracker to activate even in the absence of external power (previously a tracker would deactivate upon any restart if external power was not present).

v03.03.15

  • Software Failure Detection (Watchdog) - for defence against software failure, new watchdog improves logging and error catching. If a software hang is detected, the watchdog should perform a reset.

v03.03.14​

Released 24 October 2019

Improvements

  • Multiple Serial API Messages are now included in a single transmission. Previously only the first message would be included and each of any remainder sent with subsequent unrelated transmissions as and when these occurred.
  • Serial API: Corrected issue which caused R7+WH= command to fail (since 03.01.00)
  • Improved Logging when exiting hibernation
  • Improved Iridium Traffic logging
  • BLE advertisement packets have been extended to include 'Manufacturers' type data,ie Tracker IMEI, software version, PCB type, Battery level, etc.
  • External logging (to the serial port) is now retained through restart, previous a reset defaulted logging back to SD card.

New behaviour

  • Serial API: Added R7+WHNC, WHNCP, WB, WBNC, WBNCP, MSGMO. See Rock7 Serial API docs for more information
  • Away From Home feature added - a new feature which serves as an 'activity sense' by virtue of being either inside or outside a fence boundary.
  • Away From Home BLE and OTA configuration support added.
  • Distress Mode transmit context added
  • Complex Polyfence support added

v03.03.12​

Released 17 September 2019

**SOG Monitoring (GPS errors)
**
These features depend upon SOG monitoring in order to adjust their state to correspond to being above/below a particular speed threshold:

  • Fixed-wing Taxiing/Takeoffs/Landings
  • Airborne vertical speed alerts
  • Hover/Flight mode
  • Auto Deactivation

Invalid GPS data over prolonged periods caused speed to be interpreted as zero leading to possible erroneous changes of state. State changes now occur only when supported by prolonged valid GPS data.

**GPRS Log Upload
**
Corrected an issue where some log files uploaded to Rock 7 via GPRS were corrupted (since V3.1.0).

**Tracking Failures
**
Corrected some conditions that can occasionally lead to automatic transmissions stopping. Some example cases:

  • Deactivation/activation with, in particular, the activity+SOG feature enabled and burst mode fix rate set toward the faster end of its spectrum.
  • Location refresh requests from the Connect App every 10 seconds whilst the tracker unable to obtain a GPS position fix.

**SD card Insertion/Removal
**
Improved reliability when experiencing frequent Insertion/removal of the SD card (i.e. that caused by mechanical vibration).

**GPS failure at Deactivation
**Corrected a condition where particular configurations could cause a GPS fix to fail to complete, leading to failure of any further transmissions until the tracker is reset. The failure can happen when:-

**GPRS with limited-power mode
**Corrected an issue where if a tracker was configured for limited power, and allowed to hibernate in GPRS mode so that GPRS communication was lost, it was not re-established when the tracker awoke. If awaking for a GPRS transmission then this would fail although if the tracker remained awake then the communication would eventually be restored.

**Power Loss Deactivation with Power Loss Alert
**Corrected an issue where a simultaneous power loss deactivation and power loss alert (when configured) could cause a tracker to become unresponsive.
(Note: Only Griffin E boards are vulnerable to this issue)

**Iridium/GPRS Contention
**Corrected an issue where transmissions became inhibited until a tracker reset, experienced in the following scenario:

  • GPRS set as default transmit carrier.
  • Deactivation immediately after an activation (mail check queued).
  • Absence of Iridium network (mail check continuously retried)
  • Reactivation before deactivation is complete (contention between GPRS re initialisation and iridium transmit).

v03.01.03​

Released 8 January 2019

Improvements

  • Improved transmission queue behaviour when switching between GPRS Only and Iridium Only.
  • Corrections made to counter a possible Bluetooth Protocol failure during file uploads.
  • BLE Protocol upgrades inline with the Connect log viewer/uploader tool.
  • Corrected issue where burst mode packets could become corrupt when in compact transmission mode.
  • SD Card logging efficiency improved for better capture of logs that occur just prior to a reset.
  • Improved support for AES encryption of all outbound packets.

New behaviour

  • It is now possible to configure a tracker to transmit/receive via 'GSM only' regardless of the presence of an Iridium modem or any other preference settings.

v02.08.13​

Released 24 August 2018

Improvements

  • Corrected: The battery level (%) provided is now capped at 100%. It was possible for the hardware to provide values >100% while charging.

Change to existing behaviour

  • Geofence Alert is now a 'one-shot' event, it will alert upon exit from the fenced area and then switch off fence monitoring.

v02.08.03​

Released 13 June 2018

Improvements

  • Corrected: Position log files could not be uploaded via GPRS because the old GPX extension was still being used.

v02.08.00​

Released 16 March 2018

Change to existing behaviour

  • Position logging feature has been changed to create a CSV formatted file with positional information rather than the previous GPX (XML) formatted file.

New behaviour

  • Log files (.LOG) and position files (.CSV) can now be uploaded by GPRS in response to an OTA request.

Improvements

  • Low battery detection improved. Reduces risk of marginal power conditions resulting in a processor fault which would require a reset to correct.

v02.07.02​

Released 16 February 2018

Improvements

  • The tracking suspended alert is now transmitted whether or not the auto-tracking option is enabled.
  • A tracking resumed event now occurs whenever tracking is manually or automatically resumed, whether or not the auto-tracking option is enabled.
  • Performance improvements to GSM behaviour. Measures intended to prevent GSM module entering into, or otherwise remaining in any unknown erroneous state.

v02.07.00​

Released 16 January 2018

Improvements

  • Corrected: If multiple generic event alerts with no fix were created within a single session then only the last would be transmitted.
  • Corrected: Upon first BLE connection following a device reset, the GPRS board would not be indicated in the 'external board' status.

v02.05.13​

Released 8 November 2017

New Behaviour

  • The GPS dynamic model is now configurable to one of:
    Portable
    Automotive
    Marine
    Air
    The configuration is only available OTA at time of release.
    The default setting is 'Portable'.

v02.05.08​

Released 9 October 2017

*Improvements

  • Added robustness to SD card detection and access.

Change to existing behaviour

  • Removed: Log files no longer written to a signle circular system log file.

New Behaviour

  • Added: System logs now written to files according to date, e.g. 17100900.LOG for 9th October 2017. A maximum of 100 log files are supported before the oldest will be removed in order for a new one to be created.

v02.05.07​

Released 23 August 2017

Improvements

  • To avoid potential configuration loss at very low power settings are now stored in a second non-volatile memory backup.

v02.05.06​

Released 4 August 2017

Improvements

  • Optimised GPRS state refresh on restart and corrected a potential transmission synchronisation error.
  • Further optimised new packet type behaviour (introduced 02.05.00)
  • Deactivation packets in transmission queue limited to 15 minutes. If queue not emptied in this period then the transmission of those packets will be suspended until after a subsequent reactivation.
  • Corrected: Some MO messages were being retransmitted if an MT was received in the same session.

v02.05.00​

Released 28 July 2017

New Behaviour

  • New packet type allows bundling of multiple packets up to the maximum MO size.
  • Upon deactivation transmission of accumulated data continues until the transmission queue is clear. In all other respects, the device will be unresponsive as typified by a deactivated state.
  • Iridium Mailbox check performed on activation to achieve network registration for MT ring calls.

Improvements

  • Corrected an issue which caused routine transmissions not to start when re-activating device.

v02.03.00​

Released 1 June 2017

Improvements

  • Packet construction and packet transmission can now be concurrent activities.

Change to existing behaviour

  • Continuous Transmission changed to Every 15 seconds.

v02.00.00​

Released 11 May 2017

New behaviour

  • A single beep now accompanies system reset.
  • Three ascending or descending beeps now indicate whether the system has been activated or deactivated. (e.g. Ascending = Activated).
  • Mailbox check can now be requested via GPRS and is performed during GPRS sessions.

Change to existing behaviour

  • The presence of external power no longer defines whether power is considered Limited or Unlimited. Instead, this is defined by the power configuration option alone.
  • BLE location data is now a complete copy of the last packet transmitted.

Notes

  • RockFLEET and RockAIR are now integrated at this version onwards. RockFLEET assumes all relevant RockAIR changes accumulated since RockAIR 1.1.0

v01.09.05​

Released 24 April 2017

Improvements

  • Improved handling of ultrasonic wind instrument data.
Last updated on