Digital Matter Support

Bluetooth Getting Started - Tags & Scanning

  digitalmatter.com

Visit our website for a quick explanation on the use of Bluetooth in our device range and the applications that it enables

In regards to Bluetooth firmware and devices, it is critical that you upgrade to the latest firmware version and the latest bluetooth version. Later releases of device firmware may not be compatible with all versions of BLE firmware, and vice versa.

DeviceFirmwareBluetooth Firmware
Remora22.112.5
G1202.52.1
Eagle2.12.0
G2002.31.6


Firmware Version

See how to upgrade Bluetooth firmware versions below, and device firmware versions here

Bluetooth FirmwareChoosing Scan LengthPeriodic ScanningContinuous ScanningIntegrating tagsTags in TG

Setting the Bluetooth Firmware


If you intend on using any type of Bluetooth functionality on your Digital Matter device, you will need to ensure that the system parameter 'BLE Global Settings' is enabled.


To work with the system parameters, select the device in the oemserver.com device grid, and click on 'Parameters' >> Set System Parameter (single device)



Choosing Scan Length

When choosing the scan length for your Bluetooth device you are balancing the power usage and accuracy. If the scan is too short you may miss nearby tags but if it is too long you are wasting power.

Finding the Balance

The first thing you must consider is how often your Bluetooth tags advertise their data. This is called the "advertisement interval" and can typically be configured or found in the device's datasheet. You should ensure that the Bluetooth scan length is at a minimum the size of the longest advertising interval used by your devices. You may require a longer scan time than the longest advertising interval as interference from other devices could mean tags are missed.


The next thing you must consider is whether you are using multiple scanning technologies (see here). If you are using both long range and standard Bluetooth then you should at least double the scan period.

Example

We have three different tag types:

  1. A Guppy which has an advertising interval of every 1 second
  2. An Eddystone tag which has an advertising interval of every 5 seconds
  3. An iBeacon which advertises every 100 milliseconds


Clearly the longest advertisement period is 5 seconds. We want to reduce the chance of missed data so should set the scan period as a multiple of 5 seconds. We test a scan period of 5, 10, 15 and 20 seconds, and find 5 and 10 seconds occasionally miss these Eddystone tags but 15 and 20 seconds work consistently. We therefore set the tag scan time to 15 seconds to reduce power consumption. 

back to top^


Periodic Scanning

Periodic scanning is for when you have either a static, or moving gateway that you need to scan for bluetooth tags upon conditions being met, for example, start/end of trips or specific time periods.

Scanning Settings

Scan on Trip Start:
Yes/No to scan for BLE tags on movement
Trip Start Scan Offset(s):
Set period of time to elapse after trip started to scan
Scan on Trip End 
Yes/No to scan for BLE tags on end of movement
In-Trip Scan Period(mins):
Time period in minutes between BLE tag scans while in trip. set 0 to disable
Upload on in Trip Scan:
Yes/No to enable upload to server of tag data while moving.
Out of Trip Scan Period(mins):
time period to scan for BLE tags while not moving
Upload on out of Trip Scan:
Yes/No to upload scan data while not moving
Scan Length:
Set Scan length time. See Choosing Scan Length for more information
Scan Length units:
Seconds/Minutes
Minimum Tag RSSI(dBm):
Set a minimum strength of the signal to classify a tag as 'Found' or 'Lost'
Device is Stationary:
Yes/No to declare whether device is in a fixed location

Tag Settings

Enable DM Tags: Enable the identfication/logging of the DM Guppy & SensorNode tag types
Enable iBeacon Tags: Enable iBeacon Tag types

Enable Eddystone Tags: Enable Eddystone Tag types

Other tag type 1,2,3:  See Integrating tag types here

Log Tag Lost (stationary mode): Log a 'Tag Lost' record in telemetry when a consecutive scan does not renew a tag record.

back to top^


Continuous Scanning

The Continuous Tag Scanning parameters are more tuned towards logging when tags are found or lost, rather then whether they're present when a scan is executed. This option is currently only available on the G120 4G.


Enable Scanning: Yes/No to enable Continuous Scanning, this will disable Period Scanning if enabled.

Upload on Tag Found: Yes/No to upload upon finding a new tag

Upload on Tag Lost: Yes/No to upload upon losing a tag

Upload on Update Log:  Yes/No to uploading upon consecutive tag scan

Update log Period(mins): Period between logging tag list. entering in 0 will disable

Tag Expiry Time(s): Time to elapse until Tag is declared Lost

Device is Stationary: Yes/No to declare whether device is in a fixed location

Fixed Latitude (stationary mode):

Fixed Longitude (stationary mode): Use this function to manually input gateway Longitude/Latitude

RSSI Threshold - Tag Find: strength of signal to determine whether a tag is considered found

RSSI Threshold - Tag Lose: strength of signal to determine whether a tag is considered lost

back to top^


Integrating Tags

If you require a tag to be integrated into Telematics Guru or require a complex device integration, then contact your local Digital Matter representative. However if you simply want to test a device on OEM, or want to integrate a device onto a platform other than Telematics Guru, then you can integrate the tag using the device's system parameters.


To read more about Integrating tags and the process, continue here

The following tags have been integrated into device Firmware and into Telematics Guru.

  • Digital Matter Tags (Guppy BT, SensorNode BT)
  • Apple iBeacon
  • Eddystone
  • Ingics iBS01 (Basic tag)
  • Ingics iBS01T (Temperature / Humidity)
  • Technoton DUT-E S7 Fuel Level Probe

Other tags can be integrated, contact Digital Matter for Support.


Using Tags in Telematics Guru

The flow of data from tag to TG is as follows:

Point 1
Bluetooth Tag/Sensor
Point 2
DM Bluetooth Gateway Device
Point 3
Gate way device transmits data to TG
Transmits a beacon every 2 seconds containing the tag or sensor dataScans for tags either periodically or continuously and maintains a list.
An update is sent to the server if the tag is 'Lost', 'Updated' or 'Found'.
Log reason 50 is used to indicate the upload is due to tag activity. These logs can be used to display the data meaningfully.


To add a tag into TG, you simply follow the same process as adding an asset. If your tag type is not a DM tag, then you'll have to select the type from the drop down menu.

Accessing Tag Locations and Telemetry

The new 'Tags' menu has been added into Telematics Guru, and contains two sections. Tagged Asset Status and Telemetry.

For this view to be visible the Organisation must have this functionality enabled. To check organisation functionality go to Admin -> Organisation -> Edit Organisation and ensure the Tags functionality is selected.


To access Tag information, there are three levels of Tag data displayed; Status, Map and Telemetry.


Status:

 This lists all of your tags in the one place, their location and the time they were last scanned and the gateway.

Map: 

This screen displays all of your tags on a map, with cluster view.


Telemetry: 

This screen lists all the previous scans and the status of each tag separately, and includes other statistics included in the tag's payload such as battery voltage, RSSI and Tx power.

How do I get a list of where my tags are? - Tag Location Reports

If you want a easy to digest list of where your tagged assets were last reported, you can run the 'Asset Location' report. If you've set up an 'Asset Type' for all of your bluetooth tagged assets, you can filter the report to display only the tags, and no other devices.




Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.