SDK15.2 Bluetooth core protocol version

RE: SDK15.2 Bluetooth core protocol version

wangshuai — Wed, 09 Jan 2019 09:06:22 GMT

Ok, Thank you very much for your help, which makes me have a deeper understanding of Bluetooth 5.0.

Best regards,

RE: SDK15.2 Bluetooth core protocol version

Edvin — Tue, 08 Jan 2019 14:31:09 GMT

Try the ble_app_uart example. This will by default ask for increased BLE packet size (MTU of 247). Whether or not this is actually accepted depends on what you are connecting to. You can also try to request 2MBPS PHY in the BLE_GAP_EVT_CONNECTED event.

// Add this to the ble_evt_handler->BLE_GAP_EVT_CONNECTED event in the ble_app_uart example in SDK15.2.0:

        case BLE_GAP_EVT_CONNECTED:
            NRF_LOG_INFO("Connected");
            err_code = bsp_indication_set(BSP_INDICATE_CONNECTED);
            APP_ERROR_CHECK(err_code);
            m_conn_handle = p_ble_evt->evt.gap_evt.conn_handle;
            err_code = nrf_ble_qwr_conn_handle_assign(&m_qwr, m_conn_handle);
            APP_ERROR_CHECK(err_code);
        
            ble_gap_phys_t const phys_update = 
            {
                .rx_phys = BLE_GAP_PHY_2MBPS,
                .tx_phys = BLE_GAP_PHY_2MBPS
            };
            err_code = sd_ble_gap_phy_update(p_ble_evt->evt.gap_evt.conn_handle, &phys_update);
            APP_ERROR_CHECK(err_code);
            break;
            
            
// and add this event in the ble_evt_handler as well:
        case BLE_GAP_EVT_PHY_UPDATE:
        {
            uint8_t status = p_ble_evt->evt.gap_evt.params.phy_update.status;
            uint8_t rx_phy = p_ble_evt->evt.gap_evt.params.phy_update.rx_phy;
            uint8_t tx_phy = p_ble_evt->evt.gap_evt.params.phy_update.tx_phy;
            NRF_LOG_DEBUG("PHY updated. Return status: %d", status);
            NRF_LOG_INFO("rx = %d, tx = %d (2 = 2MBPS)", rx_phy, tx_phy);
        }
        break;

Then look in the log (RTT, not UART) for the PHY_UPDATED logging.

Best regards,

Edvin

RE: SDK15.2 Bluetooth core protocol version

wangshuai — Tue, 08 Jan 2019 00:42:36 GMT

Hi Edvin

As you said, nRF52832: Supports High speed and increased packet size.

Please help me how to increase the size of the software package? And how can I see the new features of Bluetooth 5.0?

Best regards,

RE: SDK15.2 Bluetooth core protocol version

Edvin — Mon, 07 Jan 2019 12:38:26 GMT

Bluetooth 5 is basically equal to bluetooth 4, with some additional optional features. You can look at the table about half the way down on this page:

https://www.amarinfotech.com/differences-comparisons-bluetooth-5-vs-4-2.html

(Just a random table I found when I googled Bluetooth 5 vs Bluetooth 4.2).

All of the new features in this table are optional in Bluetooth 5. The main new features are High speed (2MBPS instead of 1MBPS), bluetooth long range (lower throughput, but longer range). Increased message capacity (Longer packets, which is used to increase the throughput). However, it is still possible support only a few of these features, and still call it bluetooth 5.

So I ask again, what Bluetooth 5 features do you want to use? If you don't use any of the features, it is actually bluetooth 4.2, but all of our nRF52 series support at least one bluetooth5 feature. Note that the base of bluetooth 5 is bluetooth4.2. They still use the same communcation protocol, so a bluetooth 5 device can still connect to bluetooth 4.2 devices. The only difference is that you can't use any features unless both devices support it.

nRF52840: Supports long range, High speed and increased packet size

nRF52832: Supports High speed and increased packet size.

nRF52810: Supports High speed.

RE: SDK15.2 Bluetooth core protocol version

wangshuai — Mon, 07 Jan 2019 11:01:01 GMT

Hi Edvin
Thank you for your reply, if we don't need to pay attention to the mobile terminal (nrf Connect) to display Bluetooth 4.1 version or Bluetooth 5.0; then how can we prove that the SDK supports the Bluetooth 5.0 protocol?
Or can we directly observe (test) the core protocol of SDK15.x is Bluetooth 5.0? please help me.

Thank you

Best regards,

RE: SDK15.2 Bluetooth core protocol version

Edvin — Wed, 02 Jan 2019 14:35:52 GMT

Hello,

natersoz is correct! The S132_nrf52_6.1.0_softdevice is Bluetooth5 compliant. I have tested both the iOS version and the Desktop version of nRF Connect, but none of them states the bluetooth version of the advertising device. However, it is not that important.

Bluetooth 5 is just a superset of Bluetooth 4. That is, when you are advertising with bluetooth 5, it looks exactly like a bluetooth 4 advertisement, so there is no way for nRF Connect to know whether it is bluetooth 4 or 5. Basically, all Bluetooth 5 features are optional, and devices may support some of them, without supporting all. This way, Bluetooth 5 devices will still work with bluetooth 4 devices. They will just request certain features after connecting, and if accepted, the connection parameters will change. If it is not accepted/supported, then it will continue to use the old parameters.

So what sort of features from Bluetooth 5 are you considering to use?

Best regards,

Edvin

RE: SDK15.2 Bluetooth core protocol version

wangshuai — Wed, 02 Jan 2019 02:58:55 GMT

Hi natersoz

Thank you for your reply, I have updated nrf connect to version 4.22, unfortunately, when I searched with this version of the app, it still shows "Bluetooth core 4.1"

Thanks

RE: SDK15.2 Bluetooth core protocol version

natersoz — Sat, 29 Dec 2018 22:19:29 GMT

I think the problem is with the tool and not with your advertising, the SDK or the softdevice being 5.0 compliant.

I used the nRF connect application on my iPhone and the UI/display looks significantly different. Perhaps this is a really old version of nRF connect?