‎Tips and notes

← Older revision Revision as of 20:01, 29 January 2018 (3 intermediate revisions by the same user not shown)Line 37: Line 37:  ==<font color='blue'>Line scan with Elphel</font>== ==<font color='blue'>Line scan with Elphel</font>==    −[[File:Elphelimg 1015229 a.jpeg|thumb|500px|This image is downsized from 2592x3872 and rotated by 90&deg; CCW]]+[[File:Elphelimg 1015229 a.jpeg|thumb|500px|This image is downsized from 2592x8000 and rotated by 90&deg; CCW]]     {| class='wikitable' {| class='wikitable' Line 60: Line 60:     Due to the Bayer pattern of the sensor the minimal sample height is 2 lines. Due to the Bayer pattern of the sensor the minimal sample height is 2 lines. −  −  −      ==<font color='blue'>Instructions for 393</font>== ==<font color='blue'>Instructions for 393</font>== Line 98: Line 95:  ** WOI_HEIGHT=3872 ** WOI_HEIGHT=3872  ** COMPRESSOR_RUN=2 ** COMPRESSOR_RUN=2 − +<!--  * '''Example 3:''' 2592x1936, not changing any frame dimensions, sensor is triggered from internal counter at '''2000 fps''' * '''Example 3:''' 2592x1936, not changing any frame dimensions, sensor is triggered from internal counter at '''2000 fps'''  ** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5 ** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5 Line 105: Line 102:  ** TRIG=4 ** TRIG=4  ** COMPRESSOR_RUN=2 ** COMPRESSOR_RUN=2  +-->     ===Tips and notes=== ===Tips and notes=== Line 110: Line 108:  * How to process [[JP4#JP4|JP4]] * How to process [[JP4#JP4|JP4]]  * To '''seamlessly''' join 2 consecutive JP4 photo finish frames - their pixels has to be joined before demosaicing. Otherwise demosaicing algorithm will create a seam. * To '''seamlessly''' join 2 consecutive JP4 photo finish frames - their pixels has to be joined before demosaicing. Otherwise demosaicing algorithm will create a seam. −* At 2000 fps and PH_HEIGHT=2, The 2592x16384 composite frame consists of 8192 2592x2 stacked frames and covers 4.096 seconds.+<!--* At 2000 fps and PH_HEIGHT=2, The 2592x16384 composite frame consists of 8192 2592x2 stacked frames and covers 4.096 seconds.--> −   −       ==<font color='blue'>Instructions for 353</font>== ==<font color='blue'>Instructions for 353</font>== Line 130: Line 126:  ** PF_HEIGHT=2 ** PF_HEIGHT=2  ** COMPRESSOR_RUN=2 ** COMPRESSOR_RUN=2  +<!--  * '''Example 2:''' 2592x1936, not changing any frame dimensions, sensor is triggered from internal counter: '''2000fps''' * '''Example 2:''' 2592x1936, not changing any frame dimensions, sensor is triggered from internal counter: '''2000fps'''  ** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=1 ** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=1 Line 136: Line 133:  ** TRIG=4 ** TRIG=4  ** COMPRESSOR_RUN=2 ** COMPRESSOR_RUN=2  +-->     ===Tips and notes=== ===Tips and notes=== Oleg

‎Line scan with Elphel

← Older revision Revision as of 21:49, 26 January 2018 Line 37: Line 37:  ==<font color='blue'>Line scan with Elphel</font>== ==<font color='blue'>Line scan with Elphel</font>==    −[[File:Elphelimg 1015229 a.jpeg|thumb|500px|This image is downsized from 2592x3872 and rotated by 90&deg; CCW]]+[[File:Elphelimg 1015229 a.jpeg|thumb|500px|This image is downsized from 2592x8000 and rotated by 90&deg; CCW]]     {| class='wikitable' {| class='wikitable' Line 60: Line 60:     Due to the Bayer pattern of the sensor the minimal sample height is 2 lines. Due to the Bayer pattern of the sensor the minimal sample height is 2 lines. −  −  −      ==<font color='blue'>Instructions for 393</font>== ==<font color='blue'>Instructions for 393</font>== Oleg

Oleg uploaded a new version of File:Elphelimg 1015229 a.jpeg

New page

== Licensing ==
{{CC }} Oleg

Oleg Dzhimiev committed changes to the Elphel git project :
refresh after init

Oleg Dzhimiev committed changes to the Elphel git project :
Added makefile

Oleg Dzhimiev committed changes to the Elphel git project :
1. timer 2. link to pars 3. set to sensor's center

Oleg Dzhimiev committed changes to the Elphel git project :
init and refresh

Oleg Dzhimiev committed changes to the Elphel git project :
added photo finish demo

Oleg Dzhimiev committed changes to the Elphel git project :
abs path for get-image.php

← Older revision Revision as of 20:08, 24 January 2018 (6 intermediate revisions by the same user not shown)Line 60: Line 60:     Due to the Bayer pattern of the sensor the minimal sample height is 2 lines. Due to the Bayer pattern of the sensor the minimal sample height is 2 lines.  +  +  +     ==<font color='blue'>Instructions for 393</font>== ==<font color='blue'>Instructions for 393</font>== Line 102: Line 105:  ** TRIG=4 ** TRIG=4  ** COMPRESSOR_RUN=2 ** COMPRESSOR_RUN=2  +  +===Tips and notes===  +* Works in JP4 (COLOR=5) and MONO(COLOR=1) formats  +* How to process [[JP4#JP4|JP4]]  +* To '''seamlessly''' join 2 consecutive JP4 photo finish frames - their pixels has to be joined before demosaicing. Otherwise demosaicing algorithm will create a seam.  +* At 2000 fps and PH_HEIGHT=2, The 2592x16384 composite frame consists of 8192 2592x2 stacked frames and covers 4.096 seconds.  +  +     ==<font color='blue'>Instructions for 353</font>== ==<font color='blue'>Instructions for 353</font>== Line 125: Line 136:  ** TRIG=4 ** TRIG=4  ** COMPRESSOR_RUN=2 ** COMPRESSOR_RUN=2  +  +===Tips and notes===  +* Works in JPEG format  +* 2 consecutive JPEG photo finish frames can be "seamlessly" joined without any special processing. Demosaicing related artifacts are taken care of in fpga.     ==<font color='blue'>Important notes</font>== ==<font color='blue'>Important notes</font>== Oleg

Show changes Oleg

Oleg Dzhimiev committed changes to the Elphel git project :
finished photo finish debugging

Show changes Oleg

‎Instructions for 353

Show changes Oleg

Oleg uploaded File:Elphelimg 1015229 a.jpeg

New page

== Licensing ==
{{CC }} Oleg

← Older revision Revision as of 22:25, 22 January 2018 (4 intermediate revisions by the same user not shown)Line 59: Line 59:  Due to the Bayer pattern of the sensor the minimal sample height is 2 lines. Due to the Bayer pattern of the sensor the minimal sample height is 2 lines.    −====Setup instructions for 353====+   +===Setup instructions for 393===  +   +   +The instructions are the same as for 353, the key moments are switching to sensor free fun (or reasonable fps) and JP4 format modes.  +393 are set to internal 10fps trigger while 353's sensor is in the free run mode at boot.  +   +=====Examples=====  +* Example 1: 2592x1936, not changing any frame dimensions, sensor is in a free run mode  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5  +** PH_HEIGHT=2  +** COMPRESSOR_RUN=2  +* Example 2: 2592x3872, not changing any frame dimensions, sensor is in a free run mode  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5  +** PH_HEIGHT=2  +** WOI_HEIGHT=3872  +** COMPRESSOR_RUN=2  +   +* Example 3: 2592x1936, not changing any frame dimensions, sensor is triggered from internal counter: 2000fps  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5  +** PH_HEIGHT=2  +** TRIG_PERIOD=50000 (units are in 1/100MHz)  +** TRIG=4  +** COMPRESSOR_RUN=2  +   +   +===Setup instructions for 353===  +   +   * A link for quick access to parameters that might be required: * A link for quick access to parameters that might be required:    http://192.168.0.9/parsedit.php?WB_EN&AUTOEXP_ON&EXPOS&COMPRESSOR_RUN&TRIG&TRIG_PERIOD&PF_HEIGHT&WOI_HEIGHT&WOI_TOP&WOI_LEFT&WOI_WIDTH   http://192.168.0.9/parsedit.php?WB_EN&AUTOEXP_ON&EXPOS&COMPRESSOR_RUN&TRIG&TRIG_PERIOD&PF_HEIGHT&WOI_HEIGHT&WOI_TOP&WOI_LEFT&WOI_WIDTH     * To switch the camera into the line scan mode: * To switch the camera into the line scan mode: − +** '''COMPRESSOR_RUN=0''' - stop compressor −** '''set COMPRESSOR_RUN=0''' - stop compressor+** '''PH_HEIGHT=2'''      - switch to line scan mode −** '''set PH_HEIGHT=2'''      - switch to line scan mode+** '''COMPRESSOR_RUN=2''' - restart compressor −** '''set COMPRESSOR_RUN=2''' - restart compressor      {| {| −|[[File:pf-height.png|thumb|600px]]+|[[File:pf-height.png|thumb|600px|It is functional]]  |} |}    Line 85: Line 112:     =====Examples===== =====Examples===== −# Example 1: 2592x1936, not changing any frame dimensions, sensor is in a free run mode+* Example 1: 2592x1936, not changing any frame dimensions, sensor is in a free run mode −## COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0+** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0 −## PH_HEIGHT=2+** PH_HEIGHT=2 −## COMPRESSOR_RUN=2+** COMPRESSOR_RUN=2 −# Example 2: 2592x1936, not changing any frame dimensions, sensor is triggered from internal counter: 2000fps+* Example 2: 2592x1936, not changing any frame dimensions, sensor is triggered from internal counter: 2000fps −## COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0+** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0 −## PH_HEIGHT=2+** PH_HEIGHT=2 −## TRIG_PERIOD=50000 (units are in 1/100MHz)+** TRIG_PERIOD=50000 (units are in 1/100MHz) −## TRIG=4+** TRIG=4 −## COMPRESSOR_RUN=2+** COMPRESSOR_RUN=2 −   −====Setup instructions for 393====  −The instructions are the same as for 353, the key moments are switching to sensor free fun (or reasonable fps) and JP4 format modes.  −393 are set to internal 10fps trigger while 353's sensor is in the free run mode at boot.  −=====Examples=====  −# Example 1: 2592x1936, not changing any frame dimensions, sensor is in a free run mode  −## COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5  −## PH_HEIGHT=2  −## COMPRESSOR_RUN=2  −# Example 2: 2592x3872, not changing any frame dimensions, sensor is in a free run mode  −## COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5  −## PH_HEIGHT=2  −## WOI_HEIGHT=3872  −## COMPRESSOR_RUN=2  −   −# Example 3: 2592x1936, not changing any frame dimensions, sensor is triggered from internal counter: 2000fps  −## COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5  −## PH_HEIGHT=2  −## TRIG_PERIOD=50000 (units are in 1/100MHz)  −## TRIG=4  −## COMPRESSOR_RUN=2  −       ====Important notes==== ====Important notes==== Oleg

← Older revision Revision as of 22:25, 22 January 2018 (7 intermediate revisions by the same user not shown)Line 59: Line 59:  Due to the Bayer pattern of the sensor the minimal sample height is 2 lines. Due to the Bayer pattern of the sensor the minimal sample height is 2 lines.    −====353 photo finish setup instructions====+   +===Setup instructions for 393===  +   +   +The instructions are the same as for 353, the key moments are switching to sensor free fun (or reasonable fps) and JP4 format modes.  +393 are set to internal 10fps trigger while 353's sensor is in the free run mode at boot.  +   +=====Examples=====  +* Example 1: 2592x1936, not changing any frame dimensions, sensor is in a free run mode  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5  +** PH_HEIGHT=2  +** COMPRESSOR_RUN=2  +* Example 2: 2592x3872, not changing any frame dimensions, sensor is in a free run mode  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5  +** PH_HEIGHT=2  +** WOI_HEIGHT=3872  +** COMPRESSOR_RUN=2  +   +* Example 3: 2592x1936, not changing any frame dimensions, sensor is triggered from internal counter: 2000fps  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5  +** PH_HEIGHT=2  +** TRIG_PERIOD=50000 (units are in 1/100MHz)  +** TRIG=4  +** COMPRESSOR_RUN=2  +   +   +===Setup instructions for 353===  +   +   * A link for quick access to parameters that might be required: * A link for quick access to parameters that might be required:    http://192.168.0.9/parsedit.php?WB_EN&AUTOEXP_ON&EXPOS&COMPRESSOR_RUN&TRIG&TRIG_PERIOD&PF_HEIGHT&WOI_HEIGHT&WOI_TOP&WOI_LEFT&WOI_WIDTH   http://192.168.0.9/parsedit.php?WB_EN&AUTOEXP_ON&EXPOS&COMPRESSOR_RUN&TRIG&TRIG_PERIOD&PF_HEIGHT&WOI_HEIGHT&WOI_TOP&WOI_LEFT&WOI_WIDTH     * To switch the camera into the line scan mode: * To switch the camera into the line scan mode: − +** '''COMPRESSOR_RUN=0''' - stop compressor −* '''set COMPRESSOR_RUN=0''' - stop compressor+** '''PH_HEIGHT=2'''      - switch to line scan mode −* '''set PH_HEIGHT=2'''      - switch to line scan mode+** '''COMPRESSOR_RUN=2''' - restart compressor −* '''set COMPRESSOR_RUN=2''' - restart compressor      {| {| −|[[File:pf-height.png|thumb|600px]]+|[[File:pf-height.png|thumb|600px|It is functional]]  |} |}    −For more details about changing parameters, see [[Elphel_353_series_quick_start_guide#Accessing_camera_parameters|Accessing camera parameters]]+Before changing any image related parameters in this mode it's better to stop the compressor and restart it after everything is set.  +For more details about changing parameters, see [[Elphel_353_series_quick_start_guide#Accessing_camera_parameters|Accessing camera parameters]].     Photo-finish mode per “default” then samples line-pairs as fast as (exposure) settings allow with a maximum rate of approx. 2300 line-pairs per second and a maximum width of the composite frame of 16384px (defined by WOI_HEIGHT). The sensor location that is used as source for these lines is defined by WOI_TOP, WOI_LEFT and WOI_WIDTH. Photo-finish mode per “default” then samples line-pairs as fast as (exposure) settings allow with a maximum rate of approx. 2300 line-pairs per second and a maximum width of the composite frame of 16384px (defined by WOI_HEIGHT). The sensor location that is used as source for these lines is defined by WOI_TOP, WOI_LEFT and WOI_WIDTH. Line 83: Line 111:  * use the camera’s internal [http://wiki.elphel.com/index.php?title=Trigger trigger mode] with TRIG=4 and TRIG_PERIOD settings to generate a regular trigger impulse. (but due to camera’s internal delays in that mode the line rate is a bit less ) * use the camera’s internal [http://wiki.elphel.com/index.php?title=Trigger trigger mode] with TRIG=4 and TRIG_PERIOD settings to generate a regular trigger impulse. (but due to camera’s internal delays in that mode the line rate is a bit less )    −(A common pitfall in trying out photo-finish mode is that one needs to take care of appropriate exposure setting before going into photo-finish mode. If you just start that mode in low light conditions you will end up waiting for frames endlessly – and get the impression the camera does not work anymore)+=====Examples=====  +* Example 1: 2592x1936, not changing any frame dimensions, sensor is in a free run mode  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0  +** PH_HEIGHT=2  +** COMPRESSOR_RUN=2  +* Example 2: 2592x1936, not changing any frame dimensions, sensor is triggered from internal counter: 2000fps  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0  +** PH_HEIGHT=2  +** TRIG_PERIOD=50000 (units are in 1/100MHz)  +** TRIG=4  +** COMPRESSOR_RUN=2  +   +====Important notes====  +* A common pitfall in trying out photo-finish mode is that one needs to take care of appropriate exposure setting before going into photo-finish mode. If you just start that mode in low light conditions you will end up waiting for frames endlessly – and get the impression the camera does not work anymore. For example:  +<font size='2'>  +  Switching to photo finish from 2592x1936 and 50ms exposure to 2592x2 and 2592x1936 composite image will result in waiting for that composite image for 50 seconds (1936/2*50ms).  +</font>     ==== Examples ==== ==== Examples ==== Oleg

← Older revision Revision as of 22:25, 22 January 2018 (9 intermediate revisions by the same user not shown)Line 18: Line 18:  ---- ----    −===<font color='darkblue'>Photo finish / Line scan mode</font>===+==<font color='darkblue'>Photo finish / Line scan mode</font>==    −==== What is line scan? ====+=== What is line scan? ===     Line-scan is an image acquisition method that continuously samples (sensor) lines into a composite image. A Flatbed or hand held scanner is essentially also kind of a line-scanner. For some historic reasons (I guess due to the various application and realms they derived from) there are many terms:   Line-scan is an image acquisition method that continuously samples (sensor) lines into a composite image. A Flatbed or hand held scanner is essentially also kind of a line-scanner. For some historic reasons (I guess due to the various application and realms they derived from) there are many terms:   Line 35: Line 35:  Applications of these line-scan method include industrial surface scanning, photo-finish, rotating panorama cameras, aerial imaginary, the arts (an interesting overview of art and research related slit-scan approaches can be found here) and certainly many more. Applications of these line-scan method include industrial surface scanning, photo-finish, rotating panorama cameras, aerial imaginary, the arts (an interesting overview of art and research related slit-scan approaches can be found here) and certainly many more.    −==== Line scan with Elphel ====+=== Line scan with Elphel ===     {| class='wikitable' {| class='wikitable' Line 53: Line 53:  Since 2005 and the older 333 model, Elphel cameras have a '''“photo-finish”''' mode. With its 3Mpix Aptina CMOS sensor Elphel 333 was able so sample around 3072 lines per second. The photo-finsh mode was revived for the current Elphel 353 model with firmware release 8.0.8.7 by end of April 2010. The current 5Mpix Aptina CMOS sensor (width: 2536px) is a bit slower and allows a sample rate of approx. 2300 lines per second – or a line rate of 2.3 kHz (as it seems to be measured in dedicated line-scan cameras).   Since 2005 and the older 333 model, Elphel cameras have a '''“photo-finish”''' mode. With its 3Mpix Aptina CMOS sensor Elphel 333 was able so sample around 3072 lines per second. The photo-finsh mode was revived for the current Elphel 353 model with firmware release 8.0.8.7 by end of April 2010. The current 5Mpix Aptina CMOS sensor (width: 2536px) is a bit slower and allows a sample rate of approx. 2300 lines per second – or a line rate of 2.3 kHz (as it seems to be measured in dedicated line-scan cameras).      −Elphel 353 software is fully ported to the new Elphel 393 generation of camera systems.+Elphel 353 software is fully ported to the new Elphel 393 generation of camera systems and works for JP4 format.    −In '''Photo finish''' mode the camera then samples just lines and delivers composite images as video frames via RTSP network stream or directly to a hard-disc. Programming the camera into line-scan mode is as simple as setting PH_HEIGHT to the desired line height (in pixel):+In '''Photo finish''' mode the camera then samples just lines and delivers composite images as video frames via RTSP network stream or directly to a hard-disc.      −* '''set COMPRESSOR_RUN=0'''+Due to the Bayer pattern of the sensor the minimal sample height is 2 lines. −* '''set PH_HEIGHT=2'''+  −* '''set COMPRESSOR_RUN=2'''+   +===Setup instructions for 393===    − Quick link to access parameters that might be useful: http://192.168.0.9/parsedit.php?WB_EN&AUTOEXP_ON&EXPOS&COMPRESSOR_RUN&TRIG&TRIG_PERIOD&PF_HEIGHT&WOI_HEIGHT&WOI_TOP&WOI_LEFT&WOI_WIDTH  − For more details see: [[Elphel_353_series_quick_start_guide#Accessing_camera_parameters|accessing camera parameters]]     −Due to the Bayer pattern of the sensor the minimal sample height is 2 lines.+The instructions are the same as for 353, the key moments are switching to sensor free fun (or reasonable fps) and JP4 format modes.  +393 are set to internal 10fps trigger while 353's sensor is in the free run mode at boot.  +   +=====Examples=====  +* Example 1: 2592x1936, not changing any frame dimensions, sensor is in a free run mode  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5  +** PH_HEIGHT=2  +** COMPRESSOR_RUN=2  +* Example 2: 2592x3872, not changing any frame dimensions, sensor is in a free run mode  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5  +** PH_HEIGHT=2  +** WOI_HEIGHT=3872  +** COMPRESSOR_RUN=2  +   +* Example 3: 2592x1936, not changing any frame dimensions, sensor is triggered from internal counter: 2000fps  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5  +** PH_HEIGHT=2  +** TRIG_PERIOD=50000 (units are in 1/100MHz)  +** TRIG=4  +** COMPRESSOR_RUN=2  +   +   +===Setup instructions for 353===  +   +   +* A link for quick access to parameters that might be required:  + http://192.168.0.9/parsedit.php?WB_EN&AUTOEXP_ON&EXPOS&COMPRESSOR_RUN&TRIG&TRIG_PERIOD&PF_HEIGHT&WOI_HEIGHT&WOI_TOP&WOI_LEFT&WOI_WIDTH  +   +* To switch the camera into the line scan mode:  +** '''COMPRESSOR_RUN=0''' - stop compressor  +** '''PH_HEIGHT=2'''      - switch to line scan mode  +** '''COMPRESSOR_RUN=2''' - restart compressor    −[[File:pf-height.png]]+{|  +|[[File:pf-height.png|thumb|600px|It is functional]]  +|}     +Before changing any image related parameters in this mode it's better to stop the compressor and restart it after everything is set.  +For more details about changing parameters, see [[Elphel_353_series_quick_start_guide#Accessing_camera_parameters|Accessing camera parameters]].     Photo-finish mode per “default” then samples line-pairs as fast as (exposure) settings allow with a maximum rate of approx. 2300 line-pairs per second and a maximum width of the composite frame of 16384px (defined by WOI_HEIGHT). The sensor location that is used as source for these lines is defined by WOI_TOP, WOI_LEFT and WOI_WIDTH. Photo-finish mode per “default” then samples line-pairs as fast as (exposure) settings allow with a maximum rate of approx. 2300 line-pairs per second and a maximum width of the composite frame of 16384px (defined by WOI_HEIGHT). The sensor location that is used as source for these lines is defined by WOI_TOP, WOI_LEFT and WOI_WIDTH. Line 77: Line 111:  * use the camera’s internal [http://wiki.elphel.com/index.php?title=Trigger trigger mode] with TRIG=4 and TRIG_PERIOD settings to generate a regular trigger impulse. (but due to camera’s internal delays in that mode the line rate is a bit less ) * use the camera’s internal [http://wiki.elphel.com/index.php?title=Trigger trigger mode] with TRIG=4 and TRIG_PERIOD settings to generate a regular trigger impulse. (but due to camera’s internal delays in that mode the line rate is a bit less )    −(A common pitfall in trying out photo-finish mode is that one needs to take care of appropriate exposure setting before going into photo-finish mode. If you just start that mode in low light conditions you will end up waiting for frames endlessly – and get the impression the camera does not work anymore)+=====Examples=====  +* Example 1: 2592x1936, not changing any frame dimensions, sensor is in a free run mode  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0  +** PH_HEIGHT=2  +** COMPRESSOR_RUN=2  +* Example 2: 2592x1936, not changing any frame dimensions, sensor is triggered from internal counter: 2000fps  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0  +** PH_HEIGHT=2  +** TRIG_PERIOD=50000 (units are in 1/100MHz)  +** TRIG=4  +** COMPRESSOR_RUN=2  +   +====Important notes====  +* A common pitfall in trying out photo-finish mode is that one needs to take care of appropriate exposure setting before going into photo-finish mode. If you just start that mode in low light conditions you will end up waiting for frames endlessly – and get the impression the camera does not work anymore. For example:  +<font size='2'>  +  Switching to photo finish from 2592x1936 and 50ms exposure to 2592x2 and 2592x1936 composite image will result in waiting for that composite image for 50 seconds (1936/2*50ms).  +</font>     ==== Examples ==== ==== Examples ==== Oleg

← Older revision Revision as of 22:25, 22 January 2018 (16 intermediate revisions by the same user not shown)Line 18: Line 18:  ---- ----    −===<font color='darkblue'>Photo finish / Line scan mode</font>===+==<font color='darkblue'>Photo finish / Line scan mode</font>==    −==== What is line scan? ====+=== What is line scan? ===     Line-scan is an image acquisition method that continuously samples (sensor) lines into a composite image. A Flatbed or hand held scanner is essentially also kind of a line-scanner. For some historic reasons (I guess due to the various application and realms they derived from) there are many terms:   Line-scan is an image acquisition method that continuously samples (sensor) lines into a composite image. A Flatbed or hand held scanner is essentially also kind of a line-scanner. For some historic reasons (I guess due to the various application and realms they derived from) there are many terms:      −* [http://en.wikipedia.org/wiki/Digital_camera#Line-scan_camera_systems line scan]+* [http://en.wikipedia.org/wiki/Digital_camera#Line-scan_camera_systems Line scan] −* [http://en.wikipedia.org/wiki/Slit-scan_photography slit scan]+* [http://en.wikipedia.org/wiki/Slit-scan_photography Slit scan] −* [http://people.rit.edu/andpph/text-strip-basics.html strip photography]+* [http://people.rit.edu/andpph/text-strip-basics.html Strip photography] −* [http://www.bmumford.com/photo/streak/index.html streak photography]+* [http://www.bmumford.com/photo/streak/index.html Streak photography] −* [http://en.wikipedia.org/wiki/Scanography scanography]+* [http://en.wikipedia.org/wiki/Scanography Scanography] −* [http://en.wikipedia.org/wiki/Photo_finish photo-finish]+* [http://en.wikipedia.org/wiki/Photo_finish Photo finish]     Basically they all describe the same principle, a principle that is rather old and was already used in traditional analogue photography (for instance rotating panorama cameras), where you have a slit as an aperture, exposing the film as it moves by. In the digital realm one would cut out slices of existing image footage or – as in case of dedicated line-scan cameras – it is really just a one line sensor (to be correct: that’s true for monochrome cameras, color line-scan cameras normally have either 3 lines – in case of CCD sensor: one for each color – or 2, if the sensor is CMOS using Bayer pattern). Basically they all describe the same principle, a principle that is rather old and was already used in traditional analogue photography (for instance rotating panorama cameras), where you have a slit as an aperture, exposing the film as it moves by. In the digital realm one would cut out slices of existing image footage or – as in case of dedicated line-scan cameras – it is really just a one line sensor (to be correct: that’s true for monochrome cameras, color line-scan cameras normally have either 3 lines – in case of CCD sensor: one for each color – or 2, if the sensor is CMOS using Bayer pattern). Line 35: Line 35:  Applications of these line-scan method include industrial surface scanning, photo-finish, rotating panorama cameras, aerial imaginary, the arts (an interesting overview of art and research related slit-scan approaches can be found here) and certainly many more. Applications of these line-scan method include industrial surface scanning, photo-finish, rotating panorama cameras, aerial imaginary, the arts (an interesting overview of art and research related slit-scan approaches can be found here) and certainly many more.    −==== line-scan with Elphel ====+=== Line scan with Elphel ===    −Since 2005 and the older 333 model, Elphel cameras have a “photo-finish” mode. With its 3Mpix Aptina CMOS sensor Elphel 333 was able so sample around 3072 lines per second. The photo-finsh mode was revived for the current Elphel 353 model with firmware release 8.0.8.7 by end of April 2010. The current 5Mpix Aptina CMOS sensor (width: 2536px) is a bit slower and allows a sample rate of approx. 2300 lines per second – or a line rate of 2.3 kHz (as it seems to be measured in dedicated line-scan cameras).+{| class='wikitable'  +!Camera series  +!Photo finish support  +|-  +|align='center'| 333  +|align='center'| '''+'''  +|-  +|align='center'| 353  +|align='center'| '''+'''  +|-  +|align='center'| 393  +|align='center'| '''+'''  +|}    −In photo-finish mode the camera then samples just lines and delivers composite images as video frames via RTSP network stream or directly to a hard-disc. Programming the camera into line-scan mode is as simple as setting PH_HEIGHT to the desired line height (in pixel):+Since 2005 and the older 333 model, Elphel cameras have a '''“photo-finish”''' mode. With its 3Mpix Aptina CMOS sensor Elphel 333 was able so sample around 3072 lines per second. The photo-finsh mode was revived for the current Elphel 353 model with firmware release 8.0.8.7 by end of April 2010. The current 5Mpix Aptina CMOS sensor (width: 2536px) is a bit slower and allows a sample rate of approx. 2300 lines per second – or a line rate of 2.3 kHz (as it seems to be measured in dedicated line-scan cameras).    −* '''set COMPRESSOR_RUN=0'''+Elphel 353 software is fully ported to the new Elphel 393 generation of camera systems and works for JP4 format. −* '''set PH_HEIGHT=2'''  −* '''set COMPRESSOR_RUN=2'''     − Quick link to access parameters that might be useful: http://192.168.0.9/parsedit.php?WB_EN&AUTOEXP_ON&EXPOS&COMPRESSOR_RUN&TRIG&TRIG_PERIOD&PF_HEIGHT&WOI_HEIGHT&WOI_TOP&WOI_LEFT&WOI_WIDTH+In '''Photo finish''' mode the camera then samples just lines and delivers composite images as video frames via RTSP network stream or directly to a hard-disc.   − For more details see: [[Elphel_353_series_quick_start_guide#Accessing_camera_parameters|accessing camera parameters]]      Due to the Bayer pattern of the sensor the minimal sample height is 2 lines. Due to the Bayer pattern of the sensor the minimal sample height is 2 lines.    −[[File:pf-height.png]]      +===Setup instructions for 393===  +  +  +The instructions are the same as for 353, the key moments are switching to sensor free fun (or reasonable fps) and JP4 format modes.  +393 are set to internal 10fps trigger while 353's sensor is in the free run mode at boot.  +  +=====Examples=====  +* Example 1: 2592x1936, not changing any frame dimensions, sensor is in a free run mode  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5  +** PH_HEIGHT=2  +** COMPRESSOR_RUN=2  +* Example 2: 2592x3872, not changing any frame dimensions, sensor is in a free run mode  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5  +** PH_HEIGHT=2  +** WOI_HEIGHT=3872  +** COMPRESSOR_RUN=2  +  +* Example 3: 2592x1936, not changing any frame dimensions, sensor is triggered from internal counter: 2000fps  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5  +** PH_HEIGHT=2  +** TRIG_PERIOD=50000 (units are in 1/100MHz)  +** TRIG=4  +** COMPRESSOR_RUN=2  +  +  +===Setup instructions for 353===  +  +  +* A link for quick access to parameters that might be required:  + http://192.168.0.9/parsedit.php?WB_EN&AUTOEXP_ON&EXPOS&COMPRESSOR_RUN&TRIG&TRIG_PERIOD&PF_HEIGHT&WOI_HEIGHT&WOI_TOP&WOI_LEFT&WOI_WIDTH  +  +* To switch the camera into the line scan mode:  +** '''COMPRESSOR_RUN=0''' - stop compressor  +** '''PH_HEIGHT=2'''      - switch to line scan mode  +** '''COMPRESSOR_RUN=2''' - restart compressor  +  +{|  +|[[File:pf-height.png|thumb|600px|It is functional]]  +|}  +  +Before changing any image related parameters in this mode it's better to stop the compressor and restart it after everything is set.  +For more details about changing parameters, see [[Elphel_353_series_quick_start_guide#Accessing_camera_parameters|Accessing camera parameters]].     Photo-finish mode per “default” then samples line-pairs as fast as (exposure) settings allow with a maximum rate of approx. 2300 line-pairs per second and a maximum width of the composite frame of 16384px (defined by WOI_HEIGHT). The sensor location that is used as source for these lines is defined by WOI_TOP, WOI_LEFT and WOI_WIDTH. Photo-finish mode per “default” then samples line-pairs as fast as (exposure) settings allow with a maximum rate of approx. 2300 line-pairs per second and a maximum width of the composite frame of 16384px (defined by WOI_HEIGHT). The sensor location that is used as source for these lines is defined by WOI_TOP, WOI_LEFT and WOI_WIDTH. Line 61: Line 111:  * use the camera’s internal [http://wiki.elphel.com/index.php?title=Trigger trigger mode] with TRIG=4 and TRIG_PERIOD settings to generate a regular trigger impulse. (but due to camera’s internal delays in that mode the line rate is a bit less ) * use the camera’s internal [http://wiki.elphel.com/index.php?title=Trigger trigger mode] with TRIG=4 and TRIG_PERIOD settings to generate a regular trigger impulse. (but due to camera’s internal delays in that mode the line rate is a bit less )    −(A common pitfall in trying out photo-finish mode is that one needs to take care of appropriate exposure setting before going into photo-finish mode. If you just start that mode in low light conditions you will end up waiting for frames endlessly – and get the impression the camera does not work anymore)+=====Examples=====  +* Example 1: 2592x1936, not changing any frame dimensions, sensor is in a free run mode  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0  +** PH_HEIGHT=2  +** COMPRESSOR_RUN=2  +* Example 2: 2592x1936, not changing any frame dimensions, sensor is triggered from internal counter: 2000fps  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0  +** PH_HEIGHT=2  +** TRIG_PERIOD=50000 (units are in 1/100MHz)  +** TRIG=4  +** COMPRESSOR_RUN=2  +   +====Important notes====  +* A common pitfall in trying out photo-finish mode is that one needs to take care of appropriate exposure setting before going into photo-finish mode. If you just start that mode in low light conditions you will end up waiting for frames endlessly – and get the impression the camera does not work anymore. For example:  +<font size='2'>  +  Switching to photo finish from 2592x1936 and 50ms exposure to 2592x2 and 2592x1936 composite image will result in waiting for that composite image for 50 seconds (1936/2*50ms).  +</font>     ==== Examples ==== ==== Examples ==== Oleg

← Older revision Revision as of 22:25, 22 January 2018 (18 intermediate revisions by the same user not shown)Line 18: Line 18:  ---- ----    −=== photo-finish / line-scan mode===+==<font color='darkblue'>Photo finish / Line scan mode</font>==    −==== what is line-scan? ====+=== What is line scan? ===    −Line-scan is an image acquisition method that continuously samples (sensor) lines into a composite image. A Flatbed or hand held scanner is essentially also kind of a line-scanner. For some historic reasons (I guess due to the various application and realms they derived from) there a many terms: [http://en.wikipedia.org/wiki/Digital_camera#Line-scan_camera_systems line scan], [http://en.wikipedia.org/wiki/Slit-scan_photography slit scan], [http://people.rit.edu/andpph/text-strip-basics.html strip photography], [http://www.bmumford.com/photo/streak/index.html streak photography], [http://en.wikipedia.org/wiki/Scanography scanography], [http://en.wikipedia.org/wiki/Photo_finish photo-finish],.. Basically they all describe the same principle, a principle that is rather old and was already used in traditional analogue photography (for instance rotating panorama cameras), where you have a slit as an aperture, exposing the film as it moves by. In the digital realm one would cut out slices of existing image footage or – as in case of dedicated line-scan cameras – it is really just a one line sensor (to be correct: that’s true for monochrome cameras, color line-scan cameras normally have either 3 lines – in case of CCD sensor: one for each color – or 2, if the sensor is CMOS using Bayer pattern).+Line-scan is an image acquisition method that continuously samples (sensor) lines into a composite image. A Flatbed or hand held scanner is essentially also kind of a line-scanner. For some historic reasons (I guess due to the various application and realms they derived from) there are many terms:    +   +* [http://en.wikipedia.org/wiki/Digital_camera#Line-scan_camera_systems Line scan]  +* [http://en.wikipedia.org/wiki/Slit-scan_photography Slit scan]  +* [http://people.rit.edu/andpph/text-strip-basics.html Strip photography]  +* [http://www.bmumford.com/photo/streak/index.html Streak photography]  +* [http://en.wikipedia.org/wiki/Scanography Scanography]  +* [http://en.wikipedia.org/wiki/Photo_finish Photo finish]  +   +Basically they all describe the same principle, a principle that is rather old and was already used in traditional analogue photography (for instance rotating panorama cameras), where you have a slit as an aperture, exposing the film as it moves by. In the digital realm one would cut out slices of existing image footage or – as in case of dedicated line-scan cameras – it is really just a one line sensor (to be correct: that’s true for monochrome cameras, color line-scan cameras normally have either 3 lines – in case of CCD sensor: one for each color – or 2, if the sensor is CMOS using Bayer pattern).     Applications of these line-scan method include industrial surface scanning, photo-finish, rotating panorama cameras, aerial imaginary, the arts (an interesting overview of art and research related slit-scan approaches can be found here) and certainly many more. Applications of these line-scan method include industrial surface scanning, photo-finish, rotating panorama cameras, aerial imaginary, the arts (an interesting overview of art and research related slit-scan approaches can be found here) and certainly many more.    −==== line-scan with Elphel ====+=== Line scan with Elphel ===    −Since 2005 and the older 333 model, Elphel cameras have a “photo-finish” mode. With its 3Mpix Aptina CMOS sensor Elphel 333 was able so sample around 3072 lines per second. The photo-finsh mode was revived for the current Elphel 353 model with firmware release 8.0.8.7 by end of April 2010. The current 5Mpix Aptina CMOS sensor (width: 2536px) is a bit slower and allows a sample rate of approx. 2300 lines per second – or a line rate of 2.3 kHz (as it seems to be measured in dedicated line-scan cameras).+{| class='wikitable'  +!Camera series  +!Photo finish support  +|-  +|align='center'| 333  +|align='center'| '''+'''  +|-  +|align='center'| 353  +|align='center'| '''+'''  +|-  +|align='center'| 393  +|align='center'| '''+'''  +|}    −In photo-finish mode the camera then samples just lines and delivers composite images as video frames via RTSP network stream or directly to a hard-disc. Programming the camera into line-scan mode is as simple as setting PH_HEIGHT to the desired line height (in pixel):+Since 2005 and the older 333 model, Elphel cameras have a '''“photo-finish”''' mode. With its 3Mpix Aptina CMOS sensor Elphel 333 was able so sample around 3072 lines per second. The photo-finsh mode was revived for the current Elphel 353 model with firmware release 8.0.8.7 by end of April 2010. The current 5Mpix Aptina CMOS sensor (width: 2536px) is a bit slower and allows a sample rate of approx. 2300 lines per second – or a line rate of 2.3 kHz (as it seems to be measured in dedicated line-scan cameras).    −* '''set COMPRESSOR_RUN=0'''+Elphel 353 software is fully ported to the new Elphel 393 generation of camera systems and works for JP4 format. −* '''set PH_HEIGHT=2'''  −* '''set COMPRESSOR_RUN=2'''     − Quick link to access parameters that might be useful: http://192.168.0.9/parsedit.php?WB_EN&AUTOEXP_ON&EXPOS&COMPRESSOR_RUN&TRIG&TRIG_PERIOD&PF_HEIGHT&WOI_HEIGHT&WOI_TOP&WOI_LEFT&WOI_WIDTH+In '''Photo finish''' mode the camera then samples just lines and delivers composite images as video frames via RTSP network stream or directly to a hard-disc.   − For more details see: [[Elphel_353_series_quick_start_guide#Accessing_camera_parameters|accessing camera parameters]]      Due to the Bayer pattern of the sensor the minimal sample height is 2 lines. Due to the Bayer pattern of the sensor the minimal sample height is 2 lines.    −[[File:pf-height.png]]      +===Setup instructions for 393===  +  +  +The instructions are the same as for 353, the key moments are switching to sensor free fun (or reasonable fps) and JP4 format modes.  +393 are set to internal 10fps trigger while 353's sensor is in the free run mode at boot.  +  +=====Examples=====  +* Example 1: 2592x1936, not changing any frame dimensions, sensor is in a free run mode  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5  +** PH_HEIGHT=2  +** COMPRESSOR_RUN=2  +* Example 2: 2592x3872, not changing any frame dimensions, sensor is in a free run mode  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5  +** PH_HEIGHT=2  +** WOI_HEIGHT=3872  +** COMPRESSOR_RUN=2  +  +* Example 3: 2592x1936, not changing any frame dimensions, sensor is triggered from internal counter: 2000fps  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0, COLOR=5  +** PH_HEIGHT=2  +** TRIG_PERIOD=50000 (units are in 1/100MHz)  +** TRIG=4  +** COMPRESSOR_RUN=2  +  +  +===Setup instructions for 353===  +  +  +* A link for quick access to parameters that might be required:  + http://192.168.0.9/parsedit.php?WB_EN&AUTOEXP_ON&EXPOS&COMPRESSOR_RUN&TRIG&TRIG_PERIOD&PF_HEIGHT&WOI_HEIGHT&WOI_TOP&WOI_LEFT&WOI_WIDTH  +  +* To switch the camera into the line scan mode:  +** '''COMPRESSOR_RUN=0''' - stop compressor  +** '''PH_HEIGHT=2'''      - switch to line scan mode  +** '''COMPRESSOR_RUN=2''' - restart compressor  +  +{|  +|[[File:pf-height.png|thumb|600px|It is functional]]  +|}  +  +Before changing any image related parameters in this mode it's better to stop the compressor and restart it after everything is set.  +For more details about changing parameters, see [[Elphel_353_series_quick_start_guide#Accessing_camera_parameters|Accessing camera parameters]].     Photo-finish mode per “default” then samples line-pairs as fast as (exposure) settings allow with a maximum rate of approx. 2300 line-pairs per second and a maximum width of the composite frame of 16384px (defined by WOI_HEIGHT). The sensor location that is used as source for these lines is defined by WOI_TOP, WOI_LEFT and WOI_WIDTH. Photo-finish mode per “default” then samples line-pairs as fast as (exposure) settings allow with a maximum rate of approx. 2300 line-pairs per second and a maximum width of the composite frame of 16384px (defined by WOI_HEIGHT). The sensor location that is used as source for these lines is defined by WOI_TOP, WOI_LEFT and WOI_WIDTH. Line 52: Line 111:  * use the camera’s internal [http://wiki.elphel.com/index.php?title=Trigger trigger mode] with TRIG=4 and TRIG_PERIOD settings to generate a regular trigger impulse. (but due to camera’s internal delays in that mode the line rate is a bit less ) * use the camera’s internal [http://wiki.elphel.com/index.php?title=Trigger trigger mode] with TRIG=4 and TRIG_PERIOD settings to generate a regular trigger impulse. (but due to camera’s internal delays in that mode the line rate is a bit less )    −(A common pitfall in trying out photo-finish mode is that one needs to take care of appropriate exposure setting before going into photo-finish mode. If you just start that mode in low light conditions you will end up waiting for frames endlessly – and get the impression the camera does not work anymore)+=====Examples=====  +* Example 1: 2592x1936, not changing any frame dimensions, sensor is in a free run mode  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0  +** PH_HEIGHT=2  +** COMPRESSOR_RUN=2  +* Example 2: 2592x1936, not changing any frame dimensions, sensor is triggered from internal counter: 2000fps  +** COMPRESSOR_RUN=0, WB_EN=0, AUTOEXP_ON=0, EXPOS=400, TRIG=0  +** PH_HEIGHT=2  +** TRIG_PERIOD=50000 (units are in 1/100MHz)  +** TRIG=4  +** COMPRESSOR_RUN=2  +   +====Important notes====  +* A common pitfall in trying out photo-finish mode is that one needs to take care of appropriate exposure setting before going into photo-finish mode. If you just start that mode in low light conditions you will end up waiting for frames endlessly – and get the impression the camera does not work anymore. For example:  +<font size='2'>  +  Switching to photo finish from 2592x1936 and 50ms exposure to 2592x2 and 2592x1936 composite image will result in waiting for that composite image for 50 seconds (1936/2*50ms).  +</font>     ==== Examples ==== ==== Examples ==== Oleg