Trouble with NI USB-9162

[ColterM]

Hello,

I am having trouble with my USB-9162 operating to how I want it too. I have a 9125A module connected to it and what we would like to do is measure the force of a compression gun for quality purposed. We have a program to run the exe. file, but when I start the program and run it, nothing happens. It sys the program is there and operating fine, but we are receieveing no data in return. How can we solve this issue? Is there some driver that we do not have? We have the latest version of the NI DAQmx. Any help would be appreciated! Thank you.

[Miro_T]

Hi

I think your question is better suited for Multifunction DAQ forum. Now whoever responds to your question will probably want to know this:

Looks like you are using an exe that someone else wrote and you dont have an access to the developlemt code, correct?

Does your exe report any error that might indicate what is happening?

Do you see your USB-9162 and the NI 9215 in NI-MAX? Can you do simple aqusition using test panel? If yes this will tell you your hardware is ok and you have adequate driver for your HW. Your exe needs a LabVIEW run-time engine but since you are able to run your exe this would indicate you already have it.

When was the last time this setup worked and what changed since then?

[ColterM]

Hi Miro,

I will also post in the Multifunction DAQ Forum.

To asnwer your questions;

I do not have access to the development code. The exe. does not report an error, but since it was constructed in house, I dont believe they would have set that up for this problem. My USB-9162 and the NI-9215 are visible and, accoridering to NI MAX, operating correctly. I even get a solid blink from my USB-9162 indicating that it is operating properly. The Test panel results come back giving me an example funtion, also indicating it is receiveing results and displaying them accordingly.  I also have the updated version of the LabVIEW Run-Time Engine.

The setup we are working on now is brand new. With the old code running on a new version of LabVIEW. Basically, the only thing that didnt change was the old code. All new items here. This gives me the thought that the code was written for an older version of LabVIEW and for a different piece of hardware and software? Would that make a difference? 

Thank you for taking your time to answer this Miro_T.

[Miro_T]

It’s been a long time since I have touched DAQ but If I remember correctly you will need LabVIEW Run-time engine and DAQmx runtime engine versions that match the versions of development software used to make the exe.  Again DAQ folks will be better to answer this. Usually developers who write exes also build an installer that go with it. An installer installs all necessary software components for you(the user) so you don’t have to worry about it….  

[ColterM]

That may just answer my whole problem. The exe. was written by our design engineering manager a while back and he cant remember all that went into it. I do have both LabVIEW and DAQmx runtime engines, however they are in a version 5 years newer, so that wont help. I would need to revert back to the old 2011 LabVIEW.

Thanks again for your help.