LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

can't check FGPA reference with "Not a Number/Path/Refnum?"

Solved!
Go to solution

As a quick test before I tracked down an actual R Series card, I ran the code with the "Execute on Development with Simulated I/O" setting to simulate your hardware and I got the same behavior. I tried running with execution on the development machine with my cRIO, but ran in to errors regarding how execution on cRIO works (it's different than R Series, so to run these tests I have to actually execute on the RIO). The real test here will be how the test behaves with a real R Series set to execute on the FPGA.

 

Tim W.

Applications Engineering

National Instruments

http://www.ni.com/support 

0 Kudos
Message 11 of 16
(803 Views)

So I finally got a PCI-7831R in my machine to test this behavior. When the host VI is run and execution is set to go on the FPGA both dynamic and non-dynamic modes behave as expected and give false values for the boolean. However, when I switched execution to the development computer with simulated I/O, I got a false in dynamic mode and a true in non-dynamic mode. I think this behavior has something to do with the execution settings and may be a bug. We would both expect the reference to work the same way in simulated execution and actual FPGA execution. I'm going to file this with R&D and see what they have to say about it.

 

Tim W.

Applications Engineering

National Instruments

http://www.ni.com/support 

 

Message 12 of 16
(789 Views)
Solution
Accepted by nathand

This issue has been filed with R&D. The reference number for the corrective action request is 339079.

 

Tim W.

Applications Engineering

National Instruments

http://www.ni.com/support 

0 Kudos
Message 13 of 16
(786 Views)
Thanks for this. I'm out of the office for a few days but will double-check the behavior in LabVIEW 2009 when I get back, since that's what the lab systems are using. A coworker reported that the application I built in 2009 wasn't working properly and when I ran it on my machine (in simulation) I saw this behavior and assumed it was the problem on the real system with an FPGA. Adding a boolean to indicate if the FPGA was available solved the problem. Now you're telling me that in 2011 the behavior is different in simulation versus with a real card; I'll have to check if that's a change since 2009.
0 Kudos
Message 14 of 16
(781 Views)
Forgive me, as I havent read this whole thread. But would a possible work around be to typecast the reference to an int and check if its greater than 0?
0 Kudos
Message 15 of 16
(778 Views)
Haha last line of your post says my suggestion above. Doh!
0 Kudos
Message 16 of 16
(775 Views)