Distribution source + Exe NIVDM.lvlib

Similar Questions

• Save the distribution source for the previous version

  Hello

  I am trying to use the tool run a Labview VI in VBAI. I use LV2013 SP1 and VBAI 2013. The step run a VI Labview gives me an error saying "this step supports LV2012 or earlier. When I record to LV12, this time an error comes up saying "the VI has not been compiled for the specified remote target or it is not registered with LV12." After I read the forums and help documents, I see that this problem can be solved with the recording of the VI for distribution (LLB).

  But when I open the project, it becomes LV2013 and LLB built as LV2013. So I go back to the first step, saying: "this step supports LV2012.."

  How can I build a source like LV12 distribution using LV13? I couldn't find a solution.

  You can either download a 2012 version (ask your local sales engineer because it's an older version), or

  "Save your VI as" for 2012 and post the zip files exported to the Commission on conversion. Can someone respond and wrap your files in 2012 VI + llb ^^

  - http://forums.ni.com/t5/Version-Conversion/bd-p/VersionConversion

  -Eric

• A distribution source created in 32-bit LabView 2009, explains that the screws are not executable when opened in LabView 2009 64-bit. How do the main screw?

  A source distribution was made for a VI using LabView 2009 32 bit. The distribution has been verified to work on another machine which ran 32-bit LabView 2009. However, when opened on a 64-bit LabView 2009, the VI was broken as indicated by the error message attached. How can I make the executable VI?

  The VI used the noise and vibrations and HSDL screw that I suspect don't are not supported in 64-bit.

• Distribution of the source with dll error

  I am trying to build a distribution source, using LabVIEW 8.6.1.  The code calls a dll and why the dll is listed as dependencies.  When I Isaiah to compile a source distribution I get this error:

  

  Has anyone seen this before, and if yes, what is the workaround?  Thank you very much for the help.

  Good morning jmcbee,

  As says the first 'reason', an input parameter can be invalid.  Although "the Distribution Source provider creates a copy of the project (including dependencies) for easy distribution files to another machine," your .dll is one path other than that of the project and this is the error that is returned, its path can be the invalid entry to blame. (KB: what is the feature of specification of Application Builder Build?)

  Try to place a copy of this DLL in the same folder as your project and reconfigure your project and call library function nodes to get the .dll file in the new location instead of the original location.

  Another thing you can try is to remove all spaces in the name of the specification to build and ensure that no spaces at the end of the name.  Then rebuild the source distribution.

  The following links can provide some basic information:

  What is the feature of Application Builder Build specification?

  http://digital.NI.com/public.nsf/allkb/41561F98D96235FC8625708F00552ADF?OpenDocument

  Error 1 or 6 is produced during the e/s of file - input parameter is incorrect

  http://digital.NI.com/public.nsf/allkb/BB06ABD0261A9F2B86256F190049A620?OpenDocument

  Why my executable does not work when you use the constant path of the current VI?

  http://digital.NI.com/public.nsf/allkb/FD7DE8BC8FFC256C862565F4006BE363?OpenDocument

• Subvis call go dynamically within an exe file (avoiding the error 1003)

  Hello

  I use an architecture where the main program (compiled into an exe) can be supplied with a user-'plugins', which are collections of screw types inside a folder named especially compared to the exe. They can be called in the exe via 'open reference vi' provided by the corresponding strict vi types and corresponding relative paths.

  I want to avoid having to include one of the plugins in some way in the application builder, because users must be able to create own plugins that the request is totally ignore during the generation.

  In principle, this approach works rather well, since these plugins are not extremely complex, but sometimes, I get an error 1003 when loading a plugin.

  I have read many old posts on this error in this particular situation, mainly using versions of LV 7 or 8 (I use 2012). It was suggested to build a source distribution for each plugin, including everything that is used from vi.lib, instr.lib and user.lib. Indeed, it helped in my particular case - however, it bloats the plugin 'distribution' (which consists originally only a couple of the screws of the user) extremely and complicates the development user side.

  Now some good plugins run from in the exe without having to build a distribution source for them (they still use many vi.lib live) while others don't, and I have no idea why...

  These plugins are wrappers for hardware drivers that allow to control any hardware instrument within the main application via a certain API. So, in a particular case, a plugin that produces the error 1003 uses VISA series features (everything inside... \vi.lib\Instr\_visa.llb) and one without error doesn't (yet he uses several features of... \vi.lib\Utility\...).

  I can solve VISA problems in a simple way by including (only) the VISA-vis opportunity (and typedefs) inside the plugin folder and explicitly link to them (i.e. replace the VISA-vis of vi.lib with those copied to the folder of the plugin - I guess that's also what the source distribution).

  However, I'm confused why certain plugins with work of related vi.lib while others screws produce an error 1003 unless these special screws are explicitly distributed and connected with them...

  Oh and just for completeness: all plugins are working fine if the callee in the development system, the problem occurs only if called from an exe file.

  Novgorod wrote:

  However, I'm confused why certain plugins with work of related vi.lib while others screws produce an error 1003 unless these special screws are explicitly distributed and connected with them...

  Oh and just for completeness: all plugins are working fine if the callee in the development system, the problem occurs only if called from an exe file.

  Do plug-ins that work depend on the screw in vi.lib who are already part of your executable file because the main program uses these same screws?

  All the screws that your plugin needs must be available, if applicable can mean to be already loaded into memory (for the main of the application or another plugin), or can be found on the disk and load.  An executable includes all the screws of vi.lib - it includes only those he uses (and the screws that are marked always 'include' in the build specification).  I suspect that the plugins that work only dependent vi.lib screws which are also used by the main executable file.

• How can I extract the msi from exe to install drive?

  Usually, when I want to extract the msi file from the distribution of exe (for Group Policy) installation drive, I download from get.adobe.com/reader/enterprise and decompress the exe file using 7zip.   Then I integrate the msp inside file and I'm pretty much good to go.

  Now, when I try to extract the msi file, I get a directory full of stuff, but no msi at all.  I tried the installer and watch in C:\users\username\AppData (it works for Java), but it wasn't there.

  No idea what I am doing wrong? Or y at - it a new way to extract the msi file that I missed?

  Thank you!

  Bryan

  Hi bryan10983,

  You can visit this link to get the answer to your query: http://blogs.adobe.com/dmcmahon/2010/06/16/how-to-extract-an-msi-file-from-the-exe-for-ado be-player /

  Kind regards

  Ajlan Huda.

• build the specification

  Hi all

  I'm pretty new to Labview and are now using LV2009 and have trouble with "build specification".

  are not supposed to be 5 features, including, Installer, EXE, DLL or the source distribution and the zip file?

  Why only can I find 2, namely the Distribution Source and (RESTful) Web Service it?

  THX

  You have the application Builder installed?

  See here

• Missing vi.lib in 2012 LabVIEW Run-Time files

  Hello

  I have a problem running under RT of VI in LabVIEW 2012.

  Our system consists of several independent modules that are open and run from a VI Manager. VI paths to modules are read in a VI Manager .ini file.

  We create a single executable file (RT Launcher) who takes the path of the VI Manager as an argument (attachment: RT Launcher.png).

  The RT Launcher is placed in the... 2012 as the LabVIEW.exe \National Instruments\LabVIEW dossier.

  The RT Launcher is called from the CLI.

  "C:\Program NIUninstaller Instruments\LabVIEW 2012\RT Launcher.exe" "C:\Workspace\Labview\Manager.vi."

  This will run the Manager.vi in the runtime environment and the Manager.vi will open the .ini file and run a Module VI.

  By calling the Launcher.exe RT from the same folder as the LabVIEW.exe, search paths should be the same.

  The system has worked well in LabVIEW 2010.

  The VI Manager opens with a broken arrow and the errors indicate that void vi.lib screws are missing (attachment: errors.png Manager VI)

  I know that there is code LV2010-> LV2011-> LV2012 compiled cache object and separate questions, but simply could not figure out how to get around this problem.

  Can someone explain the difference and how to solve the problem?

  Thank you

  Hi Morten,

  I just sent you an e-mail (before I saw your post) with some other information related to this.

  About the reproduction looks that you have included a palette in your source distribution file (mnu), that will not work (sorry for not seeing this before).

  Could you try to see if it was unintentionally included in your dependendies or whatever it is? The behavior of mnu files is also something that changed from 2010 to 2011, so if you run with the old project of 2010 there could be some bad dependencies. (We recommend always to create a new project when migrating a LabVIEW project to a newer version).

  There is a little more information about the error you see everything by creating the distribution source here:

  How can I include .mnu files in a built LLB?

  http://digital.NI.com/public.nsf/allkb/051F1533145089A1862578B80060D93B?OpenDocument

  Best regards

  Anders Rohde

  Technical sales engineer

  National Instruments Denmark

• Rich project shared with IO Library?

  I have an application that needs to share resources/instruments with TestStand steps.  Requirements require the application to communicate with these resources/instruments with or without leaving the engine of TestStand.

  I understand that the suggested approach is to put ONLY the instrumentation code in a test sequence.  However, what is the best approach if the application conditions dictate the resource or the instrument must be shared?

  • Project packed library can be shared with the operator interface?
  • Is a distribution source, the only option?

  Hey LVB,

  Thanks for the information. Based on what I think you are trying to you should be able to do what you are looking for. The reason that the manuals say to not use instrumentation with the interface code user is to preserve the modularity, it is not recommended that you add an instrumentation specific Interfacing to the OI of LabVIEW TestStand as this will make the instrument specific OI. And as long the .exe OI runs will run your instrumentation process, and until your operator selects actually trial USE or simple Pass (or whatever TestStand entry point you choose) the TestStand API will just await you. This example, I think that shows what you need to do the https://decibel.ni.com/content/docs/DOC-21047.

  I hope this helps.

• LabVIEW Application Builder

  I've successfully created an application and required to make corrections to the code and want to do an another EXE build - now I get the following error!

  What is the cause?

  NI_FileType.lvlib error, copy of files

  LabVIEW 2009

  Error copying the files.
  Source: C:\Program NIUninstaller Instruments\LabVIEW 2009\vi.lib\Utility\lvfile.llb\NI_FileType.lvlib
  Destination: C:\Projects\S\SuperiorWellServices\20090032\SourceCode\New Shell\NODE\propPORT_I\propPORT_Builds\propPORT_I_EXE\propPORT_I.exe\NI_FileType.lvlib

  Invoke the node in AB_Source_Library.lvclass:Copy_SourceItem.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

  Details:

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

  Error 8 is is produced in AB_Source_Library.lvclass:Copy_SourceItem.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: File permission error. You do not have the correct permissions for the file.
  =========================
  NOR-488: Error detected DMA hardware.

  I have this error before and see an article that talks about something similar:

  Why do I get 'Error 8 has occurred open the file' when writing to or reading from a file?

  Trying to build after the closure of all the files on your machine. I also recommend to restart the computer. It seems that there is an intermittent error that appears during the generation of application.

• The EVS LabVIEW runs automatically when you open a file, LLB

  How can I configure my build Distribution Source so that the LabVIEW shared Variable engine is loaded and all my shared variables are deployed?  I need to build my code in a LLB file, which, once opened, automatically launch the high level vi and deployed all shared variables.

  I can do this for code that is compiled into an EXE file, but I can't understand how do for code compiled in a LLB file.

  I'm using LabVIEW 2009.

  Also, how is it when I click on the listbox element "Shared Variable deployment" under my. Build settings EXE, run my software?  For some reason, the compiler to the LabVIEW run my software while it is built.  This only happens when my EXE uses the shared Variable engine.

  Thank you

  Richard

  I thought that the problem starts the first level VI, does not deploy, sorry.

  You can deploy the library using a node to invoke with the library "deploy" or 'deploy libraries' method in the application class. Simply give the path to the library then.

  

  Christian

• Device custom 3D-graphics

  Hello

  I tried to create a custom device allowing the display of data in 3D graphics. I created my device custom graph XY Add - found on the Web site OR in order to have the right model. But load in my workspace, error 1003 has occurred (see error.jpg).

  Can someone explain to me how do I solve this problem?

  Hello

  I assume you have copied only the model (Graph - Graph.vi 3D) display in folder view models?

  If so, the problem might be related to missing dependencies of your view model. I suggest that you create a distribution source of your view model and try again.

  We have a tutorial interesting on how to create objects of the custom for NI VeriStand workspace:

  http://zone.NI.com/DevZone/CDA/tut/p/ID/9989

  You can also view this custom, view model which is similar to yours with respect to dependencies:

  http://decibel.NI.com/content/docs/doc-5705

  Let me know if that helps!

  Thank you

  Tom

• Personalized services

  Hello

  I use a 2011SP1 time VeriStand real LabVIEW RT applications on a device PXI.

  I need to run a specialized home network service that needs to run as soon as the target is started and until its closure. It has no interaction with VeriStand.

  It of in LabVIEW code and undertakes with VeriStand at boot time.

  What is the way to do this?

  Best regards

  There is no way taken in charge to do this, but you can use an entry point of debugging we have for VeriStand start a top-level VI at the start of the VeriStand engine. It does not wait for the deployment and has no interaction with a deployed system definition file.

  To do this, create a top-level called NIVS Debug.vi VI and build a distribution source LLB with she named NIVS Debug.llb. Then place the LLB in the same directory as the file rtexe VeriStand. If this works, you should see "start NIVS Debug... ' displayed on the console when the engine starts first to the top. If something goes wrong, you should see an error message printed.

  This VI is started asynchronously.

  I hope this helps.

• Add screws to LLBs - is there an easy way?

  Hi all

  I have a question on the use of the LLB Manager to make a LLB file.  Currently, I have a bunch of screws in a LabVIEW project and want to add to a Bachelor's degree in LAW (or new).  The only way I found to do this is by entering each VI and performing a ' Save as ' and saving the VI in the LLB.  There is no simple way to drag / drop the screws into a LAW degree?  Or maybe even a recording/import batch in the LLB?

  Thank you!

  I think you can create a Distribution Source of your code and indicate it should go in a Bachelor's degree in LAW.  Alternatively, you can use the screws in vi.lib\utility\libraryn.llb to write a utility that would settle all your screws in a Bachelor's degree in LAW.

• How we prevent screw consisting of a large number of subvis

  Hi all

  I need your suggestions regarding the prevention of the labour dispute with two PC on same vi. I built a program and there a lot of subvis and I work with 2 PCs. When I detects an error on a Subvi or something else, that I have to change things subvis and releated on the same PC by transferring all subvis records and live by USB key. Sometimes, this causes an error. for example, I could delete some subvis unconsciously. I've read about labview project and libraries, but documents are not explanatory. I want to collect all my vis and subvis in a project or folder. but I don't really know how to do it. And also I want to change subvis or live in this folder, whenever I want. How can I handle this? Thanks in advance.

  Kind regards.

  Create a new empty project, save it neer your main VI then the main VI for the project. The project automatically finds all the dependencies of your main VI (subVIs, CTL, etc...), in the windows project, you have a tab "Files", from there, you have a tree that shows you where are all the dependencies of your project. This is really useful.

  If you go back to the tab 'Éléments' and create a new generation sepcification (right-click on the icon), and then choose "new > Distribution Source" you can set an "export" which will include all you the source code.

  Hope this helps