This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nrf52 S140 Sdk15 dose not respond to read request

Hi to all,

i am developing a device with NRF52840 DK, in my device i had implemented a service that has some characteristic with noti/read properties. notifications work well with these characteristics and i can send notification to the connected devices through these characteristics, but when central try to read from these characteristics NRF did not respond to these requests and as result the pairs disconnect from each other(i encountered with this problem when i want to connect my device to windows 10). there is any reason that nrf52840 did not respond to read request that was sent to notify/read char?? is there any thing that i must to done to nrf52840 respond to this request?? i am new in BLE and i do not have any idea to how can i solve this problem, in below screen shot you can see the sequence that i described in above:

and also attached BLE DUMP of my device and windwos 10. i am using S140 with SDK15.

1_Connect_Disconnect_Always.pcapng

thanks.

Parents
  • Hi,

     

    I wouldn't think much about that specific frame, as the peripheral has already responded that there's no characteristic on that handle (0x002d).

    Your problem is later on in the connection. The PC rejects your connection parameters in packet #2916, which is likely the reason why the PC also disconnects the link and refuses to re-connect properly. Could you try to adjust your defines "MIN_CONN_INTERVAL" and "MAX_CONN_INTERVAL" to a wider area?

     

    Best regards,

    Håkon

Reply
  • Hi,

     

    I wouldn't think much about that specific frame, as the peripheral has already responded that there's no characteristic on that handle (0x002d).

    Your problem is later on in the connection. The PC rejects your connection parameters in packet #2916, which is likely the reason why the PC also disconnects the link and refuses to re-connect properly. Could you try to adjust your defines "MIN_CONN_INTERVAL" and "MAX_CONN_INTERVAL" to a wider area?

     

    Best regards,

    Håkon

Children
Related