Eyesis4Pi 393 User Guide - Recording

From ElphelWiki
Revision as of 09:50, 12 June 2018 by Oleg (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Download & Install GUI

Install GUI to the device that will be used for recording. There are several ways to install it:


cd <any-path>
git clone https://git.elphel.com/Elphel/eyesis4pi-393-gui.git
git pull (repeat any time to get the latest)

Follow the instructions in INSTALL.txt:

1. (For Kubuntu 16.04) Install the following packages, terminal:
 sudo apt-get install apache2 php5.6 php5.6-curl
2. Make the src folder visible to the web server:
2a. Create a link, terminal: "sudo ln -sf <path-to-eyesis4pi_gui-folder> /var/www/html/eyesisgui"
2b. Or copy all the files to /var/www/eyesisgui.
Note: /var/www/html is apache2 document root folder.

(for recording over network only to host device)
2c. Make the footage root folder "/data/footage" writable for everyone.

3. Make editable eyesis4pi-393-gui/settings.xml for the webserver
   $ chmod 777 settings.xml
   This file restores the settings from previous session.


  • php5.6-xml
~$ sudo apt install php5.6-xml
~$ sudo service restart apache2


  • Eyesis4Pi 393
  • External SSD enclosure
  • Switch
  • PC / Laptop

Power On

  • Connect all cables - power, network, eSATA.
  • Power on: switch, SSD enclosure, Eyesis4Pi393. Boot takes about 1 min.
  • Setup PC IP (can be done beforehand, see Network Setup below)
  • Refresh GUI after camera boots
Note: If GUI is refreshed before subcamera has mounted SSD it will not display SSD free space. Refresh in a few moments or until SSD gets mounted.
Note: Each subcamera's drive has 2 partitions:
      * /dev/sda1 - ext4 file system - used by the logger on the 1st subcamera (, and stored write info of the second partition
      * /dev/sda2 - no file system - images are written to the 'raw' partition for better speed. They are extracted later, using dd mostly
      In the GUI under SSD free space:
          * the 1st number - /dev/sda1
          * the 2nd number - /dev/sda2

Important Note: Use a fan to cool the camera's pole when shooting indoors.

GUI access
Live preview: opens in a new tab, can be refreshed during recording but a bit slow because of format conversion

Network Setup

  • Connect the PC to the Gigabit port of the switch.
  • Configure the PC's network settings:

IP address: (example)

Note: Eyesis4Pi 393 default IP addresses are


Test results output

Setting recording parameters: camera settings


  • Settings -> Camera-tab
Trigger period,ms  - 1/FPS, 250 = 4fps, 500 = 2fps, 1000 = 1fps...
HDRVexpos - not used.
Manual Exposure - used when auto exposure is off.
AutoExp max, ms - the autoexposure value limit.
AutoExp level - value of a pixel at which the autoexposure works.
AutoExp fracpix - number of pixels below the Autoexp level.
AutoExp frame ahead - number of previous frames used for calculatin the current frame exposure.
HDR mode - not used
Compression quality - JP4/JPEG compression quality.
  • Settings -> Other-tab
Displays temperatures
External - switch to external SSD (wait ~30s then click Refresh button and refresh the whole page - note the free space data)
Internal - switch to internal SSD (wait ~30s then click Refresh button and refresh the whole page - note the free space data)
Refresh - refreshes the recorder program write pointer (raw partition) - is needed mostly if the GUI was loaded before SSD was detected.
Reset - the system stores write pointer on an SSD, reset sets the write pointer back to the beginning of the raw partiiton
Reboot - system reboot
Eyesis4pi393gui tab camera.png
Eyesis4pi393gui tab other.png

Minimum setup example

  1. Trigger period = 250 - hit APPLY (below AutoExp frame ahead)
  2. Compression quality = 96 - edit or use +/-, the value is applied on change
  3. Start recording


  • Record-button to start recording


  • Stop-button for stop.


Error 5 (frame buffer overflow)

  • Frame buffer overflow counter ( = dropped frames).
  • Possible causes:
    • Not enough bandwidth - FPS and compression quality (combined) set too high: 5fps + 100%
    • SSD write speed is slowed
Buffer overflow errors
  • Errors are displayed as err5(N) against each buffer, where N is a cumulative number of errors