• State Not Answered
  • Replies 7 replies
  • Subscribers 93 subscribers
  • Views 934 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 332335
Options

"High Duty Directed advertising" appears repeatedly and then Disconnected and Connected.

ParanBada

I am developing a keyboard using "ble_app_hids_keyboard" of SDK17.1.0 version.
When I look at the log during testing, "High Duty Directed advertising" appears repeatedly and then Disconnected and Connected.

What is this function and why does it appear like this?
And is there a detailed document about this?

High Duty Directed advertising.
Disconnected
Connected
High Duty Directed advertising.
Disconnected
Connected
High Duty Directed advertising.
Disconnected
Connected
High Duty Directed advertising.
Disconnected
Connected
High Duty Directed advertising.
Disconnected
Connected
High Duty Directed advertising.
Disconnected
Connected
High Duty Directed advertising.
Disconnected
Connected  

  • 0 in reply to Edvin

    1.
    The problem occurs frequently on Windows laptops. I erase use [eraseall] the BLE devices and downloaded the firmware again and I removed the BLE device from Windows and reconnected it.
    The above problem occurs when connected to windows for a long time.

    2.
    It does not appear on Android.

    3.
    How to know if the device connected to BLE (nRF52840) is Windows, Android, or Macbook.

    4.
    And I will also try the method you mentioned(sniffer).

    Best Regards,

  • 0 in reply to ParanBada

    Hello,

    I understand. Well, if it happens only after being connected to Windows for a long time, does it mean that it goes away if you use "eraseall" and remove the BLE device from Windows? 

    Do you know if the log says something right before it falls into this state?

    High Duty Directed advertising.
Disconnected
Connected
High Duty Directed advertising.
Disconnected
Connected
High Duty Directed advertising.
Disconnected
Connected
High Duty Directed advertising.
Disconnected
Connected
...

    At this point, I believe a sniffer trace will be helpful. When you flash the sniffer FW to another DK or Dongle, remember to select the advertiser from the drop down menu close to the top of WireShark, so that it filters out everything not belonging to the peripheral. Then it will also follow into a connection with this device. You may need to enter the 6-digit passkey when the device pair into wireshark as well.

    Best regards,

    Edvin

Related
Terms of service