EIP_APS_SET_CONFIGURATION_PARAMETERS_CNF is always sent back with size zero, should contain applied configuration (V1) according to manual and packet definition

EIP_APS_SET_CONFIGURATION_PARAMETERS_REQ has the following confirmation packet defined according to manual and header files:

typedef __PACKED_PRE struct __PACKED_POST EIP_APS_SET_CONFIGURATION_PARAMETERS_CNF_Ttag
{
  uint32_t  ulPacketVersion;  /*!< Version related to the following union entry */

  __PACKED_PRE union __PACKED_POST
  {
    EIP_APS_CONFIGURATION_PARAMETER_SET_V1_T tV1;
  } unConfig;

} EIP_APS_SET_CONFIGURATION_PARAMETERS_CNF_T;

typedef __PACKED_PRE struct __PACKED_POST EIP_APS_PACKET_SET_CONFIGURATION_PARAMETERS_CNF_Ttag
{
  HIL_PACKET_HEADER_T                        tHead;
  EIP_APS_SET_CONFIGURATION_PARAMETERS_CNF_T tData;
} EIP_APS_PACKET_SET_CONFIGURATION_PARAMETERS_CNF_T;

Whcih means that we are supposed to send the actually applied configuration back to the host.
First finding: It is suspicious that in the returned union only parameter version V1 is contained.
Anyway, in the handler, we return the following configuration packet back to the host:

typedef __PACKED_PRE struct __PACKED_POST EIP_APS_PACKET_SET_CONFIGURATION_CNF_Ttag{
  HIL_PACKET_HEADER_T tHead;
} EIP_APS_PACKET_SET_CONFIGURATION_CNF_T;

With the confirmation command code of EIP_APS_SET_CONFIGURATION_PARAMETERS_CNF. Not precisely what we want.