LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

digital input with digital trigger on USB-6259

I'm trying to do digital input of a line, with another line serving as a digital trigger.  I keep getting error message 200452 and I don't understand why.

I'm enclosing both the VI and a picture of the error message. 

Can anyone please help?

Download All
0 Kudos
Message 1 of 5
(3,280 Views)

I believe that a digital trigger only applies if you are using hardware timing.  Your VI uses software timing.  That's why you're seeing the error message.  The digital trigger doesn't apply to what you're doing.

 

What, precisely, are you trying to achieve?  It sort of looks like you want to acquire U32 digital data at the rate of 1kHz (hence the nonsensical 1msec loop delay), using a Start trigger to initiate the data sequence.  Do I have this right, or are you trying to do something different?

 

 

Message 2 of 5
(3,256 Views)

Hello DianeS,

Thank you for your reply.  Let me explain what we would like to do:

 

We would like to sample two digital data lines, where a third line (a clock) serves as a digital trigger (edge, falling).  The clock rate is ~1KHz.  Data on the data lines is synchronized by the clock, and there are 10 samples in every cycle of 100msec.  So actually we need to sample 10 bits of data (on each line), which are transmitted in a 10msec period in every 100msec cycle.

 

 

You can see everything in the attached files.  File scope_1.jpg shows the general behavior:  the upper (yellow) line is the clock, the lower lines are the data lines we want to sample.  File scope_2.jpg shows a magnification of a 10msec period.

 

We need the trigger because we want to sample data ONLY in the 10msec where there is actual data, we don’t want to sample in the 90msec "silent" period.  The samples must be written to an output file, and sampling is planned to take place for several days (may be even for a month or so), so we need to reduce the size of the output file to a minimum.  Using the trigger will let us reduce the size of the output file to 10% of the size we would get had we not used a trigger.

 

 

Download All
0 Kudos
Message 3 of 5
(3,242 Views)

I see.  Thank you for the clarification.

 

Have you looked at the example "Read Dig Chan -- Change Detection.vi" in the examples that ship with LabVIEW?   Click on "Find Examples", "Hardware Input and Output", "Digital Measurements".  You'll find it there.  It sounds very close to what you are trying to do.

 

Message 4 of 5
(3,216 Views)

Hello DianeS,

Thank you for your help.

I will try to follow this example and see if it solves the problem.

Gad

0 Kudos
Message 5 of 5
(3,172 Views)