Streaming SAADC values over BLE at 1 ksps

[Ankush]

Hi ,

I am working on one application in which i need to stream the ADC values over BLE to the mobile App. This should happen at very high rate i.e. 1000 samples per seconds. I am using SAADC of nrf52 with 12 bit resolution.

Can it be possible and what are the parameters should I consider while doing this? Please help me to solve this issue. Kindly suggest any sample code or any important thread related to this.

[Ankush]

Also When I used APP_TIMER_TICKS(1,0) for sampling at 1 ms seconds interval and then collecting 12 samples to form a packet then my BLE connection gets disconnected. I don't know why it happening.Is it because of connection interval ?

[puz_md]

Hi Ankush,

First of all, I would like to mention that I am a Nordic customer like you are and I don't have the time to go through all your code (which is in my opinion way too large, by the way) and give you full support. But I'll try to gice you some hints as my linited time allows.

I have never worked with app_timer (and probably never will), so I cannot give you much help there. Maybe the app_timer does not support small intervals like 1ms? I don't really know at all.

I suggest you do some debugging and analyze the data that is sent and received. It seems like you use a sequence number in the first byte of the packet. Are packets missing between the sequence numbers? Then you might have a buffer overflow on the sender side (maybe the connection interval is set too slow), or your smartphone is not powerful enough to handle all received notifications. If the sequence number is always the same and does not increase, it seems like your software is causing a reset due to implementation errors. Have you checked for continuous resets? You can also add a printf() statement each time you try to send a packet, so you can track down the error.

It also seems that you are calling the ble_nus_string_send() with APP_IRQ_PRIORITY_LOW (callback!) and not from the main() loop. Is this allowed? Please check the documentation, if there is a problem with priorities maybe this could cause the SoftDevice to trigger a reset. By the way, when your BLE connection gets disconnected, this usually suggests that something went wrong within the SoftDevice (e.g. SoftDevice timing is out of sync) and there was a system reset.