Note: If a System parameter tab is not shown in the device, it will be set to defaults. This is the same as showing the tab and not changing any values.
The Bolt’s tracking centres on the concept of a trip. When not in a trip and otherwise idle it sleep and generate heartbeats. These are regular health checks that log a telemetry record and do an upload. The default period is 1 hour.
PDOP, Position & Speed Accuracy: These settings allow you to configure the minimum accuracy accepted for a fix. The PDOP is a measure of how imprecise a GPS fix is. This is due to the satellites that are used being too close together to triangulate effectively. Please note that values lower than 2.0 for PDOP will be difficult to achieve in practice. Default Position Accuracy is 50 metres.
Static Hold: If a device is measured to be going less than this speed, it will set it to stationary and it's position fixed.
GPS Model: This selects a statistical module used by the GPS hardware when filtering out noise during GPS fixes. Generally choose Automotive
Discard First N Fixes: This option discards a configurable number of points from the GPS if the PDOP is above 2.3. This gives the GPS some time to improve its accuracy, and lowers the chance of outlying GPS fixes slipping through the filters.
The Bolt uses Movement based trips to log movement also known as emulated ignition.
Movement Threshold: If the device detects GPS movement beyond 150m (default) it will begin tracking a trip.
Speed Threshold(km/h): The device will start a trip if this speed is exceeded.
Movement Count: The GPS counts in seconds after exceeding a threshold before declaring a trip start and calculating the distance travelled
Assumed Start Point Range (m): If a trip is started within this distance, make the new trip start equal to the previous trip end point.
Distance (m): If the distance between the last logged point and the current position exceeds this value, then log a new point with log reason “distance”.
Heading change logs are split into short and long heading changes to minimise points in large heading changes in a small distance and are logged use the log reason “heading change”.
If the distance since the last logged point is greater than Heading Change Distance (m) log a point if the heading changes by more than Heading Change Short (deg).
If the distance since the last logged point is less than Heading Change Distance (m) log a point if the heading changes by more than Heading Change Short (deg).
This setup allows accurate reproduction of corners and bends without excessive data use.
Speed Change (km/h): If the speed of the device changes by this value since the last logged point, log a new point with log reason “speed change”.
Stationary: Set to Yes to log a point when the speed reaches 0 km/h. This results in a “stationary” log reason
The threshold for harsh driving vary between different vehicle types. A large truck and a motorcycle will require very different thresholds. The thresholds should be configured in system parameters on the OEM Server.
As a guideline:
- Defaults: acceleration and braking 4.4m/s^2. Cornering 5.5m/s^2. These are set high to log a minimum number of events on most vehicles.
- Testing: artificially low to generate events. For example; Acceleration and braking 3.0m/s^2. Cornering 3.5m/s^2
In practice: choose levels between the defaults and the testing levels.
Digital Input: Select a digital input to log records to
Idle Time Threshold (s): after this time has elapsed of the device being lower than the idle speed threshold (km/h) set Digital Input N to 'On'
Stay Connected to GSM: This will keep the modem powered permanently, use only if you are sure that you know what you're doing.
Upload Attempt Timeout(min): Change this to lengthen or shorten the time to gain a connection, please note longer timeout periods impact the life span of your batteries.
Record the external power voltages to a digital input
Run Detect offers a different form of logging and trip detection rather than emulated ignition. you can read more in the Using Run Detect on the Bolt article here
The GPS module reports whether jamming has been detected or suspected by the receiver. The jamming status sets a configurable digital input. The detector monitors background noise and looks for significant changes, which may indicate jamming. These settings can be configured to record on a Digital I/O by using the follow parameters tab.
Enable or Disable ability to send APN SMS commands to the device.
Accident Logging allows 3 levels of logging.
- Off (default): results in no detection and automatic upload of reconstruction data. Reconstruction data can still be requested by an async message.
- Accident Log Reason: logs only the accident record and no reconstruction data.
- Accident Log Reason & Reconstruction Data: logs the accident record and reconstruction data.
Accident Delta-V Threshold is the magnitude of the change in 2D velocity over 120ms that will trigger an accident. The units are km/h. The default is 7km/h. This corresponds to 1.6G over the 120ms period.
Disable Orientation allows the advanced accelerometer features (roll detection, driver profiling, and drop detection) to be disabled.
Disable Vertical Accident Filtering allows the drop notification to be disabled.
Wakeup Threshold and Wakeup Count relate to the accelerometer's sensitivity to movement that will wake the device up or keep it awake. Generally, the defaults of 1 and 0 respectively should be used.
This enables the recording of log reasons into the Device Telemetry regarding distances, odometer and run hour measurements.
The Inactivity Timer is a new function on Firmware 1.13v or newer and functions as a timer where the 'Inactive' Digital input is set when an asset has not registered a trip for the set time.
Please note this is different to a device not connecting report, where a device has not been able to connect & Commit to the server in x amount of time.