Hey everyone! Quick update on what happened at our event with the drive. Unfortunately we never got it to work correctly. We’ll be switching to Sparks and CIMs for our drive train for our next competition this weekend since we haven’t been able to fix the problem. The axes switching thing happened another 2 times during the matches we had. We were able to add a button onto the joystick that we could press that would reverse them so we could still drive although it was with significant difficulty still.
However, the SPARK MAXs all had the correct lights when we were moving. For example, if we pushed the joystick forward 2 of the lights would be green and 2 would be red as one side would have to be inverted due to it being on the other side of the drivetrain. This is what we would expect to happen however the robot would turn instead of going straight. This is really the most bizarre part of the entire issue.
The CSA at the event talked to HQ and no one up there could come up with an answer for our issues. We talked to the FTAs and the FMA program director and no one had an answer as to why we were having these problems. They even looked through all of our code and everything seemed fine. When the axes switched it was always in the middle of a match if they switched at all.
The CSA and our programmers took a look at the Spark MAX settings and they all looked fine. We tried a new computer and a new joystick and had the same issues. As to what version of WPIlib we use, it is the most recent version.
We’ll be emailing/calling REV tomorrow to see what information they have on all this and I’ll let you all know if they give any good insight.