Instaburst example for nrf 2.30 sdk

RE: Instaburst example for nrf 2.30 sdk

tesc — Thu, 01 Jun 2023 14:35:41 GMT

Hi,

[quote user="yogeshiggalore"]need your help in sending a payload without multiple segments.[/quote]

This is not possible in Bluetooth mesh.

It was possible as a proprietary change to the bearer layer for the mesh stack in nRF5 SDK. It then became non-standard and non-qualifiable. This is not an option in nRF Connect SDK.

What do you need unsegmented messages of this size for? What is the reason for not wanting segments? There may be other options...

Regards,
Terje

RE: Instaburst example for nrf 2.30 sdk

yogeshiggalore — Thu, 01 Jun 2023 09:18:34 GMT

Hi tesc,

nrf device is working fine with 248 payloads, no issue I have in that.

need your help in sending a payload without multiple segments.

RE: Instaburst example for nrf 2.30 sdk

tesc — Tue, 30 May 2023 09:02:27 GMT

Hi,

1. This sounds correct, but please note that one mesh node can have several elements. If the node has multiple elements then each element has its own address. In that case the address for the next node should be higher.

2. If you connect directly to node 4 over a BLE connection, then messages sent to this node (using the unicast address) will not be sent over the network using the advertising bearer. It will only be sent using the direct BLE connection. I must admit I am not quite sure how the details works out regarding segmentation and reassembly (SAR) over the GATT bearer (the direct BLE connection) compared to normal mesh traffic using the advertiser bearer. The main point, however, is this is supposed to be handled by the stack. From the application layer, all you should need to care about is to send a message (within the maximum message size.)

Are there any message lengths that works? For instance, 5 bytes? 8 bytes? 11 bytes? 50 bytes? 200 bytes?

What example (if any) have you based your application off of?

Regards,
Terje

RE: Instaburst example for nrf 2.30 sdk

yogeshiggalore — Sat, 27 May 2023 06:41:55 GMT

I have edited nrf mesh app to send 248 bytes of payload,

these are the following things I did, correct me, if my understanding is wrong.

1. Provisioned 3 mesh devices to a network and assigned addresses 2, 3, and 4.

2. If I need to send 248 bytes of payload to device 4.

a. connected to device 4 in app.

b. if the connection success then in the UART console, nrf52840 says the ble connected.

c. sending 248 bytes of payload. internally it is converted into 22 segments and sent one by one.

d. I am sure communication is not happening in the adv channel(37,38,39).

If the above points are correct, then why can't I send 248 bytes at a time if I am not using advertising channels for communications?

RE: Instaburst example for nrf 2.30 sdk

tesc — Fri, 26 May 2023 12:23:57 GMT

Hi,

No, 248 bytes cannot be sent in a single packet in Bluetooth mesh in nRF Connect SDK, no.

A mesh message can have that size, and such a message will typically be split into 22 segments, as per the Bluetooth mesh specification. On the application level this will look like one message with one payload. On the deeper levels and over-the-air it will be sent as segments.

For suggesting a workaround or better suited technology, can you elaborate on the "single packet requirement"? What is the reason/rationale for this requirement, and may there be other ways to achieve the underlying goals?

Regards,
Terje

RE: Instaburst example for nrf 2.30 sdk

yogeshiggalore — Fri, 26 May 2023 03:21:08 GMT

Thanks tesc for clarification. the requirement is needed to send ~248 bytes of payload in a single packet instead of doing multiple segments. any option we have in nrf2.3.0?

RE: Instaburst example for nrf 2.30 sdk

tesc — Thu, 25 May 2023 11:46:16 GMT

Hi,

Nordic Advertiser Extensions (Instaburst) is a proprietary replacement for the BLE Advertiser bearer. It does not adhere to the Bluetooth Mesh specification, and it is not available in nRF Connect SDK.

Instaburst was a proprietary feature we added to our mesh stack in nRF5 SDK for Mesh. Please note that it was not qualifiable, and the feature did not have the same test coverage as the proper Bluetooth mesh stack in nRF5 SDK for Mesh.

nRF5 SDK for Mesh is now in maintenance mode and not recommended for new projects. For new projects you should use nRF Connect SDK instead. Please see our nRF Connect SDK and nRF5 SDK statement.

Regards,
Terje

RE: Instaburst example for nrf 2.30 sdk

yogeshiggalore — Wed, 24 May 2023 13:29:21 GMT

sorry nrf 2.3.0