Simulation mode for PCI-5640R

[gregus]

Hi,

Here's what I tried so far (w/o success):

1. Clean reinstall of Labview on a clean Windows XP install (just running Labview in evaluation mode for now).

2. Various combinations of FPGA VI loaded /not loaded

3. Deleting Open FPGA VI Reference Node and reinserting it

4.  Just running a copy of ni5640R template code, which only runs the configuration loop on the FPGA Vi. 

Can someone please try running the ni5640R template code in simulation to see if this is really the problem?

thanks

greg

[Chris_W.]

Hi Greg,

I have been doing some tests as well and I am seeing the same issue that you are. I'm sorry for the inconvenience. I am currently looking into the issue that is causing the LabVIEW crash. I do have one question though, when you run the example VIs does LabVIEW crash, throw an error (specifically with the template), or does it just freeze up and go to a "Not Responding" state?

I found that the template VI just freezes LabVIEW but doesn't crash it, where the Analog Input example actually shut LabVIEW down totally, without an error message. What was your experience?

Chris W

[gregus]

Hi Chris,

ok, it's good you can reproduce the problem, but of course that's not great news in general. 

Regardless of the VI I run (i've tried ni6540R template, "analog input only", "analog input and output", "processing only")  I get a crash. I always get a dialog box "Labview 8.6 Development System has encountered an error and needs to close".  Error code is always the same, 0xC0000005, which is an illegal memory access, I believe. I never get into a state where I'd need to kill Labview because it is frozen.

Thanks for your help

Greg

[Chris_W.]

Hi Greg,

Thanks for the answers, I think I've tracked down where the problem is steming from but I am going to have to go through it with our R&D group on Monday to really figure out the root cause. I will post an update when I find an answer.  Thanks for being patient with this. For the time being, you could begin your FPGA code development and just run it alone (without the Host VI), and monitor the indicators so that you don't have to wait too long to begin your development/testing. Have a good weekend!

Chris W

[Chris_W.]

Hi Greg,

I have dug down to find that there is an issue with the way the driver is configured to run with simulated I/O. Unfortunately, there is not really much we can do to fix it right now. I have filed a corrective action request to have that issue fixed in the next driver release, but as for now, we basically don't have the option to simulate on the development computer. 

I am happy to try to help in any way I can if you are curious about anything along the way of your code development. Just let me know if I can help. Thanks for your patience, and again, I'm sorry that we cannot work around this right now. Have a good week.

Chris W