Strange behavior in central device using nrf51822

RE: Strange behavior in central device using nrf51822

Sigurd — Tue, 21 Feb 2017 14:02:09 GMT

Great that you solved the problem. I can't see any reason why a array overflow could have caused this, and I have never seen this kind of behavior before.

RE: Strange behavior in central device using nrf51822

Gustavo Velasco-Hernández — Tue, 21 Feb 2017 12:55:39 GMT

Hi @Sigurdon, I previously clean the list and the device appears again. Also RSSI graph shows a continuous line during the blocking condition. Only after scanner is powered off, RSSI graph is discontinued and advertising interval and RSSI are greyed out. A good new is that we found an array overflow in our code. That was causing this problem. However, I keep wondering on how the scanner could become a "broadcaster". Thanks for your reply.

RE: Strange behavior in central device using nrf51822

Sigurd — Tue, 21 Feb 2017 10:13:06 GMT

Note that nRF connect will still show all the peripherals it have found while scanning. If you turn off the peripheral during scanning, it will still show in the app, but the RSSI and advertising interval field will be greyed out after a while. If click on More in the app, and then history you can see when the last advertising packet was received.

RE: Strange behavior in central device using nrf51822

Gustavo Velasco-Hernández — Mon, 20 Feb 2017 19:19:01 GMT

We used ble_app_uart_c example as a start point for our application, but all the code related to NUS, UART, GPIOTE were removed. In some cases, I've found that in nRF connect app keeps appearing Eddystone frames, even using the MAC address of any of the REAL Eddystone beacons when all of them are disconnected.

RE: Strange behavior in central device using nrf51822

Daniel Wang — Mon, 20 Feb 2017 19:05:42 GMT

What central SDK example is this scanner based on, have you done any modification to it? the central starts to send advertising packets it previously received?