Need to get rid of flicker in between image displays--the PC in which LabVIEW 8.2 is installed is routing images via LaVIEW code & 'extended desktop' to typical visual projector and between each image display is a flicker--that we need to remove

[Rongo324]

Need to get rid of flicker in between image displays--the PC on which LabVIEW 8.2 is installed is routing images via LabVIEW code & 'extended desktop' to a typical visual projector and between each image display is a flicker--that we need to remove

[johnsold]

How are you running this program? Is there a top level vi which calls the ones you posted? The Display image on screen.vi will display two images in succession, but according to the note on the block diagram the second image is blank. It seems as though this would intentionally create a flicker.

The sequence structure is unnecessary. Dataflow will determine the order of execution. The only exception is the time delay in the third frame. Since it has no data dependency, a single frame sequence may be useful to assure that the delay occurs before the picture is updated. A simple state machine might be a more versatile architecture for what you may be trying to do.

It is not necessary to write the FR.PanelBounds property immediately after reading it, nor is it necessary to read it a second time in the second frame. Just wire from the first read.

Lynn

[Rongo324]

In response to below------Thank you Lynn-----Yes, there is a main panel--I will attach----and if you have any further suggestions please let me know--Thanks again

How are you running this program? Is there a top level vi which calls the ones you posted? The Display image on screen.vi will display two images in succession, but according to the note on the block diagram the second image is blank. It seems as though this would intentionally create a flicker.

The sequence structure is unnecessary. Dataflow will determine the order of execution. The only exception is the time delay in the third frame. Since it has no data dependency, a single frame sequence may be useful to assure that the delay occurs before the picture is updated. A simple state machine might be a more versatile architecture for what you may be trying to do.

It is not necessary to write the FR.PanelBounds property immediately after reading it, nor is it necessary to read it a second time in the second frame. Just wire from the first read.

Lynn

[johnsold]

I won't try to decipher that main program. All the local variables and nested sequence structures make it very difficult to understand. The local variables make race conditions quite likely. That could be part of your flicker problem.

I strongly recommend that you look into rewriting the program using the state machine architecture.

Lynn

[kehander]

A quick and easy suggestion: have you tried right-clicking the Picture indicator and unchecking "Erase First" ?

I had a flicker problem in a very simple program, and it would not go away until I found that option.  (If you are indeed accidently writing a blank image to the picture control every now and then, that would be something you would have to solve first, of course.)