Start by cRIO

Similar Questions

• cRIO: best way to start/run a VI running on the RT.vi of the host.vi

  Hi all

  I recently (3 weeks) he started to use with Labview/cRIO. I think I have the concept of the cRIO down, but I'm fighting on what seems to be a simple communication in Labview. Here's my problem:

  I have a cRIO 9074 with x 1 NI 9234 (4 analog input channels) and x 3 modules NI 9512 (motor controller). I am running in hybrid mode. My RT.vi control all movements of engine (scan mode) and also the FPGA FIFO beginning/read it. My Host.vi is in fact a UI and did some post processing on the data that I acquire by my NI 9234. My issue is with how to begin the RT.vi of the Host.vi. Just use the "VI reference.vi open? I tried but I do not think I do it properly, because what settings should I get for this? Can I configure it with the IP address of the RT? Also, for the path of the file, where are the screws on the RT?

  Thank you!

  Troy

  Note: The final product must be converted into a .exe. If the implementing method is to open/run the RT.vi automatically.

  Normally you compile the application of RT, deploy and set it as the startup application.  In this way, it will be saved on the internal flash of the cRIO drive and will automatically load when you start the cRIO.  What is an option for you?

• 9033 OR & NI 9870 - series recording parameters do not restart the cRIO.

  Hello

  I have a cRIO OR 9033 with two RS232 9870 cards. The two cards series and their ports do not appear when I turn on the cRIO. When I run my executable in real time, once it crashes, saying: he cannot find the ports I ask. After that it crashes, the channels appear in MAX and VISA resource controls, and when I run the program a second time, it works very well. Why does this happen? Is it possible that I can have the save of the series, so I don't need to have the program crash whenever the cRIO starts?

  I run my program in hybrid mode. I Interface FPGA and including two maps cRIO outside the FPGA target, like this:

  

  I tried the cancellation of the deployment and the deployment of all, but it does not help. It blocks the first time regardless if I execute the suite of LabVIEW Development or if I deploy it as an RT executable and run at startup.

  Here are some pictures of what is happening:

  10-port VISA should be available. The two on the chassis and four for each card to 9870.

  When I start first cRIO, only the ports of two chassis looks for selection in a control channel VISA:

  

  And the channels do not arise to the MAX:

  

  Showing also currently installed software.

  When I go to the settings of NI-VISA 14.0.0 page I see this:

  

  Channels appear here, but nowhere else.

  When I try to run my program, I get this error:

  

  And after the error, the channels appear in LabVIEW and MAX!

  

  

  Series settings will remain as long as I leave the cRIO powered. If I disable, settings series pannals and I need run my program once only it crash before I can use the serial ports.

  I would really like for these settings apply automatically without having it fail the first time.

  Any suggestions?

  I also run hybrid FPGA on cRIO with cards 9870 and 9871 under the scanning engine you are. I also noticed behaviour buggy when accessing the COM ports - for example, if the cRIO running the executable version of his program and you interrupt it to run the same program in interactive mode, often, you receive the error message "missing resources VISA." So what I do is restart the cRIO with the disabled startup application.

  I honestly would not bother to configure anything through MAX when it comes to your cRIO. You configure port configuration programmatically. In the process of initialization of your program, open your bitfile, run it, wait, a few seconds to have everything settle, make a VISA "find resources" and confirm all your ports appear, then use the VISA to configure and open the port by program. This way worked for me.

• An application compiled on cRIO is very slow

  Hello

  I have a RT-application created with LV2009 that runs on a cRIO 9074.

  If I run my app from inside the LV2009, it works in real time on the cRIO, as expected.

  If I compile the same application in a rtexe that must run after that started the cRIO, sample time (10ms) is never reached. It seems that I get the command on each cycle.

  All the parameters concerning the timing of my timed loop are the same in both cases.

  Why is there such a difference? What can I do to run the compiled application in real time too?

  Thank you in advance,

  Christian

  I found the solution to this problem. It makes no sense to specify the call library node must run in the user interface thread. Obviously, there is no UI thread when you run an application compiled on cRIO.

  Christian

• Open FPGA reference fails to run

  Hello

  I apologize if this is covered elsewhere; I found nothing relevant.

  I have a fair size RT application that calls the vi FPGA reference open as the second point during initialization.  The FPGA is compiled and worked fine before with a simpler application of the RT.  When you run the program I probe the wires of the error as well as highlight the execution and the program is just stuck on that vi.

  The vi is configured to point to the FPGA vi in the project.  I tried pointing to the bitfile and the same behavior occurs.

  The goal of the RT is a sbRIO 9631 with NOR-RIO installed 3.5.1 (without scan interface).  I reinstalled it during my troubleshooting.

  So with that, any suggestions?  Otherwise, I can be on the phone with TOMORROW and will post whatever I learn.

  In the same vein, it would be possible that the user interface is simply not updated because you use too many resources on the RT controller. Especially with probes and highlight the running, the transformation of the network might be causing a problem. In the measurement and Automation Explorer or distributed systems manager, you can view the sbRIO here memory/CPU usage:

  http://digital.NI.com/public.nsf/allkb/8C7B655978C8ADFB86256AAE004AD261?OpenDocument

  I would try also to Flash the sbRIO then reinstalling the 3.5.1 drivers on the device and try again. If you had a different version on the target as 3.5, it may have been a fix that resolves this.

  Finally, try to have the FPGA vi to run when load/run when starting the crio by following these KBs:

  http://decibel.NI.com/content/docs/doc-3076

  http://digital.NI.com/public.nsf/allkb/BC513C2A0DC29C89862574BF0002B0B9?OpenDocument

  Thank you

  D Smith

• I want cRIO to start and stop the acquisition by push physical button on the cRIO, is this possible?

  When you use my cRIO 9024 on the ground, I prefer to be able to start and stop the acquisition with pressing a physical button on cRIO.

  I want to say I don't want it to be "as a start-up," I don't want cRIO to start the acquisition as soon as the power supply is ensured.

  Is this possible?

  Hi Cashany,

  you will surely find this switch status. But there are easier ways (but more expensive) for a button. Fiddling with a pen or a small screwdriver to switch USER1 is not what I call "user friendly"...

  -You have at least 2 voltage inputs on your module available. Use a switch voltage on the power inputs. Use a 'real' button!

  -You have an available serial port. You can set some pins on GND or voltage and check their status inside the cRIO/RT target...

• How to start the new vi on cRIO?

  Hello

  I want to do two things:

  (1) I would first of all a new vi of the cRIO level but the vi is on the host computer. I thought to use the Invoke method: run a VI, but I don't know how to use it with cRIO and two different paths. I hear cRIO a c drive and host as well. What I do now, I start the vi on the cRIO and after on the host, but I would like it automated.

  (2) I have two vi running, we're on the host computer and on the cRIO. They have two different times. The cRIO has 10ms on the host 20 min. How is possible to stop at the same time? I mean to interrupt the vi on the host between cycles?

  Thanks for any help.

  Best regards

  Kamil

  Hi Kamil,

  It is possible to interrupt a loop timed from somewhere in your code, but please be careful with him.

  If Cancel you a timed loop, so not sure what actions were performed in the timed loop and who do not have.

  As an attachment, you can find an example that illustrates the error that appears when the abandonment of one loop timed.

• cRIO compiling code another start-up

  Hi, I compiled (build start-up) a standalone application on cRIO and it works well.

  Now when I plug the Ethernet cable into the cRIO to connect to cRIO to remove the previous application and build another, I can not connect to the cRIO due to the following error.

  I was wondering how to solve.

  

  First steps - confirmed that the networking for the cRIO is still correct? When you plug the ethernet cable, you can test the cRIO (command line)? You see the cRIO able and Automation Explorer? If you can't access it at all, then there is a network problem. Check your IP address and the firewall settings.

  The cRIO has a set of DIP switches, which disables any startup application. If you set this switch, and then reboot the cRIO, you can then connect? If so, there might be a problem with your startup application - perhaps you have a loop with no wait which prevents background networking tasks to run (like allowing connections in the development environment).

• Error getting started example 1 cRIO MDK

  Hello

  I have a problem with my MDK for the cRIO (April 2009).

  I am connected to a 9074 with a 9263 to location 1.

  In the manual page 5-6 o is a description of example 1. I opened the example and connected to the cRIO. (Screenshot60)

  When I tried to launch the example I got an error message. (Screenshot57)

  What I've done wrong?

  Sven

  Ok

  I have soved the problem.

  The examples are for 9101 Chassis und I used a 9074.

  Now, I have copied the single VI in a new project, fixed nodes and it worked.

  Sven

• Problems with the start of the vi using TCP on a cRIO, error code 63

  I'm trying to deploy the 'multiple connections - Server.vi' in examples of TCP & UDP to a cRIO as the startup application. The vi works fine and I can connect with many clients until I have deploy the vi and set it as vi on a cRIO device startup. When the device restarts and I try to connect with the 'multiple Client connections 1(vi)"also found in examples of TCP & UDP, I get"error 63 occurred to TCP connection open. Are there additional parameters that need to be enable to allow TCP as the boot vi?

  I don't know that is the question and I don't have an RT target available to test it, but here's a possibility: property nodes sometimes do not work as expected when you run on a RT system without front panel.  In the case of multiple connections - server example, the first thing that happens is that the VI wrote a false value in the property node.  As explained in the link, this has no effect.  For example, if the default value of the control 'Look stopped' is 'True' the top loop will close after the first run, which will stop the VI, probably leading to the error that you see when you try to connect.

  To resolve this problem, I recommend you remove the 'Missed listening' control completely and change conditions to stop for the two while loops.  You run a compiled application on RT, so unless you will connect using a remote panel, there is no need any façade including the stop button control.

  EDIT: if I have correctly identified your problem, you can vote for this idea: "Warn on the face property node to use when you build a RT".

• Dynamically spawning cRIO demons using 'open VI ref' and ' Start Asynchronous Call?

  Hello

  I am creating a cRIO application that must lay a dynamic number of processes based on events that occur during execution. On the Windows platform, it's relatively simple, just get a VI reference or reference of vi of typedef'ed static, strict, etc., then run. works like a charm. I can't get this to work on the cRIO.

  Someone can tell me quickly or to the list, the restrictions (if any) and proposed the method to achieve this?

  Thank you!

  Q

  Hi q:

  Can you give us an overview of how you are trying to do now?  I ask because you should be able to use the same method that you used on the Windows.

  If your project contains your main VI as well as the screws, you want to call dynamically, all screws must be in the same place.  So, you should be able to provide the path to the dynamic VIs using the method of access to your VI main road and replacing the main name of VI with the dynamic name of VI.  So that it works, make sure you deploy all the screws under your cRIO controller.

  

  There are no restrictions, I see then this gives a shot and let us know if you have more trouble with it.

• CAN the c series modules and drivers XNET and Ethernet expansion chassis cRIO compatibility issues

  Hello

  I encountered a problem with my current setup which was not picked up by the tool advise cRIO or by the engineer of applications OR that we used to check our configuration before starting the project.  It turns out that the NI 9853 CAN modules require a XNET driver that is not compatible with the NI 9149 expansion chassis.

  We currently have a system with a cRIO NI 9068 with general IO and some CAN controller and CAN open modules in a carrycot and an Ethernet NI9149 with more general IO expansion chassis and more CAN and CAN open an another pod remote modules and all of this should work under water, so I can not move the modules of the expansion chassis to the chassis controller without a lot of overhaul of the system and equip and a team of angry engineers and technicians.

  I have developed the FPGA code for the 9068 OR and have CAN and CAN open networks works with happiness.  Then I tried to copy the same FPGA code on the expansion chassis and it compiles, but when I try to launch it I get the error-63184 code.  After long calls OR support, and tries to install the missing drivers on the expansion chassis, we discovered that XNET is not compatible with this chassis.

  Can anyone suggest the best course of action?  Is there an expansion chassis Ethernet that will support XNET?  I have here no information online about this compatibility issue that I can't find?

  I'll be communication with DIRECTLY, but from previous experience of the "odd" questions, I know the community often hold the key.  Any suggestions gratefully received.

  Thank you, Ed

  It's official.  CAN open modules are not compatible with the expansion chassis.  I have them moved to RIO and will get the upgraded pods.

  Thank you

  Ed

• Webcam USB on a cRIO

  Hi all

  The vision platform again. I connected a webcam usb (2.0) until a cRIO 9035 and I would like to start collecting pictures of him. I do not see the camera displayed on the cRIO chassis as do the modules. Being new to this... where to start to actually start to talk to the camera and receive images?

  Thanks in advance!

  Did you install IMAQdx and the subsidiary question for webcam support to 9035 himself? Once you do, the camera should appear under devices and Interfaces directly in MAX.

  If you still don't see it, a possibility is that the camera is not compatible with the standard USB Video Class that supports IMAQdx. Most webcams are, but it is possible to find some that are supported only by custom drivers and therefore will not work.

• Stop the cRIO or sbRIO via command software

  Hello

  After a little digging around I still not found a software command to stop a cRIO or sbRIO. There is a restart vi, but not a stop. I wonder if I missed something that someone may know.  For a RT Linux RIO it may be possible using a Linux command, I wonder? And for a VxWork, an idea? THX

  L.

  In general, it does not resemble the power management is not very well supported. Looks like there is a command to do it on Linux RT systems:

  How should I stop OR Linux Devices in real time?

  http://digital.NI.com/public.nsf/allkb/55A17D8F99D96ECC86257CEF004F4588?OpenDocument

  I have done some research and there is a little more information in the following forum post, and it seems that there are some utilities for Windows that are not available for RT.

  The start distance and stop the controller SMU running Labview RT (WoL)

  http://forums.NI.com/T5/LabVIEW/remote-startup-and-shutdown-of-of-PXIe-controller-running/TD-p/24496...

• Choose the network protocol for CRIO-9024 to PXI on Ethernet

  We are in the design phase, implementation of an embedded controller for CRIO-9024 to send data captured at an SMU-8105 on ethernet controller. The data will be arrays of double-precision 2D. These data should be sent to the pxi at the end of each test step. Each stage will have a different number of channels and sampling frequencies.

  For example, Test step 1 will have 5 channels of analog inputs that will be sampled to 100,000 KHz for 1 second. These data will come from the CRIO FPGA. Data will be get dealt with by the CRIO-9024 and analyzed post to pass or not not metric. Then, the CRIO controller will send the data 2D (data points 500 000 5 X 100 000) table and the results of all the measures (a table 1 d) for PXI.

  The connection with the PXI will use Ethernet.

  Do not forget that the PXI should also send the CRIO certain values to tell the CRIO when starting the test, and when the test sequence is completed.

  I thought that TCP/IP would work better because of communication 2-way necessary. But then I was watching streaming network or even using shared Variables.

  If anyone has any ideas or suggestions please please post them.

  Hello

  You can use either.  If you are more comfortable with really.  The STM method will be a little less overhead on my style XML tagging data, but it will be very short given the size of the data.  Probably go with STM has it right most of the work for you.

  Regarding the size data the you must normally transfer data as this is to flatten to a string.  If you convert a string of numbers readable human you will either lose accuracy, increase the size or both.  Because the string after that flattened will be the same size as the original array anyway for the quick calculation based on your previous post 500 000 double (8-byte) is 4 miB (3.8 MB)

  See you soon,.