Hey VexForum! My team and I recently went to a tournament and tried our autonomous code. Our code worked in practice but not in the official tournament. Can someone please clarify?
perhaps post your code, explain what it should have done and what actually happened.
basically this is the basic code at the beginning the “when started” portion is to set the velocities and lower the catapult for the pre-load then the “at the very start” function is called which brings the robot to the goal close to the starting zone. This was where the problem started. The robot went to the goal on the other side then didn’t follow any commands after that. Back to the code, the robot shoots then goes back to load the ball and then shoots in the low goal on loop
Sometimes if you tell your bot to drive 12 inches and then your only able to drive 11 inches it will continue attempting it forever its also isnt just driving it’s any motors task but yeah that’s probably why it wouldn’t continue
1 Like
I believe that I can help this person using two of my videos. As a teacher I know that videos work much better than words or pictures. Further, my team has exactly same problem that cost us two tournaments. So, am I allowed to help with this issue?
Sure, as long as it’s not one one that advises completely re-entering all the code, why you think that is a solution I have no idea (full disclosure, I develop the firmware for many VEX products including IQ generation 2). The OP’s issue is far more likely to be related to differences in field friction, leveling etc.
If that response is for me then sure. Thank you!
Perfect! Thank you so much! I will definitely ask you for help if at some point I will consider re-entering the code again. However, in this case I would not advice this drastic measure. The problem might be that due to unevenness of the field, the robot does not complete the operation and gets stuck. What worked for me is the standard timeout command, custom programmed timeout loop, using the driving motors as sensors or placing a sensor on the catapult. That is what those two videos are all about:
I hope it will help, but of course we never know for sure. Worth to try though.
1 Like
Try replacing “when started” with “when auton”. This is how the field control system knows which parts are auton and which are driver control. in v5 anyway.
@56860A, there is no field control in Vex IQ.
sorry, my competition experience is entirely v5.