Zero-to-robot arcade drive example should use four motors and following

[calcmogul]

The kitbot has more than two motors, so following is required to get full performance. The example just needs some extra motor declarations and some leader.addFollower(follower) calls in robotInit().

See https://docs.wpilib.org/en/stable/docs/zero-to-robot/step-4/creating-test-drivetrain-program-cpp-java-python.html.

[sciencewhiz]

It's based on the wiring instructions in step 1 which uses a PWM Y cable

[calcmogul]

A team I just dealt with on the FRC Discord apparently didn't do that, and had them all wired to individual ports. They couldn't find a code example to fit their needs after looking for several weeks.

[sciencewhiz]

I assume they didn't find this? https://docs.wpilib.org/en/stable/docs/software/hardware-apis/motors/wpi-drive-classes.html#multi-motor-differentialdrive

[jasondaming]

I think we can close this as not planned? I struggle to see why we should support the use case not specifically following the instructions in this specific document. Maybe there is a different issue and another place to address this but I don't see this as a common stumbling block.