Log in

View Full Version : Can't load code into Crio

kinganu123
13-01-2012, 15:56
Our team recently reflashed our crio with the 2012 image. Also, we wiped our classmate and then downloaded and installed all the latest 2012 software. Since reformatting the classmate we have been unable to deploy code to the robot. The robots ip is set to 10.2.24.2 (team 224) and our computers ip is set automatically using the driverstation. According to the manuals everything is configured correctly. When the classmate is connected to the crio the robot communications light is green and robot code is red, due to the flash. We are using the FRC plugin in netbeans and code in java.


The build always fails and gives us the following error:


C:\Users\Developer\sunspotfrcsdk\ant\upgrade.xml : 40:
java.net.ConnectException: Connection timed out: connect


If anyone has any clue how to make this work then your help will be greatly appreciated.

We are using last years Crio if that matters
mathgeek0001
13-01-2012, 16:40
Are you using the access point or crossover cable?
kinganu123
13-01-2012, 16:41
Are you using the access point or crossover cable?

Both

Neither worked and ip settings were correct
RufflesRidge
13-01-2012, 16:44
Sounds like something is blocking Netbeans. Try turning off the firewall.
dave1027
13-01-2012, 17:12
Have you specified your team number inside netbeans?

Under Tools -> Options, Miscellaneous click on FRC Configuration and enter your team number.

that's how netbeans knows where to send the code.
kinganu123
13-01-2012, 17:39
Have you specified your team number inside netbeans?

Under Tools -> Options, Miscellaneous click on FRC Configuration and enter your team number.

that's how netbeans knows where to send the code.

Yeah thats been done
kinganu123
13-01-2012, 23:02
We are running NetBeans 7.1
Based upon a post found here (http://www.chiefdelphi.com/forums/showpost.php?p=1104876&postcount=7), I figure that I try downgrading to 6.9.1
I'll let you guys know once I get to school tomorrow to try it out
kinganu123
14-01-2012, 19:19
Ok, so it was a combination of things
Partially because the firewall was blocking Netbeans, and that the plugins needed a reinstall