LabVIEW project: Mass compile automatically

Similar Questions

• Version of selector mass compilation VI

  I was using Version TestStand selector to switch between the two latest versions of TestStand I have installed on my computer.  I noticed that when you switch between TestStand versions he reinstalles the TestStand addon in the LabVIEW directory.  This causes a small question, where I got a rubdown compiles this directory every time so I don't have to re-record my VI using the monitor for the termination and other VI in this library.

  Before that I post this as a request to the exchange of idea (to do a compilation of mass), does anyone know if this already exists (except manual)?

  Thank you

  Hi paulmw,

  One option is to write a VI to change the compilation version and the mass of TestStand directory automatically.  You can call the Version TestStand selector from the command line.  The arguments for this are displayed using TestStand.

  

  There is also an example VI here that shows how a directory compile mass.  This, combined with a system Exec function to call the picker version and you wouldn't have mass compile manually.

  Kind regards

  Brandon v.

  Engineering applications

  National Instruments

  www.NI.com/support

• There is a possibility to run Labview projects or to set them off from a batch file or if the exist and the ability to control labview or run it from an external application?

  Hi, I m a bit new in LabVIEW and I'd like to ask a few questions...

  -There is a possibility to run Labview projects or to set them off from a batch file or if the exist and the ability to control labview or run it from an external application?

  -One API PI or raspberry beaglebone exists for LabVIEW?

  -Power supply Wich can recommend you control with LabVIEW? (some chip solution witn 0 - 30v / 0 - 3A DC)

  Thank you very much for your advice!

  Best regards

  Elena

  Elena,

  I know raspberry, so no comment on that.

  For the rest:

  -Do you want to create tools for developers? If so, we must look in the API of project VI and VI server. If this isn't the case, please compile your application LV as executable and call this one using a batch file.

  -LV prefer specific supplies. LV is a programming language. There are several power supply providers (including OR) which provide directly the LV API for their power supplies. So, essentially, the approach is:

  1. choose food that serves your needs.

  2. check if the power supply has a standard interface for programming (such as Ethernet, GPIB, or if the power supply is PXI, is already providing a programming interface!)

  3. check if the LV API (so-called "instrument driver") is available for the device. In the case of a PXI system, get you a device driver (for example NI DCPower).

  4. check if the LV samples are available (for example in the Finder for example LV once you have installed the driver).

  Norbert

• Unable to connect target RT in the LabView project

  Hello

  I use time LabView real-time 8.5 on a desktop PC. I see the target at MAX where I can change the network settings on the target and use FTP without problem. But it is impossible to connect to the target in a LabView project.
  The error of the target journal wrote:
  ####
  #Date: Monday, June 9, 2008 03:04:29
  #OSName: PharLap
  #OSVers: 13.0
  #AppName: PH_EXEC
  #Version: 8.5
  #AppKind: AppLib
  #AppModDate: 09/06/2008 06:55 GMT

  LVRT. DLL loads the address: 0x003EE000

  Can someone help me?

  Thanks in advance

  Hello everyone.

  The problem is solved! The reason of my problem is that LabView RT 8.5.0 supports no more than 2 GB of RAM installed on the computer, as described in this document.
  My RAM GB setting the things that were not possible before:
  -to connect to the target in a LabView project and deploy the code.
  -to activate the multiple core processor in the BIOS of the machine

  I said that the withdrawal of the USB keyboard is useful. Indeed with my keyboard plugged in, when I install other software as server VISA for example, MAX do not recognize the target automatically, I have to add it manually by specifying the IP address and I can not connect to the target in a project of LV.
  Unplug the USB keyboard (and other devices) to solve this problem.

  Good day...

• Find the requirement software LabVIEW project

  Hello world

  Someone knows how, a LabVIEW project with multiple targets data (computer, Compact RIO sbRIO, PXI,...), which is the component of the software and drivers required to run correctly and completely the screws of the project contains assuming the screws project successfully on the developer's computer and I have the hardware components of project defined at my disposal.

  What should I exactly ask the report as software OR necessary components.

  Thanks guys...

  Hello

  With Labview 2013 generation project installation program may automatically add all additional installers to your installation package.

  I don't think that the process is perfect, but it should certainly help. More details here...

  http://zone.NI.com/reference/en-XX/help/371361K-01/lvdialog/addl_install_info_db/

• Max OR simulated PXI devices that are not present in the Labview project

  I added a map of e/s digital NOR-PXI-6527 simulated to my MAX NI PXI's, but it does not seem possible to access this IO card simulated in a Labview project.

  Is this normal?

  Have sorted it.

  It turns out that on my desk and PXI data acquisition driver wasn't the same version.

  Updated PXI, and then it worked.

  See you soon

• Is there a way to determine the equivalent ANSI C code of a Labview project?

  I'm a complete newbie to Labview.  I have this quite complex Labview project that was used to create a DLL that matlab may call to order my card PCI-6534 without having to know NIDAQmx calls.

  I am trying to find how to make these calls directly from Matlab NIDAQmx, but I do not get the same results when I call this DLL mentioned above, so I thought I would try to give a sense Labview projects live I begins to make sense of the general economy of the screw, but I would like to be able to run the project , step through it and perhaps see NIDAQmx orders (or something equivalent, so I can determine how to call NIDAQmx commands in Matlab).

  Is this possible to do?

  Thank you

  Jason

  Yes. The toolbar allows you to turn on highlighting so that you can run the VI and see the content of the son. You can put sensors on the wires. You can single-step through the code. This is explained in the help of LabVIEW under Fundamantals-> running and debugging screw-> Concepts-> Debugging Techniques.

  In what the question implied in the title of your message, don't you can directly convert LabVIEW C code in the development environment. Yes, there are tools to convert LabVIEW in C, but which is intended for microprocessors.

• Client server of executable activex LabVIEW project with excel vba

  Hi all

  I submitted a ticket to support nor on this problem, but my deadline for this project is very close, so I would like to ask the community to see if someone has encountered this problem before (I hope it's ok that I'm doing this!). I did a fair amount of forum-scouring, and I didn't know this even discussed problem.

  I built a labView project which is essentially in the material data and
  preforms various visualizations and transformations on the data. A bit of the
  Screws in this project are available by VBA Excel as a Server ActiveX with LabView and
  Excel as the customer - and it works! I recently discovered I would need to do a
  executable version of my project, so I'm now trying to figure out how to do the same thing
  with my executable file as the server instead of LabView. Here's a simplified version are
  My VBA code:

  Void Button1_Click()
  Dim lvapp As MyServer.Application
  Dim vi MyServer.VirtualInstrument

  Set lvapp = CreateObject ("MyServer.Application")
      
  VI the value is lvapp. GetVIReference ("Main.vi", "", True)
      
  Sheet1.cells (1, 1) = vi. GetControlValue ("Path")
      
  lvapp. Quit smoking
  End Sub

  I replaced LabView here with the name of my server. The code
  failure of the CreateObject method with the following error:

  Run-time error '13':
  Type mismatch

  Things, I'm pretty sure I'm doing it correctly:
  -L'application is configured as an ActiveX server in the build options
  -J' ran the VI once and close/re-open it just after each build before trying the
  worksheet
  -In excel, VBA method is configured to reference the type library of the server.
  -J' have LabView itself closed when I run the .exe

  Thank you

  Alex

  My versions and such:
  Software of NEITHER: LabVIEW version 2012
  OS: Windows 7

  It's interesting - I'll have to look into the issue. In the meantime, I found a solution.

  It's quite mysterious, but it seems that all I had to do was make sure you only the type library of the server executable has been referenced in VBA (no LabView or OLE type library) and declare the variable app as object, rather than MyServerName.Application. Honestly, I have no idea why this works, but it does. Also, I learned that you need to use the executable file paths, which are a little different than the paths of project files.

  Thank you

  Alex

• Error adding programmatically to item to LabVIEW project

  I try to add a VI programmatically to a LabVIEW project using ActiveX nodes property/invoke:

  

  I get an error message (not as an ordinary LabVIEW error) when the name of the VI contains an underscore (who do a lot of my screws...):

  -When I try to add item.vi, everything's all right

  -When I try to add item_.vi, the error dialog is displayed.

  

  See the attachment for a sample application (LabVIEW 2010) showing the problem.

  Anyone have an idea how I can avoid this problem without having to rename all my screws?

  Hello dlanger

  you want to add a file please try this

  

  Adding items is used to add a folder to a project.

  Pleas let me know if it works.

• Custom LabVIEW projects

  I'm trying to create a new template to be used with LabVIEW 2013 Create Project wizard. I followed the tutorial "using examples and custom models of projects to develop LabVIEW projects" but always seem to have questions.

  I'm sure it's something really simple that I'm doing wrong, but can't seem to find the problem.

  I placed the template project in the xml code in metadata/ProjectsTemplates-LabVIEW and LabVIEW/ProjectTemplates data sources data.

  When I create a new project using the wizard, the project is created and works perfectly the first time.

  Then when I open it again, there's a load of conflicts that exist all of a sudden where some of the vi are linked to the model project.

  I can go and solve all conflicts and the project works, but there must be something I am doing wrong.

  I'll be grateful for any help getting this sort. I have attached the conflicts and my xml file (I changed the extension of the xml file to attach it).

  Thank you

  Greg

  Hi Larry,

  Thanks for the help.

  I had a look at my model and noticed that I had records value auto fill. I who took off in the model, and it seems to work now.

  Greg

• Open a reference to a labview project

  I am trying to automate a database containing information on all of our bunch of labview code ancient user. I need to determine what version of labview has been used, then collect information about the screws that are part of this. I don't find a way to open a reference to a project?

  I had almost closed the window when I happened to watch again invoke the mode that made me the 'VI' Version in VI files. And it was there, under the path of the project. So simple. I must owe marewa more. Have a nice day together.

• AutoStart VeriStand using LabView project

  Hi all
  I want to manage through selection LabView and deployment of projects on my PXI system.

  In order to know which project is running that only, I founded the solution to create an ad-hoc ALIAS that appears at the top of the list. Is there anyone who knows a smarter way?
  Attached is my example .VI
  Thank you very much for your answers

  You can watch the NI VeriStand - Get function System State.vi located in the NIVS palette. Notably, she returns the path to the definition file deployed where he is already running a (and you can use Connect to System.vi to run a definition instead of a project file). It is perhaps more convenient than your alias workaround solution!

• LabVIEW FPGA, 2015 compilation error

  I've recently switched to LabVIEW 2015 and I'm working on OR myRIO. So also installed myRIO 2015 bundled software. The problem I have is that the compilation of fpga fails within 10 seconds.

  

  and the target Xilinx journal report is empty

  

  The first time when I tried to compile on 2015 version, it failed and the message box that failed came alongwith the avast antivirus warning for malicious activity. I reported it as wrong and now I tried several times with avast shield disabled control, but the results are the same. While the version of labVIEW 2014 works very well.

  Now, I'm sure that there is something wrong with the installation of Vivado because this dll is part of it. The dll must be default in the2014_4\lib\win32.o directory C:\NIFPGA\programs\Vivado if you are using an operating system for 32-bit AND also in C:\NIFPGA\programs\Vivado2014_4\lib\win64.o If you use a 64-bit operating system. If the dll is not here, it is probably that the anti virus (I've never seen what happens to Xilinx but I have for other stuff).

  I'm emphasizing the 2014_4 because LabVIEW 2015 uses Vivado 2014_4 while 2014 LabVIEW uses Vivado 2013_4. Since you have also installed LabVIEW 2014, you must have 2013_4 as well and if it works, you will find the dll I just wanted you make sure you check the correct directory for the Vivado 2014_4.

  Download and install (reinstall or repair if already installed) 2015 LabVIEW FPGA Module Xilinx tools Vivado 2014.4. You can also use the DVD Setup if you have. It would be a good idea to do the installation with the disabled and even anti-virus try the first compilation the same. Try and let me know if the problem persists.

  Kind regards

• How to convert labview projects in the class diagram

  Hello

  I don't know if this option exsit in labview, but if she does will really help.

  How can I convert a labview in class diagram project?

  Hello

  Your windows to the Project Explorer, select the view menu and go to the "hierarchy of LabVIEW classes. This will then show you a diagram of your classes and their dependencies.

  Kind regards

• Which supplier Source control would you recommend for a single developer on a labVIEW project moderately important

  I have not used a front Source control provider.  My hope is that I don't have to deal with a large learning curve in using the basic features of a source control provider.

  Also curious is the most popular provider used by LabVIEW developers.

  Thank you.

  If you are getting started with Subversion (Tortoise SVN is the 'client' to a Subversion server), you have the choice between three options:

  1. Use a server Subversion maintained by your company or your University.  (I, fortunately, put at my disposal one).
  2. Use a commercial Subversion server.
  3. 'Rolling' (which means that the other host a server yourself, on your PC or on another PC, or simply use a 'local' repository).

  I listed them in the following order (according to me) that it is "desirable".  I, myself, would be enough worked to avoid Option 3, because it puts all the "eggs in one basket', in other words, you must assume the responsibility of not only keep your code Committed/updated the repository, but you must keep secure, backed up repository, and 'remote' (if your house burns down and the external unit containing the repository also goes up in flames you lost everything).

  I recently started a collaboration with a colleague in the Canada.  Because of institutional policies, I couldn't access our server local to Subversion, but found that assembled (www.assembla.com) offered a Subversion server access at a reasonable cost.

  Once you have identified a server, get your created repository and your project saved in the repository is not too difficult.  A practice I found works well is to organize the filing of LabVIEW, one project per repository projects, with the name of deposit is the name of the project.  I have adopted the model of trunk/branches/tags subfolder for the repository (i.e. the filing "Of Bob Project" will have a trunk, a branches and a subfolder of tags), with most of the activity taking place in the trunk.  I try to use the branches almost never, but that's another story.

  There are a number of tools to put "hooks" in Subversion in LabVIEW.  My personal preference is to do all my work of Subversion at the level of the Explorer of Windows files, validation and updating of entire projects to the end and beginning of work sessions (commit to the end, updated at the beginning).

  Bob Schor