Modify ble uart central to show all advertising ble uart peripherals and give option to connect/disconnect to/ from user's choice.

[Robin]

We are using a Nordic 100028 usb dongle programmed as a ble uart central to interface with our ble uart peripheral based boards.  The subject line pretty much says it all.  For production testing we need to be have several boards powered up for test, and then select the board to test, disconnect once testing is initiated, and connect to the next untested board, etc...

Has anybody seen a mod to ble uart central similar to this scenario, or have an idea where one would start to make such a mod?

Thank you all kindly for your continued support of this aged Nordic Neophyte!

Robin@TL

From what I see in the examples, this looks like it may be possible by merging the ble multi central and ble uart central examples, and then changing a few things, no?

[awneil]

Could you not just use nRF Connect for this?

Or the pc-ble-driver - https://github.com/NordicSemiconductor/pc-ble-driver - and write a PC app?

In the embedded code, it's the Advertising Report event which tells you which devices have been "seen" ...

Nordic also have a CLI library:

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v15.0.0%2Fgroup__peer__manager.html

(used in some examples in the SDK)

[Robin]

Hello awneil,

Thanks for the suggestions.

We already have the basic functionality working  in our test code using the resources mentioned, but as you likely know, the the uart central only connects to the first advertiser it finds.  So investing in a new project around either of these option seems overly ambitious. But again, thank you kindly for these suggestions.

Robin@TL

[awneil]

awneil said:

In the embedded code, it's the Advertising Report event which tells you which devices have been "seen"

So that's what you need to see all the units that are advertising.

Then you use that to send a list to you terminal, along with user prompts & instructions

Then you'll need to receive & handle the user responses.

The CLI library would be good for that user interface part.

Or, for an automated test, just iterate through the list ...