Probes (and some other aspects) not working
 

I'm experiencing an intermittent and annoying issue.

For some reason, in some (not all) of my VIs, the debugging probes list "Not Executed." I am certain that the VI itself is running, since in particular my drive code is having this problem and the robot is still mobile.

In addition, some of these VI's have the task of updating some global variables. If the VI goes from a working state into this "Not Executed" state, it appears to stop updating the global variable, and code that reads from that variable finds stale (unchanging) values.

In some cases, this problem only applies to _some_ of the code in a VI. In my drive code, I have two main loops. One loop reads from globals and sets motor outputs, and the other loop reads from gyros/encoders and publishes that to a local variable. Everything in the drive loop shows "Not Executed", but in my sensor loop one of my encoders has a reliable probe, even though all the other encoders/gyros show "Not Executed."

The best reference I found online was a list of things that were fixed in LV 2011:
ID, Legacy ID, Fixed Issue
255014, —, Probes are listed as Not Executed intermittently on Real-Time target

This is especially painful, since one of the things I like about LabVIEW is the debugging =[

Any idea what this is?

Re: Probes (and some other aspects) not working
 

Debugging can be turned off in a VI, and marking a VI as reentrant also impacts which debugging features are available and how they work.

From your description, I can't be sure if these are involved.

Try putting another indication, such as a display on the panel, and update it from the same wire as the probe. If neither one updates, work your way back to see if logic is truly preventing the code from running. If the indicator updates and probe does not, then it truly sounds like a bug in the way the probe is implemented.

Greg McKaskle

Re: Probes (and some other aspects) not working
 

Can you post a picture of your diagram code? I'm going to guess something is keeping that code from running.

Re: Probes (and some other aspects) not working
 

Hello Everyone,
This year we are getting our Kit late because of some issues with customs. Because of that, we are spending some much time with thinking and will practice on last year's robot. In order to practice, we do need Labview but our labview has been expired. What else can we do to find labview. Is there any link that you can give us to download ?

Re: Probes (and some other aspects) not working
 

greetings,
Labview is in your kit,hopefully. It is a package that looks like it should hold a CD. When you open it, you will find a credit card size device that is a USB drive. That contains Labview.

Re: Probes (and some other aspects) not working
 

They do not have their Kit, so they are looking for a temporary stop-gap solution.

Re: Probes (and some other aspects) not working
 

Failed at reading comprehension there, sorry.

You can get the updates online and you can get a regular version of Labview as well, but you cannot get the FRC version of it online as far as I can find. I've been looking because i MIGHT have misplaced my copy. Those cards thingies are cool but way to easy to put then in a pocket and forget where it went...

Re: Probes (and some other aspects) not working
 

Has anyone tried applying the downloaded FRC update onto a standard 2011 Labview?

If this worked it could be a stop-gap.
There's probably an eval version of 2011 available.

Just wondering...

Re: Probes (and some other aspects) not working
 

My experience is that "Not Executed.... means "Not Excecuted since you created the Watch Window."

eg: If you run the program and then put a watch window inside the BEGIN Vi, it will say Not Executed. However, if you then stop the program, and re-run it again, you will see the existing watch window update.

If you have a watch window in the Teleop VI, and you are driving the robot, I'd certainly expect it to display data. Do you have any Case Structures (for optional driving code). Perhaps these are not running as you expect.

Re: Probes (and some other aspects) not working
 

We encountered this bug during Beta Testing and still notice it from time to time. See the thread here: http://firstforge.wpi.edu/sf/discuss...468?_pagenum=1

We mainly use Global Variables that are written in the Teleop/Autonomous.vi's and used in Periodic Tasks, so instead of using the Probes we just open the corresponding Global instead and it works fine.

Re: Probes (and some other aspects) not working
 

I get "The page you requested cannot be found." Can you copy over any relevant information from that page?

Re: Probes (and some other aspects) not working
 

Also, I don't have access to the code now, but I can try and find the smallest diagram where this issue is occurring so you all can try some visual debugging =]

Re: Probes (and some other aspects) not working
 

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

Re: Probes (and some other aspects) not working
 

Sorry, I did not read your post carefully enough. If your Globals themselves are not updating, I doubt it is a problem with the Probe but instead is in your code. Probe/open up the Drive (and any other applicable WPI Library) functions and see if you are getting Errors in the Error Cluster. Also, make sure to check the Diagnostics Panel on the Driver Station for errors and post back here what you find please.

Re: Probes (and some other aspects) not working
 

Ah, there is one more thing I failed to mention.

If you turn on "Retain Wire Values" before running the VI, then everything appears to work perfectly (all probes work). However, if you start with "Retain Wire Values" off and then turn it on during execution, you still see "Not Executed."