High-Speed Digitizers

cancel
Showing results for 
Search instead for 
Did you mean: 

Simulate PXIe-5170 on Labview 2020 Windows


Hello,
I have been working on getting the Multirecord Acquisition (NI 5170) template project working on Labview 2020 where it works fine on Labview 2015.

 

This is a continuation of my efforts in Simulate PXIe5170R on Windows Desktop. In that thread, I successfully got the simulation working on Labview 2015.

 

I have been unable to get the same VI working in Labview 2020. I run "Configured Acquisition (Host).vi" and end up with this error:

 

  • Error -63195 occurred at _nirio_device_attrGet32.vi:7370001 -- Possible reason(s) the handle for device communication is invalid or has been closed. Restart the application.

Obviously I tried restarting Labview and my computer but no change.

 

For some detail, I installed Labview 20.0.1f1 (32-bit) on a different Windows 10 PC than

the one with Labview 2015, and installed the Real-Time Module, and the 5170 Instrument Design Libraries using NI Package Manager.

 

Thinking that maybe the problem was that the 2015 template project (or my edits) no longer worked in 2020, I started over by creating a new default project in Labview 2020 (i.e., from the main menu: Create Project -> Sample Projects -> Oscilloscopes -> Multirecord Acquisition (NI 5170).

 

Same error result. I followed all the steps from the prior thread including building the FPGA bitfile and setting Simulation Mode for execution.

 

I tried debugging a little bit and here is where I got. I called my project "mpol8".
In "mpol8 Configured Acquisition (Host).vi", an error occurs in "mpol8 Device Session.lvclass:Open Session", shown below since probe [1] has no error, and probe [2] has an error.

 

Error in Configured Acquisition (Host).viError in Configured Acquisition (Host).vi

 

Within this VI (mpol8 Device Session.lvclass:Open Session.vi), an error occurs between probes [11] and [12], placed before and after "niHSAI Group A Config v1 Host.lvclass:Open Session.vi". I stopped debugging from here since it seems like I'm getting pretty deep. See below with some minor annotation:

 

Screenshot 2022-01-28 092217.png

 

I do notice that there are some type-coercion dots in the Open Session VI and I'm wondering if those are some factor in what's happening.

 

All of the code produced by the project template should be the default -- I tried not to change anything except setting the "Open Session" VI to non-reentrant, only for the purpose of getting a debug probe.

 

Thanks for any assistance in getting this example running.

0 Kudos
Message 1 of 1
(1,910 Views)