We are trying to run code from the 2010 Classmate on the cRIO, but we are getting the error that the cRIO has different software installed, has there been a firmware update, and if so, where would we be able to get it?
Here is the exact error message:
Access denied: This target is running a version of LabVIEW Real-Time that is different than the Real-Time Module software on the host computer. You can verify the version and reinstall the Real-Time software using Measurement & Automation Explore.
I experienced this tonight. I thought I had forgotten to update the Classmate but all indicators show that the update was previously installed.
When using the classmate, image FRC_2010_v5 was available. This is AFTER the DS Update (which is for the classmate). It formatted fine but after installing programs, we could never see the battery value nor would the program run. The symptoms you described are what we found as well.
Thus, I tried imaging from my laptop which also was updated. It had version FRC_2010_v10. One of our student caught that thankfully and said that the classmate’s version was older. The cRIO imaged correctly, and we saw the battery voltage! Installed the program and it ran! 20 of us high-fived as we thought the problem was the classmate had not been updated.
However, I think the DS update has FRC_2010_v5 while the Laptop/LabVIEW update has FRC_2010_v10. I’ll try and post on USFIRST as well because I think other people will hit this problem.
I hope this is/was our problem and we will format from the laptop only. It has been a set of nasty nights getting that figured out.
Those should be the right updates. Your DS, on the diagnostics page, should say DS Version: 2010.01.06.00, for C++ is also says cRIO image: C-2010_v19
Make sure your DS has the right version. You might have to run the DSUpdate1.0for2010.zip and tell it to UNINSTALL, then run it again and tell it to install.
I was having similar trouble, so I went to the NI website to look for help. There I noticed a posting called “[FRC 2010] How Do I Deploy Default Code To My Robot?” by a user named NI-Bob. It has a Word document attached which describes a slightly different method for deploying Default Code through LabView than the “2010 Getting Started” manual does. I used this method successfully to get my last year’s robot running with the ClassMate Drivers Station- at least with LabView code. Now to C++.
I finally connected to the cRIO through WindRiver. What I needed to do was to completely install all parts of the C/C++ update posted here: http://first.wpi.edu/FRC/frcupdates.html
In particular, after applying the “Workbench Software Update”, I was able to create a connection in Workbench without getting an error message from the target server like the following:
“Error: The systems running on the target and loaded into the target server memory are different. Either wrong core file is selected on the host or text section is corrupted on target side. Error during target server core initialization
Target Server will exit”
It’s important to know that not just the DS update is required, but so is the LabVIEW update (even if you’re not using LabVIEW to program.) This contains the important updates for the cRIO formatting utility.
Here, here to Joe’s post. The WindRiver update is what got me going and I had ‘no code’ also. Again it’s the “Workbench Software Update” download from the location I gave earlier.
All - Thank you VERY much. We had PAIN through Sat afternoon when another mentor forced me to retrace all the steps and found that we were missing an update (WindRiver Workbench). We are rocking and rolling now with getting simple code to run. Again, thank you all for your assistance.
-Ted Dressel, Mentor, Team 1111