LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

grayed out probe. "no debug info"

Solved!
Go to solution

Hi, Everyone:

 

I have a strange problem where I put a probe on a (double) wire and it is grayed out and says "no debug info".  When the data goes through the probe (in highlight execution mode you can see the dot go right through it - sometimes) it says "not executed".  This doesn't seem to be cosmetic, either.  It causes calculation errors downstream.  Does this sound like a corrupt VI?  It's not set to "re-entrant" and probes I put elsewhere seem to be "normal".  It's just that wire...

 

Edit:

I forgot, when we probed the same wire in another state, it contained error info???  (Wire still looked like a double.)

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 1 of 5
(2,320 Views)

Is there anything else that is not default about that VI? Running in-lined or with special priority?

0 Kudos
Message 2 of 5
(2,311 Views)

Have you tried clearing your compiled cache?



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
0 Kudos
Message 3 of 5
(2,293 Views)

Is that probe inside a parallel FOR loop?

 

(You cannot probe inside a parallel FOR loop unless you temporarily change the options for it, forcing sequential execution)

 

altenbach_0-1652207664802.png

 

0 Kudos
Message 4 of 5
(2,279 Views)
Solution
Accepted by topic author billko

Hi, Everyone:

 

Sorry it took so long to get back to you all.  I should've remembered to clear the cache, that may have solved things.  SO anyway, we did the tried and true snippet to new VI and it worked.  (It appeared that all the previous versions had the same issue, but it could've been corrupt cache.)

 

Oh, well.  Since we have versioned it in GIT, I can just go one rev back, clear the cache, then see if that works.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 5 of 5
(2,241 Views)