NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

ovrebekk — Tue, 26 Apr 2022 09:18:48 GMT

Sorry for the slow response, I have been out of office for the last couple of weeks.

If you are using the Zephyr controller you can set the static output power by using the BT_CTLR_TX_PWR configuration settings, as described here.

If you are using the Nordic SoftDevice controller these configurations don't work, and the only way to change the TX power is to do it like in the hci_pwr_ctrl sample I shared earlier.

Best regards
Torbjørn

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

yoyou — Sat, 09 Apr 2022 01:28:11 GMT

Hi,

thanks for reply,

Do you need to set the power statically or dynamically?

i want to set maximum statically only.

Best regards

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

ovrebekk — Fri, 08 Apr 2022 12:25:23 GMT

[quote user="yuyou"]

Create a non-connectable non-scannable DIRECTED advertising set

Only some devices can receive data.

how to do it?

[/quote]

This is not supported in the Bluetooth specification unfortunately. Periodic advertising can not be directed.

[quote user="yuyou"]how to set max TX power and max GIAN for long rang (without nRF21540) ?[/quote]

Do you need to set the power statically or dynamically?

There is a sample in Zephyr showing how you can set the TX power for Bluetooth applications:
https://docs.zephyrproject.org/2.6.0/samples/bluetooth/hci_pwr_ctrl/README.html

Best regards
Torbjørn

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

yoyou — Sat, 02 Apr 2022 06:38:27 GMT

Hi,

thanks for reply, you work carefully!

i delete it and rebuild,it work fine,can recv 202 byte,good!

now,

First question:

i want

Create a non-connectable non-scannable DIRECTED advertising set

Only some devices can receive data.

how to do it?

if Peer address set to not NULL, periodic_sync will can't recv.

maybe periodic_sync side also need set Peer address?

Second question:

how to set max TX power and max GIAN for long rang (without nRF21540) ?

thanks

Best regards

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

ovrebekk — Thu, 31 Mar 2022 11:40:00 GMT

[quote user="yuyou"]

I can try to figure out if there is an easier way to detect duplicate packets on the receive side, so you don't have to do this manually.

that is great!

[/quote]

I checked with the team, and it seems the SoftDevice controller doesn't support this feature unfortunately. In other words it is necessary to check this manually, like I do in the example I sent.

[quote user="yuyou"]but when i add CONFIG_BT_CTLR_ADV_DATA_LEN_MAX=202 two side or only adv side prj.conf bese on your project. sync side can't recv data,maybe I'm missing something?[/quote]

You only have to add this to the advertiser, the scanner will already be set up to support reception of long packets.

Do you see any error messages in the advertiser or scanner that could explain why you don't receive anything?

Best regards
Torbjørn

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

yoyou — Wed, 30 Mar 2022 01:53:53 GMT

Hi,

thank you very much,

avoid packet loss is most important to me.

I can try to figure out if there is an easier way to detect duplicate packets on the receive side, so you don't have to do this manually.

that is great!

If you send a 200 byte payload every 50ms you should get 4 kByte/s easily.

it is so good!

but when i add CONFIG_BT_CTLR_ADV_DATA_LEN_MAX=202 two side or only adv side prj.conf bese on your project. sync side can't recv data,maybe I'm missing something?

Best Regards

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

ovrebekk — Tue, 29 Mar 2022 13:02:58 GMT

[quote user="yuyou"]

If NCS can support each packet sending finished will have a callback(without bt_le_ext_adv_stop and restart),

it is best to bt_le_per_adv_set_data().itcan reduce duplicate data.

[/quote]

What is most important to you? To avoid duplicate data or to avoid packet loss?

If you only send each packet once you will have much higher packet loss than if you send each packet multiple times, and this will surely have a negative impact on the user experience.

I can try to figure out if there is an easier way to detect duplicate packets on the receive side, so you don't have to do this manually.

[quote user="yuyou"]

i've add config to prj.conf

# Allow for large Bluetooth data packets.

CONFIG_BT_L2CAP_TX_MTU=252

CONFIG_BT_BUF_ACL_RX_SIZE=256

if set greater than 30, periodic_sync will can't recv data.

[/quote]

If you increase the CONFIG_BT_CTLR_ADV_DATA_LEN_MAX parameter on the advertiser side you should be able to send longer advertise packets. I tested this myself by setting CONFIG_BT_CTLR_ADV_DATA_LEN_MAX=202, and was able to send 200 byte long packets (200 bytes of data + 2 bytes of manufacturer ID).

If you send a 200 byte payload every 50ms you should get 4 kByte/s easily.

Best regards
Torbjørn

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

yoyou — Fri, 25 Mar 2022 07:03:20 GMT

Hello,

thank you very much, good job,great!

If NCS can support each packet sending finished will have a callback(without bt_le_ext_adv_stop and restart),

it is best to bt_le_per_adv_set_data().itcan reduce duplicate data.

your codes can send 20 valid data per second, send 100byte at a time will be reached 2kByte/s;

but now less than 30 bytes at a time.

i've add config to prj.conf

# Allow for large Bluetooth data packets.

CONFIG_BT_L2CAP_TX_MTU=252

CONFIG_BT_BUF_ACL_RX_SIZE=256

if set greater than 30, periodic_sync will can't recv data.

thanks

Best Regards

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

ovrebekk — Thu, 24 Mar 2022 14:29:44 GMT

In your screenshot you are not using the fastest possible advertising interval. To do that you should configure the periodic advertising parameters using the BT_GAP_PER_ADV_MIN_INTERVAL define, instead of the BT_GAP_PER_ADV_FAST_INT_MIN_1 define.

I tried to get this working myself, and I am able to get a reliable transfer when I update the advertise data every 40ms:

devzone.nordicsemi.com/.../sequence_5F00_test_5F00_per_5F00_adv.zip

The example I shared shows an example of implementing a sequence number, allowing me to identify retransmitted packets easily, and also detect when packets are lost.

Packet loss is not great when transmitting audio, but any wireless application is susceptible to packet loss, and this is something you need to handle somehow in the application.

Best regards
Torbjørn

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

yoyou — Thu, 24 Mar 2022 02:19:01 GMT

Hello,

i've use bt_le_per_adv_set_param(...),

30ms-60ms send one time,it is enough to (2kByte/s);

The key is how to ensure that the packet is modified immediately after each sent.

Otherwise,periodic_sync will recv "123123123789"

it is repeat "123" and lost "456" (audio data can't do that).

Best Regards

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

ovrebekk — Wed, 23 Mar 2022 11:47:01 GMT

1) Possibly the issue is that the advertising interval is too slow, which means you will send the advertise packets at a very slow rate.

To use the quickest possible advertising interval you can change the call to bt_le_per_adv_set_param(..) like this:

err = bt_le_per_adv_set_param(adv, BT_LE_PER_ADV_PARAM(BT_GAP_PER_ADV_MIN_INTERVAL, BT_GAP_PER_ADV_MIN_INTERVAL, BT_LE_PER_ADV_OPT_NONE));
if (err) {
	printk("Failed to set periodic advertising parameters"
	       " (err %d)\n", err);
	return;
}

Could you try this and see if it helps?

2) A second suggestion is to not use the timeout feature, and simply run the bt_le_per_adv_set_data(..) function on a timer at regular intervals to update the data without stopping advertising. Then you will most likely have less gap between sending the old and new packets, and you should get more advertise packets through.

Best regards
Torbjørn

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

yoyou — Wed, 23 Mar 2022 03:04:57 GMT

Hello,

thanks for help,

my project is directed advertising low quality audio（2kByte/s),

One-way communication,no reply. need to send continuous audio data.

i've try 500ms,when timeout less than 500ms periodic_sync can't recv data.

Send data at least 20 times per second, 100 bytes each time,timeout must set 50ms. so

your approach doesn't seem to achieve (2kByte/s),

whether nRF5340DK or nRF52840DK.

devzone.nordicsemi.com/.../adv_5F00_sync_5F00_nRF5340DK_5F00_cpuapp_5F00_config.rar

Best Regards

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

ovrebekk — Tue, 22 Mar 2022 10:20:00 GMT

I made some modifications to the periodic_adv sample in order to do this:

devzone.nordicsemi.com/.../285510_5F00_periodic_5F00_adv.zip

Essentially I configure the sent callback, start advertising with a 3 second timeout, and reconfigure the data every time the sent callback occurs.

Please note that I don't update the advertising directly in the sent callback, instead I use a semaphore to signal to the main loop that the advertising is ready to be restarted.

Best regards
Torbjørn

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

yoyou — Fri, 18 Mar 2022 07:35:51 GMT

Hi,

thanks for reply,

I know how to do the project of ble_app_uart in nRF SDK,

but i do not know how to do in periodic_adv/sync NCS.

i just want to get a callback when send one data finished,

and then immediately modify it to the next data for next advertising.

why is it difficult to achieve? NCS1.9 not support it at all.

Best Regards

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

ovrebekk — Fri, 18 Mar 2022 07:07:52 GMT

Most likely you need to include some kind of sequence counter in the payload, so that the receiver knows when it is receiving a repeated payload, and when it is receiving new data. Then the receiver should be able to assemble the data in the right order, and also recognize if it has lost some packets completely (if the sequence number suddenly increases by more than one).

The sequence number is essentially just a counter that you increment every time you are updating the payload with new data.

Best regards
Torbjørn

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

yoyou — Thu, 17 Mar 2022 03:03:29 GMT

Hi,

my project directed advertising low quality audio（2kByte/s), One-way communication,no reply.

Because need to send continuous audio data, so prepare the next data in sent function.

data must be send one by one,

it means :

send next data at finshed last data sending，

not at timeout.

as:

i'll periodic_adv send "123456789", three bytes are sent at a time.

1.bt_le_per_adv_set_data("123")

2.when "123" send finshed, in sent() function

bt_le_per_adv_set_data("456")

3.when "456" send finshed, in sent() function

bt_le_per_adv_set_data("789")

Make sure periodic_sync receives correctly "123456789".

Error received:

"123123456789"

"456123789"

"789123"

"123789"

You know what I mean?

thanks

Best Regards

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

ovrebekk — Wed, 16 Mar 2022 14:35:18 GMT

The second parameter of the bt_le_ext_adv_start(..) function provides a pointer to a struct of type bt_le_ext_adv_start_param, which allows you to define the timeout either as a time (in 10ms units), or as a number of advertising events:

struct bt_le_ext_adv_start_param {
	/**
	 * @brief Advertiser timeout (N * 10 ms).
	 *
	 * Application will be notified by the advertiser sent callback.
	 * Set to zero for no timeout.
	 *
	 * When using high duty cycle directed connectable advertising then
	 * this parameters must be set to a non-zero value less than or equal
	 * to the maximum of @ref BT_GAP_ADV_HIGH_DUTY_CYCLE_MAX_TIMEOUT.
	 *
	 * If privacy @kconfig{CONFIG_BT_PRIVACY} is enabled then the timeout
	 * must be less than @kconfig{CONFIG_BT_RPA_TIMEOUT}.
	 */
	uint16_t timeout;
	/**
	 * @brief Number of advertising events.
	 *
	 * Application will be notified by the advertiser sent callback.
	 * Set to zero for no limit.
	 */
	uint8_t  num_events;
};

If you create a struct like this, define either the timeout or num_event fields as you want, and provide a pointer to the structure in the bt_le_ext_adv_start(..) call, then the advertising should time out accordingly.

Best regards
Torbjørn

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

yoyou — Tue, 15 Mar 2022 02:11:12 GMT

Hi,

how to configured a timeout？is it.

the starting example code is not perfect, some difficult for novice,

can help debug the basic function:

1. bt_le_per_adv_set_data() in sent function;

prepare the next data at finished last sending；

2. set Peer address, for directed advertising;

for only some one hear;

3. enable LE_CODE for long rang;

for low rate 125kbit/s;

4. periodic_sync can recv directed advertising data;

now it can't recv data.

thanks

Best Regards

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

ovrebekk — Mon, 14 Mar 2022 19:18:32 GMT

Have you configured a timeout on the advertising?

Looking at your code I can't see that you configure a timeout anywhere.

As explained here the sent callback won't be triggered until the advertising times out, which won't happen unless you enable it.

Best regards
Torbjørn

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

yoyou — Fri, 11 Mar 2022 02:03:23 GMT

Hello

thank you very much,

it work,but can't enter sent callback function,no recv callback.

i want change next data in sent callback(when send finished).

#include <bluetooth/bluetooth.h>
#include "common/log.h"

static uint8_t mfg_data[9] = { 0xff, 0xff, 0x00 };
static struct bt_le_ext_adv_cb cb;//call back

static const struct bt_data ad[] = {
	BT_DATA(BT_DATA_MANUFACTURER_DATA, mfg_data, 9 ),
};
static const struct bt_data sd[] = {
	BT_DATA(BT_DATA_MANUFACTURER_DATA, mfg_data, 9 ),
};

void sent(struct bt_le_ext_adv *adv, struct bt_le_ext_adv_sent_info *info)
{
        printk("Sent Data...");
}
void connected(struct bt_le_ext_adv *adv, struct bt_le_ext_adv_connected_info *info)
{
      printk("connected...");
}
void scanned(struct bt_le_ext_adv *adv, struct bt_le_ext_adv_scanned_info *info)
{
      printk("scanned...");
}

void main(void)
{
	struct bt_le_ext_adv *adv;
        cb.sent=sent;//call back
        cb.connected=connected;//call back
        cb.scanned=scanned;//call back
	int err;

	printk("Starting Periodic Advertising Demo\n");

	// Initialize the Bluetooth Subsystem
	err = bt_enable(NULL);
	if (err) {
		printk("Bluetooth init failed (err %d)\n", err);
		return;
	}
 
        // Non-connectable extended advertising with @ref BT_LE_ADV_OPT_USE_NAME BT_LE_ADV_OPT_CODED
       #define BT_LE_EXT_ADV_NCONN_NAME_CODED  BT_LE_ADV_PARAM(BT_LE_ADV_OPT_EXT_ADV | \
						 BT_LE_ADV_OPT_USE_NAME | BT_LE_ADV_OPT_USE_TX_POWER | \
                                                 BT_LE_ADV_OPT_CODED, \
						 BT_GAP_ADV_FAST_INT_MIN_1, \
						 BT_GAP_ADV_FAST_INT_MAX_1, \
						 NULL)   //Peer address, set to NULL for undirected advertising
	// Create a non-connectable non-scannable unDIRECTED advertising set
	err = bt_le_ext_adv_create(BT_LE_EXT_ADV_NCONN_NAME_CODED, &cb, &adv);
	if (err) {
		printk("Failed to create advertising set (err %d)\n", err);
		return;
	}

        #define BT_LE_PER_ADV_P   BT_LE_PER_ADV_PARAM(BT_GAP_PER_ADV_FAST_INT_MIN_1, \
						  BT_GAP_PER_ADV_FAST_INT_MIN_1, \
						  BT_LE_PER_ADV_OPT_USE_TX_POWER)
	// Set periodic advertising parameters
	err = bt_le_per_adv_set_param(adv,BT_LE_PER_ADV_DEFAULT);
	if (err) {
		printk("Failed to set periodic advertising parameters (err %d)\n", err);
		return;
	}
        err = bt_le_ext_adv_set_data(adv,ad, ARRAY_SIZE(ad),sd, ARRAY_SIZE(sd) );
	if (err) {
		printk("Failed to set  bt_le_ext_adv_set_data (err %d)\n", err);
		return;
	}

	// Enable Periodic Advertising
	err = bt_le_per_adv_start(adv);
	if (err) {
		printk("Failed to enable periodic advertising (err %d)\n", err);
		return;
	}

	// Start extended advertising
	err = bt_le_ext_adv_start(adv, BT_LE_EXT_ADV_START_DEFAULT);
	if (err) {
		printk("Failed to start extended advertising (err %d)\n", err);
		return;
	}

    for(int i=0;i<sizeof(mfg_data);i++){mfg_data[i]=0;}
	while (true) 
	{
		k_sleep(K_SECONDS(1));

		mfg_data[2]++;

		printk("Set Periodic Advertising Data...");
		err = bt_le_per_adv_set_data(adv, ad, ARRAY_SIZE(ad));
		if (err) {
			printk("Failed (err %d)\n", err);
			return;
		}
		printk("done.\n");
	}
}

thanks

Best Regards

RE: NCS1.9.0 or NCS1.9.1 periodic_adv work error in nRF5340-DK

ovrebekk — Thu, 10 Mar 2022 15:01:34 GMT

Could you try this sample instead?

devzone.nordicsemi.com/.../periodic_5F00_adv_5F00_5340_5F00_fix.zip

I believe the issue is that extended advertising is not set up properly for the network core, since the standard sample doesn't include the child_image configuration.

Best regards
Torbjørn