[DonRotolo]

Complexity for the sake of complexity is the wrong path.

If the simplest way to do something just ahppens to be complex, then, well, complexity wins.

For example: Controlling the speed of the shooter. You can use a gear tooth sensor in a feedback loop to maintain a certain speed, or just let it run open loop with a fixed value to your victor. Both accomplish the task, and unless the open-loop version has a quantifiable drawback significant enough to affect performance, it is the better solution.

Rememberm adding complexity also adds to cost, time, and detracts from reliability.

My 2 cents advice is to define the tasks, design the basics as simple as possible to accomplish the tasks, verify the system, and go. IF (and only if) there is still time (and weight!) you can 'fancy up' the system.

For the learning experience, that's what the off season (i.e., right now) is for, sop you don't have to figure out how to make it work during build season. Get the GTS code working now, not in February.

Don