This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Connection timeout when handling ADV_REPORT eventa

Hello,

I'm developping an application using softdevice S130 with the nRF51822 evaluation kit. The device has to scan multiple devices, and to save power, I'm storing the BLE_GAP_ADV_REPORT events to handle them when the scan timeout event occurs. At this point, my device connects to devices scanned previously to do something, but I always get a connection timeout event, and the devices never connect. When connecting directly to the devices while handling the BLE_GAP_ADV_REPORT, the devices connect without any problem.

  • I'm assuming the peripheral is still advertising when you try to connect? What advertising interval are you using? What scan paramaters are you using in sd_ble_gap_connect()?

  • Yes, the peripheral advertise continously with an interval of 25ms. For testing, I put and a scan window and scan interval both at the maximum possible values : 0x4000 and a timeout of 10s.

  • What are the laser markings on the nRF51822 chip? What version of SoftDevice and SDK are you using? I tried to connect directly with sd_ble_gap_connect() by hard coding the device address of the peripheral, and it seems to be working. I used the nRF51 DK, S130 1.0.0, and SDK 8.1.0. Would it be possible for your to share your complete project so I could test it here?