Scan Engine & EtherCAT Custom Device Feedback

[StephenB]

Hi Arnold,

You cannot use two different bit files for the same device. You must reference the same bitfile in both the XNET port settings and under Hardware -> Chassis -> FPGA.

Simply update your project with your FPGA code to have a 9862 in the desired slot and recompile. Then use that FPGA bitfile.

Take care,

[StephenB]

Usman,

I've built and attached the 2014 beta version of the custom device. This was built with release candidate labview 2014, and beta versions of NIVS and all the drivers.

[Hissi]

Stephen,

thank you for your fast answer. I have already tried to apply the same bitfile. But when I use the bitfile for the FPGA target und des XNET 986x Support I get following error:

Error code: -61200

Error Message: LabVIEW FPGA: The operation could not be performed because the FPGA is busy operating in FPGA Interface C API mode. Stop all activities on the FPGA before requesting this operation.

How can I handle this error / problem?

Thanks,

Arnold

[StephenB]

That error happens when you try to load two different bitfiles to the same fpga target. Are you absolutely sure you are using the exact same bitfile from each place in your system definition?

[Hissi]

Now I created a new LabView Veristand Project und compiled it, imported these files to a new VeriStand project, to ensure that I use the same file. It seems that I have selected unfortunately two different bitfiles.

Now I get following error:

The VeriStand Gateway encountered an error while deploying the system Defintion file.

Details:

Error 66 occurred at Project Window.lvlib:project Window.vi >> Project Window.lvlib:Command Loop.vi >> NI_VS Workspace ExecutionAPI.lvlib:NI Veristand Connect to System.vi

Possible reason(s):

LabView: The network connection was closed by the peer. If you are using the Open VI Reference function on a remote VI Server connection, verify that the machine is allowed access by selecting Tools >> Options >> VI Server on the server side.

But this error only appears when I use the bitfile twice (FPGA target and 986x support). Testing the FPGA target and the XNET port seprately it works.

[StephenB]

ah ok. Your cRIO target is crashing. This is because of a bug in XNET 1.8. I don't remember if they have a fix or if the only fix is to revert to xnet 1.7. If you call support they will be able to help you

[TylerJ]

Devin,

I have been using the scan engine for over a year, and recently when I deploy my project, it gives me error 537700

Error 537700 occurred at Project Window.lvlib:Project Window.vi >> Project Window.lvlib:Command Loop.vi >> NI_VS Workspace ExecutionAPI.lvlib:NI VeriStand - Connect to System.vi

It happens randomly, and sometimes it will go away if I restart the PXI Chassis.  I've also tried deleting the scan engine custom device off the PXI Chassis, then letting it re-download it when it deploys.  Sometimes that will work.  At this point I'm just sick of messing with it and am looking for a lasting solution.  I've looked through this forum and it seems to be a known issue, but I've tried a few things and nothing has worked so far. 

Thanks.

[UsmanKhan]

Hi Stephen,

When I use the Scan Engine that you compiled for VeriStand 14 beta, I get the following error when I try to add it in the system def

Possible reason(s):

LabVIEW:  File version is later than the current LabVIEW version.

An error occurred loading VI 'Scan Engine Custom Device.lvlib:Scan Engine Initialization VI.vi'.
LabVIEW load error code 9: VI version (14.0) is newer than LabVIEW version (14.0b86).

[StephenB]

Well crud. That means the LabVIEW version I used was after the beta period ended. Sorry about that, I didn't realize this.

I have to remake an entirely new virtual machine and reinstall old versions and build again... would take me all day. As NIVS 2014 isn't too far away... how important is this? Alternatively I could find a way to get you a version of NIVS 2014 that isn't tied to the LabVIEW 2014 beta but rather tied to 2014 release.

Thanks for your patience.

[UsmanKhan]

Sure that would work for me. Are you going to send me a link to download that version of NIVS?