← Older revision Revision as of 21:27, 7 December 2016 Line 1: Line 1: ==10385B== ==10385B==  +Note: 9-36V modification requires more changes than replacing a DC-DC converter.  +  +[[Image:10385_bottom_sm.png|frame|[[Media:10385_bottom.png|bottom view]]]]  +[[Image:10385_18-75V_top_sm.png|frame|[[Media:10385_18-75V_top.png|18-75V, top view]]]]  +[[Image:10385_9-36V_top_sm.png|frame|[[Media:10385_9-36V_top.png|9-36V, top view]]]] ==Links== ==Links== * [[Media:10385b.pdf|10385 Rev B Circuit Diagram, Parts List, PCB layout]] * [[Media:10385b.pdf|10385 Rev B Circuit Diagram, Parts List, PCB layout]] * [[Media:10385b gerber.tar.gz|10385B Gerber files]] * [[Media:10385b gerber.tar.gz|10385B Gerber files]] Oleg

uploaded "[[File:10385 9-36V top sm.png]]"

Oleg

Created page with "==10385B== ==Links== * 10385 Rev B Circuit Diagram, Parts List, PCB layout * 10385B Gerber files"

New page

==10385B==
==Links==
* [[Media:10385b.pdf|10385 Rev B Circuit Diagram, Parts List, PCB layout]]
* [[Media:10385b gerber.tar.gz|10385B Gerber files]] Andrey.filippov

uploaded "[[File:10385b gerber.tar.gz]]"

Andrey.filippov

← Older revision Revision as of 19:54, 6 December 2016 (4 intermediate revisions not shown)Line 36: Line 36: ===How to record log on the camera=== ===How to record log on the camera===  +====over network==== (see http://192.168.0.9/logger_launcher.php source for options and details): (see http://192.168.0.9/logger_launcher.php source for options and details): * START: http://192.168.0.9/logger_launcher.php?file=/absolute_path/name.log&index=1&n=10000000&mount_point=/absolute_path * START: http://192.168.0.9/logger_launcher.php?file=/absolute_path/name.log&index=1&n=10000000&mount_point=/absolute_path   mount_point=/absolute_path - the path at which the storage is mounted (usb or nfs)   mount_point=/absolute_path - the path at which the storage is mounted (usb or nfs) * STOP:  http://192.168.0.9/phpshell.php?command=killall%20-1%20log_imu * STOP:  http://192.168.0.9/phpshell.php?command=killall%20-1%20log_imu  +====from command line (10393)====  +* START:  + mkdir /www/pages/logs  + cat /dev/imu > /www/pages/logs/test.log  +* STOP:  + CTRL-C or killall cat  +  +===View recorded logs (read_imu_log.php)===  +====from 10393s camera====  +<b>http://192.168.0.9/read_imu_log.php</b>  +* looks for logs in <i>/www/pages/logs</i> (automatically created on the first access)  +* displays and filters messages - EXT, GPS (NMEA GPVTG, GPGSA, GPGGA, GPRMC), IMU, IMG (4 ports)  +* can convert a log to a CSV file (is saved to PC) ===Notes=== ===Notes=== Oleg

Boot:

← Older revision Revision as of 02:19, 30 November 2016 Line 26: Line 26: Normally camera boots from the internal NAND flash memory, and it is always possible to boot it from the micro SD card, so even corruption of files on the internal flash will not "brick" the system. There are no buttons or switches on the camera and the camera should be instructed to change the boot source. Always booting from micro SD is not practical - in that case it would not be possible to leave a non-bootable card (intended just for image/video storage) in the camera slot. Normally camera boots from the internal NAND flash memory, and it is always possible to boot it from the micro SD card, so even corruption of files on the internal flash will not "brick" the system. There are no buttons or switches on the camera and the camera should be instructed to change the boot source. Always booting from micro SD is not practical - in that case it would not be possible to leave a non-bootable card (intended just for image/video storage) in the camera slot. -There are two ways to switch camera to the micro SD boot mode. One requires camera to be connected to the host computer with the USB cable (micro USB socket under the network jack - marked "console" on the picture). There is an internal USB-to-serial converter in the camera (CP2103) that offers 4 additional GPIO signals in addition to just the serial connection. One of these signals selects the boot source (GPIO0 - 0 - MMC, 1 - NAND), another (GPIO3 - 0 reset, 1 - normal operation). Unfortunately GPIO control of the CP2103 is not in a mainline cp210x Linux driver so this functionality requires a mudified version (see instructions below).+There are two ways to switch camera to the micro SD boot mode. One requires camera to be connected to the host computer with the USB cable (micro USB socket under the network jack - marked "console" on the picture). There is an internal USB-to-serial converter in the camera (CP2103) that offers 4 additional GPIO signals in addition to just the serial connection. One of these signals selects the boot source (GPIO0 - 0 - MMC, 1 - NAND), another (GPIO3 - 0 reset, 1 - normal operation). Unfortunately GPIO control of the CP2103 is not in a mainline cp210x Linux driver so this functionality requires a modified version (see instructions below). Another way to "tell" the camera to boot from the &mu;SD card instead of the internal NAND flash is to use a mechanically modified card or card adapter (such cards are provided with the camera). Standard specifies two alternative ways for detection of the card presence - one is a mechanical switch (closed when the card is inserted), another is a pull-up resistor on a data line. Camera uses both signals at boot time to determine the boot source: Another way to "tell" the camera to boot from the &mu;SD card instead of the internal NAND flash is to use a mechanically modified card or card adapter (such cards are provided with the camera). Standard specifies two alternative ways for detection of the card presence - one is a mechanical switch (closed when the card is inserted), another is a pull-up resistor on a data line. Camera uses both signals at boot time to determine the boot source: Oleg

← Older revision Revision as of 20:14, 25 November 2016 Line 73: Line 73:   git clone https://github.com/Elphel/elphel393.git   git clone https://github.com/Elphel/elphel393.git   cd elphel393   cd elphel393 -  ./setup.sh dev+  ./setup.py   cd poky   cd poky   . ./oe-init-build-env   . ./oe-init-build-env Oleg

← Older revision Revision as of 21:46, 21 November 2016 (One intermediate revision not shown)Line 2: Line 2: [[Image:103695.jpeg|frame|[[Media:103695a.pdf|103695A  Circuit Diagram, Parts List, PCB layout]]&nbsp;&nbsp;&nbsp;&nbsp; [[Media:103695a_gerber.tar.gz|103695A Gerber files]]]] [[Image:103695.jpeg|frame|[[Media:103695a.pdf|103695A  Circuit Diagram, Parts List, PCB layout]]&nbsp;&nbsp;&nbsp;&nbsp; [[Media:103695a_gerber.tar.gz|103695A Gerber files]]]] === Description === === Description === -103695 is an adapter board used with the [[10369]] interface board to connect [http://www.analog.com Analog Devices] inertial measurement units (IMU) such as ([http://www.analog.com/en/mems-sensors/imu/adis16375/products/product.html ADIS-16375], [http://www.analog.com/en/mems-sensors/inertial-sensors/adis16405/products/product.html ADIS-16405] and similar to the [[353 | Elphel Model 353 camera]].+103695 is an adapter board used to connect [http://www.analog.com/en/products/mems/inertial-measurement-units.html Analog Devices Inertial Measurement Units (IMUs)] to Elphel products. -Adapter uses two general purpose I/O of the camera FPGA, available on each of the [[10369]] USB/extension connectors J9..J11. The 103695 board provides 3.3V/5.0V power to the IMU (selectable by on-board resistors) and supports different speed SPI interface to the sensor unit. The device connector (J2) can accommodate a number of Analog Devices units, it should be possible to use the board with connector adapter with other SPI sensors.+Adapter uses two general purpose I/O of the camera FPGA available on each of the USB/extension connectors. The 103695 board provides 3.3V/5.0V power to the IMU (selectable by on-board resistors) and supports different speed SPI interface to the sensor unit. The device connector (J2) can accommodate a number of Analog Devices units, it should be possible to use the board with connector adapter with other SPI sensors. Camera interface to the 103695 board is implemented in the FPGA (starting with firmware revision 8.1.0). Up to 28 different 16-bit registers (plus 8 bytes of the timestamp with 1 microsecond resolution) are periodically addressed, read and stored in the  camera system memory over the DMA channel. The The logged register addresses are programmed at run time in the FPGA using the device driver. Camera interface to the 103695 board is implemented in the FPGA (starting with firmware revision 8.1.0). Up to 28 different 16-bit registers (plus 8 bytes of the timestamp with 1 microsecond resolution) are periodically addressed, read and stored in the  camera system memory over the DMA channel. The The logged register addresses are programmed at run time in the FPGA using the device driver.  +  +=== Compatibility ===  +====Elphel====  +{|  class="wikitable" style="background:#fcfcfc; "  border="1"  +! Camera series !! Interface board, connectors !! Support  +|-  +|align='center'|[[10393|10393]]  +|align='center'|[[10389]], J8,J9  +|align='center'|+  +|-  +|align='center'|[[353|10353]]  +|align='center'|[[10369]], J9..J11  +|align='center'|+  +|}  +  +====Analog Devices====  +{|  class="wikitable" style="background:#fcfcfc; "  border="1"  +! IMU !! Tested  +|-  +|align='center'|[http://www.analog.com/en/mems-sensors/imu/adis16375/products/product.html ADIS-16375]  +|align='center'|+  +|-  +|align='center'|[http://www.analog.com/en/mems-sensors/inertial-sensors/adis16405/products/product.html ADIS-16405]  +|align='center'|+  +|}  +  +<b>NOTE:</b> All IMUs have compatible interface and most likely will work with Elphel products. === Connectors === === Connectors === Oleg

103695 - IMU Adapter Board:

← Older revision Revision as of 21:21, 21 November 2016 Line 2: Line 2: [[Image:103695.jpeg|frame|[[Media:103695a.pdf|103695A  Circuit Diagram, Parts List, PCB layout]]&nbsp;&nbsp;&nbsp;&nbsp; [[Media:103695a_gerber.tar.gz|103695A Gerber files]]]] [[Image:103695.jpeg|frame|[[Media:103695a.pdf|103695A  Circuit Diagram, Parts List, PCB layout]]&nbsp;&nbsp;&nbsp;&nbsp; [[Media:103695a_gerber.tar.gz|103695A Gerber files]]]] === Description === === Description === -103695 is an adapter board used with the [[10369]] interface board to connect [http://www.analog.com Analog Devices] inertial measurement units (IMU) such as ([http://www.analog.com/en/mems-sensors/imu/adis16375/products/product.html ADIS-16375], [http://www.analog.com/en/mems-sensors/inertial-sensors/adis16405/products/product.html ADIS-16405] and similar to the [[353 | Elphel Model 353 camera]].+103695 is an adapter board used with the [[10389]]/[[10369]] interface boards to connect [http://www.analog.com Analog Devices] inertial measurement units (IMU) such as ([http://www.analog.com/en/mems-sensors/imu/adis16375/products/product.html ADIS-16375], [http://www.analog.com/en/mems-sensors/inertial-sensors/adis16405/products/product.html ADIS-16405] or similar (in short, all other are compatible but not tested) to the [[10393 | Elphel Model 393 camera]]/[[353 | Elphel Model 353 camera]]. Adapter uses two general purpose I/O of the camera FPGA, available on each of the [[10369]] USB/extension connectors J9..J11. The 103695 board provides 3.3V/5.0V power to the IMU (selectable by on-board resistors) and supports different speed SPI interface to the sensor unit. The device connector (J2) can accommodate a number of Analog Devices units, it should be possible to use the board with connector adapter with other SPI sensors. Adapter uses two general purpose I/O of the camera FPGA, available on each of the [[10369]] USB/extension connectors J9..J11. The 103695 board provides 3.3V/5.0V power to the IMU (selectable by on-board resistors) and supports different speed SPI interface to the sensor unit. The device connector (J2) can accommodate a number of Analog Devices units, it should be possible to use the board with connector adapter with other SPI sensors. Oleg

Interfaces:

← Older revision Revision as of 21:05, 18 November 2016 Line 23: Line 23: [[File:Nc393 4sensors.jpeg|thumb|220px|10393 + 4 sensors]] [[File:Nc393 4sensors.jpeg|thumb|220px|10393 + 4 sensors]] * Gigabit ethernet * Gigabit ethernet -* micro USB - system console, reboot, select boot device+* micro USB - system console (serial port), reboot, select boot device * 4x sensor ports - routed to FPGA, each reconfigurable for general multi-purpose use * 4x sensor ports - routed to FPGA, each reconfigurable for general multi-purpose use * Added by [[10389|10389 Extension board]]: * Added by [[10389|10389 Extension board]]: Oleg

Created page with "==10389== 10389 interface board is an extension board for the Elphel 393 series cameras. Provides extra interfaces, adds an internal storage - M.2 SSD. [[Image:10389_t..."

New page

==10389==
10389 interface board is an extension board for the [[10393|Elphel 393 series cameras]]. Provides extra interfaces, adds an internal storage - M.2 SSD.

[[Image:10389_top_sm.png|frame|[[Media:10389_top.png|10389 board, top view]]]]
[[Image:10389_top_ssd_sm.png|frame|[[Media:10389_top_ssd.png|10389 board with M.2 SSD, top view]]]]
[[Image:10389_bottom_sm.png|frame|[[Media:10389_bottom.png|10389 board, bottom view]]]]
==Interfaces==
* USB2.0 (host)
* eSATA + USB port
* M.2 SATA port
* External synchronization (master or slave):
** 2.5mm audio
** 4-conductor flex cable
*2x 10-conductor flex cable ports
**carry 3.3VDC, 5VDC, USB, I²C and GPIO
**support other extension boards ([[103695|IMU]], [[103696|GPS]])

==Mechanical properties==
* Dimensions: 98 x 38 x 9 mm (all connectors installed)
* Weight: <30 g
* Mechanical drawings and CAD files for the 10393 board: [[Elphel_camera_parts_0393-00#0393-00-21B_-_10389_rev_B_interface_PCB_assembly|link]]

==Links==
* [[Media:10389b.pdf|10389 Circuit Diagram, Parts List, PCB layout]]
* [[Media:10389b gerber.tar.gz|10389 Gerber files]] Oleg

uploaded a new version of "[[File:10389 bottom.png]]"

Oleg

New page

== Licensing ==
{{GNU FDLv1.3 }} Oleg

uploaded "[[File:10389 top ssd sm.png]]"

Oleg

Licensing:

← Older revision Revision as of 20:03, 18 November 2016 Line 1: Line 1: == Licensing == == Licensing == -{{CC }}+{{GNU FDLv1.3 }} Oleg

uploaded "[[File:10389 bottom sm.png]]"

Oleg

← Older revision Revision as of 18:41, 18 November 2016 Line 64: Line 64: ==More details== ==More details== -[[Image:10393_bd.png|thumb|400px|[[Media:10393.pdf|10393 Circuit Diagram, Parts List, PCB layout]]&nbsp;&nbsp;&nbsp;&nbsp; [[Media:10393_gerber.tar.gz|10353 Gerber files]]]]+[[Image:10393_bd.png|thumb|400px|[[Media:10393.pdf|10393 Circuit Diagram, Parts List, PCB layout]]&nbsp;&nbsp;&nbsp;&nbsp; [[Media:10393_gerber.tar.gz|10393 Gerber files]]]] This camera system board is designed to simultaneously support multiple sensors - both with legacy parallel interface (it is directly compatible with [[10338|10338 Sensor board]] and [[10359|10359 Sensor multiplexer board]]) and with new high-speed serial interface (up to 8 lanes + clock per each port), such as [[10398 | 10398 14MPix SFE]]. Sensor ports of the 10393 can be combined to interface larger/higher speed sensors, interface supply voltage is programmable in the range of 1.35V to 2.8V. All the sensor port interface signals are routed directly to the FPGA pads (22 I/O signals on each of the 4 flex cable connectors) , so the same ports can be uses for other purposes, for example to control the motors or interface IMU of the quadcopter. This camera system board is designed to simultaneously support multiple sensors - both with legacy parallel interface (it is directly compatible with [[10338|10338 Sensor board]] and [[10359|10359 Sensor multiplexer board]]) and with new high-speed serial interface (up to 8 lanes + clock per each port), such as [[10398 | 10398 14MPix SFE]]. Sensor ports of the 10393 can be combined to interface larger/higher speed sensors, interface supply voltage is programmable in the range of 1.35V to 2.8V. All the sensor port interface signals are routed directly to the FPGA pads (22 I/O signals on each of the 4 flex cable connectors) , so the same ports can be uses for other purposes, for example to control the motors or interface IMU of the quadcopter. Oleg

Format micro SD card (command line):

← Older revision Revision as of 18:34, 18 November 2016 Line 26: Line 26: * Insert, power on * Insert, power on -==Format micro SD card (command line)==+==Format micro SD card (command line, can be done in the booted from nand camera)== Example for '''/dev/sdX''': Example for '''/dev/sdX''': * create partitions with fdisk , gparted or any other program: * create partitions with fdisk , gparted or any other program: Line 33: Line 33: formatting with mkfs: formatting with mkfs: * mkfs.vfat -F 32 /dev/sdX1 * mkfs.vfat -F 32 /dev/sdX1  +----  + * mkfs.ext4 /dev/sdX2 * mkfs.ext4 /dev/sdX2 [[Category:Elphel393]] [[Category:Elphel393]] Oleg

uploaded "[[File:10389b gerber.tar.gz]]"

Andrey.filippov

Operating:

← Older revision Revision as of 22:25, 9 November 2016 Line 16: Line 16: |[[File:Eyesis4pi393 cables.png|thumb|300px|Fig.1 Cables]] |[[File:Eyesis4pi393 cables.png|thumb|300px|Fig.1 Cables]] |- |- -|[[File:Eyesis4pi393 recording external disks.png|thumb|300px|Fig.2 Recording to external drives]]+|[[File:Eyesis4pi393 recording external disks.png|thumb|300px|Fig.2 Recording to swappable external drives]] |[[File:Eyesis4pi393 recording internal ssds or network.png|thumb|300px|Fig.3 Recording to internal SSDs or over network]] |[[File:Eyesis4pi393 recording internal ssds or network.png|thumb|300px|Fig.3 Recording to internal SSDs or over network]] -|[[File:Eyesis4pi393 footage download from internal ssds.png|thumb|300px|Fig.4 Downloading data from internal SSDs]]+|[[File:Eyesis4pi393 footage download from internal ssds.png|thumb|300px|Fig.4 Downloading data from internal SSDs to PC]] |} |} Oleg