Skip to main content

Beacon configuration explained

Based on AT2 firmware v2.6

The beacon configuration is applied on top of the default delivered compact & industrial configuration. Every parameter not listed below keeps that default value.

The delivered configuration​

This is the configuration file applied to beacons at delivery:

CONFIGURATION
mode=0
lora_period=600
transmit_strat=4
periodic_pos_period=0
beaconing_type=4
beaconing_tx_power=1
beaconing_static_interval=500
beaconing_motion_interval=200
beaconing_motion_duration=20
beacon_id_0=-1410465791
beacon_id_1=-1410465790
beacon_id_2=0
beacon_id_3=0x3509
beacon_id_4=0
END

Result: the beacon advertises an iBeacon frame with UUID ABEE0001-ABEE-0002-0000-000000003509, Major 0, Minor 0, and sends a heartbeat over LoRaWAN every 10 minutes.

Line by line​

Parameter (ID)ValueDefault deliveredWhat it means
mode (0xF9)00Standby: no geolocation, only supervision messages
lora_period (0x01)600600Heartbeat ("I'm alive" message) every 600 s = 10 min
transmit_strat (0x0E)42Network ADR: the network picks the best data rate, and each message is sent once instead of twice. Saves battery on a device that never moves
periodic_pos_period (0x03)014400Periodic GPS position disabled: a fixed anchor doesn't need to locate itself
beaconing_type (0x6A)40Beaconing on, with the iBeacon frame format
beaconing_tx_power (0x6B)12Radiated power +3 dBm. This is an index, not a dBm value (see table below)
beaconing_static_interval (0x6C)50010000One advertisement every 500 ms while the beacon is still
beaconing_motion_interval (0x6D)200333One advertisement every 200 ms while the beacon is being moved
beaconing_motion_duration (0x6E)2020After a motion is detected, the beacon is considered "moving" for 20 s
beacon_id_0 (0x70)0xABEE00010UUID bytes 1–4
beacon_id_1 (0x71)0xABEE00020UUID bytes 5–8
beacon_id_2 (0x72)0x000000000UUID bytes 9–12
beacon_id_3 (0x73)0x000035090UUID bytes 13–16
beacon_id_4 (0x74)0x000000000Major (2 bytes) and Minor (2 bytes)

Why are some values negative?​

Each beacon_id_x holds 4 bytes of the frame, shown in hexadecimal. The configuration file and the CLI read values as 32-bit integers, so any value of 0x80000000 or more is written as a negative decimal number:

HexadecimalSigned decimal (as in the file)
0xABEE0001-1410465791
0xABEE0002-1410465790
0x0000350913577 (or 0x3509)

Both notations set exactly the same value. The Beacon configuration tool shows both, and computes them for you.

How the frame maps to beacon_id_0…4​

The 5 parameters hold up to 20 bytes, filled in order, most significant byte first:

Frame type (beaconing_type)beacon_id_0beacon_id_1beacon_id_2beacon_id_3beacon_id_4
iBeacon (4)UUID bytes 1–4UUID bytes 5–8UUID bytes 9–12UUID bytes 13–16Major (high 2 bytes) + Minor (low 2 bytes)
Eddystone UID (3)Namespace bytes 1–4Namespace bytes 5–8Namespace bytes 9–10 + Instance bytes 1–2Instance bytes 3–6not used
AltBeacon (5)Beacon ID bytes 1–4bytes 5–8bytes 9–12bytes 13–16bytes 17–20
Quuppa (2)not usednot usednot usednot usednot used

For Quuppa, the tag ID is derived by the firmware from the beacon DevEUI. See the Quuppa application note (AN-012) in Firmware resources.

TX power index​

beaconing_tx_power012345678
Power (dBm)+4+30−4−8−12−16−20−40

Higher power means a longer range but a shorter battery life. Your RTLS provider usually recommends a value.

Changing the configuration​

Use the Beacon configuration tool: choose a frame type and enter its content, and the tool gives you the LoRaWAN downlinks, the CLI commands and the configuration file.