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

[Karl Ylvisaker]

Hello,

Please elaborate on what the issue is. How is the nRF Connect for desktop application working differently from the nRF Connect for smartphone application? What behavior are you observing and how does it diverge from what you would have expected?

Best regards,
Karl

[Ridhi]

when i am enabling notify and trying to write 11 to get data i am not able to get it in nrf app for desktop but in nrf app for mobile it works perfectly fine

[Ridhi]

2000loging 22_11_41.txt

 nrf connect app for mobile

and for 

nrf connect app for desktop

log file of nrf connect app for desktop.txt

[Ridhi]

gentle reminder

[Ridhi]

Karl pls look into

[Karl Ylvisaker]

Hello again, Ridhima

Thank you for your patience with this, and thank you for providing the logs.

From your nRF Connect for desktop log it does not seem that "11" is ever written to the characteristic, like you are doing in the nRF Connect for smartphone logs.
It also seems that you connection times out eventually.

Could you detail when in the logs you attempt to do the write?
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?
What does your peripheral device's log say when this occurs?

Best regards,
Karl

[Ridhi]

My operation is to enable notify, write 11 and get the data 

karl i am following this same process in nrf app for mobi;e in which i get the data but on nrf app for desktop m not able to get it. pls help me

[Ridhi]

Karl kindly help

[Karl Ylvisaker]

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

[Ridhi]

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.

[Karl Ylvisaker]

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

[Ridhi]

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