10-28-2009 05:06 PM
Hi, I seem to have uncover a bug in my C++ when I tried removing some cards:
Usualy, I sync every task to a master task and THAT task is linked to the NISYNC_VAL_PXITRIG0 by using DAQmxCfgDigEdgeStartTrig
Now it worked fine because my master task was a S serie, but when I made my master tasks M and Signal Acquisition serie, they never start.
And yes I did some tests on the S serie (link it to a NISYNC_VAL_PXITRIG1 to watch it freeze...to make sure it was indeed listening to the trigger signal)
Also, if I do remove the start trigger from NISYNC_VAL_PXITRIG0 it works like a charm...
Finaly, every task is linked to the master task by its "/ai/StartTrigger" and it works fine....
So only NISYNC_VAL_PXITRIG0 is an issue.....is it because some slots don't receive the signal sent by PXI_Trigger or something?
Should I use the STAR version instead? (Using a timing card in slot 2)
Solved! Go to Solution.
10-29-2009 06:43 PM
Hi Sebastien,
NISYNC_VAL_PXITRIG0 should be a valid source terminal for trigger connections. I recommend using a STAR line and see if it simulates the same bahviour.
11-19-2009 08:54 AM
Well after trying it this sunday...
I noticed that all my issues were gone if instead of linking it manualy to trigger lines I would let the chassis automaticaly link everything like so:
(not actual code but more of a sketch)
StartTrigger(taskHandle, "/Dev1/StartTrigger")
and every ither things I used I also changed to never call the trigger lines myself...it solkved that issue
Sorry for the long time between reply...never got the message that I had an answer ^^;
Thanks though