Recently, Nordic released ncs1.7.0, I wonder if it supports the following features:
1. What is the maximum length of broadcast data for extended advertisement? It cannot exceed 251 bytes in ncs1.6.0.
2. Periodic advertising can't set advertising data via calling bt_le_per_adv_set_data() in ncs1.6.0, is it worked now?
3. Can BLE AoA be used for product?
Hi
1. The same goes for nRFConnect SDK (NCS) v1.7.0 as well. One advertisement can be up t 251 bytes. You can also used chained advertising to reach up to 255 bytes of advertising. We will support larger chained advertising in the future.
2. The bt_le_per_adv_set_data seems to be part of the Zephyr stack, so it should be usable if you're using the Zephyr controller.
3. Yes, the Direction Finding sample projects in NCS are BLE compatible and can be used in products, but you'll likely want to make some changes to the sample projects to fit your product as good as possible.
4. There does not seem to be a limit in the Bluetooth specification to the max number of simultaneous periodic advertising syncs. From what I can tell the restriction may be due to the use of a uint8_t for indices and memory buffer counts. If more than 64 instances are buildable and functional, you are free to increase this to what you'd like.
5. From what I can see both I and Q samples are 12 bits signed. Where do you see that the I samples are 16-bits unsigned in the documentation and 8-bits in NCS?
Best regards,
Simon
Hi
1. The same goes for nRFConnect SDK (NCS) v1.7.0 as well. One advertisement can be up t 251 bytes. You can also used chained advertising to reach up to 255 bytes of advertising. We will support larger chained advertising in the future.
2. The bt_le_per_adv_set_data seems to be part of the Zephyr stack, so it should be usable if you're using the Zephyr controller.
3. Yes, the Direction Finding sample projects in NCS are BLE compatible and can be used in products, but you'll likely want to make some changes to the sample projects to fit your product as good as possible.
4. There does not seem to be a limit in the Bluetooth specification to the max number of simultaneous periodic advertising syncs. From what I can tell the restriction may be due to the use of a uint8_t for indices and memory buffer counts. If more than 64 instances are buildable and functional, you are free to increase this to what you'd like.
5. From what I can see both I and Q samples are 12 bits signed. Where do you see that the I samples are 16-bits unsigned in the documentation and 8-bits in NCS?
Best regards,
Simon
Hi Simonr,
Question-2: I run nrf/samples/bluetooth/sample direction_finding_connectionless_tx, and it use zephyr controller, but it can't set advertising data by calling bt_le_per_adv_set_data. And it's same to run sample zephyr/samples/bluetooth/periodic_adv. Can you help me to confirm the api wether it worked?
Question-5: I'm sorry that I misunderstood the documentation, But it's 8-bits signed in file "zephyr/include/bluetooth/hci.h",
