Thread: What do we do with legacy cRIO when we get Athena?
View Single Post
  #6   Spotlight this post!  
Unread 29-08-2013, 19:56
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
  
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: What do we do with legacy cRIO when we get Athena?
The goal is for the SW tools given out in future years to support roboRIO and cRIO controllers -- at least for a transition period. Changes made to WPILib may mean that old code needs a few tweaks to work with the new SW tools, but ideally, you simply recompile.

Things like the driver station and dashboards may undergo enough changes so as to have an old and new version that are both present on the system.

I also suspect that some of the legacy SW tools will be made available, particularly if you ask and explain the value in it. I'd love to see the FPGA tools be made available as well, but that is not getting much attention at the moment.

Greg McKaskle
Reply With Quote