-
-
Notifications
You must be signed in to change notification settings - Fork 34
Indications stop working shortly after starting #62
Comments
I wrote a very simple sketch to try to isolate this problem, with temperature measurement values simulated. Nothing is connected to any of the Arduino Primo pins during testing. I find that after 7 indications have been successfully transmitted and acknowledged, the setValue API starts to return false, meaning it failed and the connected client (nRF Connect) no longer receives indications. This happens completely consistently after 7 indications, every time I test. Here's the code:
and here's the serial monitor content:
|
Bump! Is this library supported or not? |
If you look at the commits by the organisation, nothing seems to have happened since the acquisition of arduino-org by arduino-cc. |
Thanks @honnet , good observation. Disappointing though! |
The version maintained by @sandeepmistry & co is good, it looks like you know it but here is the link for others who don't: |
Excellent, thank you. I'll give it a try. |
https://github.com/sandeepmistry/arduino-nRF5 does not suffer from this issue (for anyone else having problems). |
I wasn't sure which repo to log this against. I've logged the same issue against the BLEPeripheral API here:
sandeepmistry/arduino-BLEPeripheral#204
To repeat: I'm using a Primo and I'm transmitting temperature measurement characteristic values as indications. Consistently however, the first few calls to setValue return true, the client receives and ACKs the indication and I see the packets in flight. After a few successes (7 in my most recent test) however, setValue starts to return false and does not return to true responses unless I disconnect and reconnect.
Examples:
Protocol analyser showing 7 indications sent and ACKed
Serial monitor tracing indication values and API responses:
What could be causing indications to stop and is there a recommended way of getting to the root cause?
The text was updated successfully, but these errors were encountered: