Advertising signals is not seen by nRF-Connect.

RE: Advertising signals is not seen by nRF-Connect.

PopradiArpad — Wed, 04 Apr 2018 11:57:03 GMT

Hi Terje,

thank you very much.

Regards,

Árpád

RE: Advertising signals is not seen by nRF-Connect.

tesc — Wed, 04 Apr 2018 09:37:55 GMT

Hi,

One option may be to use the Serial interface, which means you use an nRF device running the mesh stack as connectivity device connected to a PC, or RP3, or any other controlling device for that matter. Then you can use an interactive user interface through PyACI, or you can write test scripts that uses the serial interface (commands and events).

Regards,
Terje

RE: Advertising signals is not seen by nRF-Connect.

PopradiArpad — Tue, 03 Apr 2018 11:01:55 GMT

Hi Terje,
thank you for your answer and sorry for my the late answer.

On RP3 I wanted to test the MCU with BT mesh application.
I use RP3 to test a simple BLE application on MCU already.

On Android I wanted to see when the MCU is in advertising mode.

Regards,

Árpád

RE: Advertising signals is not seen by nRF-Connect.

PopradiArpad — Tue, 03 Apr 2018 10:59:07 GMT

Thank you!

RE: Advertising signals is not seen by nRF-Connect.

Aleksander Nowakowski — Tue, 13 Mar 2018 18:15:46 GMT

I'll add some support for mesh in the next release.

Records won't be unknown EIRs anymore.

RE: Advertising signals is not seen by nRF-Connect.

tesc — Tue, 13 Mar 2018 18:08:37 GMT

Hi,

Bluetooth Mesh uses Advertising Data types (AD types) in the advertising packet that has been assigned for the Mesh Profile Specification. For devices that do not have support for Bluetooth Mesh those AD types are unknown, and it looks like some systems may choose not to relay the advertising packet to applications in such cases.

There is very little change from version 1.0.0 to version 1.0.1, and none that should affect advertising. That means you probably see exactly the same both for v1.0.0 and v1.0.1 if you use the same device for scanning. I.e. it all probably depends on how the device handles advertising packets that are formatted in an unknown way.

I do have a couple of questions back. For what purpose are you detecting the advertising packets from an rPi3 or Android device? Perhaps we might have some other suggestions for how to achieve your end goals here.

Regards,
Terje

RE: Advertising signals is not seen by nRF-Connect.

PopradiArpad — Wed, 21 Feb 2018 07:30:32 GMT

Hi Aleksander,

thanks for your answer. My phone is on Android 7.0. I can detect the advertising signals with another pca10040 but it would be nice to detect it from my phone or (better) from a Raspberry Pi.

RE: Advertising signals is not seen by nRF-Connect.

Aleksander Nowakowski — Tue, 20 Feb 2018 14:57:10 GMT

Hi, if you're using Android 8 or newer it disregards packets that contain errors, for example extra 0s at the end of an advertisement packet. You could try on an older phone if that's the case.

You may also use nRF Connect for desktop to check if your device is advertising and with what data exactly.