inconsistent configuration packets are not detected leading to invalid content of data in DPM

2 problems with manual IOPS handling: IOPS always at offset 0; all IOPS are mapped to one byte in DPM.

Configured controller by packets to handle IOPS manually. Used packet PNM_APCTL_CMD_SET_CONFIG_PNM_EXT_REQ:
ulIOPSModeConsumer = 0x00000002; ulIOPSOffsetConsumer = 0x00000020
ulIOPSModeProvider = 0x00000002; ulIOPSOffsetProvider = 0x00000020
Expected 2x IOPS at offset 32 in DPM.

"cifxrepns" with 2x4 bytes in + 2x4 bytes out, starting at offset 0 in DPM.
Started cyclic communication.

DPM input area from offset 0: 80 <7 byte Date from slave>
No IOPS at offset 32.

DPM ouput area at offset 0: first byte is sent as output data and as IOPS to slave for both modules.
IOPS is not taken from offset 32.

Same problem with bitwise IOPS.