Can't Create Dynamic Data Constant for Obtain Queue Function

[jcannon]

Thanks... I did get that far... But I still need a constant for the write to file to work after dequeuing in another loop...

[jcannon]

Yes, I take your point... The .vi I am working on is quite a few years old and acquires data using the DAQ Assistant... I don't have time to re-write it using DAQmx functions and "better" coding...

[GerdW]

Hi jcannon,

---

@jcannon wrote:

Thanks... I did get that far... But I still need a constant for the write to file to work after dequeuing in another loop...

---

It looks like there is such a constant at the upper left corner of your truncated image…

---

@jcannon wrote:

I don't have time to re-write it using … "better" coding...

---

Well, you could atleast cleanup the loop to follow style guide.

And you could reduce Rube-Goldbergs: why do you need two ArrayMinMax functions to determine the min and max of the very same array???

Why do you need to clear ALL ERRORS when the error wire is used to stop a loop upon error???

[JÞB]

---

@pincpanter wrote:

I guess that Dynamic Data are too... dynamic for queues. You need to convert DD to a well defined type (Express -> Data manipulation palette).

---

Let's stop guessing!  A simple experiment will uncover a truth.  

Experiment NULL hypothesis: the LabVIEW memory manager cannot fully support all Data flowing on a DDT wire without using To/FromDDT Express.vis.

Method find a method that breaks dataflow using a DDT wire.

TRY

• Queues,
• Dynamic Events
• Value Properties Methods or Events
• Notifiers
• Local Variables
• Global.vis 

Did we find any evidence to reject the null hypothesis or, must we accept it?

[GerdW]

Hi jcannon,

---

@jcannon wrote:

The dequeue element in the consumer loop cannot be wired to the write-to-file function if a DDT constant is not wired into the obtain queue element data type input (see the Data Queue).

---

Wrong.

You can have a queue of 1D-array elements and still wire to WriteMeasurementFile:

LabVIEW will automatically place a ToDDT before the WriteMeasurementFile function!

Again: there's most often no need to use DDT wires at the data source…

[jcannon]

Yes, it's a mess... 😂

[jcannon]

Agreed... Thanks...

[jcannon]

Thank you everyone for your replies...

I've decided I will create a new vi for this application using appropriate style guides etc...

Given the time this will take, I may regret this decision, but my OCD will be much happier with the outcome... 😂  

[jcannon]

Thanks...