Probes (and some other aspects) not working

[Joe Ross]

Originally Posted by JohnGilb

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."

I think that's another hint that the problem isn't that the probes aren't working, but that your code really is only executing once.

[JohnGilb]

I'll double-check tonight, but I'm fairly certain the code is executing. It's responsible for moving the robot around, and the robot actually does move around. I tried putting probes just before the "Motor -> Set Output" and got "Not Executed."

One way or another, I'll have more information in a few hours.

[JohnGilb]

One other note -

After noticing this behavior, I tried to change my debugging strategy. I placed breakpoints on various blocks (some .vi's, some just basic blocks) in the code. When the breakpoints were hit, I probed the wires, and saw "Not Executed."

If you break on a block, shouldn't the wires that are attached to the inputs of that block be available for probe?

Thanks in advance.

[JohnGilb]

All right, the project is attached. Here is the (in)consistent repro:

1) Download the code to the robot
2) Without enabling the robot (you can enable it, this just saves you a step), just go to Robot Main --> Periodic Tasks --> Mobility System.vi
3) Put some probes around. Nearly all of them say "Not Executed."

One curious example is the Gyro1, which is updating the front panel, but shows "Not Excuted" on the wire going into it on the Block Diagram.

Any red flags in our code that would explain this strange failure?

[JohnGilb]

Is there any sort of logging that LabVIEW does that I can package up (or would something like a memory dump be helpful?)