Difference between revisions of "10393 manual"
From ElphelWiki
(→In the package) |
(→Defaults) |
||
Line 65: | Line 65: | ||
* The default IP address is set in the ''/etc/elphel393/init_elphel393.py''. | * 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 | ||
==<font color="blue">Command line access</font>== | ==<font color="blue">Command line access</font>== |
Revision as of 13:16, 29 December 2016
Contents
- 1 Important Notes
- 2 In the package
- 3 Interfaces
- 4 Power on
- 5 Defaults
- 6 Command line access
- 7 Serial console access
- 8 Web user interface (camvc)
- 9 Download live images
- 10 Video
- 11 Event Logger (GPS, IMU, IMG & EXT)
- 12 Change parameters
- 13 Temperature monitor
- 14 eSATA port switching
- 15 Proper shutdown
- 16 Firmware/software update
- 17 Firmware images
- 18 Other info
- 19 Known problems
- 20 Notes
Important Notes
- As of 2016/12/15, the software ported from 10353 supports only 5MPix sensors, for 14MPix, please see:
In the package
- 10393 camera system
- Power supply wall adapter (default: 18-75V, 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:
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: 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. More information on available boot options and recovery boot.
Defaults
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 (multi media card = μ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
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.
- pause compressor and search within buffered images
- help tips available - see Fig.2 - select then mouse over a control element of interest
Download live images
camvc
- For a currently opened port (displayed in the window title and as "...sensor_port=0..." in the URL):
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
Record (to internal storage)
- Recording to internal storage is performed by the camogm program
- important: Event logger (GPS, IMU, IMG, EXT) recording is started/stopped separately. See 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 these scripts to get the data and split it into images.
- Can record to an mmc partiton as well.
- 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
browser
Example 1: (provide a correct media mount point - /mnt/sda1/)
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)
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
- 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
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
Temperature monitor
- http://192.168.0.9/hwmon.html:
- Tshutdown - automatic shutdown temperature level (default is 90°C)
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
- 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
Firmware images
TBA
Other info
switch between ERS and GRR modes in MT9P006
External/internal trigger and FPS control
SSD/MMC/USB formatting
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) ...
- 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 - disable bash history