Problem installing software on cRIO 9040

[idc12]

Similar issue to others reported on the forum but as far as I can tell the cRIO 9040 is still compatible with the latest software.

I have downloaded on to the host PC all the latest NI software needed for the cRIO as advised in the documentation.

I also have on the host PC an older version of the NI Compact RIO software from the previous time that I went through this exercise (vsn 18.1)

For the cRIO as received (not latest NI Linux RT System) NI MAX gives me the option to load the legacy Compact RIO software but nothing current. (Screenshots provided)

Thinking that I needed to upgrade to the latest NI Linux RT System I installed the current RT System on a different box (takes forever!!).

However having done that it is now not giving me any options to install the Compact RIO software. (Again screenshots provided)

What am I missing? I have a colleague who is trying to do the same thing and because he doesn't have the legacy software installed on his system he is completely blocked from installing anything.

[ZYOng]

Is your cRIO-9040 connected to the internet? The RT target itself must connect to the internet.

[idc12]

Thanks for responding.

No the cRIO-9040 is not connected to the internet. I didn't know that was a requirement. Is that new thing with the newer Linux RT System?

I seem to be able to load the legacy software with the older Linux RT System on the cRIO without being connected to the internet.

Do I need to try the 'Install Offline' option? 

[AustinManinTown]

Short answer, connect the cRIO to the network, make sure https://download.ni.com/ is accesable and you should find the installation experience a lot easier.

Like most Linux distros, NI Linux RT uses a package manager, OPKG. NI MAX hides what is happening, but on the cRIO OPKG is downloading packages and installing them. If you open an SSH shell to the cRIO you can execute the opkg command and install other packages.

If you are curious, Google OPKG and you will find plenty of information on how to use it and available packages. Disclaimer; there is no guarantee 3rd party packages will work on NI Linux RT.

The legacy installers had the software on the host machine. If you want to replicate that behavior you will need to download the offline installer. The OPKG package manager will use the host PC to download packages.

My advice is to install software online first, as it is easy, then try the offline method. 

[idc12]

Thanks David. I appreciate the help and the detail. I kind of half understand what you are saying but I am not an expert on Linux

I understand the suggestion to use the OPKG but how would I know which packages I needed to install?

I would prefer to use MI-MAX if possible.

I took the cRIO out of Safe Mode and got a bit further. Screenshot is attached. The message is puzzling because it seems to require that either the target or the host PC needs to be able to access the feeds. The host PC can definitely access them, I checked using the link in your reply

One other puzzle. I don't see the benefit of the Install Offline option unless I am not using it correctly

Up to now I have been downloading all the packages that I thought I needed to my host PC.

Today I used the Install Offline option but when I tried to run it, it just seemed to be trying to download the same packages to my host PC. In fact it decided that there was nothing it needed to do. Am I supposed to copy that file to the cRIO and run it there?

[ZYOng · Accepted solution]

To use the Linux RT System Image OPKG installation, your cRIO itself must connect to the internet to have access to the online feed.

The screenshot you provided is showing that the cRIO is trying to access the online feed. If you follow the steps in Installing Software to Offline NI Linux Real-Time Targets correctly, it will not access the feed from http://download.ni.com but http://<host-pc-ip-address:port>

[idc12]

Thank you ZYOng and also to David C for his helpful comments.

Following the steps in Installing Software to Offline NI Linux Real-Time Targets solved the problem.

Appreciate you both taking the time out to help me. Thanks