[DavidGitz]

Ah, sorry I thought they published it to the public after the Beta Testing was over. Here is the transcribed text:

Posted By Post
David Gitz Mentor for Team #1208
11/08/2011 8:28 PM
post6302
LV Probe Issue
Ok, this is kind of a weird one. We are noticing that the LV 2011 Probe doesn't always display data when it should.
Unfortunately I do not have a screenshot of this happening but I've attached a screenshot of the code that causes this.

What happens is that we have some code that builds an array in a while loop in Periodic Tasks. We have an indicator
that tells the size of the array. No matter what mode the robot is in (Autonomous/Telelp/Disabled) the array increments
in size, as it should and does this fine. However, when you probe the line going to the indicator the probe will say "
Not Executed" and will show a value of 0 (greyed out). However, it has worked once. The only verification of this
problem we've done is confirm that it happens to every wire in a loop in Periodic Tasks in this Project. We have not
checked this against any other vi's or Projects, or with LV 8.6

This is definitely not an issue of selecting the wrong indicator or something along those lines. The indicator clearly
increases and a probe on the wire going to the indicator indicates "Not Executed".

Any thoughts?
Attachment: Probe.png 248.52 KB
Associate QuoteReply
Greg McKaskle (NI Software)
11/10/2011 7:33 AM
post6321
Re: LV Probe Issue
Looks like a bug to me, most likely associated with the new parts of the optimizer. I'll show it to the lead on 2011 and
see if it has already been reported. Otherwise, he may ask for the code. Thanks for reporting.

Greg Mckaskle
Associate QuoteReply
Greg McKaskle (NI Software)
11/10/2011 2:23 PM
post6328
Re: LV Probe Issue
Would it be possible to email the code to me so that I can attach it to the bug report. My email is gam@ni.com.

Greg McKaskle
Associate QuoteReply
David Gitz Mentor for Team #1208
11/16/2011 10:26 AM
post6483
Re: LV Probe Issue
More evidence on this bug (attached)
The Probe Display had worked at one point (since it's not grayed out) but since then has not updated. The Drive Global
Variable (which includes the Gyro Angle) is on the right and indicates an angle of -24 degrees, which is continuously
updating. The probe hooked to the wire going into that Global Variable does not update.
Attachment: 1.png 209.08 KB
Associate QuoteReply
Doug Norman (NI Developer)
11/16/2011 12:11 PM
post6492
Re: LV Probe Issue
Did you ever send greg your code? Also, if you can distill this down to a very simple VI, it would be easier to debug.
Associate QuoteReply
David Gitz Mentor for Team #1208
11/16/2011 2:07 PM
post6495
Re: LV Probe Issue
I did, on Nov 12. Attached is what I emailed him. Also, I am unsure what you mean by "distill down to a very simple vi
", as all of the Periodic Tasks.vi is affected. Do you mean something along the lines of creating a new project, and
insert code in until we notice this issue again?

The problem with this approach is that so far this bug is intermittent and occurs throughout the Periodic Tasks, so as
we insert more and more code in the task of actually verifying if the issue occurs or not gets much more time consuming.
From my experience with LV, it doesn't matter how good/bad your code is, as long as it is running the probe should be
updated. And it is apparent that the code is at least running, so I don't see the issue as being our code. And
everything in our code works fine, and there are no significant error messages on the Diagnostics. But we will try.
Attachment: Mecanum Practice bot.zip 1.64 MB