Deploying Java via NetBeans on the driver station PC fails
 

We're having uploading code to the cRIO from NetBeans installed on the driver station netbook. Uploading fails with this warning, followed by a Java stack trace regarding the failed connection:

Note that the subnet mask is being printed as 255.255.255.254 and it should be 255.0.0.0. This doesn't make much sense, because ipconfig and the Control Panel both show the subnet mask being set to 255.0.0.0.

I can transfer code to the cRIO from my personal laptop (that is running OS X), so it is not an issue with the cRIO or wireless router. I believe it's either an a problem with the computer's network configuration or the NetBeans plugin. I have already verified that our team number is set in NetBeans, verified that the compiler plugins are up-to-date, and have disabled IPv6 on both wifi and ethernet. Any suggestions?

Re: Deploying Java via NetBeans on the driver station PC fails
 

The "incorrect" subnet should not cause a total failure. You might never get rid of that warning; it's generally a bug.
I'm not sure why you can't connect though. A few restarts of the classmate/netbeans and the robot, with some confirmation of the network configuration seems to clear up the failure for me. I can't explain why. :P

Re: Deploying Java via NetBeans on the driver station PC fails
 

As nickpeq said, that error shouldn't cause it to completely fail. We get that error every time, but it still works.

What error are you getting after that? Just cannot connect to the cRIO... failed after x attempts...?

Re: Deploying Java via NetBeans on the driver station PC fails
 

It's good to know that the warning is a known issue.

Immediately after the warning I get a Java stack trace caused by an uncaught SocketException. I don't have the full stack trace on hand (not that it contained much useful information), but I'll post it next time I have access to the cRIO.

Have you ever encountered something like this?

Re: Deploying Java via NetBeans on the driver station PC fails
 

Did you install the latest Labview? This was our issue. Also the latest firmware on the cRio. Try FTPing to it manually by putting
into a windows explorer window. If it connects, your configuration is good. Just get the latest labview and utilities updates.

Re: Deploying Java via NetBeans on the driver station PC fails
 

We're using Java, which does not depend on LabVIEW and it works fine from my personal computer. In any case, we do have the latest version of LabVIEW installed.

I provisioned the cRIO yesterday with FRC_2012_v43.zip. As far as I can tell, this is the latest version of the firmware.

Re: Deploying Java via NetBeans on the driver station PC fails
 

Can you FTP to it? Because we had the exact same problem, but everything got resolved after doing all that.

Re: Deploying Java via NetBeans on the driver station PC fails
 

Do you mean manually FTPing (e.g. ftp 10.xx.xx.2) from the driver station netbook to the cRIO? It is definitely possible to FTP from my personal computer to the cRIO because it is part of a normal deployment. If that's what you mean, I'll try manually FTPing next time I have access to the robot.

Can you try turning off the windows firewall temporarily to see if that fixes the problem?

Brad

Re: Deploying Java via NetBeans on the driver station PC fails
 

Run a command line (type "cmd" into the search bar in the Start Button), and see if you can ping the cRIO.

ping 10.42.81.2

Getting a response will at least ensure the network itself is working fine.

If you get a ping, and still can't successfully send code, disable your firewall, and/or make an exception for NetBeans.exe.

If that still doesn't work, you might be experiencing this:
http://www.chiefdelphi.com/forums/sh...hreadid=100588

For which I personally am still stumped by, and don't have a solution.

Re: Deploying Java via NetBeans on the driver station PC fails
 

I already allowed netbeans in Windows Firewall. i finally fixed the problem by following the instructions in this post on the NetBeans forums. Specifically, run the following command in a command prompt with administrative rights: