I can’t speak to the V10, but I am very familiar with its operation on the V6, with a pair of 120 SE’s. I explored this in great depth in setting up my SR-71.
To utilize it, an extra ‘pigtail’ needed to be attached to each of the led boards in the plane, so they could be cross connected, and therefore have an awareness of each other. Once the physical is taken care of, there are extra menu options that you can access via the ground control units.

You can modify 3 parameters….

1. When the engines are greater than XXXXX rpm apart from each other, it goes into a ‘limited’ mode, as indicated by a ‘L’ on the ground unit. You can set the RPM number that they are apart before it goes into this mode.
2. Next parameter is time, that if it is exceeded, it triggers an action. If it has not exceeded the time, when it’s in ‘limited mode’, the ECU that has the higher RMP, is trying to lower itself to match the RPM on the lower engine. This is really cool, and you can see it working when watching the 2 ground units at the same time. Practically, it really is only put into this mode for a second or two if you slam the throttle back and forth quickly, unless you’ve had a failure.
3. Last parameter is what the engines do. If step two above has triggered, in that its attempt to equalize the engines have failed, then it will do an action. You can pick a couple different actions. The one I chose was to simply shut down the running engine. I’d say this is only a valid train of thought if you have extremely separated engines, such as a SR-71 like mine, or say a ME-262. Anything like an A-10, or especially a F-4 Phantom, you’d instead pick the option to keep the other running. But for me, I’d rather have a dead stick to deal with, than a spin, and possible fire, because I didn’t react quick enough to get the other engine shut down while it was in a spin.

I worked the parameters for quite a time, and got it working pretty well. The thing is, you need to set the RPM numbers tight enough to be effective, but yet, not to tight that it triggers too easily. It’s not as easy as you’d think… 10,000 RPM difference for a single second is easily possible at the top end of your power, as each engine his peak just different from each other…. But.. Think about landing, and the engines are at idle… say one dies on landing approach, and you don’t realize it, and then decided you want to punch it and do a go around. Perfect setup for a snap/spin… low, and slow, and now you add full power to only one engine. So, that same 10,000 that works for high power, now, is a huge range on the low end. The engine that just died needs to actually spin down for a few seconds, for the range to be big enough. Or, as I found out, the practical answer is, the running engine will spool up a bit, then reach out of range and then shut down, hopefully before the stall/spin.

Whenever you have one engine die (such as me shutting off the fuel valve for example), its ground unit would read the expected: “Low RMP”, as the reason for the shutdown. Then the 2nd engine’s ground unit would read: “2nd Engine Fail”. Great info to see what happened and why.

However…

After doing all the setup and getting it working well, I was faced with a technical glitch that could not be answered. 3 times when I was taxiing around at idle speeds… literally moving the throttle just one click on the transmitter, both engines would die simultaneously. When I would look at the ground units, BOTH of them would say: “2nd Engine Fail”. To me, this felt like going to my 2 sons, and seeing a mess in the floor, and they both pointing at each other saying: “He did it!”.

I spoke with JetCat about it and was not able to get a concrete answer about this behavior, and then decided to disconnect it until I could find out for sure. The 3 times it happened, it was always at near idle and on the ground taxiing about. But without a black and white answer I didn’t feel comfortable continuing to use it in the air.

Upon reflection, I got to wondering if this feature was more geared to drone usage, where twin engines are used, and basically run at full throttle until one dies due to whatever reason (being shot down), and it kills the other engine. The initial parameter for the RPM difference is like 50,000, which would be applicable in a full throttle or off, frame of mind for drone usage, but might not have the fidelity for a much smaller number that I was trying to tune it to. (In the 5,000 to 10,000 range)

Since this setup work in the beginning, I’ve just run them independently, and have learned that a smooth hand on throttle changes helps a bunch in the air, and to date have 30+ flights and all is well so far. I’d love to hear your results on V10 of the ECU. Maybe it’s a different in the software and the issue I’ve seen has been addressed, but it would be nice to hear that clearly from JetCat.

I think the feature is great, and would love to use it, but I need 100% confidence in it, that it would not cause more risk than it solves.

Lance