so, I was driving our robot today, and at one point I was holding both joysticks forward, and driving our base directly straight ahead, and when I took my fingers off of the joysticks, the drive kept moving. so I turned off the controller, but even without connection the drive kept going, so I turned off the cortex, and it stopped. I tried turning the cortex back on, and nothing happened. I turned on the controller, and still nothing. I tried driving forward again, but the drive didn’t even move. all other parts of the robot still went, and nothing had come unplugged. the motors still worked, we tested them with a 9v, but they wouldn’t turn. so I got some other motor controllers I knew to be working, and swapped the ones on our drive with the new ones, and nothing happens. so, I try driving forward, and it works. then I try lifting my fingers off the joysticks again, and the drive still goes forward. when we turn off the cortex and try to drive again, the drive is unresponsive. we tried testing the ports of the cortex with other motors, put they worked perfectly, with no issues. we didn’t want to ruin another 4 motor controllers by testing more new ones, so we didn’t test it again. why did this happen, and how would I fix this?
Have you tried using a different Cortex? Alternatively, have you tried rewriting the firmware on the Cortex?
we tried rewriting the firmware, yes, but not tried replacing the cortex. the problem is… we don’t have a replacement yet. all the other cortex’s are being used on our other robots.
Another thought: This could be in the code. I’ve seen people accidentally do very similar things with buttons in code. It’s not something I would expect when checking the joysticks instead of the buttons, but it could still happen. But we can’t check the code without seeing it. Can you post your operator control portion of the code?
we are literally using the default driver control code. I can post it in monday, as I don’t have access to it over the weekend.
Are you using IME’s?
This is a driver function, not autonomous.
@Baguette123 He might be referencing auto-correct or a P controller during driver, so the motors drive straight.
@Baguette123 - Just FYI - If you’re using IMEs, they only have to be plugged in to cause problems. You can run a program that does not even use them once or reference them in any way and they can still cause weird things to happen.
Did you try recalibrating the controllers, we have had issues where they joysticks get stuck at a value, but recalibration solved it.
oh i see
I’m not using any special code, or IMEs, it is literally the default driver code, no sensors, or anything. I’ll try recalibrating it.