Had a scan and a good example is in the thread I mentioned right at the top.
Specifically, this bit
It’s very similar to your situation, in that, in Pipeline
- does something according to a mapped state
- sends the response out to the device
- also sends it to a physical loopback D->D
- in the loopback only one CC is let thro’ and that is mapped to a new one. This stops any further looping. Importantly, the new CC re-enters D is picked up by the mappings in pipeline 1, and Hey Presto! the mapped Transform fields are set ready for the next change.
(btw, the reasons for choice of CCs can be gleaned by the OP’s specs.)
Well done for wanting to suss patches out with Editor alone, btw.
Your patch has the nice little twist of needing a ±1. Nice…!