LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why would an uninitialized shift register (bool) revert to false without close or init?

Looking for some help here....

I have an uninitialized shift register that keeps track of first call of the VI. I use this to do init steps before running the VI. The shift register is then set to true and not touched until the close case is called (where it is set to false). For some reason, the shift register will go false without provocation. I've probed the wire going into the right side of the shift register and that is always true. Suddenly the left side becomes false. What else could set this back to default? The VI doesn't get closed out of memory because I would see the probes go away, right? How else could it be set back to false?

Any help would be appreciated...

Thanks,
Tim
0 Kudos
Message 1 of 8
(3,331 Views)
Please attach some code that shows the problem.
  1. Do you have a TRUE diagram constant directly wired to the right shift register or is there some code?
  2. Are there any partially wired output tunnels set to use default if unwired?
  3. Are you editing the subVI, causing a recompile?
  4. Is the subVI set to reentrant by mistake?
  5. What is your LabVIEW version?

Message Edited by altenbach on 07-12-2007 01:35 PM

0 Kudos
Message 2 of 8
(3,317 Views)
Here is the VI in question....Thanks. You might need my control that goes with it. I included it too.
0 Kudos
Message 3 of 8
(3,310 Views)
Where? 😉
0 Kudos
Message 4 of 8
(3,310 Views)
how do you attach on this forum? I selected the files, but nothing came up.....sorry, I've never attached a file here
0 Kudos
Message 5 of 8
(3,301 Views)
Below the form is a browse button where you select the attachment. After selecting, press "submit post". I think if you would do another "preview post", the attachment gets dropped and needs to be redone.
0 Kudos
Message 6 of 8
(3,280 Views)
That would explain it. Sorry for the delay.
Download All
0 Kudos
Message 7 of 8
(3,271 Views)
I am looking at your code, but I can't see the problem. Explain exactly what you do with this VI to cause the problem. Also can you create a version that demonstrates the problem without all the drivers in it? As it is I can't actually run it.

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 8 of 8
(3,262 Views)