Details
Description
Seen with V3.2.11.0:
When creating a sub object with ODV3_CREATE_SUBOBJECT_REQ and
usDatatype = ECAT_OD_DTYPE_UNSIGNED32
bValueInfo = ODV3_VALUE_INFO_VIRTUAL
bIndicationFlags = 0
(and no indication handling implemented)
ODV3 delivers "eafbfffa" as value of sub object. Normally bIndicationFlags would have to be set != 0 when using bValueInfo = ODV3_VALUE_INFO_VIRTUAL
but the case "bIndicationFlags = 0" has to be safe also.