Reuest for Quote LWIR-16
Reuest for Quote LWIR-16
Reuest for Quote LWIR-16
Created page with "Elphel, Inc. invites the machine shops to Quote manufacturing of the following parts: {| class="wikitable" style="background:#fcfcfc; " border="1" |+ Camera Metal Parts |- !..."
New page
Elphel, Inc. invites the machine shops to Quote manufacturing of the following parts:{| class="wikitable" style="background:#fcfcfc; " border="1"
|+ Camera Metal Parts
|-
! Part !! Description !! QTY 1 !! Notes
|-
| [[Elphel_camera_parts_0393-13#0393-13-14A_-_Half-plate_for_SFE_mount.2C_Rev_A|0393-13-14A ]] || Half-plate for SFE mount, Rev A || 3 ||
|-
| [[Elphel_camera_parts_0393-13#0393-13-15C_-_Sensor_Assembly_Cover.2C_rev_CB|0393-13-15C ]] || Sensor Assembly Cover, rev C || 3 ||
|- Olga
Request for Quote 353
Request for Quote 353
Request for Quote 353
Created page with "Elphel, Inc. invites the machine shops to Quote manufacturing of the following parts: {| class="wikitable" style="background:#fcfcfc; " border="1" |+ Camera Metal Parts |- !..."
New page
Elphel, Inc. invites the machine shops to Quote manufacturing of the following parts:{| class="wikitable" style="background:#fcfcfc; " border="1"
|+ Camera Metal Parts
|-
! Part !! Description !! QTY 1 !! Notes
|-
| [[Elphel_camera_parts_0353-12#0353-12-29_-_Sensor_Front_End.2C_CS-mount|0353-12-29 ]] || Sensor Front End, CS-mount || 20 ||
|-
| [[Elphel_camera_parts_0353-12#0353-12-30_-_Sensor_Adjustment_Plate|0353-12-30 ]]|| Sensor Adjustment Plate || 20 ||
|-
| [[Elphel_camera_parts_0353-18#0353-18-02_-_connector_cover|0353-18-02 ]]|| connector cover || 30 ||
|-
| [[Elphel_camera_parts_0353-20#0353-20-04_-_Spacer_for_tripod_mount|0353-20-04 ]]|| Spacer for tripod mount || 20 ||
|-
| [[Elphel_camera_parts_0353-11#0353-11-02_-_camera_top_with_connector_holes_for_the_10369_.28serial_port.2C_optoisolated_I.2FO.29.2C_l.3D104.77mm|0353-11-02]]|| camera top with connector holes for the 10369 || 30 ||
|-
| [[Elphel_camera_parts_0353-10#0353-10-02_-_Camera_Bottom.2C_l.3D104.77mm|0353-10-02]]|| Camera Bottom, l=104.77mm || 30 ||
|- Olga
103891
Added A-D description
← Older revision Revision as of 20:02, 9 July 2023 (One intermediate revision by the same user not shown)Line 19: Line 19: Connector provides high-current (up to 0.5A) dc-coupled 5V output and optoisolated I/O. When optoisolated pair is used used as an input (common use), external signal is applied between XSYNC1 (+) and XSYNC2(-). When the pair is used as an output (less common), external 5V power source should be connected in series with the receiver and 103891, so that "+" will be applied to XSYNC2, and "-" - to XSYNC1 (opposite to the input mode). Details are available in the circuit diagram of the [[10389]] board. Connector provides high-current (up to 0.5A) dc-coupled 5V output and optoisolated I/O. When optoisolated pair is used used as an input (common use), external signal is applied between XSYNC1 (+) and XSYNC2(-). When the pair is used as an output (less common), external 5V power source should be connected in series with the receiver and 103891, so that "+" will be applied to XSYNC2, and "-" - to XSYNC1 (opposite to the input mode). Details are available in the circuit diagram of the [[10389]] board. −Output synchronization can be just a pulse or carry additional timestamp data when used to synchronize multiple NC393 cameras. See [[Trigger_393]] for the settings.+Output synchronization can be just a pulse or carry additional timestamp data when used to synchronize multiple NC393 cameras. See [[Trigger_393]] for the settings. Pin A is the tip, B - next, then C and D is the closest to the connector housing. {| class='wikitable' {| class='wikitable' |+Connector pinout |+Connector pinout Line 28: Line 28: |- |- |XSYNC1 |XSYNC1 −|1+|1 (D) |black |black |optoisolated, "+" input with respect to XSYNC2 |optoisolated, "+" input with respect to XSYNC2 |- |- |SYNC_DRV |SYNC_DRV −|2+|2 (A) |red |red |Sync output (DC-coupled), +5V pulses with respect to GND |Sync output (DC-coupled), +5V pulses with respect to GND |- |- |GND |GND −|3+|3 (B) |white |white |Output reference, connected to the camera system ground |Output reference, connected to the camera system ground |- |- |XSYNC2 |XSYNC2 −|4+|4 (C) |green |green |optoisolated, "-" input with respect to XSYNC1 |optoisolated, "-" input with respect to XSYNC1 Andrey.filippovPoky manual
Setup
← Older revision Revision as of 19:22, 1 June 2022 (2 intermediate revisions by the same user not shown)Line 91: Line 91: * Before building * Before building Installing some dependencies: Installing some dependencies: − sudo apt install git build-essential chrpath diffstat gawk makeinfo zlib1g-dev python3-numpy+ sudo apt install git build-essential chrpath diffstat gawk texinfo zlib1g-dev python3-numpy libssl-dev Installing old python2.7 (bitbake snapshot that we used has problem with python3.8): Installing old python2.7 (bitbake snapshot that we used has problem with python3.8): sudo apt install python2.7 sudo apt install python2.7 Line 123: Line 123: * Notes (required actions are already listed above): When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it: * Notes (required actions are already listed above): When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it: − sudo apt install python2.7+ sudo apt install python2.7 python-numpy sudo ln -s python2.7 python2 sudo ln -s python2.7 python2 sudo ln -s python2.7 python sudo ln -s python2.7 python Andrey.filippovPoky manual
Setup
← Older revision Revision as of 17:18, 1 June 2022 (One intermediate revision by the same user not shown)Line 91: Line 91: * Before building * Before building Installing some dependencies: Installing some dependencies: − sudo apt install git build-essential chrpath diffstat gawk makeinfo zlib1g-dev python3-numpy+ sudo apt install git build-essential chrpath diffstat gawk texinfo zlib1g-dev python3-numpy Installing old python2.7 (bitbake snapshot that we used has problem with python3.8): Installing old python2.7 (bitbake snapshot that we used has problem with python3.8): sudo apt install python2.7 sudo apt install python2.7 Line 123: Line 123: * Notes (required actions are already listed above): When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it: * Notes (required actions are already listed above): When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it: − sudo apt install python2.7+ sudo apt install python2.7 python-numpy sudo ln -s python2.7 python2 sudo ln -s python2.7 python2 sudo ln -s python2.7 python sudo ln -s python2.7 python Andrey.filippovAdjusting sensor clock phase
Software interface for adjusting the sensor clock phase (firmware 8.0.x)
← Older revision Revision as of 22:06, 1 May 2022 (One intermediate revision by the same user not shown)Line 16: Line 16: === Software interface for adjusting the sensor clock phase (firmware 8.0.x) === === Software interface for adjusting the sensor clock phase (firmware 8.0.x) === Open the following URL in the browser (replace 192.168.0.9 if camera has different IP): Open the following URL in the browser (replace 192.168.0.9 if camera has different IP): −http://192.168.0.9/parsedit.php?embed=0.15&title=Parameters+for+groups:+phase&SENSOR_PHASE&SENSOR_REGS7&SENSOR_REGS7__0310&SENSOR_REGS7__0307&WOI_HEIGHT&refresh+ + [http://192.168.0.9/parsedit.php?embed=0.25&title=Parameters+for+groups:+phase&SENSOR_PHASE&SENSOR_REGS7&SENSOR_REGS7__0310&SENSOR_REGS7__0307&WOI_HEIGHT&WB_EN&THIS_FRAME http://192.168.0.9/parsedit.php?embed=0.25&title=Parameters+for+groups:+phase&SENSOR_PHASE&SENSOR_REGS7&SENSOR_REGS7__0310&SENSOR_REGS7__0307&WOI_HEIGHT&WB_EN&THIS_FRAME] That page combines several controls: That page combines several controls: Andrey.filippov10393 manual
Firmware images
← Older revision Revision as of 17:49, 12 April 2022 (One intermediate revision by the same user not shown)Line 354: Line 354: ==<font color="blue">Firmware images</font>== ==<font color="blue">Firmware images</font>== −* [https://community.elphel.com/files/393/20210628/ '''20210628''']+* [https://community.elphel.com/files/393/20220412/ '''20220412'''] +* [https://community.elphel.com/files/393/20210628/ 20210628] * [https://community.elphel.com/files/393/20200903/ 20200903] * [https://community.elphel.com/files/393/20200903/ 20200903] * [https://community.elphel.com/files/393/20200520/ 20200520] * [https://community.elphel.com/files/393/20200520/ 20200520] Line 360: Line 361: ===Changelog=== ===Changelog=== + <font size='1'>'''==20220412==''' + * Added websockets test + * More options in format_disk (single partition, reformat already formatted disk,...) + * Bug fixes <font size='1'>'''==20210628==''' <font size='1'>'''==20210628==''' * Added support for FLIR Boson sensors * Added support for FLIR Boson sensors Andrey.filippovTrigger 393
External connector
← Older revision Revision as of 18:45, 10 April 2022 Line 118: Line 118: software: frame counter is running software: frame counter is running −* It's easy to modify the cable to trigger itself and other multiple cameras.+* It's easy to modify the cable to trigger itself and other multiple cameras by connecting together red and black wires (+) and white with green (-). For self-testing (external trigger loop back) it is sufficient, for LED - connect anode to "+" (red+black), cathode - to "-" (white+green). {| {| |[[File:10389 extsync selftest.jpeg|thumb|400px]] |[[File:10389 extsync selftest.jpeg|thumb|400px]] |} |} + +Turn on external trigger loop back (cable should be inserted): + http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0x80000&TRIG_OUT=0x66555&TRIG_PERIOD=25000000&TRIG=4 + +Or use interactive page: + http://192.168.0.9/parsedit.php?sensor_port=0&embed=0.25&title=Parameters+for+groups:+trigger+&TRIG&TRIG_MASTER&TRIG_CONDITION=0x80000&TRIG_DELAY&TRIG_OUT=0x66555&TRIG_PERIOD=25000000&TRIG_BITLENGTH&EXTERN_TIMESTAMP&XMIT_TIMESTAMP&TRIG_DECIMATE&THIS_FRAME&refresh + +And then click "Apply" button. + +Both variants should turn camera into external loop back mode with 0.25s period (4 fps). If the page (and the camera) hangs, the loop is not working. For troubleshooting you may restart the camera, open + http://192.168.0.9/parsedit.php?sensor_port=0&embed=0.25&title=Parameters+for+groups:+trigger+&TRIG&TRIG_MASTER&TRIG_CONDITION=0&TRIG_DELAY&TRIG_OUT=0x66555&TRIG_PERIOD=25000000&TRIG_BITLENGTH&EXTERN_TIMESTAMP&XMIT_TIMESTAMP&TRIG_DECIMATE&THIS_FRAME&refresh + +and press "apply". The camera will continue using internal trigger (TRIG_CONDITION=0) but still generate trigger output (TRIG_OUT=0x66555). This output can be controlled by either the LED soldered to the cable or the oscilloscope (ground to the green+white, signal - red+black - it should show not just a pulse but a encoded timestamp some 22us long. Changing TRIG_CONDITION to 0x80000 (enter 80000 into "New value/Hex" field without "0x" and press "Apply") should activate loop back, and if it works then "Refresh" button should cause new "THIS_FRAME" field value. If it does not work - trigger input does not reach camera - bad cable or connector. ===Internal connectors=== ===Internal connectors=== Andrey.filippovPoky manual
Setup
← Older revision Revision as of 21:00, 27 January 2022 Line 100: Line 100: <font size='2'> <font size='2'> git clone -b '''warrior''' https://git.elphel.com/Elphel/elphel393.git git clone -b '''warrior''' https://git.elphel.com/Elphel/elphel393.git + +If you are a developer and plan to commit changes you should use ssh access instead: git clone -b warrior git@git.elphel.com:Elphel/elphel393.git + + cd elphel393 cd elphel393 ./setup.py ./setup.py Andrey.filippovUsing minicom to connect to Elphel393 camera
Poky manual
Setup
← Older revision Revision as of 22:26, 26 January 2022 (5 intermediate revisions by the same user not shown)Line 89: Line 89: ==<font color="blue">Setup</font>== ==<font color="blue">Setup</font>== +* Before building +Installing some dependencies: + sudo apt install git build-essential chrpath diffstat gawk makeinfo zlib1g-dev python3-numpy +Installing old python2.7 (bitbake snapshot that we used has problem with python3.8): + sudo apt install python2.7 + sudo ln -s python2.7 python2 + sudo ln -s python2.7 python * Poky 2.7.1 Warrior (Kubuntu 20.04) * Poky 2.7.1 Warrior (Kubuntu 20.04) Line 110: Line 117: <!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--> <!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--> </font></s> </font></s> + +* Notes (required actions are already listed above): When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it: + sudo apt install python2.7 + sudo ln -s python2.7 python2 + sudo ln -s python2.7 python + +After this bitbake just complained about missing tools (git, build-essential were already installed): + + sudo apt install chrpath diffstat gawk makeinfo + +Program test_mcntrl.py that builds x393.h header files from FPGA code that runs during ./setup.py requires numpy and results in error output if missing Still setup.py continues, you need to look through its output few lines after + * x393 + git host: git.elphel.com + Clone and checkout: x393 + +You may install numpy with + sudo apt install python3-numpy + +If you did not notice missing numpy, then during bitbake you will get error "build No rule to make target 'drivers/elphel/x393.o', needed by 'drivers/elphel/built-in.a'. Stop." in that case you need to install numpy, re-run setup.py (make sure numpy error is gone) then re-create linux kernel links during next build by erasing old ones: + bitbake linux-xlnx -c clean +and re-running + bitbake linux-xlnx device-tree core-image-elphel393 + +When building php: configure: error: zip support requires ZLIB. Use --with-zlib-dir=<DIR> to specify prefix where ZLIB include and library are located + sudo apt install zlib1g-dev ==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>== ==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>== Andrey.filippovPoky manual
Setup
← Older revision Revision as of 22:12, 26 January 2022 (3 intermediate revisions by the same user not shown)Line 110: Line 110: <!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--> <!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--> </font></s> </font></s> + +* Notes: When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it: + sudo apt install python2.7 + sudo ln -s python2.7 python2 + sudo ln -s python2.7 python + +After this bitbake just complained about missing tools (git, build-essential were already installed): + + sudo apt install chrpath diffstat gawk makeinfo + +Program test_mcntrl.py that builds x393.h header files from FPGA code that runs during ./setup.py requires numpy and results in error output if missing Still setup.py continues, you need to look through its output few lines after + * x393 + git host: git.elphel.com + Clone and checkout: x393 + +You may install numpy with + sudo apt install python3-numpy + +If you did not notice missing numpy, then during bitbake you will get error "build No rule to make target 'drivers/elphel/x393.o', needed by 'drivers/elphel/built-in.a'. Stop." in that case you need to install numpy, re-run setup.py (make sure numpy error is gone) then re-create linux kernel links during next build by erasing old ones: + bitbake linux-xlnx -c clean +and re-running + bitbake linux-xlnx device-tree core-image-elphel393 + +When building php: configure: error: zip support requires ZLIB. Use --with-zlib-dir=<DIR> to specify prefix where ZLIB include and library are located + sudo apt install zlib1g-dev ==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>== ==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>== Andrey.filippovPoky manual
Setup
← Older revision Revision as of 20:19, 26 January 2022 Line 110: Line 110: <!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--> <!--''Temporary: linux-xlnx in Rocko depends on branch 'lwir' for x393. Change in projects.json line 42 from 'master' to 'lwir'.''--> </font></s> </font></s> + +* Notes: When trying to run bitbake on a new install got problems with older bitbake version (current build uses specific snapshot) and python3.8. So I install old python2.7 and linked it: + sudo apt install python2.7 + sudo ln -s python2.7 python2 + sudo ln -s python2.7 python + +After this bitbake just complained about missing tools (git, build-essential were already installed): + + sudo apt install chrpath diffstat gawk makeinfo ==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>== ==<font color="blue">Compare '''built''' vs '''deployed''' software versions</font>== Andrey.filippov