LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Broken Wire but Runnable. Should I be concerned?

How concerned should I be if I have a few VIs where the run arrow is not broken, but a wire regularly shows up as broken?

 

_carl_0-1695745924748.png

 

If I replace the wire, it's non-broken again.  But when I come back to this VI later (perhaps after recompile), the wire's broken again -- even though all code runs.  I've seen this in a few places -- and yes, the VI on the right is a malleable VI.

 

LV 23, Q1, 64-bit.

 

0 Kudos
Message 1 of 5
(533 Views)

I've seen this a few times with malleable VIs in LV 2020, I thought it had been fixed.

Most times, the Vi is fine and the display is wrong, all you need is a recompile.


We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

0 Kudos
Message 2 of 5
(479 Views)

I'd be worried about that unbundle though 😊.

 

.vims cause all combinations, broken wires\running VI, good wires\broken VI, broken wires\broken VI...

0 Kudos
Message 3 of 5
(428 Views)

wiebe@CARYA wrote:

I'd be worried about that unbundle though 😊.

 

.vims cause all combinations, broken wires\running VI, good wires\broken VI, broken wires\broken VI...


That's the coolest unbundle I've ever seen.  How do you do that?

0 Kudos
Message 4 of 5
(396 Views)

@paul_a_cardinale wrote:

wiebe@CARYA wrote:

I'd be worried about that unbundle though 😊.

 

.vims cause all combinations, broken wires\running VI, good wires\broken VI, broken wires\broken VI...


That's the coolest unbundle I've ever seen.  How do you do that?


I assumed the image was obfuscated by the user (e.g. in paint).

0 Kudos
Message 5 of 5
(387 Views)