beacons are missed when debugger is not connected

RE: beacons are missed when debugger is not connected

Simonr — Mon, 15 Jul 2019 06:51:11 GMT

Then it seems the problem is based in the central. You say you've added UART to the ble_app_blinky_c example. You might've missed something when implementing UART into that example which is what causes the central to not receive all the beacon advertisements. Can you try using the ble_app_uart_c example for your central application? Also, please add a snippet of code to show how you've implemented UART to your central as of now.

Best regards,

Simon

RE: beacons are missed when debugger is not connected

Kadir — Tue, 09 Jul 2019 14:21:52 GMT

i checked the beacon signals, there is no problem in the beacon module

RE: beacons are missed when debugger is not connected

Simonr — Mon, 08 Jul 2019 09:33:41 GMT

Ok, thanks for the clarification. Can you try using a sniffer to see what happens to the advertising packets? If they're sent from the beacon at all? The nRF Sniffer should be a useful tool if you don't have a sniffer already.

Best regards,

Simon

RE: beacons are missed when debugger is not connected

Kadir — Mon, 08 Jul 2019 08:11:27 GMT

No, arm microcontroller is connected to nrf52 central via uart to receive beacon data, i am using ble_app_blinky_c as a central and ble_app_blinky as a peripheral. In the central, i only added uart. In the ble_evt_handler, if there is a beacon, beacon data is send to the uart with non_blocking mode. I do not change any paramaters except power management function actually

RE: beacons are missed when debugger is not connected

Simonr — Mon, 08 Jul 2019 07:34:45 GMT

This arm microcontroller is connected to the beacon, correct? And the central is not able to receive the BLE signals from the beacon 100% of the time. The lack of using power management should not be an issue. Did you base your project on one of our SDK examples? In that case, which one, and what changes have you made to it other than removing the power management function?

Best regards,

Simon

RE: beacons are missed when debugger is not connected

Kadir — Fri, 05 Jul 2019 12:00:51 GMT

there is an arm microcontroller that receives beacon data from nrf52 through uart, i checked the uart signals with oscilloscope, and i see that there is not problem in the uart or arm mcu. I will make more research the issue regarding HFLCK. Additionaly, i do not use nrf_pwr_mgmt_run() function, is it the reason?

Thank you

RE: beacons are missed when debugger is not connected

Simonr — Fri, 05 Jul 2019 11:47:22 GMT

A common reason something would work "better" in debugger mode, is that in debugger mode, the HFCLK is forced to stay on all the time, while in normal mode, the HFCLK will be turned off to minimize the current consumption when it isn't needed, so for example between scanning/transmitting radio events. Which could be the reason it ain't received. A few questions, as I don't quite understand your setup:

Does this gateway work as a relayer, so it receives a beacon signal, and transmits it to your central? What device is your central? If you're able to see that the beacons are received by the central, is it the gateway that isn't receiving 40% of your beacon signals?

Best regards,

Simon