connectless CTE TX/RX problem

I am testing connectless CTE RX/TX.
A strange behavior is occurring.
Please advice me.

・connectless CTE TX
     nRF52833-DK + nRF Connect SDK + connectless CTE TX (almost same as sample)
・connectless CTE RX
   nRF52833-DK + nRF Connect SDK + My Application (customised connectless CTE RX)
   Scan doesn't stop after sync_create().

1. CTE is received normally for several tens of minutes.
2. Suddenly reception on the connectless CTE RX side stops. (stop scan)
3. If you start advertising while reception is stopped, you will be able to receive it.
4. When advertising stops, reception also stops. (stop scan)
5. If the connectless CTE TX is operating (transmitting) while advertising is running, reception will not stop even if advertising stops.

Is there anything we can investigate?

Parents
  • Hi

    Okay, so it seems like it stops scanning because the sync to the advertiser is lost then. Does the TX device also stop advertising at this point, and that is why the scanner stops? By default the advertising timeout is set to 0 in the connectionless CTE TX sample, but if you've changed this, it could be that the advertiser simply times out perhaps? It could also be helpful with a log from the advertising device in that case.

    Best regards,

    Simon

Reply
  • Hi

    Okay, so it seems like it stops scanning because the sync to the advertiser is lost then. Does the TX device also stop advertising at this point, and that is why the scanner stops? By default the advertising timeout is set to 0 in the connectionless CTE TX sample, but if you've changed this, it could be that the advertiser simply times out perhaps? It could also be helpful with a log from the advertising device in that case.

    Best regards,

    Simon

Children
  • When the advertising ends, the scanning that was running until then stops at the same time.
    Calling bt_le_scan_stop() in this state will not return an error.
    This is a strange move.
    A successful bt_le_scan_stop() means the scan was working. However, the scan is not actually working.

    In addition, I tested the same thing with nRF5340 (app+hci_rpmsg), but the same trouble occurs when it works for a long time.

    Any problem with bluetooth stack?

Related