Create the Installable

[spKalanga]

Hi all,

I am using LabVIEW 2009 with vision development module. i have developed the code for my application. im using Mightex USB camera. I need to create the Installable, apart from Labview run time engine and Vision run time engine. I need to install Mightex drivers, imaq_usb_installer_setup.exe and imaqUSB.llb. how can i link these things with my installer to create the perfect installable for my application.

Thanks in Advance,

Kalanga

[Cat]

I'm assuming that when you say you have code for your application, it means you have built your code into an application (*.exe)?? Otherwise, that's a completely different question...

There is no way to get the LabVIEW Installation Builder to automatically create an installation that will "install" anything other than your LabVIEW components. You can have it copy the driver files to someplace during the installation, but if they need anything more than this to work, you will need to then "install" the drivers manually. Or write some sort of program to do it, but either way it's a separate action.

You might want to take a look at a stand-alone installation builder like InstallShield . It is very powerful and might be able to perform multiple installations. I used to use it before NI included the Installer in LabVIEW.

[spKalanga]

Thanks CAT,

Ok, i can install external drivers manually. But the "imaq_usb_installer_setup.exe" and "imaqUSB.llb" and all how can i add with installer? Is there any options to make it in installer itself otherwise i have to install it seperately.....

Thanks in Advance,

Kalanga

[ShaunR]

If you get rid of the imaqUSB.llb (usb is has been supported in MAX since V2009) you can just include the MAX configuration in the installer.

USB Camera Error

[Dan DeFriese]

Thanks CAT,

Ok, i can install external drivers manually. But the "imaq_usb_installer_setup.exe" and "imaqUSB.llb" and all how can i add with installer? Is there any options to make it in installer itself otherwise i have to install it seperately.....

Thanks in Advance,

Kalanga

The 'Advanced' page of the installer properties allows you to specify an executable to run after the installer completes. In the past I've used this feature to lauch the 3rd party installers. (I create a small .exe in my project which gets placed in the TempFolder by the installer. After the NI stuff gets installed this temp.exe runs and calls the 3rd party installers located on my install CD.)

It's certainly not perfect but it usually works for me.

[asbo]

The 'Advanced' page of the installer properties allows you to specify an executable to run after the installer completes. In the past I've used this feature to lauch the 3rd party installers. (I create a small .exe in my project which gets placed in the TempFolder by the installer. After the NI stuff gets installed this temp.exe runs and calls the 3rd party installers located on my install CD.)

I imagine a batch file here could work just as well (if you don't want to jump through the hoops of writing your executable).

[spKalanga]

If you get rid of the imaqUSB.llb (usb is has been supported in MAX since V2009) you can just include the MAX configuration in the installer.

USB Camera Error

Thanks Shaun,

I tried that one. But while accessing the USB cam from MAX after grab if i want to stop the CAM and moving for some other things in MAX means the MAX is completely closed. i tried with LabVIEW code also. It is running with out any error but after running the code when coming to the Close camera function the total labview gets closed. I dont know whether this is the Problem with Camera(im using Mightex USB camera) or NI.

Thanks in Advance,

Kalanga

The 'Advanced' page of the installer properties allows you to specify an executable to run after the installer completes. In the past I've used this feature to lauch the 3rd party installers. (I create a small .exe in my project which gets placed in the TempFolder by the installer. After the NI stuff gets installed this temp.exe runs and calls the 3rd party installers located on my install CD.)

It's certainly not perfect but it usually works for me.

Thanks Dan,

You gave a good idea. i will try with that. Im using seperate NI library for USB camera "Imaq USB.llb". whether i should add this library with installer to run my application or no need?.

Thanks in Advance,

Kalanga

[Cat]

The 'Advanced' page of the installer properties allows you to specify an executable to run after the installer completes. In the past I've used this feature to lauch the 3rd party installers. (I create a small .exe in my project which gets placed in the TempFolder by the installer. After the NI stuff gets installed this temp.exe runs and calls the 3rd party installers located on my install CD.)

Good point. I should have been a little more specific when I said an option was to write another program to do it for you.

There's an idea on IE that would take care of this.

[spKalanga]

If you get rid of the imaqUSB.llb (usb is has been supported in MAX since V2009) you can just include the MAX configuration in the installer.

USB Camera Error

Hi Shaun,

I can find my USB camera in MAX, But if i try to stop the grab in max after caputuring the image the total MAX gets closed. the same thing is happening in LabView also( whenever i call the USB close.vi function). whether this is camera issue or i have to do some other thing. please give your ideas. (I am using Mightex USB camera).

Regards,

Kalanga

[ShaunR]

Hi Shaun,

I can find my USB camera in MAX, But if i try to stop the grab in max after caputuring the image the total MAX gets closed. the same thing is happening in LabView also( whenever i call the USB close.vi function). whether this is camera issue or i have to do some other thing. please give your ideas. (I am using Mightex USB camera).

Regards,

Kalanga

MAX uses NI-IMAQdx so you should be using the IMAQdx functions instead of the USB driver.llb functions (see the link I posted earlier). These are notoriously problematic. Make sure they are uninstalled / removed from your system.

Also, make sure you have the latest IMAQdx drivers installed.