LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Diagram disable structure not really disabling?

I have a VI in which I had put a diagram disable structure (not the conditional one) around a section of code containing the Time Delay VI (this is the only place where I have the Time Delay VI). I built an executable containing this VI. When I start the executable I get an error that esssentially says it can't find the Time Delay VI. I removed the diagram disable structure (and the code inside it) and I no longer get the error. I thought the code inside the diagram disable structure wasn't supposed to get compiled. Right?
 
George
0 Kudos
Message 1 of 8
(3,740 Views)
I just made a test built with a diagram disable structure containing an odd subVI in the disabled case and cannot reproduce this error. Are you sure that the relevant case is set to disabled?
 
Can you attach a simple VI that shows the problem?
0 Kudos
Message 2 of 8
(3,732 Views)

Yes I'm sure that the relevant case is set to disabled. That was the first thing I checked. This is the first time it's happened to me. I've had no trouble other times that I've had disable structures in an executable. It might take me awhile to pare my VI down. Lots going on right now. Just thought I'd see if anyone else has run into this.

George

0 Kudos
Message 3 of 8
(3,730 Views)
(Just as an additional note, I was testing under 8.0.1. I don't know if it makes a difference.)
0 Kudos
Message 4 of 8
(3,723 Views)
(Just as an additional note, I was testing under 8.0.1. I don't know if it makes a difference.)
 
Me too.
 
George
0 Kudos
Message 5 of 8
(3,719 Views)
I've verified this with the Time Delay and Simulate Signal Express VIs, so my first guess is that this is true for all Express VIs. I tested it out with a custom reentrant subVI and had no problems, so reentrancy isn't the issue. I'll do some more testing and report this to R&D as soon as I've narrowed it down to one particular situation. Thanks for pointing this out!

Jarrod S.
National Instruments
0 Kudos
Message 6 of 8
(3,692 Views)
This has been reported to R&D (# 3XAB0FV2) for further investigation. A possible workaround is to ignore the missing items (they shouldn't be needed in the executable, but I understand the inconvenience). You can also convert the disabled Express VI into a normal subVI by opening its front panel. That resolves the issue. Or you could delete the disabled code. Thanks for the feedback!

Jarrod S.
National Instruments
Message 7 of 8
(3,687 Views)

It does work to just ignore the error. It was just confusing for awhile. At least I know now that it's a bug. Thanks.

George

0 Kudos
Message 8 of 8
(3,681 Views)