07-11-2011 04:43 PM
Hello,
I am currently trying to connect my newton Andor Shamrock camera and access the VI's so that I can use them in my LabVIEW program.
The readme software directed me to the LLB directory, in which I found all the applicable VI's for the camera. However, when I try to open them, a dialogue box appears directing me to find various files in the "Shared Library". Canceling this dialoge box allows the VI to still open, however the block diagram show ? and blanks where the icons of the camera's VIs should be.
Is there a way for me to access the VIs in the LLB Manager list or do I need to secure them from a separate source?
Thanks,
Justin
Solved! Go to Solution.
07-11-2011 05:11 PM
You do not need to use the LLB manager to access the VIs. File -> Open will let you open VIs inside of an LLB. It seems the VIs in the LLB are looking for other VIs. It sounds like you're missing some dependent files. Where did you get the files?
07-11-2011 05:20 PM
07-11-2011 05:23 PM
The files were sent from the Andor Company along with software for the camera--I can't open any of the VI's that were included in the LLB. As far as toolkits, do you mean converting them with the LLB Manager to an llx file?
As for opening them from LabVIEW itself, I still get the same message--again told to Find the files...Is it likely that I actually don't have the VIs?
07-11-2011 05:31 PM
07-12-2011 09:42 AM
Mainly because all of the VI's are unable to be opened--and there is close to a hundred. Would you think that the needed toolkit would be specific to the software/company?
07-12-2011 09:58 AM
Just a few names would be sufficient to give us a better idea. You can do a ctrl+h and hover over one of the missing subVI with the mouse and the missing filename will show in the context help.
07-12-2011 11:23 AM
Also, when it's trying to load the VIs the dialog will show the entire path for the file it's trying to load. You can click on the Browse... button to tell LabVIEW to stop searching and then write down the original path to the VI. These paths often tell you exactly what toolkit or library, if any, it's looking for.
07-12-2011 11:29 AM
Fortunately, after conversing with the company, its seems to have been a fault on their part. After redownloading the software, the VI's became available. Thank you to everyone for their help; hopefully this is useful to others.