We are having issues deploying our code in Eclipse. There is no issue when using the build function, but an error occurs when deploying the code. The error states
C:\eclipse\plugins\edu.wpi.first.javadev.sunsportfrcsdk_1.0.7.1\sunsportfrcsdk\ant\upgrade.xml:40: java.net.socketexception: Network is timed out: connect
We have tried many troubleshooting techniques but to no avail. Any help would be greatly appreciated.
How are you programming in eclipse? Theres no updated plugin? are you sure its not netbeans? Did you set up your router and crio correctly? Did you set your comp ip? Did you configure the frc plugin for the correct ip? Did you disable all other network cards?
The problem that you are having is because your computer can not connect to the cRIO.
I am not sure how you setup your ant build for 2013 but you need to provide it the IP address of your cRIO.
I hope you are not using the 2012 plug-ins, because they won’t work!
It is possible to use eclipse for 2013 development. See my other thread on this topic and follow the video.
http://www.chiefdelphi.com/forums/showthread.php?t=110420&highlight=eclipse
there is a .sunspot.properties file in your user directory. In there should contain the IP address to the crIO, as well as the location to the new 2013 WPILIBJ library file.
If you don’t have an important reason for developing with eclipse, I would recommend using netbeans. It has almost all of the same features, but its easier to get started with, and people will be able to help you more if you’re using net beans.
I think you should work with what you are familiar with … I personally think Eclipse is way better than Netbeans, and see no reason not to do it (Netbeans is not easier to get started with, and it uses way more resources than some of our old & tired laptops have). The FRC plugins aren’t magic, and the YouTube video on the web is pretty straight forward on how to get going with Eclipse this year (we are currently running Eclipse on Windows, Linux and Macs for development).
From what you have, it sounds like you didn’t define the remoteaddress property on the run Ant target with the IP address of the robot (we had the same problem until we watched the YouTube video). Although you can mess around with the properties files, you can also specify it on the command line arguments for your custom build command. If you can ping the robot successfully, then the deploy should work.
Again, assuming you can ping the robot successfully (or, as a better test, download and run a simple project using NetBeans) - the problem is likely to be the step at minute 20:00 in this YouTube video, which is what we used to get up and running.
Glad to see the video is helping 