The Yabby3 allows geofences to be downloaded from the server onto to the device. This allows for two key solutions:

• Disabling cellular communications and GPS fixes for a period of time in sensitive area such as an airport, military space etc.
• Using alternate logging parameters when inside/outside certain areas to increase battery life

For basic geofence settings, such as creating geofences and setting entry/exit alerts, please see the article here. Simply generating entry/exit alerts does not require the 'download to device' functionality to be configured.

This feature is fully integrated with Telematics Guru. Geofences can be downloaded to the device from a 3rd party server, however significant integration work may be required. Contact our support team for documentation, DM can offer only limited integration support for this feature.

How to enable Geofence downloads for the Yabby3?

To enable geofence download to the device, we need to

1. Add the geofence download server in device parameters via OEM Server
2. Configure our geofences and settings in Telematics Guru

OEM Server Parameter Setup:

In OEM Server, go to Parameters->Edit Admin parameters->Add Geofence Server

Add your custom Telematics Guru URL to the "Geofence Download server" tab. This is just the URL that you use to access Telematics Guru.

Enabling Geofence Download in Telematics Guru:

• From  Assets-> Manage Assets-> Edit Asset (click on the asset name or the cog menu on the far right hand corner)
• Since geofence download parameters are grouped by "Asset Type", in the General Tab of the edit asset screen, set the desired asset type
  
  
  This can also be done in bulk
  
  
  
  
• Select the Advanced tab from the edit asset dialogue, and check the "Enable Geofence Download" checkbox at the bottom of the window.
  
  

Geofence Asset Types

Geofence downloads are grouped by asset type, allowing for intelligent management, and fast application of this feature. The process for configuring a geofence asset type is as follows:

1. Navigate to Admin->Asset Type Geo-Fences and select the desired asset type. (An individual 'Asset Type' is created in Admin > Asset Types, and assigned in Assets > Asset Manage)
2. Click "Create Geofence Asset Type Setting"
3. Select a Geofence to download and edit the desired fields. Not all features are available for the Yabby3 (for example, the Yabby3 does not have outputs, and so the 'Digital Output Settings' will have no effect). 
4. Click save, and repeat for each Geofence to download

Additional Geofence settings

Speed Settings (not relevant to Yabby3)

The minimum and maximum speed can be set for the geofence, and for powered devices configured when outside this range. There are no IOs on the Yabby3, so this feature is not relevant and can be left alone.

Upload When

The moment a device recognizes it has entered or exited a Geofence (dependent on the logging parameters), it can be configured to upload, which in turn could be used to trigger an alert (either an SMS or email). 

Example: 

• Yabby3 default parameters are 2 min GPS fixes in trip, with 30 min updates
• This means data only reaches TG every 30 min, so we will be waiting this long for Geofence entry/exit arlets
• If we configured to upload on Entering/Exiting a Geofence - as soon as a device gets a fix entering/exiting - it will immediately upload - meaning the latency is now 2 min. 
• If parameters were say 15 min GPS fixes in trip, latency would be up to 15 min.
• For information on how to set an alert on Telematics Guru, please consult: Configuring an Alert

No Communication Duration

This can be used to define a time for which the device will not attempt a cellular upload/connection after obtaining a fix inside a geofence. 

If the device gets a GPS fix inside a no communications Geofence, then it will not use cellular communications until it gets a GPS fix outside the fence. 

The device will not communicate while 'inside' the Geofence. This means no uploads are attempted between:

• When the device first obtains a fix inside a no-comms geofence
• When the device first obtains a fix outside a no-comms geofence it will now resume uploads as normal.

The device will not communicate while inside the geofence and for 24 hours after leaving. 

Alternate Logging (OEM server)

If this is set, the device will use the alternate set of geofence logging system parameters configured on OEM. This can be used to intelligently manage the battery life of a device.