Unable to deploy over Ethernet using WindRiver C++

[kbocheltree]

This is our second year and we are moving to C++. We are able to build our projects using WindRiver and have only been able to deploy them over wireless, ethernet will not allow use to deploy the code, it hangs on transferring the code and never starts. We can do everything using wireless, but as soon as we try using wired Ethernet, it won't deploy

In Ethernet (With wireless disabled)
1. We are using the static IP address
2. We can ping the cRIO over ethernet
3. We can see the communications to the remote cRIO in the WindRiver window
4. Firewall and Antivirus was turned off

Any other suggestions? Is there a good way to get a trace to see where it fails?

[connor.worley]

Make sure the FIRST Downloader settings are set correctly. I think they're under Window -> Settings.

[gyroscopeRaptor]

Originally Posted by connor.worley

Make sure the FIRST Downloader settings are set correctly. I think they're under Window -> Settings.

Different team, same issue. The Getting Started with the Control System page says the file we should download is C:\WindRiver\workspace\DefaultRobot\PPC603gnu\Defa ultRobot\Debug\DefaultRobot.out but that doesn't exist for us. What file should we be downloading?

[mprasolov]

We experienced a problem exactly like that. My laptop is capable of compiling and downloading programs, but another programmer's laptop just would not do it, even with the same IP settings, WRWB settings, and code. Try on another computer and see if that helps!

[RufflesRidge]

Originally Posted by gyroscopeRaptor

Different team, same issue. The Getting Started with the Control System page says the file we should download is C:\WindRiver\workspace\DefaultRobot\PPC603gnu\Defa ultRobot\Debug\DefaultRobot.out but that doesn't exist for us. What file should we be downloading?

Replace instances of DefaultRobot with whatever you called your project.

[BradAMiller]

Just clarified the directions to show how to find the .OUT file you need to use in the FIRST Downloader preferences. Look at the last few sections at the bottom of this web page:

http://Wpilib.screenstepslive.com/s/3120/m/7913/l/79735

Brad

[bob.wolff68]

I'm a bit surprised to hear this inability to deploy and yet you can ping the cRio -- have you tried ftp'ing with the cRio just as another way to poke at the beast? On the computer that DOES transfer (or in the mode in which it transfers - wireless) -- goto a browser and type into the address bar
ftp://10.xx.yy.2
where xxyy is your team number (for our team 1967 it is ftp://10.19.67.2)
If you can see files/directories, then you've successfully made an ftp connection to the cRio. Then switch to the other non-transfer-able computer (or switch off wireless and go to wired mode) - re-do the same test. Whether you are able to ftp or not might help illuminate the issue here. Brad might be able to help a bit more based on these results.

bob

[Fifthparallel]

I had a similar problem when the Driver Station had changed my subnet on my wireless connection to 255.255.255.0, and I had 255.0.0.0 as the subnet for my ethernet connection (cRio was in the 255.255.255.0 subnet).

It was 2 years ago, though, and I don't rightfully remember if that was the same problem.