FPGA Read/Write Control Error 52005

[YueLiao]

Hi Mayank,

I searched this post page since I met totally the same problem as you metioned here.

I am using the LabVIEW given example for 6587 named 'NI 6587 Serial Generation - Export Clock' project without any change.

After successfully compiled the FPGA vi, Runing the Host vi returns the error 52005.

Also, I found this error is caused by writing the controls which are set inside the SCTL (namely, 'Gen_Reset','Static/Count Up' & 'LVDS_Ch0_Wr').

Have you resolved the problem? Any clue?

[mbothra]

Hi,

It is a bug in LabVIEW 2016 release. Older NI6587 FPGA VIs don't run. I was told that if new VIs are created from scratch they should work. The only solution I found was to move back to LabVIEW 2015.

Thanks,

Mayank

[YueLiao]

Thanks for your reply.

I suppose this problem is coming from the FlexRIO driver 16.0 instead of LabVIEW 2016, because my software environment configuration is: LabVIEW 2015 & FlexRIO 16.0.

I've tried to downgrade the FlexRIO driver to 15.0, the problem was resolved.

Yue

[Ancient1]

I received this error when I tried to use an example "NI 6589 Continuous Generation - Export Clock(FPGA).vi".  I am running Labview 2016 and FlexRIO 16.0 on a laptop with Windows 7.  I am using the NI 7932R with the NI 6589 adapter module.  I simply rewrote the VI and the error disappeared. Hope this helps someone.

[Veeru_8899]

Hi i am also getting the same error suddenly in my application, before same code with same bit file working fine with flexrio 7962 and 5781 module.only Read/ write note has generating the error.why? any one can answer. i am using labview 2015.

[jordans]

Hi PowerStar102108,

Have you taken a look at this documentation?

Error -52005 After Compiling in LabVIEW FPGA
http://digital.ni.com/public.nsf/allkb/8A49034C699AA6FF862577D2007D9970

Why do I receive Error -52005 when trying to use my PXI system from my Host computer?
http://digital.ni.com/public.nsf/allkb/AF06F7E46037E39586257A44006F5F1D

If this doesn't work, could you tell us more about the situation when this error occurs?

Thanks