can't send packet in specified time interval

RE: can't send packet in specified time interval

Karl Ylvisaker — Fri, 28 May 2021 16:33:16 GMT

[quote user="ali_dehghan_nayeri"]yes, debug is enabled.[/quote]

Are you getting any error messages in your log, when you have DEBUG defined?

[quote user="ali_dehghan_nayeri"]can you adwise me for changing that?[/quote]

If you intend to send multiple packets each connection event, you will indeed need to have a queue size longer than 1. If you are not explicitly setting the queue size anywhere in your code it will use the default value, which is 1. This means that only 1 packet can be queued for sending each connection event. If you would like to change this, you can use the sd_ble_cfg_set function to do so. You can see how this could be done in the answer by my colleague Petter in this ticket. You must make this configuration before enabling the SoftDevice, as mentioned in the functions API reference.

Are you familiar with the nRF Sniffer tool? It is a powerful tool to wield when developing with BLE, as it lets you see all the on-air BLE traffic. It would help a lot if you could setup a sniffer, to see how many packets are being sent every connection event.

Best regards,
Karl

RE: can't send packet in specified time interval

ali_dehghan_nayeri — Fri, 28 May 2021 11:43:50 GMT

thanks for your response.

yes, debug is enabled.

changing the queue size was my goal in the first but I couldn't change it.

I issued that on this page.

can you adwise me for changing that?

thanks.

RE: can't send packet in specified time interval

Karl Ylvisaker — Fri, 28 May 2021 07:18:10 GMT

Hello,

[quote user="ali_dehghan_nayeri"]Interrupt of timer0 was the problem.[/quote]

Yes, TIMER0 is in use by the SoftDevice, and may not be used by the application when the SoftDevice is enabled, this will cause the SoftDevice to assert.

You mention that you get error for resources, could you make sure to have DEBUG defined in your preprocessor defines, like shown in the included image?

This will make the logger output a detailer error message whenever a non-NRF_SUCCESS error is passed to an APP_ERROR_CHECK.
If you are getting NRF_ERROR_RESOURCES from sd_ble_gatts_hvx then that means that you are queueing notifications faster than you are sending them, leading to the buffer filling up.

[quote user="ali_dehghan_nayeri"]so can we set sending ble packet priority more than the interrupt priority of timer0?[/quote]

You do not need to worry about prioritizing to send packets - the SoftDevice handles all this for you.
I think the issue here is that your notification buffer is full, so that you are unable to queue all the packets you want to have sent. What queue size are you using?

Best regards,
Karl

RE: can't send packet in specified time interval

ali_dehghan_nayeri — Thu, 27 May 2021 15:18:44 GMT

so can we set sending ble packet priority more than the interrupt priority of timer0?

RE: can't send packet in specified time interval

ali_dehghan_nayeri — Thu, 27 May 2021 11:39:35 GMT

Interrupt of timer0 was the problem.

I got a lot of interrupts from timer0 and nrf couldn't send my packets in the expected time.