06-23-2021 11:33 PM
I'm currently receiving a reproducible error when attempting to apply a system state to a cRIO-9065, via our SystemLink server. The state was created from a cRIO-9065, and I receive an error when attempting to apply the state to the same, or other cRIO-9065 systems.
I have been able to use this SystemLink server to deploy states to other types of CompactRIOs in the past without any issues. The states that have succeeded in the past were for CompactRIO's with the NI Linux Real-Time x64 architecture, rather than cRIO's with the NI Linux Real-Time ARM architecture like the cRIO-9065.
I'm using SystemLink version 2020 R2.
The cRIO-9065 devices are setup with the 2020 Q1 Linux RT System Image.
I'm able to install additional packages through NI MAX to the cRIO-9065's as normal, but I receive the state deployment error regardless of the packages installed on the cRIO-9065 when I attempt to deploy the state. I receive the error on systems with packages already installed, and on a system with only the base Linux RT System Image installed.
SystemLink reports the following error under the Detailed Results section of the job history entry related to the failed state deployment:
"comment": "The following packages failed to install/update: ni-sysmgmt-sysapi-expert=22.214.171.124152-0+f0
845 targeted packages were already installed",
Has anyone had issues deploying states via a SystemLink server to ARM based cRIOs in the past?
06-24-2021 07:21 AM
Does your state include a System Image and if so what version. In addition, what version of the system image is currently installed on the cRIO-9065.
06-27-2021 08:52 PM
The system image currently installed on the cRIO-9065s is the "2020 Q1 Linux RT System Image".
I didn't think RT system images were included as part of a Systemlink state, but I may be wrong about that. I created the Systemlink state from a cRIO-9065 which had the same 2020 Q1 RT System Image installed, in addition to a couple of other drivers.
The other software I had installed on the cRIO, and included in the state is:
I even seem to receive the error when I perform the following: