<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic configure imaq in Machine Vision</title>
    <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/254956#M7204</link>
    <description>&lt;DIV&gt;Hello !&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;I've tried to use the Imaq 1410 for non-standard video input. My video is&amp;nbsp;a 0 - 1 Volt analog signal, and I use 2 external syncronization signals (Hsync and Vsync). Hsync and Vsync are both TTL 0 - 5 Volt, 15.62 khz (Hsync) and 50 Hz (Vsync). I tried to configure the Measurement and Automation Explorer with the following options: &lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Video Lock Mode: External H lock&lt;/DIV&gt;
&lt;DIV&gt;Channel 0 camera: (All kinds of them which are in the list: VGA, CCIR, NTSC, PAL, RS-170, AREA SCAN, 30/50/60/25 HZ PROGRESSIVE SCAN, LINE SCAN, JAI CV-A1, JAI CV-M1.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;When I press on the "Snap" or "Grab" Icon in MAX, I get the "Error 0xBFF6001F - Cannot detect recognizable video source".&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;When I use the option: &lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Video Lock Mode : Standard &lt;/DIV&gt;
&lt;DIV&gt;and connect a standard NTSC camera to the IMAQ 1410, I get a good picture, it works.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Can anyone please tell me how to configure my IMAQ&amp;nbsp; in order to be able to see an image with Video, Hsync and Vsync signals ?&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;</description>
    <pubDate>Tue, 16 Aug 2005 12:31:55 GMT</pubDate>
    <dc:creator>Mic_Scale</dc:creator>
    <dc:date>2005-08-16T12:31:55Z</dc:date>
    <item>
      <title>configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/254956#M7204</link>
      <description>&lt;DIV&gt;Hello !&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;I've tried to use the Imaq 1410 for non-standard video input. My video is&amp;nbsp;a 0 - 1 Volt analog signal, and I use 2 external syncronization signals (Hsync and Vsync). Hsync and Vsync are both TTL 0 - 5 Volt, 15.62 khz (Hsync) and 50 Hz (Vsync). I tried to configure the Measurement and Automation Explorer with the following options: &lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Video Lock Mode: External H lock&lt;/DIV&gt;
&lt;DIV&gt;Channel 0 camera: (All kinds of them which are in the list: VGA, CCIR, NTSC, PAL, RS-170, AREA SCAN, 30/50/60/25 HZ PROGRESSIVE SCAN, LINE SCAN, JAI CV-A1, JAI CV-M1.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;When I press on the "Snap" or "Grab" Icon in MAX, I get the "Error 0xBFF6001F - Cannot detect recognizable video source".&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;When I use the option: &lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Video Lock Mode : Standard &lt;/DIV&gt;
&lt;DIV&gt;and connect a standard NTSC camera to the IMAQ 1410, I get a good picture, it works.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Can anyone please tell me how to configure my IMAQ&amp;nbsp; in order to be able to see an image with Video, Hsync and Vsync signals ?&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Tue, 16 Aug 2005 12:31:55 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/254956#M7204</guid>
      <dc:creator>Mic_Scale</dc:creator>
      <dc:date>2005-08-16T12:31:55Z</dc:date>
    </item>
    <item>
      <title>Re: configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/255627#M7219</link>
      <description>&lt;DIV&gt;From the specs you have listed, the 1410 should be able to handle your video signal (however you did not list the image size ie:640x480). &lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;The 1410 uses a PLL (phase lock loop) to generate an internal&amp;nbsp;pixel clock for a video signal that is non-standard (not 640x480). The PLL parameters in the camera file must be set to match the expected video input - these settings are not available through the Measurement and Automation Explorer interface as of now.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;A custom&amp;nbsp;camera file can be requesested by using the&amp;nbsp;the link at the bottom of Camera Advisor (www.ni.com/camera). This provides a form to fill out and an email address to send the form to.&lt;/DIV&gt;</description>
      <pubDate>Wed, 17 Aug 2005 16:41:13 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/255627#M7219</guid>
      <dc:creator>MarcoPolo5</dc:creator>
      <dc:date>2005-08-17T16:41:13Z</dc:date>
    </item>
    <item>
      <title>Re: configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/255968#M7224</link>
      <description>&lt;DIV&gt;Thank you for your answer !&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;My system is composed of LSM (laser scanning microscope) , which generates the video output in correlation with the laser scan position. The LSM controller generates the HSYNC and VSYNC signals according to the laser spot position. The image size is flexible - 256x256 or other square sizes. &lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;How would you recommend to reconfigure the system&amp;nbsp;and&amp;nbsp;the camera setup in order to be able to acquire an image ? &lt;/DIV&gt;
&lt;DIV&gt;(I have an absolute &amp;nbsp;control over the HSYNC, VSYNC signals.&amp;nbsp;I am&amp;nbsp;also able to generate&amp;nbsp;through the LSM control a&amp;nbsp;pixel clock with various frequencies, however this clock is not synchronized with the HSYNC signal.)&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Up until now the only thing that I was&amp;nbsp;able to get was&amp;nbsp;some kind of an&amp;nbsp;image output (just&amp;nbsp;a bunch of dots) &amp;nbsp;(from the Measure and Automation Explorer) by setting HSYNC to 4 KHZ and VSYNC to 200 HZ, I played with the image resolution of various sizes. Even then, the GRABBING function lasted for the most for a few seconds, it always outputs&amp;nbsp;the error "Error 0xBFF6001F - Cannot detect recognizable video source" after a short time. When I used other HSYNC frequencies, it did not work. &lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Can you please also explain to me what HSYNC, VSYNC,&amp;nbsp;image size&amp;nbsp;values are acceptable to the IMAQ 1410 PLL&amp;nbsp; that I can use ? It seems that there is some kind of a connection between all these values that I can't figure out.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;You also mentioned a camera file that I should request. Given the information I wrote, can you please tell me what options should I check when requesting this non-standard camera file ?&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Thanks a million times, waiting for your answer or anyone who can help.&lt;/DIV&gt;</description>
      <pubDate>Thu, 18 Aug 2005 10:51:25 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/255968#M7224</guid>
      <dc:creator>Mic_Scale</dc:creator>
      <dc:date>2005-08-18T10:51:25Z</dc:date>
    </item>
    <item>
      <title>Re: configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/256739#M7240</link>
      <description>&lt;P&gt;Here is a preliminary document (should be on our website shortly) on how to configure the 1410 for non-standard analog signals.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Aug 2005 19:42:27 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/256739#M7240</guid>
      <dc:creator>MarcoPolo5</dc:creator>
      <dc:date>2005-08-19T19:42:27Z</dc:date>
    </item>
    <item>
      <title>Re: configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/260150#M7319</link>
      <description>&lt;P&gt;Thank you for your helpful document, Marco !&lt;/P&gt;
&lt;P&gt;I can now see an image in MAX (Measurement and Automation Explorer). &lt;/P&gt;
&lt;P&gt;As explained in this IMAQ 1410 document, I've made a camera file, using the technique explained&amp;nbsp;there for non-standard cameras. Only, in my case "area scan camera" did not work for me, so I chose "line scan" and it did, but still wrote the error from my previous question:"Error 0xBFF6001F - Cannot detect recognizable video source" after a while, as before. Next, I changed "DetectPCLK (Yes)" to "DetectPCLK (No)", and it now began working smooth.&lt;/P&gt;
&lt;P&gt;As I've described before,&amp;nbsp;my system outputs a Video signal, Hsync and Vsync, therefore I work in the "External H Lock Mode". What surprised me was the fact that weather I unplug VSYNC or connect it,&amp;nbsp;it does not affect the&amp;nbsp;image&amp;nbsp; (is this normal ?), as if the IMAQ does not use this.&lt;/P&gt;
&lt;P&gt;The questions I wanted to ask are:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A)&lt;/P&gt;
&lt;P&gt;When Grabbing or Snapping pictures on MAX, I have horizontal "shifted" lines reappearing on my image. They appear at different locations on it, like "sparks". They seem as if they're a shifted line from another location of the image itself.&amp;nbsp; In addition&amp;nbsp;it happens that&amp;nbsp;I&amp;nbsp; see a "down shifting" of the frames as can be seen on old TV's that are not set correctly to the broadcasted station.&lt;/P&gt;
&lt;P&gt;I've tried changing the following parameters (in MAX and in the camera file):&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;AcquisitionWindow, MaxImageSize, AcqWinHeightRef, AcqWinWidthRef, ClampStart, ClampStop, VCODivider, DPAOffset, LinePixels, LinePixelsRef.&lt;/P&gt;
&lt;P&gt;None of this seemed to help. I suspected that there is a connection between HSYNC&amp;nbsp;frequency and the MaxImageSize or maybe other parameters, and that they need to be set&amp;nbsp;in a specific relation to each other. If this is the case can anyone please explain me how to do that ? Or maybe there is a document ? If not, what can cause this "horizontal noise" ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;B)&lt;/P&gt;
&lt;P&gt;In the camera file there are additional parameters which I can't find any documentations explaining their functions. This is very crucial for me, since I would not be able to activate my camera&amp;nbsp;had I used only&amp;nbsp;IMAQ 1410&amp;nbsp;options given by MAX.&lt;/P&gt;
&lt;P&gt;Where could I find information about them, their values and form&amp;nbsp;of use ? &lt;/P&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;I would very appreciate&amp;nbsp;your&amp;nbsp;help on these issues.&lt;/DIV&gt;</description>
      <pubDate>Mon, 29 Aug 2005 17:14:24 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/260150#M7319</guid>
      <dc:creator>Mic_Scale</dc:creator>
      <dc:date>2005-08-29T17:14:24Z</dc:date>
    </item>
    <item>
      <title>Re: configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/260912#M7341</link>
      <description>&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;Yes - changing DetectPCLK to No will allow your board to generate the pixel clock rather than searching for one generated from the camera. Since your camera does not output a pixel clock, this setting would have to be set to No.&lt;NAMESPACE prefix="o" ns="urn:schemas-microsoft-com:office:office"&gt;&lt;P&gt;&lt;/P&gt;&lt;/NAMESPACE&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;&amp;nbsp;&lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;The 1410 uses PLL (phase lock loop) when acquiring the image and locks onto the embedded Hsync and Vsync signals of the video feed – separate Hsync and Vsync signals are not required. It uses the timing info to generate the pixel clock needed to capture the image data.&lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;&amp;nbsp;&lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;A) Changing the parameters you mentioned: &lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;&amp;nbsp;&lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;AcquisitionWindow, MaxImageSize, AcqWinHeightRef, AcqWinWidthRef, ClampStart, ClampStop, VCODivider, DPAOffset, LinePixels, LinePixelsRef&lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;&amp;nbsp;&lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;should fix the issue you described - steps 12 through 16 of the previously attached document describe what these changes should do. &lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;&amp;nbsp;&lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;I would imagine, from what you described, that a "down shifting" would occur from having too small of a acquisition window height or too much of a top offset. Horizontal shifted lines might be occurring because of too small of a window width is specified or too much left offset (or too little). &lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;&amp;nbsp;&lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;As the attached document described, it is an iterative process to get the 1410 to generate a matching pixel clock to what your camera is using.&lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;&amp;nbsp;&lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;B) Creating custom Camera Files is not fully supported at this time and there is little documentation available that describes the setup and usage of the additional parameters you see in your file. If you are still unable to acquire a good pic, you can request a camera file from our R&amp;amp;D department through ni.com/camera (see option 4). &lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;I wish I could give you a solid answer as to what setting is off, however, It is difficult to see what is going on without seeing how the changes in the cam file are affecting the image. &lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt"&gt;&lt;SPAN style="FONT-SIZE: 11pt; COLOR: #666666; FONT-FAMILY: Arial"&gt;I hope this helps.&lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Aug 2005 22:35:23 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/260912#M7341</guid>
      <dc:creator>MarcoPolo5</dc:creator>
      <dc:date>2005-08-30T22:35:23Z</dc:date>
    </item>
    <item>
      <title>Re: configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/263543#M7396</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;
&lt;P&gt;Thanx again, I now have more control over my image.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;I managed to recieve a picture from my Line Scan camera (MAX 3.1.3), but&amp;nbsp;it's all blurred&amp;nbsp;and unfocused. Is it possible that even though my camera outputs a good and focused picture, my IMAQ 1410 is not configured properly and it is the one who causes this ?&lt;/P&gt;
&lt;P&gt;If so, what can I do about this, are there any parameters that by setting them right&amp;nbsp;can help ?&lt;/P&gt;
&lt;P&gt;Besides the camera file used by MAX, are there other files that are used by it and can be tweaked to change IMAQ 1410/camera properties ?&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;</description>
      <pubDate>Wed, 07 Sep 2005 03:48:22 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/263543#M7396</guid>
      <dc:creator>Mic_Scale</dc:creator>
      <dc:date>2005-09-07T03:48:22Z</dc:date>
    </item>
    <item>
      <title>Re: configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/264572#M7419</link>
      <description>&lt;P&gt;I'm glad to hear that you have a better image. It is possible that the 1410 is causing the image to be "blurry"&amp;nbsp; - to quote the previously attached document again:&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0in 0in 0pt 0.5in; TEXT-INDENT: -0.25in; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1; tab-stops: list .5in"&gt;&lt;SPAN style="FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: Arial"&gt;&lt;SPAN style="mso-list: Ignore"&gt;&lt;SPAN style="FONT: 7pt 'Times New Roman'"&gt;16.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp; &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 9pt; COLOR: black; FONT-FAMILY: Arial"&gt;At this point you may need to adjust one additional parameter in the camera file to fine tune the image quality. Open the camera file in a text editor. The DPAOffset parameter controls the phase offset between the pixel clock and the HSync signal. The valid range is 0 to 63, representing 1 pclk cycle. Most video signals give the best image quality with a value close to or equal to 0. Adjust the value of DPAOffset up and down and observe the effect on the image quality. Between each adjustment, save the camera file and reload it in MAX.&lt;NAMESPACE prefix="o" ns="urn:schemas-microsoft-com:office:office"&gt;&lt;P&gt;&lt;/P&gt;&lt;/NAMESPACE&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;a poor image might also be caused if the camera is sending data faster than the 1410 can aquire - the maximum pixel clock speed is 25.8 MHz when the board is generating the pixel clock internally. This would mean that if you have a 1024 pixels in your linescan, you could go ~25,000 lines/sec. (maybe a little bit slower to account for camera delay between lines).&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;But it could be&amp;nbsp;just as likely that you have a lense or focus issue.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Hopefully these tips will help out.&lt;/DIV&gt;</description>
      <pubDate>Thu, 08 Sep 2005 22:37:17 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/264572#M7419</guid>
      <dc:creator>MarcoPolo5</dc:creator>
      <dc:date>2005-09-08T22:37:17Z</dc:date>
    </item>
    <item>
      <title>Re: configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/265259#M7434</link>
      <description>&lt;DIV&gt;Thanx, Marco.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;But, I think maybe my problem is the opposite. Our machine scans at a low rate of 185 Hz each line, or HSYNC, which means that if I have 1000 pixels, I'm scanning at Pixel-clock rate of 0.185 MHZ. &lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;From what I've read in&amp;nbsp;the IMAQ's&amp;nbsp;manual,&amp;nbsp;the IMAQ 1410 is able to produce an inner Pixel Clock&amp;nbsp;in the range of 2MHZ - 25.8 MHZ, which means that we're far behind. Could this be our problem of not being able to get a focused sharp&amp;nbsp;image ? &lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Moreover, in the document&amp;nbsp; "Configuring a Non Standard Camera for IMAQ 1410" which you've attached, was said that I should also make sure that 100MHz &amp;lt;= PCLK * VCODivider &amp;lt;= 500MHz (STEP 7), which means that&amp;nbsp;the Minimum P-Clock&amp;nbsp;I should reach is &amp;nbsp;6.25 MHZ (if I set VCODivider to its maximum 16)..... which sets my P-Clock range up to 6.25 MHZ - 25.8 MHZ.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;If this is&amp;nbsp;the&amp;nbsp;cause for our struggle&amp;nbsp;for getting a sharp picture, what can we do about it ?&amp;nbsp;Can't the&amp;nbsp;IMAQ 1410 produce a lower P-clock than&amp;nbsp;2 MGHZ ?&amp;nbsp;&amp;nbsp;And how can I fulfill the second requirement of&amp;nbsp;100MHz &amp;lt;= PCLK * VCODivider &amp;lt;= 500MHz&amp;nbsp;? &amp;nbsp;We cannot reach such a high&amp;nbsp;Pixel-Clock.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Thanx again, we really appreciate your help.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Sun, 11 Sep 2005 16:44:13 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/265259#M7434</guid>
      <dc:creator>Mic_Scale</dc:creator>
      <dc:date>2005-09-11T16:44:13Z</dc:date>
    </item>
    <item>
      <title>Re: configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/265834#M7447</link>
      <description>&lt;P&gt;I'm still confused about what is causing your image to be "blurry" - could you attach a "blurred" picture and if possible a good picture&amp;nbsp;(or at least describe what you are expecting)? How was data previously obtained from the microscope? Is it at all possible to output a pixel clock from your system?&lt;/P&gt;
&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 12 Sep 2005 22:29:09 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/265834#M7447</guid>
      <dc:creator>MarcoPolo5</dc:creator>
      <dc:date>2005-09-12T22:29:09Z</dc:date>
    </item>
    <item>
      <title>Re: configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/265976#M7449</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;
&lt;P&gt;Yes, of coarse.&lt;/P&gt;
&lt;P&gt;I'm attaching a picture we expect from our Laser Scanning Microscope with a lens of (X8). We got this picture when we used this exact system (and exact linses of coarse), only our scanning routine was controlled automatically by a control, and we used another Image Grabbing card.&lt;/P&gt;
&lt;P&gt;I'm also attaching an image we're getting now . Third attachment would be our Scope picture of our Video signal Vs H_Sync signal (H_sync is the upper signal, Video is the lower one).&lt;/P&gt;
&lt;P&gt;Our system works in the following way: (It does not output a Pixel clock, only H-sync and V-sync (since we've seen&amp;nbsp;that V-sync is not used by the card,&amp;nbsp; we don't use it).&lt;/P&gt;&lt;FONT size="2"&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The microscope is controlled by a computer program which sends the following orders periodically.&lt;/P&gt;
&lt;P&gt;******************************************************&lt;/P&gt;
&lt;P&gt;Repeat&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1. Produce a V-Sync.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1.1. produce an H-Sync.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;1.2. scan a line (by sampling from x = 0 to x = 10000, when 1 = basic machine step) and send continuously data to analog OUTPUT.&amp;nbsp; &lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; (line&amp;nbsp;scan&amp;nbsp;takes 200 clocks currently. A clock is a basic amount of time).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1.3. go 3 steps up ( y --&amp;gt; y + 3) (it takes 2 clocks currently).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;1.4. go back 10000 steps left (x=10000 to x = 0) (it takes 20 clocks currently).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;Repeat ( 1.1 - 1.4 ) steps until frame completed, after 480 times (480 lines scanned).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2. Go back to the origin, which is (x = 0, y = 0)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Until Stopped by user&lt;/P&gt;
&lt;P&gt;******************************************************&lt;/P&gt;
&lt;P&gt;I control machine's speed of line scanning rate manually and produce an H-Sync after each line. Then I connect the H-sync and the Video signals (Which are on separate lines) to an IMAQ 1410 imaging card and work in the "External H Lock Mode" in "Measurement and Automation Explorer" (MAX). &lt;/P&gt;
&lt;P&gt;Thank you.&lt;/P&gt;&lt;/FONT&gt;</description>
      <pubDate>Tue, 13 Sep 2005 08:54:56 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/265976#M7449</guid>
      <dc:creator>Mic_Scale</dc:creator>
      <dc:date>2005-09-13T08:54:56Z</dc:date>
    </item>
    <item>
      <title>Re: configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/266380#M7463</link>
      <description>&lt;P&gt;I was able to&amp;nbsp;find out more details about the lower end specs of the 1410 board - the PLL does have a lower limit for the H-Sync signal it uses to generate the pixel clock off of. It should be able to go as low as 8kHz line clock rate - however, from what you have described, you have ~1kHz H-Sync signal. Such a slow signal is going to cause abnormal opperation from the PLL and is most likely the cause for your unclear images. If you are not able to speed you acquisition to at least an 8kHz H-Sync signal, you will not be able to grab a clean picture with the 1410. Even oversampling, or setting the pixels generated by the 1410 to be within specs will not compensate for too&amp;nbsp;slow of a H-Sync signal.&lt;/P&gt;
&lt;P&gt;Digitizing your signal could be done with a Digitizer board like the PCI-5102 or even with a multifunction DAQ baord like our M-Series (PCI-6220). These boards can be setup with variable clock speeds and re-triggerable acquisitions (which would allow multi&amp;nbsp;line acquisitions). Digitized data can be organized into arrays and then changed into a Image format with the Array to Image.vi that comes with our Vision Development Module - once in the image format, you could perform any vision routine needed.&lt;/P&gt;
&lt;P&gt;I'm sorry that there does not seem to be a solution for the 1410. This is a very specialized hardware setup you are using with specs that do not fall into the abilities of the 1410.&lt;/P&gt;
&lt;P&gt;Let me know if I can clarify anything further for you or if you have any further questions I can help out with.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Sep 2005 23:04:27 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/266380#M7463</guid>
      <dc:creator>MarcoPolo5</dc:creator>
      <dc:date>2005-09-13T23:04:27Z</dc:date>
    </item>
    <item>
      <title>Re: configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/266579#M7468</link>
      <description>&lt;DIV&gt;Thank you, I guess we need to use another&amp;nbsp;device then.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;With this limitation of H-sync of ours, could you recommend&amp;nbsp;us&amp;nbsp;of&amp;nbsp;products that would support our LSM ? &lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;I would like to attach our Video signal vs. H-Sync scope picture , so that that would be easier. I would like to stress out the fact that our signal does not have a back porch, front porch, blanking are, ext'...&amp;nbsp;&amp;nbsp;that has a standard Video signal. It outputs data continuosly. I've read that I need an area that would be a&amp;nbsp;"Black reference".&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Is there a device that could take our continuous Video signal, without the need to have these clamping areas ? In other words, what do we need to do or what devices to purchase, assuming we cannot change our signals, in order to be able to get a good and clean image ?&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Wed, 14 Sep 2005 12:44:21 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/266579#M7468</guid>
      <dc:creator>Mic_Scale</dc:creator>
      <dc:date>2005-09-14T12:44:21Z</dc:date>
    </item>
    <item>
      <title>Re: configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/267379#M7481</link>
      <description>&lt;P&gt;Any of NI's M-Series DAQ boards will have a digitizing rate fast enough for your application and more than enough bit depth (16 bits). The PCI-6220 is the lowest end (does not include any analog outputs - but it doesn't sound like you need any for you application). This board can be setup with a analog input clock rate based on it's internal counters which can be set for any speed up to the max analog input rate of 250 samples/s. You could set the board up to capture each line at a specified rate (since you do not have a pixel clock) and trigger the start of the capture based on your H-Sync signal. The acquisition can be retriggerable, meaning it will capture and digitize the data each time a pulse is received on the trigger or H-Sync line.&lt;/P&gt;
&lt;P&gt;The 6220 will accept a differential input. Calibration (or clamping) could be done by sampling the voltage from your system when the output is 0 (or a base level) and then subtracting that value from all of the data you digitize. &lt;/P&gt;
&lt;P&gt;The data will be received as an array of double precision values from -1 to 1 volts - which you could then convert to integer values in a 16 bit range - or you can extract the 16 bit value from the 6220 to begin with by extracting "raw data".&lt;/P&gt;
&lt;P&gt;The arrays of data can be manipulated and organized into a 2D array that represents your image - the IMAQ Array to Image will convert this into a Image Datatype which can be used in any of the vision processing functions or viewed on the Image Display Control. &lt;/P&gt;
&lt;P&gt;Hopefully this gives you a better idea of how this setup would work. Let me know if you have any questions about this approach.&lt;/P&gt;
&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 15 Sep 2005 21:48:52 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/267379#M7481</guid>
      <dc:creator>MarcoPolo5</dc:creator>
      <dc:date>2005-09-15T21:48:52Z</dc:date>
    </item>
    <item>
      <title>Re: configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/267798#M7487</link>
      <description>&lt;DIV&gt;Yes, I've heard about this approach.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;We actually posses a NI PCI-6025e daq board. I want to start working on what you have&amp;nbsp;suggested. I'm already reading the board's user manual. &lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;
&lt;DIV&gt;Will this board do the job ? &lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;
&lt;DIV&gt;Thing is I really don't have much of an idea how to begin building the&amp;nbsp;physical setup and the Labview program,&amp;nbsp;we haven't worked on this board before.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Could you please help me, knowing how our system works, understand more specifically the signal setup with this board&amp;nbsp;&amp;nbsp;?&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Also, I'd be very grateful for the Labview programming side help, maybe an already written vi's, or close to the video acquisition needs of ours&amp;nbsp;? &lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Thank you very much&lt;/DIV&gt;</description>
      <pubDate>Fri, 16 Sep 2005 17:11:47 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/267798#M7487</guid>
      <dc:creator>Mic_Scale</dc:creator>
      <dc:date>2005-09-16T17:11:47Z</dc:date>
    </item>
    <item>
      <title>Re: configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/268445#M7499</link>
      <description>&lt;P&gt;The PCI-6052 E DAQ Board will work fine to digitize your laser data. It will digitize a single analog input up to 333kHz. &lt;/P&gt;
&lt;P&gt;I attached an examples to help you get started - it is a modified version of&amp;nbsp;a Retriggerable Analog Input DAQmx example&lt;/P&gt;
&lt;P&gt;I changed the input to acquire 16 bit raw data (you might need to play around with the scaling so that it ranges over 0 to 1 volt rather than -10 to 10v)&lt;/P&gt;
&lt;P&gt;I added a small portion at the end to convert the 1D array of acquired data to a 2D array and then to an image.&lt;/P&gt;
&lt;P&gt;I have not been able to test this vi - I have no hardware to simulate what you are seeing, however this code should get you started.&lt;/P&gt;
&lt;DIV&gt;(Code created in LabVIEW 7.1)- requires that you have Vision Development Module&lt;/DIV&gt;</description>
      <pubDate>Mon, 19 Sep 2005 20:42:44 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/268445#M7499</guid>
      <dc:creator>MarcoPolo5</dc:creator>
      <dc:date>2005-09-19T20:42:44Z</dc:date>
    </item>
    <item>
      <title>Re: configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/268449#M7500</link>
      <description>&lt;P&gt;MarcoPolo:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Isn't the 6025 a 200Ks/sec 12 bit board? I think you transposed the 2 and the 5 and related the 6052's specs&lt;IMG onmouseover="this.style.cursor='hand';" style="CURSOR: hand" onclick="parent.insertSmilies(':smileyindifferent:');parent.postPopup.hide();" height="16" src="http://forums.ni.com/i/smilies/16x16_smiley-indifferent.gif" width="16" /&gt;&lt;/P&gt;
&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 19 Sep 2005 20:47:53 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/268449#M7500</guid>
      <dc:creator>AnalogKid2DigitalMan</dc:creator>
      <dc:date>2005-09-19T20:47:53Z</dc:date>
    </item>
    <item>
      <title>Re: configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/268468#M7501</link>
      <description>Thanks for the correction - the 6025 is a 200ks/s 12-bit - this should still work with the application - since the laser scanning microscopes pixel clock is at&amp;nbsp; ~185kHz. Just remember to change the acquired data conversion to 12 bit rather than the 16 bit setup I set it for.
&lt;DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 19 Sep 2005 21:37:51 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/268468#M7501</guid>
      <dc:creator>MarcoPolo5</dc:creator>
      <dc:date>2005-09-19T21:37:51Z</dc:date>
    </item>
    <item>
      <title>Re: configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/268981#M7513</link>
      <description>&lt;DIV&gt;Thank you very much for the vi.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;I still do not posses the visual model for Labview, but I have&amp;nbsp;looked at&amp;nbsp; your work. I have a few question about the vi and another about the DAQ 6025e board of ours.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;a. How does the retriggering work ? Does it function&amp;nbsp;like a loop which jumps again and again to start the clock frequency ?&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;b. You have defined 1000 clocks for the counter, so does that mean that after each H-Sync, exactly 1000 pixels are digitized, and then the program waits idle&amp;nbsp;for the next H-Sync ?&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;c. You have defined&amp;nbsp; [Height * Width] samples to the analog channel, does that mean that the retriggering will continue until all these much samples are taken ? In other words, is this is how you control the end of the acquisition (or the program) ?&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;d. I think that you have created a snap acquisition. What do I need to change/add if&amp;nbsp;I want a continuous frame grabbing ? (If we suppose that besides H-Sync, I could use V-Sync too as an additional&amp;nbsp;external trigger).&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;e.&amp;nbsp;Currently we are working on&amp;nbsp;isolating&amp;nbsp;the digital and the analog Input/Output signals on the&amp;nbsp;board in order to protect it from damage. Hence, from technical and financial reasons, we will not be able to use all of our&amp;nbsp;10&amp;nbsp;PFI's&amp;nbsp;and not all of&amp;nbsp;our other&amp;nbsp;digital&amp;nbsp;and analog connections,&amp;nbsp;that&amp;nbsp;are on the board. We now need to decide which PFI's and which other digital and analog connections&amp;nbsp;we need for sure&amp;nbsp;for our system to use. Can you please tell&amp;nbsp;me which PFI's and which other digital/analog connection we need for our application ? I really want to get right with it.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;Thanks a million times.&lt;/DIV&gt;</description>
      <pubDate>Tue, 20 Sep 2005 17:57:46 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/268981#M7513</guid>
      <dc:creator>Mic_Scale</dc:creator>
      <dc:date>2005-09-20T17:57:46Z</dc:date>
    </item>
    <item>
      <title>Re: configure imaq</title>
      <link>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/269560#M7538</link>
      <description>&lt;DIV&gt;a) retriggering does "function&amp;nbsp;like a loop" - so in the example it will output a finite pulse train (which acts as the sample clock) and then waits till another trigger occurs to repeat.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;b) I wired "Image Width" into the number of pulses the counter outputs to digitize the analog signal. You will have to match the "Rate" to allow the number of pulses output to match up to the time your laser scans one line - if the rate is too slow, it will miss the H-sync pulse starting the next line.&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;c) yes&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;d) This is a snap acquisition - you would have to add a start trigger (that is retriggerable)&amp;nbsp;that would trigger off of the V-Sync signal - you could setup the current analog acquisition to be triggered this way&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;e) Here is a link to the E-Series users manual - this has the pinout for your device as well as descriptions of the PFI lines:&lt;/DIV&gt;
&lt;DIV&gt;&lt;A href="http://digital.ni.com/manuals.nsf/websearch/05A25C65C755D8DB86256FD30081687D" target="_blank"&gt;http://digital.ni.com/manuals.nsf/websearch/05A25C65C755D8DB86256FD30081687D&lt;/A&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;If you need consulting help with your project look at the list of alliance members we have in your area:&lt;/DIV&gt;
&lt;DIV&gt;&lt;A href="http://digital.ni.com/productpages/nialliance.nsf/main?readform" target="_blank"&gt;http://digital.ni.com/productpages/nialliance.nsf/main?readform&lt;/A&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;If you hook up your analog input in differential mode, there will be a significant ammount of common mode voltage rejection.&lt;/DIV&gt;
&lt;DIV&gt;From the above maual:&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;
&lt;TABLE class="Borderless"&gt;
&lt;TBODY&gt;
&lt;TR class="alt"&gt;
&lt;TD colspan="2"&gt;Max working voltage (signal + common mode)&lt;/TD&gt;
&lt;TD class="gutter"&gt;&amp;nbsp;&lt;/TD&gt;
&lt;TD&gt;Each input should remain within ±11 V of ground&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;
&lt;TD colspan="2"&gt;Overvoltage protection&lt;/TD&gt;
&lt;TD class="gutter"&gt;&amp;nbsp;&lt;/TD&gt;
&lt;TD&gt;
&lt;TABLE class="Bordered"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TH&gt;Signal&lt;/TH&gt;
&lt;TH&gt;Powered On&lt;/TH&gt;
&lt;TH&gt;Powered Off&lt;/TH&gt;&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;AI &amp;lt;0..15&amp;gt;&lt;/TD&gt;
&lt;TD&gt;±42&lt;/TD&gt;
&lt;TD&gt;±35&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;AI SENSE&lt;/TD&gt;
&lt;TD&gt;±40&lt;/TD&gt;
&lt;TD&gt;±25&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/DIV&gt;
&lt;TABLE class="Borderless"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD colspan="4"&gt;&lt;FONT style="BACKGROUND-COLOR: #316ac5" color="#ffffff"&gt;Common&lt;/FONT&gt;-&lt;FONT style="BACKGROUND-COLOR: #316ac5" color="#ffffff"&gt;mode&lt;/FONT&gt; rejection ratio (CMRR), DC to 60 Hz&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;
&lt;TD class="gutter"&gt;&amp;nbsp;&lt;/TD&gt;
&lt;TD&gt;Range 10 to 20 mV&lt;/TD&gt;
&lt;TD class="gutter"&gt;&amp;nbsp;&lt;/TD&gt;
&lt;TD&gt;85 dB&lt;/TD&gt;&lt;/TR&gt;
&lt;TR&gt;
&lt;TD class="gutter"&gt;&amp;nbsp;&lt;/TD&gt;
&lt;TD&gt;Range 100 mV to 1 V&lt;/TD&gt;
&lt;TD class="gutter"&gt;&amp;nbsp;&lt;/TD&gt;
&lt;TD&gt;90 dB&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
      <pubDate>Wed, 21 Sep 2005 20:06:18 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/Machine-Vision/configure-imaq/m-p/269560#M7538</guid>
      <dc:creator>MarcoPolo5</dc:creator>
      <dc:date>2005-09-21T20:06:18Z</dc:date>
    </item>
  </channel>
</rss>

