LabVIEW is a data flow language, so the loop to the top right will not get executed until the previous loop, which it is connected to by the error cluster wire, finishes, which it only does on an error, which (not looking at the diagram right now, so I have forgotten) may cause the "second loop" to not execute. The display loop, a timed loop set to 1000Hz, or an update rate of 1 mS, will update the display. Writing to a local variable is like writing to the actual indicator connection. So, even if the second loop is running, the bottom loop overrides it. Try putting the data in the bottom loop on a shift register, then run a case statement off of a timer that "samples" the shift register and is connected to the display terminal, eliminating the second top loop and all writes to the local variable.
PutnamCertified LabVIEW Developer
Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5
LabVIEW Champion