From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
03-06-2013 05:23 PM - edited 03-06-2013 05:25 PM
Hi all,
So I am aware that the 6008 does not have a hardware clock onboard and is unable to output analog signals on a timed basis. I have two mass flow controllers that need to change flowrates simultaneously at specified times and I get a SampleClock error (see attached) when I use a VI that was adapted from another DAQ (NI-6229) with hardware clock.
Is there any way to use my PC's clock for this? I am told that this requires a lot of work and is not very accurate, but I do not need very accurate timing (just simultaneous for two channels).
I have no experience with LabView and this question is so a more knowldgeable associate can help me figure this out. I was also wondering if I could find a way to "plug in" a clock VI from the tutorials or examples database on this website into my VI and use it as a clock.
03-06-2013 11:21 PM
03-07-2013 07:54 AM - edited 03-07-2013 07:57 AM
Well, I would need to maintain a constant pressure (I'm mixing gases for calibrating some electrochemical sensors that have pressure sensitive membranes) when changing flows (same total flowrate. For example, going from 100-0 to 50-50 ml/min on my 2 MFCs.
A more specific example would be having the 2 MFCs going at 100-0 for 5 minutes, then switching to 75-25 for 5 minutes, then switching to 50-50 and so forth at given time points. I could these manually (On Demand) but the VI I have is not written for that kind of operation.
It sounds like the lag may be very large if I use a timed loop on my PC, which may cause problems for my sensors. How bad can the lag be?
03-07-2013 08:48 AM
Hard to say how bad. In the seconds range certainly.
03-07-2013 08:52 AM - edited 03-07-2013 08:54 AM
Yikes! That would likely be unacceptable for my applications. Is its seconds rnage lag in terms of simultaneous switching or seconds in the time specified for the change? I don't mind lag in the timing, as long as the two switch in relative uniso.
I shall look elsewhere in if thats the case. Thanks for your input!
03-07-2013 09:02 AM
It is the lag in the time specified for the switch.
03-07-2013 09:22 AM
In this case, I would be OK with it as long as the two MFCs make the switch together in unison. Could I take a clock VI from the dataase and plug it into my block diagram? Or would I need to fashion the timed loop myself?
03-07-2013 11:00 AM
I don't understand your question. The timed loop is a function on the Structures palette and you have several functions on the timing palette (Wait (ms), Elapsed Time, etc. that use the pc clock). It sounds like you need a basic tutorial on LabVIEW.