As I am a new LabView's user, I have never converted a library or VI's, so I would like to know some informations. You said that they were looking for a DLL... This happened in the convert process? Or you tried to open a example? I tried to open the VI's which you converted, but they are looking for .lsb files. I couldn't find a C code or CIN objects related to the ADAC board which I am using. I have gotten the drivers and VI's from the manufacture's website, but they were built in LabView 5.0.x.
I would be glad if you could help me.
PS.: I got a DLL when I downloaded the files from the website.
To convert them I simply mass-compiled the directory. Mass compilation is done from the Tools->Advanced->Mass Compile... The mass compilation has to load each VI. Several subVIs in the AdacDaq\Advanced used the Call Library Function Node function, and it was looking for the ADLCORE.DLL dll.
I have no idea why when you're opening them it's looking for .lsb files. That has to do with CINs, which are something different. I did not get this. Are you opening a specific VI that's doing this?
The "Easy AO Update Channel" example does not use the CINs. Several of the subVIs (e.g., "AL_InitDevice") make use of the ADLCORE DLL, however.
Not having the DLL would not affect the mass compile. It will just flag it as part of the mass compilation report. The VI will still be converted.