Parameter Tabs (in OEM) of the G62 are discussed below. Many of the G62 parameters are based upon the Dart and settings are similar:
The following are default settings under the Movement Trips parameter tab for the G62
Digital Input determines which digital input to set when in a movement trip. A movement trip is started/ended based upon the other settings in the tab.
Select Emulated Ignition to use Emulated Ignition, which sets input 0 (Ignition).
Select None if you want to track 'Transport Trips' - A movement trip will start but the Ignition bit won't be set - and TG can recognise this to distinguish when an asset is being towed
Select Input 3-9 to set these inputs.
Movement Threshold (m) is the distance used to start and stop movement based trips.
Movement Count is how many GPS fixes beyond the threshold are required before a trip is started. This helps to disregard false GPS data. Increase this if false trip starts are occurring.
Assumed Start Point Range:
Assumed Start Point Range (m): if a movement trip start is detected, log an assumed start point if the device is still within this radius of the start point. If within the assumed start point range, the trip start will be logged at the rest position, and a distance travelled point will be logged at the point when the device crossed the threshold. If not within this assumed start point range, the trip start is logged at the point where the device decided it was in trip.
Trip End Time:
Trip End Time (s) is the amount of time, in seconds, that the device should be stationary or without a GPS fix before ending a movement based trip.
Trim Movement Trip:
Trim Movement Trip can be set to Yes if the device should log a trimming record. The trimming record indicates the trip type and the stationary period. If understood by the software front-end platform, it can be used to trim the stationary time off the end of a movement trip. The default is No, or do not log a trimming record.
What is a heartbeat?
Digital Matter devices use the concept of a heartbeat. When the G62 is not tracking a trip and otherwise idle, it will sleep. It will schedule a regular wake-up on the heartbeat period.
On the heartbeat period it will:
- Log a heartbeat record, which will include GPS, analogue and digital data. This telemetry forms a health check. The GPS data is likely to be the last logged point, unless it has moved since it was logged.
- The Dart will then do an upload. It will connect to the server and attempt to upload the heartbeat and any other records that have been logged. The server will notify the Dart if it needs to update any of its slots. The Dart will check the age of its offline GPS Assist data. If older than 5 days, it will connect to the u-Blox servers and download an update.
- The Dart will turn on the GPS to refresh the module’s ephemeris data. This improves the quality of subsequent fixes.
The heartbeat period can be adjusted:
The Heartbeat Period is the maximum time between upload attempts in minutes.
Once a trip has started, the logging behaviour is determined by the settings in this section. The goal of this tracking algorithm is to provide an accurate and customisable representation of the trip with the minimum number of records. Defaults are shown.
Set any of the following parameters to zero to disable their function.
If more than Time (s) seconds have passed since the last data point was logged, then log a new point with the log reason “elapsed time”.
If the distance between the last logged point and the current position exceeds Distance (m), then log a new point with log reason “distance”.
Heading Change Short:
Heading change logs are split into short and long heading changes to minimise points in large heading changes in a small distance. It operates as follows:
- If the distance since the last logged point is less than Heading Change Distance (m) and if the heading changes by more than Heading Change Short (deg), log a point.
- If the distance since the last logged point is more than the Heading Change Distance (m) and if the heading changes by more than Heading Change Long (deg), log a point
Heading change records use the log reason “heading change”. The heading change setup allows accurate reproduction of corners and bends without excessive data use.
If the speed of the device changes by Speed Change (km/h) since the last logged point, log a new point with log reason “speed change”.
Set Stationary to Yes to log a point when the speed reaches 0 km/h. This results in a “stationary” log reason.
A global speed limit can be set on the device to activate a buzzer. Depending on the configuration and device build, it could be an internal buzzer and/or external buzzer on a switched ground output. There is no internal buzzer on the G62, so this is only useful if you are going to connect a buzzer to the switched ground output, and set the output up as a buzzer in the system parameters.
Defaults are shown:
Threshold (km/h) determines the speed at which the buzzer is turned on
Delta (km/h) is the speed below the Threshold (km/h) at which the buzzer will be turned off.
Threshold = 100km/h, Delta = 3.0km/h
The buzzer will be turned on when the vehicle reaches 100km/h, and won't go off until the speed drops to 97km/h.
The G62 has an internal accelerometer which can be used to detect harsh driving events. The threshold at which these are logged can be adjusted via the Harsh Driving parameters.
Defaults are shown:
Acceleration/Braking/Cornering Log Threshold:
The threshold for which a harsh events are logged. See this article for a discussion of how to set your thresholds
How many times the buzzer will beep (if one is wired up to the digital output) on logging a harsh driving event. This is useful for providing drivers with real-time feedback about their driving behaviour.
The following article applies to the G62:
The following settings are available - it is best to leave them as the defaults unless you know what you are doing.
The following parameters are available, defaults are shown - these parameters are the same as the G100 and Dart. Search for Driver ID for further articles.
Buzz on no Driver ID
If a trip starts and a Driver ID tag has not been scanned, sound the buzzers. On the G62 you will need to connect a buzzer to the Digital Output - no others are available.
If Yes, Immobilise via the digital output until a Driver ID tag is scanned. This means any Digital Outputs set to Immobilise will be set on '1' until a tag is scanned.
Expire on Trip End
Immediately expire the Driver ID when a trip ends. Otherwise, use the expiry time. If you are set up to immobilise, the vehicle will be re-immobilised as soon as the trip ends.
Test Against List
If Yes, ensure any scanned Driver ID tags are present in the Driver List. If the scanned tag is not in the list, it is as if one has not been scanned - buzzing will continue, and the vehicle will stay immobilised.
If set to No, allow any driver - the tag will be recorded.
How long, in seconds, a Driver ID remains cached after scanning. If a trip starts while cached, it is kept until the end of the trip, or until another tag is scanned. Expire on Trip end must be no to use the Expiry Time
Example: If this is in use with immobilisation, and expiry time is 120s - if a trip starts, and the driver scans their driver ID, the vehicle will be allowed to start. The will be able to ignition off and then restart the vehicle within 120s without the vehicle immobilising again.
See this article for a description of the parameters in this section:
The Ignition line can be thought of as another digital input - however the bias resistor is not configurable for pull-up/pull-down, it is permanently pulled down in hardware. Settings are the same as for Digital Inputs - however the Bias Resistor parameter is not available due to this permanent pull-down.
Defaults under the ignition tab are:
Digital Input - Input 0
Active Level - High
Log and Upload on Active and Inactive
Others are the same as other the Digital Input defaults.
In general these should stay as defaults - you may need to increase the debounce time if you are getting multiple trip start/stops when the asset is started.
The following settings are available - defaults are shown.
None, Digital Input, or Pulse Counter.
Set these to disable the input, use it as a Digital Input, or use as a Pulse Counter.
Which virtual input number it is mapped to. Generally leave as default
See note about bias resistors here: Bias Resistors
Which level is considered 'on/1' for the input. See here: Active Level
Log/Upload On Active/Inactive
Whether the device will log a record on the input coming off or on. If this is set, but upload is not - it will be uploaded with the next upload - e.g in trip log, heartbeat etc.
The device can be configured to sound a buzzer when the Digital Input is active or inactive, in the case of the G62 if the Digital Output is set to Buzz it will be set high/low to drive a buzzer that may be connected. This can be useful to provide feedback to the user that an input has been activated (e.g. Panic Button) or left on.
Settings are described in the image:
Buzz on Active Period = 2, Buzz on Active Count = 5
The buzzer output will be: ON, OFF, ON, OFF, ON, OFF, ON, OFF, ON, OFF (20ms each)
When set to Yes - if an upload due to an input change fails, it will be retried until it is successful.
When set to No - if an upload fails, the input change log will be sent on the next event (heartbeat, trip start etc)