Operation of imgSessionLineTrigSource2

[femtoamy]

I noticed that in the NIMAQ manual entry for imgSessionLineTrigSource2, it says in the note:

"To implement this functionality, the external line rate signal must be cabled to one of the IMAQ control lines."

So, does this mean that I'd have to make my own hardware cabling to connect my signal to the CameraLink control line? (Wouldn't this function be completely useless then?)

I am using a PCI 1426 connected to a Dalsa P2-2x 2k40 line camera. Using Visual C++ to currently run the camera via triggering the start of a frame acquisition, but I actually need to trigger or clock the line-by-line acquisition of the camera so that it is synchronized with the analog output of a PCI 6711. So, I think I would like to accomplish this by tying the output of a GPCTR from the 1426 to the control line on the CameraLink cable (and also to the 6711 through the RTSI). Can this be accomplished in software only?

[Luke H]

femtoamy,

In order to send a trigger over to the camera, you must wire into D-SUB trigger connector on the board.  The pinout is on page 3-3 off this manual:

NI PCI-1426 User Manual

In order to trigger your camera, you would need to wire a TTL signal into pin 1 and the ground to pin 9.  The easiest way to do this is probably to use the 15-pin cable assembly kit (part number 190912-04) mentioned on page A-1 of the same manual.

Regards,
Luke H

[femtoamy]

Thanks for your suggestion.  So, I checked the voltage across pins 1 and 9 on the DSUB.  It seems that I am already able to get my GPCounter on this line. 

What I'm doing is generating the GPCounter on the 6711, actually, then sending it to RTSI0, then using imgSessionTriggerRoute2 to send RTSI0 to the external trigger 0 line on the 1426.  It has exactly the behavior I expect (I am using ND_PULSE_TRAIN_GNR).

So, now how do I get this line to be connected to the CameraLink control line CC1?  I would think this would be accomplished using the imgSessionLineTrigSource2 command with IMG_SIGNAL_EXTERNAL as the trigger type, but it doesn't seem to be working, at least, the camera isn't line triggering...

[femtoamy]

OK, it's working now.  I guess the imgSessionLineTrigSource2 command is not necessary.  I think the key was setting the CC1 line source to External Trigger 0 in the NIDAQ measurement & automation software.  Also it's important to perform the various imgSession commands in the correct order.