11-10-2009 11:59 AM
11-23-2009 05:14 AM
new NI-RIO driver 3.3.0
RTf2 Patch released
- check if the bug still exists
02-09-2010 08:36 PM
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
02-10-2010 04:20 AM
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
02-10-2010 02:55 PM
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
02-11-2010 03:01 AM
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!
02-26-2010 06:56 AM - edited 02-26-2010 06:59 AM
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.
02-26-2010 11:11 AM
Can you post a portion of code that reproduces the issue on SP1?
Also, is the deployment error still exactly the same?
Kurt
03-09-2010 06:59 AM
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
03-16-2010 02:08 PM