Configuring MAX and Device Monitor as part Installer -

[FIC]

I am building an Installer for a system that uses Compact DAQ (Chassis + modules). My tasks, channels and scales are stored in MAX. As part of building the installer, I am exporting the MAX configuration from my development system and asking the installer to import the settings as part of the install process (.nce file).  The installer works fine but the problem starts when the installer reboots. The installer wants to import the configuration file that was included. It will not import the configuration unless hardware is present. See screen shot.

The way the system is designed. We should be able to load the software independently of the hardware. Once you connect to the hardware it should all be recognized and software then just works. No messages. No choices. No hassles.

If  I connect to hardware and import the configuration, It all works fine. I would just like to avoid this step.

Second issue - The installer installs "NI Device monitor" which is configured to run at Startup. So every time cDAQ is plugged in it comes up asking if you want to start a measurement task. I understand that this can be disabled by the user. But I would like it to be not installed or not run at start up. The user does not need to know or is not interested in knowing about NI-9172. He wants the installer to finish and just click his icon to start the program to do his work.

I need workaround for these two issues. Import Configuration file silently. Disable NI-device monitor as part of installation.

The funny thing is once you have hardware installed, and then remove it, Max does show all the hardware with an X next to it. It is not simulated. I can't understand, why it would not do it on import.

Any help is appreciated.

[EadieU]

 First Issue:

If the hardware is not going to be installed when you run the software installer, don't include the MAX configuration as part of the installer.  Instead, create it on its own in MAX (File»Export...), and import it on the target computer when the hardware is connected and you're ready to use it.  If you want, you can also import and export a MAX configuration through LabVIEW.

Second issue:

I do not know if it is Device Monitor that pops up the message asking if you want to start a measurement task every time cDAQ is plugged in.  I will look into this further. 

Regards,

Mark E.

Applications Engineer

National Instruments

[FIC]

First Issue  - Your answer is simplistic in that it assumes the enduser (not me) knows how to use MAX and import the hardware configuration. The machine with CDAQ can be shipped all over the world and the target user can be a novice computer user. To ask them to use MAX is unfair and unnecessary. I wouldlike to use the installer to do all the task at this time. Import via Labview is a possibility but requires some more coding to figure out all the hardware that is connected. It is a moving target.

Second Issue - I believe it is the Device monitor that pops up. You can confirm otherwise if it is so - But whatever is doing it needs to be stopped.

Bottom line is a professional machine and software needs a professional no hand holding installer. That is what I am looking for.

[EadieU]

First Issue - There are two ways I would go about this:

1. Import the configuration in LabVIEW when the application runs using the VIs that I mentioned in my previous post.  Your customer probably won't (or at least shouldn't) be running the executable until the hardware is installed, so this should work. 

2.Preferred - Programmatically set the devices in the application.  This will require more programming, but is the best way to go about the device/task/scaling correlation. 

The issue you are trying to work around is that the MAX configuration is very specific.  For instance, the devices all need to be connected to the computer, and the modules need to be in the exact right slots in the cDAQ chassis.  That's the way MAX configuration is. There are benefits to this, but it means that for situations like yours the devices should be programmatically set.  

Second Issue - You are correct. It is the Device Monitor that pops up.  This can be stopped by removing the registry key for niDevMon.  You should make your installer do this at the end. The key to remove is located at HKEY_LOCAL_MACHINE»SOFTWARE»Microsoft»Windows»CurrentVersion»Run»niDevMon.

Regards,

Mark E.

Applications Engineer

National Instruments