01-09-2025 05:23 AM
Hello everybody,
at the moment we are setting up a new computer with LabView 2021. Previously we were using LabView 2014 on a different computer which shall be kept like it is to have always the possibility to step back to the old running version of LabView if there are any malfunctions in the 2021-version.
In addition to the software, we are using a cRIO-9067 which was used with the 2014-version and shall be used again with the 2021-version. To make sure, to be always able to step back to the 2014-version we are looking for a way to backup the driver-software of the cRIO as we are afraid that the driver is updated once I connected the cRIO with the 2021-version. We guess that in that case we wouldn’t be able to use the 2014-version in connection with the cRIO. We have to avoid this scenario.
As operating system on the cRIO we have "NI Linux Real-Time ARMv7-A 3.2.35-rt52-2.10.0f0" and the firmware version "3.0.1f0".
Our first general question is: Does anybody know if the cRIO-driver is updated automatically when we connect it to a newer desktop LabView-Version (here 2021) or is absolutely necessary to do this update manually e.g. by USB-Stick/Ethernet?
And our second question is then, what would be the best way to backup my cRIO-driver? So far, we have researched the following methods:
Replication and Deployment Utility (RAD): This looks like the most promising solution but when we wanted to install the software it said, that updates for system components were going to be done. That’s why we didn’t finish the installation as we wanted to prevent automatic updates to happen to any system components of the 2014-version. This version shall be untouched.
We have also tried the “Create-Image (Folder)”-Function: We have tried to implement this function into our main VI and also created a separate VI but always got the error message “−2147467263 - Not implemented”. As “session in”, we selected the NI-cRIO-9067. A screenshot of th setup is attached. Is this method even suitable for creating a backup of the cRIO-driver software or do we have to work with it?
Thank you very much for your help.
Best regards,
LenJo
Further information about our software versions:
cRIO: 14.5.0
NI-DAQmx Device Driver 14.5.1f1
NI-DAQmx ADE Support 14.5.1
NI-DAQmx MAX Configuration 14.5.1
DIAdem 2014 14.0.0.5641
NI I/O Trace 15.0.0f0
LabVIEW Runtime 2012 SP1 f9 12.0.1
Measurement & Automation Explorer 15.0.0f0
Measurement Studio Visual Studio 2010 Support - See individual versions below.
DotNET
Common 13.5.40.173
Common (64-bit) 13.5.40.173
NI-USI 14.0.0.5640
NI PXI Platform Services Configuration 15.0.0f1
NI PXI Platform Services Runtime 15.0.0f1
NI-RIO 14.5.0
NI R Series Multifunction RIO 14.5.0
NI FlexRIO 14.5.0f0
NI-PAL Software 15.0.0
NI 1588-2008 Network Management 15.0.0f0
NI-Serial Runtime 14.0.0f0
NI-Serial Configuration 14.0.0f0
NI System Configuration 15.0.0f0
NI-VISA 15.0.1
NiVisaServer.exe 15.0.0.49152
NIvisaic.exe 15.0.0.49152
NI-VISA Runtime 15.0.1
LabVIEW 14.0.0
Database Connectivity Toolkit 14.0.0
Datalogging and Supervisory Control 14.0.0
FPGA 14.0.0
MathScript RT Module 14.0.0
Real-Time 14.0.0
Real-Time Trace Viewer - LabVIEW 2014 Support 14.0.0
Report Generation Toolkit For Microsoft Office 14.0.0
LabVIEW Runtime 2013 SP1 f2 13.0.1
LabVIEW Runtime 2014 SP1 f11 14.0.1
01-09-2025 10:56 AM