bt_le_per_adv_sync_create() term event timing

[loquat]

My system is nRF52833 + nRF Connect SDK.
I testing PeriodicAdvertising with CTE.

After executing bt_le_per_adv_sync_create(), if synced is not completed for about 10 seconds, the term event seems to be called. Is this correct?
Also, is it written in the documentation?

[Simonr]

Hi

In the create_sync() function in I.E. the Direction Finding Connectionless RX sample, you can see that the sync_create_param.timeout is set to 10 by default. So yes, this is correct. It should be fine to change this to what you seem fit though.

Best regards,

Simon

[loquat]

timeout is explained as follows.
"Synchronization timeout (N * 10 ms)"

Indeed the timeout is set to 10.
But it means "100ms". (Not 10 seconds.)
Also, isn't the timeout the timeout when ADV_SYNC_IND can't be received after synced?

[Simonr]

Of course, you're correct. My mistake. I have not found anything specific on why the sync. is terminated after 10 seconds yet, but I'll ask around and keep looking.

Are you able to use the bt_le_per_adv_sync_term_info() and read out the reason for the termination of the synced advertisement on your end?

Alternatively. Can you give us some instructions on how to reproduce this issue on our end so we can try to debug this? Are you using an nRF52833 DK, what sample project have you used as a base for this, and have you made any changes to said sample project on your end?

Best regards,

Simon

[loquat]

bt_le_per_adv_sync_term_info.reason is 0x3E.

[loquat]

Upload sample code.
Please write to nRF52833-DK.

Stop the TX side after s_adv_sync_count[2] is incremented.
s_adv_sync_count[3](sync_cb) is not incremented and s_adv_sync_count[4](term_cb) is incremented.
This time was 6-7 seconds in the sample code.

5861.df_tx.zip6740.df_rx.zip