FRC C++ Update 3111

[bob.wolff68]

Hi all,

I've just realized today (2/20/2012) that there's an update to C++ Workbench which is dubbed rev 3111. I downloaded and installed it, but I have no idea how to tell if it successfully installed. I'd like to know if there's a way to tell what rev is running. I looked in Windriver Workbench Help->About and looked at the plugin versions and such but didn't see anything there that looked 'right'.

Knowing that we have the RIGHT software loaded as we all know is critical to success in the final chute, so I want to make sure this gets distributed to our various laptops and validated as correct.

Thanks,
bob

[RufflesRidge]

Look in the Examples for the 2012 Vision Example or Rectangle Processing Example or something like that (not sure exactly how it is named). That was included as part of the update.

[Brian3618]

Hey guys my team has a problem when using the 3111 workbench update. Our robot is programmed using the command based robot. When we compile out c++ code and deploy it into the robot it deploys with no errors.

The problem is that when we load up our driver station the robot says the is zero code on the robot. When we compile and deploy our non command based robot code the robot says that there is code on it.

We would really like to use the command based robot code, but we can't if our robot will not see it. Any help would be great.

~Brian

[rbmj]

Can you check NetConsole and post any output that gives you?

[kccowan]

Back to Bob's question, in last year's code, one of the many messages during boot is which version of WPILib your code compiled against. Since we're still using the first update for 2012, I haven't looked closely to see if the message is still there.

The version number was call "SVN Rev xxx" or something like that.

Good luck! One day to ship!

KC

[frdrake]

I found a similar error. We would build and it built with no errors then we'd deploy and that would work fine as well but when we got to the robot it would tell us no robot code. As soon as you turn the CRIO on hook up the WTX console (right click your connection and then go to Target Tools and then WTX console) something is not loading right on the CRIO boot up and you will get output as to what that is in the console at boot up.

This method solved this problem twice for us with minor issues that the compiler didn't catch.