Re: Passing data from subvi's several levles down to top level vi
Is 100 msec too slow? I have loops that update the indicators this fast.
Re: Passing data from subvi's several levles down to top level vi
I have used a completely different approach to solve this problem: 1) Create a vi that is nothing more than the indicator. Show and position this indicator as part of the main user panel. Use FP.PanelBounds and FP.Origin property nodes to control size and position. Also activate the =91show front panel when loaded=92, deactivate =91close afterwards=92, =91title bar=92 and all other show options besides panel related from the window-appearance vi properties. 2) Call this vi from anywhere in the program to update the display data. I typically create programs whose main panel is comprised of the front panels of 4-8 vis. In effect it=92s a displayable global with code capability. I use this method to create indicators that display all my measurement instruments readings giving the user one place for all current measurements regardless of the instrument taking the measurement.
Re: Is anyone aware of a timing problem when using Notifiers ?
Try setting the 'ignore previous(F)' flag to true.
Re: Matrox frame grabber & LabVIEW
I also use ActiveMIL. I have found it better to turn off automatic allocation to all controls and programatically allocate them. This has the benefit of giving you greater control to troubleshoot and process errors or resets of the video system. I use allocate methods to allocate each control and the free methods to disallocate (free) them when an error occurs or a reset is issued. My systems are completely stable. I would recommend that you don=92t use grabcontinuous. Synchronize the video to your program by calling grabs as you need them. I typically have a video processing vi that runs independent of my test executor and all other vis and use notifiers to publish the video data of interest. I typically grab images at 60 msec rate with a 40% CPU usage on a 1 GHz processor. This gives me every other frame from the camera, fast enough for all my applications and leaves me 60% CPU for other procesing.