Unable to configure external trigger input source in ULx VI for data acquisition from MCC DAQ board

[SDS9]

Hi, I need to do voltage measurements using MCC DAQ data acquisition board. This board is accessible in Labview through ULx VIs and a number of examples are also there in Labview under the 'Hardware Input Output section'. But I need to acquire data in synchronous with an external TTL input. There is a 'ULx Trigger VI' to synchronize the data acquisition with external TTL input, but this VI has no 'source input' to select the trigger source. A similar DAQmx VI, 'DAQmx start trigger' VI in 'start digital edge' mode has a 'source input' to select the trigger source. This feature is lacking in the 'ULx Trigger VI' and so I am unable to access data synchronously with external TTL input. Please suggest a solution.

[ZYOng]

This board is for NI DAQ devices. For MCC DAQ, the question is best to be posted at Measurement Computing (MCC) - Digilent Forum.

Anyway, I downloaded the ULx Help from LabVIEW DAQ | ULx for NI LabVIEW. The Basic Digital Pattern instance of the ULx Trigger VI allows you to specify the source of the trigger channel. Perhaps you should try to spend some time exploring the help file. 

[SDS9]

Hi, Sorry for the delay in reply and thanks for the suggestion. But Labview shows that only Basic Digital Edge, Basic Digital Level and Basic Analog Edge instances of the ULx Trigger VI are supported for the data acquisition device  I am using (MCC USB-1608HS). It does n't support Basic Digital Pattern instance.

[SDS9 · Accepted solution]

As you suggested, I posted this query in the digilent forum also. They suggested to use the Basic Digital Edge instance.

The data acquisition device I am using (MCC USB-1608HS) has only one physical trigger input terminal. So when we select the basic digital edge instance of the ULx Basic Trigger VI, it automatically takes this physical trigger input terminal as the trigger source, even though there is no option to select the physical trigger source in the basic digital edge instance.

Though they have not told this aspect explicitly, I could conclude this by doing some experiments. Its working fine now..Thanks...