More specifically, it consists of 3 image displays, 4 waveforms and a bunch of buttons and numeric indicators.
The more elements I added, the more laggy the GUI got, which is especially visible in the camera image which is updating at ~ 2 Hz instead of 20 Hz.
I'd like to know if it is possible to somehow have this loop inside my sub VI and have the sub VI sending one of the output parameters after each iteration.
If you look at the Lab VIEW help for the terms in bold you'll find documentation and examples for how to use them.
By using DIM, Lab VIEW and EPICS applications can be linked together.
The Lab VIEW DIM interface is provided on THIS web-site.
Because my robot’s control system runs on a Lab VIEW real-time machine, I have no recourse but to add new features in Lab VIEW.
The GUI is built as a queued message handler and I included a message which sets "Defer Panel Updates" to true before the "Update GUI" message and another one afterwards that sets "Defer Panel Updates" to false (see attachement).
Otherwise, stick to the current, stable version 1.7.
This project started life as an article for Microsoft's Coding4Fun website.
DIM is a communication system for distributed / mixed environments, it provides a network transparent inter-process communication layer based on TCP/IP. Basically, our Lab VIEW interface is just a wrapper around the "dim.dll" which is part of the official DIM distribution maintained by Clara Gaspar (thanks a lot! This means, that the DIM functionality itself is encapsulated within the "dim.dll".
DIM has been developed at CERN and is available for VMS, Unix, Linux, Windows, OS9, Lynx OS and Vx Works. The Lab VIEW DIM interface does not re-implement DIM.