What cause the empty PDU

RE: What cause the empty PDU

Håkon Alseth — Tue, 12 Sep 2023 07:45:05 GMT

Hi,

The problem is the flag "SEND_RDY", where it is reset and set for each BLE_GATTS_EVT_HVN_TX_COMPLETE evt.

You can for instance move the SEND_RDY=0 to the BLE_GAP_EVT_DISCONNECT event.

Kind regards,

Håkon

RE: What cause the empty PDU

Tom.Fu — Tue, 12 Sep 2023 02:29:41 GMT

Hi Håkon

Many thanks for the detail explanation.

Is there any other way to avoid or reduce the empty PDU in some connection? In our application, we would like to send 10bytes a packet to the peer every 20ms accurately to control the motor, and the connection interval I set is 20ms, so it requires that a packet must be sent in every connection. Is there any way to achieve this? Many thanks.

RE: What cause the empty PDU

Håkon Alseth — Mon, 11 Sep 2023 12:21:33 GMT

Hi,

Sorry for not seeing this earlier, but the SEND_RDY flag is the reason why you're seeing every other payload.

When your function is called, you are effectively queueing one payload to the SoftDevice, and for an ACK (ie. evt BLE_NUS_EVT_TX_RDY occurs, which sets SEND_RDY=1 again), that will happen when a notification has completed.

When receiving GATT event "BLE_GATTS_EVT_HVN_TX_COMPLETE", which is the same as BLE_NUS_EVT_TX_RDY, it means that the TX has successfully occurred. This comes with a count field, which shows how many packets has been successfully sent in this specific interval, as described by my colleague here: RE: Missing BLE_GATTS_EVT_HVN_TX_COMPLETE events

Kind regards,

Håkon

RE: What cause the empty PDU

Tom.Fu — Mon, 11 Sep 2023 09:52:52 GMT

Hi Håkon

I set NRF_SDH_BLE_GAP_DATA_LENGTH to 27 and the APP_TIMER_CONFIG_RTC_FREQUENCY to 0　and I tried sending data in the ways separately like the screenshot below. But it still catch the empty PDU like before.

RE: What cause the empty PDU

Håkon Alseth — Mon, 11 Sep 2023 09:20:57 GMT

It depends on if you want to send as much as possible or not.

It is up to you how you want it to behave.

Kind regards,

Håkon

RE: What cause the empty PDU

Tom.Fu — Mon, 11 Sep 2023 09:13:21 GMT

Hi Håkon

Many thanks for your supporting.

But this part is the sample implementation by default. By the way, what is the correct way to call the ble_nus_data_send() in this case? Many thanks.

RE: What cause the empty PDU

Håkon Alseth — Mon, 11 Sep 2023 09:02:48 GMT

Hi,

Thanks for sharing.

I think you want the do-while to be checked with this:

do {
...
} while (err_code != NRF_ERROR_RESOURCES);

You should also set sdk_config.h::NRF_SDH_BLE_GAP_DATA_LENGTH to 27 or higher. It was set to 23 by default.

To send more packets per connection interval, you can also consider adjusting sdk_config.h::NRF_SDH_BLE_GAP_EVENT_LENGTH to a higher number.

The 40 ms comes from the RTC prescaler. You should set the sdk_config.h::APP_TIMER_CONFIG_RTC_FREQUENCY to '0' to fix this.

Here's a small screenshot from the sniffer after making the adjustments above:

Kind regards,

Håkon

RE: What cause the empty PDU

Tom.Fu — Mon, 11 Sep 2023 02:31:33 GMT

Hi Håkon

Sorry for that, I upload the peripheral code again.

But I found that the NRF_LOG_DEFERRED has been set to 1 both in these two sample by default.

Many thanks.

devzone.nordicsemi.com/.../1067.ble_5F00_app_5F00_uart.7z

RE: What cause the empty PDU

Håkon Alseth — Fri, 08 Sep 2023 12:43:53 GMT

Hi,

Unfortunately, it seems that the peripheral code was not uploaded properly. Could you please re-upload this?

Without having tested or looked deeper into the implementation, I would recommend that you use deferred logging, as logging in the handler will delay the function.

Either set sdk_config.h::NRF_LOG_DEFERRED to 1, or try to limit log printing in your callback handler to see if this has an impact on the behavior.

Kind regards,

Håkon