09-02-2016 04:02 PM
Thanks for that explanaition RavensFan. Sorry if it seemed like I wasn't taking the advice, but I did not know about the different behaivors at run time based on wether the terminal is connected or not.
I understand the underlying code is not ideal, but when it was functional in one state, but not the other it didn't make sense (in my head)
09-02-2016 04:07 PM
I hope the explanation helps. I couldn't see the full extent of the problem until I had the full code and could run it. The original message and just he subVI showed me local variable problems and code logic that looked like it never changed because the other subVI controls weren't wired. So all I could concentrate on was that.
Seeing the execution and seeing the other cases run despite unchanging controls helped me remember the existence of that other thread. I can't claim I completely understand that thread. But it is one more point that tells me excess local variables lead to problems.