06-30-2006 03:32 PM
07-03-2006 03:18 AM
Hi Jim,
Screen-shots are good - even encouraged - but it's more typical to submit JPGs. DOCs are one of those animals that can carry viruses and I'd rather not risk it. ![]()
It sounds like something is explicitly defining the number of samples at run-time - resetting the value you're defining back to 1000? If this is occurring on a top-level Control & Front-Panel, then the program is probably setting the value through a "Local Variable". The value may also be set via a "Property Node" or even via a "Reference" - regardless, you can track them all down by right-clicking on the control and following the "Find" options. If you see Find ->Local Variable(s), examine each Local Variable (or property node). For the record, there's no guarantee that the program will work correctly once you do manage to change this particular value. ![]()
Regards.
07-03-2006 01:10 PM
Thank you,
I was just thinking about being able to increse the size of the doc. for better visability. I have tried working with the rate input for the DaQmx for the sample clock and it does change the frequency of sampling, but I still get just the 1000 samples. I have included Jpegs this time. I have tried to exppand the two DAQ assistants that arn't expanded but am unable to, I also am unable to find a "propertys" command to open them up and see what exactly they do. The nested while loop for output also seems strange to me. Maybe I would be better to attempt a new program but being new to the language I thought using an existing program might be best.
Jim
07-04-2006 01:07 AM
Hi Jim,
The DAQmx Timing.vi (see "Sample Clock") has a "samples per channel" input which is unwired on your diagram - surprise! - it defaults to 1000. ![]()
I don't want to insult you with instructions on how to wire a value, if you already know how, just ignore the rest! On your diagram, choose the wiring tool and move it along the top-edge of "DAQmx Timing.vi". You should see the names of the connectors as you move the tool along. With the mouse on the "samples per channel" input, RIGHT-click and choose, either, Create Control or Create Constant. If you Create Control, a new control will appear on the Front Panel. I'd send a pic, but this PC doesn't have the DAQmx VIs installed! (had to go to another machine to open DAQmx...)
Cheers.
07-05-2006 10:02 AM - edited 07-05-2006 10:02 AM
Thank you for your suggestions, we are getting closer. Don't be afraid to insult my intelligence, I have been told I need to have some before it can be insulted.
When I wires in a control for the sample count I started getting a warning telling me that the VI was stopping at the "Analog 1D Wfm NChan NSamp" data assistant in the middle of the first loop. I wired in a counter to the timeout node and now the VI will run for the full amount of samples. Which is a good thing because I can now take all the needed samples. But it is also a bad thing, because I can't stop the VI until ALL the samples are taken. The program ignores the stop button and runs for the full number of samples. Is there a way to change the input of the timeout to a true/false or something that could be controled with the stop button?
Message Edited by jimsteinmeyer on 07-05-2006 10:04 AM
07-05-2006 10:28 AM
07-05-2006 04:03 PM
> Don't be afraid to insult my intelligence, I have been told I need to have some before it can be insulted.
Well, speaking from personal experience, ignorance is bliss!
> The program ignores the stop button and runs for the full number of samples. Is there a way to change the input of the timeout to a true/false or something that could be controled with the stop button?
I'm gonna have to bail on you here. If you set a low time-out - to get the loop to iterate and check the Stop button - then you may have to handle a timeout-error (the DAQ won't complete within timeout). The "DAQmx READ.vi offers a "number of samples per channel input" that might allow an incremental READ (no timeout error) - but what happens when the entire pre-set number of samples have been acquired, and the loop tries to read more?
I think you're headed for a "Continuous Acquisition" solution. The "Cont Acq&Graph Voltage-To File(Binary).vi" example seems to fit your requirements.
Cheers.