NI Home > Community > NI Discussion Forums

Components

Showing results for 
Search instead for 
Do you mean 
Reply
Member
Terje
Posts: 73
0 Kudos

Re: cRIO Information (CRI)

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

Active Participant
Christian_L
Posts: 662

Re: cRIO Information (CRI)

[ Edited ]

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.

Christian Loew, CLA
Principal Systems Engineer, National Instruments
Please tip your answer providers with kudos.

Any attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system,
or for use in hazardous environments. You assume all risks for use of the Code and use of the Code is subject
to the Sample Code License Terms which can be found at: http://ni.com/samplecodelicense
Member
Terje
Posts: 73
0 Kudos

Re: cRIO Information (CRI)

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

Active Participant
Christian_L
Posts: 662

Re: cRIO Information (CRI)

[ Edited ]

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

 

 

Christian Loew, CLA
Principal Systems Engineer, National Instruments
Please tip your answer providers with kudos.

Any attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system,
or for use in hazardous environments. You assume all risks for use of the Code and use of the Code is subject
to the Sample Code License Terms which can be found at: http://ni.com/samplecodelicense
Member
Terje
Posts: 73
0 Kudos

Re: cRIO Information (CRI)

Thanks for the update Christian.

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

 

Terje

Active Participant
Christian_L
Posts: 662
0 Kudos

Re: cRIO Information (CRI)

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.

Christian Loew, CLA
Principal Systems Engineer, National Instruments
Please tip your answer providers with kudos.

Any attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system,
or for use in hazardous environments. You assume all risks for use of the Code and use of the Code is subject
to the Sample Code License Terms which can be found at: http://ni.com/samplecodelicense
Member
Fro2
Posts: 47
0 Kudos

Re: cRIO Information (CRI)

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.

Member
Kokosinela
Posts: 62
0 Kudos

Re: cRIO Information (CRI)

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

Active Participant
Christian_L
Posts: 662
0 Kudos

Re: cRIO Information (CRI)

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.

Christian Loew, CLA
Principal Systems Engineer, National Instruments
Please tip your answer providers with kudos.

Any attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system,
or for use in hazardous environments. You assume all risks for use of the Code and use of the Code is subject
to the Sample Code License Terms which can be found at: http://ni.com/samplecodelicense
Member
Kokosinela
Posts: 62
0 Kudos

Re: cRIO Information (CRI)

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