Hi
What you are seeing is a standard debugging feature provided by LabVIEW in conjuction with the NXT.
If you are using LabVIEW you must be using the NXT Terminal to download and run the program. You are probably pressing the left hand icon on the terminal to run the program.
Instead, if you press the third icon over (Arrow pointing to lightbulb) it will compile and download the program and then maintain a connection with the running program for debugging purposes. Any LabVIEW display elements that you have included in your NXT program will now operate and be visible on the PC's normally-empty front panel. (This is one of the main reasons I planned to use LabVIEW.... it's a powerfull debugging tool).
There are (of course) the usual caveats: It slows down your program a bit, and it only updates at the bandwidth available by your link to the NXT.
For bench testing this program, I don't need the Bluetooth link, so I connect to the NXT with USB. It provides a pretty good debug window.
For robot testing (on the bench), you can download and debug via USB, while the Bluetooth is used by the Controller program.
I haven't found a way to debug while driving on the field yet
Try this yourself by LEFT-clicking on any wire and selecting "Create - Indicator".
The indicator will be added to both the block diagram and the Front panel.
Change it to any graphical type you like.
When you start debugging, there is a several second delay before the Front panel starts updating... so be patient.
Note: I've attached the LV program that shows the bad encoder resets.
Download (debug) it using the method I expalined and just let it tun.
Phil