Why does Lab View add control elements to some driver VI's!

[Matthew_Kelton]

If you don't have the same instr.lib code in the LV2009 and LV2010 folders, it won't matter if you open the same project, because your project doesn't carry the instr.lib driver code.

LV2010 will load the version that is in its instr.lib folder and LV2009 will load the version in its instr.lib folder.  If you delete the LV2010 version of that driver and copy the LV2009 instr.lib code over, LV2010 will upgrade the instr.lib code and it will be the same.

[Matthew_Kelton]

Dave,

Depending on how long this equipment has been around, he could have downloaded the previous version for 2009, and then upgraded to LV2010 after that version was released.

[.aCe.]

---

@DavidBoyd wrote:

.aCe.,

Now I'm curious - I followed the download links for both the 2009 and 2010 versions of that driver - carefully, into separate folders - and in both zip archives the file in question has a modified date of 2011-12-15, and a file history version of 74.  Where do you see the OP's older version without the extra parameter?

Further down on that page, there are links for the individual instruments supported - and some of those lead you to an older-style driver "0604" enclosed in an LLB.  But those look completely different.

Dave

---

My point being that the 2009 drivers in OP's screenshot is before the upgraded drivers in the link. LabVIEW cant be automatically adding connector pane inputs, controls and changing enum parameters just because its saved in a different version!

[WolfS]

Yes that's right. It is only one version exist for the two different downloads.

And now when you store the folder HH ZSxx Series

on time in ...\Programme\National Instruments\LabVIEW 2010\instr.lib\

and one time in ...\Programme\National Instruments\LabVIEW 2009\instr.lib\

then you get the difference in the VI Configure Mode and also some changes in other VI's. And all changes which are done in LV2010 get an error.

[DavidBoyd]

.aCe., Matthew,

My only interest in all this was, "where did the OP get the version without the other input"?  Both his screenshots are clearly from a "project-style" driver - the VI titles show the same LVLIB namespace.  But there's only a single, 1.0 release of this driver that I can find on the IDN.  It may have links for two different LabVIEW versions, but the VIs sure look the same to me under both.

I can only guess that he inherited some kind of pre-release 0.9 beta release from an incomplete development effort.... but that's only a guess.

Dave

[DavidBoyd]

WolfS,

If you select Edit->VI Revision History on each version of the VI, what do you see for "Next Revision"?  Just curious.

Are driver libraries downloaded from IDN localized somehow?  I'm trying to think of any way that you would get a different package of VIs from what should be the same link that I followed.

Dave

[WolfS]

Hi Dave,

I have checked which next revision are displayed in the dialog VI revision history and it is different. in LV2009 it suggest 64 as next revision and in LV2010 suggest 74 as next revision.

But the files should be the same. I have it downloaded on time. I unzipped it in a separate folder. I copied it and then I paste it on time in LV2009 in on time in LV2010.

Also it isn't only one difference between this two installation, there are some changes.

It looks like LV2010 did made this changes.

[WolfS]

Attached a pdf file with some furthermore changes.

[Matthew_Kelton]

So LabVIEW is telling you you have installed two different versions of the driver.  Regardless of what you THINK you did, you have two different versions.  Delete the LV2010 version and copy the LV2009 version into the LV2010 folder.

[WolfS · Accepted solution]

Hi,

I have it done as you have it descript and now it works. But I don't know why. And I'm not the only one how have this problem. 

OK, thanks for this solution.