A few thoughts in no particular order:
1. Both devices can use digital signals at their PFI terminals as a start trigger. This can help you sync the start time on the 2 different devices.
2. However, the subsequent sampling most likely will *NOT* remain in sync for the 2 different devices. By default, both will use their own separate internal timebase clocks to derive their sample clocks. These are typically spec'ed for something like 50 ppm accuracy, which equates to an error of about 3 msec per minute of acquisition.
However, it is *also* possible for both devices to use a PFI terminal signal as a sample clock. Giving both of them the same sample clock signal could *keep* them in sync.
3. I don't use Matlab for data acq but have learned from many threads over the years that it doesn't provide access to all the detailed settings of DAQmx. I don't know the specific limitations, but I can recall many times that things which were possible via LabVIEW simply couldn't be done via Matlab due to the restricted API.
The things I described are possible with DAQmx and your devices. But I don't know if the Matlab toolbox will give you access to what you need.
-Kevin P
ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
