LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Challege - Unbreak this VI

Solved!
Go to solution

While editing some VIs, my fingers slipped and I entered a back door into a place where I wasn't supposed to be.

So of course I had to poke around.  And I discovered a way to break a global VI.

The challenge is:

  1. Figure out why the VI is broken.

  2. Fix the VI.

 

0 Kudos
Message 1 of 13
(3,108 Views)

1. ??? Gloabal memory usage seems a bit off. ???

2. Does the attached work?

 

-AK2DM

 

 

~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~
0 Kudos
Message 2 of 13
(3,062 Views)

1. You're on the right track,  The broken VI has something extra.

2. You didn't fix the broken on, you just built a new one.

 

From now on, use the VI attached to this post rather than the original (It will be easier to tell if a 'repaired' VI is from the one provided).

0 Kudos
Message 3 of 13
(3,048 Views)

Somehow you managed to put a label and a Not primitive on the BD.

 

-AK2DM

~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~
0 Kudos
Message 4 of 13
(3,035 Views)

@AnalogKid2DigitalMan wrote:

Somehow you managed to put a label and a Not primitive on the BD.


Well, I was going to say that the unwired not primitive on the BD which shouldn't exist is probably not helping things, but it looks like you beat me to it...

 

P.S. And yes, I did leave that comment there.


___________________
Try to take over the world!
0 Kudos
Message 5 of 13
(3,029 Views)

It was here, not there, within the comment 🙂

 

I can't figure out how to fix it, I have to go measure some micron-level stuff for now.

 

-AK2DM

~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~
0 Kudos
Message 6 of 13
(3,023 Views)
Solution
Accepted by paul_a_cardinale

@AnalogKid2DigitalMan wrote:

I can't figure out how to fix it


By deleting the unwired not, like so.


___________________
Try to take over the world!
0 Kudos
Message 7 of 13
(3,017 Views)

My path to the BD was:

1. Drop the global onto a Static VI reference.

2. Hold down Ctrl while double-clicking that reference.

 

Is that how you got in?

 

0 Kudos
Message 8 of 13
(3,006 Views)

@paul_a_cardinale wrote:

My path to the BD was:

1. Drop the global onto a Static VI reference.

2. Hold down Ctrl while double-clicking that reference.

 

Is that how you got in?


No. While someone once showed me that method, which he stumbled upon accidentally, I didn't remember it. I used the heap peek window.


___________________
Try to take over the world!
0 Kudos
Message 9 of 13
(3,000 Views)

I created a beta bug for this behavior. I'm not sure if NI will actually do something about it, because it's a corner case, but now it's up to them.


___________________
Try to take over the world!
0 Kudos
Message 10 of 13
(2,960 Views)