11-28-2009 06:31 PM
After alot of screwing around i was finally able to get my build to preview. the problem now is that i can't get past the build process altogether. it hangs during the save process.
nvoke Node in AB_Source_VI.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_RTEXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_RTEXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_Frmwk_Build.lvclass:Build.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller
<APPEND>
Method Name: <b>Save:Target Instrument</b>
This is what i get.
Jeff Y
11-30-2009 12:53 PM
Hi jeffyy,
What version of LabVIEW are you using? What is your application doing (general description)? At what point exactly are you seeing this error? What RT target are you using?
At this point, I would suggest trying to build just a really simple RT exe (such as a while loop that blinks an LED or something like that) and see if you can deploy that to your target.
Thank you for choosing National Instruments.
Aaron Pena
National Instruments
Applications Engineer
11-30-2009 05:02 PM
I'm usingLV 2009. The point that it fails is during the build when it attempts to save the vi i'm building. I have also tried to build a simple RT target with success. I have several functions along with a PID vi from the toolkit.
JY
12-01-2009 06:00 PM
Hi jeffyy,
Are you using autotuning by chance? According to this KnowledgeBase article, autotuning is not support in RT.
Since you are able to build a simple RT executable successfully, I would suggest trying to cutting down your VI (make a backup first) until you can successfully build an executable. At that point, you'll know what is causing this error and then work on repairing it.
Thank you for choosing National Instruments.
Aaron Pena
National Instruments
Applications Engineer
12-01-2009 06:14 PM
Jeff,
It may be possible that the build is trying to create files with paths that are longer than the Windows maximum. If the local destination directory in your build specification is significantly long, it is possible for files to be created that are too long. I believe this results in "Error 6" if I remember correctly. You can test this by changing the "local destination directory" in your build spec to a shorter path, such as "C:\testapp".
Chris M