Hi Matt
As LabVIEW 7.1 loads so fast it took me at least 50 opennings and use close reading glasses to see that I have LabVIEW 7.1.
I remember I tried in the past to add laVIEW 7.1.1 on top of LV 7.1 but did not let me do it.
Maybe because I have also version 8.0 and 8.6 or for some other reason.
This past weekend I came to work both days to advance on this issue but no luck yet
Our requirements are that in the end to have one version for our drivers LV wrappers and that is LV 7.0. Tough requirement when the tool I use are against me 🙂
I may have some good news below for me and for anyone that read these posts.
POSSIBLE SOLUTION BELOW:
Today I could make some sense of all my troubles why all LV 8.0 and LV 8.6 versions are working but LV 7.1 not.
To recount my original problem I was forced to create LV wrappers in LV 8.6 as my IVI drivers have an underscore in their name jdMAP200_VOA.dll.
If I try to use the Import Driver Wizard CVI Tool from LV 7.1 on jdMAP200_VOA.dll it did crash the LV 7.1 in a flash.
After a long research of this crash I discovered that LV 7.1 Import Wizard Tool crashes on this IVI driver since has an underscore in the name as jdMAP200_VOA.dll.
Fortunately later I was able to get version LV 8.6 and that version has a new import driver tool caled "Create VI Interface to a CVI instrument driver" under the Intrumentation menu.
This new LV 8.6 version tool did accept the driver name with underscore jdMAP200_VOA.dll and build all the LV wrappers for LV 8.6 correctly.
Along all these LV wrappers in LV 8.6 other menu files are created plus a specific file called jdMAP200_VOA.rc are automatically created. I copied these extra files along the LLB pacakge savede for lower LV versions.
At that time little did I know that this .rc file will prove to be later a source of nightmare when I stepped from LV 8.0 down to LV 7.1
From LV 8.6 I saved those LV wrappers in LV 8.0 and they are working fine for all methods plus any Property Node.
From LV 8.0 I saved in LV 7.1 and here all methods work but Property Node always throw ERR 7.
Only today I have found that Property Node is reading the resource file that is created with LV wrappers but I never suspected something wrong with that file.
When I build my LV wrappers in LV 8.6 the Import Tool has a GUI interface that ask you for the driver_name and has a * for extension of the DLL file and in my case this was jdMAP200_VOA.*
Now in LV 8.6 and LV 8.0 when the jdMAP200_VOA.rc file with jdMAP200_VOA.* for the library name properly connecting the Property Node at design and run time and get whatever propert I need from the driver DLL as these versions now that jdMAP200_VOA.* stands in fact for jdMAP200_VOA.dll and is working fine.
But LV 7.1 is completely numb when is time to read the DLL name from the resource file. At design time LV 7.1 read the driver name as jdMAP200_VOA don't care about its extension and all properties are clean on diagram but at run-time is another story. At run time is looking for jdMAP200_VOA.* but this file does not exist in this form on my drive so throw out ERR 7.
Today I decided tp open the jdMAP200_VOA.rc file in edit mode and manually change the name of driver library from jdMAP200_VOA.* to jdMAP200_VOA.DLL inside this resource file.
After restarting LV 7.1 and redo that small VI the Property Node did get the right property value out of my IVI driver.
There is not much information about how Property Node works in LabVIEW and even less about the role of .rc file for the Property Node. The same could be said about the ERR 7 few posts around that end up in wrong file path or file names.
Hope that the next guy hitting this roadblock would read this posts and make more sense of ERR 7 when is coming from a resource file build automatically by one of LabVIEW tools.
Thanks for feedback
Sorin
