They Oyster3 supports High-G and Tip Detection. While both features are set off based on accelerometer activity exceeding certain thresholds, for some applications Tip Detection cannot be used. This is because that Tip Detection works only in one particular axis. High-G Impact Detection can be used for such applications where we are interested in something falling over - which will result in a crash and some G-forces seen.
In this article, we will covers the parameter setup to monitor assets that can easily tip/fallover in 2 axis. We will consider the example of a portable toilet.
Below is how the Oyster3 operates out of the box
Default Tracking Parameters - [Oyster3]
- In Trip (on the move):
- Upload on trip start.
- GPS points every 2 minutes
- Upload every 30 minutes
- End a trip after 5 minutes of no movement (or losing GPS)
- Upload on trip end.
- Out of Trip (stationary) - heartbeat every 12 hours. This is a GPS point and uploads every 12 hours.
For a stationary asset like the portable toilet, infrequently moving it may not be necessary to track trips. Getting the location update once or twice a day should be sufficient. It will maximise battery life and minimise data usage. Periodic Tracking will let you do this.
To set the Oyster3 to periodic tracking, set the "Tracking Mode" to Periodic Update and "Heartbeat Period" to 12 or 24hr update.
High-G detection is disabled on the device by default. This can be enabled from the Accelerometer Settings parameter tab. Set the Alternate Function to High-G.
Once selected, the thresholds can be added from the High-G Detection parameter.
Though there are no special requirements as to how the device should be mounted for High-G detection, it is recommended that the device be mounted high up on the asset. This way, the device should see a clear high-G event on falling over and experience decent G force. This means we can set the threshold a bit higher and better filter out false alerts.
There is not a particular threshold that we suggest for any application. The specific force threshold will be dependant on the size of the asset and the nature of the fall. So some initial testing/trial and error may be required.
We want to set the threshold such that an event is reported when the toilet falls over, and not if it is transported between locations.
To aid in this, while testing we can leave the device in its default tracking mode (GPS Movement Trips). This can make it easier to identify the correct thresholds.
In this way, if the device goes in trip when there is GPS movement, and if you get any High-G events during the trip, then we can increase the thresholds based on this. - as we know the level of G force experienced in-trip.
Once we identify suitable threshold we can then set the device to Periodic Tracking.
Setting Up Alerts
Alerts in 3rd Party Platforms
When a High-G event is detected, the Oyster3 will log a record containing:
- Log Reason 46 - 'High-G Event'
- Record Time
- Last known GPS time and position (FID 0)
- The Peak Force (FID 24)
- The Average force (FID 24)
- The Duration of the High-G event (FID 24)
As such alerts can be set up to fire when Log Reason 46 is seen.
Alerts and Reports in Telematics Guru
See how to set up an alert here.
Ensure to give the alert a name and message in the General Tab; apply the alert to the relevant assets in the Assets Tab, and select who TG should send the alert to under Notifications.
In the Conditions tab, select 'Use Device Data Log Reason' and select High G Event from the list that's populated.
The Asset Timeline history view, will show a history of these alerts/events.
High G Event Report
In Reports > All Reports, you can select the High G Event Report- Detail or Summary to view the occurrences of the High G Events with a variety of filters including Assets, Asset Types and Drivers with the date range as a parameter.
Peak-G, Average-G and Duration
In Telematics Guru, these values are reported in the following Analogue Fields:
- Analogue 18:
- Peak G-Force
- Analogue 19:
- Average G-Force
- Analogue 20:
- Duration of the event
They can be viewed in the device telemetry under Assets -> Telemetry.