Dear Nordic:
My use scenario may be a little complex. I try to describe it clearly.
A device developed on NRF52832/S332/SDK13, acts as a combination of Bluetooth central, peripheral, ANT+ display.
What i expect is: when it starts up, it tries to connect a target Ble sensor with known peer address, it also starts Ble scan and ant+ search, and sends the realtime results to PC by Nordic Nus notification.
Without connection behavior, it works well. But when I added the connection operation today, the peripheral role (nus) quickly disconnects. The reason shows 0x08 BLE_HCI_CONNECTION_TIMEOUT.
By the way, i use extended packet in nus service which support MTU 247. I checked all the parameters configured for BLE initialization, and found nothing to solve my problem.
My use scenario may be a little complex. I try to describe it clearly.
A device developed on NRF52832/S332/SDK13, acts as a combination of Bluetooth central, peripheral, ANT+ display.
What i expect is: when it starts up, it tries to connect a target Ble sensor with known peer address, it also starts Ble scan and ant+ search, and sends the realtime results to PC by Nordic Nus notification.
Without connection behavior, it works well. But when I added the connection operation today, the peripheral role (nus) quickly disconnects. The reason shows 0x08 BLE_HCI_CONNECTION_TIMEOUT.
By the way, i use extended packet in nus service which support MTU 247. I checked all the parameters configured for BLE initialization, and found nothing to solve my problem.
Does the environment i am using support my scenario? It's a prototype of a bike computer. Please give me some advise to check my issue or how to accomplish the scenario with better solution.
Thanks very much.
Thanks very much.
