To display in Telematics Guru, do the following:

Set up the I/O Mapping

Setting up the I/O mapping simply gives a meaningful name to the digital input. The previous step ensures that data will be sent to TG when the door opens or closes, but now we need to put it in an easily readable format.

1. Go to Assets -> Manage Assets
2. Click the Asset Name you want to edit (or do this when creating your asset)
3. Go to I/O Mappings
4. Create the Mapping

The active state (1) is Open, and inactive (0) is closed (as per OEM set-up)

Display on Trip view results in the status being available on the map

To send alerts via Telematics Guru, we simply need to set up an alert that is sent when the Digital Input is activated.

This can be done using the "Advanced" Alert creator, found under Admin -> Alerts

If the relevant asset is selected in the "Assets" Tab of Create Alert, the name given in the I/O mapping will appear as shown in the image.

An alert can also be sent when the door closes again, so the user is notified when everything is back to 'normal' Under the Advanced tab of the alert setup, simply select this option and fill in the message you would like.

Alternatively, the Panic/Duress Button Alert from the Alert Wizard can be used - just use the Digital Input you are using with the reed switch, and a more accurate name at the end of the set up.

Reporting on Door Being Left Open

It may not be of much interest if the door is simply opened or closed, but important if it remains open. The "Duration" condition of the Alert setup can be used

The above issue shows set up for an alert to fire if the door remains open for over 10 minutes. 

However for this scenario it is important that "Upload on Inactive" is selected in OEM so we know immediately when the door is closed again. 

There are also some caveats to this set-up which are discussed here Duration Condition for Alerts

Reporting on Door Open/Close

To run a report on the times and duration the door was opened, we can set up a Custom Event. An Alert is the email/SMS sent due to a condition occurring, and an Event can be thought of the way this is recorded for later reporting, via the Event Reports. 

To set up an event, go to Admin -> Event Types

We want to log on the Start and End of Event, so the time that the duration the door was left open for can be monitored. In this scenario the other logging is not relevant - e.g. Distance, Geofence etc. However if it was door on a truck etc that moves, Distance may be relevant, it depends on the application.

Now we can return to the Asset's I/O mappings and link Digital Input 1 to the Event

 A record of door opens/closes will be available in the Custom Events - Summary, and Custom Events - Detail Reports

See High-G Event Detection

Our battery powered devices feature Jostle Mode Tracking where accelerometer activity is used to detect trips/movement, i.e, when accelerometer activity is detected, a trip is started and we can set the device to upload for an alert. Then once it has sat still for a while (timeout configurable) - the trip will end. 

Please refer to Default Tracking Parameters for more details on different tracking modes.

So for this application, a Trip Start = Door Open (Movement)

This setup is not 100% foolproof. Below are some key points that need to be considered

• Install is super simple, see image below
• We need to be careful with how we choose our accelerometer wakeup parameters (i.e. how much movement causes a trip start) - to avoid missing a door open/close event, or generating false ones
• The device is only looking at accelerometer activity, so for example if a sea container is loaded onto a truck - it looks the same as door open/closed.
• We can't distinguish definitively between open/closed - just movement of the door
• We can't detect multiple events <60s -60 sec is the minimum trip end timeout configurable.

This may sound like instructions to avoid this setup! But it is not the case, just things to be aware of. For example sea containers are an excellent example of a what this would work for. Perhaps they sit in the yard for long periods, and we just need an alert if anyone opens the door. The container would sit very still, so as not to prevent false alerts - and we'd get an alert if there was unauthorized entry, and can action it. We wouldn't be able to say the door was opened and closed exactly 50 times - but perhaps this isn't necessary information. 

Installation Overview

First we have to look at how to attach the device and the positioning factors that come into play. If you're trying to monitor movement on an interior door that doesn't have a good view of the sky for GPS positioning, the Yabby Edge or Oyster Edge will be a good option to go with.

There are two main levels when using the accelerometer to detect door/gate movement. You can disable the wake filter to make even the slightest bump will wake the device up, or you can configure the wake filter to measure a certain type of movement.

For the first option - for any tiny movement to make the device upload, we want to have upload on movement detection and Disable Wake filter set to Yes. 

We have set the trip end time to 60 sec in this case. If you're installing a device on a doorway that is used for x minutes at a time, you could set the end trip to slightly longer than this to reduce multiple alerts.

We can disable logging and uploading during trip off since we are only interested if the door has moved at all, rather than monitoring usage after the door is opened. 

We can also adjust the adjust the accelerometer settings to configure what level or movements will start a trip. The wake-up threshold is the force of the movement and the wake-up count is how long it persists for.

These settings come into play with what your use case is, if you have a gate that gets bumped by the wind on it's latch normally, but you want to know when it's opened you can set the wake-up count to be higher to filter out the short jostles.

By the same token you can set the wake-up threshold higher so you only want to the asset to upload when a strong bump is identified for either a long or short period as determined by the count.

After Hours Detection

If you wanted to have high resolution reporting after hours, you can set up a second set of movement detection parameters which the device will use once it moves into the declared time period. The settings in this tab are the same as the standard movement detection. Adaptions you could make are:

1. No logging or uploads on movement detection during 9am - 5pm, but uploads on movement detection between 5pm and 9am
2. Enable wake filter during 9am - 5pm to only detect larger movements and disable to detect slight jostles after hours.

Parameter setup for After Hours Movement can be found here: After Hours Movement