cRIO deployment fails

[Rimrock]

I too recently upgraded to LabVIEW 2009. 

I have been developing a project for a cRIO device and have been deploying a VI without problem in 8.6.1.

After upgrading I immediately began receiving the same "Host LabVIEW failed to download ..." deployment error message mentioned by others.

After seeing Pauls message I disabled the "Allow Debugging" VI property and now it deploys and runs fine.

[jkurtw]

Hi Rimrock,

Can you or anyone else that is getting this error share your code with NI?

We are aware of the issue, but tracking it down without a project that reproduces the issue is difficult.

If you are not comfortable posting your entire project on the forums, you can email it to me at kurt.williams@ni.com or to our support department at support@ni.com.

thanks, 

Kurt Williams

Product Manager - LabVIEW Real-Time 

[jkurtw]

Update - we have code that reproduces this issue and are actively investigating the root cause.

Kurt 

[Stackbuster]

Hi!

I have also experienced this problem recently. But compared to other members who got this problem after upgrading to Labview 9, my application was created in LW 9 and worked just fine in the beginning. My problems started after I added 2 new C-modules to my design and compiled it again. I got this error:

"Deploying MyHostCode.lvlib:MyHostCode.vi
Host LabVIEW failed to download MyHostCode.lvlib:MyHostCode.vi
Deploying cRIO2 Container
Deployment completed with errors" 

 I added the modules in Project Explorer and configured the FPGA by using the FPGA Wizard. Like SAKALAUKUS explains the FPGA-vi runs just fine on the target, but the RT-vi is not.

I can also report that when I disable the "allow debugging" option, I don't get the error message, and the vi apparently runs like it should.

The 2 new C-modules I added to the design are just added in the software. The hardware modules are yet to be put into the chassis when they arrive from the factory.

Jarle

[Riconquistiamola]

Hello all,

As Kurt said, we are actively investigating this issue (CAR 191558) to determine the cause. If you are experiencing this issue and can provide us with reproducing code, we will validate our solution fixes the problem with your code. Simply contact NI Support or email Kurt, who provided his email address in an above post.

Please contact NI Support if you have an active deadline that is currently hindered by this issue. I will update this forum when we have found a solution.

Cheers.

[Riconquistiamola]

Hello all,

Our developers have investigated CAR 191558 and determined adding 64-bit support to a LabVIEW function causes the failed deployment. The LabVIEW function is not available to users but is called in many LabVIEW block diagram items, including FPGA Read/Write Control nodes and FPGA Invoke Method nodes.

To resolve this problem, please view KnowledgeBase 52RHPSQ0: Why do does my VI fail to deploy in LabVIEW 2009 Real-Time with the message “Host LabVIEW failed to download RT_Original.vi. Deployment completed with errors.”?

Please contact NI Support if you need further assistance.

[xkenneth]

Is there an error log I can read somewhere, this one is still biting me.

[jkurtw]

xkenneth,

I don't know of a log file that is catching this, but there may be.

Are you still getting a deployment failure even with all of your FPGA Interface VIs inside of subVIs?

Was there something you added that brought the problem back? 

[xkenneth]

I'm using the scan engine. Is there a limit to the number of timers you can have? As I have quite a few. I don't know if those RT timer blocks are working some magic behind the scene.

- Ken 

[jkurtw]

Hey xkenneth,

What do you mean by "RT timer blocks?" Are you using Timed Loops?

Can you share your code?

Kurt