• State Not Answered
  • Replies 20 replies
  • Subscribers 74 subscribers
  • Views 3631 views
  • Users 0 members are here
Attachments (8) Download All
Nordic Case Info
  • Case ID: 283030
Options

nrf connect app for desktop

Ridhi

I am using nrf52832 dev kit and soft device s132. I have use my board as peripheral

and i have another nrf52840 dev kit which i am using as a central connect it with my PC which has nrf connect app for desktop.

i have a code which is perfectly running on my nrf connect app on mobile but it is not running on nrf connect app for desktop.

pls help

Parents Reply
  • 0 in reply to Ridhi

    I have personally never seen a characteristic write retuning NRF_ERROR_BUSY on the nRF Connect desktop. This error code usually means that too many SoftDevice API calls have been issued, so that the command queue is full, however I would not expect this to be a problem on a desktop application. This supports my suspicion from earlier that the '11' value is never sent to the peripheral device, which is why you are not seeing the notifications on the nRF Connect desktop.

    Please answer the questions in my previous reply, so that I may get a better understanding of what is happening in your application.

    Best regards,
    Karl

Children
  • 0 in reply to Karl Ylvisaker

    i have saved logs in flash memory. When i connect i just enable notify , write 11 and get the data. i nrf app for desktop also i am doing the same.

  • 0 in reply to Ridhi

    Thank you for providing the videos, this makes the issue more clear.
    I will try to replicate this on my end as well.

    It looks to me like you attempt to enable CCCD before the CCCD characteristic is discovered, and that you also try to write to the characteristic before the discovery is complete.
    What happens if you wait until it is complete before writing to the characteristic?

    Please also answer:

    Karl Ylvisaker said:
    Could you also tell me if you are able to read and write the other services of the device, or if they all are inaccessible?


    Best regards,
    Karl

  • 0 in reply to Karl Ylvisaker

    I HAVE battery service, i am able to read it. 

    when i even wait for CCCD to discover still i am not able to write in the characteristic for the second service for which i have to get notification data

  • 0 in reply to Ridhi
    Ridhi said:
    I HAVE battery service, i am able to read it. 

    Thank you for clarifying this.

    Ridhi said:
    when i even wait for CCCD to discover still i am not able to write in the characteristic for the second service for which i have to get notification data

    It seems to me that you are attempting to enable the notification before the CCCD characteristic has been discovered.
    I am not able to reproduce this behavior on my end, unfortunately.

    Could you try to reinstall the Bluetooth Low Energy application in nRF Connect, and re-flash the nRF52840 DK that you are using on the central side, and see if this changes anything?
    I will ask internally if anyone else has seen the NRF_ERROR_BUSY error in the Bluetooth Low Energy application before.

    Best regards,
    Karl

Related
Terms of service