• State Verified Answer
  • Replies 8 replies
  • Subscribers 63 subscribers
  • Views 3265 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 127320
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

I am having a problem on the second connect after bonding to a bluez 5.43 central

jlarsen

I can connect/pair/bond to the nrfConnect app and disconnect then reconnect just fine. When I try to do the same to a central running on arm bluez 5.43, the second and subsequent connections timeout after about 30 seconds and the peripheral gets a BLE_GATTC_EVT_TIMEOUT and disconnects.

I have wireshark cptures of the nrf Connect connections and the failing connection to my central.

1st and 2nd connections working as expected rfconnect.pcapng

1st connection mycentral.pcapng

2nd connection (disconnected by peripheral after 30 seconds) mycentral2.pcapng

Parents
  • 0

    softdevice = s132 chip = nRF52

    ble_app_proximity does the same thing in that it disconnects after 30 seconds. The connection parameters seem to work better in the proximity app. I actually see them set on the central side.

    I have been using the nRF52 board to sniff. Theres are some issues doing this. I will post the sniffer results once I get a board that that the sniffer code works on.

    I am not sure if we do write requests but we do attempt to change the MTU

Reply
  • 0

    softdevice = s132 chip = nRF52

    ble_app_proximity does the same thing in that it disconnects after 30 seconds. The connection parameters seem to work better in the proximity app. I actually see them set on the central side.

    I have been using the nRF52 board to sniff. Theres are some issues doing this. I will post the sniffer results once I get a board that that the sniffer code works on.

    I am not sure if we do write requests but we do attempt to change the MTU

Children
No Data
Related