I am working on a product using the CC1352R1 Sub-GHz 15.4 radio stack and it has been working fine in our "shorter" tests. However, after running the devices (a mix between heavily modified versions of the collector and sensor examples) for a couple of weeks the sensor just disconnects and stops generating scan confirmation calls, even after receiving multiple collector beacons. Neither does the sensor seem to be able to request a beacon from the collector, both are running in non-beacon mode.
However, if I get another sensor to request a beacon the malfunctioning device also receives it during its scanning phase. Though, even after receiving the beacon correctly, at the end of the scan it does not generate a call to the pScanCnfCb callback, which it normally does during normal operation.
I have seen several other questions at E2E regarding the scan callback not being called:
My question is then if a scan not triggering the scan callback is a known issue, and what could cause it?
Since I do not have access to the underlying source code for the 15.4 stack I have not been able to come very far into the debugging, other than confirming the above behavior.
It seems to be completely arbitrary as some devices do this after just a couple of days and others after about a month after shipped to the customer.