← Older revision Revision as of 02:15, 12 January 2018 Line 1: Line 1: −{{Legacy}} See similar current products here: [[10393]]+{{Legacy}}  +See current products here: [[10393]]  == Elphel 353/363 series cameras and camera modules == == Elphel 353/363 series cameras and camera modules ==    Andrey.filippov

← Older revision Revision as of 02:15, 12 January 2018 (One intermediate revision by the same user not shown)Line 1: Line 1: −{{Legacy}} See similar current products here: [[10393]]+{{Legacy}}  +See current products here: [[10393]]  == Elphel 353/363 series cameras and camera modules == == Elphel 353/363 series cameras and camera modules ==    Line 27: Line 28:  [[Image:Prototype363_detail.jpeg|frame|[[Media:Prototype363.jpeg|Detail of one of the first images acquired with Elphel Model 363 camera (click here for the full image)]]]] [[Image:Prototype363_detail.jpeg|frame|[[Media:Prototype363.jpeg|Detail of one of the first images acquired with Elphel Model 363 camera (click here for the full image)]]]]    −There is a new series of Elphel cameras that continue the line of 303, 313/323 and 333 - it is 353/363 now.+Goolge loves obsolete products: There is a new series of Elphel cameras that continue the line of 303, 313/323 and 333 - it is 353/363 now.  * Elphel Model 353 cameras are designed for video applications, use small format (usually - 1/2") high-resolution CMOS sensors and C/CS mount lenses * Elphel Model 353 cameras are designed for video applications, use small format (usually - 1/2") high-resolution CMOS sensors and C/CS mount lenses  * Model 363 use large format CCD imagers, have higher resolution and lower frame rate - they acquire and send individual images. These cameras use 35 mm (or larger) format lenses. * Model 363 use large format CCD imagers, have higher resolution and lower frame rate - they acquire and send individual images. These cameras use 35 mm (or larger) format lenses. Andrey.filippov

Oleg Dzhimiev committed changes to the Elphel git project :
turned off debug

Oleg Dzhimiev committed changes to the Elphel git project :
added frame in video buffer selecting

Oleg Dzhimiev committed changes to the Elphel git project :
fixed image dimensions back

Oleg Dzhimiev committed changes to the Elphel git project :
fixed image sizes

Oleg Dzhimiev committed changes to the Elphel git project :
+ run membridge via sysfs file

‎Specs

← Older revision Revision as of 02:15, 11 January 2018 Line 27: Line 27:  [[Image:Prototype363_detail.jpeg|frame|[[Media:Prototype363.jpeg|Detail of one of the first images acquired with Elphel Model 363 camera (click here for the full image)]]]] [[Image:Prototype363_detail.jpeg|frame|[[Media:Prototype363.jpeg|Detail of one of the first images acquired with Elphel Model 363 camera (click here for the full image)]]]]    −There is a new series of Elphel cameras that continue the line of 303, 313/323 and 333 - it is 353/363 now.+Goolge loves obsolete products: There is a new series of Elphel cameras that continue the line of 303, 313/323 and 333 - it is 353/363 now.  * Elphel Model 353 cameras are designed for video applications, use small format (usually - 1/2") high-resolution CMOS sensors and C/CS mount lenses * Elphel Model 353 cameras are designed for video applications, use small format (usually - 1/2") high-resolution CMOS sensors and C/CS mount lenses  * Model 363 use large format CCD imagers, have higher resolution and lower frame rate - they acquire and send individual images. These cameras use 35 mm (or larger) format lenses. * Model 363 use large format CCD imagers, have higher resolution and lower frame rate - they acquire and send individual images. These cameras use 35 mm (or larger) format lenses. Andrey.filippov

Oleg Dzhimiev committed changes to the Elphel git project :
fixed spinlocks

Oleg Dzhimiev committed changes to the Elphel git project :
simplified lseek

Oleg Dzhimiev committed changes to the Elphel git project :
added mmap

Oleg Dzhimiev committed changes to the Elphel git project :
gcc,cpp,g++,make

Oleg Dzhimiev committed changes to the Elphel git project :
added spinlock

‎Connection

← Older revision Revision as of 21:37, 10 January 2018 Line 17: Line 17:  [[File:10359top.jpeg|thumb|200px|Fig.2 10359 mux board (older revision)]] [[File:10359top.jpeg|thumb|200px|Fig.2 10359 mux board (older revision)]]    −* <font color='red'>'''if the number of connected mux boards is 4 and 10389+SSD then extra power is needed'''</font>:  +* <font color='red'>'''if the number of connected mux boards is 1+ and internal SSD is used then extra power is needed'''</font> (a lot depends on SSD power consumption):    quick mod: see Fig.2   quick mod: see Fig.2    lift pins 3,4 on J1, put teflon tape under them and solder a wire to those lifted pins connected. Then add a MOS transistor or a switch that will apply external 3.3 V to W2 when those J1.3, J1.4 have     lift pins 3,4 on J1, put teflon tape under them and solder a wire to those lifted pins connected. Then add a MOS transistor or a switch that will apply external 3.3 V to W2 when those J1.3, J1.4 have   Oleg

Oleg Dzhimiev committed changes to the Elphel git project :
+waitFrame function

‎10359

← Older revision Revision as of 19:15, 10 January 2018 Line 10: Line 10:     [[Image:10359 current clock tree.png|thumb|500px|10359 current clock tree]] [[Image:10359 current clock tree.png|thumb|500px|10359 current clock tree]] −10359 is an optional multi-function board for [[353|Elplhel Model 353/363 Cameras]]. It can be connected between the [[10353|10353 Processor board]] and a sensor one (up to three sensor boards can be connected)+10359 is an optional multi-function board for [[10393|'''Elphel Model 393 Cameras''']] and [[353|Elphel Model 353/363 Cameras]]. For 10393, also see [[Using_10359_mux_with_10393|using 10359 with 10393]].  +It can be connected between the [[10353|10353 Processor board]] and a sensor one (up to three sensor boards can be connected)  This board has the same FPGA-DDR SDRAM pair as on the 10353 (Processor) board. It uses just one extra conductor in the flex cable to configure the on-board FPGA, rest of the JTAG programming interface pins share connections with the data signals. This board can fit in the standard camera enclosure (when only one sensor board is used) and does not interfere with the boards that use inter-board connectors (i.e. 10357) - the 10359 is mounted on the other side of the 10353 board. This board has the same FPGA-DDR SDRAM pair as on the 10353 (Processor) board. It uses just one extra conductor in the flex cable to configure the on-board FPGA, rest of the JTAG programming interface pins share connections with the data signals. This board can fit in the standard camera enclosure (when only one sensor board is used) and does not interfere with the boards that use inter-board connectors (i.e. 10357) - the 10359 is mounted on the other side of the 10353 board.    Oleg

← Older revision Revision as of 18:47, 10 January 2018 Line 17: Line 17:  [[File:10359top.jpeg|thumb|200px|Fig.2 10359 mux board (older revision)]] [[File:10359top.jpeg|thumb|200px|Fig.2 10359 mux board (older revision)]]    −* if the number of connected mux boards is 4 and 10389+SSD then extra power is needed:  +* <font color='red'>'''if the number of connected mux boards is 4 and 10389+SSD then extra power is needed'''</font>:      quick mod: see Fig.2   quick mod: see Fig.2    lift pins 3,4 on J1, put teflon tape under them and solder a wire to those lifted pins connected. Then add a MOS transistor or a switch that will apply external 3.3 V to W2 when those J1.3, J1.4 have     lift pins 3,4 on J1, put teflon tape under them and solder a wire to those lifted pins connected. Then add a MOS transistor or a switch that will apply external 3.3 V to W2 when those J1.3, J1.4 have   Oleg

‎Links

← Older revision Revision as of 18:46, 10 January 2018 Line 103: Line 103:  ==Links== ==Links==  *[[10389|10389 board]] *[[10389|10389 board]]  +*[[Using_10359_mux_with_10393|Using 10393 with multiplexer boards 10359]]     ==Known issues== ==Known issues== Oleg

Oleg Dzhimiev committed changes to the Elphel git project :
static declaration followed non-static

Oleg Dzhimiev committed changes to the Elphel git project :
started implementing lseek