Losing data along wire when not in Highlight Execution

[Mancho00]

I don't have LV2018, but last I checked, you can't put two probe points on the same wire.  Anyone have a clue what's happening here?

[paul.r]

Good catch - unless this has changed in LV2018 (why would it) it looks like you have two wires overlapping. 

---

@Mancho00 wrote:

I don't have LV2018, but last I checked, you can't put two probe points on the same wire.  Anyone have a clue what's happening here?

---

[GammageATX]

I don't think I do? I've attached a version that's even cleaner and showing the same problem.

[RavensFan]

Something is pointing to a wiring problem with the double probe.  When I open your VI, I don't see an extra wire that could cause a double probe.

Use Block Diagram Cleanup tool on your diagram.  If there are overlapping tunnels or wires, they should jump out.

There is no need for a separate tunnel to exit the while loop to go to the indicator.  Just use the output of the shift register.

[paul.r]

Can you save for a prior version?

[Mark_Yedinak]

Just for clarity, place a probe on the Action wire as well.

[billko]

I think the probe thing is a red herring.  In fact, it's not even incorrect.  I believe wires are different across structure boundaries, since the values could be different from one side to the other.  (Tunnels/SRs.)

Try triple-clicking a wire to see if you can select anything "on the other side" of a boundary and you'll see what I mean.

[paul.r]

---

@billko wrote:

I think the probe thing is a red herring.  In fact, it's not even incorrect.  I believe wires are different across structure boundaries, since the values could be different from one side to the other.  (Tunnels/SRs.)

Try double-clicking a wire to see if you can select anything "on the other side" of a boundary and you'll see what I mean.

---

I believe you're looking at the wrong image - the one on the prior page (post 10) shows two probes on what appears to be the same wire.

[RavensFan]

They are referring to the picture in message #10 where probes 2 and 4 "appear" to be on the same wire in the same structure, i.e. between the case structure and the while loop.

[paul.r]

In either case, unless its a duplicate wire, as others have said it is most likely a race condition. In whatever case you are passing out the default value, replace that with a 'test' string constant, and put a breakpoint in that case. I would bet it is being called from somewhere you aren't expecting.