Traditional NI-DAQ Compatibility VIs

[TonY_20]

Hello, i'm trying to use "Traditional NI-DAQ Compatibility VIs" to use a Daq-mx card on an old application based on traditionnal Daq.

The conversion works well only on non-compilated version of the program.

When i run the executable, i get an error on the "hardware config.vi".

I'm sure that it's only this "vi" that make the problem, because i've made different test without it.

But, the main problem is that the application need this vi to configure all channels (range, type etc...).

So, someone have an answer of my problem? Why this doesn't work only on executable file ?

Thx,

Tony.

[devchander]

Which DAQ card are you using??

E series cards have suppost for both Traditional as well as DAQmx

While M series cards are suppported only by DAQmx

[TonY_20]

Of course, the daq card is a serie M... else i won't have any problem 🙂

[TonY_20]

Nobody knows this problem ?

[Travis G.]

Hello TonY 20,

I believe that the issue you are seeing has to due with the fact that the Traditional NI-DAQ Compatibility VIs internally call some subVIs dynamically, and these dynamically called VIs are not automatically included in the executable that you create.  The dynamically called VIs that are missing from the executable will be reported in the error message, similar to the following:



The dynamic call can be observed by going to the program's block diagram and following the chain of VI's given in the error message. If a different VI is referred to in the error message, you can figure out which one needs to be included in the build of the executable by locating it in the block diagram.

After you figure out which dynamic VI is missing, you will need to find where this VI is located on disk and include it in the Source Files section of the executable that you create.

I hope this helps, and if you have any further questions, it would help to provide some details about the exact error message you are seeing.

Travis G.
Applications Engineering
National Instruments
www.ni.com/support

Message Edited by Travis G. on 01-12-2007 03:55 PM

[TonY_20]

OK thank you Travis for your answer... i'll try this solution soon as possible.

[TonY_20]

Travis,

i've tried to include the vi specified in the error message, but i've still the same error, the same as you show on your screenshot..

i've tried to include this vi as dynamic vi, support file... but always the same error... i've even tried to include the full library that contain this vi but with no result ...

I don't know what to do, if you have another solution, i'll enjoy to see it....

Regards,

Tony.

[Sandra_T]

Hello TonY 20,

It looks like you are still getting the same error even though you have included all the vis as dynamic vis when you are building your application. In your application are you using any additional dynamic vis? Do you have any dlls that you use in your code?

Are you using LabVIEW 7.x and above and also have NI-DAQ driver 7.2 and older? What version of the Traditional NI-DAQ Compatibility VIs do you have?
The specific error that you got? Is it exactly as the one seen in the above reply? If it is different, can you post a screen shot of your error.

Regards,
  Sandra T.

Applications Engineer | National Instruments

[Manfred Steinle]

Hello,

I've the same problem, please review error 7" Traditinal Ni-DAQ .....
I attached a small test program, but got no answer till now ...

I hope anybody can help me,
Manfred

[Sandra_T]

Hello Manfred S.

I took some time to look over your last post and the program you posted. I tried building an .exe with LabVIEW 7.1.1 and was unable to get the error that you got. I basically left everything as the default after selecting Build Application or Shared Library (DLL). The application built without the error. I was unable to test the .exe on a different system without an LabVIEW environment, but I did test the system that it was developed on. I was unable to  see the error. What setting have changed? Let me know how I can recreate the error on my system.

The error 7 is often related to building applications were some of the vis that are called dynamically need to be added to the build. Take a look at the last paragraph of this KnowledgeBase:

What Is the Difference between Calling a VI with an Invoke Node and Calling a VI with a Call by Refe...


Please take a look at the KB and reply with how to recreate this issue. Thanks in advance.

Regards,
  Sandra T.

Applications Engineer | National Instruments