Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Beacon code #29

Open
hoonkai opened this issue Oct 24, 2015 · 1 comment
Open

Beacon code #29

hoonkai opened this issue Oct 24, 2015 · 1 comment

Comments

@hoonkai
Copy link

hoonkai commented Oct 24, 2015

Hi

Just wondering what the purpose of the "Beacon code" is. Why is the big endian representation of a seemingly random hex needed in the advert packets?

Thanks

@davidhelms
Copy link
Contributor

The AltBeacon advertisement makes use of the Manufacturer Specific Advertising Data structure as defined in Bluetooth Specification Version 4.0, Volume 6, Part B, Section 2.3 Advertising Channel PDU. The payload of the Manufacturer Specific Advertising Data is arbitrarily defined by the sender, and is generally defined by the manufacturer of the beacon. The AltBeacon specification defines a meaningful data structure for this payload. The beacon code as the first 2 bytes of the payload communicates to the receiver that this payload should be recognized as being an AltBeacon advertisement and that the following bytes should be interpreted as defined by the AltBeacon specification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants