In rereading your initial post more carefully I’m realizing that my suggestion is not helpful.
If you want to use the Apollo as an input to Sensory V2, and just use the ADAT outs of the Portal, then you would need to use a DAW (or some other software capable of routing) essentially as a pass-through.
The screenshot below shows how it would work using Ableton:
With sensor 1 (input channel 5 on the Portal), going out ADAT 1 (output channel 9 on the Portal).
Yes, I initially misunderstood. To get this to work you would need a DAW or some kind of routing software to route the sensor signal out of the ADAT outputs (see my followup comment, above). So your signal chain would look something like this:
Sensor > portal (plugged into the computer) > DAW for routing > ADAT > apollo > Sensory V2
I’m not sure I understand the use of the ADAT out of the portal, if you can’t output directly to an other interface via ADAT in?
It seems like for the signal path you are suggesting, using a DAW for routing, I would get the same results by having the interfaces in parallele (no need ADAT in this case)
Or is it that the sensors can only output signal via the USB out of the portal, and the ADAT out are 8 other outputs not directly related to the sensors?
The main use-case for the ADAT outputs is if you want to route more submixes from the Sensory V2 software to another system (for example: a live sound engineer, or a mixing desk) – the analog outputs are obviously easier to use, but if someone runs out of analog outputs and still wants to send more submixes somewhere, they can use the ADAT outputs with a compatible system.