file system on cRIO9014?

[zerosun]

HI @ all

I am looking for Info about the file system that runs on my cRIO9014, the system has the following components installed:

• LabVIEW real-time 9.0.1
• Web Server for LabVIEW RT 2.0.0
• Network Variable Engine
• NI-RIO 3.4.0
• NI-VISA 4.6.2
• NI-VISA Server 4.6.2
• Run time engine for web services 2.0.1
• System state publisher 1.1.0
• Variablen client support for labview rt 1.6.1

I would like to know which file gets generated and where does it end up, when I deploy my RT-App?  

Thanks for your help

[M_Berggren]

Hi

Have you made a build specification for the RT application? When you build this, it generates a file structure equal to the one used on the cRIO device: <local build destination>\c\ni-rt\startup. Another important file is the ni-rt.ini found in the root of the cRIO disc.

I don't know if any files are saved to the cRIO if you deploy/run a VI directly, without a build specification.

best regards

Michael

[zerosun]

HI

I know that thanks, I am interested in a little bit more detailed Information. For example, I installed LabView Real Time 9.0.1 and in the figure below you can see what MAX did.

I would like to know which file does what and what the folders are for. I use different software packages (web server, ni rio, visa, scan engine, variable publisher) and I lose the overview. That is why I like to have more Info about what MAX installs and how LabVIEW works with that.

Thomas

[Tanya_V]

Hi zerosun,

The top-level directory on your cRIO will contain your configurations files and error files.

Within the ni-rt folder you will have your startup folder. In 'startup', you will have your startup executable and associated data.

Also within the ni-rt folder, in the system folder, you will find all the operating systems files.

Within the temp directory you will have the log files.

Take care!

[zerosun]

Hi Tanya,

The point is to deploy the cRIO software without the labview development system.

1)      Install Software (MAX) on cRIO , in this case:

1. LabVIEW Real-Time
   1.                                                                i.      Web Server for LabVIEW RT
2. NI-RIO
3. Language Support for LabVIEW RT
4. NI-VISA
5. NI-VISA Server

2)      Use RIO device setup to deploy FPGA bit file

3)      Copy Paste startup folder [RT build] to the RT target [ftp transfer c:\ni-rt\startup]

I still have to change the ini file on the RT target.  Maybe more?!

INI file: (changes to make for deploying by hand on a new system)

Line 53: change switch on the webserver

Line 58: change RTTarget from startup.rtexe to my_program.rtexe

Line 60 to 65 are all new ?  when the rt target gets deployed, it creates 6 new entries?

I did not know that because I did not found information about what happens when I deploy on a target.

Lets say I have a cRio system and I have different applications that I want to run on it.

I thought it would be enough to save the different FPGA bit files and the different RT builts and just exchange them on the target. But that doesn’t work. I don’t have the possibility to run a development system beside every cRIO system.    

Do I need an aliases file when I don’t use “system sate publisher” or “variable client support …”?

What is the “depinstr.bin” file for, which gets created with the RT built?

thank

thomas

[M_Berggren]

I suppose you've found the RTTarget.LaunchAppAtBoot key.

NI: The deployment process for cRIO systems really should be simpler. It would be neat to be able to build an installer in the same way as for the PC application. I'll post that in the Ideas exchange.

best regards

Michael

[speleato · Accepted solution]

Hello Thomas,

Have you seen the RT System Replication Tools (http://zone.ni.com/devzone/cda/tut/p/id/3937)?

I haven't used them myself, but based on the Dev Zone article, you should be able to make and store a number of different images which can then be deployed to your cRIO targets.

Sebastian

[zerosun]

thanks man

i think that will work

It was always there :-)...

Regards Thomas