Old cRIO resurrection with LabVIEW

We are trying to use a couple of our old cRIOs to make entry-level programming test beds for new students. We realize none of the new features run on the cRIO but it’s still a viable sandbox for rookie programmers to learn the basics of LabVIEW.

I’ve installed LV2014 along with the FRC updates and the cRIO responds to its IP address via the imager tool (latest image on board is v52). When I start a new project in LV2014 I get an error I can’t resolve.

It has been a while since I messed with this but I suspect your computer is not on the right subnet.
First played games with the IP mask (subnets). The default mask for a 10.xxx.xxx.xxx is Your computer is probably on a 192.168.xxx.xxx with an IP mask of If so your computer will not talk to the Crio. Your computer needs an IP address of 10.40.4.xxx with the xxx being anything but 2.

The FRC imaging tool is special case that can search for nodes not in your subnet.

You can try pinging the Crio. To test this

We have setup a second NIC with persistent routes for the cRIO only. It does reply to a ping (see attached) . This error happens when I first create a new robot project. I’m not even at the point of uploading code yet. I didn’t think the target (cRIO) had to even be present during that time.

1055 usually means that some software being referenced is missing.
So, when it is pulling your new project together it cannot find pieces.

That often occurred in 2014 when the software was installed either out of order, e.g., the FRC specific before the LV2014, or possibly when there was another version of LabVIEW on the same machine and mismatched pieces were getting pulled in, or just a corrupted installation.

I’d suggest that you uninstall all NI software on one of your machines, then reinstall LV 2014 followed by the 2014 FRC specific piece.

The error is likely tied to the NI CompactRIO driver. Since you have both the 2021 and 2014 software installed in the same machine, the installer upgraded the driver to the one that ships with 2020, which does not support LabVIEW 2013 anymore.

I replied to the conversation in your NI forum post, as well. I recommend continuing the conversation there, if needed:

Re: Using old cRIO (4-slot) with LabVIEW 2014

Installing LV2013 with the FRC2014 updates on a separate PC does the trick. I can now create and deploy projects to the cRIO. Thanks everyone for the comments.

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.