We started from the standard 288 base code, which works well except our robot throws an error randomly from the FTC Move Motor.vi that causes it to stop working.
This error will continue the last action of the driver for maybe two seconds and then the robot will stop. We designed a function to indicate that the error has occurred through beeps. The error can be corrected by switching off the battery for approximately five seconds. We cannot figure out what throws the error though. Sometimes the error will throw itself every couple of seconds while other times the robot will run fine indefinitely, or at least until we turn off and on the program.
We modified the 288 scaling code to cap the maximum values in case of weird controller values, so we don’t believe that to be the problem. We also do not use the encoder values in our program.
-
Which program are you using?
-
Do you believe it to be a problem with the code? If you think so, then post your code somehow and we’ll look over it.
-
Do you think it’s a problem with the motor controller? If this is the case, I think you should contact Pitsco with your problem.
Make sure you have downloaded the latest updates. The latest FTC Move.vi seemed to fix our similiar issues.