Real-Time Measurement and Control

cancel
Showing results for 
Search instead for 
Did you mean: 

cRIO deployment fails

Solved!
Go to solution
The timers and counters under the real time palette. I'll upload the code asap.
0 Kudos
Message 21 of 43
(4,618 Views)

new NI-RIO driver 3.3.0

RTf2 Patch released

 

- check if  the bug still exists

Message 22 of 43
(4,547 Views)

I still have the bug in Ni-RIO 3.3.0.  I am downloading 3.3.1 now, and I'll let you know if the bug exists in that one later.  If any NI applications engineers still want sample code for this bug, I will email it to you, just let me know. 

 

Thanks for all your support.

 

James Sakalaukus

0 Kudos
Message 23 of 43
(4,319 Views)

NI-RIO 3.3.1 is FlexRIO specific this will not solve your problem.

 

Try this:

 

- reformat the cRIO

- install NI-RIO 3.3.1 on your controller select all options available ( just for the deployment test )

- mass compile your project

- deploy your project

0 Kudos
Message 24 of 43
(4,310 Views)
Solution
Accepted by sakalaukus

The fix is in the LabVIEW patch, not in the NI-RIO update.

 

Make sure you install the software to the cRIO from a machine that has the RTf2 patch applied.

 

Kurt 

Message 25 of 43
(4,296 Views)

Thank you both for the replies, I didn't have the new patch.  After downloading and installing it, I am able to deploy my applications with Labview 2009.  Thanks!

0 Kudos
Message 26 of 43
(4,280 Views)

Well I am experiencing this issue as well. However I have Labview 2009 SP1 installed along with NI-RIO 3.4 and I am still experiencing the issue.

 

I am weary of the workaround suggested in the knowledge base article because we are loading different bitfiles at different times because the fpga doesnt have enough gates to hold it all at once. This results in broken reference wires if we try to place any of the FPGA functions into subvi's. The workaround for the broken reference wire issue involves creating reference constants binded to a specific bitfile. Obviously this will not work either because we are loading different bitfiles at runtime. 

 

I am stuck. I am working on a deadline so while upgrading the massive project to 2009 initially sounded like a great idea, now I am not so sure.

Message Edited by rex1030 on 02-26-2010 07:59 AM
---------------------------------
[will work for kudos]
0 Kudos
Message 27 of 43
(4,144 Views)

Can you post a portion of code that reproduces the issue on SP1?

 

Also, is the deployment error still exactly the same?

 

Kurt 

0 Kudos
Message 28 of 43
(4,127 Views)

Hi All,

My PC has:

LabVIEW 2009 SP1

LabVIEW RT 2009 SP1

NI-RIO 3.3.1

 

And inside cRIO:

NI-cRIO 3.3.0 with Scan Engine support

 

I just fixed this issue by uninstall all software inside cRIO then reinstall NI-cRIO 3.3.0 Nov 2009 without "NI-cRIO 3.3.0 with Scan Engine support".

 

Waheeb Alwan

Application Engineer

Pioneers Technical Systems

0 Kudos
Message 29 of 43
(4,052 Views)
Thats exactly everything I have installed and I am still having the issue. I will try again though, formatting the device again and everything. I am more than willing to FTP my project to you guys and let you see if you can reproduce the error. Its a big project so posting it here just isn't possible.
---------------------------------
[will work for kudos]
0 Kudos
Message 30 of 43
(3,987 Views)