notification not receivied with timer

RE: notification not receivied with timer

mobi — Thu, 22 Jan 2015 17:36:13 GMT

Debugging in further... the problem was in send_debug_message... As per documentation, the application must take care of application buffer when sending messages and keep the count of message buffered and decrement when BLE_EVT_TX_COMPLETE happens..

or simply, if receive BLE_ERROR_NO_TX_BUFFERS when error from sd_ble_gatts_hvx call... then wait till BLE_EVT_TX_COMPLETE happens, meaning buffer have place to send more packets.

Hope this helps for other who end up trying something like that.

Here is what helped me to understand this:

developer.nordicsemi.com/.../a01058.html

developer.nordicsemi.com/.../a01043.html

RE: notification not receivied with timer

leo b. — Thu, 22 Jan 2015 17:27:50 GMT

I think I know the problem. I think you are sending all 10 notifications in a single connection interval. I think a single connection interval can only send 4 to 6 packets/notifications. The rest are discarded. Try using a faster connection interval, an interval time that is smaller than your timer delay.

RE: notification not receivied with timer

mobi — Thu, 22 Jan 2015 09:46:09 GMT

in total I receive only 9 notifications... and then I don't receive any notification even If I loop for 20 or 30 times...

RE: notification not receivied with timer

mobi — Thu, 22 Jan 2015 08:21:34 GMT

I tested and now I send the message number a long as well... Now I see, index 0,1,2,3,4,5 But I don't see 7,8,9 being sent.... That is strange.

RE: notification not receivied with timer

mobi — Thu, 22 Jan 2015 06:28:35 GMT

now that is interesting point... "Maybe some of the notifications are overlapping with each other during one connection interval, causing some notifications to be discarded." any topic ? I would like to know this in detail. As I'm looking into reliable data transmissions.

RE: notification not receivied with timer

leo b. — Thu, 22 Jan 2015 06:23:26 GMT

Maybe the connection interval you are using is much slower than the timer delay. Maybe some of the notifications are overlapping with each other during one connection interval, causing some notifications to be discarded.