That is good to hear.
My biggest concern is the licensing aspect. As official support tapers off, and moves to the more modern hardware, I don't want to be dependent on time locked licenses for the tools needed to program the legacy hardware.
Do we need a project to create a replacement for vxWorks as the cRIO base OS?
Do we have enough info to make such a project practical?
Quote:
Originally Posted by Greg McKaskle
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
|