Is it required to use 2017 control system?

[RyZeRun]

I don't feel like reimaging the RoboRIO, installing other C++ stuff, etc.

[DonRotolo]

I dunno, take a look at this year's rules.

[NShep98]

Originally Posted by RyZeRun

I don't feel like reimaging the RoboRIO, installing other C++ stuff, etc.

You are going to be in for a bad time, my friend.

[cad321]

Originally Posted by RyZeRun

I don't feel like reimaging the RoboRIO, installing other C++ stuff, etc.

If re-imaging the roborio and installing some updates is too much work, you're in for a rather rude awakening when you see just how much more work is needed to make a functioning FRC robot in these 6 (now 3) weeks.

[SamCarlberg]

Is it required to use 2017 control system?

Only if you want to compete in 2017.

[Retired Starman]

Sorry folks, but I can't pass this up. . .

Was this question posted by RyZeRun, or by LazyRun?

[MikLast]

If you do become interested in updating everything, 4513 is willing to help you guys. Feel free to message me and ill get something set up.

[Oblarg]

I will remark that it is highly inconvenient that you have to update everything to the 2017 versions during build season. Our team has recently moved to a persistent framework from which we build all our code, and updating all of our legacy code to work with the new versions of all the software is a huge job. It'd be lovely if this stuff could be released a few months earlier...

[Jaci]

Originally Posted by Oblarg

I will remark that it is highly inconvenient that you have to update everything to the 2017 versions during build season. Our team has recently moved to a persistent framework from which we build all our code, and updating all of our legacy code to work with the new versions of all the software is a huge job. It'd be lovely if this stuff could be released a few months earlier...

You can access development versions of WPILib from their github page and from their maven.

If you want even more stuff, you can always apply to become a beta testing team.

[rich2202]

Originally Posted by Oblarg

updating all of our legacy code to work with the new versions of all the software is a huge job.

Hmmm.... I don't recall our team having to do much, if anything. What changed that requires updating legacy code?

I know when we went from crio to roborio, there was a big change. However, I don't recall our programmers complaining about code not running on updated roborios.

[Oblarg]

Originally Posted by rich2202

Hmmm.... I don't recall our team having to do much, if anything. What changed that requires updating legacy code?

I know when we went from crio to roborio, there was a big change. However, I don't recall our programmers complaining about code not running on updated roborios.

That's curious, because 2016 code pretty explicitly does not run on 2017 roborios for us. Lots of dependencies break.

[ollien]

Originally Posted by Oblarg

That's curious, because 2016 code pretty explicitly does not run on 2017 roborios for us. Lots of dependencies break.

Should be mostly CANTalon and CameraServer dependencies, no? Those are easily fixed.

[KPSch]

Originally Posted by ollien

Should be mostly CANTalon and CameraServer dependencies, no? Those are easily fixed.

For teams that use Command-Based C++, the changes are significant. Our team spent several frustrating hours getting a Command-Based C++ project built and running. The biggest hurdle was the fact that ScreenSteps has not been updated for 2017.

[euhlmann]

Originally Posted by KPSch

For teams that use Command-Based C++, the changes are significant. Our team spent several frustrating hours getting a Command-Based C++ project built and running. The biggest hurdle was the fact that ScreenSteps has not been updated for 2017.

It has. http://wpilib.screenstepslive.com/s/4485

[Joe Ross]

Originally Posted by KPSch

For teams that use Command-Based C++, the changes are significant. Our team spent several frustrating hours getting a Command-Based C++ project built and running. The biggest hurdle was the fact that ScreenSteps has not been updated for 2017.

I believe the significant changes occurred prior to the 2016 season, not the 2017 season. Can you explain the changes you found this year that are causing issues?