LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

If you update a graph on the main vi in a subvi by wiring a reference, the graph on the main vi lags behind one reading


@Sarci1 wrote:

Hi SegmentationFault,

 

I looked into this issue a bit further and compared it to the response of an XY graph and you are correct the behavior is faulty.  I am going to file a Corrective Action Request on this issue.  For now, however, I would suggest using the workaround of output the last data set from your subVI to your main VI.

 

Thanks!


Lynn


 

Could you please post the CAR once filled.

 

Ben

 

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 11 of 15
(958 Views)

The CAR for this issue is #278933.  Thank you for bringing it to our attention.

National Instruments
Senior Systems Engineer
Message 12 of 15
(949 Views)

Oh, so it was a bug within labview? Well that was a bit unexpected. Is there a way to know when this is resolved/receive the fix? 

0 Kudos
Message 13 of 15
(941 Views)

Hi SegmentationFault,

 

Unfortunately there is no way to know when a CAR will be fixed.  However, you can review the Release Notes for each version of LabVIEW.  If the CAR has been fixed that number will appear within.  For now, I would suggest using the workaround provided which outputs the last data set from the subVI to the main VI. 

National Instruments
Senior Systems Engineer
0 Kudos
Message 14 of 15
(938 Views)

In my case I worked around it by placing case structure after my event that is executed after teh event but only if there was a change.

 

I sorta thought it was working like the Image control that does not update when I expect.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 15 of 15
(925 Views)