Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Qt BLE writeDescriptor error
Forum Update on Monday, May 27th 2025

Qt BLE writeDescriptor error

Scheduled Pinned Locked Moved Solved Mobile and Embedded
qtconnectivitybluez5
2 Posts 1 Posters 777 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K Offline
    K Offline
    Kutyus
    wrote on 15 Oct 2018, 13:30 last edited by
    #1

    Hi!

    I upgraded from Qt 5.10.1 to 5.11.2, and my code is not working, on new environment.
    I connected to a BLE device, discovery services, and I would like to written the ClientCharacteristicConfiguration descriptor(0100, subscribe), and first try the device is going to ClosingState, and disconnecting. The second try, I have a DescriptorWriteError with Already notifying message.
    I downgraded the environment, and i have same errors.

    Thank you for reply.

    K 1 Reply Last reply 15 Oct 2018, 15:01
    0
    • K Kutyus
      15 Oct 2018, 13:30

      Hi!

      I upgraded from Qt 5.10.1 to 5.11.2, and my code is not working, on new environment.
      I connected to a BLE device, discovery services, and I would like to written the ClientCharacteristicConfiguration descriptor(0100, subscribe), and first try the device is going to ClosingState, and disconnecting. The second try, I have a DescriptorWriteError with Already notifying message.
      I downgraded the environment, and i have same errors.

      Thank you for reply.

      K Offline
      K Offline
      Kutyus
      wrote on 15 Oct 2018, 15:01 last edited by
      #2

      Ok, I have a mistake, in descriptorwitten signal I checked it new value, and if it is 0000, I disconnect from device.
      But I checked the 1 index byte (the second), not the 0 index byte (first), and the second is always zero.
      This is my byte order mistake.

      1 Reply Last reply
      0

      1/2

      15 Oct 2018, 13:30

      • Login

      • Login or register to search.
      1 out of 2
      • First post
        1/2
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved