I have a boolean NSV on a cRIO that now seems to be stuck in a True state. All Vi's on the cRIO are stopped, LV is closed on my development system and yet in the DSM I can try to set the variable to False and it will pop back to True. I do not (should not) have any bindings to this variable. It would be nice to be able to get a complete view of the internal state of a NSV engine to see if there is some weird cross linking or stray deployed variables. Has anyone seen a probem like this? BTW, I am running under LV 9.0f2