nrf beacon not detectcing

[pavan]

image description(/attachment/a49b3ec690a646f7bead02928ff0a381)(/attachment/a22b78f8886f98aac724a2b9785f9c25)(/attachment/00e9df542ed79773e83dde5fb38e46cc)Hi all,

I have designed the nrf51822 based coin size custom board for beacon application. i programmed the code using keil and nrfgo studio its programming properly its advertising . but issue is, i can detect the device in nRF connect app and also in other beacon apps. but i am not detecting in nRF beacon application y is so?

is there any bugs in app?

please confirm.

thanks in advance.

[endnode]

Have you read description about exactly what "beacons" is nRF Beacon app looking for? I guess your device simply isn't sending proper UUID in advertising data or not using correct Manufacturer ID in Vendor Specific AD object of Advertising Data etc. nRF Connect shows all GAP Peripheral/Broadcaster devices so that's why it doesn't care and works OK.

[pavan]

Hi ,

But i have programmed the same program which is programmed in nRF518222 Bluetooth smart kit of nordic. its working fine in that kit but not in my custom board.

Adding to above do i need to upadate any manufacturer ID.?

[endnode]

Get radio trace from BLE sniffer or at least past RAW advertising data as captured by nRF Connect app for Android (or other OS). If the same BLE FW works on one HW (= meaning nRF Beacon app from your oriinal question can detect it and connect if necessary) and not on other then it's most likely not broadcasting at all. If you claim that certain FW on some HW (whatever custom or Nordic dev kit) works with certain application but not with other then it must be alive (= advertising and capable of connection) so it would mean that the same FW or other HW should either work the same or not work at all (because it fails during boot) but nothing in between.

[pavan]

well then you mean to say if my custom board broadcasting with some firmware in nRF connect then it should also broadcast in nrf Beacon application. rie?

[endnode]

I mean HW change should not change broadcasted information or reaction to received Connection Request. So if given FW works on some HW completely as you expect then it should either work the same or other HW or doesn't work at all.

When it comes to your nRF Connect vs. nRF Beacon app behavior I'm still missing the point. Can you update your original question with step by step summary 1/2/3/... of what you do and what you see? Then I might be able to understand what exactly is happening and what do you expect vs. what is happening.