cRIO-9073 only with Labview 8.6? Data record?

Similar Questions

• TestStand communicates only with labview

  Hi all

  I use 2012 Teststand and Labview 2012 SP1. I use Testsequence calling developed Codemodules usnig Labview 2012.

  Question 1: When I call the main sequence code modules was not called. But when I sperately run the VI (besides it's simple, DMM vi) the VI was running perfectly.

  solution:-open the tab configuration and selected LabVIEW and selected adapters. After that obtaining in that we chose Runtime Engine to motor development.

  With this, the issue got sorted on why is this behavior happened.

  Please let me know if anyone knows or in front of the same type of problem.

  Hello

  I have recently experienced problems with TestStand and LabVIEW code modules, finally I found linked below white paper, which can also be useful for you:

  http://www.NI.com/white-paper/9923/en/

  In order to understand what is the cause, I have a few questions below:

  Having developed this VI or is it a real VI from the NI-DMM palette?

  If you open the VI in the LabVIEW development system and select the file-> properties VI, is version 12.0 indeed?

  The VI uses no control or Subvi, so then, what are these and also they are stored in libraries?

  If you build a project with your VI, create an executable, done this successfully executed? (Some properties and functions are not supported on the runtime incompatibility may be found here).

  Best regards

  Ed

• A HMI TCP can be used only with Labview with no material of CAP?

  Hello

  I have an application where I have a DAQ card in a PC running a Labview application. I want to have a TCP HMI display in the next room where info can be displayed as well as entries digital operator. Is this possible? If so is there an example how to do that.

  Thank you

  John

  Hi John,.

  Yes, it is certainly possible (I guess this PTC is National instruments, and you use the LabVIEW Touch Panel Module).  The best way to proceed would be to use shared variables to send information about a PC for the TPC network.  Here is a quick tutorial specific for the TPC-2006 and LabVIEW 8.2, but the process is similar across other HW.  Additional information on variable support shared for different versions HW and LabVIEW can be found hereand in the sections of links on this page.

  Finally, there are examples of shared variable communication that install with the Touch Panel Module.  Head to the example finder (help > find examples...) and navigate to the Toolbox and Modules > Touch Panel > Networking > General.  Here you will find some examples of shared variables.  There are also some examples of TCP & UDP in this matter of networking which are another option.

  I hope this helps!

  see you soon,

• Beginner's Guide to out of Labview to MySQL data

  Hello

  I am a student who has started only recently, using Labview for a data recording project, so that my knowledge of its use is rather absent. My current goal is to be able to get out the data stored directly in a MySQL server, so that data are accessible remotely via internet and processed using PHP scripts.

  I have some basic knowledge of MySQL, as I've previously used to create dynamic web pages, but my knowledge of how it works is also a bit lacking. The MySQL database I want to connect to the stands remotely on a server of the University I want to connect to.

  I saw that this connection is possible from previous posts, but I would really appreciate a basic account plus the steps I should follow to make such a link.

  Thank you

  Rob

  
  

• VBAI2014 fast data recording

  I work with a VBAI.vi which captures images of a dual GigE camera and a cRIO information. It is supposed to recover information quickly and write them on a hard drive.

  The procedure looks like this (you can also see them in the picture ' "operating mode." ") JPG'):

  1. The image is entered via dual-gig-e and the module "image acquisition.
  2. Via the "Calculator" module, the name of the file is determined and several variables are read via a cRIO network.
  3. Through the module "data record" variables are written in a .csv file in the hard drive.
  4. Via the 'image' module, the acquired image is written as a .tiff file to hard shore.

  Our camera is able to charge up to 19 frames per second per double Gig-Ethernet. To avoid a passing image-guy, we need to acquire and write the information on the hard disk in seconds 1/19--> ~ 50 milliseconds.

  As you can see in the "" measures. "" "JPG", the procedure takes between 80 and 100 ms, the slowest of the modules seems to be "data record" stage which takes 44 ms, which seems strange because it appears less elaborate than the image logging. You can see the data that are saved in "" forest operations. "" JPG ".

  You have an idea how I can speed up this process? I thought to write a LabVIEW VI, which records data from worksheet instead of using the module "data record" of the VBAI, but I don't know how to run VI in VBAI.

  These delays are not by the speed of the hard drive, I get similar results on a virtual disk.

  Thank you very much for the help!

  Sincerely,
  Paul

  Here are some tips to improve performance:

  1. make sure that you uncheck "Display result Image for that State" upstairs to the left of the script of inspection box. This, for all your States to improve performance. I think the Datalogging might look like he takes so long because the update of the display is asynchronous, and whenever the operating system decides to redraw the image, it can happen to be whenthe datalogging step is running.

  2. make sure that you run in mode of inspection. Configuration mode adds a lot of delays, so you can see the status of the inspection

  3. you can try logging of images and data in the background (there is a setting in steps). This will not be guaranteed that each image is saved but if you get images faster your hard drive can connect to them. If this is the case, you may want to consider:

  -Get a faster as HD and SSD.

  -Try different file formats (BMP or JPG can be faster than tiff)

  -Make sure that you are not including the overlay to the image since this converts into a color image and can produce much more to save on disk images.

  4 try to run the 64-bit version of the VBAI to improve performance.

  5. do you have a fast PC you run this on?

  As a quick test of validation, open the attached inspection. I put a CQI simulation in the State of the installation (view > view full Inspection Setup, then click the installation state in the box on the left toolbar). Then choose Run > Benchmark Inspection with 50 iterations and see how long the image is logging. This will give you an idea of just how fast your hardware can support saving to disk. Try various formats such as JPG, BMP, PNG image, etc. as different PC configurations will have different performance.

• CRIO-9073 is compatible with LabVIEW 8.5.1?

  I just got a cRIO-9073 and a cRIO-9074.

  When I set up, both of them appear correctly in MAX.

  When I add them to a project LabVIEW, the cRIO-9073 does not show the target FPGA. The cRIO-9074 shows.

  I'm using LabVIEW 8.5.1, is compatible with the cRIO-9073?

  Thanks for any help.

  Michel

  Hi Michel!

  According to this link, the interface FPGA and Scan of the cRIO 9073 are only supported in LV 8.6 using the NOR-RIO 3.0 driver.

  The link where you can check the compatibility is:

  FTP://FTP.NI.com/pub/DevZone/tut/crio_software_versions.htm

  Good day!

  Oswald Branford

• Unable to create a file with "nidll_vxworks" in Matlab for use with the LabVIEW SIT 2010 and a cRio 9073, error sh.exe

  I am trying to compile an OUTPUT for my Simulink model file by using "nidll_vxworks" and execute it using the Simulation Interface Toolkit for a cRIO 9073. I am able to compile the DLL file by using "nidll" and managed to run the simulation using my PC as a host.

  I have already downloaded the files "gccdist" and "vxworks61gccdist" and copied in "c:" when I build the model in Sumulink I get the following error at the end of the process (at the same time windows tells me that "sh.exe" has stopped working). If it's important, I'm on Windows 7 64-bit, but using Matlab 2009 b 32bits and LabView 2010 32-bit. ANY HELP WILL BE APPRECIATED. "QofV" is the name of my Simulink model and I changed to parts of "XXX" in the path of the file.

  6.1 CCG is only supported on Windows XP.  It is almost indicated in the readme_sit_vxworks.txt found in C:\SimulationInterfaceToolkit\xxxx\VxWorks (where xxxx is the version of the DIS).  It is said:

  * Known issues
  
  ---------------------------
  
  -WindRiver GNU Toolchain 6.3 and 6.1 do not work on Windows Vista.

  To be more explicit, it should be "Vista and later.

  Carl L

  National Instruments

• cRIO-9073 not appearing is not in devices and Labview 2009 targets

  In MAX, I show the following: a cRIO-9073 with NOR-RIO 3.0.0 installed. My system software has NEITHER-RIO 3.0. In LabView 2009, when I try and add the cRIO to my project in LabView 2009 in New-> targets and devices, I don't have a list in time real CompactRIO and my cRIO does not appear. I tried to add manually with its IP address, but it does not work either. I've updated the cRIO to LabView real-time 9.0 software.

  Is there other software that I need to update on the cRIO so that it is visible in LabView 2009? Do I need a new version of NOR-RIO?

  Thanks for any help.

  Todd

  I upgraded from NEITHER RIO NOR-RIO 3.2.1 3.0 and LabView 2009 seems happy.

  See you soon,.

  Todd

• cRIO only with switch ethernet connection and the computer

  Hello

  I use a cRIO-9073 connected via an ethernet switch and then to my computer and also connected to the corporate network. The cRIO connects fine (I can interact with the remote façade on the cRIO) using this method, but I can't view the remote façade when I connect just my computer for the cRIO via the ethernet switch. Where can I find the method of connection to cRIO by ethernet switch?

  Thank you

  Note: I configured manually my computer an arbitrary IP address and the subnet mask when you use only the ethernet, cRIO combo switch, no network. But I can't repeat the cRIO connection, there may be a step I'm missing.

  bermea,

  Hello! Let me be sure I understand your problem and then make a sugguestion.

  You have your PC and the cRIO connected to an ethernet switch that is also connected to your company network and you are able to see the cRIO to the MAX. However, when you have disconnected your network switch companies, leaving only the PC and the cRIO connected, you are more able to use the cRIO or see in MAX. Is this correct?

  It seems that you have indicated that you have setup your PC to have a static IP address for when it is disconnected from the network. If this is the case, you must also set the cRIO to have a static IP address. Here are some documents that can help you do this.

  • Choose a static IP address for your engine in real time
  • Why my controller cRIO not Show Up in MAX?

• LabVIEW 2009 .exe works only with windows 2000

  I created a simple vi with Labview 2009 for resetting a counter in the registry key. I changed it to an exe. The program works well on any machine with XP, but it does not work on the machine, that I need on which is running Windows 2000 SP4. I have installed the runtime of 2009, but I keep getting an error when it starts the vi is not executable and I need the full development to correct errors. But like I said it works everywhere else. I tried other exe wrote in LV2009 on this machine and they work. Is there something in my vi which is not compatible with Windows 2000?

  Thank you

  dkfire wrote:

  If you build an exe on a XP machine, then it will work only on XP.

  You need generate the exe on a Windows 2000 machine to make it work.

  Simply not true - even close to not being not right.

  Chris,

  My guess is that the .NET component is not present on the pc of w2k.

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

  Michel

  Paul,

  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

• How to read data from the unit to acquire data with LabVIEW

  Hello everyone, I'm new with LabVIEW and I need help. How to build LabVIEW program to read and store the data acquisition unit temperature data. the data can be any store such as Excel or a text file? Thank you.

  Start passing by examples of LabVIEW.  Go to help-> find examples.  There are several examples here just for the analog input and then even more for logging data to a file.  After that, show us what you have and we can guide you a little better that way.

• NEITHER 9481 relay are not locked when running the labview compiled exe on a computer with only installed labview execution?

  I recently bought a cDAQ-9172 with several modules.  One of the modules is a NI 9481 relay module.  I created an application using Labview and built an exe file.  If I run the exe on the computer, it was developed on the relays work properly, that is, they remain locked up until their status is changed.  If I run the same exe on a computer with only the Labview runtime installed (no software installed), the pulse relay contacts and not locked.  I'm using Labview version 7.1 for my development and execution.  Everyone knows about this problem?

  Ignore this announcement, the error stems from a difference between each computer ini-files and has nothing to do with the Labview Labview runtime vs, my bad developer.

• Installation DAQmx 9.1.1 with LabView 8.2, but focused on the acquisition of library data do not appear

  I'm under LabView 8.2 on Windows XP, with an NI PCI-MIO-16XE-50 card. I tried to install DAQmx 9.1.1 on my system, but libraries DAQ do they not appear in the folder C:\Program NIUninstaller Instruments\LabVIEW 8.2\vi.lib.

  Here is the chronology of the events:

  After you add the DAQ card to my computer, I installed DAQmx 9.4. When I learned that 9.4 DAQmx is incompatible with LabView 8.2, I uninstalled and replaced with DAQmx 9.1.1 and installed the patch.

  I can see my device in MAX, but DAQ Assistant is not listed under functions > Express > entry in LabView.

  From advice on forums, I tried using Add/Remove programs to change NI DAQmx 9.1.1. Under 'Application Development Support' I see "Support of LabView 8.2" has a green check mark, but the text in the right panel says "this feature will not be installed. A newer version of this product is already installed on your computer. »

  I tried to "Repair" NI DAQmx 9.1.1 (and patch), but did not see a difference.

  I guess I need to uninstall the latest version of "Support of LabVIEW 8.2" before installing OR-DAQ 9.1.1, but there is no element of that name in Add/Remove Programs > National Instruments software. How uninstall this version of LabView Support for DAQmx 9.1.1 will install correctly?

  Or, if this is not the source of my problem, what is?

  Thank you!

  
  

• cRIO-9073 disconnects

  I connected a cRIO-9073 to my computer and connected to my LabVIEW project. I downloaded the software to it and configure it to scan mode. It is, whenever I connect to it in LabVIEW, it disconnects after only 3 minutes exactly. I did nothing at all with it, to make it work, no program or whatever it is. Y at - it software it is absent, is there some configuration details, I am missing or is this possible?

  Martin

  I found the solution to the problem.

  When I format it and install the software on the cRIO-9073 from a computer win Win 7 (64 bit) the communication problem is present. When I install the same software on a computer with Win - XP (32 bit), the problem disappeared. The problem is reproducible.

  Martin