Bernd Brandstetter

The type should according to the SDTv2 API however be UINT16 instead of UINT8.

No, that's something different ("Channel monitoring threshold"). Anyway, I just spoke with GH, he will check.

Well, I can't really subscribe to that since BITSET8/16/32/64 are TCN data types, whereas the type ANTIVALENT8 which is supported by TRDP is not. Anyway, it isn't really important but rather a matter of curiosity.

BITSET types

Attribute missing in sdt-parameter element of XML configuration?

At least after a quick look through the files, I don't see that including vos_private.h would be necessary in any of the API header files; I don't know why these inclusions exist at all. vos_private.h mainly specifies platform-dependent structure definitions of the types VOS_SEMA, VOS_MUTEX and VOS_SHRD. But since the VOS API uses hidden definitions it is not necessary that the structure definitions are actually known in the header files.

VOS: Problematic type definitions

VOS: Public API headers include private header file