multilink uart peripheral - how to choose which to connect

RE: multilink uart peripheral - how to choose which to connect

Jared — Fri, 02 Oct 2020 13:28:23 GMT

[quote user="Avi"]Regarding sending the messages via UART: currently the LOG output is via UART and I can get the output if I connect it to external MCU[/quote]

Yes, you can use NRF_LOG_RAW_HEXDUMP_INFO to only send the raw data.

RE: multilink uart peripheral - how to choose which to connect

Avi — Thu, 01 Oct 2020 09:33:03 GMT

Regarding sending the messages via UART: currently the LOG output is via UART and I can get the output if I connect it to external MCU. Is it the same as adding UART entity into the code?

RE: multilink uart peripheral - how to choose which to connect

Jared — Wed, 30 Sep 2020 07:02:32 GMT

Hi,

Yes, this is possible just set this line to false, and use the SD API function call sd_ble_gap_connect() to connect to the peer.

regards

Jared

RE: multilink uart peripheral - how to choose which to connect

Avi — Tue, 29 Sep 2020 16:42:35 GMT

Thanks - the disconnection indication is working

Instead of the automatic connection after scan, is it possible to connect "manually" with one of the MACID that was detected? (i.e. suppose I have a list of MACIDs which I write to the device via UART)

RE: multilink uart peripheral - how to choose which to connect

Jared — Tue, 29 Sep 2020 12:30:42 GMT

Hi,

This example already use the logger with the UART as backend and prints out what peripheral(connection handle) that disconnected and what reason. If you want to use the UART peripheral to send this information instead for example to a external MCU etc then you would have to first disable the logging over UART, and then add the UART peripheral and driver to the project by for example merging the UART example.

[quote user="Avi"]And prevent any peripheral to connect unless it is within the white list of the central[/quote]

Only a Central can send connection requests, not a peripheral. Which means that the Central decides which peripheral it wants to connect to. See this post regarding whitelist.

Note that all examples on the Nordic-playground repository are un-supported and provided as is.

RE: multilink uart peripheral - how to choose which to connect

Avi — Mon, 28 Sep 2020 13:57:30 GMT

No, I am using nrf52-ble-app-uart-c-multilink-master

This example is in Github and not within the SDK.

I am interested in getting information (via UART), which peripheral has been disconnected

And prevent any peripheral to connect unless it is within the white list of the central

RE: multilink uart peripheral - how to choose which to connect

Jared — Mon, 28 Sep 2020 13:48:04 GMT

Hi,

If you're referring to the ble_app_multilink_central example then it does write what links that is disconnected. It does this at during the DISCONNECTED event here:

case BLE_GAP_EVT_DISCONNECTED:
        {
            NRF_LOG_INFO("LBS central link 0x%x disconnected (reason: 0x%x)",
                         p_gap_evt->conn_handle,
                         p_gap_evt->params.disconnected.reason);

            if (ble_conn_state_central_conn_count() == 0)
            {
                err_code = app_button_disable();
                APP_ERROR_CHECK(err_code);

                // Turn off the LED that indicates the connection.
                bsp_board_led_off(CENTRAL_CONNECTED_LED);
            }

For example:

[quote user=""]

The central will scan the area and list all the peripherals

The central will have a white list (MACID) and connect to each peripheral that is within that list

[/quote]

There is many threads on these topics on the forum, I suggest that you use the search function and see similar threads.

regards

Jared