cDAQ intermittent USB communications with executable VI

[Felixr]

We are replacing a computer that is running one of our test stands. The stand runs on a USB NI cDAQ-9174 and has three modules:

NI 9472 (digital out)

NI 9265 (4-20mA out)

NI 9203 (4-20mA in)

The old computer was running the stand straight from LabView, but we are out of licenses and have NI Developer Suite, so I figured this would be a good time to use Application Builder and try compiling an executable to run the test stand from the new computer without installing LabView.

I compiled the executable in LV2011 and installed the LV RT environment as well as the necessary device drivers on the new machine. I also applied a Windows hotfix on the machine to improve USB communications for LV running on Windows XP.

The new machine can access all three DAQ modules through MAX. I can toggle the digital outs, generate 4-20 mA signals and read them back from the sensors.

The executable VI opens, but only the NI9472 module works. The other two are not communicating with the VI.

Is this an issue with the executable VI or one of the many bugs I have experienced with LV USB communications?

Your help is much appreciated,

- Felix

[PackersFan]

Are the names of the modules exactly the same in MAX on the new computer as they were in the old computer?

[Brad_K]

Hi Felix,

What are the symptoms of "not communicating"? Is there an error message?

Brad

[Felixr]

Chris,

I checked the names in MAX, they appear to be idential to the ones on the old machine.

Brad,

The NI 9472 ditital module turns its ditital channels on and off when commanded by the executable VI.

The NI 9265 current output module does not output any current when commanded by the executable VI.

The NI 9203 current input module does not return any values to the executable VI. All indicators read NAN.

The VI runs fine - there are no error messages.

All three modules work fine in MAX.

Thanks in advance for helping me out with this one... it's driving me nuts.

[salidobitbetter]

Hi Felixr,

Since you are using the Application Builder, you might want to consider creating an installer which would include all the drivers and dependencies needed for your application including the RunTime Engine.

What operating system are you running on the new machine? Make sure that the RunTime Engine version is compatible with the OS and your version of LabVIEW. The fact that you are communicating with MAX on your machine tells me that the modules and drivers are working fine, so I'd look at the executable setup.

Have you tried running the executable on the development machine?

Best Regards,

Andrew S.

[Felixr]

Still no luck.

I have tried compiling an installer that has the RunTime engine built in. (Runtime version is LV2011 running on a Dell Windows XP laptop) - Same problem as before.

I have even tried running the executable on a second laptop to make sure the problem wasn't with the first machine. Same problem: Everything works fine in MAX, but the VI only communicates through the ditial ports, both analog in and out aren't operable.

Everything works flawlessly when I run the executable from the development machine, or any other machines that have full LabView installed on them.

I'm sure there is a simple fix to this issue. Any tips would be greatly appreciated.

[Ever_Song]

Hi Felixr,

First, here is a forum post that should prove useful at it is very similar to what you are experiencing. Second, it might be worth including the development machine’s Measurement and Automation Explorer (MAX) configuration file in the installer. Found under the Hardware Configuration category in the installer. Third, it may be worth including the DAQmx runtime engine in the installer (though it sounds like the drivers are already installed since the modules work in MAX).

Hope this helps.