Editing software created with labview

Similar Questions

• 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

• Software FPGA with LabVIEW 2013

  I have a system with a rotating computer "development" under Windows 7 and an NI PXI-1036 chassis with a PXI-8101 controller as well as a card FPGA PXI-7853R. Recently, I upgraded to LabVIEW 2011-2013 of LabVIEW. I kept LabVIEW 2011 installed just to make sure everything is still working on the new LabVIEW.

  Now, when I open my project in LabVIEW 2013 Project Explorer, my FPGA comes with a warning triangle yellow next to him (see attached photo). The warning says:

  "Software support for this target FPGA is not installed on the computer. You can view and copy elements into the project, but you can not compile any screw under the FPGA target, until you install support for the target. Refer to the documentation of specific material for more information on the proper drivers and for more information about the installation and configuration of the target FPGA ".

  Regarding the installed software, I have LabVIEW SP1 of 2013, 2013 of LabVIEW FPGA Module SP1, SP1 of Module 2013 LabVIEW Real-time, and Xilinx Compilation tools 14.4. On the chassis of the TARGET (with the PXI-8101 controller), I have attached a list of installed software.

  Interestingly, when I open the project in LabView 2011, no errors or warnings are present with the FPGA card. It is only under LabVIEW 2013 I see the warning. Did anyone see a glaring omission of software that could be the cause of LabVIEW raise this error? Thank you for your help.

  

  

  Best guess is that're missing you the driver for your FPGA device. Try to install the latest version of NOR-RIO (or at least the version supplied on your 2013 SP1 install disks). Have you installed device drivers at the time that you have installed SP1 2013 LabVIEW?

• 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

• VI Analyzer - edit saved config with LabVIEW 8.6.1 problem

  I use VI Analyzer with great success, but have recently switched to LabVIEW 8.6.1.  I am trying to load, edit and save a file previously configured and when I save and run a file CFG 'old', the tests are completely different.

  Specifically, I'm trying to change the chess ' maximum reported "since 'Block-> Style-> son under objects' from the default setting of 5 to 10.  After I change the value to 10 and save the configuration, change the selected tests stored in the CFG file and I can not run the same tests selected before changing the numeric value.

  I have attached my 8.6 and 8.6.1 CFG files

  I wonder if this has something to do with this serious bug.

  I think I found my problem.  We have recently added the LabVIEW Instrument Driver VI Analyzer plugin to our installation of LabVIEW. I created the cfg files until we added it.  I use the VI Analyzer API to load and run tests on a selected VI.

  When I insert my old CFG file via "tools-> VI Analyzer-> Analyze live... "on a computer to which I added the plug driver, the default behavior seems to be adding newly found as selected tests (checkbox = True). I changed a value ("Block-> Style-> son and objects-> maximum failures reported" and then by saving the CFG file, and then running the CFG file via the API.)

  I saw 22 more tests running that I select and thought that my change of the numerical value may have had something to do with the bug that I quoted above. I know what the problem is now.  I just need to deselect the Instrument Driver Tests when I save the CFG of the user interface.

  I would say when you load an existing CFG with the VI Analyzer, the default behavior for newly found tests should not be included (box = False), or that a dialog box should inform the user that new or previously configured tests (presumably of the plugins) have been found or are detected as missing.

• How the interface telnet or PuTTY or plink software Windows with LabVIEW

  Please find the screenshot attached screen of the problem that face here.

  He is, can't open the telnet session by using the IP address of the DEVICE. But after that am not able to send commands or argument to the PuTTY or plink.

  Exec System does not accept standard input.

  In the plink.exe screenshot began operating only after sending to put manually... and after getting invited ">" if I send the command 'SEND' to plink.exe he answers returns with the data of the unit.

  Here I am not able to automate this send command Enter and SEND to get the data of the unit.

  He will be grateful if someone give me a solution.

  Thank you

  Vijay

  I solved this with Telnet VI by adding \r\n for all orders that we send to the unit.

  Pls find the attached final VI in LabVIEW 8.6

  Concerning

  Vijay

• exe created with labview, 2012 will not be run using LVRTE2013

  I created an exe using Labview 2012.  I had the user to install the latest rte (lvrte2013).  The exe wouldn't and told the user to TENS of 2012.  Should users have the same rte for each exe?

  Yes.  But different rural enterprises can co-exist on the same PC.

• OR LabVIEW Student Edition Software Suite 2013 with toolkits 2012 cannot load

  OR LabVIEW Student Edition Software Suite with LabVIEW 2013

  The toolkits LabVIEW which accompanies the software were dated 2012 and therefore will not instal without prior agreement of LabVIEW 2012 installed.

  2012 LabVIEW Control Design and Simulation Module
  2012 LabVIEW MathScript RT Module
  LabVIEW 2012 LEGO MINDSTORMS NXT module
  Module OR Vision Development 2012
  LabVIEW Toolkit 2012 Digital Filter Design
  Toolkit OR Modulation 4.3.3
  2012 LabVIEW System Identification Toolkit
  LabVIEW Signal Express 2012
  NEITHER Vision Builder for Automated Inspection 2011 SP1
  NEITHER Vision Acquisition Software 2012.08

  Thanks for any help

  Mike Petrowski

  Hi Mike,.

  Have you tried to download versions of 2013 from the web page? That is to say:

  http://search.NI.com/nisearch/app/main/p/bot/no/AP/global/lang/es/PG/1/q/control%20Design%20&%20Simu...

  http://search.NI.com/nisearch/app/main/p/bot/no/AP/global/lang/es/PG/1/q/MathScript%20RT%20Module%20...

  http://search.NI.com/nisearch/app/main/p/bot/no/AP/global/lang/es/PG/1/q/LEGO%20MINDSTORMS%20NXT%20M...

  Another option would be that you install LabVIEW 2012 and try again to load the 2012 versions.

  Concerning

• Modbuss problem with Labview 12 DURATION

  Hey guys / girls.

  I have a labview.exe work created with Labview 12 on a PC with the completely installed verstion LV12

  As I said created and built and tested again on the pc

  On another pc I just installed labview RT and the exe to bed

  the program consist of modbus

  but it does not work.

  Y at - it an additional package, I need to add more to the Runtime to get my Modbuss to work

  additional information:

  I tried two different com Modules while both B & B electronics is with drivers other works out of the 232/485 with drivers troubleshooting

  It is on Win 7 32 bit labview is 12 32-bit

  -Kurt

  What modbus library are you using? DSC or VISA? You have the runtimes for what you use.

• IMAQ PCI-1424 compatibility with Labview 8.6

  Hi, the computer that I used for image analysis had a broken motherboard issue, and I replaced it with a new one. I removed both the drives and the jury from the old computer to the new and then installed IMAQ Labview 8.6, but Labview 8.6 is not compatible with the software programmed with labview 5.0, so I uninstalled Labview 8.6 and re-installed Labview 6.0 image processing. I still have some problems to run the Analyzer software and image processing. After you have uninstalled the software or labview, the computer does not start correctly, poping up error as information "check your hard drive to ensure that it is properly configured and completed. Run CHKDSK /F to check for hard drive corruption, and then restart your computer."

  Some basic information on this computer and the image acquisition system (introduced in 2000) are as follows:

  • Windows 2000 operating system;
  • LabVIEW 5.0 basic package;
  • IMAQ vision for Labview advanced;
  • IMAQ PCI-1408, Cables IMAQ-BNC-1 and or-IMAQ for Windows NT / 95;
  • IMAQ-A2504-1 (1 m).
  • Sony XC - 55 1/3 "Interline transfer progressive scan CCD, 659 (H) X 494 (V), C-mount with JB - 77, SERVICES-12 p-02 and DKT503M;
  • Computar H1212FI 1/2 "mount C 12 mm w/focus and iris (10 inches FOV at 24 work dist.);
  • Extension tube Kit Computar VM100;
  • GRAFTEK high frequency fluorescent light 11 ";

  -What hardware IMAQ I use compatible with Labview 6.0 or 8.6? Should I install also drivers for the hardware of the IMAQ when I remove the card IMAQ? All the solutions for my problems? Thank you very much in advance!

  Hi simpra,.

  Here are two links to articles that list compatibility between Windows & LabVIEW and LabVIEW and IMAQ.   Why do you say that the image processign software was not compatible with the LV 8.6?  A message appear?  Or it simply did not work?  Also, are you talking about Module Vision Development, by chance?

  I'm afraid that I can't help hard drive corruption, if that's the case here.  Have you been able to go beyond that?

  My suggestion is to upgrade to the latest version possible.

  I hope this helps!

  Kristen H.

• editing in BC with Muse and what else?

  Hello

  I know that we can have on Business Catalyst for editing sites created with Muse. But anything else?

  I can't find any information and e-learning on: e-commerce platform, email-marketing, articles, adding page with model, web application custom...

  Possible with sites created with Muse, how does it work?

  Where can we find good tutorial to use all possibilities of BC with Muse?

  Thank you very much.

  SEB

  The best resource for adding features to Business Catalyst for a Muse site is http://www.bcgurus.com. Some content, for that you must be a member but the bases are free. It's the best Business Catalyst tutorial site out there.

• The jury of ELVIS will work with LabVIEW Student Edition 2010

  Hello

  This question was asked in the forums of LabVIEW, but no solution has been found. I have a windows 7 x 64 machine with LabVIEW 2010 Student Edition. When I try to install ELVIS 3.0.5 traditional software I get the following (no error code) message: "this Setup program requires the LabVIEW 8.5 development system or later to be present on this computer. Development system LabVIEW Base in any version of LabVIEW is not supported. Please install LabVIEW and then rerun setup of NI ELVIS. »

  I also installed the DAQ software for PCI DAQ board. I do not have access to a 32 bit machine and do not know how to get my board work (no ELVIS II) ELVIS. I have provided a screen shot of the message during the installation of the software of ELVIS.

  .

  Hey dduong16,

  Thank you very much for taking the time to provide additional information. After talking with several experts about your system, we concluded that this error is the result of an incompatibility between 3.0.5 Elvis and LabVIEW 2010 64-bit. Even the latest drivers of Elvis are not yet supported by 64-bit LabVIEW: see notes in support of the operating system on the Readme Elvismx 4.2.3

  To solve your problem, you will need to uninstall the 64-bit version of LabVIEW and install a 32-bit version. If you are a student, you should be able to get this version of your computer (it will work fine with your Windows 7 64-bit OS - it will install on 32-bit OS emulated inherent in your system). If you are not a student, please send me a personal message, and we will be working with an account representative to get you the necessary version.

  I apologize for the inconvenience, this made you and appreciate your patience. We have updated the Elvis 3.0.5 Readme to reflect this incompatibility (the change may not appear yet, because it takes time to propagate through our system), and I'm trying to create a Base of knowledge on the subject article to help future users who encounter this error.

  If there is anything else that I can help you, please you after return. Thank you!

  ~ kgarrett

• Conversion/appeal of an application created with CVI in Labview

  Hello

  I have a third-party application code created with labwindows CVI (attachment: scissor lift CVI code.rar) which is used for our control of movement of CT scans. I want to serve the Labview 8.6 my main software for data acquisition and software interface for my development. My idea is to create a dll from this CVI code and called the dll with Labview library import function is shared.

  My problem is that I am no expert in CVI programming if anyone can help me how to create a dll from this code? or any other suggestions to implement this conversion?

  Code CVI attached for reference.

  Thank you

  Lojius

  A starting point can be found here

• allow to create or write a PDM file with labview 2014

  Hello

  I need help. I'm new with LabView. I tried to create a PDM file, but it does not work. My code in the link below is really simple, but I don't know what the problem is. My code doesn't throw any errors so I don't know what to look for in the internet. Once my code is excuting, no file is created. I use LabView 2014 and my laptoop has windows 7 on it.  My question is, in all I need to do whenever I create a new VI of specific configurations that will be play/create/write a .tdms so that my code may work correctly because the writing in a .txt file works perfectly.

  Thank you and sorry for my English

  Hi bmtanguay,

  you want to run your VI on your cRIO9074?

  Where do you think your cRIO creates this file? A cRIO is a clean computer - and it has its own 'hard drive '. This is where your file is created: C partion on your cRIO!

  You cannot create a file on your Windows pc from a VI running on your cRIO!