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]

I mean like:

1. I take pre-compiled HEX file named xyz from this path in this nRF5 SDk version and flash it by this program with this SoftDevice HEX file to this HW.
2. Then I see this LED blinking (or not), I turn on nRF Connect app, I see the device broadcasting (what are "RAW" advertising and scan response data??? Paste it here!) and I can connect to the device (what happens in nRF Connect then? Any change on the board e.g. LEDs blink/light differently?)
3. Then I open nRF Beacon app and do this and that, see this and that.
4. Then I take same HEX files and flash the same way another HW (any description of that HW???) and see this and that.
5. Then I open nRF Connect app again and see this and that etc. ......................

[pavan]

Hi below are my steps,

1. I take softdevice from this path (C:\Nordic Semiconductor\nRF51822 Beacon v1.1.1\SoftDevice) and programmed successfully using nrfgo Studio on nrf51DK.
2. then i took application program from this path (C:\Nordic Semiconductor\nRF51822 Beacon v1.1.1\Precompiled hex) and programmed successfully using nrfgo Studio on nrf51DK. 3)Then I see no LED blinking I turn on nRF Connect app, I see the device broadcasting now i opened nRF Beacon i can see detect device in App with monalisa picture.No LEDs blinking.

Now i repeated the same steps with my custom board i can see device detecting nRF Connect app but not in nRF Beacon it keeps scanning. Attached the raw data and images of both DK and custom board for your refeance.

[endnode]

If you look and compare the data you can see straight away that they are different! Then no surprise that applications are working differently! Mainly manufacturer ID at the beginning of last LTV object data (0x5900 vs. 0xFEAA) can make any beacon scanner failing because it usually don't look for two IDs but just one (but Manufacturer ID isn't typically the only filter on scanner's side!) So you obviously don't run the same FW on both beacons. Why such misleading description in the question? Why you imply that some app has bug when you test with almost "random" devices? I don't get it.

[pavan]

Hello ,

As per your suggestion i run one firmware only on my custom board but still no change its not detecting in nRF beacon app could you please help us solve this issue . i will be running the firmware only on my custom board.

[endnode]

I cannot argue about how you mix HW and FW versions during your tests but the advertising data are different so you have definitely more then one FW/configuration. Once you are OK with some of them then stick with it and test the other HW. Also note that some mobiles might cache adv. data so restarting BT/whole device might help as well. But that applies to cases where nRF Connect app displays data which you don§t expect. I§m afraid you are not there yet;)