FMB125 Beacon List

From Wiki Knowledge Base | Teltonika
This is the approved revision of this page, as well as being the most recent.
Main Page > Fleet management > FMB125 > FMB125 Configuration > FMB125 Beacon List

Beacon Settings


Beacon Detection

0 (Disabled) – Functionality disabled.
1 (All) – All visible beacons are detected (Max. 100).
2 (Configured) – Only beacons from the list are sent to server

Beacon Record

0 (Eventual) – Disabled. (Record is sent after scan procedure is completed). This parameter depends from the Bluetooth 4.0 Scan Settings.
1 (Periodic) – All beacons are sent to server. (Record will be saved accordint to configured period).

Record Period - Beacon record saving period

Record Period on Move & Record Period on Stop. Timers for record generation when device is moving and staying at place.
Record Period on Move (Default value 60 seconds)
Record Period on Stop (Default value 60 seconds)

Beacon Settings.PNG

While selecting the Beacons Detection as All, the device will detect all beacons which are located around the device.

All.png

Select Beacons Detection as the Configured, in this case, the beacons will only be detected and send if they were added to the Beacons List.

Configured.png

Beacon List


List of authorized beacons. Eddystone and iBeacon protocols are supported*.

Beacon List
*Beacon Ids can be entered the following way: Namspace:CompanyID, UUID:Major:Minor. Any of the ID parts can be omitted ex., Namespace:. UUID::, UUID::Minotr, etc


There is also possible to select Beacons Detection as the Configured, in this case, the beacons will only be detected and send if they were added to the Beacons List.

Example for the configured beacons detection in the List.


Below there is provided the example of the List, while using the Beacons Detection source as Configured. The provided example is showing the configuration for the iBeacon and Eddy-stone.

Configured List.png

The Beacons settings is configured as showed. The iBeacon or Eddystone is added to the list with the following structure:

iBeacon – 20 Bytes (UUDI (16-bytes:major(2-bytes):minor (2-bytes))

Eddystone – 16B (Namespace (10-bytes):Instance ID(6-bytes))

There is possibility to detect the devices just by UUID or Namespace (see the 2 and 6 element in the list).

Or by the Major/Minor for iBeacons and Namespace for Eddystone. (see the 3 and 7 element in the list).