ElphelWiki - User contributions [en]

Camogm

2017-06-16T18:47:26Z

Mikhail: /* allow_sync */

== Description ==
This program allows recording of the video/images acquired by Elphel 353/363 series cameras to the storage media. It is developed to use such media as hard disk drives, compact flash cards or USB storage devices (with reduced data rate as ETRAX FS processor currently supports only USB 1.1, not the fast USB 2). But it might work over the NFS and be useful even for the basic model 353 cameras that do not have any additional storage devices attached.

camogm is designed to run in the background and accept commands through a named pipe. It writes JPEG-encoded frames from the camera [[Circbuf|circbuf]]-circular video buffer in any of the 3 formats:
*'''ogm''' - MJPEG video in Xiph Ogg container
*'''jpeg''' - series of the individual JPEG files (1 file per frame)
*'''mov''' - MJPEG video in Apple QuickTime(R) container
As of today the last one (mov) is probably the fastest one in the camera as it uses the minimum of computational resources. Ogg is optimized for streaming and requires additional memory copying and checksum calculation for all of the recorded data, individual JPEG files grow large directories that can use system resources, while recording mov format simply merges FPGA-encoded frames (with JPEG and optional Exif headers added by the software) and the file header (with frame index) is calculated only once per file.

This program makes use of the [[Circbuf|circbuf]] that can hold several seconds of even high resolution/high frame rate video, so switching from file to file and/or waiting for the search operations on the HDD will not cause the frame loss - that can be verified if the Exif headers are enabled - regardless of the format selected each frame will have the exact timestamp (with 1 microsecond resolution).

== Usage ==
=== Starting camogm ===

Eventually camogm will be started (and restarted if needed) automatically at boot time, now it is started manually with the command

camogm <named_pipe_name>

Where <named_pipe_name> is the filename that will be used to pass commands to the camogm. A good choice is "/var/state/camogm_cmd" and it is used in a [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/camogm/camogmstate.php?view=markup camogmstate.php] - a demo PHP script that can read the current status of the camogm recorder. Running camogm without any parameters or with "--help" will just output the short version of this page. So this is the example of the command that starts camogm as a background process from the shell prompt (i.e. telnet or [[Phpshell]]):

camogm /var/state/camogm_cmd &

=== Sending Commands to camogm ===

When the camogm is running you may verify that with the command:
ps | grep "camogm"
It is waiting for the commands to be sent to the pipe (/var/state/camogm_cmd above) as text strings. Commands are separated with the new lines ("\n") and/or semicolons (";"), command names are separated from the optional parameters by spaces " " and/or equal signs "=". The following is an example of such command sent from the shell prompt using command "echo" and output redirection ">" to th camogm command pipe

echo "status; exif 1; format=jpeg;status=/var/tmp/camogm.status" > /var/state/camogm_cmd

That command will:
# print current status information sending it to the standard output (may not be visible if the program was not started from the same session),
# set exif mode ON (each frame will have the full Exif header including a precise time stamp),
# set output format to a series of individual JPEG files, and then
# send status information to a file /var/tmp/camogm.status in the camera file system.
The [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/camogm/camogmstate.php?view=markup camogmstate.php] script shows how to use a named pipe for the status information so the caller will wait until camogm returns that status info (the "echo" command by itself will not wait for the status, there can (and will) be a delay between finishing of echo (or equivalent) and the appearance of the status info in the output file. ''With the current state of the software that status info may never come if the camera frame capture process is stopped while camogm was recording video as it checks for the new commands once per frame if it is in the "running" state (in "stopped" state in checks for the incoming commands twice a second)''

== camogm Commands ==
===start===
No parameters - just start recording video/images. At least two frames in the buffer are needed to start recording (they will not be lost) - the time stamp difference is used to calculate the frame rate. In the case there are not enough frames in the buffer (i.e. video acquisition is not started) the state of the camogm (reported by ''status'' and ''xstatus'') will be "starting" before it will become "running". The video will be recorded to the same file (may be a directory for .jpeg format) until explicitly stopped, or until the specified file size/duration/number of frames is exceeded or some critical parameters (like frame dimensions) are changed. In those cases (not explicitly stopped) camogm will restart recording into a new file (filenames are composed from the specified prefix and the timestamp) so that no frames will be lost (if it is not overwhelmed by the incoming frame rate) and the first frame of a new file segment will be the next one acquired after the last one in the previous file.
===stop===
Just stop the recording. If the video acquisition is on and camogm is started again before the [[Circbuf|circbuf]] is overrun, there will be no gaps in the recording. But if the pause will be too long some frames will be lost and there will be a gap between the next file and the previous one.

===exit===
Terminate camogm program (it will execute implied "stop" command first to finish recording if any).
===duration===
duration=<time_in_seconds>
Specify the maximal duration of each individual file segment. The new file will be started if this time limit will be exceeded. The default duration is 60 seconds, current value is reported by status/xstatus commands.
===length===
length=<file_size_in_bytes>
Specify the maximal size of each individual file segment in bytes. The new file will be started if this limit will be exceeded. The limit is 2.147.483.647 bytes (~2 GB), current value is reported by status/xstatus commands.

===max_frames===
max_frames=<number_of_frames>
Specify the maximal number of frames of each individual file segment. The new file will be started if this limit is exceeded. The default value is 16384.

===frames_per_chunk===
frames_per_chunk=<number_of_frames_per_chunk> (default 10)
Sets the number of chunk entries in the *.mov header (10 means there's 1 chunk entry with an absolute offset in the header for each 10 frames).

===start_after_timestamp===
start_after_timestamp=SS.UU # double (0123456789.012345)
Delays recording start until a specific time-stamp has been reached.
This command alone does not start a recording you need to run the "start" command as well after setting start_after_timestamp.

===prefix===
prefix=<file_name_prefix>
prefix value is used by the camogm to generate file names/paths to store video content. Full paths will be generated from the specified prefix, timestamps of the first frame in the segment and appropriate extension (".ogm",".jpeg" or ".mov"). The prefix consists of directory path (everything before the last slash "/") and the file name prefix (what remains after the last "/"). In the case of video formats (".ogm",".mov") the directory prefix should point to an existent directory on the mounted writeable media - camogm will not try to create missing directories and will just fail to start recording. In the case of individual JPEG files camogm will try to create the last level in directory structure if it does not exist and place all the frame files there.

===exif===
Controls generation and output of [[Exif]] headers for each JPEG-encoded frame. These headers slightly (for the large frames) increase the file sizes and add a little of computation to the CPU, but they are very useful for later processing as they provide precise timing information that does not depend on particular file format and timing calculations that involve frame rate and frame numbers.
exif=0
turns it off, while
exif=1
turns it on. Current default value is off, but that may change in the future so it is better to specify the desired value.
===timescale===
Currently only works for "mov" format (will add to "ogm" later). Values >1.0 make the video play back slower than recorded ('slow motion'), the values less than 1.0 make the playback faster (time lapse video).
===frameskip===
frameskip=<number_of_frames_to_skip>
Skip specified number of frames after each frame stored (default 0 - no skip)
===timelapse===
timelapse=<number_seconds_between_frames>
Alternative way to reduce frame rate of the recorded images - specify required image period (integer value, in seconds). All intermediate images will be skipped, only first after each multiple of the specified interval will be stored. That means, that the time interval between subsequent images maybe slightly different, but the rounding error will not accumulate during long recordings.

''timelapse'' and ''frameskip'' are mutually exclusive (they even use the same variable with positive values for frame skip (in frames) and negative - timelapse (in seconds).
===format===
format=[ogm|jpeg|mov]
*ogm - record video as Ogg Media Stream
*jpeg - record video as a series of JPEG files
*mov - record video as Apple Quicktime (R) files
===reset===
Mostly a debug feature. Force camogm to start next file from the two most recent images in the circbuf, discarding all the older ones. It is the same action camogm does when the buffer is overrun and frames are lost.

===debug===
debug
debug=<file>
The first command form (with to file specified) turns the debug output off, the second - directs it somewhere. camogm recognizes several special names like "stdout" and "stderr", it also treats file name "none", "null" and "/dev/null" as empty and turns the debug feature off.
===debuglev===
debuglev=<integer_value>
Allows to specify debug verbosity level, the higher the level the more information is output (it may slow down camogm and cause it to drop frames even if it could handle it with no/low debug output).
===save_gp===
save_gp=[0|1]
As a debug feature camogm can set the camera global circbuf read pointer to the current value of camogm's read pointer. In that case it is possible to watch the camogm progress by other programs, such as [[Imgsrv|imgsrv]]
===status===
status
status=<status_output_file>
This command provides the current camogm state information and sends it to standard output (maybe invisible if camogm was started from different shell session or by other means) or to the specified output file in plain text format. The same information is available in XML format - see xstatus command below. The following is a commented sample output generated by the status command:

state running // may be '''stopped''', '''running''' and '''starting'''. Usually the last
// one can be only visible if there are no images coming to the buffer.
file /tmp/z/qvid1195433980_662716.mov // full path toi the current file being recorded
frame 293 // current frame number (starts from 0)
file duration 14.616060 sec // current duration of the video in this file segment
file length 13167561 B // current video file size
frame period 50055 (0xc387) // frame period in microseconds (this one is approximately 1/20 sec)
frames to skip 100 (left 37) // number of frames to skip after the frame is acquired. Shown only if frame skip mode is enabled.
timelapse period 10 sec (remaining 10 sec) // frame period for time lapse mode (time till next frame will be stored). Shown only if time lapse mode enabled
width 1024 (0x400) // frame width in pixels
height 768 (0x300) // frame height in pixels
// - blank line
output format mov // output file format - one of "ogm", "jpeg" and "mov"
using exif yes // frames are generated with Exif headers that include time stamps
path prefix: /tmp/z/qvid // file prefix as specified in '''prefix''' command
max file duration: 60 sec // maximal file duration as specified in '''duration''' command
max file length: 100000000 B // maximal file length as specified in '''length''' command
max frames 16384 // maximal number of frames as specified in ... none yet, uses default
timescale 1.000000 // time scale as specified in '''timescale''' command
frames per chunk 10 // "frames per chunk" used in "mov" format
// - blank line
buffer overruns 0 // number of buffer overruns while recording since last status/xstatus
// (these commands zero the buffer overruns counter). If no overruns
// are reported, no frames are lost, including between file segments.
buffer minimal 19748288 // Minimal level of the buffer memory since last status/xstatus command.
buffer free 19748192 // Current amount of free memory in the video buffer (actual value might
// be one frame less as the FPGA write pointer is reported only after
// the whole frame is stored
buffer used 43680 // Amount of memory currently used in the video buffer.
circbuf_rp 10933536 (0xa6d520) // Current location of the read pointer in the video buffer
// - blank line
debug output to stderr // where the debug messages are sent to (as specified in '''debug''' command)
debug level 1 // Debug verbosity level, the higher - the more "noisier". Set in
// '''debuglev''' command.
use global pointer no // see '''save_gp''' command.

"-1" values that status/xstatus commands may return for some parameters mean "undefined", they are calculated only during video recording.

===xstatus===
status
status=<status_output_file>
Same information as described for '''status''' command above, but presented in XML format more suitable to be processed by other software while '''status''' is easier to read by humans. See [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/camogm/camogmstate.php?view=markup camogmstate.php] PHP script that returns this XML data to the HTTP GET requests.

<?xml version="1.0"?>
<camogm_state>
<state>"running"</state>
<file_name>"/tmp/z/qvid1195440137_027276.mov"</file_name>
<frame_number>281</frame_number>
<file_duration>14.015400</file_duration>
<file_length>12731197</file_length>
<frame_period>50055</frame_period>
<frames_skip>0</frames_skip>
<seconds_skip>10</seconds_skip>
<frames_skip_left>0</frames_skip_left>
<seconds_skip_left>7</seconds_skip_left>
<frame_width>1024</frame_width>
<frame_height>768</frame_height>
<format>"mov"</format>
<exif>"yes"</exif>
<prefix>"/tmp/z/qvid"</prefix>
<max_duration>60</max_duration>
<max_length>100000000</max_length>
<max_frames>16384</max_frames>
<timescale>1.000000</timescale>
<frames_per_chunk>10</frames_per_chunk>
<buffer_overruns>0</buffer_overruns>
<buffer_minimal>19747712</buffer_minimal>
<buffer_free>19747808</buffer_free>
<buffer_used>44064</buffer_used>
<circbuf_rp>16275392</circbuf_rp>
<debug_output>"stderr"</debug_output>
<debug_level>1</debug_level>
<use_global_rp>"no"</use_global_rp>
</camogm_state>

'''This program does not control the process of acquisition of the video/images to the camera internal buffer, it only retrieves that data from the buffer (waiting when needed), packages it to selected format and stores the result files.'''

==Geo Tagging Specific Commands==

===kml===
kml=1 # turn on geotagging

kml=0 # turn off geotagging

Enable / Disable KML output (geotagging).

===kml_period===
kml_period=<number_seconds_between_kml_entries>
Set the amount of seconds between KML entries. (default: 2)

===kml_hhf===
kml_hhf=45 # set horizontal half FOV to 45° so the full horizontal FOV is 90°
Set horizontal half FOV in degrees. (default: 20.0)

===kml_vhf===
kml_vhf=30 # set half vertical FOV to 30° so the full vertical FOV is 60°
Set vertical half FOV in degrees. (default: 15.0)

===kml_near===
???Set "near" distance to PhotoOverlay in metres (Don't use "0") (default: 40)???

===kml_alt===
kml_alt=[gps|ground]
Set altitude/height mode.
* gps - absolute GPS altitude
* ground - relative to ground (default)

===kml_height===
kml_height=100
Set height offset (added to GPS altitude) in metres. (default: 10)

== Camogm2 ==
This is modified version of camogm to support audio recording (from the firmware 7.1.7.28 or later). It support recording of audio 16bit mono/stereo, from 11025 to 44100 Hz to QuickTime(MOV) and OGG(OGM) file formats. Source of the audio is the sound card (can be connected to camera over USB), and file storage can be USB-flash, HDD (connected to camera directly) or NFS-mounted disk. Preferred method is HDD drive, connected to camera directly, because NFS-mounted disk have a non-uniform system load what can cause broken files.

The recorded movie have the same duration of the video and sound, but when play it's depend on how player work with file - for example, QuickTime player play movie like the sound is shorter than video, MPlayer will repeat the last sound piece at the end of movie etc. - so it's better to merge movie from the chunks to single movie.

P.S. First check the sound hardware: set volume to maximum by command
amixer set PCM 100
and try to play test sound file:
aplay /share/sounds/alsa/Front_Center.wav
- if you can't hear any sound, probably you have an old USB card on the camera - this new [http://wiki.elphel.com/images/0/00/10349RevC.jpg 10349 RevC] will work correctly with sound card.

== camogm2 Commands ==
===audio===
audio=<on|off>
command to enable or disable audio recording. When audio support is disabled, camogm work in the same way as original camogm. By default audio is disabled.

===audio_format===
audio_format=<[rate][/channels]>
command to set audio format - frame rate and number of channels. Frame rate can be from 11025 to 44100 Hz; number of channels - 1 for mono sound, or 2 - for stereo. By default 44100/2

===allow_sync===
allow_sync=<enable|disable>
This option is to force writing to storage after each recorded frame. Using a filesystem the OS will write data to buffer before writing to a real device.
This is not a problem with a HDD or other storage media mounted directly on the camera, but with NFS mounted folder this causes trouble as the NFS driver will fill up the buffer and only send data over the network once the buffer is full - this causes a short hang on the camera and frames might be lost. (default: disabled)
===audio_volume===
audio_volume=<volume>
Set recording audio volume in percent.

== camogmgui ==

'''G'''raphical '''U'''ser '''I'''nterface for camogm.

Please see [[Camogmgui]]

== Elphel393 series cameras ==
The functionality of ''camogm'' has been updated in Elphel393 series of cameras. The new version of the program can write data to a raw disk (disk without file system) and send the data over web sockets. The new version of ''camogm'' should be started with two command line arguments:
camogm -n <named_pipe_name> -p <port_number>
Where <named_pipe_name> is the file name that will be used to pass commands to ''camogm'' and <port_number> is a port number used for web interface. The existing command set has been extended with several new commands addressing new functions.

=== port_enable ===
port_enable=<port_number>
Enable sensor port <port_number>. All sensor ports are enabled by default.

=== port_disable ===
port_disable=<port_number>
Disable sensor port <port_number>. ''camogm'' does not read data from disabled ports.

=== rawdev_path ===
Use
rawdev_path=<path_to_disk>
or
rawdev_path
commands to set or reset path to raw device buffer. Setting path to raw device buffer along with jpeg format set switches ''camogm'' to raw device buffer operation. All subsequent writes and reads will be performed to or from raw disk. ''camogm'' saves write pointer while the program is running and sequential starts and stops will not lead to data overwrite. ''camogm'' will reject the 'start' command if the path to raw device buffer is set and current image format is not jpeg. You should either reset the path with 'rawdev_path' command without parameters or set format to jpeg with 'format=jpeg' to continue operation. Note, that ''camogm'' does not check the disk in any way and if the path is mistakenly set to a device with file system, the file system and the data on it will be destroyed.

''camogm'' can process commands sent over a web socket. A command can be sent as HTTP GET request or as a simple string prefixed with 'cmd/', e.g.:
cmd/next_file
''camogm'' can process the following commands:

=== find_file ===
find_file:2016:07:12_17:14:00
Find a file with a time stamp which is within one minute time frame from the time stamp given. If such a file was found, ''camogm'' saves the position of the file and 'next_file' command can be used to advance to the next file on disk. If file was not found, ''camogm'' silently resets connection without any data sent.

=== next_file ===
Get next file from disk. This command should only be used after 'find_file' command successfully finished and returned a file. If file pointer was not set or file was not found, ''camogm'' silently resets connection without any data sent.

=== read_disk ===
Read disk dump and send it over socket. The dump is split into several pieces and ''camogm'' returns the number of files to be sent in response to the command:
Number of files: <number>
The socket is closed right after this string is sent. ''camogm'' opens a socket for each file to be send, waits for connection, sends a file and closes connection after a file was sent.

=== build_index ===
Read raw device buffer and create disk index directory. This directory contains the offsets of all files found on disk and can be used to retrieve files from disk. This command is a prerequisite for get_index, read_file and read_all_files commands. Note that reading disks of several dozens or hundreds of Gib in size can take much time.

=== get_index ===
Get disk index directory. Each record in the directory corresponds to a single file and has the following format:
port_number=<port_number>;unix_time=<unix_time>;usec_time=<usec_time>;offset=<disk_offset>;file_size=<size_in_bytes>
<unix_time> here is time in Unix format, it represents the number of seconds elapsed since 1970-01-01 00:00:00 +0000 (UTC).

=== read_file ===
read_file:port_number=<port_number>;unix_time=<unix_time>;usec_time=<usec_time>;offset=<disk_offset>;file_size=<size_in_bytes>
Read a file from raw disk buffer and send it over socket. The disk index directory should be built prior this command. If a file was not found in disk index directory (for example, because of a mistake in the command string), ''camogm'' silently resets connection without any data sent.

=== read_all_files ===
Retrieve all files from disk. Disk index directory should be built before this command can be executed. When this command is received, ''camogm'' sends back the number of files in the disk index directory:
Number of files: <number>
The socket is closed right after this string is sent. ''camogm'' opens a socket for each file to be send, waits for connection, sends a file and closes connection after a file is sent.

10393 manual

2017-06-01T01:21:55Z

Mikhail: /* Firmware images */

==Important Notes==
* As of 2016/12/15, the software ported from 10353 supports only 5MPix sensors, for 14MPix, please see:
**[http://wiki.elphel.com/index.php?title=Tmp_manual&oldid=14676 older version of this manual with links to older software images]

==In the package==
* 10393 camera system
{|
|[[File:NC393-CS marked ports.jpeg|thumb|200px|Fig.1 10393 interfaces]]
|}
* Power supply wall adapter (default: 18-75V, [[10393_power|more information]])
* CAT6 network cable
* μUSB-to-USB cable
* Recovery μSD card
* If the camera is calibrated the calibration data will be on a separate storage media or on the internal SSD (likely /mnt/sda1)

==Interfaces==
See Fig.1:
{| class="wikitable"
|-
! GigE
| gigabit network
|-
! μSD
| micro SD card slot - boot or storage
|-
! console
| serial console port, use μUSB-to-USB cable
|-
! eSATA+USB
| 2-in-1. Connect USB or eSATA device. USB2.0 host
|-
! μUSB
| USB2.0 host
|-
! sync
| sync multiple cameras or other devices - input/output trigger signal through a 4-conductor 2.5mm audio plug with cable (example: [http://www.digikey.com/products/en?keywords=839-1029-ND digikey])
|}

==Power on==
* Plug in the power supply
* Connect to LAN using the network cable

====Notes====
* Boot time: ~30s
* The default boot is from the on-board NAND flash. [[Boot_options_393|More information]] on available boot options and recovery boot.

==Defaults==
{| class="wikitable"
|-
! IP Address
| 192.168.0.9
|-
! User
| root
|-
! Password
| pass
|}

* The default IP address is set in the ''/etc/elphel393/init_elphel393.py''.
* If present the internal SSD will be formatted into 2 partitions:
** /dev/sda1 - ext4 (~64-100GB)
** /dev/sda2 - raw partition (no file system) for fast recording

==Command line access==
* ssh from PC terminal:
$ ssh root@192.168.0.9

==Serial console access==
* Use a ''microUSB-USB cable'' to connect '''console μUSB port''' (see Fig.1) to PC - the cable's end should be thin enough otherwise interferes with an inserted mmc ('''m'''ulti '''m'''edia '''c'''ard = μSD card).

* In Linux the '''minicom''' program can be used
$ minicom -c on
Most likely the device will be /dev/ttyUSB0. Settings:
* 115200 8N1, no for hardware/software flow control
Refer to the following article for more details on using '''minicom''': [http://wiki.elphel.com/index.php?title=Using_minicom_to_connect_to_Elphel393_camera Using minicom to connect to Elphel393 camera]

==Web user interface (camvc)==
http://192.168.0.9/ (if not found - http://192.168.0.9/closeme.html (type in the browser address bar - will be changed soon)):
* The page contains links to camvc user interface for each individual camera port.
* camvc was ported from the 10353 camera series:
** change parameters like image format, resolution, auto exposure, auto white balance and more. Alternative way to change parameters is described [[Tmp_manual#Change_parameters|below]].
** pause compressor and search within buffered images
** help tips available - see Fig.2 - select then mouse over a control element of interest
{|
| valign='top'|[[image:Help tips.jpeg|250px|thumb|Fig.2 enable camvc help tips]]
|[[File:Controls with blank.jpeg|300px|thumb|Fig.3 camvc controls]]
|}

==Download live images==
====camvc====
* For a currently opened port (displayed in the window title and as "...sensor_port=0..." in the URL):
{|
|[[image:Camvc image capture.jpeg|250px|thumb|Fig.4 Acquire an image from the Camera Control Interface]]
|}

====browser====
port 0: http://192.168.0.9:2323/img
port 1: http://192.168.0.9:2324/img
port 2: http://192.168.0.9:2325/img
port 3: http://192.168.0.9:2326/img

====command line====
wget http://192.168.0.9:2323/img -O filename.jpeg
wget http://192.168.0.9:2324/img -O filename.jpeg
wget http://192.168.0.9:2325/img -O filename.jpeg
wget http://192.168.0.9:2326/img -O filename.jpeg

==Video==
===Display===
====Multipart JPEG stream====
http://192.168.0.9:2323/mimg
http://192.168.0.9:2324/mimg
http://192.168.0.9:2325/mimg
http://192.168.0.9:2326/mimg

====GStreamer====

gst-launch-1.0 souphttpsrc is-live=true location=http://192.168.0.9:2323/mimg ! jpegdec ! xvimagesink

* Only mjpeg, no rtsp yet.
* More examples at [[Using_gstreamer#Display|Using GStreamer]]

===Record===
* Recording is done by the '''camogm''' program
* If recording to internal or external SSD, please, read about [[Tmp_manual#eSATA_port_switching|eSATA port switching]]
* important: Event logger (GPS, IMU, IMG, EXT) recording is started/stopped separately. See [[Tmp_manual#Record_the_Event_Logger_data_.28GPS.2CIMU.2CIMG_.26_EXT.29|instructions]] below.
* For SATA devices camogm supports:
** recording to a partition with a file system - up to 80MB/s
** (default) faster recording to a partition without a file system (raw partition) avoiding OS calls - up to 220MB/s
* To extract data from a raw partition use '''dd''' or [https://github.com/Elphel/elphel-tools-x393 these scripts] to get the data and split it into images. Follow [[Extracting_images_from_raw_partition | this link]] for details.
* Can record to an mmc partiton or usb.
* [[Using_camogm_with_Elphel393_camera|More info]]
* If the ''prefix'' parameter, which is ''absolute path + prefix'', for a channel is not set the file will be written somewhere to rootfs.
** if prefix is empty then the ''absolute path'' must end with a slash.

====browser====
Example 1: (provide a correct media mount point - /mnt/sda1/)

* http://192.168.0.9/camogmgui.php

Follow [[Camogmgui|this link]] for GUI description.

====command line====
Example:

* '''/home/root''', file prefix='''test_''', '''1GB''' or '''10min''' files whichever occurs first
** setup and start (in one line):
echo "format=mov;status=/var/tmp/camogm.status;prefix=/home/root/test_;duration=600;length=1073741824;start" > /var/volatile/camogm_cmd
** stop recording:
echo "stop" > /var/volatile/camogm_cmd
sync


==Event Logger (GPS, IMU, IMG & EXT)==
* [[Event_logger|'''More information''']]
===Record===
====web====
* Start:
http://192.168.0.9/logger_launcher.php?cmd=start&file=/mnt/sda1/test.log&index=1&n=10000000
* Stop:
http://192.168.0.9/logger_launcher.php?cmd=stop
* Help:
http://192.168.0.9/logger_launcher.php

====command line====
* start:
root@elphel393:~# cat /dev/imu > /path/filename.log
* stop - CTRL-C or kill the process

===Read===
* http://192.168.0.9/read_imu_log.php (will display help)
** on the first access creates /www/pages/logs/ (http://192.168.0.9/logs/)
** link the recorded logs to /www/pages/logs/
** refresh http://192.168.0.9/read_imu_log.php

==Change parameters==
* http://192.168.0.9/autocampars.php - save/restore/initialize camera/sensor parameters
[[Autocampars 393|'''More information''']]

* http://192.168.0.9/parsedit.php - read/write parameters:
** POST request
Read: http://192.168.0.9/parsedit.php?sensor_port=0&PAR1&PAR2
Change: http://192.168.0.9/parsedit.php?sensor_port=0&PAR1&PAR2 - update values - submit form

** GET request - XML response
Read: http://192.168.0.9/parsedit.php?immediate&sensor_port=0&PAR1&PAR2
Change: http://192.168.0.9/parsedit.php?immediate&sensor_port=0&PAR1=VAL1&PAR2=VAL2

Note 1: if the parameter's value is specified in URL it will be applied. The call can have mixed specified and unspecified parameters.

Note 2: The new value is read on the next call.

Example:
* set 10 fps and enable output trigger signal
http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0&TRIG_OUT=0x66555&TRIG_PERIOD=10000000&TRIG=4

[[Parsedit.php|'''More information''']]

'''Notes:'''
* parsedit.php and autocampars.php were ported from 353 camera series. There are a few changes from the originals related to 4x sensor ports:
** parameters are individual for each sensor port - writing parameters to multiple port at once is controlled with a (bit-)'''mask''' input box
** if opened w/o sensor_port specified the page will show links to available ports
** '''sensor_port=x''', where x=0..3 - in the address string - for a single sensor camera it is normally 0

==Image formats==
====jpeg====
* '''color''': YCbCr 4:2:0, 3x3 pixels
* '''mono6''': monochrome - color YCbCr 4:2:0 with zeroed out color components
* '''mono''' : monochrome - color YCbCr 4:0:0 with omitted color components

'''Note:''' Is not the best for processing since a lot of information is lost at demosaicing
====jp4 raw====
* [[JP4|'''More information''']]

==Temperature monitor==
* http://192.168.0.9/hwmon.html:
** Tshutdown - automatic shutdown temperature level (default is 90°C)
{|
|[[File:10393_hwmon.jpeg|thumb|200px]]
|}

==eSATA port switching==
* requres [[10389]]
* available connections:
** camera <=> internal SSD (default)
** camera <=> external drive (external drive will need a separate power source)
** PC <=> internal SSD
* [[Sata_multiplexer_10389|'''More information''']]

==Proper shutdown==
* if not properly shutdown - μSD might get corrupted (run '''sync''' at least)
shutdown -hP now
Same effect:
http://192.168.0.9/autocampars.php?reboot

==Firmware/software update==
[[Poky_2.0_manual#Write_files_to_media_and_boot|'''More information''']]

==Firmware images==
* [http://community.elphel.com/files/393/20170124/ 20170124]
* [http://community.elphel.com/files/393/20170531/ 20170531]

==Other info==
====Tools for calibrated systems====
* [[Elphel_Software_Kit_for_Ubuntu#ImageJ_and_Elphel_plugins_for_imageJ|Install ImageJ plugins]]
** decode jp4 raw format
** aberrations correction
** distortion correction (pixel mapping)
** rectification and projection
** '''JP46 Reader camera''' - decode JP4/JP46
** '''Eyesis correction''' - post-process JP4s using calibration data

====switch between ERS and GRR modes in MT9P006====
* [[Electronic_Rolling_Shutter#ERS_and_GRR_in_MT9P001_on_10393|Read article]]
====External/internal trigger and FPS control====
* [[Trigger_393]]
===SSD/MMC/USB formatting===
* [[Format_SSD_MMC]]
===Boot modes===
* [[Boot_options_393|Boot options]]
===Pointers monitor===
* Displays sensor, compressor and buffer states per 10393 port:
http://192.168.0.9/pointers/

==Known problems==
* [solved] Vertical artifacts in jpegs. Images are ok at 100% quality. Fixed, testing.
* http://192.168.0.9:232x/noexif/mimg - multipart jpeg displays corrupted frames from time to time. Reason: network bandwidth?
* [solved] Sometimes on power-on (NAND flash boot) cannot mount the card's rootfs partition. Kernel Panics. Power off/on. Soft "reboot -f" works ok.
...
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
...
[[VFS:_Unable_to_mount_root_fs_on_unknown-block(179,2)|More info]]
* Changing exposure/quality/gains - can corrupt images - needs testing.

* After rewriting rootfs to μSD card - some of the cards get a corrupted partition - re-partitioning (reformatting?) solves the problem.
On the camera the rootfs is mounted as RW and some of the files are changed (also links created) -
most of the changes are now moved to tmpfs but something might have been missed.

==Notes==
* In case rootfs is on flash, it might make sense (or maybe not as the history is updated only once on session exit) to disable bash sessions command history - [http://stackoverflow.com/questions/18663078/disable-history-in-linux disable bash history]

* When using '''overlays''', deleting, existing in the lower layer, dirs can cause errors (hopefully it gets fixed someday), example:
** /mnt/sda1 exists in lower layer: /tmp/rootfs.ro/tmp
** upper layer is mounted to "/"
# rmdir /mnt/sda1
# mkdir /mnt/sda1
mkdir: cannot create directory '/mnt/sda1': Operation not supported

[[Category:393]]

Elphel camera parts 0393-12

2017-04-14T20:29:45Z

Mikhail:

[[Elphel_camera_parts_0393|Elphel NC393 series camera parts]]
== 0393-12 - front ends ==
=== 0393-12-20 - Mounting plate for calibrated SFE ===
Note: X3D model will be updated later.
{{Cad4a|0393-12-20}}
----

=== 0393-12-29 - Sensor front end, CS-mount ===
{{Cad4a|0393-12-29}}
----
=== 0393-12-29A - Sensor front end, CS-mount, Rev "A" ===
Note: X3D model will be updated later.
{{Cad4a|0393-12-29A}}
----
=== 0393-12-29B - Sensor front end, CS-mount, Rev "B" ===
Note: X3D model will be updated later.
{{Cad4a|0393-12-29B}}Section of this model

[[File:SFE section.png|250px]]

----
=== 0393-12-30 - Sensor adjustment plate ===
{{Cad4a|0393-12-30}}
----
=== 0393-12-30A - Sensor adjustment plate, Rev. "A" ===
Note: X3D model will be updated later
{{Cad4a|0393-12-30A}}
----

=== 0393-12-31 - Disk springs support pin ===
Made of stainless steel 316 hypodermic round tubing
{{Cad4a|0393-12-31}}
----
=== 0393-12-31A - Disk springs support pin, Rev. "A" ===
Made of stainless steel 316 hypodermic round tubing

Note: X3D model will be updated later
{{Cad4a|0393-12-31A}}
----

=== 0393-12-43 - SFE M12 body ===
{{Cad4a|0393-12-43}}
----
=== 0393-12-44 - SFE M12 adapter ===
{{Cad4a|0393-12-44}}
----
=== 0393-12-50 - Fisheye head adapter ===
{{Cad4a|0393-12-50}}
----
=== 0393-12-51 - SFEs mount ===
{{Cad4a|0393-12-51}}
----

Elphel camera parts 0393-12

2017-04-14T20:26:02Z

Mikhail: /* 0393-12-29B - Sensor front end, CS-mount, Rev "B" */

[[Elphel_camera_parts_0393|Elphel NC393 series camera parts]]
== 0393-12 - front ends ==
=== 0393-12-20 - Mounting plate for calibrated SFE ===
Note: X3D model will be updated later.
{{Cad4a|0393-12-20}}
----

=== 0393-12-29 - Sensor front end, CS-mount ===
{{Cad4a|0393-12-29}}
----
=== 0393-12-29A - Sensor front end, CS-mount, Rev "A" ===
Note: X3D model will be updated later.
{{Cad4a|0393-12-29A}}
----
=== 0393-12-29B - Sensor front end, CS-mount, Rev "B" ===
Note: X3D model will be updated later.
{{Cad4a|0393-12-29B}}
[[File:SFE section.png|250px|thumb|left|Section of this model]]
----

=== 0393-12-30 - Sensor adjustment plate ===
{{Cad4a|0393-12-30}}
----
=== 0393-12-30A - Sensor adjustment plate, Rev. "A" ===
Note: X3D model will be updated later
{{Cad4a|0393-12-30A}}
----

=== 0393-12-31 - Disk springs support pin ===
Made of stainless steel 316 hypodermic round tubing
{{Cad4a|0393-12-31}}
----
=== 0393-12-31A - Disk springs support pin, Rev. "A" ===
Made of stainless steel 316 hypodermic round tubing

Note: X3D model will be updated later
{{Cad4a|0393-12-31A}}
----

=== 0393-12-43 - SFE M12 body ===
{{Cad4a|0393-12-43}}
----
=== 0393-12-44 - SFE M12 adapter ===
{{Cad4a|0393-12-44}}
----
=== 0393-12-50 - Fisheye head adapter ===
{{Cad4a|0393-12-50}}
----
=== 0393-12-51 - SFEs mount ===
{{Cad4a|0393-12-51}}
----

File:SFE section.png

2017-04-14T20:19:29Z

Mikhail:

SATA data logger

2017-04-12T22:26:04Z

Mikhail: Created page with "=== Logger data format === SATA controller implemented in FPGA has it own low level logger. It uses 4 KB circular buffer to record timestamps, each host to device and dev..."

=== Logger data format ===
SATA controller implemented in FPGA has it own low level logger. It uses 4 KB circular buffer to record timestamps, each host to device and device to host FIS (first 5 DWORDs only for long FISes), FIS length and a few other values that were used while debugging the controller. It also can record software generated timestamps and IRQ line state changes. 28 bits timestamp counter stores timestamps with 1/75 microsecond resolution and rolls over every ~3.58 s. All DWORDs in log containing timestamps have the following format:
0x<4 bit tag><28 bit timestamp>
where the 4 MSB tag field can be one of the following:
<table>
<tr style="text-align:left;padding:20px"><th>Tag</th><th>Description</th></tr>
<tr style="text-align:left;padding:20px"><td>0x0</td><td>register H2D FIS</td></tr>
<tr style="text-align:left;padding:20px"><td>0x1</td><td>register D2H FIS</td></tr>
<tr style="text-align:left;padding:20px"><td>0x8…0xd</td><td>software generated tags</td></tr>
<tr style="text-align:left;padding:20px"><td>0xe</td><td>set IRQ</td></tr>
<tr style="text-align:left;padding:20px"><td>0xf</td><td>clear IRQ</td></tr>
</table>
Software generated and IRQ timestamps are single DWORDs and have no any other data after them. Each FIS timestamp is followed by minimum 8 DWORDs for single DWORD FISes and maximum 12 DWORDs for longer FISes. These DWORDs contain the following data:
* up to 5 first DWORDs of the FIS
* 0xffff0000 | <fis length>
* 0xaa000000 | <DWORD count in the current command>
* 0x55000000 | <last DMA command>, where <last DMA command> is one of 0x25 (READ DMA EXT), 0x35 (WRITE DMA EXT), 0xc8 (READ DMA), 0xca (WRITE DMA); see [http://www.t13.org/Documents/UploadedDocuments/docs2013/d2161r5-ATAATAPI_Command_Set_-_3.pdf ATA/ATAPI Command Set] for command codes and description
* 0x33333333 or FIS data in case this was not DMA activate FIS
* (<8-bit counter of FIFO not ready (Device asked to wait), rolling over>) << 24) | <0x100000 if there was DMATp primitive - never happened> | <22-bit_link_count latched - dwords passed link layer>

=== Getting logged data ===
To get the latest log, go to ''/usr/local/bin'' on camera and start python in this directory. Copy the following startup code to python console:
from __future__ import print_function
from __future__ import division
import x393sata
import x393_mem
mem = x393_mem.X393Mem(1,0,1)
sata = x393sata.x393sata()
Data log starts at address 0x80001000:
_=mem.mem_dump (0x80001000, 0x400,4)
But it is more convenient to use the following command to get data log along with the state of AHCI registers:
hex([((mem.read_mem(0x80000ffc) >> 10) & 0xffc) + 0x80001000,mem.mem_dump (0x80001000, 0x400,4),sata.reg_status()][0])+" "+hex(mem.read_mem(0x80000ffc))
The last line of the output contains the address where data logger had stopped. The first timestamp after this address has smaller value and was recorder during previous buffer run. The log should be analyzed starting from this address and in reverse order.

=== Analysing log ===
Here is an example of the log:
>>> hex([((mem.read_mem(0x80000ffc) >> 10) & 0xffc) + 0x80001000,mem.mem_dump (0x80001000, 0x400,4),sata.reg_status()][0])+" "+hex(mem.read_mem(0x80000ffc))
Turning OFF use of negative offsets in mmap

0x80001000:ffff0801 aa024800 55350540 33333333 00024048 176f79ad 00000039 ffff0001 aa024800 55350540 33333333 00024849 076f79cc 00000046 91b093c3 48e500c8
0x80001040:93919300 f5f6199c ffff0801 aa025000 55350540 33333333 00024849 176f82f8 00000039 ffff0001 aa025000 55350540 33333333 0002504a 076f8317 00000046
0x80001080:a9242796 4d70103c c5626548 c1be4255 ffff0801 aa025800 55350540 33333333 0002504a 176f8c44 00000039 ffff0001 aa025800 55350540 33333333 0002584b
0x800010c0:076f8c63 00000046 ce495209 2c845250 ed6df9e6 422a1d21 ffff0801 aa026000 55350540 33333333 0002584b 176f9590 00000039 ffff0001 aa026000 55350540
0x80001100:33333333 0002604c 076f95af 00000046 635c2c17 cacd1ced 39ea9573 92d51935 ffff0801 aa026800 55350540 33333333 0002604c 176f9edc 00000039 ffff0001
0x80001140:aa026800 55350540 33333333 0002684d 076f9efb 00000046 6ed338a9 ba9623be a8b818a5 9cdaa6d1 ffff0801 aa027000 55350540 33333333 0002684d 176fa828
0x80001180:00000039 ffff0001 aa027000 55350540 33333333 0002704e 076fa847 00000046 49f4885f 75296a4a 69e23265 2722170c ffff0801 aa027800 55350540 33333333
0x800011c0:0002704e 176fb174 00000039 ffff0001 aa027800 55350540 33333333 0002784f 076fb193 00000046 5623759a 72ade510 6ae4e652 9c937192 ffff0801 aa028000
0x80001200:55350540 33333333 0002784f 176fbac0 00000039 ffff0001 aa028000 55350540 33333333 00028050 076fbadf 00000046 d21e0a61 20158e3c 949354e1 f004a1d3
0x80001240:ffff0801 aa028800 55350540 33333333 00028050 176fc40b 00000039 ffff0001 aa028800 55350540 33333333 00028851 076fc42a 00000046 751c7830 7a479324
0x80001280:228181a4 0edac916 ffff0801 aa029000 55350540 33333333 00028851 176fcd57 00000039 ffff0001 aa029000 55350540 33333333 00029052 076fcd76 00000046
0x800012c0:77db6a45 8d32964f 3ae5945a f425fd94 ffff0801 aa029800 55350540 33333333 00029052 176fd6a3 00000039 ffff0001 aa029800 55350540 33333333 00029853
0x80001300:076fd6c2 00000046 65348f73 ca1915cb a993a46e b9c928ed ffff0801 aa02a000 55350540 33333333 00029853 176fdfeb 00504034 e0337c28 0000000c 00000540
0x80001340:00000000 ffff0005 aa02a000 55350540 00504034 0002a054 f76fe01a e76fe42e 97711f30 07711f8b 00358027 e0338168 0000000c 08000180 00000000 ffff0005
0x80001380:aa000000 55350180 33333333 00000000 17712314 00000039 ffff0001 aa000000 55350180 33333333 00000000 07712333 00000046 06301be9 310edf3e a7b547e4
0x800013c0:c8c617e0 ffff0801 aa000800 55350180 33333333 00000000 17712c8a 00000039 ffff0001 aa000800 55350180 33333333 00000801 07712ca9 00000046 e9a4617d
0x80001400:bfdf9dc6 b4931256 67bf182d ffff0801 aa001000 55350180 33333333 00000801 177135d4 00000039 ffff0001 aa001000 55350180 33333333 00001002 077135f3
0x80001440:00000046 4e123c09 43c7f176 d54fcfc0 743f6499 ffff0801 aa001800 55350180 33333333 00001002 17713f1e 00000039 ffff0001 aa001800 55350180 33333333
0x80001480:00001803 07713f3d 00000046 c3b5ce9f 18729b92 306ec39d 407dbfaa ffff0801 aa002000 55350180 33333333 00001803 1771486a 00000039 ffff0001 aa002000
0x800014c0:55350180 33333333 00002004 07714889 00000046 d528cb25 a31ddc84 8513ce38 afc22945 ffff0801 aa002800 55350180 33333333 00002004 177151b4 00000039
0x80001500:ffff0001 aa002800 55350180 33333333 00002805 077151d3 00000046 a919d6a0 54f99cd3 65b8447a 3ed8fd65 ffff0801 aa003000 55350180 33333333 00002805
0x80001540:17715b02 00000039 ffff0001 aa003000 55350180 33333333 00003006 07715b21 00000046 cf480283 3ca92707 49dd8492 3aa9ab4a ffff0801 aa003800 55350180
0x80001580:33333333 00003006 1771644f 00000039 ffff0001 aa003800 55350180 33333333 00003807 0771646e 00000046 2a27e273 35231c55 0facdc33 ad349418 ffff0801
0x800015c0:aa004000 55350180 33333333 00003807 17716d99 00000039 ffff0001 aa004000 55350180 33333333 00004008 07716db8 00000046 0fae0300 5dba9c24 1f4116dd
0x80001600:a42a94cb ffff0801 aa004800 55350180 33333333 00004008 177176e5 00000039 ffff0001 aa004800 55350180 33333333 00004809 07717704 00000046 2a46be7b
0x80001640:2ac1a9ea 493ba770 d353e15f ffff0801 aa005000 55350180 33333333 00004809 17718031 00000039 ffff0001 aa005000 55350180 33333333 0000500a 07718050
0x80001680:00000046 ed97e764 0acf6739 ce5e583f 67258f71 ffff0801 aa005800 55350180 33333333 0000500a 1771897b 00000039 ffff0001 aa005800 55350180 33333333
0x800016c0:0000580b 0771899a 00000046 50a5d1ac 21e28936 da295470 ebfdfd58 ffff0801 aa006000 55350180 33333333 0000580b 177192c9 00000039 ffff0001 aa006000
0x80001700:55350180 33333333 0000600c 077192e8 00000046 aaa8d2e9 3c5a7345 2e8d8abc a6758857 ffff0801 aa006800 55350180 33333333 0000600c 17719c14 00000039
0x80001740:ffff0001 aa006800 55350180 33333333 0000680d 07719c33 00000046 5cbb8a1f 8db587f3 ac462925 6ed51827 ffff0801 aa007000 55350180 33333333 0000680d
0x80001780:1771a55e 00000039 ffff0001 aa007000 55350180 33333333 0000700e 0771a57d 00000046 a5041d39 749c6e2a ae748d70 c55dea94 ffff0801 aa007800 55350180
0x800017c0:33333333 0000700e 1771aeac 00000039 ffff0001 aa007800 55350180 33333333 0000780f 0771aecb 00000046 50f34801 e1401b17 70f9419d 4e0204c7 ffff0801
0x80001800:aa008000 55350180 33333333 0000780f 1771b7f7 00000039 ffff0001 aa008000 55350180 33333333 00008010 0771b816 00000046 17e410c3 48304ec6 05e2871d
0x80001840:139c04dc ffff0801 aa008800 55350180 33333333 00008010 1771c141 00000039 ffff0001 aa008800 55350180 33333333 00008811 0771c160 00000046 49a54ebd
0x80001880:5329752a 6621559a d27e88e7 ffff0801 aa009000 55350180 33333333 00008811 1771ca8d 00000039 ffff0001 aa009000 55350180 33333333 00009012 0771caac
0x800018c0:00000046 97124ea7 58ae2a3d 5aabd15a 83bc8d20 ffff0801 aa009800 55350180 33333333 00009012 1771d3d7 00000039 ffff0001 aa009800 55350180 33333333
0x80001900:00009813 0771d3f6 00000046 4ea3d339 4a416a55 2925a76a 856bfba9 ffff0801 aa00a000 55350180 33333333 00009813 1771dd22 00000039 ffff0001 aa00a000
0x80001940:55350180 33333333 0000a014 0771dd41 00000046 6aacd89d d98a6c83 09c6b862 e748f918 ffff0801 aa00a800 55350180 33333333 0000a014 1771e66e 00000039
0x80001980:ffff0001 aa00a800 55350180 33333333 0000a815 0771e68d 00000046 635606e4 c00c7fec bfdb351a be053970 ffff0801 aa00b000 55350180 33333333 0000a815
0x800019c0:1771efba 00000039 ffff0001 aa00b000 55350180 33333333 0000b016 0771efd9 00000046 2a491877 6269e149 4a376714 1937e7a4 ffff0801 aa00b800 55350180
0x80001a00:33333333 0000b016 1771f905 00000039 ffff0001 aa00b800 55350180 33333333 0000b817 0771f924 00000046 3ec839f5 5047ce99 64c4b479 14ce9391 ffff0801
0x80001a40:aa00c000 55350180 33333333 0000b817 1772024d 00504034 e0338168 0000000c 00000180 00000000 ffff0005 aa00c000 55350180 00504034 0000c018 f772027c
0x80001a80:e7720544 9d14768a 0d147721 00ca8027 e00c40c0 00000000 08000008 00000000 ffff0005 aa000000 55ca0008 33333333 00000000 33333333 0001a835 176ec90a
0x80001ac0:00000039 ffff0001 aa01b000 55350540 33333333 0001b036 076ec929 00000046 6020c72a 7390006d e5c6fc9e 73dbe206 ffff0801 aa01b800 55350540 33333333
0x80001b00:0001b036 176ed258 00000039 ffff0001 aa01b800 55350540 33333333 0001b837 076ed277 00000046 6c281f96 0f7a3092 978f0097 edc2c79d ffff0801 aa01c000
0x80001b40:55350540 33333333 0001b837 176edba3 00000039 ffff0001 aa01c000 55350540 33333333 0001c038 076edbc2 00000046 0ef941d5 e7799073 a1bc5559 0fa7d628
0x80001b80:ffff0801 aa01c800 55350540 33333333 0001c038 176ee4f0 00000039 ffff0001 aa01c800 55350540 33333333 0001c839 076ee50f 00000046 30928bf6 aa4949b5
0x80001bc0:caefabb2 e3848332 ffff0801 aa01d000 55350540 33333333 0001c839 176eee3c 00000039 ffff0001 aa01d000 55350540 33333333 0001d03a 076eee5b 00000046
0x80001c00:94ab8e1a 934afb29 b9484587 2aab5353 ffff0801 aa01d800 55350540 33333333 0001d03a 176ef788 00000039 ffff0001 aa01d800 55350540 33333333 0001d83b
0x80001c40:076ef7a7 00000046 e4d4eaed 504de754 1925e554 9dae9ece ffff0801 aa01e000 55350540 33333333 0001d83b 176f00d2 00000039 ffff0001 aa01e000 55350540
0x80001c80:33333333 0001e03c 076f00f1 00000046 83620949 27956139 70125080 ed04010e ffff0801 aa01e800 55350540 33333333 0001e03c 176f0a1f 00000039 ffff0001
0x80001cc0:aa01e800 55350540 33333333 0001e83d 076f0a3e 00000046 51e6730a fbe5548a a65453a8 e1a42595 ffff0801 aa01f000 55350540 33333333 0001e83d 176f136b
0x80001d00:00000039 ffff0001 aa01f000 55350540 33333333 0001f03e 076f138a 00000046 18f7e039 03488e01 2919d7df 465978d6 ffff0801 aa01f800 55350540 33333333
0x80001d40:0001f03e 176f1cb5 00000039 ffff0001 aa01f800 55350540 33333333 0001f83f 076f1cd4 00000046 35e1bcd1 2297b23a ab5219ab 70b1ba19 ffff0801 aa020000
0x80001d80:55350540 33333333 0001f83f 176f2602 00000039 ffff0001 aa020000 55350540 33333333 00020040 076f2621 00000046 4932a6a7 a9072307 14ce9b07 d41b18c5
0x80001dc0:ffff0801 aa020800 55350540 33333333 00020040 176f2f4e 00000039 ffff0001 aa020800 55350540 33333333 00020841 076f2f6d 00000046 82e08012 4b929c8f
0x80001e00:80531876 43af07d9 ffff0801 aa021000 55350540 33333333 00020841 176f3898 00000039 ffff0001 aa021000 55350540 33333333 00021042 076f38b7 00000046
0x80001e40:919459ca cb4182b4 98591b2f f5730e1c ffff0801 aa021800 55350540 33333333 00021042 176f41e5 00000039 ffff0001 aa021800 55350540 33333333 00021843
0x80001e80:076f4204 00000046 6fa39e00 1e008224 3ccf9187 c20a05b0 ffff0801 aa022000 55350540 33333333 00021843 176f4b31 00000039 ffff0001 aa022000 55350540
0x80001ec0:33333333 00022044 076f4b50 00000046 b015460f 263e97f1 c8618cab b44a27ea ffff0801 aa022800 55350540 33333333 00022044 176f547b 00000039 ffff0001
0x80001f00:aa022800 55350540 33333333 00022845 076f549a 00000046 840ee418 9dd4c965 5a9d4638 b9949372 ffff0801 aa023000 55350540 33333333 00022845 176f5dca
0x80001f40:00000039 ffff0001 aa023000 55350540 33333333 00023046 076f5de9 00000046 9607790e 47f244f5 09ac82f1 b1a45064 ffff0801 aa023800 55350540 33333333
0x80001f80:00023046 176f6715 00000039 ffff0001 aa023800 55350540 33333333 00023847 076f6734 00000046 d20cde4f e4102eb0 ca0fac10 0e7237c8 ffff0801 aa024000
0x80001fc0:55350540 33333333 00023847 176f7061 00000039 ffff0001 aa024000 55350540 33333333 00024048 076f7080 00000046 88a51355 abd96f4a daa45150 cb488d57
Turning OFF use of negative offsets in mmap
HBA_PORT__PxIS: 0x00000000 [80000110]
HBA_PORT__PxCMD: 0x00048007 [80000118]
1 : HPCP (Hot Plug Capable Port)
1 : CR (Command List Running (section 5.3.2))
1 : POD (Power On Device (RW with Cold Presence Detection))
1 : SUD (Spin-Up Device (RW with Staggered Spin-Up Support))
1 : ST (Start (HBA may process commands). See section 10.3.1)
HBA_PORT__PxTFD: 0x000000d0 [80000120]
1 : STS.BSY (Latest Copy of Task File Status Register: BSY)
5 : STS.64 (Latest Copy of Task File Status Register: command-specific bits 4..6 )
HBA_PORT__PxSIG: 0x8fe2af00 [80000124]
101 : SIG (Data in the first D2H Register FIS)
HBA_PORT__PxSSTS: 0x00000123 [80000128]
1 : IPM (Interface Power Management)
2 : SPD (Interface Speed)
3 : DET (Device Detection (should be detected if COMINIT is received))
HBA_PORT__PxSERR: 0x00000000 [80000130]
HBA_PORT__PxCI: 0x00000001 [80000138]
1 : CI (Command Issued: bit per Port, only set when PxCMD.ST==1, also cleared by PxCMD.ST: 1->0 by soft)
'0x80001ab4L 0x966ad03cL'
Last DWORD was recorded at address ''0x80001ab4'' and the whole record is marked in green. Red mark is set for the timestamp from the previous buffer run. The analysis of last record is the following:
* ''0d147721'' FIS timestamp, 4 MSBs indicate that this was host to device FIS
* ''00ca8027 e00c40c0 00000000 08000008 00000000'' FIS data as described in SATA specification
* ''ffff0005'' marks the end of FIS data and indicates that FIS data consists of 5 DWORDs
* ''aa000000'' shows DWORD count in the current command
* ''55ca0008'' indicates that last DMA command was 0xca (WRITE DMA)
* ''33333333''
* ''00000000'' contains additional counter values
Three timestamps marked in yellow preceding this FIS are IRQ and software generated timestamps:
* ''f772027c'' indicates when IRQ was set
* ''e7720544'' was set when IRQ was reset
* ''9d14768a'' was set when new command was prepared in driver; this one is driver specific
The light blue background marks register device to host FIS which was logged before IRQ:
* ''1772024d'' FIS timestamp, 4 MSB indicate that is was device to host FIS
* ''00504034 e0338168 0000000c 00000180 00000000'' FIS data as described in SATA specification
* ''ffff0005'' marks the end of FIS data and indicates that FIS data consists of 5 DWORDs
* ''aa00c000'' shows DWORD count in the current command, 0xc000 value indicates that 0x30000 bytes were transferred during last command
* ''55350180'' indicates that last DMA command was 0x35 (WRITE DMA EXT)
* ''00504034'' FIS data
* ''0000c018''
Long series of data starting from address 0x80001364 corresponds to WRITE DMA EXT command and consists of DMA activate plus data FISes.

=== Software timestamps ===
SATA data logger can record software generated timestamps. Only 3 bits of 4 MSBs in timestamp are available for software tags. These tags should be written to a vendor specific register PxVS in AHCI port 0 registers and will appear in the log combined with timestamp: 0x<software tag + 8><timestamp>. Software tag is written in data series marked in yellow in the example above. The address of the register for tags is 0x78. Driver code setting software tag may look like this:

static void set_dscope_tstamp(struct ata_port *ap, unsigned int cmd)
{
void __iomem *port_mmio;
uint32_t data = 0;

port_mmio = ahci_port_base(ap);

data |= (cmd & 0x7);
iowrite32(data, port_mmio + PORT_TIMESTAMP_ADDR);
}
where PORT_TIMESTAMP_ADDR is defined as 0x78.

[[Category:393]]
[[Category:Event_logger]]

Elphel camera parts 0353-01

2017-03-31T17:36:52Z

Mikhail: /* 0353-01-58 - 103388 - FPC 250mm long */

== 0353-01 - cable assemblies ==
=== 0353-01-01 - flex jumper, 30 conductors, 0.5mm pitch, l=30mm, t=0.3mm both ends ===

=== 0353-01-02 - flex jumper, 10 conductors, 0.5mm pitch, l=76mm, t=0.3mm both ends ===
=== 0353-01-021 - flex jumper, 10 conductors, 0.5mm pitch, l=80mm, t=0.3mm both ends, Gold (Au) Plating===

=== 0353-01-022 - flex jumper, 10 conductors, 0.5mm pitch, l=400mm, t=0.3mm both ends, Gold (Au) Plating ===

=== 0353-01-023 - flex jumper, 10 conductors, 0.5mm pitch, l=305mm, t=0.3mm both ends Gold (Au) Plating ===

=== 0353-01-03 - flex jumper, 40 conductors, 0.5mm pitch, l=70mm (one end t=0.3mm, other end t=0.2mm) ===

=== 0353-01-04 - RJ45/DB9F Modular Adapter, wired ===

(Supplier: Cables to Go - Part#: 02941, http://www.cablestogo.com/product.asp?cat_id=107&sku=02941)

The wiring procedure is described on the [[RJ45/DB9F_Modular_Adapter]] page.

=== 0353-01-05 - 6P6C crossed modular cable ===

=== 0353-01-06 - 48V DC Power Injector Cable for custom 12v-36v applications. ===

(Supplier: WISP-router, Inc. - Part#: EZPOEPA02, http://store.wisp-router.com/itemdesc.asp?Tp=&eq=&ic=EZPOEPA02)

=== 0353-01-07 - 48V DC Power Injector Cable - 6 ft. for 48V DC power supply - American ===

(Supplier: Cables4Sure.com http://cables4sure.com/proddetail~prod~260002.htm)

=== 0353-01-08 - 48V DC Power Injector Cable - 6 ft. for 48V DC power supply - European ===

(Supplier: Cables4Sure.com http://cables4sure.com/proddetail~prod~260008.htm)

=== 0353-01-10 - Connector Molex, Microfit 3.0, 4 pins, p/n 43645-0400 ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-10.jpeg|thumb|[[Media:0353-01-10.stp.tar.gz|3d (step)]]  [[Media:0353-01-10.dxf.tar.gz|2d (dxf)]]  [[Media:0353-01-10.pdf|2d (pdf)]]]] ||
|-
|}

=== 0353-01-11 - Connector, Norcom D-sub 26 pins, p/n 180-026-203 ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-11.jpeg|thumb|[[Media:0353-01-11.stp.tar.gz|3d (step)]]  [[Media:0353-01-11.dxf.tar.gz|2d (dxf)]]  [[Media:0353-01-11.pdf|2d (pdf)]]]] ||
|-
|}

=== 0353-01-20 - flex jumper, 30 conductors, 0.5mm pitch, l=2" (50.8mm), t=0.3mm both ends ===
=== 0353-01-201 - flex jumper, 30 conductors, 0.5mm pitch, l=50mm, t=0.3mm both ends ===

=== 0353-01-21 - flex jumper, 30 conductors, 0.5mm pitch, l=4" (101.6mm), t=0.3mm both ends ===
=== 0353-01-211 - flex jumper, 30 conductors, 0.5mm pitch, l=3" (76mm), t=0.3mm both ends ===
=== 0353-01-212 - flex jumper, 30 conductors, 0.5mm pitch, l=100mm, t=0.3mm both ends ===

=== 0353-01-22 - flex jumper, 30 conductors, 0.5mm pitch, l=6" (152.4mm), t=0.3mm both ends ===
=== 0353-01-221 - flex jumper, 30 conductors, 0.5mm pitch, l=150mm, t=0.3mm both ends ===

=== 0353-01-23 - flex jumper, 30 conductors, 0.5mm pitch, l=8" (203.2mm), t=0.3mm both ends ===
=== 0353-01-231 - flex jumper, 30 conductors, 0.5mm pitch, l=200mm t=0.3mm both ends ===
=== 0353-01-232 - flex jumper, 30 conductors, 0.5mm pitch, l=250mm t=0.3mm both ends ===

=== 0353-01-25 - flex jumper, 4 conductors, 0.5mm pitch, l=2" (50.8mm), t=0.3mm both ends ===
=== 0353-01-251 - flex jumper, 4 conductors, 0.5mm pitch, l=50mm, t=0.3mm both ends, Gold (Au) Plating ===

=== 0353-01-252 - flex jumper, 4 conductors, 0.5mm pitch, l=200mm, t=0.3mm both ends, Gold (Au) Plating ===

=== 0353-01-253 - flex jumper, 4 conductors, 0.5mm pitch, l=500mm, t=0.3mm both ends, Gold (Au) Plating ===

----

=== 0353-01-40 - RJFTV21N - sealed 8p8n connector ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-40.jpeg|thumb|[[Media:0353-01-40.stp.tar.gz|3d (step)]]]]
|-
|}
----
=== 0353-01-41 - USBFTV21N - sealed USB connector ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-41.jpeg|thumb|[[Media:0353-01-41.stp.tar.gz|3d (step)]]]]
|-
|}
----
=== 0353-01-42 - Sealed 3-pin connector p/n D38999-20JA98SN ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-42.jpeg|thumb|[[Media:0353-01-42.stp.tar.gz|3d (step)]]]]
|-
|}

----
=== 0353-01-43 - SATA (M) to eSATA (F) Cable Assembly, 0.5m ===

{{Cad4|0353-01-43}}

----

=== 0353-01-44 - SATA to SATA Cable Assembly, 1.0m ===

----

=== 0353-01-45 - eSATA to eSATA Cable Assembly ===
=== 0353-01-46 - SATA to SATA Cable Assembly 500mm, p/n 5602-44-0142A-500 ===

=== 0353-01-47 - Micro SATA 1.8" combo 5V & 3.3V Power & SATA cable, p/n MS16P15PMWVD7S ===

=== 0353-01-50 - FPC flexible printed circuit 90 degree for panoramic head ===
=== 0353-01-51 - FPC flexible printed circuit straight for panoramic head ===
----

=== 0353-01-52 - 103383 - FPC 450mm long ===
----

=== 0353-01-53 - 103384 - FPC 70mm long ===
----

=== 0353-01-55 - 103385 - FPC 150mm long ===
Gerber files: [[Media:103385A_gerber.tar.gz‎|103385A_gerber.tar.gz]]
----

=== 0353-01-56 - 103386 - FPC 100mm long ===
Gerber files: [[Media:103386A gerber.tar.gz|103386A gerber.tar.gz]]
----

=== 0353-01-57 - 103387 - FPC 50mm long ===
Gerber files: [[Media:103387A gerber.tar.gz|103387A gerber.tar.gz]]
----

=== 0353-01-58 - 103388 - FPC 250mm long ===
Gerber files: [[Media:103388A gerber.tar.gz|103388A gerber.tar.gz]]
----

=== 0353-01-54 - Eyesis4Pi GPS receiver (Locosys LS2xxxx) cable ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-52.png|thumb|[[Media:0353-01-52.pdf|2d (pdf)]]]]
|-
|}
{|
|-
| 1x CONN SOCKET 8POS 1.25MM CRIMP
| digikey p/n H1569-ND
|-
| 6x CONN TERM 26-28AWG CRIMP GOLD
| digikey p/n H1577CT-ND
|-
| 1x CONN SOCKET 6POS 0.100 W/RAMP/RIB
| digikey p/n WM2616-ND
|-
| 6x CONN RCPT CRIMP 22-30AWG GOLD
| digikey p/n WM3725CT-ND or similar
|}
----

=== 0353-01-551 - Eyesis4Pi power cable for SSD MUX ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-551.png|thumb|[[Media:0353-01-551.pdf|2d (pdf)]]]]
|-
|}
{|
|1 x CONN RECEPT 2POS 3MM SINGLE ROW
|(Molex: 0436450200) digikey p/n WM1845-ND
|-
|1 x CONN RECEPT 4POS 3MM SINGLE ROW
|(Molex: 0436450400) digikey p/n WM1847-ND
|-
|4 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/n WM7082CT-ND
|}
----

=== 0353-01-552 - Eyesis4Pi 10369 power cable for stereo pair camera & switch ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-552.png|thumb|[[Media:0353-01-552.pdf|2d (pdf)]]]]
|-
|}
{|
|2 x CONN RECEPT 4POS 3MM SINGLE ROW
|(Molex: 0436450400) digikey p/m WM1847-ND
|-
|4 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/m WM7082CT-ND
|}
----

=== 0353-01-553 - Eyesis4Pi 10369 power cable 1-to-4 (for head cameras) ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-553.png|thumb|[[Media:0353-01-553.pdf|2d (pdf)]]]]
|-
|}

{|
|5 x CONN RECEPT 4POS 3MM SINGLE ROW
|(Molex: 0436450400) digikey p/n WM1847-ND
|-
|10 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/n WM7082CT-ND
|}
----

=== 0353-01-554 - Eyesis4Pi SATA-eSATA power 1-to-2 cable ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-554.png|thumb|[[Media:0353-01-554.pdf|2d (pdf)]]]]
|-
|}
{|
|1 x CONN RECEPT 4POS 3MM SINGLE ROW
|(Molex: 0436450400) digikey p/n WM1847-ND
|-
|2 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/n WM7082CT-ND
|-
|2 x CONN SOCKET 2POS 1.25MM CRIMP
|digikey p/n H1563-ND
|-
|4 x CONN TERM 26-28AWG CRIMP GOLD
|digikey p/n H1577CT-ND
|}
----

=== 0353-01-555 - Eyesis4Pi Power cable 48V ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-555.png|thumb|[[Media:0353-01-555.pdf|2d (pdf)]]]]
|-
|}
{|
|1 x CONN RECEPT 2POS 3MM SINGLE ROW
|(Molex: 0436450200) digikey p/n WM18457-ND
|-
|2 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/n WM7082CT-ND
|-
|1 x CABLE ASSY ID=2.5mm OD=5.5mm, 1.83m, (18 AWG)
|digikey p/n CP-2209-ND or CP-2218-ND
|}

----

=== 0353-01-556 - Eyesis4Pi mSATA-SATA cable with power ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-556.png|thumb|[[Media:0353-01-556.pdf|2d (pdf)]]]]
|-
|}
{|
|1 x CONN SOCKET HOUSING 2POS 1.25MM
|digikey p/n H2179-ND
|-
|2 x CONN CONTACT 26-30AWG CRIMP GOLD
|digikey p/n H9991CT-ND
|}

Elphel camera parts 0353-01

2017-03-31T17:35:45Z

Mikhail: /* 0353-01-57 - 103387 - FPC 50mm long */

== 0353-01 - cable assemblies ==
=== 0353-01-01 - flex jumper, 30 conductors, 0.5mm pitch, l=30mm, t=0.3mm both ends ===

=== 0353-01-02 - flex jumper, 10 conductors, 0.5mm pitch, l=76mm, t=0.3mm both ends ===
=== 0353-01-021 - flex jumper, 10 conductors, 0.5mm pitch, l=80mm, t=0.3mm both ends, Gold (Au) Plating===

=== 0353-01-022 - flex jumper, 10 conductors, 0.5mm pitch, l=400mm, t=0.3mm both ends, Gold (Au) Plating ===

=== 0353-01-023 - flex jumper, 10 conductors, 0.5mm pitch, l=305mm, t=0.3mm both ends Gold (Au) Plating ===

=== 0353-01-03 - flex jumper, 40 conductors, 0.5mm pitch, l=70mm (one end t=0.3mm, other end t=0.2mm) ===

=== 0353-01-04 - RJ45/DB9F Modular Adapter, wired ===

(Supplier: Cables to Go - Part#: 02941, http://www.cablestogo.com/product.asp?cat_id=107&sku=02941)

The wiring procedure is described on the [[RJ45/DB9F_Modular_Adapter]] page.

=== 0353-01-05 - 6P6C crossed modular cable ===

=== 0353-01-06 - 48V DC Power Injector Cable for custom 12v-36v applications. ===

(Supplier: WISP-router, Inc. - Part#: EZPOEPA02, http://store.wisp-router.com/itemdesc.asp?Tp=&eq=&ic=EZPOEPA02)

=== 0353-01-07 - 48V DC Power Injector Cable - 6 ft. for 48V DC power supply - American ===

(Supplier: Cables4Sure.com http://cables4sure.com/proddetail~prod~260002.htm)

=== 0353-01-08 - 48V DC Power Injector Cable - 6 ft. for 48V DC power supply - European ===

(Supplier: Cables4Sure.com http://cables4sure.com/proddetail~prod~260008.htm)

=== 0353-01-10 - Connector Molex, Microfit 3.0, 4 pins, p/n 43645-0400 ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-10.jpeg|thumb|[[Media:0353-01-10.stp.tar.gz|3d (step)]]  [[Media:0353-01-10.dxf.tar.gz|2d (dxf)]]  [[Media:0353-01-10.pdf|2d (pdf)]]]] ||
|-
|}

=== 0353-01-11 - Connector, Norcom D-sub 26 pins, p/n 180-026-203 ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-11.jpeg|thumb|[[Media:0353-01-11.stp.tar.gz|3d (step)]]  [[Media:0353-01-11.dxf.tar.gz|2d (dxf)]]  [[Media:0353-01-11.pdf|2d (pdf)]]]] ||
|-
|}

=== 0353-01-20 - flex jumper, 30 conductors, 0.5mm pitch, l=2" (50.8mm), t=0.3mm both ends ===
=== 0353-01-201 - flex jumper, 30 conductors, 0.5mm pitch, l=50mm, t=0.3mm both ends ===

=== 0353-01-21 - flex jumper, 30 conductors, 0.5mm pitch, l=4" (101.6mm), t=0.3mm both ends ===
=== 0353-01-211 - flex jumper, 30 conductors, 0.5mm pitch, l=3" (76mm), t=0.3mm both ends ===
=== 0353-01-212 - flex jumper, 30 conductors, 0.5mm pitch, l=100mm, t=0.3mm both ends ===

=== 0353-01-22 - flex jumper, 30 conductors, 0.5mm pitch, l=6" (152.4mm), t=0.3mm both ends ===
=== 0353-01-221 - flex jumper, 30 conductors, 0.5mm pitch, l=150mm, t=0.3mm both ends ===

=== 0353-01-23 - flex jumper, 30 conductors, 0.5mm pitch, l=8" (203.2mm), t=0.3mm both ends ===
=== 0353-01-231 - flex jumper, 30 conductors, 0.5mm pitch, l=200mm t=0.3mm both ends ===
=== 0353-01-232 - flex jumper, 30 conductors, 0.5mm pitch, l=250mm t=0.3mm both ends ===

=== 0353-01-25 - flex jumper, 4 conductors, 0.5mm pitch, l=2" (50.8mm), t=0.3mm both ends ===
=== 0353-01-251 - flex jumper, 4 conductors, 0.5mm pitch, l=50mm, t=0.3mm both ends, Gold (Au) Plating ===

=== 0353-01-252 - flex jumper, 4 conductors, 0.5mm pitch, l=200mm, t=0.3mm both ends, Gold (Au) Plating ===

=== 0353-01-253 - flex jumper, 4 conductors, 0.5mm pitch, l=500mm, t=0.3mm both ends, Gold (Au) Plating ===

----

=== 0353-01-40 - RJFTV21N - sealed 8p8n connector ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-40.jpeg|thumb|[[Media:0353-01-40.stp.tar.gz|3d (step)]]]]
|-
|}
----
=== 0353-01-41 - USBFTV21N - sealed USB connector ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-41.jpeg|thumb|[[Media:0353-01-41.stp.tar.gz|3d (step)]]]]
|-
|}
----
=== 0353-01-42 - Sealed 3-pin connector p/n D38999-20JA98SN ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-42.jpeg|thumb|[[Media:0353-01-42.stp.tar.gz|3d (step)]]]]
|-
|}

----
=== 0353-01-43 - SATA (M) to eSATA (F) Cable Assembly, 0.5m ===

{{Cad4|0353-01-43}}

----

=== 0353-01-44 - SATA to SATA Cable Assembly, 1.0m ===

----

=== 0353-01-45 - eSATA to eSATA Cable Assembly ===
=== 0353-01-46 - SATA to SATA Cable Assembly 500mm, p/n 5602-44-0142A-500 ===

=== 0353-01-47 - Micro SATA 1.8" combo 5V & 3.3V Power & SATA cable, p/n MS16P15PMWVD7S ===

=== 0353-01-50 - FPC flexible printed circuit 90 degree for panoramic head ===
=== 0353-01-51 - FPC flexible printed circuit straight for panoramic head ===
----

=== 0353-01-52 - 103383 - FPC 450mm long ===
----

=== 0353-01-53 - 103384 - FPC 70mm long ===
----

=== 0353-01-55 - 103385 - FPC 150mm long ===
Gerber files: [[Media:103385A_gerber.tar.gz‎|103385A_gerber.tar.gz]]
----

=== 0353-01-56 - 103386 - FPC 100mm long ===
Gerber files: [[Media:103386A gerber.tar.gz|103386A gerber.tar.gz]]
----

=== 0353-01-57 - 103387 - FPC 50mm long ===
Gerber files: [[Media:103387A gerber.tar.gz|103387A gerber.tar.gz]]
----

=== 0353-01-58 - 103388 - FPC 250mm long ===
----

=== 0353-01-54 - Eyesis4Pi GPS receiver (Locosys LS2xxxx) cable ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-52.png|thumb|[[Media:0353-01-52.pdf|2d (pdf)]]]]
|-
|}
{|
|-
| 1x CONN SOCKET 8POS 1.25MM CRIMP
| digikey p/n H1569-ND
|-
| 6x CONN TERM 26-28AWG CRIMP GOLD
| digikey p/n H1577CT-ND
|-
| 1x CONN SOCKET 6POS 0.100 W/RAMP/RIB
| digikey p/n WM2616-ND
|-
| 6x CONN RCPT CRIMP 22-30AWG GOLD
| digikey p/n WM3725CT-ND or similar
|}
----

=== 0353-01-551 - Eyesis4Pi power cable for SSD MUX ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-551.png|thumb|[[Media:0353-01-551.pdf|2d (pdf)]]]]
|-
|}
{|
|1 x CONN RECEPT 2POS 3MM SINGLE ROW
|(Molex: 0436450200) digikey p/n WM1845-ND
|-
|1 x CONN RECEPT 4POS 3MM SINGLE ROW
|(Molex: 0436450400) digikey p/n WM1847-ND
|-
|4 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/n WM7082CT-ND
|}
----

=== 0353-01-552 - Eyesis4Pi 10369 power cable for stereo pair camera & switch ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-552.png|thumb|[[Media:0353-01-552.pdf|2d (pdf)]]]]
|-
|}
{|
|2 x CONN RECEPT 4POS 3MM SINGLE ROW
|(Molex: 0436450400) digikey p/m WM1847-ND
|-
|4 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/m WM7082CT-ND
|}
----

=== 0353-01-553 - Eyesis4Pi 10369 power cable 1-to-4 (for head cameras) ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-553.png|thumb|[[Media:0353-01-553.pdf|2d (pdf)]]]]
|-
|}

{|
|5 x CONN RECEPT 4POS 3MM SINGLE ROW
|(Molex: 0436450400) digikey p/n WM1847-ND
|-
|10 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/n WM7082CT-ND
|}
----

=== 0353-01-554 - Eyesis4Pi SATA-eSATA power 1-to-2 cable ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-554.png|thumb|[[Media:0353-01-554.pdf|2d (pdf)]]]]
|-
|}
{|
|1 x CONN RECEPT 4POS 3MM SINGLE ROW
|(Molex: 0436450400) digikey p/n WM1847-ND
|-
|2 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/n WM7082CT-ND
|-
|2 x CONN SOCKET 2POS 1.25MM CRIMP
|digikey p/n H1563-ND
|-
|4 x CONN TERM 26-28AWG CRIMP GOLD
|digikey p/n H1577CT-ND
|}
----

=== 0353-01-555 - Eyesis4Pi Power cable 48V ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-555.png|thumb|[[Media:0353-01-555.pdf|2d (pdf)]]]]
|-
|}
{|
|1 x CONN RECEPT 2POS 3MM SINGLE ROW
|(Molex: 0436450200) digikey p/n WM18457-ND
|-
|2 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/n WM7082CT-ND
|-
|1 x CABLE ASSY ID=2.5mm OD=5.5mm, 1.83m, (18 AWG)
|digikey p/n CP-2209-ND or CP-2218-ND
|}

----

=== 0353-01-556 - Eyesis4Pi mSATA-SATA cable with power ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-556.png|thumb|[[Media:0353-01-556.pdf|2d (pdf)]]]]
|-
|}
{|
|1 x CONN SOCKET HOUSING 2POS 1.25MM
|digikey p/n H2179-ND
|-
|2 x CONN CONTACT 26-30AWG CRIMP GOLD
|digikey p/n H9991CT-ND
|}

Elphel camera parts 0353-01

2017-03-31T17:35:04Z

Mikhail: /* 0353-01-56 - 103386 - FPC 100mm long */

== 0353-01 - cable assemblies ==
=== 0353-01-01 - flex jumper, 30 conductors, 0.5mm pitch, l=30mm, t=0.3mm both ends ===

=== 0353-01-02 - flex jumper, 10 conductors, 0.5mm pitch, l=76mm, t=0.3mm both ends ===
=== 0353-01-021 - flex jumper, 10 conductors, 0.5mm pitch, l=80mm, t=0.3mm both ends, Gold (Au) Plating===

=== 0353-01-022 - flex jumper, 10 conductors, 0.5mm pitch, l=400mm, t=0.3mm both ends, Gold (Au) Plating ===

=== 0353-01-023 - flex jumper, 10 conductors, 0.5mm pitch, l=305mm, t=0.3mm both ends Gold (Au) Plating ===

=== 0353-01-03 - flex jumper, 40 conductors, 0.5mm pitch, l=70mm (one end t=0.3mm, other end t=0.2mm) ===

=== 0353-01-04 - RJ45/DB9F Modular Adapter, wired ===

(Supplier: Cables to Go - Part#: 02941, http://www.cablestogo.com/product.asp?cat_id=107&sku=02941)

The wiring procedure is described on the [[RJ45/DB9F_Modular_Adapter]] page.

=== 0353-01-05 - 6P6C crossed modular cable ===

=== 0353-01-06 - 48V DC Power Injector Cable for custom 12v-36v applications. ===

(Supplier: WISP-router, Inc. - Part#: EZPOEPA02, http://store.wisp-router.com/itemdesc.asp?Tp=&eq=&ic=EZPOEPA02)

=== 0353-01-07 - 48V DC Power Injector Cable - 6 ft. for 48V DC power supply - American ===

(Supplier: Cables4Sure.com http://cables4sure.com/proddetail~prod~260002.htm)

=== 0353-01-08 - 48V DC Power Injector Cable - 6 ft. for 48V DC power supply - European ===

(Supplier: Cables4Sure.com http://cables4sure.com/proddetail~prod~260008.htm)

=== 0353-01-10 - Connector Molex, Microfit 3.0, 4 pins, p/n 43645-0400 ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-10.jpeg|thumb|[[Media:0353-01-10.stp.tar.gz|3d (step)]]  [[Media:0353-01-10.dxf.tar.gz|2d (dxf)]]  [[Media:0353-01-10.pdf|2d (pdf)]]]] ||
|-
|}

=== 0353-01-11 - Connector, Norcom D-sub 26 pins, p/n 180-026-203 ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-11.jpeg|thumb|[[Media:0353-01-11.stp.tar.gz|3d (step)]]  [[Media:0353-01-11.dxf.tar.gz|2d (dxf)]]  [[Media:0353-01-11.pdf|2d (pdf)]]]] ||
|-
|}

=== 0353-01-20 - flex jumper, 30 conductors, 0.5mm pitch, l=2" (50.8mm), t=0.3mm both ends ===
=== 0353-01-201 - flex jumper, 30 conductors, 0.5mm pitch, l=50mm, t=0.3mm both ends ===

=== 0353-01-21 - flex jumper, 30 conductors, 0.5mm pitch, l=4" (101.6mm), t=0.3mm both ends ===
=== 0353-01-211 - flex jumper, 30 conductors, 0.5mm pitch, l=3" (76mm), t=0.3mm both ends ===
=== 0353-01-212 - flex jumper, 30 conductors, 0.5mm pitch, l=100mm, t=0.3mm both ends ===

=== 0353-01-22 - flex jumper, 30 conductors, 0.5mm pitch, l=6" (152.4mm), t=0.3mm both ends ===
=== 0353-01-221 - flex jumper, 30 conductors, 0.5mm pitch, l=150mm, t=0.3mm both ends ===

=== 0353-01-23 - flex jumper, 30 conductors, 0.5mm pitch, l=8" (203.2mm), t=0.3mm both ends ===
=== 0353-01-231 - flex jumper, 30 conductors, 0.5mm pitch, l=200mm t=0.3mm both ends ===
=== 0353-01-232 - flex jumper, 30 conductors, 0.5mm pitch, l=250mm t=0.3mm both ends ===

=== 0353-01-25 - flex jumper, 4 conductors, 0.5mm pitch, l=2" (50.8mm), t=0.3mm both ends ===
=== 0353-01-251 - flex jumper, 4 conductors, 0.5mm pitch, l=50mm, t=0.3mm both ends, Gold (Au) Plating ===

=== 0353-01-252 - flex jumper, 4 conductors, 0.5mm pitch, l=200mm, t=0.3mm both ends, Gold (Au) Plating ===

=== 0353-01-253 - flex jumper, 4 conductors, 0.5mm pitch, l=500mm, t=0.3mm both ends, Gold (Au) Plating ===

----

=== 0353-01-40 - RJFTV21N - sealed 8p8n connector ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-40.jpeg|thumb|[[Media:0353-01-40.stp.tar.gz|3d (step)]]]]
|-
|}
----
=== 0353-01-41 - USBFTV21N - sealed USB connector ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-41.jpeg|thumb|[[Media:0353-01-41.stp.tar.gz|3d (step)]]]]
|-
|}
----
=== 0353-01-42 - Sealed 3-pin connector p/n D38999-20JA98SN ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-42.jpeg|thumb|[[Media:0353-01-42.stp.tar.gz|3d (step)]]]]
|-
|}

----
=== 0353-01-43 - SATA (M) to eSATA (F) Cable Assembly, 0.5m ===

{{Cad4|0353-01-43}}

----

=== 0353-01-44 - SATA to SATA Cable Assembly, 1.0m ===

----

=== 0353-01-45 - eSATA to eSATA Cable Assembly ===
=== 0353-01-46 - SATA to SATA Cable Assembly 500mm, p/n 5602-44-0142A-500 ===

=== 0353-01-47 - Micro SATA 1.8" combo 5V & 3.3V Power & SATA cable, p/n MS16P15PMWVD7S ===

=== 0353-01-50 - FPC flexible printed circuit 90 degree for panoramic head ===
=== 0353-01-51 - FPC flexible printed circuit straight for panoramic head ===
----

=== 0353-01-52 - 103383 - FPC 450mm long ===
----

=== 0353-01-53 - 103384 - FPC 70mm long ===
----

=== 0353-01-55 - 103385 - FPC 150mm long ===
Gerber files: [[Media:103385A_gerber.tar.gz‎|103385A_gerber.tar.gz]]
----

=== 0353-01-56 - 103386 - FPC 100mm long ===
Gerber files: [[Media:103386A gerber.tar.gz|103386A gerber.tar.gz]]
----

=== 0353-01-57 - 103387 - FPC 50mm long ===
----

=== 0353-01-58 - 103388 - FPC 250mm long ===
----

=== 0353-01-54 - Eyesis4Pi GPS receiver (Locosys LS2xxxx) cable ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-52.png|thumb|[[Media:0353-01-52.pdf|2d (pdf)]]]]
|-
|}
{|
|-
| 1x CONN SOCKET 8POS 1.25MM CRIMP
| digikey p/n H1569-ND
|-
| 6x CONN TERM 26-28AWG CRIMP GOLD
| digikey p/n H1577CT-ND
|-
| 1x CONN SOCKET 6POS 0.100 W/RAMP/RIB
| digikey p/n WM2616-ND
|-
| 6x CONN RCPT CRIMP 22-30AWG GOLD
| digikey p/n WM3725CT-ND or similar
|}
----

=== 0353-01-551 - Eyesis4Pi power cable for SSD MUX ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-551.png|thumb|[[Media:0353-01-551.pdf|2d (pdf)]]]]
|-
|}
{|
|1 x CONN RECEPT 2POS 3MM SINGLE ROW
|(Molex: 0436450200) digikey p/n WM1845-ND
|-
|1 x CONN RECEPT 4POS 3MM SINGLE ROW
|(Molex: 0436450400) digikey p/n WM1847-ND
|-
|4 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/n WM7082CT-ND
|}
----

=== 0353-01-552 - Eyesis4Pi 10369 power cable for stereo pair camera & switch ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-552.png|thumb|[[Media:0353-01-552.pdf|2d (pdf)]]]]
|-
|}
{|
|2 x CONN RECEPT 4POS 3MM SINGLE ROW
|(Molex: 0436450400) digikey p/m WM1847-ND
|-
|4 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/m WM7082CT-ND
|}
----

=== 0353-01-553 - Eyesis4Pi 10369 power cable 1-to-4 (for head cameras) ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-553.png|thumb|[[Media:0353-01-553.pdf|2d (pdf)]]]]
|-
|}

{|
|5 x CONN RECEPT 4POS 3MM SINGLE ROW
|(Molex: 0436450400) digikey p/n WM1847-ND
|-
|10 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/n WM7082CT-ND
|}
----

=== 0353-01-554 - Eyesis4Pi SATA-eSATA power 1-to-2 cable ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-554.png|thumb|[[Media:0353-01-554.pdf|2d (pdf)]]]]
|-
|}
{|
|1 x CONN RECEPT 4POS 3MM SINGLE ROW
|(Molex: 0436450400) digikey p/n WM1847-ND
|-
|2 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/n WM7082CT-ND
|-
|2 x CONN SOCKET 2POS 1.25MM CRIMP
|digikey p/n H1563-ND
|-
|4 x CONN TERM 26-28AWG CRIMP GOLD
|digikey p/n H1577CT-ND
|}
----

=== 0353-01-555 - Eyesis4Pi Power cable 48V ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-555.png|thumb|[[Media:0353-01-555.pdf|2d (pdf)]]]]
|-
|}
{|
|1 x CONN RECEPT 2POS 3MM SINGLE ROW
|(Molex: 0436450200) digikey p/n WM18457-ND
|-
|2 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/n WM7082CT-ND
|-
|1 x CABLE ASSY ID=2.5mm OD=5.5mm, 1.83m, (18 AWG)
|digikey p/n CP-2209-ND or CP-2218-ND
|}

----

=== 0353-01-556 - Eyesis4Pi mSATA-SATA cable with power ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-556.png|thumb|[[Media:0353-01-556.pdf|2d (pdf)]]]]
|-
|}
{|
|1 x CONN SOCKET HOUSING 2POS 1.25MM
|digikey p/n H2179-ND
|-
|2 x CONN CONTACT 26-30AWG CRIMP GOLD
|digikey p/n H9991CT-ND
|}

Elphel camera parts 0353-01

2017-03-31T17:34:20Z

Mikhail: /* 0353-01-55 - 103385 - FPC 150mm long */

== 0353-01 - cable assemblies ==
=== 0353-01-01 - flex jumper, 30 conductors, 0.5mm pitch, l=30mm, t=0.3mm both ends ===

=== 0353-01-02 - flex jumper, 10 conductors, 0.5mm pitch, l=76mm, t=0.3mm both ends ===
=== 0353-01-021 - flex jumper, 10 conductors, 0.5mm pitch, l=80mm, t=0.3mm both ends, Gold (Au) Plating===

=== 0353-01-022 - flex jumper, 10 conductors, 0.5mm pitch, l=400mm, t=0.3mm both ends, Gold (Au) Plating ===

=== 0353-01-023 - flex jumper, 10 conductors, 0.5mm pitch, l=305mm, t=0.3mm both ends Gold (Au) Plating ===

=== 0353-01-03 - flex jumper, 40 conductors, 0.5mm pitch, l=70mm (one end t=0.3mm, other end t=0.2mm) ===

=== 0353-01-04 - RJ45/DB9F Modular Adapter, wired ===

(Supplier: Cables to Go - Part#: 02941, http://www.cablestogo.com/product.asp?cat_id=107&sku=02941)

The wiring procedure is described on the [[RJ45/DB9F_Modular_Adapter]] page.

=== 0353-01-05 - 6P6C crossed modular cable ===

=== 0353-01-06 - 48V DC Power Injector Cable for custom 12v-36v applications. ===

(Supplier: WISP-router, Inc. - Part#: EZPOEPA02, http://store.wisp-router.com/itemdesc.asp?Tp=&eq=&ic=EZPOEPA02)

=== 0353-01-07 - 48V DC Power Injector Cable - 6 ft. for 48V DC power supply - American ===

(Supplier: Cables4Sure.com http://cables4sure.com/proddetail~prod~260002.htm)

=== 0353-01-08 - 48V DC Power Injector Cable - 6 ft. for 48V DC power supply - European ===

(Supplier: Cables4Sure.com http://cables4sure.com/proddetail~prod~260008.htm)

=== 0353-01-10 - Connector Molex, Microfit 3.0, 4 pins, p/n 43645-0400 ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-10.jpeg|thumb|[[Media:0353-01-10.stp.tar.gz|3d (step)]]  [[Media:0353-01-10.dxf.tar.gz|2d (dxf)]]  [[Media:0353-01-10.pdf|2d (pdf)]]]] ||
|-
|}

=== 0353-01-11 - Connector, Norcom D-sub 26 pins, p/n 180-026-203 ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-11.jpeg|thumb|[[Media:0353-01-11.stp.tar.gz|3d (step)]]  [[Media:0353-01-11.dxf.tar.gz|2d (dxf)]]  [[Media:0353-01-11.pdf|2d (pdf)]]]] ||
|-
|}

=== 0353-01-20 - flex jumper, 30 conductors, 0.5mm pitch, l=2" (50.8mm), t=0.3mm both ends ===
=== 0353-01-201 - flex jumper, 30 conductors, 0.5mm pitch, l=50mm, t=0.3mm both ends ===

=== 0353-01-21 - flex jumper, 30 conductors, 0.5mm pitch, l=4" (101.6mm), t=0.3mm both ends ===
=== 0353-01-211 - flex jumper, 30 conductors, 0.5mm pitch, l=3" (76mm), t=0.3mm both ends ===
=== 0353-01-212 - flex jumper, 30 conductors, 0.5mm pitch, l=100mm, t=0.3mm both ends ===

=== 0353-01-22 - flex jumper, 30 conductors, 0.5mm pitch, l=6" (152.4mm), t=0.3mm both ends ===
=== 0353-01-221 - flex jumper, 30 conductors, 0.5mm pitch, l=150mm, t=0.3mm both ends ===

=== 0353-01-23 - flex jumper, 30 conductors, 0.5mm pitch, l=8" (203.2mm), t=0.3mm both ends ===
=== 0353-01-231 - flex jumper, 30 conductors, 0.5mm pitch, l=200mm t=0.3mm both ends ===
=== 0353-01-232 - flex jumper, 30 conductors, 0.5mm pitch, l=250mm t=0.3mm both ends ===

=== 0353-01-25 - flex jumper, 4 conductors, 0.5mm pitch, l=2" (50.8mm), t=0.3mm both ends ===
=== 0353-01-251 - flex jumper, 4 conductors, 0.5mm pitch, l=50mm, t=0.3mm both ends, Gold (Au) Plating ===

=== 0353-01-252 - flex jumper, 4 conductors, 0.5mm pitch, l=200mm, t=0.3mm both ends, Gold (Au) Plating ===

=== 0353-01-253 - flex jumper, 4 conductors, 0.5mm pitch, l=500mm, t=0.3mm both ends, Gold (Au) Plating ===

----

=== 0353-01-40 - RJFTV21N - sealed 8p8n connector ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-40.jpeg|thumb|[[Media:0353-01-40.stp.tar.gz|3d (step)]]]]
|-
|}
----
=== 0353-01-41 - USBFTV21N - sealed USB connector ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-41.jpeg|thumb|[[Media:0353-01-41.stp.tar.gz|3d (step)]]]]
|-
|}
----
=== 0353-01-42 - Sealed 3-pin connector p/n D38999-20JA98SN ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-42.jpeg|thumb|[[Media:0353-01-42.stp.tar.gz|3d (step)]]]]
|-
|}

----
=== 0353-01-43 - SATA (M) to eSATA (F) Cable Assembly, 0.5m ===

{{Cad4|0353-01-43}}

----

=== 0353-01-44 - SATA to SATA Cable Assembly, 1.0m ===

----

=== 0353-01-45 - eSATA to eSATA Cable Assembly ===
=== 0353-01-46 - SATA to SATA Cable Assembly 500mm, p/n 5602-44-0142A-500 ===

=== 0353-01-47 - Micro SATA 1.8" combo 5V & 3.3V Power & SATA cable, p/n MS16P15PMWVD7S ===

=== 0353-01-50 - FPC flexible printed circuit 90 degree for panoramic head ===
=== 0353-01-51 - FPC flexible printed circuit straight for panoramic head ===
----

=== 0353-01-52 - 103383 - FPC 450mm long ===
----

=== 0353-01-53 - 103384 - FPC 70mm long ===
----

=== 0353-01-55 - 103385 - FPC 150mm long ===
Gerber files: [[Media:103385A_gerber.tar.gz‎|103385A_gerber.tar.gz]]
----

=== 0353-01-56 - 103386 - FPC 100mm long ===
----

=== 0353-01-57 - 103387 - FPC 50mm long ===
----

=== 0353-01-58 - 103388 - FPC 250mm long ===
----

=== 0353-01-54 - Eyesis4Pi GPS receiver (Locosys LS2xxxx) cable ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-52.png|thumb|[[Media:0353-01-52.pdf|2d (pdf)]]]]
|-
|}
{|
|-
| 1x CONN SOCKET 8POS 1.25MM CRIMP
| digikey p/n H1569-ND
|-
| 6x CONN TERM 26-28AWG CRIMP GOLD
| digikey p/n H1577CT-ND
|-
| 1x CONN SOCKET 6POS 0.100 W/RAMP/RIB
| digikey p/n WM2616-ND
|-
| 6x CONN RCPT CRIMP 22-30AWG GOLD
| digikey p/n WM3725CT-ND or similar
|}
----

=== 0353-01-551 - Eyesis4Pi power cable for SSD MUX ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-551.png|thumb|[[Media:0353-01-551.pdf|2d (pdf)]]]]
|-
|}
{|
|1 x CONN RECEPT 2POS 3MM SINGLE ROW
|(Molex: 0436450200) digikey p/n WM1845-ND
|-
|1 x CONN RECEPT 4POS 3MM SINGLE ROW
|(Molex: 0436450400) digikey p/n WM1847-ND
|-
|4 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/n WM7082CT-ND
|}
----

=== 0353-01-552 - Eyesis4Pi 10369 power cable for stereo pair camera & switch ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-552.png|thumb|[[Media:0353-01-552.pdf|2d (pdf)]]]]
|-
|}
{|
|2 x CONN RECEPT 4POS 3MM SINGLE ROW
|(Molex: 0436450400) digikey p/m WM1847-ND
|-
|4 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/m WM7082CT-ND
|}
----

=== 0353-01-553 - Eyesis4Pi 10369 power cable 1-to-4 (for head cameras) ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-553.png|thumb|[[Media:0353-01-553.pdf|2d (pdf)]]]]
|-
|}

{|
|5 x CONN RECEPT 4POS 3MM SINGLE ROW
|(Molex: 0436450400) digikey p/n WM1847-ND
|-
|10 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/n WM7082CT-ND
|}
----

=== 0353-01-554 - Eyesis4Pi SATA-eSATA power 1-to-2 cable ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-554.png|thumb|[[Media:0353-01-554.pdf|2d (pdf)]]]]
|-
|}
{|
|1 x CONN RECEPT 4POS 3MM SINGLE ROW
|(Molex: 0436450400) digikey p/n WM1847-ND
|-
|2 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/n WM7082CT-ND
|-
|2 x CONN SOCKET 2POS 1.25MM CRIMP
|digikey p/n H1563-ND
|-
|4 x CONN TERM 26-28AWG CRIMP GOLD
|digikey p/n H1577CT-ND
|}
----

=== 0353-01-555 - Eyesis4Pi Power cable 48V ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-555.png|thumb|[[Media:0353-01-555.pdf|2d (pdf)]]]]
|-
|}
{|
|1 x CONN RECEPT 2POS 3MM SINGLE ROW
|(Molex: 0436450200) digikey p/n WM18457-ND
|-
|2 x CONN SOCKET 20-24AWG GOLD
|(Molex: 0462350001) digikey p/n WM7082CT-ND
|-
|1 x CABLE ASSY ID=2.5mm OD=5.5mm, 1.83m, (18 AWG)
|digikey p/n CP-2209-ND or CP-2218-ND
|}

----

=== 0353-01-556 - Eyesis4Pi mSATA-SATA cable with power ===
{| border="0" cellpadding="2"
|-
| [[Image:0353-01-556.png|thumb|[[Media:0353-01-556.pdf|2d (pdf)]]]]
|-
|}
{|
|1 x CONN SOCKET HOUSING 2POS 1.25MM
|digikey p/n H2179-ND
|-
|2 x CONN CONTACT 26-30AWG CRIMP GOLD
|digikey p/n H9991CT-ND
|}

Elphel camera parts 0393-27

2017-02-23T22:18:06Z

Mikhail: /* 0393-27-20 - IMU+GPS enclosure */

[[Elphel_camera_parts_0393|Elphel NC393 series camera parts]]

All parts on this page were prepared for 3D printing. Some of them have support elements manually place in most critical parts, so you do not need to enable support elements in your slicer software. All those elements can be easily removed after printing. We used Ultimaker2 with 0.4 mm nozzle for 3D printing all of these parts and achieved good results with 0.7 mm wall thickness and 20% infill density. We posted some examples of 3D printed parts on [http://blog.elphel.com/2016/05/3d-print-your-camera-freedom/ our blog]

One of the parts below, 0393-27-07, is a helper object. It was specifically created for cutting out of SFE mount place in custom designs.

=== 0393-27-01f - C/CS SFE adapter ===
{{Cad4c|0393-27-01f}}
----
=== 0393-27-02d - Adapter for camera body ===
{{Cad4c|0393-27-02d}}
----
=== 0393-27-03c - Support frame adapter ===
{{Cad4c|0393-27-03c}}
----
=== 0393-27-04 - Cable strain relief for 0393-27-02d, 0393-27-2e ===
{{Cad4c|0393-27-04}}
----

=== 0393-27-05 - Cable strain relief for 0393-27-01f ===
{{Cad4c|0393-27-05}}
----
=== 0393-27-06 - Cable strain relief for 0393-27-03c ===
{{Cad4c|0393-27-06}}
----
=== 0393-27-07 - SFE cutout part ===
{{Cad4c|0393-27-07}}
----
=== 0393-27-08a - SFE adapter ===
{{Cad4c|0393-27-08a}}
----
=== 0393-27-09 - SFE adapter ===
{{Cad4c|0393-27-09}}
----
=== 0393-27-10 - Cable strain relief for 0393-27-03c or 0393-27-02d ===
{{Cad4c|0393-27-10}}
----
=== 0393-27-12 - SFE support platform for press fit kit ===
This platform facilitates disk springs support pins installation into SFEs.
{{Cad4c|0393-27-12}}
----

=== 0393-27-13 - Tube cap ===
{{Cad4c|0393-27-13}}
----

=== 0393-27-14 - Mount band ===
This band is used to mount additional parts on top of NC393 camera. One of the possible parts is 0393-27-15 for IMU mount.
{{Cad4c|0393-27-14}}
----

=== 0393-27-15 - IMU support plate ===
This plate is used in combination with 0393-27-14.
{{Cad4c|0393-27-15}}
----

=== 0393-27-16 - Calibration SFE housing ===
{{Cad4c|0393-27-16}}
----

=== 0393-27-17 - Cable strain relief for calibration SFE housing ===
Used with 0393-27-16.
{{Cad4c|0393-27-17}}
----
=== 0393-27-18 - Support frame adapter, short ===
{{Cad4c|0393-27-18}}
----
=== 0393-27-19 - IMU+GPS support plate ===
{{Cad4c|0393-27-19}}
----
=== 0393-27-20 - IMU+GPS enclosure ===
{{Cad4c|0393-27-20}}
----
=== 0393-27-21 - Back panel extender for SSD rack ===
{{Cad4c|0393-27-21}}
----

Elphel camera parts 0353-97

2017-02-23T22:16:11Z

Mikhail: /* 0353-97-95 Jack screw, #4-40, for D-Sub connector, L = 8.3 mm */

[[Elphel_camera_parts]]
== 0353-97 - Screws other than M2 and M2.5 ==
=== 0353-97-01 - Screw, Button cap, Stainless Steel 18-8, #4-40, 0.19"long ===
McMaster p/n 92949A105
{{Cad4|0353-97-01}}

----
=== 0353-97-02 - Screw, Button cap, Stainless Steel 18-8, #4-40, 1/8"long ===
McMaster p/n 91255A103
{{Cad4|0353-97-02}}

----
=== 0353-97-03 - Screw flat #4-40, Philips ===
McMaster p/n 91771A106
{{Cad4|0353-97-03}}

----

=== 0353-97-05 - Stud 1/4-20, l=7" ===
McMaster p/n 95475A569
{{Cad4|0353-97-05}}

----

=== 0353-97-10 - Screw M3, Flat, Socket Cap, Steel, Black, l=8mm ===
McMaster p/n 91294A128
{{Cad4|0353-97-10}}

----

=== 0353-97-12 - Screw M3, socket head, l=10mm ===
McMaster p/n 91292A113
{{Cad4|0353-97-12}}

----

=== 0353-97-13 - Set Screw M3 x 6mm With Nylon tip ===
McMaster p/n 93285A115
{{Cad4|0353-97-13}}

----
=== 0353-97-14 - Screw M3,Socket Cap, l=6mm ===
McMaster p/n 91292A111
{{Cad4|0353-97-14}}

----

=== 0353-97-15 - Screw Shoulder M3, l=4mm, D=4mm ===
McMaster p/n 90270A651
{{Cad4|0353-97-15}}

----

=== 0353-97-16 - Screw Shoulder M3, l=5mm, D=4mm ===
McMaster p/n 90270A652
{{Cad4|0353-97-16}}

----

=== 0353-97-17 - Screw Shoulder M3, l=8mm, D=4mm ===
McMaster p/n 90270A654
{{Cad4|0353-97-17}}

----
=== 0353-97-18 - screw M3 laptop HDD
----
=== 0353-97-19 - Flat Head Socket Cap Screw M3, l=10mm ===
McMaster p/n 92125A130
----

=== 0353-97-20 - Screw, M1.6, Socket Cap, Steel, Black, l=6mm ===
McMaster p/n 91290A023
{{Cad4|0353-97-20}}

----
=== 0353-97-201 - Screw, M1.6, Socket Cap, Stainless Steel 18-8, l=6mm ===
McMaster p/n 91292A263
{{Cad4|0353-97-201}}

----

=== 0353-97-21 - Screw M1.6, socket head, l=4mm ===
McMaster p/n 91290A021
{{Cad4|0353-97-21}}

----
=== 0353-97-22 - Screw M1.6x5, pan head, Phillips ===
McMaster p/n 92005A004
{{Cad4|0353-97-22}}

----
=== 0353-97-23 - Screw M1.6, socket head, l=5mm, Steel, Black Oxide ===
McMaster p/n 91290A022
{{Cad4|0353-97-23}}

----

=== 0353-97-231 - Screw M1.6, socket head, l=5mm, Stainless Steel 18-8 ===
McMaster p/n 91292A262
{{Cad4|0353-97-231}}

----

=== 0353-97-24 - Screw M1.6, socket head, l=12mm ===
{{Cad4|0353-97-24}}

----

=== 0353-97-241 - Screw M1.6, socket head, l=12mm, Stainless Steel 18-8 ===
McMaster p/n 91292A266
{{Cad4|0353-97-241}}

----

=== 0353-97-25 - Screw M1.6, socket head, l=10mm, Stainless Steel 18-8 ===
McMaster p/n 91292A265
{{Cad4|0353-97-25}}

----
=== 0353-97-26 - Screw M1.6, socket head, l=3mm, Black anodize ===
McMaster p/n 91290A020
{{Cad4a|0353-97-26}}

=== 0353-97-30 - Screw, M5, Socket Cap, l=10mm ===
----

=== 0353-97-31 - Screw, M5, Socket Cap, l=16mm ===
18-8 Stainless Steel
McMaster p/n 91292A126
----

=== 0353-97-32 - Screw M5, socket head, l=8mm ===
18-8 Stainless Steel

McMaster p/n 91292A191
{{Cad4|0353-97-32}}

----
=== 0353-97-34 - Screw M5, socket head, l=6mm ===
18-8 Stainless Steel

McMaster p/n 91292A189
{{Cad4|0353-97-34}}

----
=== 0353-97-35 - Screw M5, socket head, l=12mm ===
18-8 Stainless Steel
McMaster p/n 91292A125
----
=== 0353-97-36 - Screw M5, socket head, l=14mm ===
18-8 Stainless Steel
McMaster p/n 91292A058
----
=== 0353-97-37 - Screw M5, socket head, l=25mm ===
18-8 Stainless Steel
McMaster p/n 91292A129
----
=== 0353-97-38 - Screw M5, socket head, l=20mm ===
18-8 Stainless Steel

McMaster p/n 91292A128
{{Cad4|0353-97-38}}

----

=== 0353-97-39 - Set screw M5x5 ===
{{Cad4|0353-97-39}}

----

=== 0353-97-40 - Screw, M4, Socket Cap, l=16mm ===
18-8 Stainless Steel
McMaster p/n 91292A118
----

=== 0353-97-42 - Screw Shoulder M5, l=20mm, D=6mm ===
McMaster p/n 90278A406
{{Cad4|0353-97-42}}

----

=== 0353-97-43 - Screw Shoulder M5, l=45mm, D=6mm ===
McMaster p/n 92981A130
{{Cad4|0353-97-43}}

----

=== 0353-97-44 - Socket screw M4, l=25mm ===
McMaster p/n 91292A122
{{Cad4|0353-97-44}}

----
=== 0353-97-45 - Socket screw M4, l=30mm ===
McMaster p/n 91292A130
{{Cad4|0353-97-45}}

----

=== 0353-97-46 - M4x0.7 Socket Screw, l=10mm ===
{{Cad4|0353-97-46}}

----

=== 0353-97-47 - M4x0.7 Socket Screw, l=40mm ===
McMaster p/n 91292A132
{{Cad4|0353-97-47}}

----

=== 0353-97-48 - M4x0.7 Socket Screw, l=12mm ===
McMaster p/n 91292A117
{{Cad4|0353-97-48}}

----

=== 0353-97-50 - Screw, M6, Socket Cap, l=16mm ===
18-8 Stainless Steel
McMaster p/n 91292A135
{{Cad4|0353-97-50}}

----

=== 0353-97-51 - Screw, M6, Socket Cap, l=12mm ===
18-8 Stainless Steel
McMaster p/n 91292A134

----

=== 0353-97-52 - Set screw, M6, l=6mm ===
18-8 Stainless Steel
McMaster p/n 92015A126
{{Cad4|0353-97-52}}

----

=== 0353-97-54 - Socket Screw, M6 l=25mm ===
{{Cad4|0353-97-54}}

----

=== 0353-97-541 - Socket Screw, M6 l=50mm ===
McMaster p/n 91292A144
{{Cad4|0353-97-541}}

----

=== 0353-97-57 - Shoulder screw, M6 OD=8.0, l=6.0 ===
{{Cad4|0353-97-57}}

----

=== 0353-97-58 - Shoulder screw, M6 OD=8.0, l=20.0 ===
{{Cad4|0353-97-58}}

----

=== 0353-97-59 - Press-fit screw head M6 ===
McMaster p/n 91175A710
{{Cad4|0353-97-59}}

----

=== 0353-97-61 - Screw M8 modified - REDUCED HEAD SIZE ===
18-8 Stainless Steel

Can be made of McMaster 92855A710
{{Cad4|0353-97-61}}

----

=== 0353-97-62 - Screw M8, socket head, l=25mm ===
{{Cad4|0353-97-62}}

----

=== 0353-97-65 - Screw M10, socket head, l=50mm ===
{{Cad4|0353-97-65}}

----

=== 0353-97-66 - Screw M10, socket head, l=30mm ===
{{Cad4|0353-97-66}}

----

=== 0353-97-70 - Thumb Screw M3, l=16mm ===
McMaster p/n 92581A150

{{Cad4|0353-97-70}}

----

=== 0353-97-71 - Screw M3, socket head, l=5mm ===
McMaster p/n 91290A021

{{Cad4|0353-97-71}}

----

=== 0353-97-72 - Set screw M3, l=6mm ===
McMaster p/n 92015A104

{{Cad4|0353-97-72}}

----

=== 0353-97-73 - Set screw M3, l=3mm, knurled cup point ===

{{Cad4|0353-97-73}}

----

=== 0353-97-80 Nylon set screw M4, slotted, l=3mm ===
{{Cad4|0353-97-80}}

----

=== 0353-97-90 Set Screw, M10x1.5, l=20mm ===
{{Cad4|0353-97-90}}

----

=== 0353-97-91 Socket head cap screw, #4-40, l=1/2", nylon ===
McMaster p/n 95868A260
{{Cad4a|0353-97-91}}

----

=== 0353-97-92 Plastic thumb screw head ===
McMaster p/n 94052A021
{{Cad4a|0353-97-92}}

----

=== 0353-97-93 Jack screw, #4-40, for D-Sub connector, L = 7.92 mm ===
Digi-Key p/n 36-7230-5-ND
{{Cad4a|0353-97-93}}

----
=== 0353-97-94 Torx rounded head thread-forming screw, #2-28, for plastic ===
McMaster p/n 96001A164
{{Cad4a|0353-97-94}}

----
=== 0353-97-95 Jack screw, #4-40, for D-Sub connector, L = 8.3 mm ===
Digi-Key p/n 609-1420-ND, hardware included
{{Cad4a|0353-97-95}}

----
=== 0353-97-96 Screw M3, socket head, L = 30 mm, partially threaded ===
McMaster p/n 91290A130
{{Cad4a|0353-97-96}}

----

FPC cables

2017-02-21T22:45:41Z

Mikhail: /* 0353-01-51 (asymmetrical) */

==[[Elphel_camera_parts_0353-01#0353-01-51_-_FPC_flexible_printed_circuit_straight_for_panoramic_head|0353-01-51]] (asymmetrical)==
{|
|[[Image:Fpc_cable.jpeg|500px|thumb|Fig.1 L=70mm]]
|[[Image:Fpc_cable_conn.jpeg|500px|thumb|Fig.2 Proper connecting: sensor and 10353 system board]]
|-
|[[Image:Fpc_cable_conn_10393.jpeg|500px|thumb|Fig.3 Proper connecting: sensor and 10393 system board (same principle as on Fig.2)]]
|}

{| class="wikitable"
|+Gerber files for FPC cables
|-
!File name
!Description
|-
|[[Media:103385A_gerber.tar.gz‎|103385A_gerber.tar.gz]]
|Straight flexible flat cable, 150 mm long.
|-
|[[Media:103386A gerber.tar.gz|103386A gerber.tar.gz]]
|Straight flexible flat cable, 100 mm long.
|-
|[[Media:103387A gerber.tar.gz|103387A gerber.tar.gz]]
|Straight flexible flat cable, 50 mm long.
|-
|[[Media:103388A gerber.tar.gz|103388A gerber.tar.gz]]
|Straight flexible flat cable, 250 mm long.
|-
|[[Media:1033890 gerber.tar.gz|1033890 gerber.tar.gz]]
|Straight flexible flat cable with diff pairs and 100 Ohm impedance matching, 100 mm long. This is a tightly coupled option without reference plane.
|-
|[[Media:103389A gerber.tar.gz|103389A gerber.tar.gz]]
|Straight flexible flat cable with diff pairs and 100 Ohm impedance matching, 100 mm long. This is a loosely coupled option with reference plane on bottom layer.
|-
|[[Media:1033900 gerber.tar.gz|1033900 gerber.tar.gz]]
|Straight flexible flat cable with diff pairs and 100 Ohm impedance matching, 150 mm long. This is a tightly coupled option without reference plane.
|-
|[[Media:1033910 gerber.tar.gz|1033910 gerber.tar.gz]]
|Straight flexible flat cable with diff pairs and 100 Ohm impedance matching, 450 mm long. This is a tightly coupled option without reference plane.
|}

[[Category:Elphel353]]
[[Category:Elphel393]]

File:1033910 gerber.tar.gz

2017-02-21T22:43:08Z

Mikhail:

File:1033900 gerber.tar.gz

2017-02-21T22:41:45Z

Mikhail:

File:103389A gerber.tar.gz

2017-02-21T22:39:42Z

Mikhail:

File:1033890 gerber.tar.gz

2017-02-21T22:38:39Z

Mikhail:

File:103388A gerber.tar.gz

2017-02-21T22:37:31Z

Mikhail:

File:103387A gerber.tar.gz

2017-02-21T22:36:24Z

Mikhail:

File:103386A gerber.tar.gz

2017-02-21T22:35:10Z

Mikhail:

File:103385A gerber.tar.gz

2017-02-21T22:21:51Z

Mikhail:

Elphel camera assemblies

2017-02-17T21:34:02Z

Mikhail: /* NC393-M2260-F-CS-IMU camera */

[[Elphel_camera_parts_0393]]

[[Elphel_camera_parts | Elphel_camera_parts_0353]]
==Camera assemblies ==

=== EYESIS4PI-26-393 camera ===
{{Cad4c_assembly|EYESIS4PI-26-393}}
----

=== NC393-M2242-CS camera ===
{{Cad4c_assembly|NC393-M2242-CS}}
----
=== NC393-M2260-CS camera ===
{{Cad4c_assembly|NC393-M2260-CS}}
----
=== NC393-M2260-F-CS camera ===
{{Cad4c_assembly|NC393-M2260-F-CS}}
----

=== NC393-M2260-F-CS-IMU camera ===
{{Cad4c_assembly|NC393-M2260-F-CS-IMU}}
----
=== NC393-M2260-F-CS-IMU-GPS camera ===
{{Cad4c_assembly|NC393-M2260-F-CS-IMU-GPS}}
----

=== MC393F21 camera ===
{{Cad4c_assembly|MC393F21}}
----
=== NC393-4PI4 camera ===
{{Cad4c_assembly|NC393-4PI4}}
----
=== NC393-4PI4-IMU-GPS camera with IMU and GPS modules ===
{{Cad4c_assembly|NC393-4PI4-IMU-GPS}}
----

=== EYESIS4PI-26 camera ===
{{Cad4c_assembly|EYESIS4PI-26}}
----
=== NC353L camera ===
{{Cad4c_assembly|NC353L}}
----
=== NC353L-369 camera ===
{{Cad4c_assembly|NC353L-369}}
----
=== MNC354-2-STEREO camera ===
{{Cad4c_assembly|MNC354-2-STEREO}}
----
=== NC353L-PHG camera ===
{{Cad4c_assembly|NC353L-PHG}}
----
=== NC353L-PHG3 camera ===
{{Cad4c_assembly|NC353L-PHG3}}
----
=== MNC354-2B camera ===
{{Cad4c_assembly|MNC354-2B}}
----

Elphel camera parts 0353-94

2017-02-17T19:42:15Z

Mikhail: /* 0353-94-90 - Washer, shim. OD=18mm, ID=12mm,t=0.5 */

[[Elphel_camera_parts]]
== 0353-94 - washers for other than M2 and M2.5 ==

=== 0353-94-01 - Washer for M1.6, stainless steel 18-8 ===
McMaster p/n 93475A190
{{Cad4|0353-94-01}}

----

=== 0353-94-02 - Washer for 1/4", stainless steel 18-8 ===
McMaster p/n 90107A029
{{Cad4|0353-94-02}}

----

=== 0353-94-11 - Washer for M3 ===
t=0.7mm, OD=9mm, ID=3.2mm

McMaster p/n 91116A120
{{Cad4|0353-94-11}}

----
=== 0353-94-12 - Washer for M3, OD=7mm, stainless steel 18-8 ===

McMaster p/n 93475A210

----
=== 0353-94-13 - Lock Washer for M3, stainless steel 18-8 ===

McMaster p/n 92148A150

----

=== 0353-94-41 - Washer for M4, plastic ===
OD=9mm, ID=4.3mm, t=0.67mm

McMaster p/n 95610A350
{{Cad4|0353-94-41}}

----

=== 0353-94-42 - Washer for M4 ===
OD=9mm, ID=4.3mm, t=0.7mm

McMaster p/n 93475A230
{{Cad4|0353-94-42}}

----
=== 0353-94-43 - Lock Washer for M4, stainless steel 18-8 ===

McMaster p/n 92148A160

----

=== 0353-94-44 - Lock Washer for M4, OD=7mm, stainless steel 18-8 ===
McMaster p/n 91111A121
{{Cad4|0353-94-44}}

----

=== 0353-94-51 - Washer for M5, OD=10mm, stainless steel 18-8 ===

McMaster p/n 93475A240

----
=== 0353-94-52 - Lock Washer for M5, stainless steel 18-8 ===

McMaster p/n 92148A170

----

=== 0353-94-61 - Washer, plastic ===
ID=0.25", OD=0.38", t=0.03+/-0.1"

McMaster p/n 95606A120
{{Cad4|0353-94-61}}

----

=== 0353-94-62 - Washer, OD14.0, ID=8.0, t=1.0 ===
{{Cad4|0353-94-62}}

----

=== 0353-94-63 - Washer, shim ID=8mm . OD=14, t=0.3===
{{Cad4|0353-94-63}}

----

=== 0353-94-64 - Lock washer M8, high collar ===
{{Cad4|0353-94-64}}

----

=== 0353-94-65 - Washer for M10, OD=20mm ===
{{Cad4|0353-94-65}}

----

=== 0353-94-66 - Lock washer, M10 ===
{{Cad4|0353-94-66}}

----

=== 0353-94-67 - Lock washer M10, high collar ===
{{Cad4|0353-94-67}}

----

=== 0353-94-71 - Washer for M6, OD=12mm, stainless steel 18-8 ===

McMaster p/n 93475A250

----
=== 0353-94-72 - Lock Washer for M6, stainless steel 18-8 ===

McMaster p/n 92148A180

----
=== 0353-94-81 - Washer for M8, OD=16mm, stainless steel 18-8 ===
McMaster p/n 93475A270

{{Cad4|0353-94-81}}

----

=== 0353-94-82 - Lock Washer for M8, stainless steel 18-8 ===

McMaster p/n 92148A200

----

=== 0353-94-90 - Washer, shim. OD=18mm, ID=12mm,t=0.5 ===
{{Cad4|0353-94-90}}

----
=== 0353-94-92 - Compensating washer, OD=6mm, t=0.8 ===
Part of hardware included to Digi-Key p/n 609-1420-ND
{{Cad4a|0353-94-92}}

----

== 0353-95 - washers for M2.5 ==

=== 0353-95-01 - M2.5 washer, OD=6mm, stainless steel 18-8 ===
McMaster p/n 93475A196

----
=== 0353-95-02 - Lock Washer for M2.5, stainless steel 18-8 ===

McMaster p/n 92148A070

----

== 0353-96 - washers for M2 ==
=== 0353-96-01 - Washer for M2, Stainless Steel 316, OD=5mm, ID=2.2mm, t=-0.3mm ===
McMaster p/n 90965A110
{{Cad4|0353-96-01}}

----
=== 0353-96-02 - M2 washer, stainless steel 18-8 ===
McMaster p/n 93475A195

----
=== 0353-96-03 - Lock Washer for M2, stainless steel 18-8 ===

McMaster p/n 92148A050

{{Cad4|0353-96-03}}

----

Elphel camera parts 0353-97

2017-02-17T19:27:36Z

Mikhail: /* 0353-97-93 Jack screw, #4-40, for D-Sub connector */

Elphel camera parts 0353-97

2017-02-14T18:06:42Z

Mikhail: /* 0353-97-92 Plastic thumb screw head */

[[Elphel_camera_parts]]
== 0353-97 - Screws other than M2 and M2.5 ==
=== 0353-97-01 - Screw, Button cap, Stainless Steel 18-8, #4-40, 0.19"long ===
McMaster p/n 92949A105
{{Cad4|0353-97-01}}

----
=== 0353-97-02 - Screw, Button cap, Stainless Steel 18-8, #4-40, 1/8"long ===
McMaster p/n 91255A103
{{Cad4|0353-97-02}}

----
=== 0353-97-03 - Screw flat #4-40, Philips ===
McMaster p/n 91771A106
{{Cad4|0353-97-03}}

----

=== 0353-97-05 - Stud 1/4-20, l=7" ===
McMaster p/n 95475A569
{{Cad4|0353-97-05}}

----

=== 0353-97-10 - Screw M3, Flat, Socket Cap, Steel, Black, l=8mm ===
McMaster p/n 91294A128
{{Cad4|0353-97-10}}

----

=== 0353-97-12 - Screw M3, socket head, l=10mm ===
McMaster p/n 91292A113
{{Cad4|0353-97-12}}

----

=== 0353-97-13 - Set Screw M3 x 6mm With Nylon tip ===
McMaster p/n 93285A115
{{Cad4|0353-97-13}}

----
=== 0353-97-14 - Screw M3,Socket Cap, l=6mm ===
McMaster p/n 91292A111
{{Cad4|0353-97-14}}

----

=== 0353-97-15 - Screw Shoulder M3, l=4mm, D=4mm ===
McMaster p/n 90270A651
{{Cad4|0353-97-15}}

----

=== 0353-97-16 - Screw Shoulder M3, l=5mm, D=4mm ===
McMaster p/n 90270A652
{{Cad4|0353-97-16}}

----

=== 0353-97-17 - Screw Shoulder M3, l=8mm, D=4mm ===
McMaster p/n 90270A654
{{Cad4|0353-97-17}}

----
=== 0353-97-18 - screw M3 laptop HDD
----
=== 0353-97-19 - Flat Head Socket Cap Screw M3, l=10mm ===
McMaster p/n 92125A130
----

=== 0353-97-20 - Screw, M1.6, Socket Cap, Steel, Black, l=6mm ===
McMaster p/n 91290A023
{{Cad4|0353-97-20}}

----
=== 0353-97-201 - Screw, M1.6, Socket Cap, Stainless Steel 18-8, l=6mm ===
McMaster p/n 91292A263
{{Cad4|0353-97-201}}

----

=== 0353-97-21 - Screw M1.6, socket head, l=4mm ===
McMaster p/n 91290A021
{{Cad4|0353-97-21}}

----
=== 0353-97-22 - Screw M1.6x5, pan head, Phillips ===
McMaster p/n 92005A004
{{Cad4|0353-97-22}}

----
=== 0353-97-23 - Screw M1.6, socket head, l=5mm, Steel, Black Oxide ===
McMaster p/n 91290A022
{{Cad4|0353-97-23}}

----

=== 0353-97-231 - Screw M1.6, socket head, l=5mm, Stainless Steel 18-8 ===
McMaster p/n 91292A262
{{Cad4|0353-97-231}}

----

=== 0353-97-24 - Screw M1.6, socket head, l=12mm ===
{{Cad4|0353-97-24}}

----

=== 0353-97-241 - Screw M1.6, socket head, l=12mm, Stainless Steel 18-8 ===
McMaster p/n 91292A266
{{Cad4|0353-97-241}}

----

=== 0353-97-25 - Screw M1.6, socket head, l=10mm, Stainless Steel 18-8 ===
McMaster p/n 91292A265
{{Cad4|0353-97-25}}

----
=== 0353-97-26 - Screw M1.6, socket head, l=3mm, Black anodize ===
McMaster p/n 91290A020
{{Cad4a|0353-97-26}}

=== 0353-97-30 - Screw, M5, Socket Cap, l=10mm ===
----

=== 0353-97-31 - Screw, M5, Socket Cap, l=16mm ===
18-8 Stainless Steel
McMaster p/n 91292A126
----

=== 0353-97-32 - Screw M5, socket head, l=8mm ===
18-8 Stainless Steel

McMaster p/n 91292A191
{{Cad4|0353-97-32}}

----
=== 0353-97-34 - Screw M5, socket head, l=6mm ===
18-8 Stainless Steel

McMaster p/n 91292A189
{{Cad4|0353-97-34}}

----
=== 0353-97-35 - Screw M5, socket head, l=12mm ===
18-8 Stainless Steel
McMaster p/n 91292A125
----
=== 0353-97-36 - Screw M5, socket head, l=14mm ===
18-8 Stainless Steel
McMaster p/n 91292A058
----
=== 0353-97-37 - Screw M5, socket head, l=25mm ===
18-8 Stainless Steel
McMaster p/n 91292A129
----
=== 0353-97-38 - Screw M5, socket head, l=20mm ===
18-8 Stainless Steel

McMaster p/n 91292A128
{{Cad4|0353-97-38}}

----

=== 0353-97-39 - Set screw M5x5 ===
{{Cad4|0353-97-39}}

----

=== 0353-97-40 - Screw, M4, Socket Cap, l=16mm ===
18-8 Stainless Steel
McMaster p/n 91292A118
----

=== 0353-97-42 - Screw Shoulder M5, l=20mm, D=6mm ===
McMaster p/n 90278A406
{{Cad4|0353-97-42}}

----

=== 0353-97-43 - Screw Shoulder M5, l=45mm, D=6mm ===
McMaster p/n 92981A130
{{Cad4|0353-97-43}}

----

=== 0353-97-44 - Socket screw M4, l=25mm ===
McMaster p/n 91292A122
{{Cad4|0353-97-44}}

----
=== 0353-97-45 - Socket screw M4, l=30mm ===
McMaster p/n 91292A130
{{Cad4|0353-97-45}}

----

=== 0353-97-46 - M4x0.7 Socket Screw, l=10mm ===
{{Cad4|0353-97-46}}

----

=== 0353-97-47 - M4x0.7 Socket Screw, l=40mm ===
McMaster p/n 91292A132
{{Cad4|0353-97-47}}

----

=== 0353-97-48 - M4x0.7 Socket Screw, l=12mm ===
McMaster p/n 91292A117
{{Cad4|0353-97-48}}

----

=== 0353-97-50 - Screw, M6, Socket Cap, l=16mm ===
18-8 Stainless Steel
McMaster p/n 91292A135
{{Cad4|0353-97-50}}

----

=== 0353-97-51 - Screw, M6, Socket Cap, l=12mm ===
18-8 Stainless Steel
McMaster p/n 91292A134

----

=== 0353-97-52 - Set screw, M6, l=6mm ===
18-8 Stainless Steel
McMaster p/n 92015A126
{{Cad4|0353-97-52}}

----

=== 0353-97-54 - Socket Screw, M6 l=25mm ===
{{Cad4|0353-97-54}}

----

=== 0353-97-541 - Socket Screw, M6 l=50mm ===
McMaster p/n 91292A144
{{Cad4|0353-97-541}}

----

=== 0353-97-57 - Shoulder screw, M6 OD=8.0, l=6.0 ===
{{Cad4|0353-97-57}}

----

=== 0353-97-58 - Shoulder screw, M6 OD=8.0, l=20.0 ===
{{Cad4|0353-97-58}}

----

=== 0353-97-59 - Press-fit screw head M6 ===
McMaster p/n 91175A710
{{Cad4|0353-97-59}}

----

=== 0353-97-61 - Screw M8 modified - REDUCED HEAD SIZE ===
18-8 Stainless Steel

Can be made of McMaster 92855A710
{{Cad4|0353-97-61}}

----

=== 0353-97-62 - Screw M8, socket head, l=25mm ===
{{Cad4|0353-97-62}}

----

=== 0353-97-65 - Screw M10, socket head, l=50mm ===
{{Cad4|0353-97-65}}

----

=== 0353-97-66 - Screw M10, socket head, l=30mm ===
{{Cad4|0353-97-66}}

----

=== 0353-97-70 - Thumb Screw M3, l=16mm ===
McMaster p/n 92581A150

{{Cad4|0353-97-70}}

----

=== 0353-97-71 - Screw M3, socket head, l=5mm ===
McMaster p/n 91290A021

{{Cad4|0353-97-71}}

----

=== 0353-97-72 - Set screw M3, l=6mm ===
McMaster p/n 92015A104

{{Cad4|0353-97-72}}

----

=== 0353-97-73 - Set screw M3, l=3mm, knurled cup point ===

{{Cad4|0353-97-73}}

----

=== 0353-97-80 Nylon set screw M4, slotted, l=3mm ===
{{Cad4|0353-97-80}}

----

=== 0353-97-90 Set Screw, M10x1.5, l=20mm ===
{{Cad4|0353-97-90}}

----

=== 0353-97-91 Socket head cap screw, #4-40, l=1/2", nylon ===
McMaster p/n 95868A260
{{Cad4a|0353-97-91}}

----

=== 0353-97-92 Plastic thumb screw head ===
McMaster p/n 94052A021
{{Cad4a|0353-97-92}}

----

=== 0353-97-93 Jack screw, #4-40, for D-Sub connector ===
Digi-Key p/n 36-7230-5-ND
{{Cad4a|0353-97-93}}

----

Elphel camera parts 0393-27

2017-02-14T18:03:14Z

Mikhail: /* 0393-27-18 - Support frame adapter, short */

Elphel camera parts 0393-18

2017-02-03T01:15:17Z

Mikhail: /* 0353-18-30 - tripod mount nut, 1/4-20 thread */

[[Elphel_camera_parts_0393|Elphel NC393 series camera parts]]
== 0393-18 - parts external other ==
----
=== 0353-18-01 - Vertical arm for H-camera ===
{{Cad4a|0393-18-01}}
----

=== 0353-18-02 - Horizontal arm for H-camera ===
{{Cad4a|0393-18-02}}
----

=== 0353-18-30 - tripod mount nut, 1/4-20 thread ===
{{Cad4a|0393-18-30}}
----

=== 0353-18-31 - tripod mount plate ===
{{Cad4a|0393-18-31}}
----
=== 0353-18-31A - tripod mount plate, Rev "A" ===
{{Cad4a|0393-18-31A}}
----

=== 0393-18-50 - IMU enclosure ===
{{Cad4a|0393-18-50}}
----
=== 0393-18-51 - Camera top with GPS ===
{{Cad4a|0393-18-51}}
----
=== 0393-18-52 - Camera top without GPS ===
{{Cad4a|0393-18-52}}
----
=== 0393-18-53 - GPS cap ===
{{Cad4a|0393-18-53}}
----
=== 0393-18-53 - Fisheye lens shade ===
{{Cad4a|0393-18-54}}
----

10393 manual

2017-01-11T19:37:01Z

Mikhail: /* Record */

==Important Notes==
* As of 2016/12/15, the software ported from 10353 supports only 5MPix sensors, for 14MPix, please see:
**[http://wiki.elphel.com/index.php?title=Tmp_manual&oldid=14676 older version of this manual with links to older software images]

==In the package==
* 10393 camera system
{|
|[[File:NC393-CS marked ports.jpeg|thumb|200px|Fig.1 10393 interfaces]]
|}
* Power supply wall adapter (default: 18-75V, [[10393_power|more information]])
* CAT6 network cable
* μUSB-to-USB cable
* Recovery μSD card
* If the camera is calibrated the calibration data will be on a separate storage media or on the internal SSD (likely /mnt/sda1)

==Interfaces==
See Fig.1:
{| class="wikitable"
|-
! GigE
| gigabit network
|-
! μSD
| micro SD card slot - boot or storage
|-
! console
| serial console port, use μUSB-to-USB cable
|-
! eSATA+USB
| 2-in-1. Connect USB or eSATA device. USB2.0 host
|-
! μUSB
| USB2.0 host
|-
! sync
| sync multiple cameras or other devices - input/output trigger signal through a 4-conductor 2.5mm audio plug with cable (example: [http://www.digikey.com/products/en?keywords=839-1029-ND digikey])
|}

==Power on==
* Plug in the power supply
* Connect to LAN using the network cable

====Notes====
* Boot time: ~30s
* The default boot is from the on-board NAND flash. [[Boot_options_393|More information]] on available boot options and recovery boot.

==Defaults==
{| class="wikitable"
|-
! IP Address
| 192.168.0.9
|-
! User
| root
|-
! Password
| pass
|}

* The default IP address is set in the ''/etc/elphel393/init_elphel393.py''.
* If present the internal SSD will be formatted into 2 partitions:
** /dev/sda1 - ext4 (~64-100GB)
** /dev/sda2 - raw partition (no file system) for fast recording

==Command line access==
* ssh from PC terminal:
$ ssh root@192.168.0.9

==Serial console access==
* Use a ''microUSB-USB cable'' to connect '''console μUSB port''' (see Fig.1) to PC - the cable's end should be thin enough otherwise interferes with an inserted mmc ('''m'''ulti '''m'''edia '''c'''ard = μSD card).

* In Linux the '''minicom''' program can be used
$ minicom -c on
Most likely the device will be /dev/ttyUSB0. Settings:
* 115200 8N1, no for hardware/software flow control
Refer to the following article for more details on using '''minicom''': [http://wiki.elphel.com/index.php?title=Using_minicom_to_connect_to_Elphel393_camera Using minicom to connect to Elphel393 camera]

==Web user interface (camvc)==
http://192.168.0.9/closeme.html (type in the browser address bar - will be changed soon):
* The page contains links to camvc user interface for each individual camera port.
* camvc was ported from the 10353 camera series:
** change parameters like image format, resolution, auto exposure, auto white balance and more. Alternative way to change parameters is described [[Tmp_manual#Change_parameters|below]].
** pause compressor and search within buffered images
** help tips available - see Fig.2 - select then mouse over a control element of interest
{|
| valign='top'|[[image:Help tips.jpeg|250px|thumb|Fig.2 enable camvc help tips]]
|[[File:Controls with blank.jpeg|300px|thumb|Fig.3 camvc controls]]
|}

==Download live images==
====camvc====
* For a currently opened port (displayed in the window title and as "...sensor_port=0..." in the URL):
{|
|[[image:Camvc image capture.jpeg|250px|thumb|Fig.4 Acquire an image from the Camera Control Interface]]
|}

====browser====
port 0: http://192.168.0.9:2323/img
port 1: http://192.168.0.9:2324/img
port 2: http://192.168.0.9:2325/img
port 3: http://192.168.0.9:2326/img

====command line====
wget http://192.168.0.9:2323/img -O filename.jpeg
wget http://192.168.0.9:2324/img -O filename.jpeg
wget http://192.168.0.9:2325/img -O filename.jpeg
wget http://192.168.0.9:2326/img -O filename.jpeg

==Video==
===Display===
====Multipart JPEG stream====
http://192.168.0.9:2323/mimg
http://192.168.0.9:2324/mimg
http://192.168.0.9:2325/mimg
http://192.168.0.9:2326/mimg

====GStreamer====

gst-launch-1.0 souphttpsrc is-live=true location=http://192.168.0.9:2323/mimg ! jpegdec ! xvimagesink

* Only mjpeg, no rtsp yet.
* More examples at [[Using_gstreamer#Display|Using GStreamer]]

===Record===
* Recording is done by the '''camogm''' program
* If recording to internal or external SSD, please, read about [[Tmp_manual#eSATA_port_switching|eSATA port switching]]
* important: Event logger (GPS, IMU, IMG, EXT) recording is started/stopped separately. See [[Tmp_manual#Record_the_Event_Logger_data_.28GPS.2CIMU.2CIMG_.26_EXT.29|instructions]] below.
* For SATA devices camogm supports:
** recording to a partition with a file system - up to 80MB/s
** (default) faster recording to a partition without a file system (raw partition) avoiding OS calls - up to 220MB/s
* To extract data from a raw partition use '''dd''' or [https://github.com/Elphel/elphel-tools-x393 these scripts] to get the data and split it into images. Follow [[Extracting_images_from_raw_partition | this link]] for details.
* Can record to an mmc partiton or usb.
* [[Using_camogm_with_Elphel393_camera|More info]]
* If the ''prefix'' parameter, which is ''absolute path + prefix'', for a channel is not set the file will be written somewhere to rootfs.
** if prefix is empty then the ''absolute path'' must end with a slash.

====browser====
Example 1: (provide a correct media mount point - /mnt/sda1/)

* http://192.168.0.9/camogmgui.php

Follow [[Camogmgui|this link]] for GUI description.

====command line====
Example:

* '''/home/root''', file prefix='''test_''', '''1GB''' or '''10min''' files whichever occurs first
** setup and start (in one line):
echo "format=mov;status=/var/tmp/camogm.status;prefix=/home/root/test_;duration=600;length=1073741824;start" > /var/volatile/camogm_cmd
** stop recording:
echo "stop" > /var/volatile/camogm_cmd
sync


==Event Logger (GPS, IMU, IMG & EXT)==
* [[Event_logger|'''More information''']]
===Record===
====web====
* Start:
http://192.168.0.9/logger_launcher.php?cmd=start&file=/mnt/sda1/test.log&index=1&n=10000000
* Stop:
http://192.168.0.9/logger_launcher.php?cmd=stop
* Help:
http://192.168.0.9/logger_launcher.php

====command line====
* start:
root@elphel393:~# cat /dev/imu > /path/filename.log
* stop - CTRL-C or kill the process

===Read===
* http://192.168.0.9/read_imu_log.php (will display help)
** on the first access creates /www/pages/logs/ (http://192.168.0.9/logs/)
** link the recorded logs to /www/pages/logs/
** refresh http://192.168.0.9/read_imu_log.php

==Change parameters==
* http://192.168.0.9/autocampars.php - save/restore/initialize camera/sensor parameters
[[Autocampars 393|'''More information''']]

* http://192.168.0.9/parsedit.php - read/write parameters:
** POST request
Read: http://192.168.0.9/parsedit.php?sensor_port=0&PAR1&PAR2
Change: http://192.168.0.9/parsedit.php?sensor_port=0&PAR1&PAR2 - update values - submit form

** GET request - XML response
Read: http://192.168.0.9/parsedit.php?immediate&sensor_port=0&PAR1&PAR2
Change: http://192.168.0.9/parsedit.php?immediate&sensor_port=0&PAR1=VAL1&PAR2=VAL2

Note 1: if the parameter's value is specified in URL it will be applied. The call can have mixed specified and unspecified parameters.

Note 2: The new value is read on the next call.

Example:
* set 10 fps and enable output trigger signal
http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0&TRIG_OUT=0x66555&TRIG_PERIOD=10000000&TRIG=4

[[Parsedit.php|'''More information''']]

'''Notes:'''
* parsedit.php and autocampars.php were ported from 353 camera series. There are a few changes from the originals related to 4x sensor ports:
** parameters are individual for each sensor port - writing parameters to multiple port at once is controlled with a (bit-)'''mask''' input box
** if opened w/o sensor_port specified the page will show links to available ports
** '''sensor_port=x''', where x=0..3 - in the address string - for a single sensor camera it is normally 0

==Image formats==
====jpeg====
* '''color''': YCbCr 4:2:0, 3x3 pixels
* '''mono6''': monochrome - color YCbCr 4:2:0 with zeroed out color components
* '''mono''' : monochrome - color YCbCr 4:0:0 with omitted color components

'''Note:''' Is not the best for processing since a lot of information is lost at demosaicing
====jp4 raw====
* [[JP4|'''More information''']]

==Temperature monitor==
* http://192.168.0.9/hwmon.html:
** Tshutdown - automatic shutdown temperature level (default is 90°C)
{|
|[[File:10393_hwmon.jpeg|thumb|200px]]
|}

==eSATA port switching==
* requres [[10389]]
* available connections:
** camera <=> internal SSD (default)
** camera <=> external drive (external drive will need a separate power source)
** PC <=> internal SSD
* [[Sata_multiplexer_10389|'''More information''']]

==Proper shutdown==
* if not properly shutdown - μSD might get corrupted (run '''sync''' at least)
shutdown -hP now
Same effect:
http://192.168.0.9/autocampars.php?reboot

==Firmware/software update==
[[Poky_2.0_manual#Write_files_to_media_and_boot|'''More information''']]

==Firmware images==
TBA

==Other info==
====Tools for calibrated systems====
* [[Elphel_Software_Kit_for_Ubuntu#ImageJ_and_Elphel_plugins_for_imageJ|Install ImageJ plugins]]
** decode jp4 raw format
** aberrations correction
** distortion correction (pixel mapping)
** rectification and projection
** '''JP46 Reader camera''' - decode JP4/JP46
** '''Eyesis correction''' - post-process JP4s using calibration data

====switch between ERS and GRR modes in MT9P006====
* [[Electronic_Rolling_Shutter#ERS_and_GRR_in_MT9P001_on_10393|Read article]]
====External/internal trigger and FPS control====
* [[Trigger_393]]
===SSD/MMC/USB formatting===
* [[Format_SSD_MMC]]
===Boot modes===
* [[Boot_options_393|Boot options]]

==Known problems==
* [solved] Vertical artifacts in jpegs. Images are ok at 100% quality. Fixed, testing.
* http://192.168.0.9:232x/noexif/mimg - multipart jpeg displays corrupted frames from time to time. Reason: network bandwidth?
* [solved] Sometimes on power-on (NAND flash boot) cannot mount the card's rootfs partition. Kernel Panics. Power off/on. Soft "reboot -f" works ok.
...
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
...
[[VFS:_Unable_to_mount_root_fs_on_unknown-block(179,2)|More info]]
* Changing exposure/quality/gains - can corrupt images - needs testing.

* After rewriting rootfs to μSD card - some of the cards get a corrupted partition - re-partitioning (reformatting?) solves the problem.
On the camera the rootfs is mounted as RW and some of the files are changed (also links created) -
most of the changes are now moved to tmpfs but something might have been missed.

==Notes==
* In case rootfs is on flash, it might make sense (or maybe not as the history is updated only once on session exit) to disable bash sessions command history - [http://stackoverflow.com/questions/18663078/disable-history-in-linux disable bash history]

[[Category:393]]

Camogmgui

2017-01-11T19:34:29Z

Mikhail: /* Web-based Graphical User Interface for camogm */

==Web-based Graphical User Interface for camogm==

The web interface for ''camogm'' is intended for recording of video or images to internal or external storage just from your browser. Elphel393 series cameras support recording in two modes: normal recording to a file system and fast recording to a raw disk or disk partition without any file system on it. The process of images extraction from raw partition is described on [[Extracting_images_from_raw_partition | this page]].

==Prerequisites==
Disk should be prepared before it can be used in either of the two modes of recording. Normal recording assumes there is at least one partition with a file system. Follow [[HDD_Format | this guide]] from step 1 to step 4 to prepare a partition for normal recording if your disk is not partitioned yet. Fast recording mode requires at least one partition without file system. Follow [[HDD_Format | this guide]] from step 1 to step 3 to prepare such partition. As alternative, the whole disk can be used as a fast recording buffer and no actions with disk required in this case given that the disk in not partitioned.

==Interface==
===Main window===
Open the following link in your browser to start ''camogmgui''
http://192.168.0.9/camogmgui.php
[[File:Camogmgui main.png|center|alt=Main window]]
The main window of the program consists of several areas (marked in red on the image) and two of them, preview (1) and buffers usage (2), are folded by default. The third area displays a list of files recorded in normal mode to some directory on the mounted disk. This list is empty right after start and you need to press ''Reload'' button to refresh the list. ''Create folder'' button makes new subdirectory in the current directory and ''Set Target Folder'' sets selected directory as a location for recorded files. The group of tabs on the right side contains status information and controls for recording. The first tab of the group, ''Status'', shows status of all ports and some recording statistics. Some fields on this tab are empty right after start but they will be updated as soon as recording has started. By default, the update period during recording is one second.

===Preview===
[[File:Camogmgui preview.png|center|alt=Preview panel]]
The ''Live-Preview'' link opens a thumbnail of a captured image and some controls for preview capturing. Preview image can be updated manually each time the ''Update'' button is pressed or automatically within a predefined period of time if ''Auto Update'' check box is checked. The ''Size'' buttons allows you to adjust the image size. Preview is displayed for a single channel selected by ''Port'' radio buttons.

===Buffers usage===
[[File:Camogmgui buffers.png|center|alt=Buffers usage]]
The ''Show Buffers'' link opens several bars indicating the usage of in-camera memory buffers. Each bar corresponds to a single sensor port and shows free space left in buffer and the space occupied by images which have not been recorded yet. The status of these bars is updated along with the content of the ''Status'' tab. Click on any bar to fold these indicators back to link. The ''HELP'' link below bars leads to this page.

===File names tab===
[[File:Camogmgui filenames.png|right|alt=File names tab]]
The ''Filenames'' tab controls file naming scheme for recorded files. There are three schemes available:
* Unix time stamps. The name of a file is created from image time stamp and channel number extracted from Exif. The example of such naming scheme is shown on the screenshot of main window. This is a default scheme.
* Prompt user for file name after recording
* Advanced naming scheme. This scheme assembles file names using several predefined fields.
The settings on this tab are ineffective in fast recording mode.
 

===Format tab===
[[File:Camogmgui format norm.png|right|alt=Normal recording mode]]
[[File:Camogmgui format fast.png|right|alt=Fast recording mode]]
The ''Format'' tab controls recording mode and path for resulting files. The group of radio buttons named ''Format'' selects resulting file format. ''Use fast recording'' check box switches ''camogm'' to fast recording mode and disables ''Format'' and ''Directory'' settings because they are ineffective in this mode. The ''Directory'' text field sets full path to a directory where files are saved. Note, that this is a path in camera system, not on your PC. The ''Devices'' panel shows a list of disks or partitions available for recording. The contents of this panel depends on the mode of operation: in normal recording mode, the list of mountable partitions is shown, and in fast recording mode the list of partitions or disks without file system is presented. The group of controls below devices list allows you to enable or disable ''camogm'' debug output, save this output to a file and adjust its level of verbosity. Do not forget to press ''OK'' button before recording to apply the settings.
 

===Advanced tab===
[[File:Camogmgui advanced.png|right|alt=Advanced tab]]
The ''Advanced'' tab controls how video files are recorded. The settings on this tab allows you to limit the size and duration of single video file. When either limit is reached, ''camogm'' starts recording to a new file. The settings on this tab are ineffective in fast recording mode.
 

==Plans for Future Releases==
* Full Audio Support
* Full Geotagging Support

==Changelog==
[[Image:Camogmgui08.jpg|thumb|camogmgui Version 0.8]]
'''Version 0.8'''

* added support for USB sound devices, underlying camogm2 is still buggy though and therefore disabled
* added support for geotagging, underlying camogm2 is still buggy though and therefore disabled
* mounting of different devices/partitions like external SATA devices is now possible, still needs testing though
* updates free hdd space dynamically while recording
* added buffer graph, still unexpected behaviour
* used different method to set quicktime mov as default format
* bug fixes

No release URL this time as from now on latest source files need to be obtained directly from the CVS tree.

----
'''Version 0.7'''

* updated to work with 8.0 firmware
* advanced naming scheme tab added
* debug output added
* bug fixes

[http://www.oneartplease.com/elphel/camogmgui_0_7.zip camogmgui_0_7.zip]

----
[[Image:Camogmgui_0_6.jpg|thumb|camogmgui Version 0.6]]
'''Version 0.6'''

I think we are getting close to a first major 1.0 release. As always please provide feedback.

* sensor state info added
* added some help text
* quicktime *.mov is now the default format
* the filebrowser can now go into subfolders, also create them or set them as target for recordings
* live video preview image added in expandable tab
* tabs remember their state across page reloads
* bug fixes

[http://community.elphel.com/files/camogmgui/camogmgui_0_6.zip camogmgui_0_6.zip]

----
[[Image:Camogmgui_0_5.jpg|thumb|camogmgui Version 0.5]]
'''Version 0.5'''

* good bye bulky placeholder design -> Hello fancy real visual interface
* camogm is now automatically started from within the script.
* hdd can be mounted with a single click
* filebrowser is is alot fancier now
* frameskip / timelapse problem fixed
* spry applets added for even more responsive and feature rich layout

[http://www.oneartplease.com/elphel/camogmgui_0_5.zip camogmgui_0_5.zip]

----
[[Image:Camogmgui_0_4.jpg|thumb|camogmgui Version 0.4]]
'''Version 0.4'''

Anything hdd mounting related can now be done directly inside the gui. I also added a filebrowser so recorded videos can immediately be downloaded. Advanced settings added. The whole script does not rely on any external resources anymore.

I tried starting camogm from within the script as well, but ran into some problems, stay tuned.

So still: before the script can be used camogm must be started manually via shell:
camogm /var/state/camogm_cmd &

[http://www.oneartplease.com/elphel/camogmgui_0_4.zip camogmgui_0_4.zip]

----

'''Version 0.3'''

Some decent progess here. Lots of ajax scripting done to show filesize, datarate, etc. live while recording video files. Record and stop-record commands are also ajax transmitted which makes the GUI much more responsive. Stability issues seem to be solved now as well.

Again: before the script can be used camogm must be started manually via shell:
camogm /var/state/camogm_cmd &

[http://www.oneartplease.com/elphel/camogmgui_0_3.zip camogmgui_0_3.zip]

----

'''Version 0.2'''

I color labeled the parts of the gui and their current grade of operation. Record Format and destination directory are now read from xml output of camogm to fill in the form. The script now checks if both camogm and compressor are running. If the compressor is not running it can be started directly in the GUI. Camogm can not be started in the GUI yet (crashes...).

Before the script can be used camogm must be started manually via shell:
camogm /var/state/camogm_cmd &

[http://www.oneartplease.com/elphel/camogmgui_0_2.zip camogmgui_0_2.zip]

----

'''Version 0.1'''

Very basic functionality as of now, format/codec can be selected, target directory can be set, record start/stop, audio recording form is already in the file but not functional yet

(Wiki hosted download link will follow as soon as the wiki permits me to upload anything else than images)

[http://www.oneartplease.com/files/camogmgui.tar.gz camogmgui.tar.gz]

==Software Interface==

The GUI strongly relies on AJAX requests to update contents on the fly. These AJAX commands can be (re)used from external programs as well.

Access:

http://*camera-ip*/camogmgui/camogm_interface.php

The following commands are available:

'''start camogm as background deamon:'''
camogm_interface.php?cmd=run_camogm
does nothing if camogm is already running

'''show camogm xml status:'''
camogm_interface.php?cmd=status

returns something like this:
<camogm_state>
<state>"stopped"</state>
<compressor_state>"running"</compressor_state>
<file_name>""</file_name>
<frame_number>0</frame_number>
<file_duration>0.000000</file_duration>
<file_length>0</file_length>
<frame_period>0</frame_period>
<frames_skip>0</frames_skip>
<seconds_skip>0</seconds_skip>
<frames_skip_left>0</frames_skip_left>
<seconds_skip_left>0</seconds_skip_left>
<frame_width>0</frame_width>
<frame_height>0</frame_height>
<format>"mov"</format>
<exif>"yes"</exif>
<prefix>"/var/hdd/"</prefix>
<max_duration>60</max_duration>
<max_length>100000000</max_length>
<max_frames>16384</max_frames>
<timescale>1.000000</timescale>
<frames_per_chunk>10</frames_per_chunk>
<buffer_overruns>-1</buffer_overruns>
<buffer_minimal>12704544</buffer_minimal>
<buffer_free>1332800</buffer_free>
<buffer_used>18459072</buffer_used>
<circbuf_rp>-1</circbuf_rp>
<debug_output>"stderr"</debug_output>
<debug_level>1</debug_level>
<use_global_rp>"no"</use_global_rp>
<kml_enable>"no"</kml_enable>
<kml_used>"no"</kml_used>
<kml_path>""</kml_path>
<kml_horHalfFov>"20.000000"</kml_horHalfFov>
<kml_vertHalfFov>"15.000000"</kml_vertHalfFov>
<kml_near>"40.000000"</kml_near>
<kml_height_mode>"map ground level"</kml_height_mode>
<kml_height>"10.000000"</kml_height>
<kml_period>2</kml_period>
<kml_last_ts>0.000000</kml_last_ts>
</camogm_state>

'''start recording:'''
camogm_interface.php?cmd=start

'''stop recording:'''
camogm_interface.php?cmd=stop

'''rename file:'''
camogm_interface.php?cmd=file_rename&file_old=ABC&file_new=XYZ

returns errors if the file names are the same or if the target file name already exists.

'''mount partition:'''

mount the default partition /dev/hda1 at /var/hdd. Also create the required directory:
camogm_interface.php?cmd=mount

You can also supply 2 more arguments specifying custom partition and mountpoint:

For example:
camogm_interface.php?cmd=mount&partition=/dev/hdb1&mountpoint=/var/externalhdd

'''unmount partition:'''

To unmount a previously mounted partition you need to supply the mountpoint:

For example:
camogm_interface.php?cmd=umount&mountpoint=/var/externalhdd

'''list devices:'''
Shows xml information about connected media no matter if they are mounted or not:

camogm_interface.php?cmd=listdevices

with only the internal HDD this returns:
<camogm_interface>
<command>listdevices</command>
<listdevices>
<item>
<partition>/dev/hda1</partition>
<size>37.25 GB</size>
<mountpoint>/var/hdd</mountpoint>
<filesystem>ext2</filesystem>
</item>
</listdevices>
</camogm_interface>

'''create directory:'''
creates a new directory

Example creating a new directory called "newdir" in the /subdir/ which has to exist already:
camogm_interface.php?cmd=mkdir&name=/subdir/newdir

'''Get remaining free HDD Space:'''
camogm_interface.php?cmd=get_hdd_space

'''is HDD mounted:'''
camogm_interface.php?cmd=get_hdd_space
returns either the mountpoint or "no HDD mounted"

'''create HDD symlink:'''
camogm_interface.php?cmd=create_symlink
makes the HDD available over http by placing a symlink in the correct directory.

'''List files:'''
camogm_interface.php?cmd=list_files&dir=/
returns an xml tree of the available files at a specified path with details like size and creation date:
<file>
<type>mov</type>
<name>1226615834_588046.mov</name>
<path>1226615834_588046.mov</path>
<size>2545355</size>
<date>13 Nov 2008 22:37:15</date>
</file>

'''set camogm record directory:'''
camogm_interface.php?cmd=set_prefix&prefix=XYZ
Tell camogm to record to this specified path. Also creates/sets a cookie called "directory" with the same value.

'''init the camera compressor:'''
camogm_interface.php?cmd=init_compressor

'''check USB audio hardware:'''
camogm_interface.php?cmd=check_audio_hardware
Returns connected (hotplugable) USB audio devices.

'''Play sound over USB audio device:'''
camogm_interface.php?cmd=test_audio_playback&soundfile=XYZ
Tests audio hardware by playing back a specific soundfile.

'''set quicktime as recording format:'''
camogm_interface.php?cmd=setmov
Tells camogm to use quicktime mov as format.

Extracting images from raw partition

2017-01-11T19:30:31Z

Mikhail: Created page with "As it was mentioned in camogmgui, ''camogm'' can save images to a raw partition or disk in fast recording mode and you need to do one additional step to extract t..."

As it was mentioned in [[Camogmgui | camogmgui]], ''camogm'' can save images to a raw partition or disk in fast recording mode and you need to do one additional step to extract these images from such a partition. This short note describes how to get images from raw partition.

1. Download [[https://github.com/Elphel/elphel-tools-x393 these scripts]] to your PC.

2. Connect camera to eSATA port, power it on and wait until it has loaded.

3. Copy ssh key to camera. This step can be skipped if it was done before.
$ ssh-copy-id root@192.168.0.9

4. Run ''int_ssd_download.py'' script to dump camera's raw partition to PC.
$ ./int_ssd_download.py -c root@192.168.0.9 -n 1 -bs 100 -bc 1 .
root@192.168.0.9: connection ok
root@192.168.0.9: raw partition name: Crucial_CT250MX200SSD6_1531103B6ABA-part2
umounting /dev/sda1
root@192.168.0.9: Enabled connection: internal SSD <-> PC
Connect camera (eSATA) to PC (eSATA/SATA). Press Enter to continue...
[sudo] password for mk:
Getting raw partition data from /dev/sdb2
1+0 records in
1+0 records out
104857600 bytes (105 MB, 100 MiB) copied, 0.501566 s, 209 MB/s
Waiting for disks to show up:
[]
root@192.168.0.9: Enabled connection: internal SSD <-> Camera
Done
Here, the ''-c'' parameter specifies which camera to use and script controls this camera to switch internal disk to eSATA and find raw partition. The ''-n'', ''-bs'' and ''-bc'' parameters specify the number of chunks to download, block size in MB and the number of blocks in each chunk respectively. The script will create a subdirectory, which name is made of disk manufacturer, model and partition number, and download disk dump into this subdirectory.
$ ls -l
total 84
drwxrwxr-x 2 mk mk 4096 Jan 11 10:53 Crucial_CT250MX200SSD6_1531103B6ABA-part2
-rw-rw-r-- 1 mk mk 4308 Jan 9 18:38 extract_images.php
-rwxrwxr-x 1 mk mk 3177 Jan 9 18:38 ext_ssd_download.py
-rwxrwxr-x 1 mk mk 4726 Jan 10 17:12 int_ssd_download.py
-rw-rw-r-- 1 mk mk 35141 Jan 9 18:38 LICENSE
-rw-rw-r-- 1 mk mk 620 Jan 9 18:38 README.md
-rw-rw-r-- 1 mk mk 6110 Jan 9 18:38 x393.py
-rw-rw-r-- 1 mk mk 10016 Jan 9 18:39 x393.pyc

5. Use ''extract_images.php'' sctipt to extract images from disk dump.
$ ./extract_images.php Crucial_CT250MX200SSD6_1531103B6ABA-part2
<pre>
Splitting Crucial_CT250MX200SSD6_1531103B6ABA-part2/file_0.img into jp4s
All images will be placed to ''result'' subdirectory.
$ ls -l Crucial_CT250MX200SSD6_1531103B6ABA-part2/
total 102404
-rw-r--r-- 1 root root 104857600 Jan 11 10:53 file_0.img
drwxrwxr-x 2 mk mk 4096 Jan 11 12:22 result

10393 manual

2017-01-06T20:44:08Z

Mikhail: /* browser */

==Important Notes==
* As of 2016/12/15, the software ported from 10353 supports only 5MPix sensors, for 14MPix, please see:
**[http://wiki.elphel.com/index.php?title=Tmp_manual&oldid=14676 older version of this manual with links to older software images]

==In the package==
* 10393 camera system
{|
|[[File:NC393-CS marked ports.jpeg|thumb|200px|Fig.1 10393 interfaces]]
|}
* Power supply wall adapter (default: 18-75V, [[10393_power|more information]])
* CAT6 network cable
* μUSB-to-USB cable
* Recovery μSD card
* If the camera is calibrated the calibration data will be on a separate storage media or on the internal SSD (likely /mnt/sda1)

==Interfaces==
See Fig.1:
{| class="wikitable"
|-
! GigE
| gigabit network
|-
! μSD
| micro SD card slot - boot or storage
|-
! console
| serial console port, use μUSB-to-USB cable
|-
! eSATA+USB
| 2-in-1. Connect USB or eSATA device. USB2.0 host
|-
! μUSB
| USB2.0 host
|-
! sync
| sync multiple cameras or other devices - input/output trigger signal through a 4-conductor 2.5mm audio plug with cable (example: [http://www.digikey.com/products/en?keywords=839-1029-ND digikey])
|}

==Power on==
* Plug in the power supply
* Connect to LAN using the network cable

====Notes====
* Boot time: ~30s
* The default boot is from the on-board NAND flash. [[Boot_options_393|More information]] on available boot options and recovery boot.

==Defaults==
{| class="wikitable"
|-
! IP Address
| 192.168.0.9
|-
! User
| root
|-
! Password
| pass
|}

* The default IP address is set in the ''/etc/elphel393/init_elphel393.py''.
* If present the internal SSD will be formatted into 2 partitions:
** /dev/sda1 - ext4 (~64-100GB)
** /dev/sda2 - raw partition (no file system) for fast recording

==Command line access==
* ssh from PC terminal:
$ ssh root@192.168.0.9

==Serial console access==
* Use a ''microUSB-USB cable'' to connect '''console μUSB port''' (see Fig.1) to PC - the cable's end should be thin enough otherwise interferes with an inserted mmc ('''m'''ulti '''m'''edia '''c'''ard = μSD card).

* In Linux the '''minicom''' program can be used
$ minicom -c on
Most likely the device will be /dev/ttyUSB0. Settings:
* 115200 8N1, no for hardware/software flow control
Refer to the following article for more details on using '''minicom''': [http://wiki.elphel.com/index.php?title=Using_minicom_to_connect_to_Elphel393_camera Using minicom to connect to Elphel393 camera]

==Web user interface (camvc)==
http://192.168.0.9/closeme.html (type in the browser address bar - will be changed soon):
* The page contains links to camvc user interface for each individual camera port.
* camvc was ported from the 10353 camera series:
** change parameters like image format, resolution, auto exposure, auto white balance and more. Alternative way to change parameters is described [[Tmp_manual#Change_parameters|below]].
** pause compressor and search within buffered images
** help tips available - see Fig.2 - select then mouse over a control element of interest
{|
| valign='top'|[[image:Help tips.jpeg|250px|thumb|Fig.2 enable camvc help tips]]
|[[File:Controls with blank.jpeg|300px|thumb|Fig.3 camvc controls]]
|}

==Download live images==
====camvc====
* For a currently opened port (displayed in the window title and as "...sensor_port=0..." in the URL):
{|
|[[image:Camvc image capture.jpeg|250px|thumb|Fig.4 Acquire an image from the Camera Control Interface]]
|}

====browser====
port 0: http://192.168.0.9:2323/img
port 1: http://192.168.0.9:2324/img
port 2: http://192.168.0.9:2325/img
port 3: http://192.168.0.9:2326/img

====command line====
wget http://192.168.0.9:2323/img -O filename.jpeg
wget http://192.168.0.9:2324/img -O filename.jpeg
wget http://192.168.0.9:2325/img -O filename.jpeg
wget http://192.168.0.9:2326/img -O filename.jpeg

==Video==
===Display===
====Multipart JPEG stream====
http://192.168.0.9:2323/mimg
http://192.168.0.9:2324/mimg
http://192.168.0.9:2325/mimg
http://192.168.0.9:2326/mimg

====GStreamer====

gst-launch-1.0 souphttpsrc is-live=true location=http://192.168.0.9:2323/mimg ! jpegdec ! xvimagesink

* Only mjpeg, no rtsp yet.
* More examples at [[Using_gstreamer#Display|Using GStreamer]]

===Record===
* Recording is done by the '''camogm''' program
* If recording to internal or external SSD, please, read about [[Tmp_manual#eSATA_port_switching|eSATA port switching]]
* important: Event logger (GPS, IMU, IMG, EXT) recording is started/stopped separately. See [[Tmp_manual#Record_the_Event_Logger_data_.28GPS.2CIMU.2CIMG_.26_EXT.29|instructions]] below.
* For SATA devices camogm supports:
** recording to a partition with a file system - up to 80MB/s
** (default) faster recording to a partition without a file system (raw partition) avoiding OS calls - up to 220MB/s
* To extract data from a raw partition use '''dd''' or [https://github.com/Elphel/elphel-tools-x393 these scripts] to get the data and split it into images.
* Can record to an mmc partiton or usb.
* [[Using_camogm_with_Elphel393_camera|More info]]
* If the ''prefix'' parameter, which is ''absolute path + prefix'', for a channel is not set the file will be written somewhere to rootfs.
** if prefix is empty then the ''absolute path'' must end with a slash.

====browser====
Example 1: (provide a correct media mount point - /mnt/sda1/)

* http://192.168.0.9/camogmgui.php

Follow [[Camogmgui|this link]] for GUI description.

====command line====
Example:

* '''/home/root''', file prefix='''test_''', '''1GB''' or '''10min''' files whichever occurs first
** setup and start (in one line):
echo "format=mov;status=/var/tmp/camogm.status;prefix=/home/root/test_;duration=600;length=1073741824;start" > /var/volatile/camogm_cmd
** stop recording:
echo "stop" > /var/volatile/camogm_cmd
sync


==Event Logger (GPS, IMU, IMG & EXT)==
* [[Event_logger|'''More information''']]
===Record===
====web====
* Start:
http://192.168.0.9/logger_launcher.php?cmd=start&file=/mnt/sda1/test.log&index=1&n=10000000
* Stop:
http://192.168.0.9/logger_launcher.php?cmd=stop
* Help:
http://192.168.0.9/logger_launcher.php

====command line====
* start:
root@elphel393:~# cat /dev/imu > /path/filename.log
* stop - CTRL-C or kill the process

===Read===
* http://192.168.0.9/read_imu_log.php (will display help)
** on the first access creates /www/pages/logs/ (http://192.168.0.9/logs/)
** link the recorded logs to /www/pages/logs/
** refresh http://192.168.0.9/read_imu_log.php

==Change parameters==
* http://192.168.0.9/autocampars.php - save/restore/initialize camera/sensor parameters
[[Autocampars 393|'''More information''']]

* http://192.168.0.9/parsedit.php - read/write parameters:
** POST request
Read: http://192.168.0.9/parsedit.php?sensor_port=0&PAR1&PAR2
Change: http://192.168.0.9/parsedit.php?sensor_port=0&PAR1&PAR2 - update values - submit form

** GET request - XML response
Read: http://192.168.0.9/parsedit.php?immediate&sensor_port=0&PAR1&PAR2
Change: http://192.168.0.9/parsedit.php?immediate&sensor_port=0&PAR1=VAL1&PAR2=VAL2

Note 1: if the parameter's value is specified in URL it will be applied. The call can have mixed specified and unspecified parameters.

Note 2: The new value is read on the next call.

Example:
* set 10 fps and enable output trigger signal
http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0&TRIG_OUT=0x66555&TRIG_PERIOD=10000000&TRIG=4

[[Parsedit.php|'''More information''']]

'''Notes:'''
* parsedit.php and autocampars.php were ported from 353 camera series. There are a few changes from the originals related to 4x sensor ports:
** parameters are individual for each sensor port - writing parameters to multiple port at once is controlled with a (bit-)'''mask''' input box
** if opened w/o sensor_port specified the page will show links to available ports
** '''sensor_port=x''', where x=0..3 - in the address string - for a single sensor camera it is normally 0

==Image formats==
====jpeg====
* '''color''': YCbCr 4:2:0, 3x3 pixels
* '''mono6''': monochrome - color YCbCr 4:2:0 with zeroed out color components
* '''mono''' : monochrome - color YCbCr 4:0:0 with omitted color components

'''Note:''' Is not the best for processing since a lot of information is lost at demosaicing
====jp4 raw====
* [[JP4|'''More information''']]

==Temperature monitor==
* http://192.168.0.9/hwmon.html:
** Tshutdown - automatic shutdown temperature level (default is 90°C)
{|
|[[File:10393_hwmon.jpeg|thumb|200px]]
|}

==eSATA port switching==
* requres [[10389]]
* available connections:
** camera <=> internal SSD (default)
** camera <=> external drive (external drive will need a separate power source)
** PC <=> internal SSD
* [[Sata_multiplexer_10389|'''More information''']]

==Proper shutdown==
* if not properly shutdown - μSD might get corrupted (run '''sync''' at least)
shutdown -hP now
Same effect:
http://192.168.0.9/autocampars.php?reboot

==Firmware/software update==
[[Poky_2.0_manual#Write_files_to_media_and_boot|'''More information''']]

==Firmware images==
TBA

==Other info==
====Tools for calibrated systems====
* [[Elphel_Software_Kit_for_Ubuntu#ImageJ_and_Elphel_plugins_for_imageJ|Install ImageJ plugins]]
** decode jp4 raw format
** aberrations correction
** distortion correction (pixel mapping)
** rectification and projection
** '''JP46 Reader camera''' - decode JP4/JP46
** '''Eyesis correction''' - post-process JP4s using calibration data

====switch between ERS and GRR modes in MT9P006====
* [[Electronic_Rolling_Shutter#ERS_and_GRR_in_MT9P001_on_10393|Read article]]
====External/internal trigger and FPS control====
* [[Trigger_393]]
===SSD/MMC/USB formatting===
* [[Format_SSD_MMC]]
===Boot modes===
* [[Boot_options_393|Boot options]]

==Known problems==
* [solved] Vertical artifacts in jpegs. Images are ok at 100% quality. Fixed, testing.
* http://192.168.0.9:232x/noexif/mimg - multipart jpeg displays corrupted frames from time to time. Reason: network bandwidth?
* [solved] Sometimes on power-on (NAND flash boot) cannot mount the card's rootfs partition. Kernel Panics. Power off/on. Soft "reboot -f" works ok.
...
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
...
[[VFS:_Unable_to_mount_root_fs_on_unknown-block(179,2)|More info]]
* Changing exposure/quality/gains - can corrupt images - needs testing.

* After rewriting rootfs to μSD card - some of the cards get a corrupted partition - re-partitioning (reformatting?) solves the problem.
On the camera the rootfs is mounted as RW and some of the files are changed (also links created) -
most of the changes are now moved to tmpfs but something might have been missed.

==Notes==
* In case rootfs is on flash, it might make sense (or maybe not as the history is updated only once on session exit) to disable bash sessions command history - [http://stackoverflow.com/questions/18663078/disable-history-in-linux disable bash history]

[[Category:393]]

Camogmgui

2017-01-06T20:40:09Z

Mikhail:

==Web-based Graphical User Interface for camogm==

The web interface for ''camogm'' is intended for recording of video or images to internal or external storage just from your browser. Elphel393 series cameras support recording in two modes: normal recording to a file system and fast recording to a raw disk or disk partition without any file system on it.

==Prerequisites==
Disk should be prepared before it can be used in either of the two modes of recording. Normal recording assumes there is at least one partition with a file system. Follow [[HDD_Format | this guide]] from step 1 to step 4 to prepare a partition for normal recording if your disk is not partitioned yet. Fast recording mode requires at least one partition without file system. Follow [[HDD_Format | this guide]] from step 1 to step 3 to prepare such partition. As alternative, the whole disk can be used as a fast recording buffer and no actions with disk required in this case given that the disk in not partitioned.

==Interface==
===Main window===
Open the following link in your browser to start ''camogmgui''
http://192.168.0.9/camogmgui.php
[[File:Camogmgui main.png|center|alt=Main window]]
The main window of the program consists of several areas (marked in red on the image) and two of them, preview (1) and buffers usage (2), are folded by default. The third area displays a list of files recorded in normal mode to some directory on the mounted disk. This list is empty right after start and you need to press ''Reload'' button to refresh the list. ''Create folder'' button makes new subdirectory in the current directory and ''Set Target Folder'' sets selected directory as a location for recorded files. The group of tabs on the right side contains status information and controls for recording. The first tab of the group, ''Status'', shows status of all ports and some recording statistics. Some fields on this tab are empty right after start but they will be updated as soon as recording has started. By default, the update period during recording is one second.

===Preview===
[[File:Camogmgui preview.png|center|alt=Preview panel]]
The ''Live-Preview'' link opens a thumbnail of a captured image and some controls for preview capturing. Preview image can be updated manually each time the ''Update'' button is pressed or automatically within a predefined period of time if ''Auto Update'' check box is checked. The ''Size'' buttons allows you to adjust the image size. Preview is displayed for a single channel selected by ''Port'' radio buttons.

===Buffers usage===
[[File:Camogmgui buffers.png|center|alt=Buffers usage]]
The ''Show Buffers'' link opens several bars indicating the usage of in-camera memory buffers. Each bar corresponds to a single sensor port and shows free space left in buffer and the space occupied by images which have not been recorded yet. The status of these bars is updated along with the content of the ''Status'' tab. Click on any bar to fold these indicators back to link. The ''HELP'' link below bars leads to this page.

===File names tab===
[[File:Camogmgui filenames.png|right|alt=File names tab]]
The ''Filenames'' tab controls file naming scheme for recorded files. There are three schemes available:
* Unix time stamps. The name of a file is created from image time stamp and channel number extracted from Exif. The example of such naming scheme is shown on the screenshot of main window. This is a default scheme.
* Prompt user for file name after recording
* Advanced naming scheme. This scheme assembles file names using several predefined fields.
The settings on this tab are ineffective in fast recording mode.
 

===Format tab===
[[File:Camogmgui format norm.png|right|alt=Normal recording mode]]
[[File:Camogmgui format fast.png|right|alt=Fast recording mode]]
The ''Format'' tab controls recording mode and path for resulting files. The group of radio buttons named ''Format'' selects resulting file format. ''Use fast recording'' check box switches ''camogm'' to fast recording mode and disables ''Format'' and ''Directory'' settings because they are ineffective in this mode. The ''Directory'' text field sets full path to a directory where files are saved. Note, that this is a path in camera system, not on your PC. The ''Devices'' panel shows a list of disks or partitions available for recording. The contents of this panel depends on the mode of operation: in normal recording mode, the list of mountable partitions is shown, and in fast recording mode the list of partitions or disks without file system is presented. The group of controls below devices list allows you to enable or disable ''camogm'' debug output, save this output to a file and adjust its level of verbosity. Do not forget to press ''OK'' button before recording to apply the settings.
 

===Advanced tab===
[[File:Camogmgui advanced.png|right|alt=Advanced tab]]
The ''Advanced'' tab controls how video files are recorded. The settings on this tab allows you to limit the size and duration of single video file. When either limit is reached, ''camogm'' starts recording to a new file. The settings on this tab are ineffective in fast recording mode.
 

==Plans for Future Releases==
* Full Audio Support
* Full Geotagging Support

==Changelog==
[[Image:Camogmgui08.jpg|thumb|camogmgui Version 0.8]]
'''Version 0.8'''

* added support for USB sound devices, underlying camogm2 is still buggy though and therefore disabled
* added support for geotagging, underlying camogm2 is still buggy though and therefore disabled
* mounting of different devices/partitions like external SATA devices is now possible, still needs testing though
* updates free hdd space dynamically while recording
* added buffer graph, still unexpected behaviour
* used different method to set quicktime mov as default format
* bug fixes

No release URL this time as from now on latest source files need to be obtained directly from the CVS tree.

----
'''Version 0.7'''

* updated to work with 8.0 firmware
* advanced naming scheme tab added
* debug output added
* bug fixes

[http://www.oneartplease.com/elphel/camogmgui_0_7.zip camogmgui_0_7.zip]

----
[[Image:Camogmgui_0_6.jpg|thumb|camogmgui Version 0.6]]
'''Version 0.6'''

I think we are getting close to a first major 1.0 release. As always please provide feedback.

* sensor state info added
* added some help text
* quicktime *.mov is now the default format
* the filebrowser can now go into subfolders, also create them or set them as target for recordings
* live video preview image added in expandable tab
* tabs remember their state across page reloads
* bug fixes

[http://community.elphel.com/files/camogmgui/camogmgui_0_6.zip camogmgui_0_6.zip]

----
[[Image:Camogmgui_0_5.jpg|thumb|camogmgui Version 0.5]]
'''Version 0.5'''

* good bye bulky placeholder design -> Hello fancy real visual interface
* camogm is now automatically started from within the script.
* hdd can be mounted with a single click
* filebrowser is is alot fancier now
* frameskip / timelapse problem fixed
* spry applets added for even more responsive and feature rich layout

[http://www.oneartplease.com/elphel/camogmgui_0_5.zip camogmgui_0_5.zip]

----
[[Image:Camogmgui_0_4.jpg|thumb|camogmgui Version 0.4]]
'''Version 0.4'''

Anything hdd mounting related can now be done directly inside the gui. I also added a filebrowser so recorded videos can immediately be downloaded. Advanced settings added. The whole script does not rely on any external resources anymore.

I tried starting camogm from within the script as well, but ran into some problems, stay tuned.

So still: before the script can be used camogm must be started manually via shell:
camogm /var/state/camogm_cmd &

[http://www.oneartplease.com/elphel/camogmgui_0_4.zip camogmgui_0_4.zip]

----

'''Version 0.3'''

Some decent progess here. Lots of ajax scripting done to show filesize, datarate, etc. live while recording video files. Record and stop-record commands are also ajax transmitted which makes the GUI much more responsive. Stability issues seem to be solved now as well.

Again: before the script can be used camogm must be started manually via shell:
camogm /var/state/camogm_cmd &

[http://www.oneartplease.com/elphel/camogmgui_0_3.zip camogmgui_0_3.zip]

----

'''Version 0.2'''

I color labeled the parts of the gui and their current grade of operation. Record Format and destination directory are now read from xml output of camogm to fill in the form. The script now checks if both camogm and compressor are running. If the compressor is not running it can be started directly in the GUI. Camogm can not be started in the GUI yet (crashes...).

Before the script can be used camogm must be started manually via shell:
camogm /var/state/camogm_cmd &

[http://www.oneartplease.com/elphel/camogmgui_0_2.zip camogmgui_0_2.zip]

----

'''Version 0.1'''

Very basic functionality as of now, format/codec can be selected, target directory can be set, record start/stop, audio recording form is already in the file but not functional yet

(Wiki hosted download link will follow as soon as the wiki permits me to upload anything else than images)

[http://www.oneartplease.com/files/camogmgui.tar.gz camogmgui.tar.gz]

==Software Interface==

The GUI strongly relies on AJAX requests to update contents on the fly. These AJAX commands can be (re)used from external programs as well.

Access:

http://*camera-ip*/camogmgui/camogm_interface.php

The following commands are available:

'''start camogm as background deamon:'''
camogm_interface.php?cmd=run_camogm
does nothing if camogm is already running

'''show camogm xml status:'''
camogm_interface.php?cmd=status

returns something like this:
<camogm_state>
<state>"stopped"</state>
<compressor_state>"running"</compressor_state>
<file_name>""</file_name>
<frame_number>0</frame_number>
<file_duration>0.000000</file_duration>
<file_length>0</file_length>
<frame_period>0</frame_period>
<frames_skip>0</frames_skip>
<seconds_skip>0</seconds_skip>
<frames_skip_left>0</frames_skip_left>
<seconds_skip_left>0</seconds_skip_left>
<frame_width>0</frame_width>
<frame_height>0</frame_height>
<format>"mov"</format>
<exif>"yes"</exif>
<prefix>"/var/hdd/"</prefix>
<max_duration>60</max_duration>
<max_length>100000000</max_length>
<max_frames>16384</max_frames>
<timescale>1.000000</timescale>
<frames_per_chunk>10</frames_per_chunk>
<buffer_overruns>-1</buffer_overruns>
<buffer_minimal>12704544</buffer_minimal>
<buffer_free>1332800</buffer_free>
<buffer_used>18459072</buffer_used>
<circbuf_rp>-1</circbuf_rp>
<debug_output>"stderr"</debug_output>
<debug_level>1</debug_level>
<use_global_rp>"no"</use_global_rp>
<kml_enable>"no"</kml_enable>
<kml_used>"no"</kml_used>
<kml_path>""</kml_path>
<kml_horHalfFov>"20.000000"</kml_horHalfFov>
<kml_vertHalfFov>"15.000000"</kml_vertHalfFov>
<kml_near>"40.000000"</kml_near>
<kml_height_mode>"map ground level"</kml_height_mode>
<kml_height>"10.000000"</kml_height>
<kml_period>2</kml_period>
<kml_last_ts>0.000000</kml_last_ts>
</camogm_state>

'''start recording:'''
camogm_interface.php?cmd=start

'''stop recording:'''
camogm_interface.php?cmd=stop

'''rename file:'''
camogm_interface.php?cmd=file_rename&file_old=ABC&file_new=XYZ

returns errors if the file names are the same or if the target file name already exists.

'''mount partition:'''

mount the default partition /dev/hda1 at /var/hdd. Also create the required directory:
camogm_interface.php?cmd=mount

You can also supply 2 more arguments specifying custom partition and mountpoint:

For example:
camogm_interface.php?cmd=mount&partition=/dev/hdb1&mountpoint=/var/externalhdd

'''unmount partition:'''

To unmount a previously mounted partition you need to supply the mountpoint:

For example:
camogm_interface.php?cmd=umount&mountpoint=/var/externalhdd

'''list devices:'''
Shows xml information about connected media no matter if they are mounted or not:

camogm_interface.php?cmd=listdevices

with only the internal HDD this returns:
<camogm_interface>
<command>listdevices</command>
<listdevices>
<item>
<partition>/dev/hda1</partition>
<size>37.25 GB</size>
<mountpoint>/var/hdd</mountpoint>
<filesystem>ext2</filesystem>
</item>
</listdevices>
</camogm_interface>

'''create directory:'''
creates a new directory

Example creating a new directory called "newdir" in the /subdir/ which has to exist already:
camogm_interface.php?cmd=mkdir&name=/subdir/newdir

'''Get remaining free HDD Space:'''
camogm_interface.php?cmd=get_hdd_space

'''is HDD mounted:'''
camogm_interface.php?cmd=get_hdd_space
returns either the mountpoint or "no HDD mounted"

'''create HDD symlink:'''
camogm_interface.php?cmd=create_symlink
makes the HDD available over http by placing a symlink in the correct directory.

'''List files:'''
camogm_interface.php?cmd=list_files&dir=/
returns an xml tree of the available files at a specified path with details like size and creation date:
<file>
<type>mov</type>
<name>1226615834_588046.mov</name>
<path>1226615834_588046.mov</path>
<size>2545355</size>
<date>13 Nov 2008 22:37:15</date>
</file>

'''set camogm record directory:'''
camogm_interface.php?cmd=set_prefix&prefix=XYZ
Tell camogm to record to this specified path. Also creates/sets a cookie called "directory" with the same value.

'''init the camera compressor:'''
camogm_interface.php?cmd=init_compressor

'''check USB audio hardware:'''
camogm_interface.php?cmd=check_audio_hardware
Returns connected (hotplugable) USB audio devices.

'''Play sound over USB audio device:'''
camogm_interface.php?cmd=test_audio_playback&soundfile=XYZ
Tests audio hardware by playing back a specific soundfile.

'''set quicktime as recording format:'''
camogm_interface.php?cmd=setmov
Tells camogm to use quicktime mov as format.

File:Camogmgui advanced.png

2017-01-06T20:11:53Z

Mikhail:

File:Camogmgui format fast.png

2017-01-06T19:08:36Z

Mikhail:

File:Camogmgui format norm.png

2017-01-06T19:07:31Z

Mikhail:

File:Camogmgui filenames.png

2017-01-06T18:48:20Z

Mikhail:

File:Camogmgui buffers.png

2017-01-06T18:26:00Z

Mikhail:

File:Camogmgui preview.png

2017-01-06T18:07:40Z

Mikhail:

Using camogm with Elphel393 camera

2017-01-06T17:40:25Z

Mikhail:

===Introduction===
Elphel 393 series cameras can be equipped with m.2 SSD drive used for images and video recording. The camera equipped with a drive should be configured in a way that the drive can be accessible from Linux operating system. This is normally done with a configuration script which is executed during system boot. The script is located in the /etc/elphel393 directory and called ''init_elphel393.py''. There is a set of parameters which this script receives from init script /etc/ini.d/init_elphel393 and one of them is responsible for SATA controller configuration and driver loading:

\"sata\" :1,

Make sure this parameter is set to 1 if your camera is equipped with SSD drive. You should see the following messages in system log after successful initialization and auto-mounting:

[ 30.587212] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 30.594510] ata1.00: ATA-9: SanDisk SD8SMAT128G1122, Z2320000, max UDMA/133
[ 30.601426] ata1.00: 250069680 sectors, multi 1: LBA48 NCQ (depth 0/32)
[ 30.616091] ata1.00: configured for UDMA/133
[ 30.620669] scsi 0:0:0:0: Direct-Access ATA SanDisk SD8SMAT1 0000 PQ: 0 ANSI: 5
[ 30.629879] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 30.630011] sd 0:0:0:0: [sda] 250069680 512-byte logical blocks: (128 GB/119 GiB)
[ 30.630987] sd 0:0:0:0: [sda] Write Protect is off
[ 30.631106] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 30.637003] sda: sda1 sda2
[ 30.646115] sd 0:0:0:0: [sda] Attached SCSI disk

The disk model and the number of partitions (sda1 and sda2) in the example above correspond to a test platform and they may not be the same in your camera. <code>/dev/sda2</code> in this example is not partitioned and not mounted:

~# mount
/dev/root on / type ext4 (rw,relatime,data=ordered)
devtmpfs on /dev type devtmpfs (rw,relatime,size=449540k,nr_inodes=112385,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /var/volatile type tmpfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
/dev/mmcblk0p1 on /mnt/mmc type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sda1 on /mnt/sda1 type ext2 (rw,relatime,errors=continue)

The program for video/images recording is called ''camogm''. Its full description for previous series of Elphel cameras is available on [[Camogm]] wiki page. Current version of the program supports four sensor channels and has the same command set as the previous version. The program can be started the same way as described in [[Camogm#Starting_camogm|Starting camogm]] section and it will create command pipe called ''camogm_cmd'' in the following directory:

root@elphel393:~# ls -l /var/volatile/state/
-rw-r--r-- 1 root root 176 Dec 21 18:56 camera
prwxrwxrwx 1 root root 0 Dec 21 19:28 camogm.state
prwxr-xr-x 1 root root 0 Dec 21 19:28 camogm_cmd

The status information output can be redirected to a file as described in [[Camogm#Sending_Commands_to_camogm|Sending commands to camogm]].

Note, that ''camogm'' is under development and not all features of the previous version have been ported to new camera. As for now, geo tagging and exif specific commands are not implemented. Watch for updates on our [https://github.com/Elphel github page].

You can start ''camogm'' as a standalone command-line application or use web GUI interface in a browser to control the program. The examples of using ''camogm'' in both ways are shown below.
===Example===
====1. WebGUI====
* http://192.168.0.9/camogmgui.php
* In the '''Format''' tab check the settings then press OK button
{|
| valign='top'|[[File:Camogmgui format tab.png|thumb|400px|Fig.1 Camogmgui - change recording formats]]
| valign='top'|[[File:Camogmgui recording 1.png|thumb|400px|Fig.2 Camogmgui - recording status]]
|}
=====Fast recording=====
''camogm'' can write data to disk or partition in a special fast recording mode. This mode supports higher sequential write speeds than those that can be achieved during regular file recording to a file system but additional step to extract data from disk is needed. Use [https://github.com/Elphel/elphel-tools-x393 these scripts] to extract raw data from disk and split it into separate images.
* Keep '''Use fast recording''' checkbox selected - press OK then RECORD
** An image sequence will be written to a raw partition.
** The '''Format:''' options will be disabled as well as '''Directory'''

=====Normal recording=====
In this mode ''camogm'' saves data to regular files on a file system.
* Deselect '''Use fast recording'''
* Choose '''Format''' (Ogg Media Stream is not tested)
* Type '''Directory''' - the absolute path the images will be stored at. Can be anything ('''Must end with /'''):
** /mnt/sdaX/ - internal SSD (example from Fig.1)
** /mnt/mmc/ or other mounted mmc partition
* Press OK then RECORD

====2. Command line====
* recorded ports: all active ports will be recorded
* mount point '''/mnt/sda1''' (also works for a micro SD card partition, rootfs partition, USB or mounted NFS partition but the recording speed is slower than for an SSD)
* max duration = '''10 min''' (new file every 10 mins or other limit)
* max size = '''1GB''' (new file every 1GB or other limit)
* format = '''mov'''
* status updates: '''/var/tmp/camogm.status'''
start recording:

echo "format=mov;status=/var/tmp/camogm.status;prefix=/mnt/sda1/;duration=600;length=1073741824;start" > /var/volatile/camogm_cmd

stop recording:
echo "stop" > /var/volatile/camogm_cmd
sync
'''NOTE:''' ''sync'' is important if you power off the camera w/o proper unmounting of the media.

File:Camogmgui main.png

2017-01-06T16:47:33Z

Mikhail:

10393 manual

2017-01-06T13:44:56Z

Mikhail: /* Serial console access */

==Important Notes==
* As of 2016/12/15, the software ported from 10353 supports only 5MPix sensors, for 14MPix, please see:
**[http://wiki.elphel.com/index.php?title=Tmp_manual&oldid=14676 older version of this manual with links to older software images]

==In the package==
* 10393 camera system
{|
|[[File:NC393-CS marked ports.jpeg|thumb|200px|Fig.1 10393 interfaces]]
|}
* Power supply wall adapter (default: 18-75V, [[10393_power|more information]])
* CAT6 network cable
* μUSB-to-USB cable
* Recovery μSD card
* If the camera is calibrated the calibration data will be on a separate storage media or on the internal SSD (likely /mnt/sda1)

==Interfaces==
See Fig.1:
{| class="wikitable"
|-
! GigE
| gigabit network
|-
! μSD
| micro SD card slot - boot or storage
|-
! console
| serial console port, use μUSB-to-USB cable
|-
! eSATA+USB
| 2-in-1. Connect USB or eSATA device. USB2.0 host
|-
! μUSB
| USB2.0 host
|-
! sync
| sync multiple cameras or other devices - input/output trigger signal through a 4-conductor 2.5mm audio plug with cable (example: [http://www.digikey.com/products/en?keywords=839-1029-ND digikey])
|}

==Power on==
* Plug in the power supply
* Connect to LAN using the network cable

====Notes====
* Boot time: ~30s
* The default boot is from the on-board NAND flash. [[Boot_options_393|More information]] on available boot options and recovery boot.

==Defaults==
{| class="wikitable"
|-
! IP Address
| 192.168.0.9
|-
! User
| root
|-
! Password
| pass
|}

* The default IP address is set in the ''/etc/elphel393/init_elphel393.py''.
* If present the internal SSD will be formatted into 2 partitions:
** /dev/sda1 - ext4 (~64-100GB)
** /dev/sda2 - raw partition (no file system) for fast recording

==Command line access==
* ssh from PC terminal:
$ ssh root@192.168.0.9

==Serial console access==
* Use a ''microUSB-USB cable'' to connect '''console μUSB port''' (see Fig.1) to PC - the cable's end should be thin enough otherwise interferes with an inserted mmc ('''m'''ulti '''m'''edia '''c'''ard = μSD card).

* In Linux the '''minicom''' program can be used
$ minicom -c on
Most likely the device will be /dev/ttyUSB0. Settings:
* 115200 8N1, no for hardware/software flow control
Refer to the following article for more details on using '''minicom''': [http://wiki.elphel.com/index.php?title=Using_minicom_to_connect_to_Elphel393_camera Using minicom to connect to Elphel393 camera]

==Web user interface (camvc)==
http://192.168.0.9/closeme.html (type in the browser address bar - will be changed soon):
* The page contains links to camvc user interface for each individual camera port.
* camvc was ported from the 10353 camera series:
** change parameters like image format, resolution, auto exposure, auto white balance and more. Alternative way to change parameters is described [[Tmp_manual#Change_parameters|below]].
** pause compressor and search within buffered images
** help tips available - see Fig.2 - select then mouse over a control element of interest
{|
| valign='top'|[[image:Help tips.jpeg|250px|thumb|Fig.2 enable camvc help tips]]
|[[File:Controls with blank.jpeg|300px|thumb|Fig.3 camvc controls]]
|}

==Download live images==
====camvc====
* For a currently opened port (displayed in the window title and as "...sensor_port=0..." in the URL):
{|
|[[image:Camvc image capture.jpeg|250px|thumb|Fig.4 Acquire an image from the Camera Control Interface]]
|}

====browser====
port 0: http://192.168.0.9:2323/img
port 1: http://192.168.0.9:2324/img
port 2: http://192.168.0.9:2325/img
port 3: http://192.168.0.9:2326/img

====command line====
wget http://192.168.0.9:2323/img -O filename.jpeg
wget http://192.168.0.9:2324/img -O filename.jpeg
wget http://192.168.0.9:2325/img -O filename.jpeg
wget http://192.168.0.9:2326/img -O filename.jpeg

==Video==
===Display===
====Multipart JPEG stream====
http://192.168.0.9:2323/mimg
http://192.168.0.9:2324/mimg
http://192.168.0.9:2325/mimg
http://192.168.0.9:2326/mimg

====GStreamer====

gst-launch-1.0 souphttpsrc is-live=true location=http://192.168.0.9:2323/mimg ! jpegdec ! xvimagesink

* Only mjpeg, no rtsp yet.
* More examples at [[Using_gstreamer#Display|Using GStreamer]]

===Record===
* Recording is done by the '''camogm''' program
* If recording to internal or external SSD, please, read about [[Tmp_manual#eSATA_port_switching|eSATA port switching]]
* important: Event logger (GPS, IMU, IMG, EXT) recording is started/stopped separately. See [[Tmp_manual#Record_the_Event_Logger_data_.28GPS.2CIMU.2CIMG_.26_EXT.29|instructions]] below.
* For SATA devices camogm supports:
** recording to a partition with a file system - up to 80MB/s
** (default) faster recording to a partition without a file system (raw partition) avoiding OS calls - up to 220MB/s
* To extract data from a raw partition use '''dd''' or [https://github.com/Elphel/elphel-tools-x393 these scripts] to get the data and split it into images.
* Can record to an mmc partiton or usb.
* [[Using_camogm_with_Elphel393_camera|More info]]
* If the ''prefix'' parameter, which is ''absolute path + prefix'', for a channel is not set the file will be written somewhere to rootfs.
** if prefix is empty then the ''absolute path'' must end with a slash.

====browser====
Example 1: (provide a correct media mount point - /mnt/sda1/)

* http://192.168.0.9/camogmgui.php


====command line====
Example:

* '''/home/root''', file prefix='''test_''', '''1GB''' or '''10min''' files whichever occurs first
** setup and start (in one line):
echo "format=mov;status=/var/tmp/camogm.status;prefix=/home/root/test_;duration=600;length=1073741824;start" > /var/volatile/camogm_cmd
** stop recording:
echo "stop" > /var/volatile/camogm_cmd
sync


==Event Logger (GPS, IMU, IMG & EXT)==
* [[Event_logger|'''More information''']]
===Record===
====web====
* Start:
http://192.168.0.9/logger_launcher.php?cmd=start&file=/mnt/sda1/test.log&index=1&n=10000000
* Stop:
http://192.168.0.9/logger_launcher.php?cmd=stop
* Help:
http://192.168.0.9/logger_launcher.php

====command line====
* start:
root@elphel393:~# cat /dev/imu > /path/filename.log
* stop - CTRL-C or kill the process

===Read===
* http://192.168.0.9/read_imu_log.php (will display help)
** on the first access creates /www/pages/logs/ (http://192.168.0.9/logs/)
** link the recorded logs to /www/pages/logs/
** refresh http://192.168.0.9/read_imu_log.php

==Change parameters==
* http://192.168.0.9/autocampars.php - save/restore/initialize camera/sensor parameters
[[Autocampars 393|'''More information''']]

* http://192.168.0.9/parsedit.php - read/write parameters:
** POST request
Read: http://192.168.0.9/parsedit.php?sensor_port=0&PAR1&PAR2
Change: http://192.168.0.9/parsedit.php?sensor_port=0&PAR1&PAR2 - update values - submit form

** GET request - XML response
Read: http://192.168.0.9/parsedit.php?immediate&sensor_port=0&PAR1&PAR2
Change: http://192.168.0.9/parsedit.php?immediate&sensor_port=0&PAR1=VAL1&PAR2=VAL2

Note 1: if the parameter's value is specified in URL it will be applied. The call can have mixed specified and unspecified parameters.

Note 2: The new value is read on the next call.

Example:
* set 10 fps and enable output trigger signal
http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0&TRIG_OUT=0x66555&TRIG_PERIOD=10000000&TRIG=4

[[Parsedit.php|'''More information''']]

'''Notes:'''
* parsedit.php and autocampars.php were ported from 353 camera series. There are a few changes from the originals related to 4x sensor ports:
** parameters are individual for each sensor port - writing parameters to multiple port at once is controlled with a (bit-)'''mask''' input box
** if opened w/o sensor_port specified the page will show links to available ports
** '''sensor_port=x''', where x=0..3 - in the address string - for a single sensor camera it is normally 0

==Image formats==
====jpeg====
* '''color''': YCbCr 4:2:0, 3x3 pixels
* '''mono6''': monochrome - color YCbCr 4:2:0 with zeroed out color components
* '''mono''' : monochrome - color YCbCr 4:0:0 with omitted color components

'''Note:''' Is not the best for processing since a lot of information is lost at demosaicing
====jp4 raw====
* [[JP4|'''More information''']]

==Temperature monitor==
* http://192.168.0.9/hwmon.html:
** Tshutdown - automatic shutdown temperature level (default is 90°C)
{|
|[[File:10393_hwmon.jpeg|thumb|200px]]
|}

==eSATA port switching==
* requres [[10389]]
* available connections:
** camera <=> internal SSD (default)
** camera <=> external drive (external drive will need a separate power source)
** PC <=> internal SSD
* [[Sata_multiplexer_10389|'''More information''']]

==Proper shutdown==
* if not properly shutdown - μSD might get corrupted (run '''sync''' at least)
shutdown -hP now
Same effect:
http://192.168.0.9/autocampars.php?reboot

==Firmware/software update==
[[Poky_2.0_manual#Write_files_to_media_and_boot|'''More information''']]

==Firmware images==
TBA

==Other info==
====Tools for calibrated systems====
* [[Elphel_Software_Kit_for_Ubuntu#ImageJ_and_Elphel_plugins_for_imageJ|Install ImageJ plugins]]
** decode jp4 raw format
** aberrations correction
** distortion correction (pixel mapping)
** rectification and projection
** '''JP46 Reader camera''' - decode JP4/JP46
** '''Eyesis correction''' - post-process JP4s using calibration data

====switch between ERS and GRR modes in MT9P006====
* [[Electronic_Rolling_Shutter#ERS_and_GRR_in_MT9P001_on_10393|Read article]]
====External/internal trigger and FPS control====
* [[Trigger_393]]
===SSD/MMC/USB formatting===
* [[Format_SSD_MMC]]
===Boot modes===
* [[Boot_options_393|Boot options]]

==Known problems==
* [solved] Vertical artifacts in jpegs. Images are ok at 100% quality. Fixed, testing.
* http://192.168.0.9:232x/noexif/mimg - multipart jpeg displays corrupted frames from time to time. Reason: network bandwidth?
* [solved] Sometimes on power-on (NAND flash boot) cannot mount the card's rootfs partition. Kernel Panics. Power off/on. Soft "reboot -f" works ok.
...
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
...
[[VFS:_Unable_to_mount_root_fs_on_unknown-block(179,2)|More info]]
* Changing exposure/quality/gains - can corrupt images - needs testing.

* After rewriting rootfs to μSD card - some of the cards get a corrupted partition - re-partitioning (reformatting?) solves the problem.
On the camera the rootfs is mounted as RW and some of the files are changed (also links created) -
most of the changes are now moved to tmpfs but something might have been missed.

==Notes==
* In case rootfs is on flash, it might make sense (or maybe not as the history is updated only once on session exit) to disable bash sessions command history - [http://stackoverflow.com/questions/18663078/disable-history-in-linux disable bash history]

[[Category:393]]

Boot options 393

2017-01-06T13:18:29Z

Mikhail:

==Description==
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 - it 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 modified version (see instructions below).

Another way to "tell" the camera to boot from the μ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:
* Switch not closed, pull-up resistor not detected -> no card present, boot from the internal NAND flash
* Switch closed -> data (non-bootable) card present, boot from the internal NAND flash
* Switch not closed, pull-up resistor is detected -> bootable card present, boot from the MMC card

{|
|[[File:Recover mmc.jpeg|130px|thumb|Fig.1 Recovery μSD card ('cut' corner) - forces the system board to boot from it]]
|}

==Boot instructions==
===Internal NAND flash (default)===
* Make sure the recovery card is not inserted (regular card can stay in)
* Power on

===Recovery micro SD card===
Requirements:
* A modified card that doesn't lock the mechanical CD pin in the slot - it's done by carefully filing off the corner (see Fig.1) - most cards have circuitry there and get damaged. Use the one that came with the camera or order a new one.
Instructions:
* insert the card, power on

===Regular micro SD card===
Requirements:
* μUSB-to-USB cable
* Linux: compile [https://sourceforge.net/p/elphel/cp210x_gpio/ci/master/tree/ cp210x driver]
Instructions:
* Power on
* Connect the camera's console port (see Fig.2, right under the μSD slot) to PC using μUSB-to-USB cable
{|
|[[File:NC393-CS marked ports.jpeg|thumb|200px|Fig.2 10393 camera ports]]
|}
* Reload the cp210x driver:
** unplug the μUSB-to-USB cable
** In the terminal from the directory where the driver was built, run:
sudo rmmod cp210x
sudo insmod cp210x.ko
** plug the cable back (the driver will stay loaded until the PC is rebooted).

* In the terminal from the directory where the driver was built, run:
./cp210x_gpio.py 0x6;
./cp210x_gpio.py 0xe;

* To reboot back to NAND flash w/o power cycling:
./cp210x_gpio.py 0x7;
./cp210x_gpio.py 0xf;

===Other boot options (set in u-boot or device tree)===
Follow the instructions of the 3 options above but with different bootloader or device tree.

The 3 options above define where the cpu's boot ROM loads SPL version of u-boot from: NAND flash or μSD card. The SPL u-boot loads the full-size u-boot.
In its turn he full size u-boot can be instructed where to load the device tree and the kernel from, available options:
* NAND flash (default if SPL was loaded from flash)
* μSD card (default if SPL was loaded from μSD card)
* internal SSD (not tested)
* network (not tested)

Next, the location of rootfs ("/") is set in the device tree. Available locations for rootfs:

* '''any μSD card partition'''. The default device tree parameter is:
bootargs = "cma=336M console=ttyPS0,115200 root=/dev/mmcblk0p2 rw ip=192.168.0.9 earlyprintk rootwait rootfstype=ext4";
* '''any internal NAND flash partition'''. The default parameter is:
bootargs = "cma=336M console=ttyPS0,115200 root=ubi0:elphel393-rootfs rw ip=192.168.0.9 earlyprintk rootwait rootfstype=ubifs ubi.mtd=4,2048";
* '''any internal SSD''' (if installed) partition. There is no default device tree.
* '''RAM''' - unpack an archive from a μSD card FAT32 partition into RAM but it was tested a while ago:
bootargs = "cma=336M console=ttyPS0,115200 root=/dev/ram rw ip=192.168.0.9 earlyprintk ramdisk_size=262144";
** Changes will not be stored
** Modify env commands in the u-boot (in elphel393.h or when in the u-boot command line)
** Carefully check the actual and hardcoded images' sizes in the u-boot (elphel393.h) and the device tree (elphel393_xxx.dts) with the actual sizes.
** Don't want to waste the RAM - make tiny rootfs

====Notes====
* when loaded the full-size u-boot can be key-interrupted and override bootargs parameter of the device tree.
* '''To build a custom device tree''', see [http://wiki.elphel.com/index.php?title=Poky_2.0_manual SDK manual]'''

The cp210x_gpio.py script controls GPIO pins for CP210X USB to UART Bridges and it comes with the patch for the cp210x driver.
==cp210x_gpio.py -h==
$./cp210x_gpio.py -h
usage: cp210x_gpio.py [-h] [-d DEVICE] [-m MASK] [gpio_value]

positional arguments:
gpio_value hex value for GPIO. Example (GPIO[3:0]): 0xf - all
1's, 0x0 - all 0's. If not specified - read GPIO only

optional arguments:
-h, --help show this help message and exit
-d DEVICE, --device DEVICE
USB device. Default: /dev/ttyUSB0
-m MASK, --mask MASK hex value for masking out GPIO bits: 1 - enable
rewrite, 0 - disable. Example (GPIO[3:0]): -m 0xf

[[Category:393]]

Boot options 393

2017-01-06T13:00:22Z

Mikhail: /* Internal NAND flash (default) */

==Description==
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 - it 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 modified version (see instructions below).

Another way to "tell" the camera to boot from the μ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:
* Switch not closed, pull-up resistor not detected -> no card present, boot from the internal NAND flash
* Switch closed -> data (non-bootable) card present, boot from the internal NAND flash
* Switch not closed, pull-up resistor is detected -> bootable card present, boot from the MMC card

{|
|[[File:Recover mmc.jpeg|130px|thumb|Fig.1 Recovery μSD card ('cut' corner) - forces the system board to boot from it]]
|}

==Boot instructions==
===Internal NAND flash (default)===
* Make sure the recovery card is not inserted (regular card can stay in)
* Power on

===Recovery micro SD card===
Requirements:
* A modified card that doesn't lock the mechanical CD pin in the slot - it's done by carefully filing off the corner (see Fig.1) - most cards have circuitry there and get damaged. Use the one that came with the camera or order a new one.
Instructions:
* insert the card, power on

===Regular micro SD card===
Requirements:
* μUSB-to-USB cable
* Linux: compile [https://sourceforge.net/p/elphel/cp210x_gpio/ci/master/tree/ cp210x driver]
Instructions:
* Power on
* Connect the camera's console port (see Fig.2, right under the μSD slot) to PC using μUSB-to-USB cable
{|
|[[File:NC393-CS marked ports.jpeg|thumb|200px|Fig.2 10393 camera ports]]
|}
* Reload the cp210x driver:
** unplug the μUSB-to-USB cable
** In the terminal from the directory where the driver was built, run:
sudo rmmod cp210x
sudo insmod cp210x.ko
** plug the cable back (the driver will stay loaded until the PC is rebooted).

* In the terminal from the directory where the driver was built, run:
./cp210x_gpio.py 0x6;
./cp210x_gpio.py 0xe;

* To reboot back to NAND flash w/o power cycling:
./cp210x_gpio.py 0x7;
./cp210x_gpio.py 0xf;

===Other boot options (set in u-boot or device tree)===
Follow the instructions of the 3 options above but with different bootloader or device tree.

The 3 options above define where the cpu's boot ROM loads SPL version of u-boot from: NAND flash or μSD card. The SPL u-boot loads the full-size u-boot.
In its turn he full size u-boot can be instructed where to load the device tree and the kernel from, available options:
* NAND flash (default if SPL was loaded from flash)
* μSD card (default if SPL was loaded from μSD card)
* internal SSD (not tested)
* network (not tested)

Next, the location of rootfs ("/") is set in the device tree. Available locations for rootfs:

* '''any μSD card partition'''. The default device tree parameter is:
bootargs = "cma=336M console=ttyPS0,115200 root=/dev/mmcblk0p2 rw ip=192.168.0.9 earlyprintk rootwait rootfstype=ext4";
* '''any internal NAND flash partition'''. The default parameter is:
bootargs = "cma=336M console=ttyPS0,115200 root=ubi0:elphel393-rootfs rw ip=192.168.0.9 earlyprintk rootwait rootfstype=ubifs ubi.mtd=4,2048";
* '''any internal SSD''' (if installed) partition. There is no default device tree.
* '''RAM''' - unpack an archive from a μSD card FAT32 partition into RAM but it was tested a while ago:
bootargs = "cma=336M console=ttyPS0,115200 root=/dev/ram rw ip=192.168.0.9 earlyprintk ramdisk_size=262144";
** Changes will not be stored
** Modify env commands in the u-boot (in elphel393.h or when in the u-boot command line)
** Carefully check the actual and hardcoded images' sizes in the u-boot (elphel393.h) and the device tree (elphel393_xxx.dts) with the actual sizes.
** Don't want to waste the RAM - make tiny rootfs

====Notes====
* when loaded the full-size u-boot can be key-interrupted and override bootargs parameter of the device tree.
* '''To build a custom device tree''', see [http://wiki.elphel.com/index.php?title=Poky_2.0_manual SDK manual]'''

==cp210x_gpio.py -h==
$./cp210x_gpio.py -h
usage: cp210x_gpio.py [-h] [-d DEVICE] [-m MASK] [gpio_value]

positional arguments:
gpio_value hex value for GPIO. Example (GPIO[3:0]): 0xf - all
1's, 0x0 - all 0's. If not specified - read GPIO only

optional arguments:
-h, --help show this help message and exit
-d DEVICE, --device DEVICE
USB device. Default: /dev/ttyUSB0
-m MASK, --mask MASK hex value for masking out GPIO bits: 1 - enable
rewrite, 0 - disable. Example (GPIO[3:0]): -m 0xf

[[Category:393]]

Using camogm with Elphel393 camera

2017-01-06T03:25:37Z

Mikhail:

===Introduction===
Elphel 393 series cameras can be equipped with m.2 SSD drive used for images and video recording. The camera equipped with a drive should be configured in a way that the drive can be accessible from Linux operating system. This is normally done with a configuration script which is executed during system boot. The script is located in the /etc/elphel393 directory and called ''init_elphel393.py''. There is a set of parameters which this script receives from init script /etc/ini.d/init_elphel393 and one of them is responsible for SATA controller configuration and driver loading:

\"sata\" :1,

Make sure this parameter is set to 1 if your camera is equipped with SSD drive. You should see the following messages in system log after successful initialization and auto-mounting:

[ 30.587212] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 30.594510] ata1.00: ATA-9: SanDisk SD8SMAT128G1122, Z2320000, max UDMA/133
[ 30.601426] ata1.00: 250069680 sectors, multi 1: LBA48 NCQ (depth 0/32)
[ 30.616091] ata1.00: configured for UDMA/133
[ 30.620669] scsi 0:0:0:0: Direct-Access ATA SanDisk SD8SMAT1 0000 PQ: 0 ANSI: 5
[ 30.629879] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 30.630011] sd 0:0:0:0: [sda] 250069680 512-byte logical blocks: (128 GB/119 GiB)
[ 30.630987] sd 0:0:0:0: [sda] Write Protect is off
[ 30.631106] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 30.637003] sda: sda1 sda2
[ 30.646115] sd 0:0:0:0: [sda] Attached SCSI disk

The disk model and the number of partitions (sda1 and sda2) in the example above correspond to a test platform and they may not be the same in your camera. <code>/dev/sda2</code> in this example is not partitioned and not mounted:

~# mount
/dev/root on / type ext4 (rw,relatime,data=ordered)
devtmpfs on /dev type devtmpfs (rw,relatime,size=449540k,nr_inodes=112385,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /var/volatile type tmpfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
/dev/mmcblk0p1 on /mnt/mmc type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sda1 on /mnt/sda1 type ext2 (rw,relatime,errors=continue)

The program for video/images recording is called ''camogm''. Its full description for previous series of Elphel cameras is available on [[Camogm]] wiki page. Current version of the program supports four sensor channels and has the same command set as the previous version. The program can be started the same way as described in [[Camogm#Starting_camogm|Starting camogm]] section and it will create command pipe called ''camogm_cmd'' in the following directory:

root@elphel393:~# ls -l /var/volatile/state/
-rw-r--r-- 1 root root 176 Dec 21 18:56 camera
prwxrwxrwx 1 root root 0 Dec 21 19:28 camogm.state
prwxr-xr-x 1 root root 0 Dec 21 19:28 camogm_cmd

The status information output can be redirected to a file as described in [[Camogm#Sending_Commands_to_camogm|Sending commands to camogm]].

Note, that ''camogm'' is under development and not all features of the previous version have been ported to new camera. As for now, geo tagging and exif specific commands are not implemented. Watch for updates on our [https://github.com/Elphel github page].

You can start ''camogm'' as a stand-along command-line application or use web GUI interface in a browser to control the program. The examples of using ''camogm'' in both ways are shown below.
===Example===
====1. WebGUI====
* http://192.168.0.9/camogmgui.php
* In the '''Format''' tab check the settings then press OK button
{|
| valign='top'|[[File:Camogmgui format tab.png|thumb|400px|Fig.1 Camogmgui - change recording formats]]
| valign='top'|[[File:Camogmgui recording 1.png|thumb|400px|Fig.2 Camogmgui - recording status]]
|}
=====Fast recording=====
''camogm'' can write data to disk or partition in a special fast recording mode. This mode supports higher sequential write speeds than those that can be achieved during regular file recording to a file system but additional step to extract data from disk is needed. Use [https://github.com/Elphel/elphel-tools-x393 these scripts] to extract raw data from disk and split it into separate images.
* Keep '''Use fast recording''' checkbox selected - press OK then RECORD
** An image sequence will be written to a raw partition.
** The '''Format:''' options will be disabled as well as '''Directory'''

=====Normal recording=====
In this mode ''camogm'' saves data to regular files on a file system.
* Deselect '''Use fast recording'''
* Choose '''Format''' (Ogg Media Stream is not tested)
* Type '''Directory''' - the absolute path the images will be stored at. Can be anything ('''Must end with /'''):
** /mnt/sdaX/ - internal SSD (example from Fig.1)
** /mnt/mmc/ or other mounted mmc partition
* Press OK then RECORD

====2. Command line====
* recorded ports: all active ports will be recorded
* mount point '''/mnt/sda1''' (also works for a micro SD card partition, rootfs partition, USB or mounted NFS partition but the recording speed is slower than for an SSD)
* max duration = '''10 min''' (new file every 10 mins or other limit)
* max size = '''1GB''' (new file every 1GB or other limit)
* format = '''mov'''
* status updates: '''/var/tmp/camogm.status'''
start recording:

echo "format=mov;status=/var/tmp/camogm.status;prefix=/mnt/sda1/;duration=600;length=1073741824;start" > /var/volatile/camogm_cmd

stop recording:
echo "stop" > /var/volatile/camogm_cmd
sync
'''NOTE:''' ''sync'' is important if you power off the camera w/o proper unmounting of the media.

10393

2016-12-22T20:23:02Z

Mikhail: /* Modifications */

==About==
[[Image:10393_top_sm.png|frame|[[Media:10393_top.jpeg|10393 board, top view]]]]
[[Image:10393_bottom_sm.png|frame|[[Media:10393_bottom.jpeg|10393 board, bottom view]]]]
10393 is the system board of Elphel NC393 series camera. It will also replace [[10353|10353 board]] in [[Elphel_Eyesis4Pi|Eyesis4pi]] and other Elphel multi-sensor cameras. It has the same physical dimensions as 10353 and may be used as an upgrade to the previous camera modules.

==Overview==
====Operating System====
* OpenEmbedded Linux (built with [https://www.yoctoproject.org/tools-resources/projects/poky Yocto Poky])
====Processor====
* Xilinx Zynq 7030 SoC
** Dual-core ARM Cortex-A9 + FPGA
** 800MHz
====Supported Image Sensors====
* [http://www.onsemi.com/PowerSolutions/product.do?id=MT9P006 MT9P006] - 5MPix 1/2.5" CMOS
* [http://www.onsemi.com/PowerSolutions/product.do?id=MT9F002 MT9F002] - 14MPix 1/2.3" CMOS
====Memory and Storage====
* 1.0 GB DDR3 memory - system RAM
* 0.5 GB DDR3 memory - FPGA RAM
* 1.0 GB NAND flash - program storage
* microSD card slot - storage and system recovery

====Interfaces====
[[File:Nc393 4sensors.jpeg|thumb|220px|10393 + 4 sensors]]
* Gigabit ethernet
* micro USB - system console (serial port), reboot, select boot device
* 4x sensor ports - routed to FPGA, each reconfigurable for general multi-purpose use
* Added by [[10389|10389 Extension board]]:
** 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, I2C and GPIO
*** support other extension boards ([[103695|IMU]], [[103696|GPS]])

====Other====
* Compressor bandwidth - up to 1 GPix/s (e.g., processing 10MPix@100fps)
* Image formats: JPEG, JP4, RAW (coming)
* Wake-up on alarm
====Power====
* 3.3VDC
====Mechanical properties====
* Dimensions: 96x38x20.5 mm (with all connectors installed). Height can be reduced by removing the network connector.
* Weight: 31 g
* Mechanical drawings and CAD files for the 10393 board: [[Elphel_camera_parts_0393-00#0393-00-20A_-_10393_rev_A_System_board_PCB_assembly|link]]

====SDK====
* Firmware:
** [https://eclipse.org Eclipse IDE] + [https://github.com/Elphel/vdt-plugin VDT-Plugin]
** [http://www.xilinx.com/products/design-tools/vivado.html Vivado WebPACK Edition]
** [http://iverilog.icarus.com/ IVerilog]
** [http://gtkwave.sourceforge.net/ GTKWave]
* Software (Kernel and Applications):
** [https://eclipse.org Eclipse IDE]
** [https://www.yoctoproject.org/tools-resources/projects/poky Yocto Poky]
* Sources:
** [https://github.com/Elphel GitHub/Elphel]

====License====
* [http://www.ohwr.org/projects/cernohl CERN OHLv1.1+]
* [http://www.gnu.org/licenses/gpl.html GPLv3+]

==More details==
[[Image:10393_bd.png|thumb|400px|[[Media:10393.pdf|10393 Circuit Diagram, Parts List, PCB layout]]     [[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.

Block diagram below shows major parts and I/O ports of the 10393 board. Left edge of the diagram corresponds to the sensor connections, right one - to the camera back panel with external connectors, top and bottom contain inter-board connections:
* The system is built around Xilinx Zynq 7030 SoC that combines a dual-core ARM processor, a rich set of the standard peripherals and FPGA on the same chip. This combination provides high bandwidth connection between the processors and the FPGA fabric.
* 4 identical sensor ports are 30-conductor 0.5mm pitch flex cable connectors, compatible with the earlier Elphel products. These connectors are split into two pairs, so they are closest to one short edge of the board - two on each side. Combined with an external multiplexer boards (at the expense of proportionally lower frame rate) each 10393 can work with up to 16 sensors (12 with the existing [[10359|10359 board]]).
* 500MB of the dedicated DDR3 memory chip is connected directly to the FPGA portion of the SoC, with the 16-channel image-optimized controller it provides efficient access to the memory for simultaneous image acquisition, compression and image processing. We plan to implement such functionality as real-time image de-warping and correlation of images from multiple sensors for the 3d data extraction.
* 1GB of DDR3 memory (2 chips providing 32-bit data bus) is uses as a system RAM for the processor subsystem.
* 500MB of NAND flash provide program storage.
* Persistent program storage is expandable with the micro-SD cards (not easy to see on the photo as the slot is hidden under the network connector). This interface provides bootable memory, so it is always possible to restore the camera functionality even if the system NAND will be accidentally flashed with corrupted image.
* Largest visible component on the board is the RJ45 connector for the Gigabit Ethernet, containing all the required magnetics (transformers) that are compatible with the PoE application. The peculiar shape of the board near connector is designed that it can be used with the hardware of the sealed RJ45 connectors.
* On the other side of the PCB under the RJ45 connector is the micro-USB connector type B (device) that can be used to implement a system console for camera software development. Additionally the USB-to-serial converter in on the 10393 board has GPIO functionality, it makes it possible to remotely reset/reboot the camera as well to as select the boot source (on the board NAND flash or external memory card). It also allows to build a fail-safe autonomous system with a camera reset-over-USB generated by a different master.
* 10353 uses 3.3VDC as a primary power source. All other voltages required by the SoC and other subsystems are generated from this primary 3.3 by the "Secondary power module" that includes fixed and adjustable by the software (over i2c bus) voltages, some voltages (such as sensor power) can be programmatically turned on or off. Primary 3.3VDC are provided by a separate [[10385|10385 power supply board]] that can be shut down by the software and awaken by an alarm signal from the clock/calendar.
* Clock/calendar uses a super-capacitor (large black cylinder on the bottom view photo) to provide power when the camera is turned off. This allows camera to be used to record time-lapse images during extended periods with only a battery, possibly combined with a small solar panel.
* Extension port uses a high-density 40-pin connector to interface a [[10389|10389 Extension board]]. It provides USB (host) signals, SATA channel, system i2c and GPIO signals from the FPGA. Extension board provides:
** SSD mass storage in m.2 SATA form-factor (up to 2260 - 22mm x 60mm).
** USB host (micro-A) external connector.
** eSATA/USB combo connector that can be used to connect USB flash drives, external HDD/SDD (powered externally or by USB 5.0V power) and host computer for high-speed data transfer (SATA3.0 - 6GHz)form the internal SSD storage.
** Inter-camera external synchronization connector (2.5mm audio type).
** Inter-camera module synchronization with a 4-conductor flex cables.
** Two of the 10-conductor flex cable ports that carry 3.3VDC, 5.0VDC, USB, i2c and GPIO, compatible with existing [[103695|103695 IMU adapter]] and [[103696|103696 GPS adapter]] boards.

==Modifications==
* [http://community.elphel.com/pictures/10393/FIX_boot_from_flash/ Fix boot from flash/mmc]
==Known issues==
* [http://wiki.elphel.com/index.php?title=SATA_issues SATA issues]

[[Category:393]]

SATA issues

2016-12-22T20:20:39Z

Mikhail: Created page with "== Issue 1: Handshake Error during fast recording == === Description === AHCI controller sets Handshake Error bit in PxSERR register and Interface Fatal Error Status bit in PxIS ..."

== Issue 1: Handshake Error during fast recording ==
=== Description ===
AHCI controller sets Handshake Error bit in PxSERR register and Interface Fatal Error Status bit in PxIS register. If debug messages for AHCI driver are enabled in sysfs then system log will contain the following record:

elphel_irq_handler: elphel-ahci 80000000.elphel-ahci: irq_stat = 0x8000000, host irq_stat = 0x1, SErr = 0x400000

The status of controller registers read from Python interface after system driver has started recovery is the following:

>>> sata.reg_status()
HBA_PORT__PxIS: 0x04000000 [80000110]
1 : INFS (Interface Non-Fatal Error Status (sect. 6.1.2))
HBA_PORT__PxCMD: 0x00040007 [80000118]
1 : HPCP (Hot Plug Capable Port)
1 : POD (Power On Device (RW with Cold Presence Detection))
1 : SUD (Spin-Up Device (RW with Staggered Spin-Up Support))
1 : ST (Start (HBA may process commands). See section 10.3.1)
HBA_PORT__PxTFD: 0x000001d0 [80000120]
1 : ERR (Latest Copy of Task File Error Register)
1 : STS.BSY (Latest Copy of Task File Status Register: BSY)
5 : STS.64 (Latest Copy of Task File Status Register: command-specific bits 4..6 )
HBA_PORT__PxSIG: 0x00000101 [80000124]
101 : SIG (Data in the first D2H Register FIS)
HBA_PORT__PxSSTS: 0x00000123 [80000128]
1 : IPM (Interface Power Management)
2 : SPD (Interface Speed)
3 : DET (Device Detection (should be detected if COMINIT is received))
HBA_PORT__PxSERR: 0x00400000 [80000130]
1 : DIAG.H (Handshake Error (i.e. Device got CRC error))
HBA_PORT__PxCI: 0x00000001 [80000138]
1 : CI (Command Issued: bit per Port, only set when PxCMD.ST==1, also cleared by PxCMD.ST: 1->0 by soft)

=== How to reproduce ===
This error can be reliably reproduced during fast recording to SanDisk SD7SF6S256G1122 mSATA SSD connected to eSATA port. All camera related software should be disabled during test as it will interfere with the test program. Edit /etc/init.d/init_elphel393

$CONFDIR/init_elphel393.py "{\"usb_hub\" :0,\"ip\" :1,\"mcntrl\" :0,\"imgsrv\" :0,\"port1\" :0,\"port2\" :0,\"port3\" :0,\"port4\" :0,\"framepars\" 
:0,\"autoexp_daemon\" :0,\"autocampars\" :0,\"autoexp\" :0,\"autowb\" :0,\"sata\" :0,\"gps\" :0,\"eyesis\" :0 }"

and restart camera. Start AHCI controller configuration program,

root@elphel393:~# x393sata.py

switch SATA multiplexer to external disk (from browser)

http://192.168.0.38/x393_vsc330x.php?c:zynq=esata

and reload disk driver. Start test program and the error will most likely appear within several seconds of recording:

root@elphel393:~# camogm_test -d /dev/sda2 -b 3000000 -c 1000

This disk can be used from the system without this issue although long run tests have not been performed.

Elphel camera parts 0393-27

2016-11-03T22:05:39Z

Mikhail: /* 0393-27-13 - Tube cap */

[[Elphel_camera_parts_0393|Elphel NC393 series camera parts]]

All parts on this page were prepared for 3D printing. Some of them have support elements manually place in most critical parts, so you do not need to enable support elements in your slicer software. All those elements can be easily removed after printing. We used Ultimaker2 with 0.4 mm nozzle for 3D printing all of these parts and achieved good results with 0.7 mm wall thickness and 20% infill density. We posted some examples of 3D printed parts on [http://blog.elphel.com/2016/05/3d-print-your-camera-freedom/ our blog]

One of the parts below, 0393-27-07, is a helper object. It was specifically created for cutting out of SFE mount place in custom designs.

=== 0393-27-01f - C/CS SFE adapter ===
{{Cad4c|0393-27-01f}}
----
=== 0393-27-02d - Adapter for camera body ===
{{Cad4c|0393-27-02d}}
----
=== 0393-27-03c - Support frame adapter ===
{{Cad4c|0393-27-03c}}
----
=== 0393-27-04 - Cable strain relief for 0393-27-03c ===
{{Cad4c|0393-27-04}}
----
=== 0393-27-05 - Cable strain relief for 0393-27-01f ===
{{Cad4c|0393-27-05}}
----
=== 0393-27-06 - Cable strain relief for 0393-27-03c ===
{{Cad4c|0393-27-06}}
----
=== 0393-27-07 - SFE cutout part ===
{{Cad4c|0393-27-07}}
----
=== 0393-27-08a - SFE adapter ===
{{Cad4c|0393-27-08a}}
----
=== 0393-27-09 - SFE adapter ===
{{Cad4c|0393-27-09}}
----
=== 0393-27-10 - Cable strain relief for 0393-27-03c or 0393-27-02d ===
{{Cad4c|0393-27-10}}
----
=== 0393-27-12 - SFE support platform for press fit kit ===
This platform facilitates disk springs support pins installation into SFEs.
{{Cad4c|0393-27-12}}
----

=== 0393-27-13 - Tube cap ===
{{Cad4c|0393-27-13}}
----

=== 0393-27-14 - Mount band ===
This band is used to mount additional parts on top of NC393 camera. One of the possible parts is 0393-27-15 for IMU mount.
{{Cad4c|0393-27-14}}
----

=== 0393-27-15 - IMU support plate ===
This plate is used in combination with 0393-27-14.
{{Cad4c|0393-27-15}}
----

Elphel camera parts 0393-12

2016-10-06T00:10:12Z

Mikhail: /* 0393-12-29A - Sensor front end, CS-mount, Rev "A" */

[[Elphel_camera_parts_0393|Elphel NC393 series camera parts]]
== 0393-12 - front ends ==
=== 0393-12-29 - Sensor front end, CS-mount ===
{{Cad4a|0393-12-29}}
----
=== 0393-12-29A - Sensor front end, CS-mount, Rev "A" ===
Note: X3D model will be updated later.
{{Cad4a|0393-12-29A}}
----
=== 0393-12-29B - Sensor front end, CS-mount, Rev "B" ===
Note: X3D model will be updated later.
{{Cad4a|0393-12-29B}}
----

=== 0393-12-30 - Sensor adjustment plate ===
{{Cad4a|0393-12-30}}
----
=== 0393-12-30A - Sensor adjustment plate, Rev. "A" ===
Note: X3D model will be updated later
{{Cad4a|0393-12-30A}}
----

=== 0393-12-31 - Disk springs support pin ===
Made of stainless steel 316 hypodermic round tubing
{{Cad4a|0393-12-31}}
----
=== 0393-12-31A - Disk springs support pin, Rev. "A" ===
Made of stainless steel 316 hypodermic round tubing

Note: X3D model will be updated later
{{Cad4a|0393-12-31A}}
----

=== 0393-12-43 - SFE M12 body ===
{{Cad4a|0393-12-43}}
----
=== 0393-12-44 - SFE M12 adapter ===
{{Cad4a|0393-12-44}}
----
=== 0393-12-50 - Fisheye head adapter ===
{{Cad4a|0393-12-50}}
----
=== 0393-12-51 - SFEs mount ===
{{Cad4a|0393-12-51}}
----

Elphel camera parts 0393-27

2016-10-06T00:04:35Z

Mikhail: /* 0393-27-12 - SFE support platform for press fit kit */

Elphel camera parts 0393-27

2016-10-06T00:02:16Z

Mikhail: /* 0393-27-10 - Cable strain relief for 0393-27-03c or 0393-27-02d */