ADAU1701 and SigmaTcp - Header mismatch

The software itself is even relatively stable.

Because some answers in the thread suggest that we did not precisely nail down the problem, here is a step by step what we did and try so far. 

1.Sigma Studio sends a read request to the Raspberry PI via the LAN interface - This step works.
2. the Raspberry PI receives the request via the LAN interface and analyzes the packet for what it should do. For   example, the first byte contains the prompt what to do. 0x0A stands for read and 0x0B for write - this step also works.   Even if Sigma TCP only checks if the first byte is not 0x0A.
3. The Raspberry PI sends a request to the ADAU that it would like to read - This step works.
4. the ADAU responds to the Raspberry PI - that works too.
5. The PI receives the response of the ADAU, this can be an analog value, for example. - It works the same way.
6. The PI packs the answer into a new package and sends it to Sigma Studio - Here's the problem!
 The problem is that Sigma Studio expects a specific package, as described here: https://wiki.analog.com/resources/tools-software/sigmastudio/usingsigmastudio/tcpipchannels. The problem is that this package seems to be different for   the ADAU1701 - it doesn't work in this package order.

Wireshark doesnt help here because SigmaStudio is the black box. SigmaStudio receives a package from us and doesnt accept it. We need to know the package format for packages from SigmaTCP to SigmaStudio. We can look into the package we sent using wireshark but we cannot the extract the information we need: Will SigmaStudio accept the package?

And if not, why not?

The software itself is even relatively stable.

Because some answers in the thread suggest that we did not precisely nail down the problem, here is a step by step what we did and try so far. 

1.Sigma Studio sends a read request to the Raspberry PI via the LAN interface - This step works.
2. the Raspberry PI receives the request via the LAN interface and analyzes the packet for what it should do. For   example, the first byte contains the prompt what to do. 0x0A stands for read and 0x0B for write - this step also works.   Even if Sigma TCP only checks if the first byte is not 0x0A.
3. The Raspberry PI sends a request to the ADAU that it would like to read - This step works.
4. the ADAU responds to the Raspberry PI - that works too.
5. The PI receives the response of the ADAU, this can be an analog value, for example. - It works the same way.
6. The PI packs the answer into a new package and sends it to Sigma Studio - Here's the problem!
 The problem is that Sigma Studio expects a specific package, as described here: https://wiki.analog.com/resources/tools-software/sigmastudio/usingsigmastudio/tcpipchannels. The problem is that this package seems to be different for   the ADAU1701 - it doesn't work in this package order.

Wireshark doesnt help here because SigmaStudio is the black box. SigmaStudio receives a package from us and doesnt accept it. We need to know the package format for packages from SigmaTCP to SigmaStudio. We can look into the package we sent using wireshark but we cannot the extract the information we need: Will SigmaStudio accept the package?

And if not, why not?