Executables LabVIEW 2016

Similar Questions

• Support for LabVIEW 2016

  Can someone tell me what VirtualBench drivers will be available for LabVIEW 2016?

  Release date is... right now! NOR-VirtualBench 16.0, with the help of LabVIEW 2016, is available here:

  • Driver 16.0.0 and NOR-VirtualBench Application

  (My apologies for yesterday, does not but it takes a little while to download pages to go live.)

• Cannot run executable LabVIEW on desktop connection remote

  I have a couple of executable files, which are compiled using a LabVIEW 2011 development system, installed on a Windows XP computer.  These programs run fine when I double-click the icon while sitting at the computer.

  If I connect to the phone remotely from another Windows XP computer using Remote Desktop connection, I can use the remote computer normally except for the executables LabVIEW.

  When I double-click on one or the other, I get the error message displayed in the attached file. The part of the text of the report has no useful information, just two lines that seem to be field for e-mail names.

  What gives?

  Remote debugging is not a good substitute because it requires the executable file already be running.

  I was able to run two executables LabVIEW on desktop connection remote to a virtual machine of Windows 7 with 2 GB of RAM, running on a MacBookPro using Parallels Desktop.

  This confirms that the problem was insufficient for memory resources.

• LabVIEW 2016 high RAM usage

  I just upgraded to LabVIEW LabVIEW 2015 2016. Previously, I had no problem of memory. With 2016, however, even though I have a few screws open, rest, only LabVIEW uses 3 GB of my RAM. As I only have 4 GB, it slows down my computer to a crawl. Everyone knows these problems with 2016 or someone has a solution to reduce the amount of RAM LabVIEW requires? Thanks for the help.

  One of my colleagues has some portable "cheap" that are configured in the same way with minimum memory (4 GB).  Even when you are running Windows XP (which, in my view, is smaller and needs less RAM than, say, Windows 08/07/10), it has been very slow to do anything (can you say 'Wait 5 minutes for the OS to load'?).

  When Windows is "do its thing" correctly, it usually creates a swap file so that the software can use more than 4 GB of storage space for himself.  As I have indicated in my answer, LabVIEW 2016, when loading, seems to take a small fraction of this (a few hundred MB), even with the open code diagrams and block.  However, if your PC takes several minutes to start, runs very slowly in doing routine tasks and is an 'old' or ridiculously short of memory, it may be wise to (a) upgrade your memory (if you can), or (b) to upgrade your PC to the less a machine with 8 GB.  Remember, you use the PC to run LabVIEW, a solid programming / Data Acquisition/Platform Instrument I/O, surf the Web, send e-mail, or (hmm, I was going to say 'play', but games moves too, and tend to put more demands on the LabVIEW PC material, so both worse...).

  Bob Schor

• Is LabVIEW 2016 fully 64-bit compatible?

  Also recently as in 2015 of LabVIEW, the 'conventional wisdom' (which, I admit, I followed myself) was "install LabVIEW to 32 bit on 64 bit Windows , unless you were really given Big stuff on a PC with a lot of memory.  I (bad?) believed that this was particularly important with device drivers and possibly with RT I also (I thought) heard that NEITHER was currently heading LabVIEW on a platform 64-bit "pure".

  I wanted to ask OR the week, but in the excitement of it all, I forgot - should now consider us install LabVIEW 64-bit on Windows 10 x 64 platforms?  What LabVIEW RT platforms, including PXI controllers?  [Hmm - I didn't follow my own advice on the Forums and do a simple Google search - just a second...]

  OK, the Web seems to say that LabVIEW 2016 has "more support for 64-bit computing".  Maybe now is the time to take another piece of my own advice and "experience" - maybe I'll build a 'pure' 64-bit system and see if I can port my LabVIEW RT code for her...

  Bob Schor

  OK, the answer to my question is "No."  NOR, we have

  • The Time Module is only compatible with LabVIEW (32 bit). Therefore, you must have LabVIEW (32-bit), even if you use a 64-bit operating system.

  Bob Schor

• LabVIEW 2016 NI_ReportGenerationToolkit error

  I upgraded to Labview 2015-2016, but when you open one having previously worked for the project I now see an error in the NI_ReportGenerationToolkit.lvlib:Excel_Save_Workbook.vi.

  He tells me that the invoke node contains terminal unwired or bad.  However, it's a NOR provided VI and has not been changed between updates. Please let me know if it is a solvable issue.

  Take a look at this thread.

  Ben64

• Sharing between several executable LabVIEW data queue

  I have 2 Executables (Exe) of LabVIEW where an Exe generates data and other we consume the same. Is there anyway that I can use a single queue for the same reference? Exe first gets the number of queue and stores the reference number in V.I.G where the second Exe to read this this V.I.G. reference number The error of the VI second dequeue mentioned the invalid queue.

  Is there anyway that I can share the same data between different exe files with the functionality of a queue?

  Each exe is mapped in its own memory space so in a context resource refs will not work in another, but...

  If you presentation engine of the Action in an instance must be used via the server VI Invoke node on the other, EI (Note: it will run in the context of the server) could queue data in the customer's name.

  Plese Note:

  If the alternate server is idle all of its resources will be invalidated (including the queue) but a ref to the EI will be valid. In this case, the enqueue op will fail if you have the code to take account of this situation. (been there, done that )

  The same approach works in any network where serve architecture VI can be used. I've used this approach about 10 years (less the queue) to allow the control of a plant of a laptop computer with an internet connection.

  Ben

• Installer and labview 2016 app builder

  After building an executable on a computer and install it on another with the installer nor, overlap the controls on the front panel, the fonts and graphics (box high etc.) are banging on each other overlap with other objects, text etc. How can I solve this problem? Course made window size was set to maintain proportions on different monitors. Installer has a file XXXXX.ini (name of my startup vi) but no labview.ini (configuration information?). Any ideas? Thank you.

  Right click on your screen on the Windows desktop, select Customize, and then select Show. Check that the fonts are on either 100, 125 or 150%. According to what has been defined when you generated your VI, this could be the difference. You can change it to match the other computer or follow these steps.

  Edit the INI file for your Application with the following lines:

  FPFont = "Segoe UI" 15
  appFont = "Segoe UI" 15
  dialogFont = "Segoe UI" 15
  systemFont = "Segoe UI" 15
  BDFont = "Segoe UI" 15

  (Use your & size of font, Segoe UI is Windows 7 by default).

  See you soon,.

  McDuff

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

• Using VI Server to check whether another executable LabVIEW is running

  Hello to you all, helpful people.

  I need to have a single executable check LabVIEW if an different LabVIEW executable is running.  The simplest way to do seems to be to ask Windows if the name of the executable runs.  A good thread is here.

  However, this requires the use of a tool (task list) that does not exist on all Windows operating systems I need support (all flavors of XP, Vista and 7).  In addition, even if I found an equivalent for each OS, I need to make sure that they continue to work and update my program whenever a new OS was released.

  A much better solution would seem to be to use Server VI in LabVIEW, so it is cross-platform.  However, despite reading over my printed manuals, by reading lots of subjects in the electronic manual, scanning through the forums and make some limited looking for a manual on the Web site of NOR, I still can't understand the basics of the implementation of a communication server VI between two executables.  It's very frustrating, because I'm sure it's a simple task, but I can't find the right instructions.

  A lot of instructions to configure a server VI say to go to tools-> Options-> VI Server: Configuration and enable the TCP/IP option.  Which seems exaggerated, if I only need communication on a local computer, but ok.  However, in other places told me that this sets the default settings for the instance of the main application (another subject I am still unclear on), so how does it apply to my existing LabVIEW project?  My current project is an executable, and I thought I would create a new build for the second executable specification.  Executable has all my existing code, while B executable would have just a reference VI available server ping, in order for an executable say if it is running.

  So I built executable B, and I joined his VI for your reference.  Deciding that the VI settings programmatically server configuration will be more comprehensible, I put options that seemed logical: a unique TCP Port number listen to Active = True, TCP/IP access list = IP Address of my computer and the executable = B.vi VI access list.

  In my test executable A.i, which I use to this get up and running before changing my main code, I use Open Application references with the IP of my computer, the unique port number and a short timeout.  I hooked up to a property App node to determine if I get the correct connection.  All I really need is to check the name of the Application and I'm good.  However, I keep getting 'LabVIEW.exe.

  If anyone call tell me that I forget in this simple configuration, I would be very grateful.  Some basics on something else I'm missing about how works the server VI, how the tools-> Options from the settings relate to all, etc., would be a big bonus.  Eventually I'll need a way to specify no IP address of the computer (or a way to interrogate LabVIEW), so I can broadcast these two executables on any random PC.

  Thank you in advance for your help!

  -Joe

  P.S. in the preview window that all of my text has run together; I hope sincerely that is not happy when he published, in particular given its length.  If so, I apologize!

  The application ini file should contain the following line:

  Server.TCP.Enabled = True

  Not to mention that this is a better way to see if your inside an executable file:

  

  Tone

• How to convert a c# executable to an executable LabVIEW

  I have a program that was created in c# by an engineer who has left the company.  C# is not widely used among my company, but is LabVIEW so I would like to convert the c# program in a LabVIEW program somehow.  I worked with C language before, but not as .NET, Java, or c#.  I downloaded Studios Visual c# and I can compile the program, change the executable window button sizes, etc..  I'm starting to learn a little more about c#, but I'm starting from scratch.

  I am, however, quite familiar with LabVIEW programming and have been using it since version 6.1.  I heard that there is an easy way to access a c# program using LabVIEW, but I had no luck find out how it's done.  In the past, I've created a dll with a C program and consulted the DLLS in LabVIEW, so I might be able to do this with a DLL that I created in c#, but I don't know how to create a DLL in c#.

  Could someone help me please to find how to compile a DLL with c# code in Visual Studio 2008 so I can use it in LabVIEW?  I searched online and I always find something that asks me to enter a line at the BACK from "SCC" command prompt, which is not a recognized command.  I was expecting something simpler and more user-friendly.  Otherwise, I would like to know all the shortcuts that are easier to access my c# program through LabVIEW.

  Thank you in advance to anyone who is able to help me or at least shed some light on my situation.

  I do not understand why you are doing a .NET library instead of a .NET application. I thought that the original goal was to deal with a c# executable. A .NET library is, well, a library, not an executable. Therefore, it does not (normally) a forms or user controls, then there would be controls and management functions to events for controls such as click on the button.

  As for your other questions: the controls would be adjusted in the same way as the code that indicates the text box. Simply change the node property to an entry instead of a reading. With regard to the definition of "sender" parameter, in my example, I just created a generic, empty sender. If you want to set this specific control, you need to get a reference to the control (like I did with the text box and use as first parameter of the table build).

  What about AutoIt: this is not intended to be used for access to .NET. The point of this is to completely ignore .NET and simply focus on the application as soon as it runs. It uses the low-level Windows API functions to simulate clicking buttons, text boxes setting, reading text boxes, etc. You can write a script and call it from LabVIEW or you can use the ActiveX of AutoIt interface to program the code in LabVIEW. For example, using the example that I had posted, a script that launches the application, click on the button and gets the value of the text box would look like this:

  ; Launch the application and wait for window to become active
  Run ("Test.exe LabVIEW Test\bin\Debug\LabVIEW")
  WinWaitActive ("Form1", "", 5)
  ; Click on the button "generate".
  ControlClick ("Form1", "", "[CLASS: WindowsForms10.BUTTON.app.0.378734 a;]") ("[INSTANCE: 2]")
  ; Get the text from the text box
  $var = ControlGetText ("Form1", "", "[CLASS: WindowsForms10.EDIT.app.0.378734 a;]") ("[INSTANCE: 2]")
  MsgBox (0, "Content of the TextBox", $var)

  Things '[class... '. ' is the ID of the access controls that are acquired using the AU3Info tool that comes with AutoIt. (In the documentation it says there are several ways to specify the ID.) The method of 'CLASS' is just one of them.) The same thing in LabVIEW would look like this:

  

  Note that this example uses ActiveX because it is the interface that exposes of AutoIt.  It seems a lot easier than .NET stuff.

• Delay in an executable LabView 10 starting with the present mapped drives in Windows 7.

  I am running windows 7 on a network peer-to-peer without internet access with an executable version of LabView 10.  Executables mapped access folders on the network and works very well once it is up and running.  The problem is the time required to run the executable when the mapped drives are present.  It takes about 65 seconds to start and now, windows displays the message "not responding".  But it always starts.  If the mapped drives are disconnected, the executable file starts in 5 seconds.  The same executable running under windows with the same mapped drives THAT XP doesn't have this problem.  Any ideas?

  Hello Rgenaway,

  Probably, it is simply a matter of Windows than a problem of LabVIEW. The difference between the time it takes to start when the drives are present and absent could be due to both the application and the readers need to connect and start communicating.

• Why my executables LabVIEW losing features GPIB after update to 488,2 drivers

  A year ago on a remote test unit, I had put in place for a production line, a worker had decided to launch National Service update of the Instruments on the test PC and update all available programs. After this update, none of the GPIB functions worked on test executable for the test of LabVIEW software. After the execution of Automation Explorer, I was able to confirm that all of the GPIB instruments were still present, operation and alias still correct. The only way I could solve this problem was by erasing all National Instruments software and put it back into place, again.

  Yesterday on a local test machine is the same thing. This time 488.2 full driver package has been installed from a USB stick to update the 488,2 drivers on the machine and subsequently, none of the GPIB functions worked, causing all LabVIEW test executables to lock up. Once again, Automation Explorer shows that the GPIB instruments are installed and functioning and all aliases are always accurate. I erased all the software of NOR and reinstalled but now I stil can't get LabVIEW programs to work properly.

  Someone at - it of another expereinced this problem?

  What is the solution?

  After thinking the problem to the remote installation, it appeared that after a year of operation, the problem occurred after update 488,2 pilots to the new version 14.0

  The cure is to install the drivers of v3.1.2 previous back on the system.

  I uninstalled all the software version 14 of OR out of my test PC set-up and installed the package v3.1.2 OR-488. 2 and all the executables started working again.

  The Readme for VISA DURATION v14.0 says is comaptible with LabVIEW versions 2011-2014, but apparently there is a problem at least 2013 that touched me.

• How to build executable labview with all dependencies and libraries contained in .exe

  Hello

  I developed an application that uses several external libraries: JKI JSON string, Datagrid, etc... Under the build properties destinations, I select Main.exe. Under source code file settings, I have everything marked 'Set destinations for all content items' = Main.exe, 'Set destinations for packaged and shared libraries' = Main.exe.

  However, when the build is finished, I still find that JKI libraries are still in separate folders. There are literally dozens of JKI files, each of them contains 1 or 2 screws in addition, the same for the equipment operators.

  What I missed and how do I fix?

  Thank you!

  What LV version do you use?

  Make sure that you have not accidentally checked the box 'use LabVIEW 8.x file layout' in your build script.

  Norbert

• How to fix the error of Labview 2016 (32-bit) on Windows 10 database.

  Hello

  I have software to read/write of labview (32-bit) database, which works fine on windows xp 2000 / 7 (64-bit). But it is not stable 10 (64-bit) Windows at all.  It pops up an error on most of the time. Please see the attached database VI. After starting my software, usually, there is no error on the face of the database of frist. but it pops up an error when opening the database section. the East-2147418113 error code. It seems that it will be more stable if I put more than a few seconds before you open the second database.

  Could someone help me understand how to solve this problem?  Enjoy.

  Steven