Losing data along wire when not in Highlight Execution

[mcduff · Accepted solution]

---

@Kevin_Price

 I *think* I have an old, vague memory of encountering a similar puzzling situation with a DAQmx task probe that showed content in some probe locations but not others.  Unfortunately, I have no recollection whatsoever of how that situation resolved itself.  It just makes me inclined to consider the possibility that a DAQmx task refnum can behave a little different than common data wires like numbers, strings, and booleans.

---

I am pretty sure that I have seen this also when debugging. Try adding something like this to your initialize, it worked for me in my application, have not tested yours.

mcduff

[crossrulz]

---

@GammageATX wrote:

Unfortunately, I can't seem to make this strategy work to pass along the reference for the Get and Exit cases.

---

That is because the local variable is a race condition.  It is very likely read before the control is updated.  So you are really just reading the value from the previous run of this VI.

[GammageATX]

---

@mcduff wrote:

---

@Kevin_Price

 I *think* I have an old, vague memory of encountering a similar puzzling situation with a DAQmx task probe that showed content in some probe locations but not others.  Unfortunately, I have no recollection whatsoever of how that situation resolved itself.  It just makes me inclined to consider the possibility that a DAQmx task refnum can behave a little different than common data wires like numbers, strings, and booleans.

---

I am pretty sure that I have seen this also when debugging. Try adding something like this to your initialize, it worked for me in my application, have not tested yours.

mcduff

This fixed it! I guess without a name the task didn't leave the loop for some reason.