LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Deploying VI to FPGA fails

When deployin a succesfully compiled project to the FPGA target, I get an error concerning the shared library NiRioSrv.dll. This can not be loaded, but is present on the system in the C:\Winnt\system32 folder. This happens with both projects of my own and projects from the examples included in LabVIEW. I have a cRIO9002 real-time controller with cRIO9101 FPGA and CRIO modules 9472, 9421, 9263, and 9201. In MAX the FPGA seems to be configured correctly, no errors are found. The following messages are shown during deployment:

1st project (my own):
Deploying HTH  (successfully deployed target settings)
Deploying Celsius to Temp.vi  (already deployed)
Deploying Temp to Celsius.vi  (already deployed)
Deploying Trim Whitespace.vi  (already deployed)
Deploying Error Cluster From Error Code.vi  (already deployed)
Deploying _nirio_device_configAddFifo.vi
Failed to download _nirio_device_configAddFifo.vi
LabVIEW:  Failed to load shared library NiRioSrv.dll:NiRioSrvLV_device_configAddFifoOutput:E on RT target device.
LabVIEW:  Failed to load shared library NiRioSrv.dll:NiRioSrvLV_device_configAddFifoInput:E on RT target device.

Download completed with errors.
2nd project (example from LabVIEW):
Deploying RT CompactRIO Target  (successfully deployed target settings)
Deploying nirviErrorClusterFromErrorCode.vi  (8.77 K)
Deploying nirviRIOSetUpMiniMite.vi  (13.75 K)
Deploying Temp to Celsius.vi  (4.54 K)
Deploying Convert to Binary (cRIO-910x).vi  (3.67 K)
Deploying nirio_AppVersionToI32.vi  (3.84 K)
Deploying Trim Whitespace.vi  (104.84 K)
Deploying Celsius to Temp.vi  (4.54 K)
Deploying Convert to Temperature (cRIO-910x).vi  (3.62 K)
Deploying Merge Errors.vi  (6.74 K)
Deploying Error Cluster From Error Code.vi  (236.04 K)
Deploying _nirio_device_endDownload.vi
Failed to download _nirio_device_endDownload.vi
LabVIEW:  Failed to load shared library NiRioSrv.dll:NiRioSrvLV_device_downloadEnd:E on RT target device.

Download completed with errors.
I have searched the forums and the help, but have not been able to find any solution to this problem. I would be very happy to hear your comments/tips.

Frank Nieuwenhuizen
0 Kudos
Message 1 of 12
(9,382 Views)
 Hello!
 
Have you set the VISA access rights?
(MAX>Software>NI VISA, VISA-Server Security, add permission)
 
BR, Christian
0 Kudos
Message 2 of 12
(9,370 Views)
Dear Christian,

thank you for your reply. Unfortunately, setting access rights for all computer on the local visa server (and starting it) did not work. I have checked the visa server on the FPGA, where all systems have access ( * ) and which is running. I verified that I have access to the file NiRioSrv.dll and even copied it to my local project folder. This results in the same error message. However, strangely the actual vi that does not download changes with every go at deploying the project.
Thank you for any further comments you might have,

Frank Nieuwenhuizen
0 Kudos
Message 3 of 12
(9,365 Views)

Hi!

Can you give please a few more details of your software, so which version of LabVIEW, LabVIEW FPGA and VISA are you using?

Regards, Christian

0 Kudos
Message 4 of 12
(9,364 Views)
Hi,

I'm using LabVIEW 8.2, LabVIEW FPGA 8.2 with Ni-RIO driver 2.1.0 and VISA 4.0.

Regards, Frank
0 Kudos
Message 5 of 12
(9,360 Views)

Hi!

Please try to remove the content of the data folder of the Measurement and Automation Explorer, C:\Programme\National Instruments\MAX\Data. Then again try to set the VISA access rights!

Regards, Christian

0 Kudos
Message 6 of 12
(9,302 Views)
Dear Christian,

thank you for your answers. Unfortunately your last reply did not work either, but I could not delete all the files from the directory you specified as two confi3* files were in use by some process that Windows did not specify. This seem to be the actual config files of MAX. The VISA access rights did not get reset and the deployment ended with the same error.
Any further suggestions are very welcome.

Regards, Frank
0 Kudos
Message 7 of 12
(9,295 Views)

Now, an other suggestion:

There could be somthing wrong with the installations on your cRIO System, so please try to reinstall all the Software of your cRIO in MAX. After this don't forget to set the VISA permission.

BR, Christian

Message Edited by Christian_M on 11-27-2006 06:49 AM

0 Kudos
Message 8 of 12
(9,296 Views)
I completely wiped the device and re-installed the software. Now my FPGA does not show up in MAX anymore as a remote device. However, I noticed that I could not re-install NI-RIO on the remote device (it is not available in the software list). I have searched on the forum, but have not found a definitive answer. Is this piece of required and if so, why is it not showing up in the list? I have installed LabVIEW with all basic options and did not change anyting in the setup.

Thanks again for your answer, Frank
0 Kudos
Message 9 of 12
(9,275 Views)
Hi Frank,


@fmnieuwenhuizen wrote:
... However, I noticed that I could not re-install NI-RIO on the remote device (it is not available in the software list). ... Is this piece of required and if so, why is it not showing up in the list? I have installed LabVIEW with all basic options and did not change anyting in the setup.

Thanks again for your answer, Frank



The initial error you were getting was most likely because NI-RIO was not installed (or somehow got corrupted) on the cRIO RT Controller. So yes, NI-RIO is required to be able to run LV FPGA applications on your cRIO RT controller. The reason why it is not showing up in the list, might be due installing NI-RIO prior to installing LV RT on your host computer.

If you have already installed LV RT on your computer (which seems you do because you were able to deploy RT VIs), re-run the NI-RIO installer and make sure cRIO support for LV RT is installed. After doing this you should be able to install NI-RIO on the cRIO RT Controller from MAX. If you still don't see NI-RIO as part of the software you can install on the controller, try repairing the NI-RIO installation.

If you can't even see the controller in MAX under Remote Systems, I suggest you Reset the controllers IP through its dip switch.

Hope this helps.

JMota
National Instruments


0 Kudos
Message 10 of 12
(9,263 Views)