This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Do i have to create a extra Instaburst Instance with the API or does it automaticly by building with the ENABLE_INSTABURST in the CMAKE File ?

Im developing a mesh network based on a custom board using the nRF52832. 

I fine with sending some bytes over mesh . But now i want so send more bytes over mesh using Instaburst, but im not sure to realize. 

I found the API and the documentation about instaburst but miss some examples how to do. 

Im working on the Light_switch example and regenerate the example with the ENABLE_INSTABURST Flag in the CMAKE-File and changed the enable define in the config file as well.

When i increase the bytes to send at 380 (ACCESS_MODEL_MAXIMUM_LENGTH) i get the error of invalid length. 

Do i have to create and init the instaburst instance (instabrust_tx and instaburst_rx) ?

Can someone leave a example here using instaburst? 

Hope someone can help here 

Parents Reply Children
  • I also enabled the EXPERIMENTAL_INSTABURST_ENABLED in die Cmake File.

    When i debugg the project i can see the instaburst_init was called as well as instaburst_(tx,rx)_init and enable.

    Is it possible to use the models and instaburst together ?

    How i have to build a message to send data with Instaburst? Can i use the typical access_model_publish from the examples ? 

    Where and How the Code decide which advertiser (extended or normal ble) is used ? 

  • Now im able to send ~377bytes (which is 377 + opcode = 380 bytes ) with the instaburst_tx but when i increase the messagesize, i end in NRF_ERROR_INVALID_LENGTH in check_tx_params as well in segmented_packet_tx where the programm check the maximum package length.

    Do i have to create an extra message type for instaburst? 

  • on the site it says:

    Does this mean MIC SIZE is MIC=(498 - (OPCODE+overhead))? i the length error:9 when choosing a 400byte  transmicsize and sending a 381 byte load.

    This may be entirely wrong, but i understand that regular models should be able to switch to the instaburst feature without change after including the EXPERIMENTAL_INSTABURST_ENABLED in the relevant files. (and ofcourse switching core_tx_adv.c with the instaburst equivalent. ). Is this correct?

Related