Create Labview application to call other installers

I am trying to create a labview application using LabView 7.0 so that it can call several other installation applications sequentially.

Hi jgv,
and where is your problem?
You can call other apps by using SystemExec...
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Similar Messages

Creating LabView application for VME-GPIB device

I am trying to learn how to create software for controlling GPIB devices attached to the VME-GPIB board. One application would be for a setup where Labview is the software used. Another is a real-time system developed with VxWorks.
It seems to me, that in order to be able to create such a LabView application I need detailed information on the VME-GPIB VME memory layout and definitions of all of its registers. Am I right assuming that? Suppose that I am right, where can I get such detail information on the VME properties of the VME-GPIB device?
I found such a document for the GPIB-1014 device, which seems to be a precursor to the VME-GPIB device.
Am I correct assuming that such manual would also be essential for writing VxWorks software as well?
Thanks in advance,
Zen

Zen,
I have received your support email regarding this issue and currently working on getting you the needed information. I will contact you when it is ready.

Adobe Application Manager and other Installers All Messed up

I have a Mac Pro running 10.5.8 and CS5 Design Premium. Today I noticed 3 new updates: Bridge 4.0.2, Camera Raw 6.1, and a Flash thing. I ran the update using Adobe Application Manager (AAM). It failed on all three. I tried every way I could find to re-install AAM including
1. Deleting the PDApp folder under OOBE
2. Running the installer from a terminal window in silent mode
3. Running the original installer
Running the original installer starts AAM, which then crashes, and when I relaunch it, it looks for updates and doesn't return to dealing with the full install.
So, I have no idea what to do. I cannot reinstall CS5 or uninstall it. I cannot update anything, even by hand.
I am a fairly sophisticated OS X person, so I am not doing something stupid like not being connected to the net. It's a permissions or ownship thing.
Any suggestions would help.

Your problem is similar to mine.AAM and Deavtive are two central actors in this isssus. OOdude is right on Deactive Question is YES/NO to AAM. Two options with some trial and error. Follow the below-but...
AAM Runs??
1) Deactivate. Uninstall. Run the clean-up script**. Reboot. Reinstall. If you product key works, you’re good. Live long and be creative.
AAM not Running? ‘
2) Backtrack on the link I left earlier. Look it over. If that helps, follow it. Try running the clean-up script. Should pull the bad installation. Reboot and Reinstall. If your product key works, you should be good.
No luck? The sticking point is the fact that you were not able to deactivate. Tech support calls time. No matter how painfull, Adobe’s product key use database has you in its grips.
3) Tell Support “reinstall due to software problems and product key not working.” Adobe will give you codes to release your product key. " You can’t out horsepower this problem.
** >The "Clean-up Script" appears drastic, but it only removes CS5 and "takes out the trash.". Cyber-house cleaning on steroids. Be mindful of instructions and follow to the letter. Reboot. Run CS5 install. Similar to a "clean install" of your OS, but CS5 is the "only-warez" affected.
Ahh...it will work again!! Good luck WileyC

Distributing an Application that calls Visual Studio built DLLs

I have a LabVIEW application that calls a Visual Studio 2005 built DLL, that then calls functions from another Visual Studio built DLL. When trying to distribute this application it will execute perfectly well on all machines with Visual Studio installed, but on any machine that doesn't have Visual Studio installed, despite installing the Visual Studio Redistributable Package on the machine, I get the error message on attempting to run the application:- "Missing External Function 4575Interface.dllname of function):C in (sub VI that uses function).vi" for the 10+ VIs that use functions called from that dll.
Any suggestions?

Hi,
You will need to manually add all of the DLLs you
are calling into your LabVIEW project. Check in the folder
"Dependencies" in your Project Explorer what external DLLs the VIs are
using, then drag and drop those DLLs into your project. LabVIEW will
not automatically include these external DLLs when you specify a build
specification unless you explicitly tell it to do so. When you
distribute the application using an executable, always explicitly
select those DLLs as "Always Included". Finally, register these DLLs on
the target machine by using Windows command: regsvr32.exe. I would recommend you to write a Windows batch file *.bat to ease the deployment process.
Another
point to note is, the DLLs you will find in the folder "Dependencies"
are the DLLs LabVIEW automatically recognized through what you are
calling in your program. However if any of these DLLs is linking some
other DLLs, LabVIEW will not be able to detect them on the build, so
you will need to add the DLLs into your project manually for
distribution.
Hope this helps,
Best regards,
Mark M.
Applications Engineer
National Instruments UK & Ireland

LabVIEW Application Developer (CLA) - Provide LabVIEW solution for SME & MNC - Singapore based

Hi ,
I have accumulated years of experience in creating LabVIEW application for SME & MNC.
In order to deliver quality solution to customer, please expect the following routine:
Requirement gathering on software application.
Translate business requirement into software specification, software model and architecture.
Application coding and regular review with client.
Continuously application improvement and maintenance based on user feedback.
Part of my experiences:
LabVIEW application development with rich-GUI features.
Process automation or data analysis through communication (Express Controller/Serial/USB/Bluetooth etc.) in between customized hardwares and LabVIEW application.
High pincount Digital data generation & acquisition.
Provide best-fit NI PXI hardwares (Digital/Analog/Serial IO/PMU etc) for customer's business requirement.
Visual Studio.NET programming, SQL, Scripting.
LabVIEW Real-time, LabVIEW FPGA
Please feel free to drop me an email at [email protected] for a non-obligatory discussion.
Thanks for reading.
Regards,
Drawsome

Please look into my profile at linked in https://in.linkedin.com/in/prashantpatel21 I m interested.
Regards,
PBP (CLAD)
Labview 6.1 - 2014
KUDOS ARE WELCOMED.
If your problem get solved then mark as solution.

I am using the NI application note "Calling IVI-COM drivers from LabVIEW" I created an Automation Open and an Invoke Node, after wiring

the 2, the AN asked to right click the Invoke Node(this is step9) and choose initialize. However there is no intialize option on the pop up menu. Anything am I doing wrong? I am using Labview6 and I did add the "enableCustomInterface=True" in the INI-fileThank you for your help.
T Tall

the 2, the AN asked to right click the Invoke Node(this is step9) and choose initialize. However there is no intialize option on the pop up menu. Anything am I doing wrong? I am using Labview6 and I did add the "enableCustomInterface=True" in the INI-fileT Tall,
What's the number of the application note "Calling IVI-COM drivers from LabVIEW"? I'm unable to find what you're looking at.
Thanks,
--Bankim

Can Any one tell me what is the step in calling a function from a *.lib file in Labview application

Hi, I am working on Labview 8.0.
I am trying to communicate to a thrid party HW using the driver file he has provided to me.
The drive file is a *.lib file.
I am unable to call the function from the lib file.
I could get only from a DLL.
Pls help .
Regards
-Patil

patil wrote:
When it is possible in Lab Windows, why calling a function from a static library is prohibited?
I was trying to use Function node, but found that it is only for functions from a DLL file.
Will CIN be useful.?
LabWindows is not the same as LabVIEW. LabVIEW cannot call .lib files. LIB files are intermediary products and you need to use a wrapper DLL that's compatible with the object format of the .lib file. It's as simple as that. LabWindows creates C application and from that perspective is no different than a regular C
compiler. That's why you can call .lib files because that's how .lib
files are used.
A CIN, as pointed out, is something completely different and will not help you.

What kind of function(s) (in dlls) have to be call by a Labview application to be able to manage the PC's power supply

Assume that a Labview application is running on a PC. The PC has a DC battery. When a "power off" is detected on the AC line, data should be saved, Labview application and Windows should be closed.
What kind of function(s) (of which dll) should be called by a Labview application to realize this data and system management in a safe manner ?

UPS (Uninterrupted Power Supply) systems can send messages to the PC through the serial port when the AC is lost and when battery is low. I'm not sure how this message is sent but I suspect they use Windows Messaging. If you could find this out, you could write your vi to constantly look for this message and shutdown when it sees the message.
- tbob
Inventor of the WORM Global

I created an application on a machine with Labview 6.01, can I run this application on another machine that has labview 5?

In the development center we use Labview 6.01, in the testcenter we use labview 5.
Additionally, in the development center we use a unix version of Labview and in the testcenter a Windows version.

You can Save with Option to save VIs as version 5.
Unless your VIs deal with system files in UNIX or Windows (ie. Registry...)
then you have to develop your VI specificly on that OS, since UNIX and
Windows have different ways to deal with system files. Mostly, LabVIEW is OS
independent. I used to have VIs developed from LabVIEW v.3 on UNIX, I can
still open these files from LV v.4 on Windows. Now I can still work with
these VIs on LV 6 on Windows.
Good luck,
Nam.
roybra wrote in message
news:[email protected]..
> I created an application on a machine with Labview 6.01, can I run
> this application on another machine that has labview 5?
>
> In the development center we use Labview 6.01, in the testcenter we
> use l
abview 5.
>
> Additionally, in the development center we use a unix version of
> Labview and in the testcenter a Windows version.

How to call WDA Application from an other SAP System

hello all,
I have a WDA Application and if the user click on a Button in this Application, i need to call an other WDA Application from an other SAP System.
example: SYStem X01 has a WDA Application and there is a Button in this Application, if the User click on this Button, a WDA Application from an Other System X09 shoud be displayed in the same window, same WDA IFRAME .
can any one tell me how can I do this?
Thank you all

Hi,
As mentioned earlier, you need to pass the host name and port of the second system. If the application name is same, pass the same application name.
DATA: lv_url TYPE string,
       lv_host TYPE string,
        lv_port TYPE string,
        lv_protocol TYPE string.
CALL METHOD cl_wd_utilities=>construct_wd_url
    EXPORTING
      application_name = 'ZWD_APPL_NAME'
      in_host          = lv_host   " host name of second system (X09)
      in_port          = lv_port    " port of second system
      in_protocol      = lv_protocol " protocol of second system
*      in_parameters    = lt_parameters
      namespace        = 'sap'
    IMPORTING
      out_absolute_url = lv_url.
To get the Host, Port and Protocol of second system, wrap the below code in a Function Module(RFC) in X09 and call this in X01 and then pass them to the cl_wd_utilities=>construct_wd_url as mentioned above
CALL METHOD cl_http_server=>if_http_server~get_location
    IMPORTING
      host         = host
      port         = port
      out_protocol = out_protocol.
hope this helps,
Regards,
Kiran

When creating an application installer in LV, what run-time engine or driver must be installed to install the VISA interactive control?

I've created an application installer using LabVIEW's application builder and use it to install NI MAX. However, after running the installer, the VISA interactive control is disabled in NI MAX.
The installer installs the following NI components: NI LabVIEW Run-Time 2014 SP-1(64-bit), NI LabWindows/CVI Shared Run-Time Engine 2013 SP2, NI Measurement & Automation Explorer 14.5, NI-488.2 Application Development Support (includes run-time), NI-VISA Configuration Support 14.0.1, NI-VISA Runtime 14.0.1, NI-VISA Server 14.0, NI Systems Configuration Runtime 14.5.0, vision run-time, dc-power run-time.
If I download and run the 488.2 installer, the VISA interactive control is enabled in NI MAX. But, the installer created with the application builder does not seem to install the necessary components.
What needs to be added to the installer to enable the VISA interactive control (VISAIC)?
Thanks.
Solved!
Go to Solution.

From Pedro Munoz, Applications Engineer, National Instruments
Sorry for the confusion with the forum post that Jon sent you. I did some research on our internal database and I found out the component will not be installed by any of the components added from the additional installers section on the configuration of the installer. As you have already found out you need to install the full installer in order to enable this feature.
I know that this might be an inconvenient for you because you wanted to have one installer to run. On this case may I suggest using the NI Batch Installer Builder.
The NI Batch Installer Builder allows building installers that contain National Instruments software from several products. That way you can create an installer for you application in LabVIEW (and not include the drivers in the additional installer section), then use NI Batch Installer Builder to include the installer for your application and the full version of the drivers that you mentioned.
Here is the download link:
http://www.ni.com/download/ni-batch-installer-builder-14.5/5193/en/
And in here you can find instructions on how to get started with it:
http://zone.ni.com/reference/en-XX/help/374206A-01/
Let me know if you have any question.
Regards
Pedro Munoz
Applications Engineer
National Instruments
http://www.ni.com/support

Is there an easy way to know if a vi within a LLB not being use by a Labview Application

To All,
I have developed a Labview application over a year that contains a number of LLBs. There are significant number of VIs within those LLB files that were written but have not been called by the application. I am trying to optimize all LLB files to exclude those unused VIs. Because there are many of them, the task to find out which Vi is being used and which one is not become very tedious. First question: Is there a way to automate the process? Second question: Does a compiled Labview application include all used and unused Vis from the LLBs in the .exe file? I am very appreciate any inputs from this community.
A Labview User

Ben wrote:
In pre-LV 8 you could do a "Save with options..." and choose development distribution, single prompt preserve hiarchy and LV will pick-up all of the used VI's and plomp them down in a new location leaving all of the used behind as well as fixing up a of the linkages to point at the new location.
In LV 8 and beyond you can create a Source Distribution in the project and acoomplish the same thing.
In LabVIEW 8+, you can get something similar to the first option by selecting "save for previous" and then pick the existing version (yes, it's there!).
LabVIEW Champion . Do more with less code and in less time .

I have been asked by my IT department how a LabVIEW application is secure

In general how does a standard LabVIEW application respond to these requirements:
The runtime environment shall not be susceptible to buffer overflows, SQL injection, LDAP and XPath injection, code injection or any other injection flaws. Malicious file execution and insecure direct object references shall be prevented at all times.

I know certain ActiveX actions that are deemed "security risks" will now generate errors in the LabVIEW Run Time Engine unless the registry of the host computer has been specifically modified to allow such ActiveX calls.
I guess my point is, NI does take some steps to prevent some issues at the run-time level regardless of how your code is written, so if that is the level <they> are concerned about, I would reach out to my local NI Field engineer and/or NI Customer Support and ask for help in how to answer <them>.
As Sam_Sharp pointed out, there are several things that are difficult/impossible for the RunTimeEngine to protect against, in any language. If the author of the code does stupid things or deliberately has maliscious intent, there are many things they can do that is outside the bounds of an RTE. In LabVIEW, some of the 'holes' in other languages are hard (impossible??) to do. For example, you as a coder, do not have access to creating and manipulating pointers, so you can't create code that intentionally overwrites other [edit: memory-]sectors in the host machine memory. So that would also be a case of where the run-time-engine (and its memory manager) plugs (or significantly shores up) things and makes it "safer".
The main security threats I see coming from the LV RTE engine is that there is no way the RTE can protect against malicious file removals, file hashing, injecting bad commands and/or data into network(s) and databases etc., beyond the protection offered by the OS (file/folder permissions) and IT infrastructure (firewalls, database query protections etc.).
Not sure any of that helps you out or not.. A dialoge with NI seems required for you, perhaps bring together reps' from both parties (NI field engineer and your IT people) so that they can get a line of communication going.
QFang
CLD LabVIEW 7.1 to 2013

Error 1073 when building LabVIEW app which calls LabVIEW dll

I am trying to use application builder to build an application that calls a dll created in LabVIEW. I get an error referencing a vi within the dll (Parse Stored String(multibyte).vi) saying that "This property is writable or this method is available only when the VI is in edit mode." The only option is to Continue which cancels the build. I had sucessfully built this application prior to including vis that call the dll and the program runs fine in the development environment.
Do you have any idea what is causing this and what I cam do about it?

I have found a temporary workaround in which I created a dummy dll that removed all functionality from exported vis but had the same name and function signatures. I then built the application using this dummy dll. Once complete, I replaced the dummy dll with the real dll.
This is not a satisfactory work around because we have to build and maintain two dlls. Also, I'm not sure we can do the same trick when creating the installer with application builder. So, I'd still appreciate any help you can give.

Requirements for creating labview DLLs

I use Labview 7.1 Professional to develop my applications. I would like to know what are the minimum requirements I need with it to create Labview libraries (DLLs)(so I can consolidate all my VIs). Thanks.

A dll and llb are two different things. You can't open a DLL with Labview, but you can call it's functions using the Call Library function. DLL's are usually functions written in one language (typically C) and called by another. If you just want to collect your vi's together into one file, use the llb. You can create llb's with the newer versions of Labview. You can start a blank vi, put all your vi's in the block diagram (no wires) and then select Save with Options - Development Distribution. I believe this will create an LLB with all the vi's in your block diagram. There are also two selections under Tools menu, VI Library Manager, and Edit VI Library. Both of these are useful in creating and adding vi's to LLBs.
- tbob
Inventor of the WORM Global

Create Labview application to call other installers

Similar Messages

Maybe you are looking for