NI cRIO-9012へのsshを利用した接続

現在、NI cRIO-9012 CompactRIO Real-Time Controllerを利用しております。別の計算機からFTP 及び Measurement & Automation Explorer で9012にアクセスすることはできますが、sshでアクセスすることは可能でしょうか?
なお、調べた限りcRIO-9012のOSはVxWorks 6.3のもようです。

坂本さん
こんにちわ。
cRIO-9012のOS -- VxWorks だとSSHをサポートしていないらしい。
cRIO-9068などNI Linux Real-Time OSを搭載されている型番だと、SSHの設定がMAX上で出来ます。
下記のリンクをご参考ください。
NI Linux Real-Timeが提供する新機能
よろしくお願いします。

Similar Messages

Need help with Call By Reference on cRIO-9012

I have a RT application running on a cRIO-9012 in which I am attempting to establish references to a variable number of clones of the PID Autotuning (Temperature).vi, and then passing these references to a FOR loop in which I am opening each clone with a Call By Reference node to perform the PID. Essentially, I am trying to make the PID Autotuning (Temperature).vi accept an array of process variables, similar to the behaviour that some of the simpler PID VIs provide out-of-the-box.
The code I am using to obtain the references is here:
...and the code within the control loop where I am trying to do the processing is here:
The problem I am encountering, according to the Highlight Execution tool, is that all inputs to the Call By Reference node are present and reach the node, but all processing stops at this point on the first iteration and the cRIO hangs. I cannot stop the SubVI or the RT parent VI without performing a software restart on the target.
I don't know if I am using the Call By Reference node or Open VI Reference functions incorrectly, or if there is a problem with the VI being part of a library, or if something else is wrong. Any help would be appreciated.
Sean

I'm not sure this is your issue, but I think there's a conflict between opening a bunch of rereferences, and then setting the asynchronous call pool size for one of them.You don't need asynchronous execution here, you just need reentrant parallel execution (you may not even need the parallel part; your current code, if it worked, would execute sequentially, and the PID calculation is just math so should be quick and may not benefit from parallel execution). You do need reentrant execution to maintain separate data spaces.
Try opening the references with the 0x08 (Prepare for Reentrant Run) flag instead. Remove the Populate Asynchronous Call Pool. If this works, you can run in parallel by enabling For loop parallelism - but you might find that's actually slower, especially on a cRIO.

CRIO 9012 USB fix drive letter

Hello All!
I am using cRIO 9012 controller with 9102 chasis along with NI 9802 and IO modules in a system. I am logging data on SD cards and on USB drive connected with controller via USB port. I am using cRIO 2.4. Is there any possibility so that whenever I connect a USB
drive
to the controller and controller will assign a fix Drive Letter say
U without taking into account that the NI 9802 SD cards are mounted
or not. The problem is when I start the application.
Regards
Mani

Thanks for the VI Mangus,
From investigating the behavior, I'll help describe what is happening with your system to give a better understanding. When power is cut at some future time, anything thats using a FAT file system can and does become corrupt if its not properly shut down. So, as you have seen, when your application loses power, if the SD cards have not been un-mounted properly, then when we attempt to mount the Card, the software sees that the FAT file system has become corrupt and requires a run of chkdsk to recover it before we can mount again.
Now, this is different than some other OS versions, as others (Windows, etc.) are more lenient on the mount side. There are lots of minor corruptions that they are lenient enough to mount anyway. NI had an explicit desire to be strict and not lenient in these cases as if we mount filesystems that are corrupt in this way we might be overwriting any data that your application may have generated. So, currently, a proper system should have a way to provide a safe shut down procedure so that File IO can have time to close and un-mount the SD card. This could be done with an external battery on the input and monitoring on the RT controller on which Power Suppy Input is being used. See the Tutorial Designing High Availability Systems with CompactRIO and Compact FieldPoint for some more information on this subject.
We have considered providing a method to explicitly Mount and SD card even though its a little bit corrupt so please file a product suggestion if you would like to see this feature.
Let me know if you have any questions.
Thanks,
Basset Hound

Doubts using NI cRIO 9012 and NI 9111..

Hello.. i'm using NI cRIO-9012, NI-9111, NI 9234, NI 9201 and NI 9474 in a school project... i started to do some easy things like sine wave acquisition in order to be more in touch with the labview hardware and software, the software that i'm using it's the LabView 2009 Service Pack 1.
i have acquired the sine wave with NI 9234 and NI 9201 and i couldn't find the diference between this two modules, is there any thing that i can do with one of them and couldn't do with the other? what's the main diference between them?
i couldn't realise either how many points am i acquiring at each period (acquisition rate i think) of the wave? (would you like me to send the code?)
from these two modules i got something, from the NI 9474 i've saw nothing yet... i was trying to generate PWM wave and i use the FPGA help wizard to generate the code, everything was fine but i couldn't get anything.
I hoping that someone can help me..
Thanks
Mário Silva

Hi Maxime,
thanks for answering, i took a look at the links you gave me and one of them i've seen it before (cRIO Pulse Width Modulation) but i must tell you that i'm new at labview and those VI's are too much for me to carry yet =) ....
About the engine times i've told my doubt was, should i use Single Point Continuous or Single Point Timed I/O to create PWM??
I tried Single Point Continuous and i'll let you know the VI's i've used...I could see that by changing the values of Active Time and Period the brightness of the little led at the output port was changing too but there was nothing appening at the scope. The signal just change all to zero or all to my source signal (12V), there's no PWM oscillation.
About the code i have some questions too, i can't understand how some subVI's are created, how are they conected with the FPGA and HOST and what are they for..
there are some blocks that appear when i run the FPGA Wizard that i can't find when i creating a blank project, i think that they has to do with the subVI's i told you and some dependencies too.
I really appreciate your patience, thanks a lot.
The best regards
Mário Silva
Attachments:
Single Point Continuous PWM_fpga.vi ‏54 KB
Single Point Continuous PWM_Host.vi ‏312 KB
FPGA_doubt.png ‏123 KB

CRIO 9012 Hardware Error

Hallo,
Ich habe ein Problem mit einer cRIO 9012 Steuerung.
Die Steuerung ist über die TCP/IP Schnittstelle in einem Netzwerk mit einem Prüfrechner und verschiedenen anderen Komponenten verbunden.
Nach ca. 1 Jahr Betrieb stürzt die Steuerung wärend verschiedenen Messungen ab. Eine Kommunikation mit der Steuerung über TCP/IP ist dann nicht mehr möglich und auch die SPI Verbindung mit dem FPGA läuft nicht mehr.
Im selben Netzwerk ist noch eine baugleiche zweite Steuerung an einem Baugleichen Prüfstand auf welchem auch die selbe Software läuft. Dieser Prüfstand läuft ohne Probleme.
Gibt es eine Möglichkeit die Hardware zu überprüfen?
Können Fehlerprotokolle oder ähnliches den Absturz dokumentiert haben?
Danke,
Gruß Tom

Guten Morgen gmeinder,
ich würde erstmal probieren, ob eine Formatierung des cRio und das neu Aufspielen der Software das Problem lösen kann.
Eine Anleitung habe ich dir unter diesem Link:
http://digital.ni.com/public.nsf/allkb/6B1343F61905203386257051006573CA
Gib bitte bescheid, ob es funktioniert hat
Liebe Grüße,
Abdülkerim
Abduelkerim
Sales
NI Germany

How does a crio 9012 act if it is in safe mode?

How does a crio 9012 act if it is in safe mode?

Have you read the manual?
It is in there.
André
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

I would like to zip files on a cRIO 9012 RT platform.Are there any suitable VIs?

I've been trying to find a way to zip folders (that contain numerous TDMS and TXT files) on a cRIO RT platform.
Zipping the same folders on windows results in zipped files 10 times smaller.
It would be fantastic if I could do the same on the cRIO before these files have to be downloaded to a computer (through FTP which takes an extremely long time and freezes for several minutes the computer that receives the data).
Any help will be greatly appreciated!
Theo

For anyone who's pursuing the same goal, I have received some feedback from NI which I am including below.
If you have succeeded to zip files on an RT platform before or know how it can be done please share.
>> The Zip VIs that are available in LabVIEW are aperating system dependent and they do not work on the RT-OS's. So the bad news is that, LabVIEW does not currently ship with RT zip functions. Therefore, officially the answer is no!!
>> However, there is some good news, another customer provided a solution on our discussion forums. The OpenG Zip library was reported to work well on LabVIEW Real-Time - both the Pharlab and VxWorks systems. Please peruse the following link. I would recommend reading through the entire thread, but the useful links appear on the final page.
Unzip Files Within Labview
http://forums.ni.com/ni/board/message?board.id=170&thread.id=199541&view=by_date_ascending&page=1
I will try the above and if I succeed i will update this thread.
Thanks

NI 9214 FPGA I/O items missing (cRIO-9030 / NI 9144 combo)

I have a new cRIO-9030 and NI 9144 EtherCAT expansion chassis which I have configured and added to an existing LabVIEW project containing a cRIO-9012. When I searched for existing targets and devices, the modules were correctly detected (NI 9237, NI 9263 and NI 9265 on the cRIO-9030, and NI 9214 and NI 9477 on the NI 9144 chassis); however, the I/O items listed for the NI 9214 module show only the 16 thermocouple channels (TC0 through TC15). The four additional channels are not shown (Autozero and CJC0 through CJC2), although they did when the module was previously configured for the cRIO-9012. Is this a known / compatibility issue with the NI 9144? or is there a configuration option I am missing? Does the terminal block need to be in place on the module for these I/O items to appear?
Solved!
Go to Solution.

Hey CFER,
You are correct only the thermocouple channels are availble through the scan engine. The availabe channels for each module are documented in the compactRIO help. This should be the same for all chassis. Can you double check the 9012 was setup in FPGA mode? Its easy to overlook sometimes.
Kyle Hartley
RIO Product Support Engineer
National Instruments

9236 enable shunt cal property crashes crio OS with scan engine

I would like to inform users of the 9236 Quarter Bridge Strain Gauge Module of a bug. The Real-Time team is aware of this issue and I have been working with an app engineer on it for about a week and he has confirmed my findings. He says the problem is most likely a driver issue or scan engine issue and they are investigating it.
There is a bug that completely crashes the cRIO operating system with the 9236 module. Currently when a cRIO device is loaded with LV2009 SP1 or LV2010 and using scan engine interface, attempting to write the "shunt cal enable" property of a 9236 module completely crashes the VxWorks OS. If you try to access the property again, the crio crashes and enters an error state where the crio has rebooted twice without being told to. The LED indicator blinks four times to indicate this.
I have tested this with a few different hardware combinations with both the crio-9014 and crio-9012 controllers, combined with either the 8-channel 9104 back plane or the 4-channel 9102 back plane with the same results. The app engineer was able to duplicate this issue as well.
To duplicate the bug:
Load a crio device with 2009 SP1 or LV2010 and configure the device for scan engine. Locate the 9236 module in the project explorer and drag and drop it into a VI to create the IO variable. Right click the output terminal of the IO Variable and go to create > property > enable shunt calibration on a channel. Once the property is dropped, right click on it and do change to write so that you can write a boolean to the variable. It doesn't matter if you write a true or false to the property, the results are the same. Hit run, watch it crash. When it reboots, hit run again. The crio is now in a state that can only be recovered by physically resetting the device.
I love the crio stuff and I use it every day because it is very reliable and robust. This kind of thing is rare, which is why I am reporting it to the community as well as NI as it is a pretty big bug that took me a while to narrow down.
[will work for kudos]

rex1030,
Shunt calibration can be accessed using a property node. The operation will be the same, you still need to acquire two sets of data and compute the scalar.
You can obtain the necessary reference by dragging the module to the block diagram from the project. Please see http://zone.ni.com/devzone/cda/tut/p/id/9351 for more information on programmatic configuration.
Let me know if you have any other questions.
Sebastian

How to monitor memory usage in a cRIO controller?

I have an application where I suspect the customer is operating in a hotter environment than they are claiming. I prepared the RT host vi to log a simple text file directly on to the RT's C: drive. In this case I'm only logging the transition of events when the chassis temperature exceeds 70C and then becomes less than 60C along with a date and time stamp. (It's not continually logging data.) However, I'm concerned that over time (i.e months from now after I've long forgotten the project) the file will get overly large and affect system operation. There are articles that deal with memory management but I'm not sure how to interpret them. They talk about RAM. Is RAM the same as the C: drive on the controller? How do I determine the available memory on the C: drive; like using "dir" in the old DOS days? What is the best Knowledge Base article that deals with this issue. This system is a stand alone application. (The host PC is not normally connected.) I am using a cRIO-9012 controller and LV v.8.6.
Dave

RAM on the controller is not the same as the C: drive. With respect to the controller, you can think of it in the same terms as your computer. RAM is volatile memory and your C: drive is non volatile flash memory.
Depending on the frequency of the temperature excursions above and below your 70C threshold, the service life of the controller and the method you used to append to the file, there could be a number of issues that may creep up over time.
The first, and the one you brought up is the size of the file over time. Left unchecked this file could grow continuously until the system literally runs out of flash memory space and chokes. Depending on how your are appending data to this file, you could also use more than a trivial slice of processor time to read and write this big file on disk. While I have not personally ever run one of the RT controllers out of "disk space", I can't imagine that any good could come of that.
One thought is to keep a rolling history of say the last 3 months. Each month, start a new file and append your data to it during the course of the month. Each time a new file is created, delete the data file from something like 3 months ago. This will ensure that you will always have the last 3 months of history on the system, however the monthly deletion of the oldest data file will limit you to say 3 files at whatever size they happen to be. Unless there are hundreds of thousands of transitions above and below your threshold this should keep you in good shape.
I also eluded to the method you use to write to this file. I would ensure that you are appending data using the actual file functions and not first reading in the file, appending your data as a string then writing the entire file contents back to disk. In addition to causing the highest load on the file system this method also has the largest system RAM requirements.

Passing array to call library function running on VxWorks (cRIO)

Hello,
I am using a cRIO 9012 running VxWorks.
I have a Call library function VI in my application and I want to pass arrays of doubles to this function.
The problem is that I can not access the values in the array.
Here is the source code of my function:
#include "D:\\Programme\\National Instruments\\LabVIEW 8.5\\cintools\\extcode.h"
double avg_num(double *in1, double *out1)
    double ret;
    ret = in1[0] + out1[0];
    return ret;
The value of in1[0] and out1[0] is always.
When passing no arrays but single values, all is fine. But since my application is more complex than this example, I need to pass arrays.
The block diagram and parameter specification is as shown in the attached screenshots.
I am compiling the source code with the Gcc 6.3 which is available here:
http://zone.ni.com/devzone/cda/tut/p/id/5694
What am I doing wrong?
Or is passing arrays not supported on cRIO?
Maybe the makefile needs to be modified?
Thank you.
Best regards,
Christian
Attachments:
vi.JPG ‏88 KB
parameter.JPG ‏41 KB

I guess I have solved the problem.
The key was to set the parameter "Minimum size" for all function parameters to <None>.
Having this, I can read the passed arrays. I do not know why this works but at the moment, it is ok for me.
Thank you all.

How to config cRIO... Help.

I am using a cRIO 9012 and am toatally new to Labview and all the NI peripherals. I am stuck with configuring the cRIO for measuring from a loadcell. Am using a universal module for excitation and output from the loadcell.. My problem is i have no idea of how to set the excitation voltage and conversion of the data thus obtained to a millivolt value in the software.

Hello,
The basic architecture for LabVIEW FPGA applications (generally) consists of code running on your FPGA which determines your data acquisition rate. The values are read onto your real-time or Windows based host VI at which point they are converted from integer to the double precision number which they are meant to represent.
It sounds as if you might want to take a look at some of the resources that are available to help get you started programming LabVIEW for cRIO applications. The LabVIEW Example Finder contains some great examples that show the overall architecture for FPGA applications: Help » Find Examples » Toolkits and Modules » FPGA » CompactRIO » Basic I/O. These will also show how the conversion is performed to translate integers to actual values. You may also want to take a look at the resources linked in the Getting Started with LabVIEW FPGA knowledgebase. I hope this information is useful for you. Please post back if we can provide any other additional assistance. Thanks,
Mike D.
National Instruments
Applications Engineer

Using FPGA cRio and 9853 for a J1939 CAN

We are currently trying to interface with a J1939 CAN network using a cRio 9012, 9104 chassis and the 9853 module. We have Labview 8.2. I stumbled accross the examples for Labview 8.6 and newer. Is there any particular solution/road we should be going down?
I have experience using Labview with a cDAQ, but have not much experince with RealTime and FPGA.
I got the thermocouple module to work using FPGA, so the RIO itself and the module do work.
Thanks for any guidance/help you can send my way.

The way I would approach J1939 on the cRIO would depend on what features of J1939 you needed for your app. If you are just reading or writing broadcast messages that fit in a single 8 byte frame it will be just as straight forward as standard CAN. Basically in this case you would be reading frames on the FPGA code, transmit them to the realtime portion where you can convert them to channel data using a CAN database. Writing would be just the opposite direction.
If you are using requests for PGN data, lets say to retrieve DTC codes, or R/W data using advance diagnostic messages (say DM14/15/16 for example) things will get a bit more difficult but not too bad. If you are expecting to tx or rx multi-frame packets and need the transport protocol of J1939, then things can get complex fast.
DMC recently developed a set of J1939 protocol drivers for LabVIEW which are based on the NI-CAN channel API. The drivers were written in LabVIEW just like the NI frame example, but provide functions at a layer above the base CAN channel API layer. This allows the simultaneous capture of data from both J1939 packets which are simple broadcast CAN frames, or more complex transport using BAM, including extended data frames.
I suppose something like this could be written into the realtime of the cRIO, and just pass frame data back and forth using some very basic code on the FPGA.

String-to-path does not work on cRIO?

I am running LV8.20 on my laptop and cRIO-9012. The laptop runs Win XP SP2.
From the attached snapshot, you can see that I am trying to form a file path from concatenated strings, using the string-to-path node. When I run this vi in Windows target, it works perfectly. The "x=y?" boolean returns true.
When I run it on CompactRIO, I get error 1430 ("The path is empty or relative. You must use an absolute path."). The "x=y?" boolean returns false. I have already created the "paths" subdirectory on cRIO with an FTP utility. If I wire the file path definition constant (as opposed to the one generated by string-to-path) directly to the "open file" node, cRIO recognizes it and writes the file... usually!
What am I missing? Any help is greatly appreciated.
By the way, I don't know how the "Wait for front panel activity" nodes work (also shown in the snapshot), but they certainly don't seem to cause the program to wait for front panel activity. Both in Windows and cRIO targets, they seem to be completely ignored.
Attachments:
string-to-path.PNG ‏13 KB

David:
Most of the time, this error is thrown when LabVIEW FPGA cannot resolve a specific I/O node used in the FPGA VI. It is possible that the name of an FPGA I/O was changed in the Project Explorer with
the FPGA VI closed and then the FPGA VI was compiled. Since the FPGA VI was not updated with the new I/O node, LabVIEW FPGA cannot resolve the specific IO node reference.
In order to verify that this is actually the source of the problem, create a new project from scratch which includes some I/O, create a new FPGA VI that uses these I/Os and then try compiling it. If the compile is successful, then the resolution to this problem would be to check the original FPGA VI and make sure that it has valid I/O nodes corresponding to the ones defined the Project Explorer.
I hope this helps and please let me know what you find.
Regards,
Rudi N.
Message Edited by Rudi N on 04-24-2007 02:27 PM

How to use cRIO USB mass storage?

Hi,
I am using the NI9215 as an analog input port and want to write the data into an external USB mass storage which is connected in the
cRIo-9012 USB port. I do not have any idea how to write the data into USB mass storage, does anyone can give me some help?

Differences among brands and models are due to the fact that certain devices take greater liberties with the USB mass storage device specification than others. A venerable operating system like Windows (or even Linux) is shot through with workarounds for device- and manufacturer-specific issues that are not present (as much) in VxWorks, which is the OS used on the cRIO-9012. Therefore only devices that adhere very rigorously to the specification are going to work properly.
Unfortunately, degree of adherence to the USB spec is not something that's generally published about a device, nor is there any sort of official certification process. So to some extent it's trial and error. I am working with our support enginners currently to develop a list of devices that NI certifies as interoperable with VxWorks, and also VxWorks is increasing the robustness of their USB support with every release.
EDIT: And the advice about reformatting the device is very sound. The cRIO-9012 does not support the NTFS file system, only FAT 12, 16, and 32. If the USB device is formatted for NTFS, it will not function properly.
Finally, if anyone sees a storage device that fails to work properly despite all these suggestions, please post as much information as possible (model number, manufacturer, capacity). Having this information will allow us to work with the manufacturers of VxWorks to improve USB support.
Message Edited by CharlesC on 02-22-2007 12:12 PM

NI cRIO-9012へのsshを利用した接続

Similar Messages

Maybe you are looking for