MCB2400 LabVIEW 2009 Embedded build error

Similar Questions

• LV 2009 SP1 Build error OR

  While trying to do a build on LV 2009 SP1, I get this error:

  The build failed.

  An error occurred during the recording of the following file: Sample.VI

  Details:

  Visit ni.com/ask support request page to learn more about the resolution of this problem. Use them following as a reference: 1 error this is produced to AB_Source_VI.lvclass:Close_Reference.vi-> AB_Build.lvclass:Copy_Files.vi-> AB_Application.lvclass:Copy_Files.vi-> AB_EXE.lvclass:Copy_Files.vi-> AB_Build.lvclass:Build.vi-> AB_Application.lvclass:Build.vi-> AB_EXE.lvclass:Build.vi-> AB_Engine_Build.vi-> AB_Build_Invoke.vi-> AB_Build_Invoke.vi.ProxyCaller

  Possible reasons: LabVIEW: an input parameter is not valid. For example if the input is a path, the path can contain a character not allowed by the operating system such as? or @. = OR-488: command requires GPIB controller charge controller.

  Note that I do not use any GPIB. Also when I build the project NAV 2009 (without SP1) on another computer, I get no error. Any ideas?

  An Application (EXE). Now what I've done is removed the previous generation in the project framework > My Computer > specifications build and created a new Build > Application (EXE). And he built successfully!

  Now, of course was was wrong the first time... but it works now. Thank you!

• LabVIEW 7.0 build error 26097

  Hi all

  Blast from the past here.

  I'm working on resurrecting an old program (I work for a company where our products are used for 30 to 50 years).

  I have all the screws assembled, the computer is a Windows XP running LabVIEW 7.0 Professional with demand for construction.

  When I try to compile the program, the application chugs, adding screws etc, but then it happens to this (see attachment):

  Anyone seen this before?

  Thanks for any help.

  Let me know if you have any questions that I can answer.

  Dan

  Hi all

  I should have updated you all on that yesterday.

  I found my mistake.  I missed to implement a patch that NEITHER we gave way at the time where we put it all together.  I installed once everything was fine.

  I appreciate the time you took to review the question and I'm sorry for the wild goose chase.

  With a few special programs, it is best that keep us those in their original configuration, where the use of 7.0 in this case.  Rest assured for any new project, we use the latest and best in LabVIEW.  It will be interesting to others down the line have to say when they pick up the new code that I'm developing now in 15 to 20 years.

  Best regards

  Dan

• 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

• Narrow ARM of SPI VI reference works do not for me LabVIEW 2009.

  I use LabVIEW 2009 Embedded for ARM in collaboration with the Council of development of LM3S8962 and the MCP3008 10 - bit ADC chip. I'm trying to use the base screws of SPI to communicate with the MCP3008 - see the attached excerpt from VI to my current attempt. I can initialize the SPI reference, read two bytes of data from the ADC, but when I try to close the reference, the application crashes. If I am the narrow ARM of SPI reference VI in a diagram to disable, the program terminates normally, and I get to see my two bytes of data printed on the OLED. Any ideas?

  Thanks in advance,

  Stuart

  Thank you!

  Who takes care of the immediate problem. I really appreciated the quick response!

  Stuart

• LabVIEW 2009 Build Path problem

  [Cross posted from LAVA]

  I got a code that worked fine on my home PC, when I moved to work, the exe would not build due to errors.

  Return errors are not good to explain the problem

  Until I got this one:

  

  Look at the path of the error:

  C:\Users\Developer2\Desktop\User group Meeting\LabVIEW 2009 new features\code\02 intermediate\01 build specifications\build file executable application. exe\LabVIEW 2009\vi.lib\addons\_ICON Library\String\_icon_lib_string.llb 9.0\my paths\dist\application

  This path refers to a VI inside of my executable!

  Maybe it's a bigger problem than I first thought

  So my question is:

  If a path inside my building that would be compared to the executable and LabVIEW must resolve, could fail, this process, depending on where the exe is located in a folder hierarchy?

  I guess it could have happened before? but it would be more probable now due to longer paths!

  Cross post solution

• 6 error when generating an executable in Labview 2009

  I am trying to build an executable that uses the Spectral Measurements Toolkit vi.  I have been able to build a source distribution that allows me to call my application using a runtime engine so I know that all the dependencies are correct in the project file.  However, if I try to build this as an executable file, I get the following message:

  An error occurred during the recording of the following file:

  C:\Program NIUninstaller Instruments\LabVIEW 2009\vi.lib\addons\Spectral measures Toolset\LVSupport\SMT niScope Utilities\SMT niScope Dependent\SMT Config niScope for .vi spectrum (auto)

  Invoke the node in AB_Source_VI.lvclass:Close_Reference.vi-> AB_Build.lvclass:Copy_Files.vi-> AB_Application.lvclass:Copy_Files.vi-> AB_EXE.lvclass:Copy_Files.vi-> AB_Build.lvclass:Build.vi-> AB_Application.lvclass:Build.vi-> AB_EXE.lvclass:Build.vi-> AB_Build.lvclass:Build_from_Wizard.vi-> AB_UI_Frmwk_Build.lvclass:Build.vi-> AB_UI_FRAMEWORK.vi-> AB_Item_OnDoProperties.vi-> AB_Item_OnDoProperties.vi.ProxyCaller
  
  Method name: Save target: Instrument

  The details of the message are:

  Visit ni.com/ask support request page to learn more about the resolution of this problem. Use the following as a reference:

  Error 6a held at AB_Source_VI.lvclass:Close_Reference.vi-> AB_Build.lvclass:Copy_Files.vi-> AB_Application.lvclass:Copy_Files.vi-> AB_EXE.lvclass:Copy_Files.vi-> AB_Build.lvclass:Build.vi-> AB_Application.lvclass:Build.vi-> AB_EXE.lvclass:Build.vi-> AB_Build.lvclass:Build_from_Wizard.vi-> AB_UI_Frmwk_Build.lvclass:Build.vi-> AB_UI_FRAMEWORK.vi-> AB_Item_OnDoProperties.vi-> AB_Item_OnDoProperties.vi.ProxyCaller

  Possible reasons:

  LabVIEW: File generic i/o error.
  =========================
  NOR-488: IO abandoned operation.

  I tried mass, the vi in the compilation of... \vi.lib\addons\Spectral Measurements Toolset\LVSupport\SMT niScope Utilities\SMT niScope Directory depending on, but for some reason any installer still tries to save to this place during construction and fails.

  Any ideas on what is happening here?

  Kind regards

  David

  Hi David,

  I built an executable with the VI, and I could not reproduce the problem.  Have you searched and found the VI in the specified directory?  A couple of things to try:

  -Use the LabVIEW 8.x file structure.  This lie in the advanced the Build menu.

  -Try and build an executable with just that VI.  Who will tell us if it is a symptom or a cause.

  Nick keel

  Engineering applications

  National Instruments

• Executable VI generating an error 222 on Keithley 2612 although his run correctly when starting labview 2009 directly

  Hi all

  I have a VI that works perfectly and I can control, a 2612 Keithley has for measurements of transistor.

  The VI run well when I realize it from the computer that has the Labview 2009 (XP OS) platform

  Equipment (IE Keithley 2612 A) is related to another computer that is not labview 2009.

  I installed the Run-time-engine 2009 (32-bit XP OS) on this computer.

  Then, I create an executable of my VI with the option 'build application.

  The executable VI starts normally on the computer, but when I run it, I get an error message from the Keithley 2612 (which wasn't the case when I ran the VI directly from the computer haing LabVIEW 2009 installed on it). The error message is 222 (ie the long parameter)

  I thought I did something wrong and I create an executable from an original VI of Keithley (IE without modification). I get the same error message.

  When I create an executable with the runtime engine 2009 included (because it is possible to do with LB 2009), I am geeting the same error message.

  So I need to check step after step, when the message arrives but

  Someone knows something about such a question?

  Thank you

  Hi all

  Just for those who might experience a similar problem.

  I found the solution after fighting all the possibilities.

  The source of the problem was (for some reason) that the country setting of the computer was wrong

  and decimals are written with one, instead of a point.

  As I correctly reset the country setting, stand-alone files work normally.

  Best regards

  Youki

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

• MathScript node: an error internal mathscript: 64-bit LabVIEW 2009

  Hi people.

  I have an installation now LabVIEW 2009 9.03f, Vision and Advanced Signal Processing Toolkit, all 64-bit versions on a new computer, so that I can convert a code from 32 to 64-bit.

  I tell myself that I will address the errors one by one and this is the first.  I have a VI with mathscript node and the VI, who instructed and ran very well in the 32-bit environment, is now broken and giving the error "mathscript node: a mathscript internal error."  My main concern - is mathscript unsupported in LabVIEW 64-bit right now?

  I enclose the VI.  Any ideas are appreciated.  I need to get this working.

  In addition, NEITHER is there a special forum of 64-bit we should publish in the future, or create to post on?

  Sincerely,

  Don

  2009 help

  LabVIEW MathScript is a language based on text that you can use to write scripts and functions. You can process the scripts using LabVIEW MathScript in the Window of LabVIEW MathScript or a MathScript node. When you create a LabVIEW MathScript, you use data types supported.

  The MathScript syntax is intuitive and logical syntax essentially based on the standard mathematical and computer programming terms, mandate of widespread and common use truncation or descriptive abbreviations and concatenations of standardized terms. The Window of LabVIEW MathScript and MathScript nodes are able to process files that you create using the MathScript current syntax and, for backward compatibility, files that you created using legacy MathScript syntaxes. The Window of LabVIEW MathScript and nodes MathScript can also process some of your files using other textual syntaxes, such as files that you created by using the MATLAB® software. Because the MathScript RT Module engine is used to treat the scripts in the Window of LabVIEW MathScript and MathScript node, and the MathScript RT Module engine can't stand any of the syntaxes, not all existing text scripts are supported.

  (64-bit LabVIEW) LabVIEW MathScript is not supported in LabVIEW (64-bit).

• DLL, error when quiting LabVIEW 2009 on WIN7

  Hello

  I reduced the problem in my EXE application code following joint (see attachment). Somehow the DLL (in User32.dll) calls create a problem when quiting Labview 2009. The Application remains resident in the bar of Windows taskbar and after a while an error pops up about that there was a problem to close the app and it may be reported to Microsoft if you wish. Then a second error message appears before the application disappears from the taskbar. If I remove the DLL:calls in the code then the problems disappear.

  Here I unloaded DLL calls on a special way before quiting LabVIEW?

  Another potential problem not mentioned in this article, it's that you have included your explicitedly user32.dll in your built application. This creates a 200% for sentencing as the kernel32.dll file user32.dll and others are always residently loaded into memory anyway and mapped in the system section of memory of a process. If you apply again to load this DLL by its explicit name, you end up having two copies of it mapped in your memory space of the process and which will cause really weird problems.

  To avoid this problem, make sure that the name of the library within the library node call indicates only the name of the DLL without any path information. Close the dialog box, and then save it. If you reopen the dialog box display the full path but it still save the name only until you make a change in the control of path, date at which you can eventually have a full path again.

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

• Remove labview 2009 without using Add/Remove program

  Hi all

  I have problem with the removal of LabVIEW 2009.

  I deleted some folders in the C drive, folder OR.

  Now I can't start my LabVIEW 2009 and it does not appear in my Add/Remove Programs list.

  I tried to delete all the folders and files in the C drive under folder OR, but the pop out error message shows that I don't have the authority to do so.

  So, how can I remove it completely?

  I had intended to reinstall LabVIEW 2009 after that I have completely removed.

  Very much appreciate your help.

  That's why I say try to reinstall LabVIEW. He could just do a repair of your installation. Then, you can use Add/Remove programs to uninstall completely.

  But when you uninstall completely there will be folders OR remaining. These are things like user.lib.

  Have you tried to reinstall the runtime?

  One last thing. I don't know how you got your installation so messed up, but remember that if you build a Setup program you should not install on a system with the development environment. There are so many things that can go wrong.

• LabVIEW 2009 installation, one of MS Office Excel VI is broken

  After installing Labview 2009, one of the MS Office Excel VI is broken. Tried several facilities. The same VI is broken and other screw works very well. What happens on 1 single laptop. the broken VI works fine on other laptops.

  Have you tried to search the forum? http://forums.NI.com/T5/LabVIEW/set-Excel-cell-color-and-border-broken-can-t-build-application/m-p/1...

  Open the Subvi, click the node to invoke that generate the error and select again the same method, it should get rid of the error (do not forget to save changes once the error disappeared.

  Ben64

• Build error: Add image and delete if possible.vi

  Hello

  I use LabVIEW 9.0 with the request of the manufacturer, and when I try to build my application I get this error:

  An error occurred during the recording of the following file:

  C:\Program NIUninstaller Instruments\LabVIEW 2009\vi.lib\printing\ReportDocExtensions.llb\Standard Report\Append image and delete if possible.vi

  Invoke the node in AB_Source_VI.lvclass:Close_Reference.vi-> AB_Build.lvclass:Copy_Files.vi-> AB_Application.lvclass:Copy_Files.vi-> AB_EXE.lvclass:Copy_Files.vi-> AB_Build.lvclass:Build.vi-> AB_Application.lvclass:Build.vi-> AB_EXE.lvclass:Build.vi-> AB_Engine_Build.vi-> AB_Build_Invoke.vi-> AB_Build_Invoke.vi.ProxyCaller
  
  Method name: Save target: Instrument

  I did some research and it seems to be related to save an image of the façade to the HTML file.  I am not save the image of front at all, nor am I store anything to a file HTML, Excel only.

  Just in case I had somehow inadvertently added to my project (this is my first project in LabVIEW and I made all kinds of mistakes, haha) I did a search for my project to "Add image and delete if possible.vi" and it has not been found.

  Does anyone have ideas on this?  I don't know what other information I should post here, please let me know if I missed something.

  Thank you!

  Apparently, I forgot the first rule of solving problems when you use a Windows operating system.

  Re-start.

  He is fine now.  Go figure.