How to 'force' a connection

Often when provisioning devices, or when developing a 3rd party platform, it is useful to be able to get the device to upload which allows:

  • Any pending firmware or parameter updates to be downloaded and applied (note they are not applied if the device is currently in trip for powered devices)
  • Some device data to be sent to the end platform - to test/assist with integration.

Note that there is no way to force a connection for a device in the field on command (particularly battery powered devices). i.e. you can't 'ping' a device. In order to receive any command that you would send a device, it would need to be connected to the network (i.e. with it's cellular modem turned on). For our battery powered devices, this would drain huge amounts of power and lead to extremely short battery life. For powered devices, you can set them to remain connected to the network at all times (i.e. leave modem on) if desired under the Upload Settings in system parameters. However it should be noted that sometimes the network may close down the connection once it detects no data is being sent over it. 

So in order to 'force' an upload for testing and provisioning, we simply take advantage of knowledge of the device's parameters, and what would cause it to attempt an upload. 


Powered/Hard Wired Devices

Dart2, G62, G120, Bolt. 

By default, all these devices are configured to upload when a change in external power is detected. So simply connect to a power supply and toggle on/off to cause an upload and GPS fix attempt. Another method would be to connect the ignition wire to a power source - i.e. make the ignition go active. However while the ignition remains active and the device is in trip - parameter and firmware updates will not be applied. So cycling external power is preferable. 


Battery Powered Devices

For battery powered, there are a variety of methods. A key challenge is that many devices have no inputs to easily toggle. Starting a trip can be difficult also as by default the Oyster2 and Remora2 require the device to move 250m from its rest position to begin a trip.

  • The Remora2 is supplied with a magnet - for it's Tamper Detect feature. Removing/reinserting the magnet from the recess on the underside of the housing will trigger an upload by default.
  • The Oyster2, Remora2 and Falcon can be set to start a trip based on accelerometer movement, meaning that you can simply shake the device at your desk to cause a trip to begin. Learn about this and how to enable here - Jostle Mode Tracking. The Yabby operates this way by default.
  • Removing the batteries, waiting around 20-30 seconds for all capacitors to discarge, then reinserting is an option. It is worth noting however then the device will lose its GPS fix stored in memory and will need to acquire a new one. Additionally the remaining battery percentage will reset to 100% for devices that report this value. 

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.