OAT Get Vector Reference.vi reset errors

[loren.crook]

I have inconsistent results when I switch reset? to True on the OAT Get Vector Reference.vi.  I have a simple rig with two proximity probes and one speed sensor on a simple shaft.  I'm using the example VI, Orbit and Timebase Plot (Analog Tach, DAQmx).vi, with modifications to include compensated runout.  And this is where I'm having the problem.  I'm using vector references for the compensation, and the OAT Get Vector Reference VI.  It starts up & runs fine when I launch the VI.  The reference output mode is averaged samples (default).  When I switch the reset? input to True to clear the averages, it will sometimes reset, and carry on, and sometimes it will give error 21407 "The input signal does not have enough samples" and then stop updating the vector references.  This happens while everything else is running normally, ie speed, proximity.  So I'm confident I'm supplying enough data to the OAT Get Vector Reference VI when this error happens.  Screenshot of the block diagram attached.  

[dsb@NI]

Please include a (tdms) log file that includes enough data to reproduce the issue you are seeing. If you are able, read segments from that log file in your code and reproduce the issue without hardware. Attach that code and the log to this post. 

What version of LabVIEW and Sound and Vibration Toolkit are you using?

[loren.crook]

What type of data should be included in the TDMS, the waveforms captured from the devices, or something more?   Removing the hardware will take some time.

I am using Labview 2025 Q1 and SVT 2023 Q3.

[dsb@NI]

For anybody to dive in on the investigation side, we need to be able to reproduce the issue without your hardware. Yes, include the acquired waveforms in the tdms. We also need your configuration - many times that can be saved as default values in the front panel. We also need the steps to reproduce (such as "Using the default configuration, run the VI. On iteration 7, reset .... I observed <this> behavior: <detailed description>, but I was expecting <this other> behavior: <detailed description>). 

Here, on the forums, you will get a broader audience of helpers if you can save your VI for previous (LV 2021 or even LV 2019).

When you reset OAT Get Vector Reference VI, does that imply that the system geometry has changed? Why reset? Does it make sense to compartmentalize stages of application (specifically separating 1. compute slow-roll compensation vector from 2. apply vector compensation)?