Skip to content
BUSMUST
Support中文

BM_CapabilityTypeDef enumeration reference

BMAPI 1.14.0.42 · bm_usb_def.h

Definition

Section titled “Definition”
typedef enum
{
    BM_NONE_CAP = 0x0000U,
    BM_LIN_CAP = 0x0001U,
    BM_CAN_CAP = 0x0002U,
    BM_CAN_FD_CAP = 0x0004U,
    BM_FLEXRAY_CAP = 0x0008U,
    BM_MODBUS_CAP = 0x0010U,
    BM_ETHERNET_CAP = 0x0020U,
    BM_AIO_CAP = 0x0100U,
    BM_DIO_CAP = 0x0200U,
    BM_VIRTUAL_CAP = 0x4000U,
    BM_REMOTE_CAP = 0x8000U,
    BM_ALL_CAP = 0xFFFFU
} BM_CapabilityTypeDef;

Busmust Device capability flags, retrieved when enumerating devices using BM_Enumerate().

Enumeration values

Section titled “Enumeration values”
Name Value expression Description
BM_NONE_CAP 0x0000U No capability
BM_LIN_CAP 0x0001U The device is capable of handling LIN messages
BM_CAN_CAP 0x0002U The device is capable of handling CAN messages
BM_CAN_FD_CAP 0x0004U The device is capable of handling CANFD (and CAN) messages
BM_FLEXRAY_CAP 0x0008U The device is capable of handling FLEXRAY messages
BM_MODBUS_CAP 0x0010U The device is capable of handling MODBUS messages
BM_ETHERNET_CAP 0x0020U The device is capable of handling ETHERNET messages
BM_AIO_CAP 0x0100U The device is capable of analog IO
BM_DIO_CAP 0x0200U The device is capable of digital IO
BM_VIRTUAL_CAP 0x4000U The device is virtual, for simulation purpose
BM_REMOTE_CAP 0x8000U The device is connected remotely and is capable of remote management
BM_ALL_CAP 0xFFFFU Typically used for masking the CAP fields when programming
Section titled “Related functions”

Source: BMAPI 1.14.0.42 released Doxygen documentation. The headers and help files bundled with an installed SDK define its version-specific contract.