Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

The purpose of this document is to highlight the recent changes to the general setup that needs to take place for the Gimbal enablement with the release of Gimbal 2.0 SDK. 

Definitions

New for SDK 2.0:

Places
Gimbal SDK 2.0 introduces the concept of PLACES. A Place can be represented by a single geofence and/or a series of beacons. There can only be one geofence per place. Thus, when you create a Place in Gimbal Manager you can draw a geofence and/or choose a set of beacons to define the Place. A Place represents both Geofence and Proximity.

For example, a Place can be represented by a geofence (circular or polygonal), a series of beacons, or a combination of a geofence and beacon[s].

 

Previous Definitions:

Gimbal Beacon
Refers to either the physical devices (small white box or smaller blue tag), or the signal that they emit. Beacons do not connect to the internet, they just send out a unique signal used to identify the beacon.
New for SDK 2.0: MobileSmith applications can now send Gimbal Beacon notifications to Android devices.

Proximity
A type of interaction between the phones and Gimbal Beacons. This primarily deals with sightings, which are broken up into arrive, dwell, and depart events.

Geofence
A region of space (typically GPS location with a radius, but polygonal shapes are allowed too) which are set up on the Gimbal server. These are not tied to any physical beacons.

Communication
A more general (and repeatable) version of an instant communication. By design these are not specifically tied to a particular beacon, but they can be due to MobileSmith extensions. This notification will be sent to the app under certain circumstances. When created, you specify the window of time that the communication will be active.

RSSI range
For proximity, the signal strength of the beacon that would constitute an “arrive” visit and a “depart” visit. Values are always negative and values closer to zero are stronger (e.g., -20 is stronger than -30). For example, an arrive strength could be set to -40 (very close) and a depart strength could be set to -70 (fairly far away). Default value is -60 for both. The Gimbal Manager App could be used to measure beacon strength in real-time to make sure that good values for these items are set. 

Sighting Frequency
The interval at which the Gimbal Server will send sighting information to the ‘Sighting Callback URL’.

Exit Interval
The elapsed time that determines when a visit is closed.  If during this elapsed time a sighting is not sent to the Gimbal Server, then the visit is over and a depart event is sent to the Sighting Callback URL.

 

 

 

  • No labels