Bluetooth low energy - All Comments

RE: Merging two BLE examples together

user115692 — Thu, 09 Jun 2022 10:23:43 GMT

I use those settings to test the UART RX and TX maximum data size with nRF Connect. In TX is fine. But in RX is only 182 bytes. I merge ble_app_hrs and ble_app_uart. Does ble_app_hrs has limitation?

RE: Bluetooth low energy central tutorial

user113482 — Wed, 01 Jun 2022 09:52:17 GMT

is there any update for this tutorial, lots of links are missing for now.

RE: Bluetooth low energy Advertising, a beginner's tutorial

user115239 — Tue, 10 May 2022 05:32:59 GMT

Hi
I want to advertising with NRF52840 DK, I do tutorial explanation and for PCA10056\S140 after load main.c it compile without any error and warning but I cant find any device with "Helloworld" name on bluetooth mobile phone .
for pca10040\s132 I have error: #5: cannot open source input file "nrf52_erratas.h": No such file or directory
any help with this issue would be a massive help
Thanks in advace.

RE: How to update advertising data dynamically using BLE Advertising library

user114984 — Wed, 06 Apr 2022 15:39:14 GMT

Answered my own question now. I believe it will cope with the situation I was looking at. I needed to reset the adv_data.len to it's maximum before calling adv_data_encode

RE: How to update advertising data dynamically using BLE Advertising library

user114984 — Mon, 04 Apr 2022 10:14:13 GMT

Hi Karl, great tutorial. I have a question about changing the manufaturer specific data length. In my application I want to increase the length of the manufacturer specific data field by 2 bytes after a certain point in time. My advertising data consistes of Flags, a dynamically changing manufacturer specific data field and a name field. The maximum length of all this is less than 31 bytes. I've found that when increasing the length of the manufacturer specific data and using ble_advdata_encode, the manufaturer data is handled correctly but the total length of the advertising data doesn't increase, leading to a truncated name field. I am passing a length of 31 bytes with my ble_gap_adv_data_t signal (unless that is being changed by another process I don't see) Would the Update_advertising_data handle this case
Thanks
Mike

RE: Bluetooth low energy Advertising, a beginner's tutorial

user97666 — Tue, 01 Mar 2022 14:25:04 GMT

Hello,

This is very informative. Thank you so much for this. I am able to set custom data to advertising but is it possible to set this data in custom type or any frame type that I wish to advertise? For more information about my question click here.

Regards,

Neeraj Dhekale

RE: How to update advertising data dynamically using BLE Advertising library

user113739 — Wed, 23 Feb 2022 07:30:42 GMT

hello everyone,

i want to use this example for 15.3 SDK but its not working so anybody have any suggestion please let me know.

thanking you.

RE: How to update advertising data dynamically using BLE Advertising library

user113598 — Wed, 16 Feb 2022 11:10:35 GMT

Finally I have managed to build the solution with correct paths to all logging functions. But same as the defualt template app it ends in the "NRF_BREAKPOINT_COND" right after starting up. Please would you be so kind and try to help a little. The immediate failure of the code is same also for the template ble app.

RE: How to update advertising data dynamically using BLE Advertising library

user113598 — Wed, 16 Feb 2022 09:14:11 GMT

Dear friends, I downloaded fresh SDK 17.0.2 and copy your linked example to the examples. I am using SES, I am not able to compile the project. Other examples worked just fine. Your linked example have problems with paths to logging things and even I tried to fix it it started to have problem to found files like sdk_common.h and I am not able to fix. Would be possible to fix the linked example so it will work just OK like your other examples among downloaded SDK. Or any other advice will be much helpful for me.

RE: How to update advertising data dynamically using BLE Advertising library

user111673 — Thu, 10 Feb 2022 18:16:37 GMT

This is a good example of a project that I am currently working on. I could use some clarifications in the function "adv_data_update_timer_handler." 1. You define PAYLOAD_SIZE as 1 but there are 6 uint8_t types of data in the actual list. Is this a typo? 2. There is a static variable defined payload_index in the function and initialized to zero. Later in the function you test that variable against a defined TOP_INDEX which equals 5. Can you explain how the payload_index will ever increment to the TOP_INDEX level because of being set to zero upon entry into the function?

RE: Bluetooth low energy Services, a beginner's tutorial

user111909 — Thu, 16 Dec 2021 12:44:12 GMT

Hi Guys,

Can someone explain, from where the variable BLE_UUID_OUR_SERVICE came? where it is defined or what is the value on this program?

line:   service_uuid.uuid = BLE_UUID_OUR_SERVICE;

Thanks for your answer!

With Regards,
Sreejith

RE: Bluetooth low energy Services, a beginner's tutorial

user102920 — Thu, 11 Nov 2021 06:40:30 GMT

Its really helpfull/

RE: How to update advertising data dynamically using BLE Advertising library

user16216 — Wed, 03 Nov 2021 20:16:57 GMT

Hi Karl,

after having stumbled over the implementation for updating advertising information in SDK 15.3 I was glad to find this explanation and demonstration for the new SDK 16.0 implementation of ble_advertising_advdata_update. That's exactly what I need.

Before adding this to our project I downloaded your example code to test it on a nRF52840 PDK and nRF-Connect on my Android smartphone. (Android 10, also tested with another phone with Android 8).
I placed the sample code into the examples folder of a Android 17.0.2 SDK, and I'm using SES (Segger Studio) v 5.64

My first impression was that it did not work at all, because I was looking for the original advertising name "Nordic_Template", but did not find it in nrfConnect. But after making some minor changes for seeing NRF_LOG messages with RTTview and a bit of debugging I found out the reason. The advertised Device name is correct at startup, i.e. after a Reset ( to be sure, I do not only test this after programming with SES, but explicitly issuing a Reset with SES.
Whenever the Reset is issued, nRFConnecgt will show the correct Device name Nordic_Template. As soon as the timer expires and the first ble_advertising_advdata_update is invoked, the name in nRFConnect is "lost" and replaced by the typical "N/A (Nordic)" display.
Note that the dynamic update of the ManufacturerSpecific Data works correctly as expected, i.e. for each timer event nRFConnect will show the updated information. This is good, but not at the cost of the wrong / missing device name during advertising.

Before I start debugging this in detail myself, I would like to know whether it is expected behavior for this example to loose the device name ??
In my application I definitely need correct advertising for all the information, including the device name.

I add two screen shots of nRFConnect, the first one shows the "correct" information after a Reset of the nRF52840, the second one shows the "wrong" information after the first timer update with ble_advertising_advdata_update is excecuted. This remains wrong for all subsequent timer events.
Note that I changed the name from Nordic_Template to DX-1234.

RE: MIDI over Bluetooth LE

user108847 — Fri, 01 Oct 2021 14:06:00 GMT

Hello Håvard, and thanks for this MIDI example!
I've got a question regarding the SysEx package being sent; when I've connected the nRF52840 DK to my nRF Connect app on the iPhone and I press button 4 (SysEx package) I receive more bytes than I expect from a SysEx package.
Here is an example of what I receive = (0x89-A7-F0-01-02-03-04-05-06-07-08-09-A7-F7).
Shouldn't I only be receiving (F0-01-02-03-04-05-06-07-08-09-F7) in order for it to be a protocol-correct SysEx package, with F0 and F7 being start and stop commands?
Kind regards,

RE: How to update advertising data dynamically using BLE Advertising library

user8498 — Tue, 14 Sep 2021 10:27:31 GMT

Hi Karl

Having looked through the many posts where everything was going wrong with advertising update, your demo worked perfectly first time. I had been using the stop/update/start method for an update to live data within the advertising and scan response packets, but this method lets me use the new advertising module sequencing and have live updates without compromising the timing!

Excellent example
Many thanks

Ken