Had an issue today with a team using the GoBilda example code (Blocks, this is a 7th/8th grade rookie team), and the code that sets the arm to a position to grab samples from the submersible wouldn’t stop running after they used that button and began to over heat the motor. What are we missing? Tried a few things, here’s the link to the block code: FTC-Starter-Kit-Robot-Into-The-Deep-Blocks-Example/BlockConceptGoBildaStarterKitRobotTeleop_IntoTheDeep.blk at main · goBILDA-Official/FTC-Starter-Kit-Robot-Into-The-Deep-Blocks-Example · GitHub
Hello! That code by default prints telemetry of the arm’s target position, and current position. Which is meant for debugging issues just like these 
If there is an issue with the motor encoder (like the wire isn’t plugged in, or is damaged in some way) then you’ll see the target position change from 0, but never see the current position change.
Another common issue is that the motor can be reversed at the adaptor wire. So that the motor spins opposite of what the code is expecting. If this is the issue, then you’ll see the current position go negative and continue moving away from the target position as the motor moves.
Hopefully we can get you up and running soon!
1 Like