Anyone know how to image new code to old Rio ?

[mitchklong]

So all of you are like us...we have old CRIOs sitting around with nothing to do.

Our attempts to image our code to the old RIO failed. Anyone have an easy way to do this ? Is it worth it to try ?

[bh202548]

Just put code on the old rio the same way you put code on it last year. You should need very few changes to the actually code to make it run on the crio it just has to be compiled and loaded differently.

[thatnameistaken]

You'll need to image it with the cRIO Imaging tool provided in this year's LabVIEW update if you haven't already. However, if my understanding is correct, you'll need to make a seperate project specifically configured for the cRIO; don't quote me on that, though, as I haven't played with it much myself.

[MamaSpoldi]

I too am interested in this topic. If you were using C++ the WindRiver license is no longer active and therefore you cannot build with it anymore (or even open the application anymore). Therefore you need a different cross-compiler which can use the libraries and other settings that were setup in WindRiver.

I'm not sure about the possibility of using the old cRIO imaging tool as I have not tried it. That might still function.

I was able to successfully copy a previously built executable onto a cRIO using FTP to copy the file to the correct path on the cRIO disk. Tp the best of my knowledge, this is basically what the deploy function did under WindRiver. It appears to function fine, but we have not done much testing.

There was some mention of backward compatibility to the cRIO using the Beta testing, but I never heard any details. We too are hoping that something will be published about it soon.

[Mark McLeod]

LabVIEW is the only 2015 language that supports running 2015 code on the older 4-slot cRIOs.
To use the 2015 LabVIEW software on a cRIO, the cRIO must be reformatted to v54 or later, using a new FRC CRIO Imaging Tool found at C://Project Files/National Instruments/LabVIEW 2014/project/CRIO Tool

We can also keep the existing environments we used last year around just to program the cRIOs. Last season's LabVIEW and Java don't expire, but c++ does so C++ will need a new toolchain to continue supporting the older cRIOs.

So
-------------
Option 1: LabVIEW & Java Can Use Existing Setups to program cRIOs
Java teams can continue using Netbeans with the old libraries
LabVIEW license from last season never expires (just other years) - caution: don't install LV FRC 2015 on the same machine with last year's LabVIEW, because some conflicts with common names may result.

Option 2: C++ WindRiver Expires, so Use a Different Setup
C++ teams can use the project located on FIRSTForge here: http://firstforge.wpi.edu/sf/projects/c--11_toochain

Option 3: LabVIEW-Only New Software Will Work on cRIO II
Backward compatibility for LabVIEW w/ 4-slot cRIO only

[harding3202]

We found the imaging tool but when we tried it this error came up. Anyone have any ideas to what or where we can find the file or what might be wrong.

Error Message:
Unable to complete operation because of unexpected error:
Error 7 occurred at File/Directory Info in ConfigUtility.lvlib:ReImageTarget.vi->ConfigUtility.lvlibialog.vi

Possible reason(s):

LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS X, and / on Linux. Verify that the path is correct using the command prompt or file explorer.

C:\Users\Developer\AppData\Local\Temp\lvtemporaryd _591025\cRIOFRC