Strange behavior in central device using nrf51822

[Gustavo Velasco-Hernández]

Hi, I'm using a nRF51822 as a observer/scanner for Eddystone beacons. This device is intended to scan up to 16 beacons, but under certain conditions (unknown at this moment) the scanner becomes unresponsive and keeps "broadcasting" one of the packets it previously received from a beacon. I say it is unresponsive because we are using it as SPI slave, and when the blocking condition appears, it starts responding the default character for ignored transmission.

Also, when I use nRF Connect app, I can view Eddystone data frames coming from beacons (which I named from 1 to 16). The beacons are intended to send data for a few seconds and then stop advertising. When the condition appears, I keep seeing a "beacon" after the timeout for sending data expires. Even if I disconnect all the beacons, only when the central is powered-down, the fake "beacon" disappears from nRF Connect app.

This is a very strange behavior, and we could not identify what the problem is. Any suggestion about what could be happening?

[Sigurd]

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.