infinitenothing

Yes, what you're doing is super common. It might be worthwhile to use the TDMS file format instead of a spreadsheet file. It's a very easy format for recording and playing back data. I'm a little curious why you're using a CRIO. It's not a bad choice but something a CDAQ could be simpler.

At this point, AutoCorr is working well enough and I'm just curious about the advantages and disadvantages of different methods. My signals are rather noisy so it's not always super clear how far back the "start" is from the trigger.

Thank you for the tip. The performance seems similar to ZoomFFT.

Interesting. I've seen its use in things like GPS. Actually, in my particular application, I'm not tracking a frequency. There's some "dead air" which I simulated above with the zeros and then the signal which is unrelated to the previous signal. Does that rule out Kalman or am I misunderstanding how you'd use it. I have the platform suite so I think I have the control design toolkit. Mhmm..yeah... I know some of these words. 😉 I'll take a look at some of the algorithms they mention.

I tried a few different ways of estimating frequency and I thought I'd compare them. If anyone has some other ideas or links to other techniques, I'd like to see how they perform. Techniques used the VI: Zoom FFT PSD AutoCorrelation Frequency Estimation.vi

You have a few options. Use a radio control if the booleans are mutually exclusive Combine the booleans into an array and then convert that to a number Nest your case structures

Maybe I should have tested this before I posted but if I switch Enque Serial Number to a .vim, the broken wire resolves and everything works out. Neat! I wonder if there are any unintended consequences.

No, the queue only contains elements of the child class. I guess I could switch my queue over to the base class. It just seems a little better to use the most specific class possible and I don't understand why the refnum input can't be made dynamic

I'm not clear how adding another dynamic dispatch input solves my problem. The queue ref is still statically dispatched and will only take a queue of the parent class. In terms of intent, I'm looking to improve reuse. Rather than writing an enqueue function in each child class, I just want one VI to handle that.

I can post a project but I'm hoping this image makes clear what I want to do. I want to be able to reuse my StartRun's Enqueue Serial Number in the same way that I'm able to use StartRun's Write Serial Number for its child's object.

I'm referring to the dynamic dispatch terminal setting being unavailable (see below). I was hoping that I could wire a queue of ChildA or a queue of ChildB into that terminal and it would autoadapt (assuming ChildA and ChildB inherited from the StartRun class

I want the children of the "start run" class to be able to use this method but I'm noticing it doesn't let me set the queue refnum input to dynamic. Is there some other way to accomplish this?

Nothing sticks out to me. Have you tried the memory profiler to see what subVI is giving you problems? http://zone.ni.com/reference/en-XX/help/371361P-01/lvdialog/profile/

To clarify the second image was posted before the forum update. Here's the thread: https://lavag.org/topic/20671-programmatically-select-all-boolean-best-way-to-avoid-race-condition/?tab=comments#comment-125949 So, I'm guessing the forum is stripping the metadata on upload now. I reposted that image in this thread by copying the link into the editor box. The box "embedded" the image for me automatically.

This snippet works for me: So does this one: