Alpha Weekend #2, 2015 Control System

[calcmogul]

Originally Posted by apples000

10. Most importantly, what are the plans for the cRIOs? Can we use them on a practice bot next year? When LV/windriver licenses run out, do we end up with really expensive paperweights? That would really suck. A lot.

For C++, one could also use GCC 4.8.0 and newer. Windows and various distros of Linux are supported natively. See http://firstforge.wpi.edu/sf/projects/c--11_toochain. There are also Eclipse plugins for it but I don't think they are officially packaged for Windows. One would have to track down the .jar files to place them in the dropins folder.

[Pault]

2 things:

1. Has anybody had time to look at using USB to communicate with a co-processor? Is this even supported? How comprehensive is wpilib in supporting this at the moment?

2. I believe this has already been adressed, but are there any updates on when the roboRIO will be released to teams? Would it be possible for the 2015 wpilib to get released first, or at least a beta version? I really want to get a chance to look at developing code for some of the newer features on the roboRIO.

[Joe Ross]

Originally Posted by Pault

1. Has anybody had time to look at using USB to communicate with a co-processor? Is this even supported? How comprehensive is wpilib in supporting this at the moment?

What support would you want to see in WPILIB, vs using the interface provided by the OS?

[Joe Ross]

Originally Posted by Tom Line

I'll add in when you plug into the USB of the RoboRio with your laptop, it shows up as an ip address in the range (from memory, might be wrong) 172.X.X.X

One advantage that is that the usb ethernet acts as a DHCP server, so you do not need to configure the IP address of your programming computer(s) to the 172 address. That is definitely nice.