LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

DAQmx Device data type, local variable VS "Value" property

I still think there is a race condition in the original but I suspect that with the sequence structure, the output does not get updated because the coercion from a value string to a DAQ device name is not correct. I don't know where the conversion from DAQ device name to string is supposed to happen but seems the value property itself does not contain it. If you wire the subVI correctly, everything works as expected.

 

get dev.PNG

 

 

0 Kudos
Message 31 of 32
(571 Views)

I like your point about conversion. Suprisingly enough, if you substitute device name by visa resource name or similar, it works as it should. It is also strange that the data type of the value is string an not DaqMx device.

 

But about the race condition: Dennis, who is performing the write in the original vi? Or what is your definition of the race condition? The one I am accustomed to includes writing (say, this one).

 

I can imagine only one write that is being performed: somewhere under the hood in one of the 5 copies of the data in the control (by AQ@lavag.org). Did you mean that?

Message Edited by mzu on 11-25-2009 04:17 PM
0 Kudos
Message 32 of 32
(567 Views)