How do I configure PCI 1428 .icd camera file to ignore the DVAL input

[Yshushan]

I am building an imager application. I could not find exact timings for the 3 control lines defined in the Camera Link standart (I looked in the standart specification too). I have got the LVDS platform to convert into CL signals and I use IMAQ PCI 1428 frame grabber. I managed to prduce an image but only in a certain configuration. When trying to change it I recieve an error message. The problem is that I don't have the timing definitions for the three "VAL" lines that control image transmition to frame grabber.

If someone could deliver those or point me to a good source I'd be very thankfull,

Yonatan.

[Yshushan]

I forgot to mention that i could not find the timing diagrams in the Camera Link 1.1 .

I tried adding a delay at the end of the line by keeping both LVAL and FVAL low but then the FG produced an error. Maybe there should be some addtion to the camera file regarding exact timing definitions for those signals...

[JesseD]

Hello Yonatan,

KnowledgeBase 2CE7SIYJ discusses the timing requirements for the 1422 and the 1424.  These same timing requirements also apply to the 1428.  One addition I might add to this is that the FVAL signal must either precede or be synchronized with the the LVAL signal.  If they are synchronized, then SynchronizeEnables must be set to "Yes" in the camera file.  When using the Camera File Generator, available here, you can check this option at the bottom of the Acquisition tab (named "Timing Signals Synchronized"). 

Another note is that the pixel clock must be at least 20MHz, as defined by the camera link spec.

Hope this helps out!

Best Regards,

Jesse D.
Applications Engineering
National Instruments

[ydattner]

Hi,

I'm having some troubles with the specifications. When referring to the pixel clock, is this the txClkin or TxIN26 in the LVDS protocol?

Message Edited by ydattner on 05-17-2010 09:51 PM

[vtypke]

Just for those browsing this thread, I answer to this very old follow-up question:

PCLK has to be fed to TxClk ( this is also referred to as signal "Strobe" in the spec.). This is also the "master clock" of the ChannelLink Chip used.

TxIN26 is the DVAL signal (data valid). You may use the DVAL signal to slow down data transfer. This is useful if your camera produces data at a rate below 20 MHz. 20 MHz is the minimum clock speed at the "Strobe" signal. So, if your camera produces data at, say a rate of 5 MHz, you still have to run the CameraLink Strobe Signal at 20MHz. Because your camera data would then be oversampled by a factor of 4, you simply assert the DVAL signal only every 4 clock of Strobe to reduce the actual data rate to that of your camera.

If your pixel clock is at least 20 MHz, you may permanently assert DVAL to high level and control data transfer by FVAL, LVAL only. Or you just short LVAL and DVAL...

[dcdayton2]

I have on old Phoenix TheramCam DTS camera with camera link interface.  The camera does not transmit a Data Valid (DVAL) signal since the pixels are read out at the same frequency as the Pixel Clock (20 MHz).  I'm trying to find out what parameters settings to get the 1428 to ingnore the DAVL signal.  I have been able to get the camera to work with a 1430 frame grabber because there is an explicit parameter in the .icd file "DVALMODE" which can be set to DVALMODE(0), however I have been trying unsuccessfully to find equivalent settings in the 1428 frame grapper .icd file.  When i use the camera file generator with the "DATA VALID Inverted" setting it produces a .icd file with DataFPAControl(34)  but this doesn't seem to work.  I just get a timeout error message.  The camera is no longer supported by Indigo/FLIR and no one has a 1428 .icd file for it.  Does anybody have any suggestions?  Thanks Dave

[vtypke]

Do you have active-high Frame (FSYNC or VSYNC) and Line Sync (LSYNC or HSYNC) signals? If so, short LSYNC and DVAL (configure DVAL to be active high as well). This should work, because your master clock and pixel rate is the same and >= 20 MHz.

Another option is to permanently assert DVAL, that should work as well. However, as you have tried inverting the DVAL level, I assume that there is some other problem.

Do you have the "NI Camera File Generator"? This is a tool that lets you create and configure .icd files by GUI. You simply create a new .icd file, select the grabber card and configure the card's resolution, interlace mode, timing signal polarity, and so on, and you can even test your setting in the GUI by grabbing still images and video. You should find it on NI's web pages. This will aid you a lot in testing different settings, so that you don't need anyone else to provide a vintage icd file for your camera. (It also comes along with a bunch of pre-created icd files for different manufacturer/camera combinations, maybe yours is included anyways?)