• State Not Answered
  • Replies 3 replies
  • Subscribers 69 subscribers
  • Views 74 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 338410
Options

Instaburst support in nRF Connect ble mesh?

Mandeep

HI,

I am developing a ble mesh application on SDK 17.2, I enable Instaburst for support long mesh message(more than 300 byte), it worked well.

Now I changed to the nRF Connect SDK v2.6 and rewritten the mesh model, still need long messages support. How can I enable the Instaburst for ble mesh? If the nRF Connect SDK does not support Instaburst,foced to use SAR, and compared to Instaburst, is less stable or slower ?

And other way in nRF Connect SDK support long messages for ble mesh?

Parents
  • 0

    Hi,

    Nordic Advertiser Extensions (Instaburst) feature is not available in NCS.

    The discussion in this ticket might be relevant to your requirements: BLE MESH DEV

  • 0 in reply to Naeem Maroof

    I have spent  lot of work on my ble mesh application, with thousands of devices running in my project. Most of their based on long message support (Instaburst). Does this mean I cannot continue my project with NCS? If disregard the Bluetooth Mesh specification, is there a way to support long messages ? I know the SAR, but it incompatible with instaburst.

  • 0 in reply to Mandeep

    Hi Mandeep,

    I wonder if there is a misunderstanding here. The Instaburst feature doesn't provide support for long messages. It changes the packet bearer from legacy BLE advertiser to a proprietary implementation somewhat based on existing BLE (not Mesh) features.

    Mandeep said:
    I have spent  lot of work on my ble mesh application, with thousands of devices running in my project. Most of their based on long message support (Instaburst). Does this mean I cannot continue my project with NCS?

    But if you have thousands of deployed devices running Instaburst, then yes, that means that you cannot add more devices working in NCS.

    Mandeep said:
    If disregard the Bluetooth Mesh specification, is there a way to support long messages ?

    If you disregard the Bluetooth Mesh specification, then you can technically reimplement the Instaburst feature. I don't think it is going to be trivial and do not recommend this approach.

    I see in the opening post you have this concern:

    SAR, and compared to Instaburst, is less stable or slower ?

    I haven't looked into speed comparison between SAR and Instaburst, but I can say that SAR wouldn't be less stable.

    Hieu

Reply
  • 0 in reply to Mandeep

    Hi Mandeep,

    I wonder if there is a misunderstanding here. The Instaburst feature doesn't provide support for long messages. It changes the packet bearer from legacy BLE advertiser to a proprietary implementation somewhat based on existing BLE (not Mesh) features.

    Mandeep said:
    I have spent  lot of work on my ble mesh application, with thousands of devices running in my project. Most of their based on long message support (Instaburst). Does this mean I cannot continue my project with NCS?

    But if you have thousands of deployed devices running Instaburst, then yes, that means that you cannot add more devices working in NCS.

    Mandeep said:
    If disregard the Bluetooth Mesh specification, is there a way to support long messages ?

    If you disregard the Bluetooth Mesh specification, then you can technically reimplement the Instaburst feature. I don't think it is going to be trivial and do not recommend this approach.

    I see in the opening post you have this concern:

    SAR, and compared to Instaburst, is less stable or slower ?

    I haven't looked into speed comparison between SAR and Instaburst, but I can say that SAR wouldn't be less stable.

    Hieu

Children
No Data
Related