Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

NI-1424 is driving the Pixel Clock line, preventing me from driving my clock to the board

I am trying to connect a custom camera to a NI-1424 grabber via a SCB-100 and cable. The frame grabber does not recognize that the camera is sending timing signals. On investigation the clock signal looks very corrupted. When I disconnect my camera I see a 10 MHz clock waveform on the PIXCLK signals (pins 49 & 50) going from about 3-6 volts. Any thoughts as to what I have misconfigured, or did I get a bad card?
0 Kudos
Message 1 of 4
(3,447 Views)
A bit of an update, took out the board to give it a visual, foun a strand of what looks to be a cloth fibre across the pins of the receiver for the clock. Removed it, and a few other stray fibres (again, none looked metalic, but you never know). On replaicng board in the system the clock now looks ok, but grabbing still doesn't work right. Get timeout errors when trying to grab the whole image. If I shrink the definition of the camera to 300 x 100 then I get a very slow grab rate of about .4 to .7 hz reported (I raised the timeout level to 10000 ms) and the data looks totally wrong. Camera is outputing 640 x 480 interlaced RS-170 timed video (12.27 MHZ pixel clock). I am currently trying to receive it as 640x240 (figure get the simple case first, then work on setting up the interlace). FIle generated with camera file maker.
 
Any idea what could be set up wrong or do I have a bad board?
0 Kudos
Message 2 of 4
(3,435 Views)
 

Hi, Richard,

How you have connected RS-170 camera to 1424 framegrabber??? For RS-170 camera you should use 1405, isn't?

Andrey.

0 Kudos
Message 3 of 4
(3,432 Views)

It is a RS-140 Format (ie timing) camera, with digital outputs

 

Found out problem was had line sync and Field Active backwards (The documentation isn't real clear on which is which is which). Things seem to be working now.

0 Kudos
Message 4 of 4
(3,428 Views)