Data Sheet

Preliminary
DATASHEET Ɩ EMBP00
Copyright 2019, EM Microelectronic-Marin SA
EMBP00-DS, Version 0.1, 3-Apr-19
16
www.emmicroelectronic.com
features can be made available on request in SimpleBeacon Configuration Tools. Disabling of advertisement
channels is not compliant with Bluetooth specifications and compatibility with other BLE technology cannot be
guaranteed when channels are disabled.
7.2.3. RSSI Table
The Eddystone™, iBeacon™ and altBeacon™ packet types include a one byte signed value that is used to
communicate the signal strength of the packet being transmitted. This byte is retrieved from the RSSI Table in
the EMBP00. The beacon engine will automatically retrieve the setting that correlates to the selected output
power setting for the advertisement. Default values are assigned using the calibration procedure defined by
Apple™ and an iPhone 4S™. The default settings are as defined in Table 12.
Table 12: RSSI Table
Tx Power Level
(dBm)
RSSI Table Entry
(dBm at 1m)
6.2
-55
4.6
-57
2.5
-59
0.4
-61
-1.4
-63
-2.6
-64
-4
-66
-5.5
-67
-6.9
-68
-8.4
-70
-9.9
-71
-11.4
-73
-13.1
-75
-14.6
-76
-16.4
-78
-17.9
-79
-29
-91
-33.5
-95
The RSSI Table values may be modified using the SimpleBeacon Configuration Tools.
7.2.4. Connectable Advertisement
These Bluetooth advertising packets are connectable, undirected advertising events (ADV_IND) which follow
the GAP specification according to the Bluetooth Specification V5.0, Volume 3, Part C, Section 11.
The friendly name used in the connectable advertisement may be redefined using the SimpleBeacon
Configuration Tools. If the friendly name is left blank in the SimpleBeacon Configuration Tools, the name is
automatically generated from the device address. Additionally the special character “$” in the friendly name
will be replaced with the lowest nibble in hex of the device address.
The default friendly name is EM-$$$$$$.
7.2.5. Non Connectable Advertisements
These Bluetooth advertising packets are non-connectable, undirected advertising events
(ADV_NONCONN_IND) which follow the GAP specification according to the Bluetooth Specification V5.0,
Volume 3, Part C, Section 11.
iBeacon™ Format
The format of the iBeacon™ packet is described in the following specification: Proximity Beacon
Specification Release R1 Draft D1, which can be obtained from Apple, Inc.
The UUID, Major ID and Minor ID used in the iBeacon™ advertisement may be redefined using the
SimpleBeacon Configuration Tools. If the UUID is set to 0, the default UUID of 699EBC80-E1F3-11E3-
9A0F-0CF3EE3BC012 is used. If the Major ID are set to 0, the Major ID from the second lowest two
bytes of the device address. If the Minor ID are set to 0, the Minor ID from the lowest two bytes of the
device address. For example, for a device with address: 0C:F3:EE:AA:BB:CC. If the Major ID is set to 0,
the transmitted Major ID will be 0xEEAA. If the Minor ID is set to 0, the transmitted Minor ID will be
0xBBCC