• State Verified Answer
  • Replies 34 replies
  • Subscribers 74 subscribers
  • Views 4861 views
  • Users 0 members are here
Attachments (4) Download All
Nordic Case Info
  • Case ID: 313503
Options

connectless CTE TX/RX problem

loquat

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
  • 0

    Hi

    Based on your case history I assume you're working on NCS 2.4.0, however I'm not able to get the TX project build on my end. Anything that might be necessary to add on my end in order to do so? Also, how rarely exactly does this occur. 

    You say the current consumption suddenly drops. How much exactly? Could it be that the RX device is going to sleep for some reason. I don't really see a reason why by reviewing your project though...

    Best regards,

    Simon

Reply
  • 0

    Hi

    Based on your case history I assume you're working on NCS 2.4.0, however I'm not able to get the TX project build on my end. Anything that might be necessary to add on my end in order to do so? Also, how rarely exactly does this occur. 

    You say the current consumption suddenly drops. How much exactly? Could it be that the RX device is going to sleep for some reason. I don't really see a reason why by reviewing your project though...

    Best regards,

    Simon

Children
  • 0 in reply to Simonr

    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)
    If advertising by other unrelated devices is being sent, it is easy to confirm that the RX side is receiving it.
    1. Start RX side
    2. Start TX side
    3. Repeat power ON->OFF on TX side (repeat about 3 seconds ON/3 seconds OFF)
    4. After repeating (3.) several times, leave the power on and wait.
    5. RX side reception stopped (LED4 blinking stopped)

    The frequency of occurrence is as short as a few minutes, and as long as several tens of minutes.

    Upload the PPK log when reception stops on the RX side.

    df_tx_2.zip  df_rx_2.zip

  • 0 in reply to loquat

    Hi

    Following these instructions I haven't been able to reproduce this after running the RX sample connected to a PPK2 for ~40 minutes (all LEDs are on/blinking as expected and the current consumption shows RX occurring as expected). I'll leave it running when I head out today and see if it has occurred when I come into office tomorrow. If not, do you have more than two DKs available for testing so you can make sure it isn't the specific DK(s) you're using? Also, how far away from each other are the two devices placed when you do these tests? I have them no more than 0.5m away on my end.

    Can you also show me how the DK and PPK you're measuring on are connected physically, and if you're testing in source meter or ampere meter mode.

    Best regards,
    Simon

Related
Terms of service