Team 6135B Innovate Entry

Team 6135B devised a safeguard for a robot resetting with the LCD for the 2014 VEX World Championship Innovate Award Entry. Let us know what you think! (:

http://www.youtube.com/watch?v=KQXdn73SKQA

Um, what?

I’ve never used RobotC, but I think there’s an issue with your code if it gets locked up in Initialize. We’ve written menu systems in EasyC, PROS and ConVEX this year, none of which have the problem you’re fixing. This is either RobotC specific, or your programmer did something wrong.

If this is working for you, great. But I’m 99% sure there’s an easier way of doing this.

The way to solve this is run a task for auton selecting so preauton starts the task and driver control ends it.

Like you said, you’ve never used it… but for the many teams that have this is an ongoing issue. It has happened to many of the teams in Kentucky, as well as some teams I’ve seen online, and my own team. RobotC has the default LCD “code chooser” program which after startup goes directly to the LCD’s program selection menu, and as shown in the video the robot will not move until a program is selected. What we did was made a pre-autonomous function that acts as a safeguard to divert it to driver control unless you tell it otherwise by pressing the LCD bottons, as shown in the video. If easyC has no problem with that then it is great, but for the teams using RobotC this is very beneficial.

How does yours react to being connected to a competition switch. It sounds like your method is either ignoring the competition switch or not working unless in driver control mode on the switch.

1 way is against the rules
1 way is useless

It sounds like your doing one of these 2 things ^

Griffin. It’s okay. Haha. All that they did (if you watch the video…) is require you to be holding down a button on the LCD display while the robot turns on/connects in order to bring up the autonomous menu. If you are not holding down the button when the robot (re)connects (for example, during user control), it does not display the menu. There are multiple ways to achieve the same result (prevent your robot to become stuck in your autonomous selection menu), and some may make more sense than others, but it’s all personal preference, as nearly all programming.

~Jordan

You must be using this in your code:

{
    while( (nLCDButtons != 0) && bIfiRobotDisabled )
        wait1Msec(5);
}

Thanks to Jpearman we were able to get away from the reset issues as well.

I see how it works now. Good job!

Thanks! (: