topic Re: cRIO Information (CRI) in Components

cRIO System Configuration Information (CRI) Library

Christian_L — Mon, 16 Jun 2025 21:51:44 GMT

Post your questions or feedback on the cRIO Information (CRI) library here.

Re: cRIO Information (CRI)

StevenA — Thu, 26 Jun 2008 16:38:58 GMT

Thanks Christian... I look forward to trying it out.

Re: cRIO Information (CRI)

JoeC — Wed, 25 Feb 2009 02:05:40 GMT

In the Dynamic FPGA Code Selection section of the document, the paragraph states, "Using the CRI component you can detect the current configuration of modules in the backplane and can then select the proper FPGA bitstream to download and run. This detection and selection of the FPGA bitstream will be part of LabVIEW Real-Time application running on the cRIO controller."

How do you programmatically pick an PFGA bitstream to download? Is there a function in the CRI library that does this?

Thanks,
Joe

Re: cRIO Information (CRI)

Christian_L — Wed, 25 Feb 2009 20:43:25 GMT

No. Currently you need to include a separate Open FPGA VI Reference node for each FPGA VI/bitstream that you want to run and then select the appropriate node using normal LV programming such as a Case structure.

Re: cRIO Information (CRI)

JoeC — Thu, 26 Feb 2009 18:16:15 GMT

Thanks for the reply. Please allow me to post an theoretical example to see if I understand what you are saying.

Let's say I have a 9205 cRIO module in a 4 slot 9013 backplane. If I wanted to have an application that detected which slot the 9205 is plugged in, I would create 4 different FPGA VIs that were configured for each to have the 9205 in each slot.

I would then use the CRI tools to detect which slot the module is located in. I would then have in my controller application, a case statement with 4 different "Open FPGA VI Reference Function" that will call each of the slot configured FPGA VIs. I assume it is at this time that when an Open FPGA VI Reference Function is called that the bitstream is loaded?

Thanks again for your clarifications...

Joe

Re: cRIO Information (CRI)

Christian_L — Fri, 06 Mar 2009 19:28:02 GMT

JoeC wrote:
Thanks for the reply. Please allow me to post an theoretical example to see if I understand what you are saying.

Exactly correct.

Re: cRIO Information (CRI)

RayKF — Mon, 30 Nov 2009 06:40:03 GMT

Hi,

Does this tool work for R-Series (78xx) cards? Or do you have a separate tool / VIs for the R-series?

Cheers,

-Ray

Re: cRIO Information (CRI)

Christian_L — Wed, 16 Dec 2009 17:58:54 GMT

This tool should work for any PCI/PXI-based R series devices as well, but you will need to add the R series cards as additional backplanes in cri_cRIO Vendor and Components Library.vi which is a VI used to define all of the device IDs that the CRI tool knows about.

This tool will not work for PCIe/PXIe-based boards and devices such as the PCIe-785xR cards.

Device IDs for some R series devices:

PCI-7811R: 0x702F

PXI-7811R: 0x702E

PCI-7813R: 0x7194

PXI-7813R: 0x7193

PCI-7830R: 0x7056

PXI-7830R: 0x7055

PCI-7831R: 0x702D

PXI-7831R: 0x702C

PCI-7833R: 0x7083

PXI-7833R: 0x7074

PCI-7841R: 0x7393

PXI-7841R: 0x7390

PCI-7842R: 0x7394

PXI-7842R: 0x7391

PCI-7851R: 0x7386

PXI-7851R: 0x7384

PCI-7852R: 0x7387

PXI-7852R: 0x7385

PCI-7853R: 0x7395

PXI-7853R: 0x7392

PXI-7854R: 0x73E1

Re: cRIO Information (CRI)

TylerDurden — Tue, 05 Oct 2010 06:36:11 GMT

Hey,

very great set of VIs. We are using these features in a component on our cRIOs. These VIs work with LV8.6.1 and LV2009SP1 very good, but on LV2010 the VI cri_RT Ping Controllers.vi is broken and the VI itself is password-protected. Is there an update for the CRI component or how can we fix this to support our applications with LabVIEW 2010.

Thanks for your replies.

Tyler

Re: cRIO Information (CRI)

Christian_L — Tue, 05 Oct 2010 18:56:33 GMT

@TylerDurden wrote:

In LV2010 the VI cri_RT Ping Controllers.vi is broken and the VI itself is password-protected. Is there an update for the CRI component or how can we fix this to support our applications with LabVIEW 2010.

Attached is an updated copy of this VI.

Re: cRIO Information (CRI)

Terje — Thu, 06 Jan 2011 14:20:45 GMT

These are greater VI and I use them a lot.

Now I have a cRIO with a 9111 backplane which does not seem to be supported by these Vis.

Will they be updated?

Terje

Re: cRIO Information (CRI)

Christian_L — Thu, 10 Feb 2011 15:17:19 GMT

I have attached updated versions of two files which contain all of the model codes for the controllers, backplanes and modules. Please copy these files to your harddrive, replacing the files that are currently there.

cri_cRIO Vendor and Components Library.vi >> ..\LabVIEW xxxx\user.lib\CRI\_subVIs

cri_cRIO Backplanes.ctl >> ..\LabVIEW xxxx\user.lib\CRI\_subVIs\TypeDefs

These files are used to lookup and convert the model code read from the HW to the corresponding controller, backplane or module name. If you have a newer piece of HW which is not listed, you can update these files yourself. By looking at the outputs of the CRI subVIs you will be able to see the model code for your new hardware.

[2/10/2011] Update: The files on the DevZone docment have been updated to the latest version.

Re: cRIO Information (CRI)

Terje — Fri, 07 Jan 2011 18:23:29 GMT

Thanks Christian

I now get the correct information about the backplane, but I don’t get the information about the connected modules which is what I really need. It seems that I need a bitfile for that specific backplane in the CRI Get cRIO Modules Info.vi. If it is possible to get an updated version of these VIs as well, I would really appreciate it.

Terje

Re: cRIO Information (CRI)

Christian_L — Wed, 09 Feb 2011 21:11:57 GMT

I have added two new attachments to the original document on DevZone containing the complete updated version of CRI.

Re: cRIO Information (CRI)

Terje — Tue, 08 Feb 2011 14:45:56 GMT

Thanks for the update Christian.

However, I still don’t get any information about the modules when using a 9111 backplane

Terje

Re: cRIO Information (CRI)

Christian_L — Wed, 09 Feb 2011 21:13:56 GMT

I updated the attachments on the document one more time. Previously I had only updated the CRI Get Remote cRIO Modules Info.vi and forgot to update the local version of the same function.

I also created separate installers for LabVIEW 2009 and LabVIEW 2010 to account for the difference in the RT Ping function.

Re: cRIO Information (CRI)

Fro2 — Wed, 27 Jul 2011 17:59:02 GMT

FYI: Even though you have fixed the subVIs to support the additional backplanes and have the bit files in the installer package. The text on the website still state that only the 9101, 9102, 9103, 9104, 9072, and 9074 backplanes are supported. I installed the CRI package from the LV2010 VIP file and noticed that it does not have the change you made within the “CRI Get Remote cRIO Modules Info” file. Not supporting the additional backplanes. Therefore I downloaded the zip file and overwrote the VI which the VIP installed with the one from the zip file.

Re: cRIO Information (CRI)

Kokosinela — Sun, 05 Feb 2012 13:07:42 GMT

Hello,

I want to use function CRI Get cRIO Modules Info.vi. In control on Front panel of this VI I can choose for example sbRIO-9602,

but in block diagram I see that there is not case which will call proper subVI (e.g bit file). So, is it possible to get support for sbRIO components for reading information about modules?

(I am interested for sbRIO 9602 most)

P.S. Kudos for library

Regards,

Sofija

Re: cRIO Information (CRI)

Christian_L — Wed, 08 Feb 2012 17:17:20 GMT

Sofija,

I'm working on an update of the CRI to include support for recent cRIO and sbRIO additions. I should be able to post a 'beta' version in a couple of days. Can you describe your application in a little bit and how you use CRI in a sbRIO-based application. In the past we have not planned on adding sbRIO support to CRI as we see sbRIO to be used in static applications in regards to HW - we don't expect users to change the HW configuration of sbRIO systems at run-time.

Re: cRIO Information (CRI)

Kokosinela — Fri, 10 Feb 2012 08:32:50 GMT

Hello Christian.

Thanks for update.

I am supporting one customer, who si using sbRIO, and idea of his application is to one of the three slots on 9602 to cover several HW/SW options by
inserting various modules. They wish that the RT recognizes the module and selects the appropriate FPGA bit file. So, acquisition of different type of signals
and processing of those based on module which is required is main idea.

Sofija Poledica
AE Eastern Europe