Difference between revisions of "10393 manual"
From ElphelWiki
(→Serial console access) |
(→Serial console access) |
||
Line 42: | Line 42: | ||
==<font color="blue">Serial console access</font>== | ==<font color="blue">Serial console access</font>== | ||
− | * 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 = & | + | * 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). |
* Linux: '''minicom -c on''' | * Linux: '''minicom -c on''' |
Revision as of 14:20, 19 December 2016
Contents
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
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.
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).
- Linux: minicom -c on
- likely device: /dev/ttyUSB0
- settings: 115200 8N1, no for hardware/software flow control
web interface (camvc)
http://192.168.0.9/closeme.html (will get changed soon)
Get images
channel 1: http://192.168.0.9:2323/img
channel 2: http://192.168.0.9:2324/img
channel 3: http://192.168.0.9:2325/img
channel 4: http://192.168.0.9:2326/img
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
- 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 (likely /usr/local/verilog/)
browser
Example 1: (provide a correct media mount point)
command line
Example:
- channel 2, /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
Change parameters
- http://192.168.0.9/autocampars.php - read & write parameters (through parsedit.php), save configuration (if booted from NAND flash - "shutdown -r now" will sync changes or copy /etc/elphel393/*.xml to /tmp/rootfs.ro/etc/elphel393/ (lower layer of overlayfs), if booted from mmc - no need to reboot, just sync)
- parsedit.php
The response is in XML form:
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: It's just if the parameter value is specified it will be applied. The call can have mixed specified and unspecified parameters.
Note 2: The new value is read on the next call.
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
Proper shutdown
- if not properly shutdown - μSD might get corrupted (run sync at least)
shutdown -hP now
Firmware image
- 20160804 (new)
- root/pass
- overlayfs enabled if rootfs is on flash - lower: /tmp/rootfs.ro, upper: /tmp/rootfs.rw - changes to the filesystem are made on:
reboot -f
or
shutdown -hP now
or (most likely will work but correct work is not guaranteed)
overlay_sync
- 20160626 (old)
- python scripts moved to /tmp - dependencies create pycs
- init_elphel393.sh moved from μSD card to /etc in rootfs - boot from flash doesn't require an inserted card for fixed boards.
- default IP address changed to 192.168.0.9 as in the image built from our repositories.
- 20160622 (old)
- 20160614 (old)
- 20160607 (old)
- 20160601 (old)
- 20160526 (old)
- 20160524 (old)
- 20160519 (old)
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