I tried to deploy a program to the cRio by clicking the run button and it always got hug up while it was “Waiting for the OTA server to reply”.
Has any one had this problem before? And if so will they tell me how to fix it?
I have the same issue and were getting “No route to host” is that what your getting.
no, after netbeans did some upgrading on the crio it sat there waiting for the “OTA server” for half an hour then i gave up on it.
It sounds like you are running the software from the DVD or a beta version.
You need to update the FRC plugins as described at:
http://first.wpi.edu/FRC/frcjava.html
You may also need the “mandatory LabVIEW update”.
Ya, I looked into that and made sure that all the updates were installed ,but it was the pre-installed software that the classmate came with, if that matters
The software that came with the Classmate is not the most recent - I had the same problem, but using the update site fixed it.
If you haven’t already, go to Tools>Plugins>Settings
Click Add.
Use this URL: http://first.wpi.edu/FRC/java/netbeans/update/updates.xml
and name it anything you want.
Now Netbeans should update automatically.
I am fairly sure i did that already but i make sure and check on monday when i have access to it again.
there is a second plugin update you need for netbeans as well as that one. look on the forums.
Also, don’t forget to perform the LabVIEW update on whichever machine you are using to format the cRIO, and that the cRIO has the latest v19 firmware.
We are using the classmate to image the crio and it used the v19 update so that shouldn’t be a problem
It still wont work and i did every thing
if any one else has something to comment about please reply.
Hi,
Please post the Run output so we can get to the bottom if this. Thanks.
Sorry it took so long but my team was really focusing on labview. Anyways heres the output:
init:
init:
No to.jar.file specified.
Using "suite\RobotTemplate_1.0.0.jar"
Deleting directory C:\Documents and Settings\Developer\My Documents\NetBeansProjects\RobotTemplate\build
Deleting directory C:\Documents and Settings\Developer\My Documents\NetBeansProjects\RobotTemplate\suite
Deleting directory C:\Documents and Settings\Developer\My Documents\NetBeansProjects\RobotTemplate\j2meclasses
clean:
Created dir: C:\Documents and Settings\Developer\My Documents\NetBeansProjects\RobotTemplate\build
Compiling 1 source file to C:\Documents and Settings\Developer\My Documents\NetBeansProjects\RobotTemplate\build
compile:
Created dir: C:\Documents and Settings\Developer\My Documents\NetBeansProjects\RobotTemplate\j2meclasses
preverify:
Created dir: C:\Documents and Settings\Developer\My Documents\NetBeansProjects\RobotTemplate\suite
Building jar: C:\Documents and Settings\Developer\My Documents\NetBeansProjects\RobotTemplate\suite\RobotTemplate_1.0.0.jar
jar-app:
Using "suite\RobotTemplate_1.0.0.jar"
CompilerOracle: exclude com/sun/squawk/Method.getParameterTypes
CompilerOracle: exclude com/sun/squawk/SymbolParser.getSignatureTypeAt
CompilerOracle: exclude com/sun/squawk/SymbolParser.stripMethods
[translating suite image [closed: false, parent: squawk] ...]
### Excluding compile: com.sun.squawk.Method::getParameterTypes
### Excluding compile: com.sun.squawk.SymbolParser::getSignatureTypeAt
Romizer processed 71 classes and generated these files:
C:\Documents and Settings\Developer\My Documents\NetBeansProjects\RobotTemplate\image.sym
C:\Documents and Settings\Developer\My Documents\NetBeansProjects\RobotTemplate\image.suite
C:\Documents and Settings\Developer\My Documents\NetBeansProjects\RobotTemplate\image.suite.metadata
C:\Documents and Settings\Developer\My Documents\NetBeansProjects\RobotTemplate\image.suite.api
Expanding: C:\Documents and Settings\Developer\My Documents\NetBeansProjects\RobotTemplate\suite\RobotTemplate_1.0.0.jar into C:\Documents and Settings\Developer\My Documents\NetBeansProjects\RobotTemplate\suite
Moving 1 file to C:\Documents and Settings\Developer\My Documents\NetBeansProjects\RobotTemplate\suite
Moving 1 file to C:\Documents and Settings\Developer\My Documents\NetBeansProjects\RobotTemplate\suite
Moving 1 file to C:\Documents and Settings\Developer\My Documents\NetBeansProjects\RobotTemplate\suite
Deleting: C:\Documents and Settings\Developer\My Documents\NetBeansProjects\RobotTemplate\image.suite.api
Connecting FTP @10.13.88.2
Remote VM does not match, upgrading
Remote bootstrap suite does not match, upgrading
Connecting FTP @10.13.88.2
Remote VM does not match, upgrading
Remote bootstrap suite matches local, no upgrade needed
upgrade:
Sending local file image.suite
Verified
flashapp:
deploy:
init:
Waiting to connect to OTA command server of 10.13.88.2:8001
After that last line it just sat there for half and hour before i just cancled the run
OK, you are running an older version of the Java SDK (netbeans modules).
Set your FRC plugs-in update site to
http://first.wpi.edu/FRC/java/netbeans/update/updates.xml
Check the page at http://first.wpi.edu/FRC/frcjava.html for updated docs and more details.
I just tried that several times, and thought maybe i should reinstall the plugins and i still didn’t work.
P.S. My team has given up on Java and I was bearly able to squeeze in these tests before our meetings. Sorry if I don’t reply for a while
We have the same problem, Netbeans do not continue to working. We have the latest updates but we can not load or run our program through NetBeans.
We need help, please!!!
Please post the run output.
Besides setting the update URL you also need to keep an eye out for new updates and select the Updates tab, and press ‘Update’. Here is an attachment of what it looks like for NetBeans updates, my FRC is up to date so I couldn’t show that.
We just started having problems with our JAVA to the cRIO ever since NetBeans AutoUpdater updated and then 2 FRC plugins got upgraded too. One of them was FRCSquak which was upgraded from 1.15 to 1.17. Getting “Feed Watchdog” Error oscilating on Dashboard. Plugged in a machine w/o the upgrade and no issues.
Anybody got a solution? Who needs to go back and check these plugins?
We had this problem immediately after we updated the cRIO to v19 and used the latest FRC Plugin updates. We set the NoApp DIP Switch on the cRIO to on and redeployed and it started working.
Hope this helps and was not a coincidence.