Open David10238 opened 5 years ago
Hmm, interesting.
Can you think of anything you might have done around when the switch happened? Was the config correct until you loaded the configuration editor?
When was the config originally made? Did you originally make it with pre-4.0 software?
The config was made with 4.x versions. The config as far as we know was incorrect before we loaded it. We noticed it only when the drivetrain immediately locked up from fighting motors, and we opened it using the FTC app to check. I believe this was the first time running the bot after a competition. When we changed the motor type back to Rev it immediately worked like expected. I believe the hardware team made some minor repairs, but there were no changes to the drivetrain.
I'm not sure that it will be helpful, but can you provide a log file from the robot controller phone?
What was the motor type? Core Hex, HD Hex 40, or HD Hex 60?
HD 20 is what it was supposed to be. I'll get a log when I have access to the phone.
Yeah sorry, I misspoke on the motor types.
Was it specifically the Tetrix motor, or was it "Unspecified Motor"?
specifically Tetrix
Our config file changed the motor type of one of our drive motors from Rev to Tetrix which reverses the polarity without us changing anything in the code, wiring or configuration file. On the Discord, there are several other teams who recently experienced motors switching polarity without changing anything. My theory is they were other config files switching themselves. We are running two rev hubs with firmware 1.8.2 and Android Studio with SDK 4.3. Our robot only has one config file.