Hello,
I have a BC127 bluetooth module with UUID: 9F B3 43 C4 A0 71 48 08 86 45 58 DC A0 FF 12 99. I have edited the app.js with my ibeacon uuid in the format (I suspect) as the other UUID and it is not coming up. I've tried multiple playstore apps as well. I send my BC127 the following serial commands to prepare it for ibeacon mode:
reset
restore
write
set ble_role=3
set ibeacon_major=0001
set ibeacon_minor=0002
advertising on
I launch ibeacon scanning apps and nothing is found. I am running melody 5.8 and according to the manual the UUID is stored in Little Endian format. . Maybe I'm missing something? The manual is found at: http://www.bluecreation.com/fdownload.p ... 414398.pdf
iBeacon Scan App not finding my iBeacon
Re: iBeacon Scan App not finding my iBeacon
You might try our example "ble-scan" and see if it shows up there. Then you can know if your device is advertising at all.
Once you've confirmed the device is advertising, you might try reversing the byte order of the UUID. You might also try adding the device's default UUID ("00001101-0000-1000-8000-00805F9B34FB") to the iBeacon Scan example, in case your UUID doesn't get set properly.
Once you've confirmed the device is advertising, you might try reversing the byte order of the UUID. You might also try adding the device's default UUID ("00001101-0000-1000-8000-00805F9B34FB") to the iBeacon Scan example, in case your UUID doesn't get set properly.
-
- Posts: 2
- Joined: 00:04, 02 Oct 2015
Re: iBeacon Scan App not finding my iBeacon
Hello,
Thank you for your reply! I have tried BLE Scan and it does find my device. I have not tried the default UUID and will try this later, that's a good idea. I also have been trying to figure out how to reverse the byte order of the uuid and I am unable to convert from little endian to big endian. Are ibeacon UUID's traditionally transmitted in big endian format? From my Googling, it appears that there is no definite answer for this. I will let you know if the default UUID works.
Thanks!
Thank you for your reply! I have tried BLE Scan and it does find my device. I have not tried the default UUID and will try this later, that's a good idea. I also have been trying to figure out how to reverse the byte order of the uuid and I am unable to convert from little endian to big endian. Are ibeacon UUID's traditionally transmitted in big endian format? From my Googling, it appears that there is no definite answer for this. I will let you know if the default UUID works.
Thanks!
Re: iBeacon Scan App not finding my iBeacon
Normally, the concept of endianess doesn't apply to UUIDs at all. They are just a string of bytes. I don't know why the manual authors decided to mention it. I agree that there is no obvious answer.
A few guesses:
For further reading, if you're interested, Wikipedia has an extensive article on Endianess.
A few guesses:
- Reverse the entire UUID such that the first byte goes last and vice versa. For your UUID, that'd be "9912FFA0-DC58-4586-0848-71A0C443B39F".
- Or, reverse it by 4-byte or 2-byte group. I'm not gonna bother calculating that. :}
For further reading, if you're interested, Wikipedia has an extensive article on Endianess.
Return to “Questions and answers”
Who is online
Users browsing this forum: No registered users and 42 guests