"Waiting for Prompt" in Netbeans from cRIO

[joshholat]

It appears as if every time we try to deploy code to our cRIO through this years Classmate or any other computer we have, it will end up displaying:

"Waiting for Prompt"

over and over again in the deploying lines that appear on the bottom and show the steps of the compile. The only way we've found to fix this is reimage the cRIO with v19 in safe mode from our classmate pc which is a pain because it takes like 10 minutes.

Is there some setting we have wrong or something that could be causing this to happen?

[Greg McKaskle]

Does this happen with a cable or just with wireless? If it is just wireless, there could be a marginal wifi connection due to mounting or other factors.

Greg McKaskle

[joshholat]

Both. We thought wired may fix it to, so we tried it that way and got the same error.

[Michael DiRamio]

Do you have any System.out.println's?

It's unable to get a prompt while output is going to the console. I removed all output from my disabled loop so I just had to disable the robot to load code (which is probably a good idea anyways...)

Another thing that seems to work is to close down the Driver Station program, then it's able to get the prompt.

[joshholat]

Yes, we use System.out.println's to see feedback from out robot in order to debug, etc. You're saying that these could be causing our issues and that we shouldn't be using them? Or are you saying that we must make sure the robot is disabled if we have these?

Also, when you say close the driver station, do you mean log out of the Driver account on the Classmate PC, or do you mean close it in the developer account when you are deploying and then reopen it once the robot has the code deployed successfully?

thanks for your help!

[rhoads2234]

We have the same problem. Using the driverstation to reboot the cRIO often temporarily fixes it, but we have not yet found a fix either.

[Michael DiRamio]

Netbeans is unable to get a prompt to reboot the cRIO when there is output going to the console.

One solution would be to remove all println's from the program.

The other is to close the Driver Station (either by logging out of the Driver account on the Classmate or closing the program if you are running the Driver Station from another computer). This stops the output and allows Netbeans to grab a prompt to reboot.