Measurement Studio for VC++

cancel
Showing results for 
Search instead for 
Did you mean: 

NI PCIe-6321, PCIe-1433 - RTSI connected use

Without trigger, the image didn't come out?

Hey, this is not a problem related to trigger configuration.

There is a problem on camera configuration, right?

Did you get desired image from the camera so far?

 

I guess there is no value to establish synchronization between two devices.

Why don't you check camera configuration again?

Certified LabVIEW Developer
There are only two ways to tell somebody thanks: Kudos and Marked Solutions

GCentral
0 Kudos
Message 11 of 14
(1,098 Views)

Looks like a video coming out.

but, the 6321/1433 trigger signal synchronization does not seem to match.

0 Kudos
Message 12 of 14
(1,086 Views)

I might have a misunderstanding... What feature is trigger signal controlling? Camera Shutter?

Certified LabVIEW Developer
There are only two ways to tell somebody thanks: Kudos and Marked Solutions

GCentral
Message 13 of 14
(1,076 Views)

I am using a camera called OCTOPLUS.

The current image is confirmed.

But the trigger doesn't seem to be correct.

 

for (int z = 0; z <XRange; z ++)
{
GarvoObuffer [z] = (-0.5 * GalvoVoltage_x + GarvoOffSet_x) + GalvoVoltage_x * z / (XRange);
}

DAQmxErrChk (DAQmxCfgSampClkTiming (m_BScanOutTask "," CounterFrequency, DAQmx_Val_Rising, DAQmx_Val_FiniteSamps, XRange));

DAQmxErrChk (DAQmx SetStartTrigRetriggerable (m_BScanOutTask, TRUE));

DAQmxErrChk (DAQmxCfgDigEdgeStartTrig (m_BScanOutTask, "/ Dev1 / Ctr0InternalOutput", DAQmx_Val_Rising));

DAQmxErrChk (DAQmx WriteAnalogF64 (m_BScanOutTask, XRange, 0, 10.0, DAQmx_Val_GroupByChannel, GarvoObuffer, NULL, NULL));

 

It doesn't move naturally when you move the x axis.

0 Kudos
Message 14 of 14
(1,018 Views)