File playback with LabVIEW 2009 AREA

Similar Questions

• Cannot bind to the shared object created with LabVIEW 2009

  I have problems referring to a shared library built from a LabVIEW VI under RHEL 5 with LabVIEW 2009.

  To illustrate the problem, I created a VI with a digital input and output that corresponds to a certain number. Then, I created a draft specification of build to create a shared library with a feature that makes use of this VI square. The shared object is created successfully (square.so).

  When I try to compile a test application written in C, that connects to this library, I get errors in the following link:

  cc  -I/usr/local/natinst/nidaqmxbase/include -I/usr/local/natinst/LabVIEW-2009/cintools build/square.so  test.c   -o test/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_istream >& std::basic_istream >::_M_extract(float&)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_istream >& std::basic_istream >::_M_extract(double&)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_istream >& std::basic_istream >::_M_extract(double&)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_ostream >& std::basic_ostream >::_M_insert(double)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_istream >& std::basic_istream >::_M_extract(float&)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_ostream >& std::basic_ostream >::_M_insert(double)@GLIBCXX_3.4.9'collect2: ld returned 1 exit statusmake: *** [test] Error 1
  

  Running ldd reveals that liblvrtdark.so.9.0 is used for the execution of labview.

  In order to investigate on what could be the cause of the problem, I have compiled the nidaqmx basic examples, and I don't have an error. Current running ldd as reveals that he uses liblvrtdark.so.8.2 for the view of laboratory, time of execution.

  My suspicion is that some components of labview are being compiled with gcc 3.4 while others are being compiled with gcc 4.1 (which is the default compiler in RHEL 5).

  Any ideas how I could fix the build errors?

  Thanks in advance for your suggestions.

  PS.

  I enclose a tar file with the source files and here are the details of the ldd:

  ldd build/square.so         linux-gate.so.1 =>  (0x008de000)        liblvrtdark.so.9.0 => /usr/local/lib/liblvrtdark.so.9.0 (0x00b9c000)        libc.so.6 => /lib/libc.so.6 (0x00110000)        libstdc++.so.6 => /usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6 (0x009a7000)        libm.so.6 => /lib/libm.so.6 (0x00756000)        libdl.so.2 => /lib/libdl.so.2 (0x00256000)        libpthread.so.0 => /lib/libpthread.so.0 (0x0025a000)        /lib/ld-linux.so.2 (0x00b80000)        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00272000)
  
  ldd /usr/local/natinst/nidaqmxbase/lib/libnidaqmxbase.so.3.3.0         linux-gate.so.1 =>  (0x00e50000)        libnidaqmxbaselv.so => /usr/local/lib/libnidaqmxbaselv.so (0x00248000)        libc.so.6 => /lib/libc.so.6 (0x00689000)        /lib/ld-linux.so.2 (0x00b80000)        liblvrtdark.so.8.2 => /usr/local/lib/liblvrtdark.so.8.2 (0x00e51000)        libdl.so.2 => /lib/libdl.so.2 (0x00813000)        libpthread.so.0 => /lib/libpthread.so.0 (0x001b0000)        libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x009c7000)        libm.so.6 => /lib/libm.so.6 (0x00b0a000)        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x0050c000)
  

  Hi mimi,

  I'm happy to report that I managed to get the code to work. I have included some of the steps I experienced the problem in case it might help improve the documentation or future generations.

  In response to your question about the "error 1" reported by do, it's just an indication that detected a compiler error (it probably resembles the return code of the compiler).

  The errors ' undefined reference... @GLIBCXX_3.4.9 "have been narrowed down. The generated labview shared library, the square.so, links to /usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6 which is a symlink to usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6.0.9. I decided to compare this version of libstdc ++ that included with RHEL:

  strings /usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6 | grep GLIBCXXGLIBCXX_3.4GLIBCXX_3.4.1GLIBCXX_3.4.2GLIBCXX_3.4.3GLIBCXX_3.4.4GLIBCXX_3.4.5GLIBCXX_3.4.6GLIBCXX_3.4.7GLIBCXX_3.4.8GLIBCXX_3.4.9GLIBCXX_FORCE_NEW
  

  strings /usr/lib/libstdc++.so.6 | grep GLIBCXXGLIBCXX_3.4GLIBCXX_3.4.1GLIBCXX_3.4.2GLIBCXX_3.4.3GLIBCXX_3.4.4GLIBCXX_3.4.5GLIBCXX_3.4.6GLIBCXX_3.4.7GLIBCXX_3.4.8GLIBCXX_FORCE_NEW
  

  So libstdc ++ RedHat does not include a string for GLIBCXX_3.4.9.

  With this in mind, I was able to get my test application to compile using the version of LabVIEW libstdc ++ using the following makefile:

  .PHONY: all cleanCPPFLAGS=-I/usr/local/natinst/nidaqmxbase/include -I/usr/local/natinst/LabVIEW-2009/cintoolsLDFLAGS=build/square.so \        /usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6 \        -Wl,--rpath -Wl,/usr/local/lib/LabVIEW-2009/patchlib/
  
  all: test
  
  clean:        rm -f test *.o
  

  When you try to run the application, I got the following error:

  ./test: error while loading shared libraries: /usr/local/lib/liblvrtdark.so.9.0: cannot restore segment prot after reloc: Permission denied
  

  But apparently, it's because of SELinux prohibiting the use of libraries shared with moving text.
  This can be disabled by running /usr/sbin/setenforce 0 as root.

  The test application now works!

  See you soon,.

  RW

• can I open a vi created with labview 2009 on worm Labview 8.5?

  I have a vi created with Labview 2009 and I want to open and run the vi in Labview 8.5.

  It opens to 8.5

  Can I save the vi since 2009 in a format that is compatible with 8.5?

  If you click the file menu in the toolbar of LabVIEW, you should see a "except for the previous version. If your vi does not have all the features that are specific LabVIEW2009, you should be able to save it to 8.5.

  LabVIEW is generally open earlier versions, not the other way around. I say generally because there are a few points that have changed drastically, such that you have to use an intermediate version to make the vi up to a more recent version.

• MsiError 1627 then install application created with labview 2009

  Hello

  I tried to install an application created with labview 2009, I have this fatal error ' MsiError 1627: 1: 2727 2: UsFile.

  Executable works fine while the installer does not work!

  UsFile is a Lvclass. I don't understand why I have this message.

  Thank you very much.

  Hi thanks for the reply,

  I don't delete the installation program. It has not been disabled or corrupted MSI.

  Problem is in the source file: ProgramFilesFolder was not also identical to my request. So I refreshed that (the folder UsFile appeared not in ProgramFilesFolde)

  Now it works!

  Thank you very much Bye

• Can I build an application with Labview 2009 for Windows 7?

  Hello

  I use Labview 2009 SP1 and the application builder 2009 SP1. If I install the app on win7 this message:

  Engine run LabVIEW depends on failure to upgrade (...) version 9.0.301, language {} code that is not in the distribution.

  Is it a problem with Windows 7, having two records of installation of 32 bit (C:\Program Files (x 86)) and 64 bit (C:\Program Files)?

  I had an application built on a XP machine and installed on a Windows 7 computer that was looking for the files in C:\Program Files when they were actually installed in C:\Program Files (x 86) - because it was 32-bit application.  After the installation I had to move the files to 1 place to another to make it work.

• Use the DAQCard 1200 with LabVIEW 2009 map

  Hi, I have a DAQCard 1200 and LabVIEW 2009 card. Can I use this device with this version of Labview? Is there anyway to make it work? Thank you.

  Hello ACTS,

  There is a difference betweenmx and traditionalDAQ DAQ!

  Installation of NI - DAQ6.9.3 is ok as outlined in this KB entry link above.

  But: you will find all of the DAQmx like this "DAQ Assistant" features! (Btw. why you insist on the use of ExpressVIs?)

  You must use the TraditionalDAQ functions instead. (There should be a few examples too...)

  Yes, DAQmx does not support your DAQCard1200. But TraditionalDAQ6.9.3 will do...

• Why some files HAVE with linked images are so great?

  I have several files .ai (not .eps) that all link to the same larger bitmap images. Most of these are 3 - 4 times .ai files (~ 220 MB) the sum of the size of the bitmaps (~ 60 MB) and none of the bitmap images embedded! Whence the huge size file?

  Secondly, while most of the .ai file is huge, a couple does not exist. There are approximately 320 KB. I compared the document between a large and a small file info, and there is no significant differences. What is going on? I use CS4.

  If you register with the option 'create a compatible PDF file', your images will be incorporated in any case (in part the .ai file PDF). If what you call "bitmap" is highly compressed JPEG images, data incorporated (in the PDF part) can swell to several times the size of the original files.

  You will find that embed the color profile (ICC) also adds to the file size.

• How to remove the scrollbars Panel sub with LabVIEW 2009 SP1?

  I did a search and found this thread on the subject: http://forums.ni.com/t5/LabVIEW/subpanel-scollbars-in-labview-8-0/m-p/284503/highlight/false#M149983

  I double checked that the horizontal and vertical scroll bars have not been successful in the appearance of window customize and they were not retained as shown in the image below.  You see scroll bars villain in the façade of the image at the bottom.  Of couse, since the code / sw cannot be shown, it has been repainted but you can still see the scroll bars along the frame of the side panel.

  Custom window appearance settings:

  

  Scroll bars appear at the bottom & right panel sub frame

  

  Found the solution...

  Right-click the scroll bars and select horizontal scroll bar and select always off.

  Repeat the procedure for the vertical scroll bar.

  

• LabVIEW how downconvert with labview 2009

  I am not a miracle solution, I tried to download my screws on this Web site to convert my 9.0 to 8.6.

  What is the best way to achieve this?  I have about 50-100 screws that need to be converted.

  What is the MAX upload on the conversion table?  I got 12 MB and it was over, but id has not shown what was the max.

  Thank you

  If it's that big, you're probably better to download the demo version of LabVIEW and do it yourself. The jury of the Conversion of the Version was not really intended to downconvert major projects.

• Hard drive size and the RAM with Labview 2009

  Hello

  I need to know please, how can I get the HDD of the hole size and the size of free hard drive using LabVIEW.

  Same for the RAM: size of free space and hole size.

  Kind regards

  Take a look at this example (and the thread):

  http://forums.NI.com/T5/LabVIEW/size-of-RAM/m-p/63942#M39616

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

• My compiled program crashes after the first run (LabVIEW 2009)

  I have a compiled program created with LabVIEW 2009 which, in the first round, once the computer is restarted, works fine but after discontinuation of the program, it will not work properly.

  The program uses a compiled Launcher to dynamically activate a set of VI containing the expectation driven by State Machines (QDSM).  Begins subsequent program launcher module appears fine, and his progress bar shows that she starts each of the VI.  Once the Launcher is complete it removes memory launched Dynamics VI and caressed.  The spear that do not reach the main UI that VI is barely long enough for the observer to see (if there is one) then stops.  The program then went from memory I can say.  There is no process in memory or anything.

  Also, when I try to run the installed version of the exe file on a computer with installed 2009 development environment I get this behavior consistently successful launch once again.

  In both case, my program does raise all errors (that are connected), or runtime generates everything I can see.  Also, when I run my program in the development environment the program does that way.  He has no problem at all.

  I have used this style of architecture front of LV8.6 with all the problems.  Can anyone suggest some possible solutions or even a few debugging tips?  I've never had a problem that I could not duplicate in the development environment, so I'm not sure how to start to attack my question.

  Thanks for any help.

  Jason

  

  I solved the problem I think that (at least with regard to the tests on this point revealed).   After that I added the possibility to connect the past States to of the QDSM, I was able to determine that the program was 'plant' after that I dynamically closed the Panel front of the Launcher.  My program is designed to close the Panel before the pitcher, then pop up the façade of the main user interface.   My EXE is inspired to hold the Launcher with my other files QDSM kept outdoors in specific directories.  What seemed to be happening is that when Launcher closed its façade and before UI opening upward the runtime engine decide since it is y no Windows Open he was closing down.  It's my guess on what might happen any way.  I modified my code to change the Launcher window to hidden and delay for 1/2 second to give a chance to fully start running to the main user interface.  This will correct the problem, or at least worked around her.  If someone out there can explain me exactly what is happening that I sure would appreciate it.

  Thanks for all the help that those of you who responded.  Your advice has been very beneficial and certainly led me to a faster resolution.

  Jason

• using NI USB 9201 with LabVIEW Real-time

  Hello

  I try to use a USB of NI 9201 on a remote real-time target. Here's what I did: 1) tricked out of a desktop PC to serve as target RT using the instructions provided on the Web site of NOR. He now starts in an RTOS with LabView RTOS 9.0. (2) I communicated successfully with the help of a host computer that has a windows with LabView 2009 BONE and I installed the software from the computer remote RT target host using ethernet. However, my problem is when I plug NI 9201 USB on the target RT that I do not see the material listed on the devices tab in MAX and interfaces on remote systems. I tried to get the manuals for the HW 9201, but it seems not much explained here, or maybe I'm looking in the wrong places. Any help is greatly appreciated.

  PS: I am attaching 2 JPEGs for additional explanations (tab network settings and the settings of the system).

  Thanks in advance,

  Benoit.

  AVS,

  9201 USB is not supported on RTPCs please visit this link. Currently no usb-DAQ devices do not support an environment CRPC. Only the PCI DAQ devices are supported.

  http://zone.NI.com/DevZone/CDA/tut/p/ID/6913

• Imaging Source DFG/SV1 acquisition card is not correctly recognized in LabVIEW 2009

  I have an Imaging Source DFG/SV1 frame grabber/capture card (I think that this example uses a Bt878 chip) that I am using with LabVIEW 2009 (Fall edition 2009 academic Site license), including elements of acquisition of vision (NEITHER Vision, NOR-IMAQ (4.3) OR-IMAQdx (3.4), etc.). I have all the latest sources of imagery support drivers and software for the Board of Directors (http://www.theimagingsource.com/en_US/products/grabbers/dfgsv1/ drivers: v6.0.3.0, IC Software v2.1 and IC Imaging Control v3.1) with drivers being compatible DirectShow. The DFG/SV1 is detected in MAX under devices NOR-MAQdx / DFG/SV1 / cam0 and I can grab and preview images, however to 320 x 240 resolution, I have a higher resolution camera and know that the jury is capable of greater resolution using IC software manufacturing and also via TWAIN with ImageJ software drivers. Interesteingly, if I try to acquire an image of the card purchase using the Vision Assistant, the DFG/SV1 card is not recognized as a card acquisition, but listed under IEEE 1394 or GigE peripheral, revealing with it being direct device that I can't understand. Despite this I can acquire images, but I am limited to 320 x 240 format and change the type of image (RGB, UYVY etc) causes an error. Once again, oddly enough, I can use "enter and select mode example VI" which should only be compatible with IEEE 1394 cameras.

  I'm not sure why LabVIEW is not seen this card properly, I contacted Imaging source who were also intrigued by the fact.

  Any information on how this could be resolved would be much appreciated.

  Thanks in advance.

  Hi OCastell,

  With this Council Imaging Source, the only interface supported with drivers of NI Vision Acquisition is through using IMAQdx DirectShow interface. It is possible that their DirectShow driver does not properly support all of the capabilities of their Council. Given that ICR software and TWAIN support can be routed to a different implementation of one of the DirectShow support, you can see the different features available. Unfortunately, you probably go through Imaging Source to determine why their DirectShow driver does not support the full resolution. You can confirm that it isn't IMAQdx this limiting trying other software such as Windows NetMeeting or AMCAP DirectShow and see what capture resolutions are listed.

  Because the DirectShow interface is managed by IMAQdx driver, it will not be detected as a framegrabber IMAQ using the IMAQ driver. This is expected since it fits in the same category as firewire and GigE Vision cameras and is supported with the IMAQdx driver instead.

  The "Grab and select the Mode" example VI isn't really specific FireWire, although he was certainly intended to highlight the various video modes that generally expose FireWire cameras. Since the DirectShow devices are similar and have several selectable video modes, it's why he's probably working. In any case, IMAQdx abstracts usually differences between all supported camera types and in general a single VI can run on all cameras IMAQdx-taking in charge unless you rely on buses or the camera-specific features.

  Regarding Vision Assistant marking the camera as 'IEEE 1394 or GigE', I think it's just an aesthetic issue (which may already be fixed in new versions). When IMAQdx was out, these are the supported types of cameras and so Vision Assistant was trying to say clearly what driver was used for the type of device. Now that IMAQdx supports a multitude of new interfaces (including DirectShow and some IP cameras) that the label is inaccurate.

  Finally, looking at the specs for this capture card, it looks like a standard reference BT878/848 model and then you could try potentially replace your Imaging Source driver with one here:

  http://BTWinCap.sourceforge.NET/

  I used this with a with IMAQdx BT878 capture card and can get it to capture an image full resolution (but of course, your results may vary...). It goes without saying that this solution using DirectShow is much more limited than using an industrial camera on 1394/firewire or a framegrabber IMAQ.

  Hope this helps,

  Eric

• Install the LabVIEW DSP Module on Labview 2009 Professional

  I have LabVIEW 2009 professional and I try to install the LabVIEW DSP Module on it. I have LabVIEW DSP Module 8.6, and I think that this is the final version. However, when I tried to install it, it says you should have LabVIEW 8.6 on your system.

  What should I do?

  Hello Brandon,.

  I did run the LabVIEW 8.6 DSP module, you must have LabVIEW 8.6 (compatibility table), which can be installed and run in parallel with LabVIEW 2009. I apologize for the inconvenience, but 8.6 is the latest version of this module, so you'll need to buy LabVIEW 8.6 for use.

  Kind regards

  Deborah Y.