Identified conflict in CheckDataSize.vi

[MogaRaghu]

I have  identified an issue with the following set up :

A ) NI-DAQmx Base Read DIO96 ( Digital U8 1 Chan 1 Sample ).vi

and

B ) Write JPEG.vi

cannot co-exist in the same  VI. If you try  to do so, then you get a broken VI.

The reason is as below :

Both the above mentioned VIs ( A and B ) need a sub .vi called "Check Data Size.vi "  but with different functionalities. Thus you will have on the machine one CheckDataSize.vi serving the Polymorphic Read and another CheckDataSize.vi serving the Write JPEG.vi.

 And hence when you try to load A and B in the same VI, then LV  loads whichever " Check Data Size.vi" happens first  for both A and B. So either A cannot run or B cannot run depending on which copy was loaded.

This conflict is due to a common name and both being library VIs, not sure how to correct the situation. Could someone chip in with an idea ?

Thanks.

Raghunathan

[Odd_Modem]

Work with just one vi that compiles correctly. Open check data size.vi and save it in the same folder as your vi. Then rename the copy and reference the new name in your vi. The vi.lib is provided in source code so that you can change things. It is up to you to manage your computer in the face of multiple users, documentation etc.

[MogaRaghu]

Hello,

Yes that seemed the only way  out ( rename the conflicting sub.vi) .

But  I was  initially worried about the aspect of  altering some VI in the standard library.  Renaming the copy of one such vi is a viable option.

Thanks for pointing out the solution.

Regards

raghunathan

[AlanArmstead]

This issue was fixed with NI-DAQmx Base 1.5. 

-Alan A.