2015 driver station questions

[AllenGregoryIV]

Originally Posted by Alan Anderson

I don't think that is true. Each team is on a separate virtual LAN.

I think he is talking about having multiple robots connected to a regular router for off-season events / practices. When teams use the 10.xx.xx.2 and 255.255.255.0 scheme they can't talk to other cRIOs.

[Greg McKaskle]

Sorry for the confusion my short post may have caused. I believe the deeper details are that the libraries for Java and C++ may not be updated to be able to call into the new FRC_Communications, but LabVIEW has been.

Essentially, this means that all languages can leave the cRIO at the old image and use the old tools (programming and DS). LabVIEW teams may update the cRIO and use the new tools.

I believe some work is still underway to see if Java and C++ can be updated easily.

So, either way, you can have a practice bot. The difference is in the consistency of the tools and libraries used to program them.

Greg McKaskle

[AllenGregoryIV]

Originally Posted by Greg McKaskle

So, either way, you can have a practice bot. The difference is in the consistency of the tools and libraries used to program them.

Greg McKaskle

I guess my hope is that teams will be able to run Java/C++ cRIO robots on the 2015 FMS. That way it's easier for teams that don't have spare RoboRIOs to run practice robots. It will be much harder to fill out some of our smaller Off-season events with out practice robots.

[Greg McKaskle]

So it sounds like you may end up with 2014 libraries and FRC_Comms running on a 2015 field, right?

In that case, the missing link would be a 2015 DS that uses the 2014 robot comms and the 2015 FMS comms. That combo exists, but it isn't the default and isn't well tested.

Greg McKaskle

[AllenGregoryIV]

Originally Posted by Greg McKaskle

So it sounds like you may end up with 2014 libraries and FRC_Comms running on a 2015 field, right?

In that case, the missing link would be a 2015 DS that uses the 2014 robot comms and the 2015 FMS comms. That combo exists, but it isn't the default and isn't well tested.

Greg McKaskle

That sounds about right. If that could exist (be tested) I think that would help teams during the off season.

[lriddick]

i just want to make sure that this is answered clearly
1) will all of the old crio's work with the new drive station.
2) can you flash the old crio's with the new software.

[orangemoore]

Originally Posted by lriddick

i just want to make sure that this is answered clearly
1) will all of the old crio's work with the new drive station.
2) can you flash the old crio's with the new software.

I believe that the 4-slot crios will still be supported but NOT the really old 8-slot crios

[nickmcski]

I dont know if the 4 slot will work with the DS but in the rules (R45)

ROBOTS must be controlled via one (1) programmable National Instruments roboRIO (P/N: am3000), with image version
FRC_2015_v23 and firmware 2.1.0f3.

[orangemoore]

Originally Posted by nickmcski

I dont know if the 4 slot will work with the DS but in the rules (R45)

I'm aware that the RoboRio is the only legal robot controller for FRC competitions but I still believe that the 4-slot crio still will be supported as a testing platform for teams.

[Team3266Spencer]

Will the new Eclipse plugins be able to develop code for cRIOs?

[cgmv123]

Originally Posted by Team3266Spencer

Will the new Eclipse plugins be able to develop code for cRIOs?

4-slot cRIOs, not 8-slot. Apparently not.

^^The striked out part applies to LabVIEW.^^

[Joe Ross]

Originally Posted by lriddick

i just want to make sure that this is answered clearly
1) will all of the old crio's work with the new drive station.
2) can you flash the old crio's with the new software.

Attached is a slide showing the current state of DS and software support. Some of the information in this thread is misleading without referencing which SW environment or cRIO version.

[Team3266Spencer]

This is very frustrating :/