This is the documentation for the latest (main) development branch of Zephyr. If you are looking for the documentation of previous releases, use the drop-down menu on the left and select the desired version.

CONFIG_BT_MESH_TX_SEG_MAX

Maximum number of segments in outgoing messages

Type: int

Help

Maximum number of segments supported for outgoing messages.
This value should typically be fine-tuned based on what
models the local node supports, i.e. what's the largest
message payload that the node needs to be able to send.
This value affects memory consumption, which is why the
default is lower than the maximum that the specification
would allow (32 segments).

The maximum outgoing SDU size is 12 times this number (out of
which 4 or 8 bytes is used for the Transport Layer MIC). For
example, 5 segments means the maximum SDU size is 60 bytes,
which leaves 56 bytes for application layer data using a
4-byte MIC and 52 bytes using an 8-byte MIC.

Direct dependencies

BT_MESH && BT

(Includes any dependencies from ifs and menus.)

Default

  • 3

Kconfig definition

At subsys/bluetooth/mesh/Kconfig:384

Included via Kconfig:8Kconfig.zephyr:42subsys/Kconfig:9subsys/bluetooth/Kconfig:332

Menu path: (Top) → Sub Systems and OS Services → Bluetooth → Bluetooth mesh support

config BT_MESH_TX_SEG_MAX
    int "Maximum number of segments in outgoing messages"
    range 2 32
    default 3
    depends on BT_MESH && BT
    help
      Maximum number of segments supported for outgoing messages.
      This value should typically be fine-tuned based on what
      models the local node supports, i.e. what's the largest
      message payload that the node needs to be able to send.
      This value affects memory consumption, which is why the
      default is lower than the maximum that the specification
      would allow (32 segments).

      The maximum outgoing SDU size is 12 times this number (out of
      which 4 or 8 bytes is used for the Transport Layer MIC). For
      example, 5 segments means the maximum SDU size is 60 bytes,
      which leaves 56 bytes for application layer data using a
      4-byte MIC and 52 bytes using an 8-byte MIC.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)