ESP32 + NRF52832

[kiranj]

hello,ESP32 ble scanner is not scanning my custom made beacon (nrf52832),I have programmed ble_app_beacon apllication in tag and ESP32 is scanning all ibeacon except our custom board tag.please help.thanks.

[run_ar]

Hi Kiranj,

Have you tried to compare the advertisement data on the custom beacon that does not work, with the advertisement data sent from the ibeacon that does work. I guess you are filtering for some UUID or other information that you are missing (or have misconfigured) in the custom beacon.

[kiranj]

yes,i have uploaded same firmware on both boards(nrf52832dk and custom made nrf52832 board) but dk board get scanned in esp32 and our board did not....but it is scanning in nrf52832 dk scanner and nrf connect app.but not in esp32.I have compared the raw data packet also it is exactly same for both boards.

[kiranj]

esp32 is third party product,on a chip microcontrollers with integrated Wi-Fi and dual-mode Bluetooth.

www.espressif.com/.../overview

[awneil]

So nothing to with Nordic, then.

Remember that this is Nordic's own forum!

As Turbo Jsaid earlier:  

https://devzone.nordicsemi.com/f/nordic-q-a/40576/esp32-nrf52832/157830#157830 

[run_ar]

I have to say I agree with Awneil, that this is an ESP32 issue. I would guess you are doing some sort of filtering or whitelist not compatible with the custom beacon.

More unlikely, There is also a possibility there is something wrong with your HW that makes it incompatible with the ESP32 but still works with nRF connect. But this is unlikely.

[awneil]

kiranj said:

esp32 is ... a chip microcontroller

Yes - but what is this "ESP32 ble scanner" that you are talking about?

A microcontroller on its own does nothing - it needs both supporting hardware and software to form a functioning product.

[awneil]

run_ar said:

this is an ESP32 issue

More specifically, it's most likely an issue with whatever software is running on the ESP32.

run_ar said:

some sort of filtering or whitelist

Indeed - which would be a software thing.

As noted above, there might be a signal strength threshold ...

May also be affected by the hardware of the mystery "ble scanner" that kiranj seems so loathe to describe.

Again, none of those things has anything to do with Nordic.

run_ar said:

There is also a possibility there is something wrong with your HW that makes it incompatible with the ESP32 but still works with nRF connect. But this is unlikely

Indeed.

So an obvious next step should be for kiranj to try another scanner (or scanners) - there are plenty of apps available to do that.

If other scanners "see" the custom beacon, the conclusion should be obvious...

[kiranj]

thanks for your suggestions.I'm also thinking that ESP32 is not compatible with these tags.

[awneil]

kiranj said:

I'm also (sic) thinking that ESP32 is not compatible with these tags

Nobody else is saying that.

Clearly your unit - which you have still not identified - is compatible, because it manages to see one of your tags!

So you need to investigate your ESP32 code to see where & why it is filtering-out the other tag.

But that, again, has nothing to do with Nordic.

You still haven't answered the question about signal levels.

[kiranj]

what do you mean by signal levels??

[awneil]

Seriously?

RSSI - the Received Signal Strength Indication.

It's how "loud" the RF signal is - if it's not "loud" enough, then a receiver won't be able to "hear" it.

https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.tools/dita/tools/nRF_Connect/nRF_Connect_Connecting_devices.html?cp=5_3_0_3

[kiranj]

I have checked it.rssi also "loud" enough to scan .