Beacon configuration tool
Build the configuration of your Industrial Manageable ATEX Beacon without working out beacon_id_0 … beacon_id_4 by hand. Choose the beacon frame, type its content, and copy the result: LoRaWAN downlinks, CLI commands or a configuration file. Everything runs in your browser; nothing is sent anywhere.
This tool is based on AT2 firmware v2.6. The AT2 BLE beaconing parameters remain the reference.
Resulting frame
- iBeacon UUID: ABEE0001-ABEE-0002-0000-000000003509
- Major: 0
- Minor: 0
Parameters
| Parameter | ID (dec / hex) | Value (hex) | Value (signed decimal) |
|---|---|---|---|
beaconing_type | 106 / 0x6A | 0x00000004 | 4 |
beaconing_tx_power | 107 / 0x6B | 0x00000001 | 1 |
beaconing_static_interval | 108 / 0x6C | 0x000001F4 | 500 |
beaconing_motion_interval | 109 / 0x6D | 0x000000C8 | 200 |
beaconing_motion_duration | 110 / 0x6E | 0x00000014 | 20 |
beacon_id_0 | 112 / 0x70 | 0xABEE0001 | -1410465791 |
beacon_id_1 | 113 / 0x71 | 0xABEE0002 | -1410465790 |
beacon_id_2 | 114 / 0x72 | 0x00000000 | 0 |
beacon_id_3 | 115 / 0x73 | 0x00003509 | 13577 |
beacon_id_4 | 116 / 0x74 | 0x00000000 | 0 |
LoRaWAN downlinks (port 2) — recommended
One "set parameter" downlink (0x0B) carries up to 5 parameters, so the configuration is split into 2 messages. Send them in order; each one uses the next ack token.
0B016A000000046B000000016C000001F46D000000C86E00000014
0B0270ABEE000171ABEE0002720000000073000035097400000000CLI commands (USB)
The CLI requires a USB connection, which means opening the casing. Never open the casing in an ATEX zone. Values are signed 32-bit integers, which is why some IDs are negative.
config set 106 4
config set 107 1
config set 108 500
config set 109 200
config set 110 20
config set 112 -1410465791
config set 113 -1410465790
config set 114 0
config set 115 13577
config set 116 0
config saveConfiguration file
Same format as the file delivered with the beacon (used when flashing).
CONFIGURATION
beaconing_type=4
beaconing_tx_power=1
beaconing_static_interval=500
beaconing_motion_interval=200
beaconing_motion_duration=20
beacon_id_0=0xABEE0001
beacon_id_1=0xABEE0002
beacon_id_2=0
beacon_id_3=0x00003509
beacon_id_4=0
ENDHow to use
- Build a configuration
- Pick the frame type your location system expects: iBeacon, Eddystone UID, AltBeacon or Quuppa.
- Type the frame content (UUID, Major and Minor for iBeacon, and so on). Dashes and spaces are accepted in hex values.
- Adjust the TX power and the advertising intervals if needed. The default values are those of the beacon as delivered.
- Copy the output you need (see below).
- Decode a configuration: paste an existing configuration (for example the file delivered with your beacon) to see which frame it produces. Values may be decimal, negative decimal or hex (
0x…).
The fields are pre-filled with the delivered configuration, which advertises the iBeacon UUID ABEE0001-ABEE-0002-0000-000000003509, Major 0, Minor 0. To understand each parameter, see The beacon configuration explained.
Applying the configuration
| Channel | When to use it |
|---|---|
| LoRaWAN downlinks (port 2) | Recommended. The casing stays closed. Send the messages in order; a "set parameter" downlink carries at most 5 parameters, so a full configuration takes two messages. |
| CLI over USB | Paste the commands into a serial terminal (user PIN 123 by default). config save keeps the configuration after a reset. |
| Configuration file | Used when flashing the firmware with Abeeway Updater, which applies it as the default configuration. |
USB access (CLI or Abeeway Updater) requires opening the casing. Never open the casing in an ATEX zone. Prefer LoRaWAN downlinks for beacons already installed.
The CLI and the configuration file take signed 32-bit integers. A value such as 0xABEE0001 is above the signed range, so it is written -1410465791. Both notations mean exactly the same bits; the tool shows them side by side.