11-15-2007 05:42 PM
11-15-2007 06:01 PM
11-15-2007 11:44 PM
Without seeing the code, providing an answer will be hard, could you share some code snippets?
@Clueless1 wrote:
Any suggestions, including code snippets would be most apreciated.
Thanks
11-16-2007 08:15 AM
The Value Change event of the event structure only fires under two circumstances:
You may want to consider a different method for your data accumulation and display. Without details, I don't know for sure, but you may want to consider separating your data caching and your display. Good data cache mechanisms are shift registers, queues, and LV2 globals.
11-16-2007 11:36 AM
11-16-2007 01:34 PM
11-19-2007 08:14 AM
Are your two charts slightly overlapped? This will cause both to refresh every time one does. Another possibility has to do with the way LabVIEW handles Value (signaling) (And Value) events. When you set a Value, this is a sychronous operation that runs through the UI thread. All other operations on the UI thread are suspended until the Value event is complete - this includes any updates to the front panel. This can cause other parts of your display to flicker by starving them from the CPU. In general, unless you are abstracting GUI operations to subVIs, you are usually better off not using the Value events due to their large performance impact.
The front pane property Defer Panel Updates may eliminate your flicker. Try setting it to TRUE before you set your Value, then FALSE afterwards.