CRio-9035 offline development

In the near future, I develop software for crio-9035. Given that shipping takes a while, I would like to start writing Victorian code now without any hardware. I have installed:

LabView - 13;

-In time real Module 13.

Module FPGA - 13;

And then, of course, NOR-RIO Drivers 14.5.

When I try to create the new target in empty project, I don't see my device in a category.

What I am doing wrong?

Thanks in advance.



I looked at my own system, and it seems that I could find in LabVIEW 2014 SP1, but not in 2013 9035 SP1. I looked again inside and looks like that because the 9035 is such a new product, it requires at least LabVIEW 2014 SP1 or later version.

You can find it in the manual on page 2, or follow this link

Tags: NI Hardware

Similar Questions

  • How to use the LabVIEW ToolKit FLIR on cRIO-9035


    now I develop vision acquire system FLIR-A655SC, LabVIEW Toolkit FLIR and cRIO-9035.

    first of all, I do a simple vi.

    Open camera-> camera information (serial number, focus distance and more)-> close camera.

    but I can't deploy this sample. and error list shows "thread: no support this objective.

    I want to get a thermal image of FLIR-A655SC on the cRIO-9035.

    Do you know how to solve this problem?

    It is resolved!

    IMAQdx on cRIO-9035 is OK

    LabVIEW ToolKit FLIR on cRIO-9035 is NG.

    There is bad wire on my block diagram. but wrong wire VI of FLIR.

    CAMCTRLLIB. LVCAM is missing on my goal.

    CAMCTRLLIB. LVCAM have the windows library.

    cRIO-9035 is Linux-RT platform.

    I was about to run LabVIEW Lib for windows under Linux.

    Thanks to you all.

  • Deploying an application by using a component definition file does not work (cRIO 9035 - LV2015)

    I created an application for the cRIO 9035 only in real-time with the component definition file, but when I try to deploy with MAX, I don't see the application - MAX has the dialog add/remove software standards. The files are created in the folder "National Instruments\RT Images\User Components".
    I was able to do with cRIO 9068 in the past with no problems. Do you know what I'm missing?
    I want to sent build files to a colleague from another place so it can deploy on a similar system without me having to create a large image with the wheel for every little change in the code.
    Thank you!

    Hello, Lucien.

    What you describe is actually a known problem with the cRIO-903 x family. It is already a CAR on the same subject when I won't be able to give you a deadline for a solution, it is already handled by R & D. The number of CAR is 545686, so if you see a bug in trouble with that number in a future version, it means, it was fixed.

    Unfortunately, currently there is no workaround solution identified, so the only way to get the application running on any cRIO-903 x is either by pushing through a project, or deploy an image (this is what we are trying to avoid the definition of the component).

    Kind regards

  • NOR-Sync with cRIO-9035


    I'm trying to configure a cRIO-9035 to receive data from timestamp 1588 via Ethernet on the second port ethernet on the cRIO (eth1).

    I'll send the signal of Grandmaster 1588 of a PXIe1065 with a time card OR 6682.

    I connected the cRIO and followed the steps in this article:

    I modified the "/ usr/local/natinst/share/TimeSync/tsm.json", the instructions in the file as shown below:

            "timeReferences":       {
                    "IEEE 1588-2008_1":     {
                            "defaults":     "/usr/local/natinst/share/TimeSync/TimeReferences/IEEE_1588-2008.json",
                            "priority":     "unknown"
                            "protocolConfig" :
                                    "priority1" : 128,
                                    "priority2" : 128,
                                    "hwTimestamping" : 1,
                                    "interface" : "eth1",
                                    "statusFile" : "/var/run/ptp_eth1.status"
                    "timeKeeper":   {
                            "library":      "/usr/local/natinst/share/TimeSync/TimeKeepers/
                    "servo":        {
                            "library":      "/usr/local/natinst/share/TimeSync/Servos/"

    But I get the following error when I read the file ' / var/log/messages:

    Time demon, got status: FAIL(-52005,null)

    Advice of the article that it might be an error in syntax when I changed the file 'tsm.json '.

    (1) someone has the code needed for the IEEE1588-2008 installation with cRIO?

    (2) is it possible to do this entirely in Measurement & Automation Explorer?

  • Problem of memory TDMS on cRIO-9035 (Linux RT)


    I was unable to move in a kind of memory problem that I am experiencing during written TDMS. I write in the PDM file, use of the RAM on my RT goal grows regularly. I thought it was due to some kind of indexing that happens with very large TDMS files so I am currently split my files at the level of the 50 MB mark. When the maximum size is reached I empty and close the file, and start a new one. So when I stop recording I rinse and close the bottle. However, use of the RAM of my continuing to increase anything.

    I've read about it and I've seen repeated references by using the NI_MinimumBufferSize property as a possible solution. I've implemented this, but it doesn't seem to do the trick either.

    Everyone has been able to overcome this problem, or I'll have to return to the spreadsheet of construction VI (please no.).

    I've included a simple set of VI that initializes an array of 16 x 2500 to simulate values 2500 for 16 channels and writes this table to classify every 50ms. In my real application table 16 x 2500 are 16 channels playback at 50 kHz readings of my analog input module. The "" would be the main VI launch.

    Thank you


    It's probably the file system buffering of i/o to files in memory. Depending on your version of LabVIEW, LinuxRT reports of memory can include these as "used" memory buffers when they are actually available to applications on request.

    There is a document which deals with it here:

    My main question is do you ever see a memory error output? What happpens if you expect that the memory fills up?

    I expect that you will see the behavior where the memory appears to fill, but any work properly!

  • Unable to develop a basic project CRio


    I work with a CRio-9073 chassis and a NI 9205 module. I want to develop a LabVIEW graphical client on the host computer.

    What I want to do is quite simple, and I think I should use scanning for this Interface. I've followed all the instructions on this page:

    ... to this page:

    Nothing goes wrong so far, but I confess that I was faced with a lot of things that I have finally fixed. Yet, when I opened a new VI in 'click-right on the time controller real CompactRIO in the project', the two before Panel and block diagram open but I have a range of empty function.

    I'm completely stuck and would appreciate any help.

    Kind regards

    What version of LabVIEW are you using? I see that you have SP2 2013 LabVIEW (with no toolkits) and LabVIEW 2014 installed (with the FPGA and real-time tools), but your cRIO 2013 installed LabVIEW. You must have the same version of LabVIEW running on the cRIO and your development computer.

    That said, this would not explain an empty palette. Can you share a screenshot, view of your project, including the cRIO target, with a VI in this goal, and with the palette that appears when you right click on the block diagram (even if it is empty) pinned to the window? I've never seen a totally blank palette. You try to add the VI to the target of cRIO, or FPGA underneath?

  • Deploy the cRIO/FPGA project on identical targets

    All, I apologize that this seems to be a frequently asked question, but I'm wondering if anyone has the tricks in their bag.  I'm looking to create several identical parts of a tester, and I'm looking for the most effective way to have a unique (RTexe and FPGA bitfile) code base that I can deploy on a bunch of cRIO-9035.

    My best case scenario is that I can compile for a chassis and deploy for the rest, because I won't be able to support long-term material and which would minimize the possibility of errors creeping in different compilations presents (and make it easier on anyone that upgrades the equipment later).  In addition, it is about half an hour to recompile everything for a new chassis, which is just a pain.

    What think you of all?

    Thank you

    Use the utility of replication and deployment (RAD).  It is a tool developed by the engineers of system OR specially for this purpose.  The underlying idea is to get a working system and then you take a picture of him.  You can then deploy this image to the rest of your controllers.

  • I can measure the speed of the NI 9401 fan & cRIO 9075 under Scan Interface?


    I am currently using OR 9401 & cRIO 9075 to develop a project, which is to control the CPU fans.

    Since I have to communicate with other instruments by serial port, while I have a NI 9870 module to implement the instrument control.

    I finished the part of control instrument under scan mode and would like to add the function of the fan speed reading.

    Now, I wonder if there is a problem when I choose the Scan Interface to deverlop the program.

    I found the following tutorial, he uses the FPGA interface to impement the acquisition of control and PWM frequency.

    So if the function of the fan control only developed under an FPGA interface, I have to rewrite the control instrument part, seems to be a bit complicated...

    You can use the hybrid mode.

  • 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.

  • Driver EtherNet/IP NOR support cRIO-903 x chassis.

    I have a cRIO-9035 chassis needed to interface with an automaton using EtherNet/IP.  The last pilot NI EtherNet/IP (14.0) does not support the new cRIO-903 x chassis.  When a new version of the EtherNet/IP driver will be released which adds support for the new cRIOs?

    Too bad.  I reboot my machine, and the issue is not persistent.  I think that my problem was caused by the presence of MAX open when I installed the EtherNet/IP driver.

  • Why do I get the compile time extremely long with FIFO on the cRIO-9073?

    I use a cRIO-9073 to develop a data acquisition system.

    When I try to use a FIFO to pass data to the host the FPGA, I get extremely long to compile (hours!).

    Currently, I use that a single analog input of a module 9205 in my loop FPGA.

    Y at - it an explanation for that?

    Thanks for any help you can provide.



    Thanks for your reply.

    I finally found the problem: the size of FIFO, I requested in the properties of the FIFO was too large to 32K items (for the type of data the FIFO U32) 4 times. He was filling the FPGA, 128 KB of RAM completely, leaving no room for manoeuvre for the compiler for the remaining logic. So bad, there was no warning for that!

    By reducing the size of my FIFO at 4K, the compile time came in 5-10 minutes instead of hours!

    Michel Lanthier

  • Support NI 9882 EDS

    Looking to design an application to talk to a peripheral part 3 on DeviceNet. I have a cRIO-9035 and LabVIEW 2015 SP1. The module NI 9882 does support loading EDS files?

    Hi JY,.

    Sorry to say that neither 9882 cannot load the EDS file. Single card PCI or PXI can load.

    Thank you!

  • using counter on NI 9401


    We ordered the cRIO 9035 system with several Modules.

    One of them is the NI9401.

    I want to use this module to count the pulses of a flow meter.

    In front, I am a beginner and started just look at a lot of tutorials and created Basic VI

    1. This Module has onboard counters, or is it only possible to use the 'material' - counters in the chassis through this Module?

      I ask this, because I can put the Module via "Digital specialty Setup" as a counter.
      If I do, it would be possible to simply create a while loop, place the channel on the inside and tie him to a digital item?
      Or is the only way to count impulses (rising edge) to use VI as the 'edge counter VI' the example of VI?

    2. My flow meter uses a Hallsensor and produces rectangular pulses at 40 Hz max.
      It is absolutely necessary to use a FPGA or can I use a VI on the host computer?

    We use 4 of these flowmeters (and many more sensors like Termocouples (NI 9211), solenoid valves (NI 9482) or a AKD-servomotor (NI 9472).)

    All the measured data should be written to a file (for example, form exel).

    Magnetic valves must be triggered if a certain number of pulses is counted.

    Yet once, it is absolutely necessary to use a FPGA or can I use a VI on the host computer?

    I know there is a lot to do and I have to learn a lot more, but I'm on it (its for my Masterthesis).

    For now, the answers to questions about existing or not existing edge counter would be great.

    Thank you for your support.

    Greetings from the Germany,


    Lukus salvation,

    Greetings from Munich (since it is a public forum, I am obliged to answer in English, in any case).

    (1) when you use a cRIO you don't have a strict meter limitation (especially if you program the FPGA) for your digital inputs. Maybe read you something about that and that only applies to the cDAQs (because he (mostly) counters come from cDAQ chassis so they are more limited)

    "If I do, it would be possible to simply create a while loop, place the channel on the inside and tie him to a digital item?"


    "Or is the only way to count impulses (rising edge) to use VI as the 'edge counter VI' the example of VI?

    I'm not sure which exact VI you are referring to, but on the FPGA you could implement a custom counter. That would work too.

    (2) you can do two ways (Scan Engine Mode and FPGA)

    If you write a master's thesis, you may be eligible for a greatly reduced price. The course Embedded Control and Monitoring ( would be very useful for you:

    Forderprogramme as research, training und Lehre - National Instruments Germany GmbH

    Best regards


  • FIFO.config - 61206: but the name of the FIFO is


    I am relative new to cRIO and I became a mistake the last time, I've compiled my FPGA.

    Description of HW

    • cRIO-9035
    • 4 x NI9229

    Description of the software

    • FPGA: I have 15 DMA FIFO (I can do this according to this document), which send asynchronous messages on each FIFO (see the joint photo)
    • RT: I get this message and I store them in a PDM file


    • FIFO. Configure or FIFO.start gives me "error-61206." This error, as shown here, means that there is no such thing as the name of the FIFO. But as pictured there. I don't know what happened. Is the first time I get an error like this.

    For your impeccable support, I'll tell you ' thanks!


    I found the problem.

    Only really used FIFOs on FPGA can be configured.

    If you declare a FIFO and you won't use it on FPGA (for example to do a test of part of your project) you need to remove from code RT parts where you configure, start closed ancd FIFO.

    Thank your for your attention.


  • Neither 9860

    Hi, I just tried setting up the chaisis ethercat 9144 with a module of the series nor 9860 c and crio 9035 is the master. But I can't get the module to appear in the project. The 9860 module is supported by the chaisis ethercat 9144? If this is not the case, how can I solve this problem? Because the 9860 NOR can be used in interface to scan mode and I don't wan't to run it on the crio 9035 because then I'll have to use the hybrid mode.

    Thank you.

    Based on the product page, I would say the 9860 is not compatible with the EtherCAT frame.  It should work directly on your cRIO-9035 however.

Maybe you are looking for