LabVIEW 8.6.1 executable do not work

Similar Questions

• LabView 8.6 TortoiseSVN PushOk does not work

  Hello

  I use LV and PushOk since a while and everything was fine. Now, I've updated to 8,6 and CSC no longer works.

  The use of TortoiseSVN everythink works. Status in LV is updated if I use TortoiseSVN at the checkout a file.

  I get the following error messages.

  any ideas?

  THX Andrew

  LV 8.6

  Turtle 1.5.7.15182

  PushOK 1.5.1.1

  Windows XP SP3

  Hai,

  I've found a workaround. I had to change my attached configuration. just a dummy repository, not the original one. don't know why, but I works.

  Best regards

  André

• 'Write Key.vi' does not work after generation

  I'm having trouble with the "Key.vi write" I use it to record the calibration values in an .ini file. It works fine when running in mode of development, but after that I build it into a stand-alone exe it does not work. It will create the file in the correct folder, but it is empty. I don't know how to figuing this one initially. Any help would be greatly appreciated.

  The following code stores the configuration values in the .ini file. I'm using LabVIEW 8.0

  

  Why my executable does not work when you use the constant path of the current VI? -Knowledge base - Support...

  I'll let someone another chime in here about all local variables. They are there, waiting in the bushes, ready to pounce when they see one of these little critters. It's always the season for them.

• Agilent 6812 B power cord does not work with the class IVI driver

  I try to use a power source Agilent 6812 B with class IVI DISARM on RS232 driver.  I have everything set up NI Max but I can't by the initialization routine.  I tried in LabView and LabWindows and nor will not work.

  I decided to follow the lines RS232 RX/TX and I see that he is sending the "* IDN?" command and it times out before receiving a response.  Unfortunately, it does not send the Terminal newline at the end of the string.  I can cross NI MAX and send "* IDN? \n' and he responds with the ID very well.

  So my question is, would be possible that the IVI specific driver is not written correctly to send a jump as an end of line character or do I need to configure the Compote to send this character separately?  The IVI driver has been downloaded from instrumement network driver of NOR and it says it is compatible with the 6812B, but has been tested with 6813B.

  
  

• Reminders does not work in the executable LabVIEW front panel

  I have a couple of reminders in the process template that trigger an event in the event structure to update of the lights on the front panel for the user. Everything works fine until I have create an executable file. This can also be an indication of the other points, I have not discovered yet.

  Any ideas?

  Thanks for all the help.

  Found!

  Not unlike most of LabVIEW developers, I have a range of utility screws that I use over and over again. Such vi is vi uses a property node to find out what environment the application is running in, i.e. .llb, exe, development, publishing student, etc.. This vi is used because SEO screws in an executable file have a way different than when their listing in the development environment. Using this vi allows your code to reference the screws properly when developing and when the executable is built. The code still works because it automatically adjusts the referenced path of the vi. See attachment 'Path Finder.vi environment'.

  Now for the fun part! For some reason, perhaps because of the friendly character of NOR and the relationship it is with its developers :-), AND decided to change the path of the executables in LabVIEW 2009. After hours of troubleshooting and countless rebuilt, I came to the conclusion that the ' paths of the band of "work magically stopped working. It was at this time one of my friends happened to walk and ask why I had everything in my monitor across the room (figuratively speaking of course, I'm sure we've all been there). I explained what could be the only conclusion, band paths do not work!

  My friend immediately began laughing, having recently had the same problem. He explained that in LabVIEW 2009 executable paths are different and our 'find the path vi' would not work. He added that NOR, after finding this funny, however gave the developers a way to solve this problem with a check box within the app Builder. The box is called "Layout using LabVIEW 8.x file." See attached photo named "App Builder."

  The only thing I could say to my friend was, ' silly me, I should have know what that.»

  Laughing out loud

  Thank you for trying to help, it launched my butt.

• VI LabVIEW Report Generation Toolkit elements in a TestStand sequence does not work with a LabVIEW 8.5 run-time engine

  Hi all

  I'm using LabVIEW 8.5.1 and TestStand 4.1. I did a sequence TestStand with a VI in this document, which uses items Report Generation Toolkit. On my machine I use LabVIEW and TestStand development system license. On another machine I use TestStand with basic deployment license and I chose the LabVIEW 8.5 run-time engine in the Configuration of the adapter. Everything works well except this VI with elements of Report Generation Toolkit. The error message shows that the VI is not executable. It works well only after I installed with a trial license and selected LabVIEW LabVIEW 8.5 development system in the Configuration of the adapter.

  I found other posts and a document in the knowledge base with a similar problem: http://digital.ni.com/public.nsf/allkb/8A0E6274D9BD7B1986256F62006AD402?OpenDocument but I am not no EXE files in my sequence, so I do not know how to fix mine. Someone has an idea?

  
  

• print easy text.vi does not work in the executable

  I have 3 computers to target that runs labview 2012 on a PXIe8101controller.  In my statemachine the vi prints a report using simple text, report vi (palletized report generation) at the end of the trial.  Its an executable vi on all 3 machines.  On 2 machines, it works fine.  On the 3rd he hangs up when I'm logged in as a standard user.  If I log in as an administrator, it works very well.  The thing I noticed is that on 2 machines, that it works, the image is "factory...". 1.2.1F6' (under control panel > systems).

  On the test equipment that it only works in admin mode the original image is 1.2.4.f1.  MAX is also 5.3.1 on that past fine and 5.5.0 f1 on the one that does not work on.  Everything I'm mssing?

  Thank you.

  solved...

• Creating a file executable, analog (sensor) does not work

  Hello

  I had a question about the creation of an executable via labview for my project be used on other computers.

  When I create my executable, everything works well except my analog inputs. As I can't get on my my executable sensors readings. It works fine on my test computer, however when I transfer it via the executable (which doesn't have labview on it) the program is not read sensors.

  I used both analog outputs and entry in my program, the difference is that for the release, I used the standard DV DAQmx and for analog input, I used the DAQ assistant. I don't know if that has anything to do with it, but the output works, just that the entry is not.

  I have attached my VI to make it easier for you guys to answer my question.

  Thank you

  Justin

  Too bad! solved the problem

• In 2012 LabVIEW MathScript RT module does not work

  Hi all

  I recently installed LabVIEW 2012 in my PC with Windows 7. However, Mathscript does not at all. It says "an internal error has occurred in the MathScript RT Module.  Restart LabVIEW and try again.  If the error persists, reinstall the MathScript RT Module. "I did it, but still does not work. It is said further than Mathscript is missing or not installed", but I have installed. What the problem would be, please?

  Have you been able to verify the installation and activation in the License Manager OR? It should say enabled for this computer and have a green square like this:

  

• description interface LabVIEW node will not work when compiling

  Hello

  I have a vi that seeks VISA resources and focuses on their name of the interface to select that you connect to.

  I have a strange problem where, if I run the vi in labview it works fine. When the vi is compiled into an exe file, it does not work.

  I traced the problem to the property node "name of Inst Intf' which gives the description of the interface. In Labview, the node of this property returns the description of the interface, as expected.

  When I compile the vi, this node property returns empty strings.

  The station nearest you, that I could find to this kind of problem is it

  http://forums.NI.com/T5/instrument-control-GPIB-serial/why-visa-property-interface-information-inter...

  However, the exe is running as an administrator, so I don't think it's a problem with permissions.

  Any help would be greatly appreciated.

  I have no idea of what was the cause, but I uninstalled the device drivers for the hardware I used, reinstalled and then restarted the computer and now it works fine.

• Windows 7 executable lonely spider and other games of executable files do not work

  I installed windows 7 and windows games do not work. Whenever I try to play the lonely spider, it is said the executable no longer works and the game closes. Spider not only but all windows games that come with windows 7. They have all worked with vista on a 32-bit system. I am now on windows 7 64 bit. Other then this problem I like windows 7 but I need spider solitaire. Thank you!

  Hello

  Run a SfC scan:
  http://support.Microsoft.com/default.aspx/KB/936212

  Good luck $

• [LAVA Cross Post] CTRL + SHIFT + Alpha shortcuts do not work in LabVIEW

  Cross-post from the LAVA: http://lavag.org/topic/15619-ctrlshift-shortcuts-sometimes-not-working-in-labview/

  Bug Synopsis: CTRL + SHIFT + Alpha shortcuts do not work in LabVIEW. In particular, CTRL + SHIFT + Z, CTRL + SHIFT + E and CTRL + SHIFT + S

  Test installation: 32-bit LV2012 with the patch of f1 running on Win7 64-bit inside a Parallels VM in OS X 10.8.1 8

  To sum up the tests, I tried:

  • Several different combinations LabVIEW, guest OS and host OS all fail, including:
  • • LV2012f1 32 and 64-bit and 32-bit LV2009
    • Win7 32 and 64-bit and Windows XP x 64
    • Parallels and Parallels 7 8
    • OS X 10.7 and 10.8
  • Capturing the keyboard to the virtual machine
  • Turn each keyboard setting possible on Parallels, guest and host
  • Reinstall the keyboard drivers
  • Connect a checked keyboard that works on a native Windows machine
  • LabVIEW.ini deleting and letting it regenerate
  • Remapping the shortcuts, for example, CTRL + SHIFT + E to CTRL + E - in this case, 'Show project' works, so this may indicate that it is a problem registering the shortened press, do not invoke the action itself.
  • Sending via the keystrokes on-screen keyboards of guest and host
  • Sending the sequence of keys via SendInput by user32.dll WinAPI
  • Test every imaginable combo of SHIFT, ALT/OPTION, FN, COMMAND/CMD, CONTROL
  • Reinstall the virtual machines from scratch and relocation of LV
  • Here's a kicker: CTRL + SHIFT + Alpha shortcuts work very well on other windows programs (I tried 4 different programs, including Chrome, Notepad ++, Paint.NET), but it does NOT work for VIPM with CTRL + SHIFT + C. This means that only two programs where there are CTRL + MAJ + Alpha bugs are both related to LabVIEW.
  • Here's a better: it is only CTRL + SHIFT + Alpha shortcuts with the prob - CTRL + SHIFT + 3 properly active / deactivates grid alignment and the "tools > Options > Menu shortcuts" will record any shortcut CTRL + MAJ + Non-alpha; He was not only meets the shortcuts CTRL + SHIFT + Alpha.

  New idea of troubleshooting is highly appreciated; Please feel free to jump in here or on the LAVA.

  X. says:

  Still well and alive in Parallels 9 and LabVIEW 2013 SP1. Of course I could upgrade the latest versions to see if things have become more.

  Any news on that?

  @mellroth has found the solution :-)

• Some executives in a window will not work on FF (work on IE and Chrome)

  Some websites that have integrated the content do not work on firefox. A good example is

  https://www.virginmobile.com/VM/ukCoverage.do?ContentId=coverage.in.UK.howdoi.sm235

  This should show an integrated card powered by google that shows the coverage of the network

  Although this isn't the only site that displays this problem.

  Hello, you can try to reproduce this behavior when you start firefox in safe mode, once? If not, maybe an addon like adblock plus is involved here...

  Troubleshoot extensions, themes, and issues of hardware acceleration to resolve common problems of Firefox

• Serial communication does not work in an executable file.

  I created a vi that communicates with a serial device. It works fine on the computer on which it was created on. I then created an application and then built an installer to put it on another machine. The second machine doesn't have a LV 2009 on it. Once installed on the machine the vi does not work. When it is running on the computer with LV 2009 the com port control is a pull down, and it lists all agrees on the computer, and then you select the one you want to connect with. The vi is installed on the computer does not list the available com ports. This leads me to believe that there is no support Comms series in the installable version. What should I do now? I noticed that you can add "Additional installers" when you build the installer and one of them is NEITHER Serial 3.4. I'm trying to add this and a message says that he had to get, so I used it thinking it was more that I needed and this standard com port driver would be included. Am I mistaken or did I miss something? Any help is greatly appreciated.

  [email protected]

  I'm sure that NEITHER Serial is the driver for COM port cards of NEITHER, and that very probably that you have to install NI-VISA.  You can add the VISA installer as an extra Installer for your application.  It may ask you a DVD during the build process, because even if the software is already on your computer, the installer so it probably isn't.

• Screw worked in LabVIEW 2009 but do not work in LabVIEW 2010

  The screws were initially written in BT 7.1 but then compiled in 2009 LV, and saves. These screws worked well on the Windows XP machine.

  Unfortunately, the XP machine was crushed and I try to run these screws in LV 2010, with windows 7, 32 bit.

  I installed the traditional DAQ drivers (latest version, 7.5) alongwith DAQmx (version 9.8).

  We use these VI to control valves of depression, using PCI-6503.

  To begin we first use a VI that reset the valves and the PCI card. The name of the first vi is: portconfig.vi this port and port config vi uses write screws I see error 10401 port config vi, when I run, step by step (i.e., sequence 1). However, the VI work but do not do any actual work.

  The second VI which depends on the first VI and therefore the second VI also does not work. on this VI, we have buttons (representing the valve) and when you click on them, the valves must close or open, but nothing happens in LV2010. the same screws worked in LV2009!

  Card PCI-6503 is defined under devices and interfaces in MAX. It is not defined under DAQ devices. When I test PCI-6503, it works.

  I enclose the two screws (there is in QuadMain.llb). I don't know how to get the real VI of your hard drive...

  first open portconfig.vi

  then open Control Panel.vi

  There are global variables used in the Panel.vi control, there are listed in the Global.VI Valve, which is located in globals. LLB second attachment).

  I really appreciate if someone can convert these screws for LV 2010.