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]

Just to confirm. This ticket and  connectless CTE TX/RX problem use the same project, but are two separate issues, correct? On my end, I'm not able to recreate this behavior either. Are you using an antenna array on the receiver side here to recreate this or just the two DKs? What exactly do you mean by "stopping" the TX side here, do you just turn it off, or what? Since logging is disabled on both sides in this project I'm not sure what to look for exactly. Please try to describe more in detail what the issue is exactly.

Best regards,

Simon

[loquat]

That's another issue.
I am using the same test code due to an issue found while testing the CTE.

The test code is built with ncs2.4.1.
I've modified the test code to make it easier to check.
Manipulate LEDs with events.
LED1 blinks periodically (code is working)
LED2 Lights up when sync_create() is successful (turns off in term)
LED3 Lights up when synced callback is called (turns off in term)
LED4 blinks every scan_recv is called (to confirm that it has been received)

Procedure (nRF52833-DK)
1. Start RX side
2. Start TX side
3. Immediately turn off the power on the TX side when LED2 on the RX side lights up.
Measure the time until LED2 turns off
There was a pattern below.
a. If LED3 lights up, LED2/LED3 turn off immediately after (3.)
b. LED2 turns off after about 6 seconds
c. LED2 does not turn off
In case (c.), sync_create() will not succeed for the same TX. (Need sync_delete()?)

I would like to know under what conditions (b.) occurs.

4426.df_tx_2.zip  2843.df_rx_2.zip