Question about Bluetooth Long Range with nRF52840

RE: Question about Bluetooth Long Range with nRF52840

Sigurd — Thu, 14 Feb 2019 12:49:19 GMT

It's because the demo on github uses SDK 15.0

You can download that from here: developer.nordicsemi.com/.../

RE: Question about Bluetooth Long Range with nRF52840

kA_nard — Thu, 14 Feb 2019 12:26:50 GMT

When I checked the SDK, I don't have this folder

\components\libraries\experimental_log\src\nrf_log_backend_rtt.c: No such file or directory

Can you send me the link for this package?

RE: Question about Bluetooth Long Range with nRF52840

kA_nard — Thu, 14 Feb 2019 12:20:36 GMT

Is there any reason why I can't open any c file in both Emproject files except main.c and sdk_config.h with Segger Studio?

RE: Question about Bluetooth Long Range with nRF52840

Sigurd — Thu, 14 Feb 2019 08:50:34 GMT

[quote userid="76579" url="~/f/nordic-q-a/43678/question-about-bluetooth-long-range-with-nrf52840/171030"]And is 0 dBm and 8 dBm is the power output of each board? [/quote]

Yes, that is correct. It's the radio transmit power in dBm.

RE: Question about Bluetooth Long Range with nRF52840

kA_nard — Thu, 14 Feb 2019 08:34:33 GMT

Hi Sigurd,

thanks for the answers, it helped me a lot. And is 0 dBm and 8 dBm is the power output of each board?

RE: Question about Bluetooth Long Range with nRF52840

Sigurd — Thu, 14 Feb 2019 08:28:06 GMT

Hi,

It's using the 125 kbps with 8 symbols per bit

RE: Question about Bluetooth Long Range with nRF52840

kA_nard — Thu, 14 Feb 2019 08:08:00 GMT

Hi,

which type of Coded Phy is the Demo on Github used? Is it transfer the data with rate 125 kbps with 8 symbols per bit or 500 kbps with 2 symbols per bit?

RE: Question about Bluetooth Long Range with nRF52840

Sigurd — Wed, 13 Feb 2019 15:46:36 GMT

[quote userid="76579" url="~/f/nordic-q-a/43678/question-about-bluetooth-long-range-with-nrf52840/170947"]it both showed that I don't have nrf_log_backend_rtt.c, nrf_log_backend_uart.c , nrf_log_backend_serial.c files.[/quote]

The demo was made using SDK 15.0, so if you are using a different version, that could be the reason.

[quote userid="76579" url="~/f/nordic-q-a/43678/question-about-bluetooth-long-range-with-nrf52840/170947"]Can I change this BLE_GAP_PHY_CODED values in BLE_APP_BLINKY in SDK?[/quote]

Yes, that is possible.

[quote userid="76579" url="~/f/nordic-q-a/43678/question-about-bluetooth-long-range-with-nrf52840/170951"]But is there any demo example for 2Mbps?[/quote]

Not on github, but If you want to test the speed with 2Mbps mode, I recommend testing with the ble_app_att_mtu_throughput example in the SDK. See this link. (If you are testing with that example, please set NRF_SDH_BLE_GAP_DATA_LENGTH in sdk_config.h to 251 to achieve max speed)

RE: Question about Bluetooth Long Range with nRF52840

kA_nard — Wed, 13 Feb 2019 15:40:35 GMT

Both works with the hex files. Thanks. But is there any demo example for 2Mbps? In the demo above can change only between Coded PHY and 1 Mbps.

RE: Question about Bluetooth Long Range with nRF52840

kA_nard — Wed, 13 Feb 2019 15:24:40 GMT

Hi Sigurd,

thanks for the code, however when I compile both of the code with Segger Embedded Studio, it both showed that I don't have nrf_log_backend_rtt.c, nrf_log_backend_uart.c , nrf_log_backend_serial.c files.

I want to open the file in the nRF_Log folder but somehow Segger shows that it can't read the file.

Can I change this BLE_GAP_PHY_CODED values in BLE_APP_BLINKY in SDK?

RE: Question about Bluetooth Long Range with nRF52840

Sigurd — Wed, 13 Feb 2019 13:57:36 GMT

Hi,

[quote userid="76579" url="~/f/nordic-q-a/43678/question-about-bluetooth-long-range-with-nrf52840"]When I used this s140, that means all of the examples which I used in nRF_SDK using Bluetooth 5 with Long Range? [/quote]

No. You will need to configure the PHY settings for this. If you are looking at doing extended advertising on Coded PHY(long range) you will need to set the primary_phy to BLE_GAP_PHY_CODED. If you want to connect on Coded PHY, then you need to set the secondary_phy to BLE_GAP_PHY_CODED.

We have a demo example here you can use to test this with.