The GUI timers will only work one at a time cause in this mode they will execute when they get time to do so.
Just a comment, in terms of your aquisition speed I would be really concerned about processor overhead logging and displaying data at such a high rate. Dependeing on the hardware and the specifiec capabilities it might be really tough to pull of.
In terms of simultaniously processing some events and data logging I would normally rather use the asynchronous timer that runns in seperate threats.
Running your code is the way it's done now you will have to wait for 150-500 seconds for that function to finish before it will process the timers again.
If the process f_startBalance_measurements() takes so long to run it might even have an affect on a v
ery fast aquisition process running in a seperate threat.
Jattie van der Linde
Engineering Manager, Software & Automation
TEL Magnetic Solutions Ltd