Traditional NI-DAQ Compatibility VIs

[Manfred Steinle]

Hi Sandra,

the ERROR occurs not during the build, it occurs when I run the application (.exe).
It works fine with an E-Series board, but if I try to run with an M-Series board the ERROR comes up.

Hope this helps for recreate the ERROR.

Best Regards,
Manfred

[Sandra_T]

Hello Manfred,

I was wondering if it was possible for you to post the executable that you have built that will cause this error. Also take a look at the naming conventions on each of your devices.
Take a look at this KnowledgeBase for more information:

Configuring Device Names for Using Traditional NI-DAQ Compatibility VIs

Let me know which device name you have labelled your device in your code, so that I know to configure my M series card to the correct name in Measurement and Automation Explorer(MAX). Also what are the step by step instructions to cause the error.

I was unable to cause the same error with my build. I am using your code and building an .exe and running it with an M series card labelled as '1' in MAX. I've been working on this issue but was unable to see the issue. What Compatibility driver version are you using? What Traditional DAQ driver do you have?

Regards,
   Sandra T.

Applications Engineer | National Instruments

[Manfred Steinle]

Hi Sandra,

device name is "1",  compatibility driver version is 1.3, NI-DAQmx driver is 8.1.0f1, traditional NI-DAQ driver is 7.4.0f0.

If I run the program in Labview 7.1.1, it works fine with E-Series and M-Series boards ...
If I build an .exe, the programm works only with the E-Series board, with the M-Series board the ERROR occurs...

If your .exe works, could you please create an install file and send it to me for testing?

Thank you in advance,
Manfred

[Tom_@_RTC]

Hello all,

I too have this problem with the compatibility VI's when you cannot run the program as a standalone exe file. The program works perfectly in the development enviroment but if it works here why not when in the distrubuted format??

I have all the correct settings that have been checked and checked again by the national instruments team. It seems that it is not taking the compatibility files when constructing the exe and yet some of the compatibility files work in exe mode it just seems the hardware related VI that is malfunctioning. Is it possible that there is an error within its source code that we can fix or you can fix and redistrubute????

Any guidence on this would be appreciated

Tom

[Sandra_T]

Hello Tom,

It looks like you have been working on this issue with National Instruments Technical Support. Let me first address your first question about why it would work on the developement environment and not on a distribution. On the developement machine you have all the correct driver components installed that will allow you to run the program, but once you try to create a distribution there is a possibility that the required dynamically called VIs that are not automatically included in the Application Builder specifications. If the subVI is not included in the distribution, then you will run into issue when the application gets deployed on the other systems this is going to cause an error.

Are you also throwing a "Error 7"? Which VIs does the error refer to?
What specifically are you seeing on your system? What hardware are you using? LabVIEW version? DAQ and DAQmx versions?

Will you be willing to post an example VI (modified version of your code) that exhibits this behavior and the Project Library, so that I can try to recreate this issue.
Also include a screen shoot of the error too.

Regards,
  Sandra T.

Applications Engineer | National Instruments

[Tom_@_RTC]

well at the moment we are in a transition stage of swapping a 6221 for a 6521 after realising the lack of analogue triggering!
It is the same error code and it is with the hardware config VI

i am running all the most reacent versions of the drivers and was compiling in LabView 8.2 but have tried it in 7, 7.1 and 8.5 all with the 6221 card. Despite the lack of analogue triggering our program works perfectly but only in Dev mode. I have tried with the engineers constructing our own support files etc for the build of the exe with no success. I am in great belief that it is an issue with either the compiler of the exe's or the actual compat VI's themselves. It seems to me that the compiler is somehow grabbing all the compat VI bar a few that are obviously critical to the function of the system.

I will post screenies on here as soon as we get our 6521 card so you can see all the errors that we are getting

Regards

Tom

[Sandra_T]

Hello Tom,

I'd definitely be interested in seeing the screen shots. Have you consider redeveloping your code using the DAQmx driver? Here are some resources that you can reference:

Transition from Traditional NI-DAQ to NI-DAQmx in LabVIEW

Another thing to test on a test machine is manually installing the compatibility VIs to see if you will still throw the same error code.

I look forward for your future post.

Regards,
  Sandra T.

[Tom_@_RTC]

i have tried installing the files manually and using the setup many times with no change to the process.

We have considored changing the whole program to a system using the DAQmx VI's but with a program that is 100's of VI's in size this is a much easier and quicker option, which we need, both the NI support staff and our NI field engineer agree with the compatibility process.

Im wondering if it is worth creating my own version of the hardware VI using the DAQmx VI's within it, in coordination with the Trad VI's that work along side it?

 have tried to look inside of the VI that is playing up but being typical it is passworded so i cannot see whats going on inside! Is there any way of obtaining the password for this or at least some screen dumps of the workings so that i can see if there is anything within that could be causing me issues?

I am aware that some features do not work in the compatibility files and am begining to think that somewhere there is a variable being gathered or changed that is causing the program to throw its toys out. However this still doent explain the working system in development mode and not working in EXE, its a real brain buster!

Regards

Tom

[Sandra_T]

Hello Tom,

I understand that for your particular application transistioning may not be the easiest solution. In the futures, you can consider making the change for new projects. I wanted to make sure that I informed you of all the various options you have.

As I understand curently, even if you install the software ( compatibility VIs) manually on another computer, you are still running into the error message. You are able to reproduce this on several different computers?

With regards to your question about the hardware VI, it is hard for me to comment on that because I don't know what your code does. If it is possible to use the DAQmx driver in conjunction, I'd give it a try.

Would you be able to create a small project with a sample of your code that is exhibiting the same error, so that I may test on my end. If you can please attach to a future post.


Regards,
  Sandra T.

Applications Engineer | National Instruments

[Tom_@_RTC]

Hello,

I am now fully armed with my 6251 card and now getting other errors than i had before! this is extremely strange!

as before i had the hardware config error, i am now getting an AI buffer read error that does not show when in the development mode, although when in development mode the speed is unbelieveibly slow! especially for a card that is supposed to be capable of doing 1 mega samples per second. I am going to try to re-install all of the drivers as i think this could be an issue with the card, but am desperately running out of time and ideas

i now have this error showing when i run the exe application that i have built from my source code:

This error only occurs when i run an exe that i have built, this does not show in the dev enviroment running but the dev enviro is slow!

I am also having issues with another error that i have solved but not in the best way possible, the error i get is:

and originates from this block in my code and anywhere else containing the seen VI:

This is the VI that controls our waveform generator module of the program and uses the hardware configuration instead of relying on software to preform the same task

As you can see i have removed this VI from the program using a case statement to allow the program to function, luckly enough my predicessor to this program wrote in

an added feature should this not be avaliable to run the waveforms but at the cost of the samples per second achieveable without causing a backlog.

Even with the waveform off it still is slow and still causes an error in this part and any other parts of my program that use this VI with DAQmx cards, is there an alternative

VI(s) within the DAQmx menu that i can use to do the same operation??

I am having difficulty reinacting the errors i was getting with the 6221 card but the cards are slightly different and the change to 8.5 might have some issues

software wise therefore i will go ahead now with my reinstalls

Hope this helps you help me

many thanks

Tom