LV 2010 probes lie in RT (yes they executed)

[Ben]

I don't have the code and could not share it if I did but I share to give you a heads-up and maybe someone else could confirm.

In LV 2010 when trouble shooting a RT app, some of the probes said "not executed". OTher probes that were "down stream" did show an update.

So botton line is...

If the probe say not executed but you have data down-stream the probe is lying.

You have been warned,

Ben

[Ben · Accepted solution]

Known problem (apparently).

CAR = 255014

as per Grant on SR# 1610031

Work-around said re-boot the RT but I did not try that.

Ben

[PsyCrow]

I have seen this problem too in LV2011, even in probes for a constant value, some times the probe shows a wrong value, some times shows a value that changes!

I had being uninstall and install LabView but it still happens.

Anybody knows a workaround?

[Michael_78]

I reported this to r&d but after some weeks gave up due to them not being able to
replicate the problem. It would be great if you have code where this problem is repeatable you contact r&d
Thanks
Michael

[Ben]

You can use the SR# (Service Request Number) I reported above and ask support about the status of the CAR. If there is a work-around, it would be documented with the CAR. Support may also be able to speak to the status of the CAR.

Keep wiring but don't trust those probes,

Ben

[timtamslam]

Howdy all,

This issue was indeed addressed in the 2011 release of LabVIEW. If you look through the list of LabVIEW 2011 Bug Fixes you'll find that the CAR# 255014 Ben is referencing has been fixed. As for experiencing this in LV2011... you may want to check and make sure you're drivers are up to date. And like what RiversDaddy said, you'll definitely want to have code that can create reproducable errors.  

[PsyCrow]

I installed LV2011 from de DVD set that NI sended me, and then patched it with the f2 patch from http://joule.ni.com/nidu/cds/view/p/id/2657
How can I verify the version of the drivers to check if they are up to date?

I'm puting the backups of the code that I'm testing.

FPGA_Bkp2011Dic03.rar is the FPGA part

cRIO_ACE1_EREG.zip is the cRIO part (that has the bug)

[timtamslam]

Here's a document on how to check driver versions: http://digital.ni.com/public.nsf/allkb/2266B58A5061E86A8625758C007A4FE3

I also like navigating to Help>System Information, In Measurement & Automation Explorer. 

There's a good chance that if you used the DVD that came with your hardware, you'll have the correct drivers. Here's a list of the drivers that are needed with cRIO systems. 

http://www.ni.com/gettingstarted/installsoftware/compactrio.htm

I would confirm that you have these and that they are the highest versions. You can check current versions at ni.com/drivers

[PsyCrow]

Thanks Tim-A,

Now I check the versions, and I have NI-RIO 4.0.0 (the correct version I guess) in both, PC and cRIO

I hope someone can reproduce the error with the code that I have posted earlier.

I will glad listening your comments.

[BuddyHaun]

I don't know if it applies in your case but I had a lot of problems with both probes and debug highlighting an RT system when I was using a wireless network. The cRIO was hardwired into the network and I was developing on a laptop with a wireless connection. The network was not loaded but the latency seemed to throw a real curve into process. I switched to a hardwired port on my laptop and the problem went away.