02-23-2009 06:16 AM
I am trying to build using Labview 8.5 rather than 8.6 for compatibility reasons. However, since installing 8.6 and porting my code over to that as well I am finding that now I reset up a build script for 8.5 it no longer functions. The build fails with :
Error copying files.
Source: C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\Vision\Display.llb\IMAQ GetPalette
Destination: C:\Work folder\Programs\builds\Acoustic\SamWare Application_8-5\internal.llb\IMAQ GetPalette
Invoke Node in AB_Source_VI.lvclass:Copy_SourceItem.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
<APPEND>
Method Name: <b>Set Path</b>
The file exists but gives the same error if I include 'IMAQ GetPalette' in the build explicitly having copied it to the application directory.
Any suggestions?
02-24-2009 05:52 AM
Hello blown_leaf,
I have been looking at the error message you have been receiving, and would like to help you. If I understand your post correctly, you have been able to prepare a Build task in Project Explorer in LabVIEW 8.6 and execute it without any problems. However, you now require a program compatible with LabVIEW 8.5, so you are building the same Build task in LabVIEW 8.5. Is this correct?
If this is the case, have you individually saved each VI for version 8.5? I also see that you are using IMAQ as part of your VI. Does your VI have multiple instances of IMAQ GetPalette within it?
Regards,
02-24-2009 07:39 AM
Hi,
After solving thi error by not selecting an option in the build specification I have gone on to having problems with the installer.
Obtaining some help from NI suggested goinf to the windows control panel > add remove software and either repairing or replacing IMAQ.
It turned out that repairing the vision section solved this problem. A long and tedious process searching through IMAQ driver versions etc. thena repair of vision has worked a treat.
Thanks for looking at the problem as your suggestion did in fact prove valid.
blown_leaf
02-24-2009 10:38 AM
02-25-2009 05:07 AM
I think it was the option to 'add files to a new project library' under the 'Destinations option of the application build specification.
The original problem was probably lihnked to the later one where I needec to make sure that relevant sections of the bits of labview innstallation such as vision and vision aquisition needed to be repaired from windows add/remove programs.
Steven.