Recovery Mode is a one-touch feature designed to set the device into "live tracking" where it reports more regularly. This is useful in trying to recover a stolen asset.
Recovery mode has a severe impact on battery life. Remember to bring the device out of recovery mode as soon as possible.
Three important things to note:
- Your data usage will increase dramatically until Recovery Mode is deactivated.
- Battery life on the device will reduce quickly until the batteries are flat (up to 7 days depending where they are in the usage cycle), or until the Recovery Mode is deactivated.
- Recovery Mode can be deactivated manually or set to timeout. (Make sure your device firmware supports the timeout)
How to enter recovery mode:
There are 4 different ways. Select the most convenient or most applicable:
Select Assets>> Manage Assets, select your asset, then go to the cog on the far right and select Enter Recovery Mode.
You will be asked to verify to be certain.
Remember; you can set an expiry date for Recovery Mode. The default timeout will be 6 hours from when Recovery Mode is activated. The timeout can be set from 30 minutes to 24 hours for the device. The timeout is an absolute expiry time, rather than a time-span from when it was received by the device.
Note that the device needs a recent version of firmware to use this timeout feature. Older versions may stay in recovery mode, until it is deactivated or the batteries go flat.
In the Asset column you will now see it is active and offers Leave Recovery Mode if you would like to deactivate.
Recovery Mode Behaviour and Parameters
The behaviour in recovery mode is configurable to suit your needs.
Recovery mode uses Jostle Tracking to start and stop trips. That means it uses accelerometer movement to decide when in trip.
The device will attempt to stay connected to the server when in trip.
The following settings are configurable. The default settings are recommended:
- GPS Fix Timeout: default of 10 minutes
- Heartbeat Period: default of 30 minutes. This applies out of trip.
- In Trip Logging Period: default of 30 seconds.
- Trip End Time: default of 10 minutes
These settings can be changed in the system parameters on the OEM server. The default settings are shown below:
When will the device actually enter recovery mode, and parameter selection
Once recovery mode is set - an asynchronous message is queued on the server - which is delivered to the device when it next connects in. This cannot be forced from the server side, as our devices sleep in a low power state, with the modem off when they can to conserve power.
For example, consider a battery powered device uploading hourly.
- 10:00am - device uploads
- 10:05am - recovery mode is enabled via TG
- 11:00am - next scheduled update occurs, only now is recovery mode active.
So for this reason, if recovery mode is to be used in the event of theft, parameters must be carefully selected such that there is an acceptable delay in between activating recovery mode via the user interface, and this message being received by the device.
Typically, this boils down to setting a suitable In Trip Upload period on your device. For example on the Oyster2, the default is an upload every 30 min in trip. Then the events which occur are:
- 10:00am - Device starts movement and begins a trip, causing an upload. A movement alert is configured in the end platform so is received by the user at this time
- 10:10am - User has checked their phone and activates recovery mode
- 10:30am - Device uploads due to 30 min In Trip Upload Period - and picks up the command and enters recovery mode.
If there is a requirement to enter recovery mode faster - then the in trip upload period should be lowered. This will come at the expense of battery life if many other trips are regularly made which don't require recovery mode to be activated.