![]() |
Is it required to use 2017 control system?
I don't feel like reimaging the RoboRIO, installing other C++ stuff, etc.
|
Re: Is it required to use 2017 control system?
I dunno, take a look at this year's rules.
|
Re: Is it required to use 2017 control system?
Quote:
|
Re: Is it required to use 2017 control system?
Quote:
|
Re: Is it required to use 2017 control system?
Quote:
|
Re: Is it required to use 2017 control system?
Sorry folks, but I can't pass this up. . .
Was this question posted by RyZeRun, or by LazyRun? |
Re: Is it required to use 2017 control system?
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.
|
Re: Is it required to use 2017 control system?
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...
|
Re: Is it required to use 2017 control system?
Quote:
If you want even more stuff, you can always apply to become a beta testing team. |
Quote:
|
Re: Is it required to use 2017 control system?
Quote:
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. |
Re: Is it required to use 2017 control system?
Quote:
|
Re: Is it required to use 2017 control system?
Quote:
|
Re: Is it required to use 2017 control system?
Quote:
|
Re: Is it required to use 2017 control system?
Quote:
|
Re: Is it required to use 2017 control system?
Quote:
Yes, the sections on installing were updated for 2017. My point is, I don't feel ScreenSteps does enough to explain how Command-Based changed so much with 2017. The core concepts are the same, but the implementation has changed quite a bit. |
Re: Is it required to use 2017 control system?
Quote:
Quote:
Updating WPILib and reflashing everything is still a pain, but it's much less so than if we did things the WPILib way of doing them. |
Re: Is it required to use 2017 control system?
Quote:
|
Re: Is it required to use 2017 control system?
Quote:
|
Re: Is it required to use 2017 control system?
Here's the history on key command-based robot header files:
Command.h CommandGroup.h The change that would definitely break things at compile time is the namespace change. According to the commit message, it requires a one line change to fix. Even in a large robot codebase, it's probably a 10 minute job to fix. Easier if you have a shared header file throughout your codebase -- for many teams that would be robotmap.h. |
Re: Is it required to use 2017 control system?
Quote:
We finally were able to make some headway by making a quickie project with RobotBuilder. What it generated looks WAY WAY different from past years and from what the project wizard in Eclipse makes. RobotMap was the biggest change. It's no longer a simple header file, but a class with static member variables. This is our team's fifth (or sixth) year using command based C++, so we certainly have some experience using it. I'm hoping we just accidentally reinstalled the 2016 plugins or something. That would explain a lot. |
| All times are GMT -5. The time now is 22:35. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi