attempt to build real-time application failed

[rex1030]

When I try to build my real-time application in order to deploy it to a crio device, it fails. I can run the program just fine by opening it and clicking run. It can deploy and run all day that way, but it needs the computer that way too. So I need to be able to build and deploy it. When I do a build preview it completes just fine with no errors. I have set the program I want to start up as the startup and my subVIs virtual folder under always include. This is typical procedure for deploying projects to the crio.

When it crashes I am getting an error:

The build was unsuccessful.

Possible reasons

An error occurred while saving the following file:

C:\Program Files\National Instruments\LabVIEW 2009\vi.lib\rvi\ClientSDK\Core\ModuleGeneration\CommunicationInterfaceUtility\niFpgaDmaChannelImplementation.ctl

Invoke 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_CreateNewWizard_Invoke_CORE.vi->RTBUIP_CreateNewWizard_Invoke.vi->RTBUIP_CreateNewWizard_Invoke.vi.ProxyCaller
<APPEND>
Method Name: <b>Save:Target Instrument</b>

I put in a service request (Reference#7259553) but I am just not getting help fast enough. I am on a real deadline here and I just sort of expected the application builder to work like it has always done. I have done this a million times with other applications and never had an issue like this. 

Thanks in advance for your help guys.

[Davidek]

Hi rex1030

Very strange. I'm asuming you have checked that the file in question exists in that location and that you can open and save it manually. Try adding the file manually to your project. Could also be worth it to try moving the same file over from another computer (attaching one from my computer) to replace the one you have.

Best Regards

David

NISW

[rex1030]

I tried both suggestions. First I manually added the file to the project and set it as "always included" in the build. Still the same error.

Next I downloaded the file you gave me (thanks for that, this is the only copy of labview 2009 installed in our lab at the moment), pulled the original out and put yours in. Still the same error.

I forgot to mention before that since that file had something to do with the FPGA I have recompiled the fpga code as well.

Message Edited by rex1030 on 09-22-2009 11:04 AM

[Davidek]

Hi 

Have you tried creating a new empty project and adding your target and files? If the problem persists then try building you program in pieces to see if you can locate exactly where to problem occurs. 

Alternativly you could look in the Dependencies -> vi.lib folder in you project and try and find niFpgaDmaChannelImplementation.ctl (should be in there, but I'm not sure), right-click it and select Find-> Caller. This will highlight the VI that uses this control. You may have to repeat the Find -> Caller step a few times to move up enough to get the which of your VIs use it. Then try removing that VI and see if that solves the problem.

Best Regards

David
   

[rex1030 · Accepted solution]

With the fantastic help of applications engineer Will Schoettler, we were able to solve the problem.

1. First we tried creating a new project file from scratch, adding all the files and compiling the fpga. Same error.

2. Next we made individual builds deploying each subvi individually to see if one of them was causing the error. Each built without a problem.

3. I tried to create a new build for the main crio program and tweek the settings. Instead of manually adding the subvi and variable library folder to the 'always include' section of the build option, I simply added the main VI to the startup programs list and was going to let LabVIEW figure out which VIs to add. For some reason this gave me a more verbose error explanation and gave the following reason as the last sentance in the error explanation

"Due to operating system limitations, LabVIEW cannot create the folder because its complete path contains too many characters." 

I moved the project folder to c:/ , fixed the broken references in the project, and it built the VI and deployed it just fine.

The builder creates a directory with a really long path name within your project folder, so if you have your project folder deep in your directory tree it will attempt to create files with paths too big for windows to handle.

Mad Kudos to Will Schoettler the app engineer for such a potent and thorough troubleshooting task list of things to try that lead me straight to the solution. I am glad it was something so simple and not some form of file corruption or something wrong with my code. 

Thanks for trying to help guys.

[Davidek]

That's great news. Good work! 

Best Regards

David