PXI
how to export via pxi star trigger to multiple dvices
Solved!
Hi golubovski,
Good catch! It looks like we are never specifying the buffer size for our Analog Output task. We need to do this at the DAQmx Timing.vi (see screenshot below).
As you can see, we have left the samples per channel input unwired. If you create a constant on this input, you will see that the default is 1000. 
So even though we are connecting 4800 samples to DAQmx Write, we are only writing out the first 1000 samples. If you wire Number of Scans (where you specify 4800) to the samples per channel input, you will get the behavior you desire.
No problem, I am happy to help! I am not sure what you mean by "this seems redundant", so I'll try and clarify what we need to configure.
rate: This is the rate which our device will acquire/generate samples. We have set this to 1000 samples/s, which is hardware-timed.
samples per channel: This is our buffer size. This gets set automatically for us if our task is continuous. For finite, we need to specify our buffer size so that the device knows how many samples to acquire/generate. If we don't explicitly specify the buffer size, it uses the default value (1000 samples per channel).
data: This is what we are actually writing out. I am guessing that this is what seems redundant to you, since we are specifying 4800 samples to write out. But 4800 only defined our data set, not what we are actually going to write out (the latter is defined by the samples per channel input of DAQmx Timing VI).
To read more about these VIs and their input parameters, bring up the context help (ctrl+H) and click on the Detailed help.
Happy Holidays!
Hi golubovski,
What exactly do you mean when you say "I cannot sense neither of the two AO channels"? If we were not receiving either the trigger or clock, I would expect to see a timeout error. You are saying that there is no signal generation, so I am guessing that you see a flat line when you probe the AO channels?
You are correct that the DSA synch example would not work out-of-the-box, since your 6713 device is not DSA. If we wanted to test whether we can simply use the AO device's own clock, and use the trigger from the master DSA we could test that easily. Simply remove the Get Device Name with Prefix.vi and the DAQmx Timing Property node in your AO task (between the Timing and Triggering VIs). Also, there is no need for the DAQmx Timing property.
If you could give a bit more info about what you are actually seeing from the AO device, this would help us pinpoint the problem. It may be something simple that we missed, but let's at least verify that we can start the DSA and AO tasks together and succesfully output the data from the 6713.
