There is loop reading Lakeshore temperature
@Bob_Schor wrote:
When timing is important, you need to avoid the Windows "clocks" and rely on hardware timing. Sounds like you might be using the two (two? as in "more than one"?) Event Loops as part of your timing apparatus, which sounds very problematic. What hardware are you using? Anything that could avoid Windows, like a LabVIEW RealTime RIO or PXI system (where the LabVIEW code has the priority, not the OS, Virus scanners, etc.).
Really looking forward to knowing more about your hardware, your "task", a simple task with controls and timing for us to see (and, I hope, improve).
Bob Schor
Thanks to Bob.
There is a loop reading temperatures from LakeShore Temperature Controller through TCP/IP which is inside the timeout event case and some instrument settings are in other event cases. There is other event loop handling user operations. The third while loop keeps fast reading magnetic fields from a box through TCP/IP. This field reading is actually made by calling a DLL file. Now we observed if this LabVIEW program window keeps in the front of desktop, the field reading is just fine catching the real field in the magnet (The magnet field is continuously sweeping). Once this LabVIEW program window is minimized on the taskbar for a while, and then taken back to the front of the desktop, the field readings is far away from the current real field in the magnet. It will take a moment to for the reading to catch the real field.
We also double checked the same program in a win 10 PC with LabVIEW 2019 32bit installed without any additional configurations. It runs just fine regardless of whether this window is minimized.
Best,
WT
