Unable to obtain repeatable scan response data.

RE: Unable to obtain repeatable scan response data.

Edvin — Thu, 09 Jan 2020 15:26:52 GMT

Perhaps you can try to hack another central example. In the advertising_report event, just set a filter on the address that you know is correct and print something every time you receive an advertisement and every time you receive a scan response.

I tried to open your project, but it says:

Other than that, I don't understand why it shouldn't work in your project. But again, it is difficult to follow the project and your state machine from looking at the main.c file.

RE: Unable to obtain repeatable scan response data.

Sam273 — Thu, 09 Jan 2020 08:21:28 GMT

The above sniffer image is what the peripheral is seeing, showing that it is getting scan request from the central Mac address 66:0b... and the peripheral responses with a scan response. It is that scan response that my central can't see in software. (I have seen a response in my software occasionally after long periods of scanning, upwards of 10 minutes.)

Yes I can see scan response data from other peripheral consistently in my software.

Central & peripheral settings are the same :

scan interval = 160 = 100ms

Scan duration = 0 = Infinite

Scan window = 80 = 50ms

Min connection interval = 7.5ms

Max connection interval = 7.5ms

RE: Unable to obtain repeatable scan response data.

Edvin — Thu, 19 Dec 2019 10:41:36 GMT

Does this only apply for this peripheral's scan responses?

You say that you can receive other peripherals' scan response, correct?

What is the advertising interval of your peripheral, and what is the scan interval and scan window on your central?

RE: Unable to obtain repeatable scan response data.

Sam273 — Thu, 19 Dec 2019 07:34:13 GMT

The data on the sniffer is quite consistent Irrespective of whether scan response was received or not.

I get a scan request every 180ms but that can be as high as 580ms or low as 16ms. Around 3 responses are missed every 20 requests. if the peripheral responds it is within 4 ms.

RE: Unable to obtain repeatable scan response data.

Edvin — Wed, 18 Dec 2019 11:24:34 GMT

If one of the devices LFCLK is off, then the timing of the scan response would be off, and the scanner may not pick it up correctly. Since you were able to pick up the scan responses from the other devices frequently, it may suggest that your peripheral's LFCLK was off, sending the scan responses at the wrong time, outside the window when your central was scanning.

Is it possible for me to recreate your issue? Is it possible for me to reproduce this with two DKs?

From your sniffer trace, is that the scan response that you received? Does it look the same the next time, when you don't get the scan response?

BR,

Edvin

RE: Unable to obtain repeatable scan response data.

Sam273 — Wed, 18 Dec 2019 11:05:11 GMT

Thanks for the suggestion, why did you think this could have been a problem using the XTAL clock?

No the behavior remain's the same after changing to the above config.

RE: Unable to obtain repeatable scan response data.

Edvin — Tue, 17 Dec 2019 09:06:30 GMT

Try to set both the peripheral and central to this:

#define NRF_SDH_CLOCK_LF_SRC 0
#define NRF_SDH_CLOCK_LF_RC_CTIV 16
#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 2
#define NRF_SDH_CLOCK_LF_ACCURACY 1

Does that change the behavior?

BR,

Edvin

RE: Unable to obtain repeatable scan response data.

Sam273 — Mon, 16 Dec 2019 16:17:22 GMT

with CTIV and CTIV_TEMP configured as zero.

RE: Unable to obtain repeatable scan response data.

Sam273 — Mon, 16 Dec 2019 16:15:56 GMT

The Client and peripheral are configured as this

RE: Unable to obtain repeatable scan response data.

Edvin — Mon, 16 Dec 2019 15:58:59 GMT

What is your peripheral? Is that also a nordic? Is that also using the internal oscillator?

So for both your central and peripheral. What is:

#define NRF_SDH_CLOCK_LF_SRC
#define NRF_SDH_CLOCK_LF_RC_CTIV
#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV
#define NRF_SDH_CLOCK_LF_ACCURACY

BR,

Edvin

RE: Unable to obtain repeatable scan response data.

Sam273 — Mon, 16 Dec 2019 12:23:41 GMT

No I am using the internal oscillator, no LFXTAL.

fnOnAdvReport is called from a softdevices event BLE_GAP_EVT_ADV_REPORT.

RE: Unable to obtain repeatable scan response data.

Edvin — Mon, 16 Dec 2019 11:56:49 GMT

I was thinking of whether you had an external LFXTAL. Do you? What are the specs on the LFXTAL if you have one? And what are your defines in sdk_config.h:

#define NRF_SDH_CLOCK_LF_SRC
#define NRF_SDH_CLOCK_LF_RC_CTIV
#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV
#define NRF_SDH_CLOCK_LF_ACCURACY

I can't say why you are not getting your scan responses from that particular device. From where do you call fnOnAdvReport()? Do you have any filtering before that call?

RE: Unable to obtain repeatable scan response data.

Sam273 — Mon, 16 Dec 2019 11:04:21 GMT

64Mhz interanl clock. I have two custom pieces of hardware with NRF52832 devices on for both my central and peripheral.

Yes i'm using the nrf sniffer and i can see scan responses:

RE: Unable to obtain repeatable scan response data.

Edvin — Mon, 16 Dec 2019 10:34:38 GMT

Ok. so you see it some times, but rarely. What is your clock settings on your device? What HW do you use (Both peripheral and central)? Are the DKs? Or some custom HW? Have you tried to sniff the advertisements? Does it actually send any scan responses? You can use the nRF Sniffer for this.

RE: Unable to obtain repeatable scan response data.

Sam273 — Mon, 16 Dec 2019 10:01:50 GMT

Hi Edvin,

I'm using SDK 15.2

Currently for debugging I just have a infinite loop of searching for devices - scan and advertising data..

I'm printing any advertised data by printing the UUID - this is working fine as im seeing my and other devices (I can connect to my device with this data)

I'm printing any scan response data - I am seeing a variety of devices, garmin, Versa, LE-reserved, ect

and the scan response data from my device - I am not/ rarely it seeing.

If i do find a scan response data from my device i check the address i came from to check it matches with the advertised data found.

Thanks,

Sam

RE: Unable to obtain repeatable scan response data.

Edvin — Fri, 13 Dec 2019 13:00:42 GMT

Hello,

What SDK are you using?

Are you sure that your device has advertising response, and that you are not picking up advertising packets from another device nearby with scan response? Check the address of the device.

Are you sure your device is not resetting? (encounters an error)? Can I see the messages you get when you use NRF_LOG_DEBUG()? (I assume LOG_DEBUG() uses this).