ble beacon over energy harvesting

RE: ble beacon over energy harvesting

Senchoi — Thu, 22 Dec 2022 06:48:37 GMT

It's natural to get very complicated as you try to modify the given code. Usually you should work on top of nordic's sdk layer. But there's a good chance you have to modify things that people normally shouldn't to implement what you want.

removing such code is not going to help. if you're using Segger Embedded Studio you can right click each code and select Go To Definition to get deeper into the sdk.

In my brief research, it seems you have to insert sd_ble_gap_adv_stop(uint8_t adv_handle) function somewhere in the code to stop advertising immediately after one adv event.

Or there may be a single-shot mode for ble_advertising_init.

Or try setting max_adv_evts to 1 for m_adv_params. This may be the single shot mode.

Also since it says 100ms is the minimum value. You may be violating the standard. In that case things can get even more complicated to implement. It may not be even possible with Nordic's sdk.

I wish you good luck. It always looks impossible before you actually make it happen.

RE: ble beacon over energy harvesting

pail — Thu, 22 Dec 2022 06:12:27 GMT

[quote userid="103143" url="~/f/nordic-q-a/95061/ble-beacon-over-energy-harvesting/401674"]Would you try disabling timing interval mechanism and sending the data once and finish the program on your device?[/quote]

would you explain about that?

I've been working on it since yesterday but... nothing changes.

what I do is

1) change the value of NON_CONNECTABLE_ADV_INTERVAL MSEC_TO_UNITS(160, UNIT_0_625_MS)

What I've checked here is that the smaller the value, the more sensitive the reaction is, and the bigger the value, the less effective it is.

1)-1 and I remove that code

: #define NON_CONNECTABLE_ADV_INTERVAL MSEC_TO_UNITS(160, UNIT_0_625_MS)

in this case, I can debug but nothing happens.

Everything I've done doesn't work...

RE: ble beacon over energy harvesting

Senchoi — Wed, 21 Dec 2022 10:53:38 GMT

Then I’m guessing it’s the lack of supply for the peak current. When I measure BLE device ppk2, my case nRF52840 dongle, peak current fluctuates a little. In range 12 to 18mA. If you’re sure you’re supplying enough power, you should look deeper into softdevice whether the timer is getting cut off because the supply lasts only 24. Since the interval looks like 160ms. The timer value is trying to meet the compare value which results in not sending the data. Would you try disabling timing interval mechanism and sending the data once and finish the program on your device?

RE: ble beacon over energy harvesting

pail — Wed, 21 Dec 2022 07:46:05 GMT

hi Senchoi

thank you for reply my ticket.

I'm sorry to say that There was something I forgot to write it down in this ticket.

in my project, beacon and central device don't have to pair and bond each other.

because my beacon only send "advertising data' to central device.

and whenever central device receive "advertising data", central device do something (like turning on the led on central board)

there is no pairing or bonding process.

[quote userid="103143" url="~/f/nordic-q-a/95061/ble-beacon-over-energy-harvesting/401623"]

as the code shows /**< The advertising interval for non-connectable advertisement (100 ms). This value can vary between 100ms to 10.24s). */

There is a minimum time for ble pairs to be connected. I believe 24ms is not enough time.

[/quote]

As far as I understand, "the advertising interval" refers to the period during which the peripheral device (in my case, beacon) sends the advertising data once and then the next advertising data.

and whenever beacon turns on, it sends the advertising data right away.

so in my case, I only need the first advertising adta. I dont need the advertising data to be sent after "the advertising interval"

RE: ble beacon over energy harvesting

Senchoi — Wed, 21 Dec 2022 04:41:10 GMT

as the code shows /**< The advertising interval for non-connectable advertisement (100 ms). This value can vary between 100ms to 10.24s). */

There is a minimum time for ble pairs to be connected. I believe 24ms is not enough time. Also you need to make sure maximum of at least 15mA is able to flow that's the peak current when adv event or conn event happens.