Support Home Portal Log in
Open navigation

Bolt2 - Overview of Operation

Modes of Operation

The Bolt2 revolves around the concept of 'a Trip' for tracking. There are two ways in which the device can detect the beginning and end of trips

  1. GPS Movement Based (Emulated Ignition)
  2. Run Detect (changes in external voltage)


The Bolt2 is configured for Movement Trips by default.

No Direct Ignition Feed

The Bolt2 only draws power from the OBDII port - it does ready any engine codes nor pick up an ignition signal. It only detects trips via the methods above - GPS Movement or external voltage changes

GPS Movement Trips (Emulated Ignition):

This mode works in a similar way to "Standard GPS Tracking" on our battery powered devices.

  • The device waits in a low power sleep state for accelerometer activity.
  • Once woken, it checks the GPS for movement over a period of a few seconds. 
  • If the GPS shows movement over the start threshold, a trip is started, and the the ignition bit (DI 0) is set to Active.
  • If this is not the case, the device then resumes sleeping, with both the GPS and mobile data off.
  • Once the asset has been stationary for some time, or the GPS signal has been lost for some time, the trip is ended, and a final upload is performed.


Movement trip start behaviour is controlled by these parameters:

To begin a trip, the movement and speed thresholds are ANDed together. i.e. we must be over 150m from the start point AND travelling over 15km/h to begin a trip with the above parameters. So very slow moving assets ideally should just have physical ignition hard wired, or be sure to drop the speed threshold. 

>>Once woken, it checks the GPS for movement over a period of a few seconds.
In detail, this means that after some accelerometer activity is detected, the device keeps checking for movement until there has been no accelerometer activity for 36 seconds (hard coded), and no GPS movement for the Trip End Time (configurable).

The "Movement Count" means that we require this many fixes (the device gets a fix second by second) that all agree that the device is over the trip start movement and speed thresholds to begin a trip. Higher values means the device is more 'sure' that it is on the move, and there is less chance that a single erroneous fix will result in a false trip start.

Run Detect

Run Detect will put the device into trip based on changes in the external voltage. The assumption is that when the engine is turned on, the vehicle battery voltage will increase as the alternator is turned on to charge the battery. In many cases this will work well if a wired ignition is not available. However this assumption does not always hold true. The resting/running battery voltage of a vehicle can change over time, so the thresholds below may need to be adjusted. Modern vehicles are also smart enough to turn off the alternator when the battery is fully charged, and some even will turn off the engine when stopped at traffic lights. For this reason run detect is not foolproof.

  • High Voltage:  Set this number to be below the average voltage output when the engine is ON so the Run Detect is activated when the engine voltage crosses the value
  • Low Voltage:   Set this number to be lower than the High Voltage value but higher than the average value when the engine is OFF so Run detect is deactivated when the voltage crosses the value.
  • Digital Input:   To have Run Detect activate trip status, set the Digital Input to Ignition (0).
  • Start Time (s):  Amount of time for voltage to register over High Voltage, i.e, engine to be running, before trip starts
  • End Time (s):    Amount of time after engine stops, i.e, voltage to cross Low Voltage for trip to end.

Did you find it helpful? Yes No

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