• State Verified Answer
  • Replies 3 replies
  • Subscribers 87 subscribers
  • Views 993 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 276208
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Samples direction_finding_connectionless_rx/tx (nRF Connect) not working (not finding the periodic advertising)

jakkra

Hi, I'm trying to migrate to Nordic  nRF Connect APIs for Direction Finding. To start I just tried getting the samples direction_finding_connectionless_rx and direction_finding_connectionless_tx working, however I'm not able to get it working. The scanner never finds the periodic advertisement sent by direction_finding_connectionless_tx sample.

See logs:

Transmitter (AoA):

west build -p -b nrf52833dk_nrf52833 -- -DOVERLAY_CONFIG=overlay-aoa.conf -DTC_OVERLAY_FILE=boards/nrf52833dk_nrf52833.overlay

*** Booting Zephyr OS build v2.6.0-rc1-ncs1 ***
Starting Direction Finding periodic advertising Beacon Demo
Bluetooth initialization...success
Advertising set create...success
Update CTE params...success
Periodic advertising params set...success
Enable CTE...success
Periodic advertising enable...success
Extended advertising enable...success
Started extended advertising as DA:6E:5E:6B:10:87 (random)

Receiver:

west build -p -b nrf52833dk_nrf52833 -- -DTC_OVERLAY_FILE=boards/nrf52833dk_nrf52833.overlay

Starting Connectionless Locator Demo
Bluetooth initialization...success
Scan callbacks register...success.
Periodic Advertising callbacks register...success.
Start scanning...success
Waiting for periodic advertising...[DEVICE]: 52:2A:FB:2C:39:E4 (random), AD evt type 3, Tx Pwr: 127, RSSI -86 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 22:45:51:DF:0C:24 (random), AD evt type 3, Tx Pwr: 127, RSSI -62 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 00:12:F3:01:19:33 (public), AD evt type 0, Tx Pwr: 127, RSSI -76 C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 37:FD:C7:01:DB:1F (random), AD evt type 3, Tx Pwr: 127, RSSI -84 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: D5:1F:F2:64:CA:90 (random), AD evt type 3, Tx Pwr: 127, RSSI -81 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 45:0C:88:85:F0:38 (random), AD evt type 0, Tx Pwr: 127, RSSI -67 C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 3E:85:92:2E:B6:DA (random), AD evt type 3, Tx Pwr: 127, RSSI -69 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: CF:98:95:2E:71:5A (random), AD evt type 3, Tx Pwr: 127, RSSI -87 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: EB:BB:D0:D6:0C:09 (random), AD evt type 3, Tx Pwr: 127, RSSI -87 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 74:2D:3C:1F:84:5A (random), AD evt type 0, Tx Pwr: 127, RSSI -88 C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 7D:9C:4E:48:84:66 (random), AD evt type 3, Tx Pwr: 127, RSSI -87 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 00:12:F3:00:00:09 (public), AD evt type 0, Tx Pwr: 127, RSSI -51 C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 00:12:F3:00:00:09 (public), AD evt type 4, Tx Pwr: 127, RSSI -50 NINA-B3-000009 C:1 S:1 D:0 SR:1 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 37:7D:4B:B5:2E:86 (random), AD evt type 3, Tx Pwr: 127, RSSI -77 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 05:94:61:72:BF:FD (random), AD evt type 3, Tx Pwr: 127, RSSI -74 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 50:32:37:A7:0D:4E (public), AD evt type 0, Tx Pwr: 127, RSSI -87 C:1 S:1 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 24:4B:03:D6:83:48 (public), AD evt type 3, Tx Pwr: 127, RSSI -89 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255
[DEVICE]: 55:18:0F:DF:91:5F (random), AD evt type 3, Tx Pwr: 127, RSSI -86 C:0 S:0 D:0 SR:0 E:0 Prim: LE 1M, Secn: No packets, Interval: 0x0000 (0 ms), SID: 255

..... goes on 

Scanner never find the advertisments sent by the transmitter

Any idea why it's not working? I tried both nRF Connect 1.6 and 1.6.1 and tested sample both in nrf/samples and zephyr/samples/ folders.

Thanks alot,

Jakob

Parents
  • 0

    Hi, 

    The sample can work as expected on my side. Try to run nrfjprog --recover on both DKs before programming the images. 

    Please let me know it can help or not. Thanks. 

    Regards,
    Amanda

  • 0 in reply to Amanda Hsieh

    Thanks for the quick reply, unfortunately did not make a difference. I'm not using the NRF52833_DKs but still use it as board since it should be close enough for this case. From the logs everything looks good.

    I have a sniffer and I can see the device sending (image is for our transmitter and not the DK)

    But I grabbed a nrf52833_DK and flashed it with same transmitter SW and it suddenly worked, so issue is with our tag hw+module. 

    When I compare the sniffer logs between our hw and the DF I can see that with our module I see no packets on channel 37, 38, 39. Must be some configuration that's breaking it. Any idea what it could be?

Reply
  • 0 in reply to Amanda Hsieh

    Thanks for the quick reply, unfortunately did not make a difference. I'm not using the NRF52833_DKs but still use it as board since it should be close enough for this case. From the logs everything looks good.

    I have a sniffer and I can see the device sending (image is for our transmitter and not the DK)

    But I grabbed a nrf52833_DK and flashed it with same transmitter SW and it suddenly worked, so issue is with our tag hw+module. 

    When I compare the sniffer logs between our hw and the DF I can see that with our module I see no packets on channel 37, 38, 39. Must be some configuration that's breaking it. Any idea what it could be?

Children
Related
Terms of service