Skip to main content

Central device not automatically connecting to a peripheral device

2 months ago

Central device not automatically connecting to a peripheral device

Posted byvuk102045 points 3 replies
0 upvotes

Hello,

I'm currently on SDK 6.0.14 using DA14585 basic development kit and I'm trying to test the central implementation example along with the proximity reporter example for the peripheral device. Each of the examples is running on a separate development board in debug mode.

The issue that I'm having is getting the two devices to automatically connect. Through the Tera terminal I can see the central device connecting to the peripheral briefly, it will start parsing and filtering through the services but then it disconnects halfway through the process and continues scanning for other devices. Other times I will get an assert error on the central device and it will stop running. If I stop and run the central device 5 to 6 times I can finally get it to connect to the proximity reporter peripheral device. After it connects the first time it seems like it has a much easier time connecting again if I stop and run it during the same debug session.

我没有做出任何改变的例子s. Any suggestions or thoughts on what the issue could be?

accepted answer!

2 months ago

PM_Dialog

Hi vuk1020,

Thanks for coming and posting your question on our new public forum

I am using theDA14585/DA14586/DA14531 Central ImplementationSW Example as provided in Dialog website but I am not able to replicate this behavior. The DA14585 GAP Central Device starts scanning and filters the proximity reporters and connect to the first advertisement seen ( step #2 in the description file ). Both the Central and the Peripheral are running in debug mode, but I cannot observe any kind of disconnection / assertion.

Once the device is disconnecting, is the GAP peripheral still advertising? Can you please share a screenshot with the assertion? Is it in the prox_reporter project?

Thanks, PM_Dialog

2 months ago

vuk1020 45 points

Hello - It turns out the devices are connecting as expected, I had some configuration issues and was making some assumptions about what I was seeing in the Tera terminal that lead me to believe that devices were not connected when in fact they are.

Yes, I'm using the prox_reporter project. The assert error is probably not worth digging into at this point as it only happens if I keep running and stopping the central device multiple times back to back in debug mode. I was only doing this for troubleshooting.

2 months ago

PM_Dialog

Hi vuk1020,

Thanks for letting us know. If you have any follow up question, please raise a new forum thread.

Thanks, PM_Dialog