A team we are mentoring is having difficulty with their vex brain. They can download code, and firmware. If they download autonomous the motors will move but to drive there is no response. Is there anyone who can help us figure out what is wrong with the brain?
To help assess your problems it would be good to know:
Are you using the Cortex controller or the older crystal set?
Are you using EasyC or RobotC?
Do you have a good connection between the controller and the robot? (Don’t know?.. check the LED’s… see next question.) The robot will run autonomous code without a connection to the controller, but will not execute driver mode code without the controller.
What LEDs are showing (on the robot and controller) when you run into the problem?
Does the system work with the “default code”?
Got a camera or camera phone? Post a photo or two of your setup.
VEX has a pretty darn reliable system, so you’re very likely to get it working. You may also want to cross post your question (with some of the data, above, attached) to www.vexforum.com
Jason
They are using cortex controllers
robotC
They also tether them together and all lights are green on controller and cortex
we’ve also tried programs like
Task main()
{
while(true)
{
motor[port3] =127;
wait1msec(1000);
motor[port2] =vexRT[ch2];
}
}
and
Task main()
{
while(true)
{
motor[port2] =vexRT[ch2];
}
}
Hmm… that sounds okay so far… although I’m not familiar enough with RobotC to consider any oddball settings in the compiler that might cause such a problem (there probably aren’t any… but I don’t know RobotC well enough to say for sure.)
And you have no problem getting the motors on Port2 and Port3 to run when you run them in auto mode, eh?
I don’t have any immediate insights in to the problem… sometimes re-flashing the master code and re-downloading default code, essentially setting the robot controller back to factor spec is a good diagnostic.
Good luck, and do consider posting to VEXForum if you haven’t done so already,
Jason
thanks