Save/Restore Multiple Waveforms Chart History

[Mr-FoX!]

After many trial/error i did manage to find dirty and very simple solution, delaying the sound configurator for 500ms was enough for app to load it's config and read, but why i get error when i resize my application?

Error 4823 occurred at Sound Input Read (DBL).vi->MicDAQ.vi

LabVIEW:  (Hex 0x12D7) You cannot perform this operation without an active task.  Ensure that a task is active and try again. An input task might stop running if the input buffer overflows. Overflow occurs when the data is not read fast enough.

[Blokk]

---

@Mr-FoX! wrote:

After many trial/error i did manage to find dirty and very simple solution, delaying the sound configurator for 500ms was enough for app to load it's config and read, but why i get error when i resize my application?

Error 4823 occurred at Sound Input Read (DBL).vi->MicDAQ.vi

LabVIEW:  (Hex 0x12D7) You cannot perform this operation without an active task.  Ensure that a task is active and try again. An input task might stop running if the input buffer overflows. Overflow occurs when the data is not read fast enough.

---

1. I cannot really comment on this, since you only show part of your VI. But the error is self-explanatory: you try to use the "Sound Input Read.vi" without creating an active task before. So you do clearly something wrong. Show your whole VI otherwise there is no chance to help.
2. What is the problem with my workaround I show you in my previous post? There you start the acquisition with a certain device, then you can change this on the fly any time...
3. I really recommend you to make some effort to learn how to use a proper state machine where you can easily program separate states like Idle, Initialize, Measure, Stop, Start File rec, Stop File rec, Exit VI... I can only assist you further if you make this effort, otherwise I think I already gave you enough help...

[Mr-FoX!]

I did found that changing sound configurator sampling rate fixed that error (strange!), your walk around has no problem but i was looking for even more simpler way, i posed my solution so that if it was right approach, others may find it useful, may be after some while i have another look on state machine, although i still find it complicated usage of event, case structure .. at least from a LV begainner point of view.

As for your help you did helped me very good, my application almost done and i'm more expert now, thak you

i don't wanna say "see you next issue" but that's a fact for a begainner 🙂