04-22-2014 02:45 PM
Thanks for your support. We will modify for now and work with it.
Please update this thread with any news on a new release once these bugs are flushed out.
Thanks,
Monil
08-26-2014 07:59 AM
I picked up where Monil and Larry left off and am working to make this a shared tool. The build to an executable was not functional and I quickly learned that many VIs were called by reference and not inlcuded n the build specification. I added the following VIs to the build specification:
However, I still cannot build due to errors present on locked VIs; Download Bitfile.vi and Set RIO Device Settings 2010.vi.
Does anyone have unlocked verisons of these VIs?
James
08-26-2014 04:00 PM
James:
Those 2 VIs call internal code, so we cannot provide you with unlocked versions of them. However, the good news is that the need for them is lowering over time as we provide more functionality through NI System Configuration API.
When used in combination with NI-RIO 14.0, those VIs are needed only when RAD is deploying a RIO FPGA bitfile to a cRIO-910x chassis. In other words, if you don't deploy bitfiles used at powerup or you use any other cRIO chassis, you could remove the calls to those VIs completely.
Dan Mondrik
08-27-2014 06:49 AM
Dan,
Thanks for the additional details regarding the use of those two VIs.
I will look into replacing them with popup messages to alert the user of the missing functionality.
Regards,
James
08-29-2014 08:01 AM
Dan,
I am deploying with FPGA to Flash to a cRIO-9014 and am getting an error from the RIO Check.vi.
Error 1003 occurred at Open VI Reference in RIO Check.vi
What are the minimum versions for the development system and RT target for this deployment to function correctly?
I am currently using LV2013 with this software on the development PC and RT Target.
Thanks for any suggestions/assistance.
James
08-29-2014 08:18 AM - edited 08-29-2014 08:18 AM
If I'm right, the cRIO-9014 controller works with both a cRIO-910x chassis and a cRIO-911x chassis. They do have different architectures, which impacts the software. If you have NI-RIO 13.1 or higher on the target and it's a cRIO-911x chassis, you should be able to deploy your FPGA to flash without needing those 2 files I referred to yesterday. Since you have NI-RIO 12.1 on the target, it still requires the legacy VIs for FPGA deployment. (And recall I had mentioned that for a cRIO-910x chassis, all shipping versions of NI-RIO require those VIs.)
I'll admit this is a complicated combination, so I hope my answer makes sense.
Dan
09-10-2014 06:30 AM
@Dan_Mondrik wrote:
If I'm right, the cRIO-9014 controller works with both a cRIO-910x chassis and a cRIO-911x chassis. They do have different architectures, which impacts the software. If you have NI-RIO 13.1 or higher on the target and it's a cRIO-911x chassis, you should be able to deploy your FPGA to flash without needing those 2 files I referred to yesterday. Since you have NI-RIO 12.1 on the target, it still requires the legacy VIs for FPGA deployment. (And recall I had mentioned that for a cRIO-910x chassis, all shipping versions of NI-RIO require those VIs.)
I'll admit this is a complicated combination, so I hope my answer makes sense.
Dan
Hello,
I'm running into this problem with 'Download Bitfile.vi' and 'Set RIO Device Settings 2010.vi' too. Could you please clarify what you replace them with?
LabVIEW 2013 SP1, NI-RIO 14.0.1, NI System Configuration 5.6.0 for Real-Time, NI System Configuration Runtime 14.0.0
Regards,
Richard.