Sorry, the term "smart decisions" means that software could do something reasonably intelligent, even though somewhat hamstrung by 2 motors in parallel. I'm not saying that anyone is doing this much more that probably averaging the responses in the QSI.
And to the other question, I did already answer it, that running a 2-8-8-2 Aristo mallet, it has 2 motor blocks each with it's own motors and you can tell by the chuffs that it is reading each motor's commutator transitions...
If I was to design a system, I most likely would of course jump to separate drivers for each motor, and then let the microprocessor handle both motors, so you could do smart stuff when one motor block slips, including have the prototype option of that actually happening.
What's the point of monitoring both motors if you cannot control them independently? Well here is an idea, if either motor slips (easy to detect) then reduce speed and then ramp up again... just like a real engineer would do. I can think of a lot of things, but this is all what if stuff, nothing you can do to change the programming of the systems as they stand.
You know, some people on this thread are genuinely interested in exploring ideas, and some just want to confront and put down.
I'm in the hobby to have fun and try new stuff... if I wanted to stifle ideas, I could go to a retirement home.
Greg
