Whenever I try to run a program I get an error message. Its something like this.



Wait for Start

Ext Batt: OFF
NXT Batt: 7.2 V
FMS Msgs: 0
Teleop FileName:
AwesomeSauseDem




Any ideas on how to fix?

Including the program would go a long way towards helping us to help you. Describe your setup, etc, etc.

We're really short on psychics on these forums, so we're having to make do with the mere mortals that frequent this place.

Regards,
Xander

You're running a program that you've built for the FTC FIRST Competition. You likely started with a "Template" for this competition rather than a "new file". These messages are expected.

In the FTC Competition, your program execution consists of a Autonomous Phase and a User-Controlled Phase. Messages are received over Bluetooth to progress through the various phases of the competition. When you see "Wait for Start" the program is waiting for the BT message that says the competition has started.

You should copy your code into a new file without all the FTC Template stuff. And then it should work -- always assuming there are no programming errors.

Hey guys, I know this thread has been dead for a while. We too are having a similar problem. Anytime we try to run our program, our NXT brick says:
Wait for start
ext batt: off
nxt batt: 8.5v
fms msgs: 0
teleop filename:

We tried to copy our code into a new file, and run it again, but the same message showed up. This is our code[Mind the idea that the code might not work even under ideal situations. We are currently just trying to fix the above error]:



Any help would be appreciated.
-HsaRobtix

If you want the robot to not wait for a signal from the FCS before starting, then remove the statement "waitForStart();".

There is no waitforstart(); command in our program. Any other advice?
-HsaRobtix

what is the code like in "JoystickDriver.c" ?

ps: would you pls put the code into code tags? it will make it more readable )

"JoystickDriver.c" tells the program to add the variables for programming the joysticks.
-HsaRobtix

sure, I know that, but I need to know what exactly:
maybe there is the wait command somewhere in the JoystickDriver source code we are wondering about - or in any 2ndary addtional depending files.
So we need to get to know how the exact code looks like !

(another strange thing is that this is a .c file you are #including (i.e., executable code) - header libraries normally are declared in a .h file...)

joystickDriver.c is provided by RobotC. You can find the source code in "c:\Program Files (x86)\Robomatter Inc\ROBOTC Development Environment\Includes\JoystickDriver.c"

This message is displayed by the displayDiagnostics() task. To get rid of it, insert a couple lines at the beginning of your program.

haha, what did I say?!

I think one could also patch the displayDiagnostics source code manually to avoid waiting for the "start signal".
hsarobtix simply should have provided the source
(I don't have it on my PC)

So, I have no idea what I'm doing. This is a high school class, that I just joined. Two days in, the teacher made me program lead... I have no experience or anything. I just google stuff, which is how I found this forum. Thank you guys or all the help you're providing.
HsaRobtix

In very general terms, if a program makes unintelligible things then you have to look through all of your code.
If it is composed of several parts you have to look through all of the parts.
If you don't find the reason in what's obvious, you must look through the parts which are obscured.

So if you don't find the reason for the message "wait for start" you have to search for the code which causes this, a program won't give such a message just because it sort of feels like that:
if you don't find it in your own code then it must be localized in any included or linked code.

And finally, if you want people to help you with your program then you must provide literally all of your code, so that we also can check all the things I mentioned above, especially when you're asked to do so.

In this case I asked you "what is the code like in "JoystickDriver.c" ?
(would you pls put the code into code tags? it will make it more readable)"

your reply was:""JoystickDriver.c" tells the program to add the variables for programming the joysticks."

This is not what I asked for.
Your reply instead should have been: