Hardcoded connection

RE: Hardcoded connection

Joakim Jakobsen — Thu, 02 Nov 2023 14:15:10 GMT

If you have any further questions, please let me know.

You are also welcome to open a new ticket if you have any more questions in the future.

Br,
Joakim

RE: Hardcoded connection

Joakim Jakobsen — Thu, 02 Nov 2023 11:23:05 GMT

Also, as the nRF5 SDK is in maintenance mode, support for new features beyond Bluetooth LE 5 will not be added to the nRF5 SDK. For instance, Bluetooth Direction Finding, Bluetooth LE Audio, and so forth are not supported and will not be supported in the nRF5 SDK.

I would suggest looking at the nRF Connect SDK.

Br,
Joakim

RE: Hardcoded connection

StanislavDimitrov — Thu, 02 Nov 2023 11:18:05 GMT

fair enough

RE: Hardcoded connection

Joakim Jakobsen — Thu, 02 Nov 2023 11:16:18 GMT

[quote user="StanislavDimitrov"]By the way it is interesting that multi peripheral example is called experimenta[/quote]

As Simon wrote in this previous ticket:

The experimental libraries have undergone less testing, and have usually been out for a shorter amount of time, so the chance of discovering bugs will be larger although none of the libraries should be assumed to be completely free of bugs.

All libraries and examples in the SDK, both experimental and not, are provided "as is", so in the end, it is up to you to test your application sufficiently and confirm that it meets your requirements.

RE: Hardcoded connection

StanislavDimitrov — Thu, 02 Nov 2023 10:34:47 GMT

Thanks all clear. By the way it is interesting that multi peripheral example is called experimental :)

RE: Hardcoded connection

Joakim Jakobsen — Thu, 02 Nov 2023 07:24:31 GMT

Yes, that is possible.

We have the BLE Multiperipheral sample in the SDK that demonstrates how one Peripheral can connect to several Centrals.

_____________

Br,
Joakim

RE: Hardcoded connection

StanislavDimitrov — Thu, 02 Nov 2023 06:46:12 GMT

Thanks. Is this also mean that one peripheral can establish a connection with two or more central simultaneously?

RE: Hardcoded connection

Joakim Jakobsen — Wed, 01 Nov 2023 11:21:22 GMT

Thanks.

I would highly recommend using the nRF Connect SDK for new designs and development.

The nRF5 SDK is currently in maintenance mode (ref: nRF Connect SDK and nRF5 SDK statement )

If you have any trouble using the NCS, I would recommend that you open a new ticket explaining what you have problems with. We will do our best to assist you.

_________

What you describe should be achievable. You can add a scan filter so that your device only connects to certain devices that match the filter, either by name, address or UUID.

How to use filters is demonstrated in the samples in the SDK. You can also add your devices to the whitelist. There are several other configurations you can look at i.e defining the maximum number of connections that is allowed etc.
I would suggest that you take a look at the samples available in the SDK and use the documentation to explore the different options you have.

Br,
Joakim

RE: Hardcoded connection

StanislavDimitrov — Wed, 01 Nov 2023 05:50:27 GMT

I am using nRF5_SDK_17.0.2 and nRF52832. I tried the Zephyr framework, but there are some issues with the UART, and no problems so far with nRF5_SDK_17.0.2.

RE: Hardcoded connection

Joakim Jakobsen — Tue, 31 Oct 2023 22:12:40 GMT

That should be possible.

Could you share information about which SDK, device etc. you are working with here?

Br,
Joakim

RE: Hardcoded connection

StanislavDimitrov — Mon, 30 Oct 2023 03:33:01 GMT

Thank you, Joakim.

Currently, we want to hardcore (in the firmware as configuration both in the peripheral and central devices) that peripheral P will connect only to Central C1, Central C2, and Central C3 (C2 and/or C3 may be not present in some cases). We do not want any interaction by the user (pressing the button, waiting for pairing), just when peripheral P and Central C1 are powered up, they establish a connection, and no more connections (except C2 and C3 if powered up) are allowed.

I assume this is possible if the peripheral serves as a beacon, right? How to select (filter) data coming from a specific beacon then? Also assuring the "freshnes" of the data received from the beacon can be a challenge.

Or do we need to switch the option - one Central device and three peripherals?

RE: Hardcoded connection

Joakim Jakobsen — Sun, 29 Oct 2023 20:53:58 GMT

Hi.

Maybe you could elaborate a little bit on your usecase here?

But after you connect to your preferred device, you don't have to start scanning for more devices. You can choose only to allow 1 connection. You can add your device to a whitelist etc.

If you share some more information about your application or requirements, we can discuss further what could be the best way for you to solve this.

Br,
Joakim