LabVIEW how downconvert with labview 2009

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

• How to create a stand-alone executable in LabVIEW 2009 Professional Development System?

  How to create a stand-alone executable in LabVIEW 2009 Professional Development System?

  This should help you http://zone.ni.com/devzone/cda/tut/p/id/3303

  Remember that the quick search with Google in many cases will be quicker to ask in this forum. I always use Google before asking for help in any forum. It is much faster

• Is the tool provided with the works of Labview 2009 with LabVIEW2010

  Hello

  I use currently LABVIEW 2010 want to know about toolkit provided with the dvd of LabVIEW 2009

  is compatible with the labVIEW 2010

  Thank you

  Check out this link.

  http://www.NI.com/support/LabVIEW/lvtool.htm

  If the required toolbox does not "(ou supérieur) ' after the requirement for 2009, or specifies LV2010 it is not compatible."

• problem with a block of memory in labview 2009

  Hi all

  I have "ERROR: MapLib:979 - LUT4 symbol" during the compilation process (lots of errors like this), and I discovered that the reason of my problem is block of MEMORY.

  To be sure that the problem is in this block, I did a very simple project in LabView 2009 (on FPGA Target PCI5640R) only with the use of this block you can see in the photo, as well as in file test_memory block.lvproj attached link: https://www.dropbox.com/sh/u87f1oihelmm4dq/Jo_6-bICSf

  

  I have a problem with compiling VI with this block, and I have so many errors like:

  ERROR: MapLib:979 - LUT4 symbol
  "window/Thatcher/n_00000036/nSCTL_00000013_00000014/n_000000A3/cOutLoc<0>1.
  (output = window/Thatcher/res000001ed_wi<2>) is the input signal
  "window/Thatcher/res0000020d_wo<1>" that will be deleted. See Section 5 of the
  Map a report file to find out why the input signal will become conveyors.

  or

  ERROR: MapLib:978 - LUT4 symbol
  "window/Thatcher/n_00000036/nSCTL_00000013_00000014/n_000000A3/cOutLoc<23>1.
  (output = window/Thatcher/res000001ed_wi<25>) is an equation that uses
  input pin I2, which no longer has a connected signal. Make sure that all the
  the pins used in the equation for this LUT are signals that are not cut
  (see Section 5 of the report file map for details on which signals were
  adjusted).

  Entire report, you can see in the file report.txt on the attached link.

  I would appreciate if someone could take a look at my problem with simple project and suggest me a solution.

  I'm really stuck with my biggest project which need to have this memory block.

  I'm looking forward to hear from you,

  King looks

  ING. Damir Hamidovic

  Hi all

  I find a sollution to my problem.

  In memory-properties-general-setting up, I changed the block to look up Table memory, and I compile memory.vi and run it successfully.

  I did change as you can see on the picture:

  

  Just, can you tell me is it all "bad properties" and limits the use of this type of memory (Look up Table) of the implementation?

  King looks

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

• How to interface a simple way using LabVIEW 2009 simulink model and SIT?

  Hello

  I finally found a way to use a template simulink with LabVIEW and the Toolbox to SIT, but I'm not satisfied.

  If you have any suggestions, the link of resource that I missed, please do not hesitate to answer

  Note that I do not know much about simulink, so that is my question seems stupid, let me know what

  Software configuration

  OS: Windows (not an RT target)

  LabVIEW 2009

  SIT 2009

  question 1: interfacing the model DLL (mapping considerations) with a driver VI

  We have created a model of DLL by using the 'Workshop in real time' tab in simulink.

  In LabVIEW, launch us the tool 'SIT connection manager' and try to use the DLL with a driver VI by mapping the e/s model for screw/lights orders.

  The fact is that I fail to connect to my controls/indicators VI/o model because they do not appear in the mapping dialog box.

  The simulink single objects that I managed to map are "constant" and "test points" while I need to edit the template simulink itself (example below)

  

  Are in e/s model, not considered as part of the parameters of the model? (this could make sense because the mapping says in fact that it operates on "model parameters")

  Is it possible to link the IO model VI commands/lights?

  Note:

  -the "configure HW i/o mapping" dialog box allows me to map model e/s with e/s HW...

  -The examples also use these "constant" and "test points".

  2nd question: use of direct screw SIT

  I tried to use the DLL directly with the screws SIT (code example below)

  This kind of code works well on another project (target of 8.0/RT LV) but not on the current project (LV 2009/Windows)

  The second stage of the model never ends:

  -0-index of the loop works as expected (model doing its job).

  -index of the loop 1 starts normally, but execution is stuck in the 'SIT scheduler.vi.

  Then I have no choice that to kill LabVIEW ("Reset screws" windows appear if I try to stop/close them).

  

  Is there a reason that I do not see what explains this behavior?

  Thanks for reading.

  Any help appreciated.

  Kind regards

  Hello

  I spent some time analyzing the VI driver as you suggested.

  Here are my findings.

  Question 1: the SIT connection manager does not pass to the model SW controls/indicators. Only, it allows the user map HW AIs/AOs.

  The only solution I found (to have a SW - for example a shared variable - object that is mapped to an input/output model) is to customize the VI driver that is scripted by the SIT Connection Manager ("_Baserate Loop.vi" in the flat sequence structure named "read code")

  Question 2: after spending some time in the VI driver, it seems that the VI to call right is not 'SIT scheduler.vi' but 'If SIT take model no time' (which uses the other as a Subvi)

  

  My conclusions are correct? If I use the API in the wrong way, please let me know.

  Kind regards

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

• LabVIEW 2009 SP1 crashes when moving large selection with the arrow key

  If I select a lot (10 or 15) diagram components and try to move some distance with the arrow button, I'm often a program crash.  Because a reduced number of components seems to hang after a longer distance traveled, it looks like some sort of buffer overflow error.  I don't see this problem when you use the mouse to move selections.

  I checked to make sure I have the latest version of the video driver for my NVIDIA Quatro FX570.  I also tried to work with no hardware acceleration and no handset, written.  What happens on Windows XP SP3 with all current updates.

  It became so bad that I have to do a save as every fifteen minutes to avoid losing data.

  Why not use my mouse for all movements?  Because it is not as specific and not so easy to limit to only one dimension of the movement.   My hand is not as stable as it once was.

  I'm hoping someone will have a suggestion that will clear up this problem.

  As I have indicated, I had the same problem with 8.5 and just DID a new install of Labview 2009.

  Since it is possible that my three monitors configuration, which of course requires more memory video, may be at the origin of the problem, I am satisfied with workaround by dragging the objects closer to their final destination and then using the arrow keys.

  Three monitors are ideal for the front, block and help/Internet/probe damaged.  When I got to work in the field with a single monitor, I felt severely handicapped.

  You can consider the issue closed.

  Thank you for trying to reproduce the failure.

• A distribution source created in 32-bit LabView 2009, explains that the screws are not executable when opened in LabView 2009 64-bit. How do the main screw?

  A source distribution was made for a VI using LabView 2009 32 bit. The distribution has been verified to work on another machine which ran 32-bit LabView 2009. However, when opened on a 64-bit LabView 2009, the VI was broken as indicated by the error message attached. How can I make the executable VI?

  The VI used the noise and vibrations and HSDL screw that I suspect don't are not supported in 64-bit.

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

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

• 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

• LabView 2009 Service Pack 1 does this cause a problem with the MAthScripts for lo

  All,

  I just installed Service Pack 1 for Labview 2009.  All of my code that loops in my MathScripts now lets my MathScripts does not compile.  Have a clue what I do?

  Thank you

  Rich

  Windows XP (32-bit)

  LabView 2009 uninstalled, reinstalled after you have removed all files related to 2009.  SP1 installed, then applied for LabView and MathScript.

• Remote panels and LabVIEW 2009

  Hello

  I updated my application PXI time real LabVIEW 2009 (Pro) and I'm now trying to connect with planels remote.  I can only have a remote panel open.  The other gives me the "connecting remote panels exceeds maximum number of licenses" the problem has not been captured in LabVIEW 8.5 and I have the remote license (unlimited) panel is activated in the License Manager.

  How this can be solved?

  Kind regards

  Patrick

  Hello

  The problem is now resolved.  This is a problem now at NEITHER and they had to send me a new license file I had to transfer on PXI.

  Kind regards