sl_btmesh_evt_mbt_client_query_block_status_complete#

Querying the current block status is complete.

All active servers have responded to the block status query. If the transfer_complete is non-zero, all blocks of the BLOB have been successfully transmitted and the transfer is complete. The MBT Client state is cleaned up and a new transfer may be started.

If the transfer is not complete, but the block_complete is non-zero, the current block is successfully transmitted and the next block should be started with sl_btmesh_mbt_client_start_block command. If the block_complete is zero, some servers still have chunks missing in the current block. The MBT client starts resending those automatically, requesting the data to send again from the application via sl_btmesh_evt_mbt_client_send_chunk_request events.

Modules#

sl_btmesh_evt_mbt_client_query_block_status_complete_s

Macros#

#define

Identifier of the query_block_status_complete event.

Typedef Documentation#

sl_btmesh_evt_mbt_client_query_block_status_complete_t#

typedef struct sl_btmesh_evt_mbt_client_query_block_status_complete_s sl_btmesh_evt_mbt_client_query_block_status_complete_t

Definition at line 10555 of file /mnt/raid/workspaces/ws.iS2YF8Lrv/overlay/gsdk/protocol/bluetooth/build/native/mesh_app/inc/sl_btmesh_api.h

Macro Definition Documentation#

sl_btmesh_evt_mbt_client_query_block_status_complete_id#

#define sl_btmesh_evt_mbt_client_query_block_status_complete_id
Value:
0x092800a8

Identifier of the query_block_status_complete event.


Definition at line 10543 of file /mnt/raid/workspaces/ws.iS2YF8Lrv/overlay/gsdk/protocol/bluetooth/build/native/mesh_app/inc/sl_btmesh_api.h