Similar Questions

• How to upgrade the AIR included in Flash Builder SDK?

  Thus, Flash Builder SDK comes with a version of the AIR, that it uses when you compress a mobile app for iOS (Android mobile applications are managed with the AIR which is downloaded on the market)...  On my Windows machine, this copy "integrated" air is located in "C:\Program Files (x 86) \Adobe\Adobe Flash Builder 4.6\sdks\4.6.0\runtimes\ ' if I am not mistaken.

  I am sure that it will not automatically refresh itself - and I am equally sure that it's a fairly old air version, because it is the one that came with the 4.6 SDK that was released 8 months ago...

  So, how to upgrade this version of AIR that is built into the software Flash Builder SDK?

  Thank you

  Laurence MacNeill

  Mableton, Georgia, USA.

  Oops - nevermind...  Didn't know that there was a distinct AIR SDK that you could download - I thought that it was integrated into the Flex SDK kit, and since it was not a new Flex SDK from 4.6, I thought I should enter somehow parts and parts of AIR to update manually...

  But grabbing the AIR SDK to http://www.adobe.com/devnet/air/air-sdk-download.html went around...  Just that unzipped to the folder sdks\4.6.0 and was made...  Sweet...

  L.

• How to include a .wav file with vi the use of the application builder?

  Hello

  I am developing an application that uses a .wav file. I want to compress this file along with the vi in an executable so that the end user has a single file to run it.  Is it possible to add the .wav file to the executable using Application Builder? Moreover, to do this, can we configure the path to the .wav file in vi to always search for the file in the installation folder (for example: C:\Program Files\E2C\MSK or according to the user installs the executable folder in)?

  Thank you

  Anvy

  Anvy,

  It is not possible to compile a wav file in an executable file using LabVIEW. You can include the wav file in the project and include it in "still included" in your build script that will copy the file in the folder wav data from your executable file. So it is quite easy to distribute the wav with your exe file, even if the wav is not in the exe file.

  hope this helps,

  Norbert

• Measurment Studio 2015 Builder installer not conditioning not DLL Analysis.Professional

  Hello

  My application uses the package MS Anaylsis I want is not included in the Installer Setup Builder installer. I checked the "OR Measurement Studio Anaylysis .NET language runtime 2015 for .NET 4.5" in the Section of the driver NOR.

  After the execution of the installation on a machine of own generation Win8-64 my application generates a "could not find error Assembly" to "NationalInstruments.Anaylsis.Professional, 13.0.45.242 Version.

  A careful review of all available libraries does not suggest there is a more appropriate library to include in the build. My installation Builder is for a mixed environment, but my request is built as x 64.

  Can anyone suggest a solution?

  Thank you, Frank.

  Hi, Frank

  On your deployed machine, can you check the following directory and take a screenshot?

  C:\Windows\Microsoft.NET\assembly\GAC_MSIL\NationalInstruments.Analysis.Professional

  It is possible that this happens because your application was built against the 13.0.45.242 version of NationalInstruments.Analysis.Professional, but the version installs the 15.0.45.49153 OR Measurement Studio analysis .NET Language Runtime install. If this is the case, you can do two things:

  • (Recommended) Rebuild your application against the Measurement Studio .NET assemblies 2015 versions before you redeploy using the 2015 runtime installation programs.
  
  
  • Create an application configuration file that redirects 13.0.45.xxxx to 15.0.45.49153 NationalInstruments.Analysis.Professional.

• How to include libraries in an application properly

  Hello

  I'm working on a project that uses an external device.

  I installed the software for this device that includes drivers and libraries (.dll files) for use with LabView.

  To connect with the device, I use the block 'create an ActiveX object '.

  I like the Active-X entry, create a new entry and choose the right class in the drop-down list.

  This adds not all the DLLs for the project dependencies.

  LabView seems to be assuming that the necessary files are there.

  I want to install this application on another computer that does not have necessarilay the software to install the unit.

  My application fails. There is no error messages of any missing library either.

  I have to add the necessary libraries manually.

  How should I do this?

  (1) I might add directly the library files to the project.

  (2) I might add the library to my file Installer files, so that they are properly installed with my request.

  I don't know how to do this.

  How to tell the installer to install the files in the library?

  (* what I mean with that is to place them in the appropriate folder. Of course, the application folder is also searched dll when running, but this means that each application has its own dll, which seems to be the wrong approach)

  (3) I might add the file redistributable .exe for setup of my application as an installer.

  I don't know how do either.

  I will add the .exe for the project file, copy it to a place (which one?)  during the installation, and then run this file after completing the installation program?

  Or do I have to add this installation program to the list of "additional installers? It seems we can add only installers of NOR. How can I add my?

  Or y at - it another way, I have to do this?

  Thank you for your help.

  If it's just a dll - you can add it to the project with "always include" in the build specification.

  If it's a dll with dependencies / drivers etc, then it would be best to run their installer to ensure that everything is installed/registered properly as directed by their redistributable.

  You can specify either the user to install the software as a sine qua non, display an error if it is not installed when you run the software and provide instructions on what to do (providing your code at least runs without him).

  In the specification to build, you can specify an executable file to be run after Setup has completed, so you may want to include the redistributable in your Installer and set it.

• Error source distribution building

  I get an error when building saying source distribution:

  «LabVIEW can not find a file that is a dependency of a startup, exported or always included VI.»

  File not found: the file "C:\Program Files (x 86) \National 2011\vi.lib\utf\common\conversion\utf_string_to_tag.vi" must have the qualified name of "NI_UnitTestFramework.lvlib:utf_string_to_tag.vi", but it has the qualified name of "utf_string_to_tag.vi".

  The missing file can be referenced by one of the libraries included in the compilation or the file - OpenData.vi. To resolve this problem:

  -Open all the startups, exported or always included live, recompile them (CTRL-SHIFT click the Run arrow) and keep them to update their dependencies.
  -Open libraries included in the building and check the existence and the location of the referenced files. Also, try to build with the option of additional exclusion, 'Delete unused library of the project members', verified. »

  Any ideas why this happens?

  I don't know what was wrong but I restarted Labview and it worked.

• Submit to the queue build - DPS App Builder v27

  I am wanting to update our current application to v27. I downloaded the new tools, including the new Builder App DPS to our DPS. (run CS6 - Pro account)

  I went through the steps of the 'edition' our existing application in App Builder and now met the window "pop-up window will disappear once completed. This process never ends. I waited over 45 minutes for the construction at present and the pop-up window to disappear. No luck. I leave App Builder to stop force.

  I have deleated App Builder and re-uploaded and have gone through the same process and always get the window closing ever 'submit to the build queue'.

  If I raise App Builder, I see in the column Details App that our application has been changed through the 'last modified date', but can I trust that he has changed that I can never get the button 'Finish' using App Builder.

  Thanks in advance.

  Tom

  Hi all

  A fix for App Builder is now in place, containing the fix for this problem.

  Here is the download URL: http://download.adobe.com/pub/adobe/digitalpublishingsuite/mac/cs/DPSAppBuilder-2.7.1.11.8 5393.dmg

• NullPointerExceptions endless in Flash Builder 4.5

  I have been using Flash Builder 4.5 with the kit Flex 3 SDK. 5 b on Mac OS X 10.8.2 for a few months. It was not an experience perfect - the software has a few bugs, but in general he worked until recently.

  Our application includes two Flash Builder 'projects', which refers to the other. Whenever clone us the repository, it is necessary to update the file .project of the primary project to include the new path of the secondary project.

  The last thing I did before all broken did was move the folder containing the project to a new location. As expected, when I open Flash Builder, it complained that it couldn't find my project files, and they were all marked as inaccessible in the "Package Explorer" view. I did not remove inaccessible project in my workspace, but I tried to re - import the main project of his new location. It was the first time I saw a dialog box that has haunted me since:

  

  The view of 'Problems' told me to return in the errorlog...

  

  .. but the error log was empty!

  The "Package Explorer" view has not changed (the new draft has not been listed) so I decided to just try the import again. When I chose the directory of the project, Flash Builder said that I couldn't import it because the project was already in the workspace. "But the Explorer Package says it's not... maybe he'll try again if I restart Flash Builder" I thought. I have bad thought. When I rebooted, it is what I saw:

  

  java.lang.NullPointerException
      at com.adobe.flexbuilder.util.PathUtils.resolveLocaleInSourcePath(PathUtils.java:297)
      at com.adobe.flexbuilder.project.actionscript.internal.ActionScriptProject.getProjectPath(ActionScriptProject.java:713)
      at com.adobe.flexbuilder.project.actionscript.internal.ActionScriptProject.getSourceContainers(ActionScriptProject.java:681)
      at com.adobe.flexbuilder.as.editor.ui.packageexplorer.content.FlexPackageExplorerContentManager.getSourceRoot(FlexPackageExplorerContentManager.java:644)
      at com.adobe.flexbuilder.as.editor.ui.packageexplorer.FlexPackageExplorerContentProvider.getWorkspaceRootChildren(FlexPackageExplorerContentProvider.java:152)
      at com.adobe.flexbuilder.as.editor.ui.packageexplorer.FlexPackageExplorerContentProvider.getChildren(FlexPackageExplorerContentProvider.java:80)
      at com.adobe.flexbuilder.as.editor.ui.packageexplorer.FlexPackageExplorerContentProvider.inputChanged(FlexPackageExplorerContentProvider.java:449)
      [...]

  He could not yet list the projects so that I could remove the one that was the origin of the problem. A similar message was displayed in the mode "Editor." Deleting all files from the project did not help either. I was unable to set the workspace, and the only way I could continue to use Flash Builder has been creating a new workspace.

  Since then, I tried a lot of different things:

  • Reinstalled Flash Builder 4.5.
  • Reinstalled Flex SDK 3. 5b.
  • Excerpt from a six - month old version of the project.
  • Flash Builder 4.6 upgrade.
  • Created a new user profile on my computer.
  • Tried to remove some trace could have broken things:
    1. Instruments to monitor the process of Flash Builder affects all files.
    2. Uninstalled Flash Builder.
    3. Used find to locate include files builder or eclipse in their name.
    4. Delete all the files found in (1) or (3) who seemed possibly related to Flash Builder.
    5. Reinstalled Flash Builder.
  • Installed Flash Builder 4.5 on another Mac running Mac OS X 10.6.8.
  • Installed Flash Builder 4.5 in a Windows 7 VM.

  None has made any difference. It seems impossible.

  Other members of my team have worked on this project for a few years without running into this particular issue, yet now project versions from before that I started appear to be broken, and even with the help of new installations of Flash Builder on entirely different systems also violates.

  I don't know what is happening. It seems I must have done something else and forgot about it, because the current situation makes no sense. Someone has encountered this problem before? Do you have an idea what could be causing it, or that I could do about it?

  We finally found a solution. It's rather disappointing.

  Ignore any errors.

  Import your project files and activate the correct SDK version in the order you want. If you find yourself with a messed up view "Project Explorer", with just the close and reopen it or restart Flash Builder.

  Once the display of "Project Explorer" is available, select your primary project and run it. It should work!

• Simulation of antenna MIMO in VSS

  Hello

  I was wondering if there is no provision to simulate a scenario of MIMO antenna space diversity in VSS? Or any form of smart antennas, in fact.

  Thank you!

  VSS includes all the building blocks for the implementation of MIMO TX and RX features. MIMO is actually implemented in the standard libraries that use this method, such as LTE.  There is also an example that comes with the output, MIMO_Channel.emp, which shows how multipath channels may be created to operate in environments of MIMO.

  I hope this helps.

• Projects

  Are there links that can provide examples and documentation on the projects of LV?  For example what the 'ÉLÉMENTS' and 'LEADER' relate to?  I'm use to the old way of creating a Labview VI.  I've never really interested in w put the files in any sort of project area.  Is there a methodical way to do?  How do you use projects?  When I use it?  What is the Dependencies tab for?  the Build Spec tab for?

  Thank you!!

  Have you tried using LabVIEW? No, really, you have? There is a whole section on the projects, including the what build specs are for. Alternatively, have you tried the site OR research? This would have led you to this:

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

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

• Problems with typedef uInt32 and NI Vision

  Hello

  I'm having a small problem my request against the headers provided by NI Vision acquisition 15.0 and CVI 2012SP1 of construction.  The problem seems to be contradictory typedefs in the files of headers associated with the types of 'SESSION_ID' and 'uInt32 '.  In NIIMAQdx.h, it is the following:

  #ifndef _NI_uInt32_DEFINED_
  #define _NI_uInt32_DEFINED_
  #if defined (_MSC_VER)
  typedef unsigned long uInt32;
  #else
  typedef unsigned int uInt32;
  #endif
  #endif

  Now, _MSC_VER is not defined, so we get defined as an unsigned int uInt32.  In niimaq.h there is:

  #ifndef _NI_uInt32_DEFINED_
  #define _NI_uInt32_DEFINED_
  #if defined (_MSC_VER)
  typedef unsigned long uInt32;
  #elif __GNUC__
  #if __x86_64__
  typedef unsigned int uInt32;
  #else
  typedef unsigned long uInt32;
  #endif
  #endif
  #endif

  Which neither _MSC_VER or __GNUC__ being defined, does nothing except set _NI_uInt32_DEFINED_ who prevernts to be set by another heading.  niimaq.h also has this in it:

  typedef uInt32 id_interface;
  typedef uInt32 SESSION_ID;
  typedef uInt32 EVENT_ID.
  typedef uInt32 PULSE_ID;
  typedef uInt32 BUFLIST_ID;
  typedef Int32 IMG_ERR;
  typedef uInt16 IMG_SYNC;
  typedef uInt32 GUIHNDL;

  This means that, by itself, a module which includes niimaq.h build because uInt32 never gets defined.  You can include NIIMAQdx.h in front of her then she cand defrine uInt32 (as an unsigned int), that works, except that nivision.h has this line int he:

  typedef unsigned long SESSION_ID;

  Yet once they do compile due to the conflicting types (unsigned int versus long unsigned).  It seems that there is no way to include niimaq.h, nivision.h and NIIMAQdx.h in the same .c file, regardless of the order, without certain types of conflicts or unknown.  Comparison of return to an older version (3.9.1), I see in NIMAQdx.h,

  #ifndef _NI_uInt32_DEFINED_
  #define _NI_uInt32_DEFINED_
  typedef unsigned long uInt32;
  #endif

  Which is nice and simple.  niimaq.h also has the same code in it too much OR-IMAQ 4.6.1.  Does this mean that I can "fix" it by defining _MSC_VER, indeed put

  #define _MSC_VER 1300

  At the top of my .c file gets in effect of things to build, but I'm wary to do this because I know there are other things that seem out of it.

  Any ideas or is the solution to restore an older version of the Acquisition of the Vision?  Thank you.

  Hi Tanner!, thanks for the reply.  I use the Debug, not 32-bit mode.  The code example you provided does not build in my configuration.  The problem is this code in niimaq.h

  typedef uInt32 id_interface;
  typedef uInt32 SESSION_ID;
  typedef uInt32 EVENT_ID.
  typedef uInt32 PULSE_ID;
  typedef uInt32 BUFLIST_ID;
  typedef Int32 IMG_ERR;
  typedef uInt16 IMG_SYNC;
  typedef uInt32 GUIHNDL;

  And the reason is that an Int32 and uInt32 are not defined (although uInt16 is defined).  On another PC with NI Vision 2009 installed it relies very well, but it does not work on this PC with IMAQ 15.0.

  Play with it, I think the problem is that CVI 2012 SP1 isn't definition _MSC_VER or __GNUC__, whereas CVI 2013SP1 __GNUC__ defined as 4 (and indefinite _MSC_VER leaves).  As __GNUC__ is defined, then in niimaq.h, uInt32 is defined as unsigned long (for 32 bit), and all is happy with CVI 2013, so the problem seems to be related to the combination of the ICB 2012 and versions more recent the IMAQ.

• How to use a static reference to maintain a VI in memory, but then call it in parallel?

  Hi all

  I have a MainVI and I want to call him a Subvi in parallel so that I can have both windows open and sensitive at the same time.  The Subvi can be closed and then reopened any number of times, but only one in existence at the same time.  I know how to do it using the reference VI opened, offering a path relative to my Subvi, check to see if its already running and if so bring window to front (using front panel: open with entries True/Standard method) and if not run it using the Invoke method: Run (and eventually open its façade by program).  This method worked very well.

  Now, I've added functional global variables in my Subvi, and I want to keep in memory inbetween opening Subvi window.  I can do this by placing a copy of the functional overall in my MainVI, even if I do not here for nothing.  It works very well.

  By chance, I came across a reference to a static reference of VI, which resembled a great improvement in my method, for the following reasons:

  1) Subvi keeps in memory all the time, eliminating the need to put the functional overall in MainVI when it is not used it.

  (2) tells the LabVIEW to include the Subvi when I build my executable, rather than me having to specifically mark as always include in the build specification.

  (3) eliminates the need to continue the path and the name of Subvi updated in a constant string in my code, in order to use the open VI reference.

  However, in trying to implement this solution, I ran into the problem that once you put a reference of VI in strictly typed static (strict typing is necessary to keep in memory) on the block diagram, that VI is reserved for execution.  This means that I can't run it using the Invoke method: Run.  I did not just put it on the diagram directly as a Subvi because I need it to run in parallel to the MainVI.  I searched through these forums extensively, and although there are several references to a static reference of VI, none of them say explicitly how to actually run this 'thing'!  : PEI

  I greatly appreciate any insight into my problem.  If I have to go back to the old way it works perfectly, but I really like the apparent elegance of this solution.  I hope that it will be technically possible, and I'm not bad understand something.

  Thank you for your help,

  -Joe

  
  

• Executable cannot find the custom error code file

  I'm building a LabVIEW 2013 application on a Windows 7 computer and deploying it to a Windows XP computer. My application has a custom error code file, stored in -- errors.txt, but my executable on the Windows XP machine can't find the custom error file and returns only the string of appeal for all errors that occur.

  When you use is not an installer, I tried to copy the error code at all locations listed here: http://digital.ni.com/public.nsf/allkb/6077DBEDA4F9FEE3862571F600449501 but the application still does not load the custom errors. I have the box checked to "Error Codes customized Include" in the construction specifications.

  When an executable of construction and the development of Windows 7 to XP, where do I put the custom error code file? It is found in Program Files (x 86), but find not because it's XP?

  It's been a few months that I posted this question and I do not know if someone cares about this track, but the solution I found was to put the custom in error code file \National Instruments\Shared\Errors\English\

  There are other places that the runtime will look for the custom error codes (I tried all the ones listed above), if the same error codes exist in 2 places the error popup will appear two error messages. Error default 1, it looks like:

  LabVIEW: An input parameter is not valid. For example if the input is a path, the path can contain a character not allowed by the operating system such as? or @.
  =========================
  NOR-488: Command requires GPIB controller charge controller.

  So if you have a custom error code file and it is available in 2 places that LabVIEW RTE check error codes, you will get the same message before and after the =.

  List the error as "still included" file when building the executable or by checking the box to include files in error did not tour, obviously. Unless you create a Setup program to distribute the application, the error code file must be moved manually. Shared\Errors file works best for me because it's a place that makes sense.

  Also, don't worry - it doesn't me taken 5 months to understand this point, I do not update all my loyal followers (ha) with a solution.

• Installer/exe

  Hello. I did the exe and Setup to be able to use my program on another computer where LabVIEW is not installed. Program is continuous provided control Agilent 5771 has who needs additional drivers to communicate with the PC, but when I have installed LabVIEW I do have a folder where I can install the driver. Y at - it no installer I need to include when I build Setup for my application?

  Thanks much for the advice.

  You use the name VISA to the instrument of the address? Then you need visa run-time.

  First you must make sure that the instrument of windows driver is installed (the device is correctly listed in the Device Manager). It can be run-time VISA, pilots of the virtual com port, instrument, etc. They know nothing of LabVIEW and don't require his file.

  LabVIEW 'pilot' is a wrapper that calls finally driver dll. When you build your application, they are included in the exe, no need to install them separately. Make sure you do not vi.lib exclude or exe files instr.lib build.

  Sometimes, there are intermediate between the driver and LabVIEW VIs DLLS, then you need to include it in the support of the exe folder. If you don't include a required dll, when you start your application, it will say he hasn't.