
ANT-B10 - User guide
UBX-22006906 -
R02
Configuration and mounting
Page 9 of 29
C1-Public
3
Configuration and mounting
3.1
Configuring and testing the board
After connecting ANT-B10 to the USB port, a serial port (COM port on Windows) becomes available
on the host. Connect the COM port to a terminal emulator or use the s-center tool
with the
following port settings:
•
115200 kbps
•
8 data bits, no parity, 1 stop bit (8N1)
•
Flow control enabled using RTS/CTS
A green LED light indicates that the board is powered on.
Having connected the COM port, the board is ready to receive AT commands. For information about
the AT commands to use for configuring direction finding, see
s-center supports specific direction-finding AT commands in the AoA tab, as shown in
. The
COM port can also be configured as a terminal for use with AT commands.
Once the system is setup, each anchor reports angle calculation events (
+UUDF
) over the serial port
connection. ANT-B10 returns events similar to the following when it detects a beacon:
+UUDF:CCF9578E0D8A,-42,
20
,0,0
,37,”CCF9578E0D8
9
”,””
,15869
+UUDF:CCF9578E0D8B,-41,
10
,4,0
,38,”CCF9578E0D89”,””
,15892
+UUDF:CCF9578E0D8A,-42,
-10
,2,0
,39,”CCF9578E0D89”,””
,15921
…
The data reported in these events can be used to estimate a position of the tracked beacon. The
parameters of the
+UUDF
event are (in order from left to right):
•
Eddystone instance ID
•
RSSI of 1
st
polarization
•
Azimuth angle
•
Elevation angle
•
Reserved
•
Detected advertising channel, that is, one of the normal Bluetooth Low Energy advertisement
channels (37, 38 or 39)
•
Anchor ID as set by
AT+UDFCFG
•
User defined strings as set by
AT+UDFCFG
•
Timestamp
For a detailed description of the
+UUDF
event parameters, see also
In the angle calculation events shown above, the beacon is moving from one side of the anchor to the
other as the azimuth angle. Given as the third parameter in the command (shown in bold), the beacon
moves from a positive value (20) to a negative value (-10).
☞
The optimal distance between anchor nodes and tags is approximately 2
–
15 m.