BLE mesh custom model message receive interval

Hi, 

I am using two Nordic boards running custom client and server models.
The board running custom client model is sending 138bytes of data, which is being received by the board running the custom server model.

I calculated the time interval between reception of each 138byte packet on the server model, and found that it is 1.5 secs.

This is too much and I want to reduce this to be under 0.5 secs.

Kindly suggest how I can send and receive data packets via BLE-Mesh faster & in a more optimal way.

If you can suggest a sample program or example, it would be better.

Thanks

Parents
  • Hi,

    Andreas asked me to have a look at this while he is out-of-office.

    As Andreas has already mentioned, CONFIG_BT_MESH_ADV_EXT is a config that will improve throughput. It enables multiple advertising sets, which increases throughput (and also gives better control of number of advertisements sent.) The drawback is it is not yet considered production quality for Bluetooth mesh, so it is use at your own risk.

    Regarding the 50 packets per second, testing has shown that number to be 20, not 50, for each advertiser. (Might have  been a confusion there about packets/second vs ms/packet.) Without ADV_EXT you get a single advertiser. The throughput should still be higher than once every 1.5 seconds for a single advertiser.

    Are you able to reproduce the behavior by creating a minimal example? For highlighting and reproducing the issue, without having to share customer code.

    Regards,
    Terje

Reply
  • Hi,

    Andreas asked me to have a look at this while he is out-of-office.

    As Andreas has already mentioned, CONFIG_BT_MESH_ADV_EXT is a config that will improve throughput. It enables multiple advertising sets, which increases throughput (and also gives better control of number of advertisements sent.) The drawback is it is not yet considered production quality for Bluetooth mesh, so it is use at your own risk.

    Regarding the 50 packets per second, testing has shown that number to be 20, not 50, for each advertiser. (Might have  been a confusion there about packets/second vs ms/packet.) Without ADV_EXT you get a single advertiser. The throughput should still be higher than once every 1.5 seconds for a single advertiser.

    Are you able to reproduce the behavior by creating a minimal example? For highlighting and reproducing the issue, without having to share customer code.

    Regards,
    Terje

Children
No Data
Related