FAQ(Frequently Asked Questions)

Setup Application

The displayed information for selected beacon is not updated

When the batteries are running low, beacon details may not be able to be obtained.
Please put in new batteries and try again.

I cannot see the change in the displayed beacon information when measured power had been updated

When only the measured power is updated in the setup app, changes to the values for proximity and accuracy cannot be seen immediately.
This will persist until the corresponding beacon becomes out of range for a while.
Remove the batteries so it cannot send out radio waves (equivalent to being out of range), then reset after 30 seconds. You should be able to see the change in measured power being reflected into the beacon information displayed.

Error dialog appears when I change the UUID

Since the UUID is defined by RFC 4122, if you would like to configure an UUID other than the default one into the beacon, you need to follow this to specify an unique value.
Below are ways to generate an unique UUID.
(1) Use [Proximity UUID]->[Request a new UUID] or [Generate a random UUID] in the setup app
(2) Used a tool to generate an unique UUID subject to RFC 4122
(3) (An original method which does not conflict with RFC 4122, such as using existing UUID)

When an UUID using the identifier assigned to Aplix by the ISO approved registration authority is manually entered into the setup app, a message saying "(BeaconUUID is not registered)" appeared and the process failed.
Changing only the final digit of the default UUID may contribute to the above.
Method (1) automatically generates non-repeating UUIDs serially subject to RFC 4122.

Here is more explanation.

UUID provided by RFC 4122 is separated into 5 blocks of hexadecimal numbers as below.

[(1) 8-digit]-[(2) 4-digit]-[(3) 4-digit]-[(4) 4-digit]-[(5) 12-digit]

Within which,
If the first character of [(3) 4-digit] is 1
* Please make sure that the first 6 characters of [(5) 12-digit] are not 001C4D (※1).
* Please make sure [(5) 12-digit] is not 00805F9B34FB (※2).
If the first character of [(3) 4-digit] is 4,
* Please make sure [(2) 4-digit] is not 24F6 (※3) or 0451 (※4).

(※1) 001C4D is the identifier assigned to Aplix by the ISO approved registration authority.
(※2) 00805F9B34FB is used by Bluetooth SIG's base UUID.
(※3) 24F6 is used by Aplix's base UUID.
(※4) 0451 is used by TI's base UUID.

Prevent unauthorized access to the beacon(s)

Data to be sent by the beacon module (proximity UUID, major, minor, measured power) is protected by electronic authentication system so it cannot be updated by any unauthorized third party. Each beacon module is assigned with an unique private key, data exchanged with the beacon module is encryptd by a system similar to HTTPS or SSL. In order to prevent the private key being disclosed by analyzing the application, encryption is done by the electronic authentication server, and can only be accessed by MyBeacon Administrator Account.


Bluetooth certification, registration, logo application, patent/copyright/license

According to the Bluetooth regulations, all products using Bluetooth technology must be registered to the End Product Listing (EPL). This applies to using purchased Bluetooth modules that had already been certified, or using in-house developed Bluetooth modules.

EPL registration is to be done by each product vendor or by each brand. If a product is not registerd to EPL, is it not approved as a Bluetooth device, not only that it cannot use the Bluetooth logo, it also cannot license patent or copyright from Bluetooth.

At Aplix, we develop our Bluetooth module in-house and sell it as certified Bluetooth module upon getting Bluetooth certification. We also use it to develop various beacons, and registered each one of them to EPL as Aplix's final product.

When you provide Aplix's beacons to end users, you can provide them under your own brand without having to go through Bluetooth certification again but by registering them to EPL only. If you provide them to end users as Aplix's beacons, you do not even need to be register them to EPL.
Since the beacons included in the trial development kits are intended for the trial developing of applications or services, Aplix does not provide any support to end users at all. If you would like to sell them to end users as general products, please register them to EPL and sell them under your own brand. If you would like to sell them as Aplix's beacons without registering to EPL, please do so upon signing the distributor agreement with Aplix, which provides what should be done when defects occur.

※Please consult your assigned sales rep about EPL registration.

Uniqueness of the UUID

UUID is not just a string of random characters. The format and generation method are defined by internation standard. It can be generated by using random numbers but uniqueness cannot be guaranteed. Or it can be generated by using an identifier issued by an ISO approved registration authority to ensure uniqueness.

MyBeaconIDs issued by Aplix or the UUIDs generated automatically by our setup app both use the identifier issued to Aplix by the ISO approved registration authority, therefore as long as the internation standard is followed, the same UUIDs shall not be generated by any organization other than Aplix.

For that reason, if you use the UUID issued by Aplix illegally, you either violate the international standard, or are using it by mistake, or are using it purposely. You may be requested to stop using it inappropriately.
UUIDs created using random numbers or the hash function are not guaranteed to be unique by standard, therefore it may be possible for someone else to claim that the same UUID was created by chance.

Please refer to UUID issued by Aplix for more details.

The longest reachable distance by the beacon's radio waves

According to Bluetooth specs, the longuest reachable distance is approximately 100m by sight distance.
However, it differs depending on environmental factors (absorption or reflection) or beacon settings.
The shortest reacheable distance is not particularly provided.

Information displayed on smartphone when beacon(s) are discovered

The beacon itself does not send out URL or images.
A typical use case is that when a smartphone app receives a beacon signal, it triggers the message embedded in the app or the content downloaded from the server to be displayed.