https://wiki.elphel.com/api.php?action=feedcontributions&feedformat=atom&user=DimitriosElphelWiki - User contributions [en]2026-05-12T11:03:04ZUser contributionsMediaWiki 1.28.0https://wiki.elphel.com/index.php?title=Imgsrv&diff=11270Imgsrv2012-02-17T01:49:40Z<p>Dimitrios: Updated imgsrv commands according to the imgsrv help page</p>
<hr />
<div>== [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/web/imgsrv/imgsrv.c?view=markup imgsrv] - Simple and fast HTTP server to provide still images and metadata acquired by the camera ==<br />
<br />
=== Overview ===<br />
This server was developed to increase the transfer rate of individual images acquired by the Elphel 353 series cameras as the CGI (and even fastCGI applications) connected through the universal web servers ([http://www.boa.org Boa], included with Axis SDK, currently on the default port 80 in camera and [http://www.lighttpd.net/ lighttpd] - now used in Elphel cameras together with php in fast CGI mode, port 81) failed to reach the top speed of the 100mbps network. Specialized imgsrv is connected through a different port (currently listens to 8081) and writes GET responses directly to the socket (reading image data from the [[Circbuf|circbuf]] using zero-copy memory mapping mmap), reaching 9-10MB/sec - virtually the full bandwidth of the network. '''This server does not provide any control over the sensor or FPGA compressor operation, its only purpose is to get data acquired to the (currently 19 MB) circular buffer in the system RAM'''. It is intended to have the functionality similar to the camera video streamers that also deal with the data already being acquired to the system buffer to be used when individual images are needed rather than the continuous video stream .<br />
<br />
The imgsrv makes use of the new functionality of the [[Circbuf|/dev/circbuf]] driver providing it with a convenient web front end. It serves JPEG images (with Exif data attached) as well as metadata and [[Circbuf|circbuf]] status formatting output as the xml files.<br />
<br />
=== imgsrv usage ===<br />
<br />
imgsrv listens to the camera http port (currently 8081) and parses the rest of the url string as a series of commands, i.e.:<br />
<nowiki>http://<camera_ip>:8081/towp/save</nowiki> <br />
<nowiki>http://<camera_ip>:8081/torp/wait/img/next/save</nowiki> <br />
<br />
The above command will be interpreted as the following sequences:<br />
<br />
First command (needed once):<br />
#set the current image pointer after the last image acquired;<br />
#save the pointer to the "global" (shared by all applications that use it) image pointer<br />
<br />
Second command (to be repeated for each image to be transfered):<br />
#set the current image pointer to the global read pointer stored in the driver;<br />
#wait for the image at that pointer to become available (it is possible that no waiting will actually take place if the image acquisition is ahead of the reading images out process. As far as the image readout process does not fall behind too far (by the size of the circbuf) it is OK.<br />
#transfer compressed image to the client<br />
#advance frame pointer to the next one<br />
#and finally - save the new pointer to the global read pointer, so that the same url can be used over and over each time providing the next acquired image<br />
<br />
If issued with empty arguments (just <nowiki>http://<camera_ip>:8081/</nowiki> ) imgsrv outputs a text file with the list of the valid commands.<br />
<br />
Commands are separated from the server url and from each other by the slashes ("/"), "?" and "&" also work. Each command is interpreted sequentially, from the left to the right. The /dev/circbuf file stays open for all the command sequence, so local image pointer stays valid from one command to the other.<br />
<br />
First group of the commands generates response data sent to the client, they are mutually exclusive and can appear only once in the command line (url). Each subsequent instances of such commands will be ignored. If none of the response-generating commands appear in the URL (but the url is not empty) the server will generate a minimalistic response - 1x1 pixel image. The commands of that group are the following:<br />
<br />
*'''img''' - send image at the current pointer (if it is the first command - use last acquired image - implied '''last''' command), if no image is available and the current pointer server will not wait for the image to be acquired (see '''wait ''' below) but rather immediately return 1x1 GIF image to the client;<br />
*'''bimg''' -same as above, but the whole image is stored in the camera outside of the circbuf before being sent to the client. It makes it safe from being overwritten by the new frames acquired by the camera. This option is useful when the camera is accessed from outside of the fast LAN over the slow network, it is safer and is recommended if the full frame rate is not required;<br />
*'''simg''', '''sbimg''' - similar to img, bimg but will imemdiately suggest to save instead of opening image in the browser<br />
*'''mimg[n]''' - send images as a multipart JPEG (all commands after will be ignored), possible to specify optional fps reduction i.e. mimg4 - skip 3 frames for each frame output (1/4 fps) <br />
*'''bmimg[n]''' - same as above, buffered<br />
*'''meta''' - send XML-formated metadata of the current frame instead of the image;<br />
*'''pointers''' - send XML-formatted data about the circbuf frame pointers.<br />
*'''frame''' - return current frame number as plain text<br />
*'''wframe''' - wait for the next frame sync, return current frame number as plain text<br />
<br />
Next commands are designed on top of [[Circbuf|circbuf]] control commands:<br />
*'''torp''' - set frame pointer to the global read pointer, maintained by the camera driver. If frame at that pointer is invalid (i.e. overran by the next images), the '''scnd''' command (see below) is used instead;<br />
*'''towp''' - set frame pointer to hardware write pointer - position where next frame will be acquired;<br />
*'''prev''' - move to previous frame in buffer, nop if none are available;<br />
*'''next''' - move to the next frame in the buffer. Pointer will not go beyond write pointer that defines where the next frame will be acquired;<br />
*'''last''' - move to the most recently acquired frame, or to write pointer if there are none already acquiured. This command is automatically executed each time the imgsrv is called with a new line;<br />
*'''first''' - move to the oldest frame still available in the buffer. It is not safe to rely on it if more frames are expected - data might be overwritten at any moment and the output image/meta data will be corrupted;<br />
*'''second''' - move to the second oldest frame in the buffer - somewhat safer than the 'first' - there will be time for the "next" command at least before frame data (and pointer structures) will be overwritten;<br />
*'''save''' - save the current frame pointer as a global read pointer that holds it values between the server requests. This pointer is shared between all the clients and applications that use it;<br />
*'''wait''' - Delay execution until there will be a frame at the current pointer ready.<br />
<br />
=== imgsrv and Exif data ===<br />
<br />
imgsrv supports Exif format and includes frame metadata in the image header. The Exif headers are generated in several steps.<br />
*First, the Exif template (''/var/state/exif.template'') file is generated by the [[Exif_init.php|Exif_init.php]] script (during the system start up). The template generated is a binary file that is a valid Exif header itself. This script provides the "static" data (data that does not change between the frames), it also includes specific data that the script collects from various parts of the camera and camera software (like current firmware file name). Finally it provides a place holders for dynamic frame data to be replaced by the actual values by the imgsrv server;<br />
*Next step happens during initialization of the imgsrv. At that time the ''/var/state/exif.template'' is read in, parsed and the pointers to the Exif data that imgsrv is aware of are stored in as internal list together with the maximal string lengths that imgsrv may use.<br />
*Last step - imgsrv reads current frames meta data and uses it to fill the Exif fields at the pointers.<br />
You may find documentation about Exif tags in [http://www.exiv2.org/tags.html Exif tags] or download an official [http://www.exif.org/Exif2-2.PDF Exif2-2.PDF]<br />
The fields that are currently updated by imgsrv are the following (all the other fields are preserved as they are generated by the [[Exif_init.php|Exif_init.php]]):<br />
<br />
{| border="1" cellpadding="2"<br />
|-<br />
| Tag || IFD || Key || Type|| Description<br />
|-<br />
|0x0132||IFD0 ||DateTime||ASCII||Date/time of the image last modified. This field is likely to be modified later by image-processing software<br />
|-<br />
|0x9003||IFD1 ||DateTimeOriginal||ASCII||Date/time of the image acquisition. Here - start of the frame readout (or start of the exposure where applicable)<br />
|-<br />
|0x9291||IFD1 ||SubSecTimeOriginal||ASCII||Fractional seconds (digits after the decimal point) to be added to DateTimeOriginal field, 6 digits<br />
|-<br />
|0x829a||IFD1 ||ExposureTime||RATIONAL|| This field consists of 2 unsigned shorts that make exposure time (in seconds) as a rational number (the nominator divided by the denominator). With the current software denominator is a constant of 10000, imgsrv only updates the nominato<br />
|-<br />
|0x927c||IFD1 ||MakerNote||BYTE|| This custom field is defined in the camera as 36 bytes, they are filled with raw frame metadata - structure ''frame_params_t'' defined in [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/include/asm-cris/elphel/c313a.h?view=markup include/asm-cris/elphel/c313a.h]. Bytes go in CPU order, so the data is little-endian (the rest is big-endian)<br />
<br />
|-<br />
|}</div>Dimitrioshttps://wiki.elphel.com/index.php?title=Elphel_Software_Kit_for_Ubuntu&diff=11267Elphel Software Kit for Ubuntu2012-02-11T15:25:09Z<p>Dimitrios: Fixed typo for ppa</p>
<hr />
<div>=About=<br />
<br />
This page is a simple howto for running Elphel software on (K)Ubuntu GNU/Linux.<br />
<br />
You can download this GNU/Linux distribution freely from http://www.kubuntu.org/<br />
<br />
A Live ISO image with almost all the packages pre-installed (except [[Elphel_Software_Kit_for_Ubuntu#Installation_of_the_source_code_of_Elphel_camera_software|Elphel camera source]] code and [[Elphel_Software_Kit_for_Ubuntu#Installing_Xilinx_WebPack_.28to_be_moved_to_a_separate_page.2C_just_a_link_here.29|Xilinx ISE WebPack]]) is available for downloading from [http://community.elphel.com/files/live-dvd/ here].<br />
<br />
=If you are new to GNU / Linux=<br />
Many forums and wikis are available in many languages to help you to install and use Ubuntu. Ex: http://www.google.com/search?q=forum+ubuntu (you can add "&hl=fr" or any language code to the URL)<br />
<br />
Most instructions below are commands that you need to enter in the in the terminal window. For the lines that do not end with "\" sign you just copy them one-by-one and paste in the terminal window (in KDE it is Konsole in the "System" menu). For pasting you '''can not''' use <cntrl-V> - you need to '''right-click in the terminal window and select "Paste"''' from the drop-down context menu. Alternatively you can use '''the middle mouse button''' to both copy (drag while middle mouse pressed) and paste - click it in the console window.<br />
<br />
Character "'''\'''" at the end of the line means continuation, so you can copy the whole block of text where each line but the very last ends with "\" and paste them together.<br />
<br />
Many of the commands start with "'''sudo'''" - first time system will ask you for your user password that you enter without any starts (provided you have administrative privileges).<br />
<br />
If you get some problems it is very useful to copy the error message that system outputs (avoiding anything specific to your particular installation - like user directories names) and paste them into the search box of you browser.<br />
<br />
=User software=<br />
<br />
Some software need to be patched and recompiled even if they exist in Ubuntu software repositories, some softwares are not yet packaged in Ubuntu, so you have to compile them from sources also. We try to push our software patches to the mainstream applications, but it take time and is not always possible. For Ubuntu users some packages can be downloaded and upgraded using our [https://launchpad.net/~elphel/+archive/ppa ppa on launchpad].<br />
<br />
sudo add-apt-repository ppa:elphel/ppa<br />
sudo apt-get update<br />
<br />
==Mplayer - Ubuntu 9.10 or later==<br />
'''Kubuntu 9.10 includes MPlayer that is working with Elphel camera "out of the box"'''<br />
So for (K)Ubuntu 9.10 you just need to install<br />
sudo apt-get install mplayer-nogui mplayer gecko-mediaplayer<br />
<br />
===Mplayer - installation for (K)Ubuntu older than 9.10 release ===<br />
<br />
With the previous verions MPlayer has to be patched and recompiled, following instructions document how to do it on (K)Ubuntu or Debian based workstation.<br />
<br />
Install gecko-mediaplayer before compiling/installing MPlayer, if you do it later it will install non-patched version of MPlayer<br />
<br />
sudo apt-get install gecko-mediaplayer<br />
<br />
<br />
First install some compilation dependencies, mainly libraries...<br />
<br />
<!-- sudo apt-get install build-essential debhelper libncurses5-dev libesd0-dev liblircclient-dev libgtk2.0-dev \<br />
libvorbis-dev libsdl1.2-dev sharutils libasound2-dev liblzo-dev gawk libjpeg62-dev libaudiofile-dev \<br />
libsmbclient-dev libxv-dev libpng3-dev libgif-dev libcdparanoia0-dev libxvidcore4-dev libdv-dev \<br />
liblivemedia-dev libfreetype6-dev em8300-headers libgl1-mesa-dev libdvdread-dev libdts-dev libtheora-dev \<br />
libglu-dev libartsc0-dev libfontconfig-dev libxxf86dga-dev libxinerama-dev libxxf86vm-dev \<br />
libxvmc-dev libggi2-dev libmpcdec-dev libspeex-dev libfribidi-dev libfaac-dev libaa1-dev libcaca-dev \<br />
libx264-dev libpulse-dev libmad0-dev ladspa-sdk libdbus-glib-1-dev libaudio-dev liblzo2-dev libdvdnav-dev \<br />
libopenal-dev libjack-dev libtwolame-dev libsvga1-dev libenca-dev libmp3lame-dev<br />
<br />
'''If you are under Ubuntu 8.10 (Intrepid) replace liblame-dev at the end by libmp3lame-dev''' --><br />
<br />
sudo apt-get install build-essential debhelper libncurses5-dev libesd0-dev liblircclient-dev libgtk2.0-dev \<br />
libvorbis-dev libsdl1.2-dev sharutils libasound2-dev gawk libjpeg62-dev libaudiofile-dev \<br />
libsmbclient-dev libxv-dev libpng12-dev libgif-dev libcdparanoia-dev libdv4-dev \<br />
liblivemedia-dev libfreetype6-dev libgl1-mesa-dev libdvdread-dev libdts-dev libtheora-dev \<br />
libglu1-mesa-dev libfontconfig-dev libxxf86dga-dev libxinerama-dev libxxf86vm-dev \<br />
libxvmc-dev libggi2-dev libmpcdec-dev libspeex-dev libfribidi-dev libfaac-dev libaa1-dev libcaca-dev \<br />
libx264-dev libpulse-dev libmad0-dev ladspa-sdk libdbus-glib-1-dev libaudio-dev liblzo2-dev libdvdnav-dev \<br />
libopenal-dev libjack-dev libtwolame-dev libsvga1-dev libenca-dev libmp3lame-dev<br />
<br />
<br />
<!--<br />
Get the MPlayer ubuntu source package:<br />
apt-get source mplayer<br />
<br />
patch the sources and compile:<br />
cd mplayer-1.0~rc2/<br />
sed s/\#define\ MAX_RTP_FRAME_SIZE\ 50000/\#define\ MAX_RTP_FRAME_SIZE\ 5000000/g \<br />
libmpdemux/demux_rtp.cpp > libmpdemux/demux_rtp.cpp_<br />
mv libmpdemux/demux_rtp.cpp_ libmpdemux/demux_rtp.cpp<br />
sudo dpkg-buildpackage <br />
cd ..<br />
<br />
install mplayer package:<br />
sudo dpkg --install mplayer_1.0~rc2-0ubuntu*.deb<br />
--><br />
Current MPlayer code is capable of working with full resolution video produced by Elphel cameras. That is not yet true for the MPlayer packages in Ubuntu repositories, so you'll have to obtain the source code from MPlayer recommended source - their Subversion (SVN) source. First you need to install Subversion itself:<br />
sudo apt-get install subversion<br />
Now create a download directory and get MPlayer source:<br />
mkdir download; cd download<br />
svn checkout svn://svn.mplayerhq.hu/mplayer/trunk mplayer<br />
Configure, compile and prepare Debian package from that source (will take some time):<br />
cd mplayer<br />
sudo dpkg-buildpackage <br />
Occasionally dpkg-buildpackage fails to build, try the comon ./configure, make, make install way then.<br />
<br />
Now uninstall the default Ubuntu's mplayer and mencoder & install the created package:<br />
sudo apt-get remove mplayer mencoder mplayer-nogui<br />
cd ..<br />
sudo dpkg --install mplayer_1.0svn*.deb<br />
<br />
===MPlayer - testing with Elphel camera ===<br />
You should be able now to play videos with up to 5MB frames (highest quality 5MPix images are around 1 MB) as a multicast or unicast video stream. (the streamer in the camera should be ENABLED)<br />
mplayer rtsp://192.168.0.9:554 -vo x11 -fs -zoom<br />
<br />
''Update 10/09/2009: In (K)Ubuntu 9.10 (Karmic Koala) repository the '''50,000 bytes limit on the frame size''' is fixed, but unfortunately the [https://bugs.launchpad.net/ubuntu/+source/mplayer/+bug/296488 other one -'''frame width limit of 2048 pixels'''] (submitted to MPlayer SVN on May, 5, 2009) - is not''--[[User:Andrey.filippov|Andrey.filippov]] 19:03, 9 October 2009 (CDT)<br />
<br />
The first (50,000) makes you picture break after the first 50,000 bytes (only top is shown), the second (current for the 9.10) makes MPlayer to report fatal error. So you still have to use MPlayer SVN to have the full resolution from Elphel cameras.<br />
<br />
Additionally, to make MPlayer work inside the web page you need to specify video output as "x11" in the [http://howto.wikia.com/wiki/Howto_configure_MPlayer MPlayer config file] - add a line<br />
vo="x11"<br />
To ~/.mplayer/config file<br />
<br />
=For developers=<br />
''Following was written for (K)Ubuntu 9.10 and earlier, it also works with 10.04, please see revision-specific notes.''<br />
<br />
==Adding universe and multiverse sources==<br />
Please follow this howto for adding universe and multiverse sources. <br />
<br />
https://help.ubuntu.com/community/Repositories/Ubuntu<br />
<br />
or <br />
<br />
https://help.ubuntu.com/community/Repositories/Kubuntu<br />
<br />
==Install needed packages==<br />
Minimal packages:<br />
sudo apt-get install cvs build-essential autoconf flex byacc bison libglib2.0-dev tcl gettext libncurses5-dev patch zlib1g-dev nfs-kernel-server bash xutils-dev<br />
Suggested packages:<br />
sudo apt-get install kinfocenter minicom firefox graphviz doxygen ctags cervisia php5 php5-cli xchat ssh kompare git-core<br />
<br />
==Configure your NFS server==<br />
<br />
Let's say you want to configure an NFS server on your machine and your IP address is '''192.168.0.15'''.<br />
<br />
<!--Edit /etc/exports file with your favorite editor. Here I use nano.<br />
sudo nano -w /etc/exports<br />
alternatively you may edit the same file with kate<br />
Those who know how to use nano will figure that out themselves --[[User:Andrey.filippov|Andrey.filippov]] 18:09, 23 May 2009 (CDT)<br />
--><br />
Modify the configuration file:<br />
kdesudo kate /etc/exports<br />
Add at the end of the file:<br />
/nfs 192.168.0.0/255.255.0.0(rw,sync,no_root_squash)<br />
save the file.<br />
<br />
If it does not yet exist make /nfs directory and make it world writable to make it possible to write logs from the camera.<br />
sudo mkdir /nfs<br />
sudo chmod 777 -R /nfs<br />
<br />
And finally export the filesystem.<br />
sudo exportfs -a<br />
<br />
<br />
== Installation of GCC Compiler kit for Axis ETRAX processor ==<br />
=== Automatic Installation ((K)Ubuntu 11.04 Natty Narwhal)===<br />
1. <br />
sudo add-apt-repository ppa:elphel/ppa<br />
<br />
(The line above is equivalent to adding the following lines to your sources.list ('''sudo kate /etc/apt/sources.list''')):<br />
deb http://ppa.launchpad.net/elphel/ppa/ubuntu natty main <br />
deb-src http://ppa.launchpad.net/elphel/ppa/ubuntu natty main <br />
<br />
2.<br />
sudo apt-get update<br />
sudo apt-get install cris-dist<br />
<br />
<br />
=== Manual Installation ===<br />
====Downloading and unpacking gcc-cris====<br />
Download and install Cris-GCC compiler. It is needed to compile C and C++ programs for the CPU used in Elphel cameras - [http://en.wikipedia.org/wiki/ETRAX_CRIS Axis ETRAX FS] :<br />
mkdir -p ~/Downloads/axis ; cd ~/Downloads/axis<br />
wget http://www.axis.com/ftp/pub/axis/tools/cris/compiler-kit/cris-dist-linux-headers-1.64.tar.gz <br />
wget http://www.axis.com/ftp/pub/axis/tools/cris/compiler-kit/cris-dist-linux-headersv32-1.64.tar.gz <br />
wget http://www.axis.com/ftp/pub/axis/tools/cris/compiler-kit/cris-dist-glibc-1.64.tar.gz <br />
wget http://www.axis.com/ftp/pub/axis/tools/cris/compiler-kit/cris-dist-1.64.tar.gz<br />
wget http://www.axis.com/ftp/pub/axis/tools/cris/compiler-kit/cris-dist-1.64-1--1.64-2.patch<br />
tar zxvf cris-dist-1.64.tar.gz<br />
cd cris-dist-1.64/<br />
tar zxvf ../cris-dist-linux-headers-1.64.tar.gz <br />
tar zxvf ../cris-dist-linux-headersv32-1.64.tar.gz <br />
tar zxvf ../cris-dist-glibc-1.64.tar.gz<br />
patch -p0 < ../cris-dist-1.64-1--1.64-2.patch<br />
<br />
==== Compiling gcc-cris ====<br />
Now you may proceed with compiling gcc-cris (takes some time):<br />
<br />
sudo ./install-cris-tools<br />
answer by default (enter, enter, ...)<br />
<br />
<!--<br />
Don't forget to export the path to the cris-compiler - the defaul location is /usr/local/cris, as example<br />
<br />
tobias@MoonbaseAlphaOne:~$ export PATH=$PATH:/usr/local/cris/bin<br />
<br />
If everything worked out well, you can check the compiler version with<br />
<br />
gcc-cris --version<br />
<br />
Which should result in an output like this one (example, might vary with version)<br />
<br />
cris-axis-elf-gcc (GCC) 3.2.1 Axis release R64/1.64<br />
Copyright (C) 2002 Free Software Foundation, Inc.<br />
This is free software; see the source for copying conditions. There is NO<br />
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.<br />
--><br />
<br />
== Build Elphel Software==<br />
Get the [http://sourceforge.net/projects/elphel/files/elphel353-8/install-8.0-fromcvs/elphel353_80_install_from_cvs.sh.tar.gz/download script]. Unpack & Launch.<br />
<br />
<br />
== Installation of Kdevelop 3.5 ==<br />
''note: Newer KDevelop 4 does not work with Elphel software''<br />
==== pre (K)Ubuntu 9.10 ====<br />
sudo apt-get install kdevelop<br />
<br />
==== (K)Ubuntu 9.10 (Karmic), 10.4 (Lucid) ====<br />
see [[KDevelop#Installation_of_KDevelop_3.5_on_.28K.29Ubuntu_9.10|Installation of KDevelop 3.5 on (K)Ubuntu 9.10]]<br />
<br />
== Install Icarus Verilog and GTKWave ==<br />
(If you plan to develop FPGA code or at least look how it works)<br />
<br />
GTKWave is OK from repository:<br />
sudo apt-get install gtkwave<br />
<br />
But unfortunately Icarus Verilog (package verilog) is compiled without needed support for compressed output format, so you'll have to compile it<br />
cd ~/Downloads<br />
wget "ftp://ftp.icarus.com/pub/eda/verilog/v0.9/verilog-0.9.3.tar.gz"<br />
tar zxvf verilog-0.9.3.tar.gz<br />
cd verilog-0.9.3/<br />
./configure<br />
make<br />
sudo make install<br />
<br />
== Installing Xilinx WebPack (to be moved to a separate page, just a link here)==<br />
If you plan to compile the FPGA code from the source code you will need to install appropriate software from the FPGA manufacturer web site. This is proprietary (and non-free) software provided by [http://www.xilinx.com Xilinx] free of charge. This software is called the [http://www.xilinx.com/tools/webpack.htm ISE WebPACK] and you may download it (currently some 2.2GB) after registering at Xilinx web site. Currently tested version is 10.1.03, we'll try to update our code when Xilinx will release the new version of their software.<br />
<br />
You will also need that software if you would like to simulate the FPGA functionality. Elphel camera FPGA code (written in Verilog HDL) is licensed under GNU GPLv3, simulator and waveform viewer (see below) are also Free Software, but there are a few Verilog models of some primitives of Xilinx FPGA that are not and can be only obtained from Xilinx as a part of their unisims library. For simulation we use small subset of the unisims library components and only for functional simulation so it will probably make sense to re-write those primitives models so the 2.2 GB distribution will not be needed to extract just few kilobytes of required source code.<br />
<br />
Such independent re-implementation will help us to solve another problem - we have to patch the Xilinx library components to make them work correctly with our code and the simulator we use and currently each Xilinx library update breaks our patches.<br />
<br />
When you will build Elphel software (as described later) the installation script will try to locate Xilinx software on your computer and patch a copy of unisims library. If you'll install Xilinx WebPack after building the camera software - you'll need to navigate to ''fpga'' subdirectory of the source tree and execute<br />
make clean ; make<br />
It is described in file ''README.simulation'' in that subdirectory.<br />
<br />
<br />
There are additional steps required for the Xilinx WebPACK installation if you have a 64-bit GNU/Linux operation system. The next command line detects if you are running on 64 bit version of GNU/Linux and conditionally installs '''ia64-libs'''. That library is needed if you'll install Xilinx WebPack software (Xilinx does not allow to use 64-bit programs in their free for download software and the provided installation script does not install 32-bit version on its own). There is [http://ubuntuforums.org/showthread.php?t=203459 another trick] you'll need to be aware of if you are using 32-bit Xilinx WebPack on a 64-bit GNU/Linux system.<br />
if [ `uname -m` = "x86_64" ] ; then sudo apt-get install ia32-libs ; fi<br />
<br />
==Installation of the source code of Elphel camera software==<br />
<br />
You may install Elphel source code by either of the two methods. Either from the CVS (the most current code) and form the tarball files. <br />
===Installation from the CVS===<br />
<br />
Get [http://downloads.sourceforge.net/elphel/elphel353_80_install_from_cvs.sh.tar.gz elphel353_80_install_from_cvs.sh] open archive that contains the shell script and execute it. It is recommended that you create subdirectory in your home directory, i.e. "elphel_projects", move and execute elphel353_80_install_from_cvs.sh script there. Directory "distfiles" will be created there and used as a cache for software archives that will be downloaded during installation.<br />
<br />
mkdir -p ~/elphel_projects; cd ~/elphel_projects<br />
wget "http://downloads.sourceforge.net/elphel/elphel353_80_install_from_cvs.sh.tar.gz"<br />
tar zxvf elphel353_80_install_from_cvs.sh.tar.gz<br />
./elphel353_80_install_from_cvs.sh<br />
<br />
===Installation from the tarball (release file)===<br />
http://sourceforge.net/projects/elphel<br />
<br />
* get one of the elphel353-8.0.* releases<br />
* decompress the archive<br />
* execute the ./install_elphel script<br />
./install_elphel<br />
<br />
There will be created a file build.log in the top installation directory. If you get any installation problems you can compress that file and email it to Elphel support.<br />
<br />
At the end of installation the script will generate a list of all the files in the target (camera) file system that are to be installed and compares it against the contents of the file ''target.list'' that is included in the distribution. If there are any differences -- they will be reported (there should be none). If there are some missing files it is likely that something failed to install correctly.<br />
<br />
After the installation will be completed successfully you may want to execute the following command in the top installation directory (the one that has apps, configure-files, ... subdirectories)<br />
./prep_kdevelop.php<br />
<br />
That will create ''elphel353.kdevelop'' - a project file for KDevelop IDE (version 3.5.x), you can use it as described here - [[KDevelop]]<br />
<br />
<br />
----<br />
<br />
== ImageJ and Elphel plugins for imageJ ==<br />
ImageJ is a powerful open source image processing package, written in Java. There are plugins to work with Elphel cameras, the most universal one allows opening JP46 files (stored on a file system or downloaded directly from the camera). This plugin reads meta data from the image and un-applies in-camera non-linear conversion resulting in the linearized image, where each pixel is represented by a floating point value proportional to the number of photons that were detected in that pixel.<br />
<br />
It is a very useful tool to do quantitative analysis of the camera images.<br />
<br />
===ImageJ installation ===<br />
You may download ImageJ bundled with Java from the [http://rsbweb.nih.gov/ij/download.html download page]:<br />
==== With 32-bit Java ==== <br />
cd ~/Download; wget "http://rsbweb.nih.gov/ij/download/linux/ij143-x86.tar.gz" ; tar zxvf ij143-x86.tar.gz<br />
==== With 64-bit Java ====<br />
cd ~/Download; wget "http://rsbweb.nih.gov/ij/download/linux/ij143-linux64.tar.gz" ; tar zxvf ij143-linux64.tar.gz<br />
http://rsbweb.nih.gov/ij/download/linux/ij143-linux64.tar.gz - 64-bit Java version<br />
===Running ImageJ ===<br />
There is "run" command the newly crated directory. You may start ImageJ with the following command:<br />
/Downloads/ImageJ/run<br />
That command allows Java to use 512M of system memory. If you need more you can change "512" to say "1024" in a single-line "run" script. If the run command is started from the command prompt, you'll be able to see some debug output - either from existent plugins or from your own ones. It is also very useful to see any error diagnostic output.<br />
<br />
=== Installation of Elphel plugins for ImageJ ===<br />
Elphel plugins are available in Elphel project page Git repository. To use it you first need to install git (if it was not already done):<br />
sudo apt-get install git-core<br />
<br />
Then clone the repository - directly to the ImageJ plugins directory. Provided you used the same directory for ImageJ as written above:<br />
cd ~/Downloads/ImageJ/plugins<br />
git clone git://elphel.git.sourceforge.net/gitroot/elphel/ImageJ-Elphel<br />
<br />
=== Updating Elphel plugins for ImageJ ===<br />
Later, when you'll need to update your files from the repository you will need another command:<br />
cd ~/Downloads/ImageJ/plugins/ImageJ-Elphel<br />
git pull<br />
=== Running Elphel plugin for ImageJ ===<br />
When you just install Elphel plugins you need to select<br />
~/Downloads/ImageJ/plugins/ImageJ-Elphel/JP46_Reader_camera.java<br />
That command will do exactly as it is named - first compile that source file to the Java bytecode, then execute it. Next time after you close and re-start ImageJ there will be a submenu in Plugins: Plugins->ImageJ-Elphel and JP46_Reader_camera command there,<br />
<br />
When you'll update the source files, you 'll need to re-run "Compile and run...". meanwhile just use the item in Plugins->ImageJ-Elphel menu.</div>Dimitrioshttps://wiki.elphel.com/index.php?title=Imgsrv&diff=11266Imgsrv2012-02-11T01:13:11Z<p>Dimitrios: </p>
<hr />
<div>== [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/web/imgsrv/imgsrv.c?view=markup imgsrv] - Simple and fast HTTP server to provide still images and metadata acquired by the camera ==<br />
<br />
=== Overview ===<br />
This server was developed to increase the transfer rate of individual images acquired by the Elphel 353 series cameras as the CGI (and even fastCGI applications) connected through the universal web servers ([http://www.boa.org Boa], included with Axis SDK, currently on the default port 80 in camera and [http://www.lighttpd.net/ lighttpd] - now used in Elphel cameras together with php in fast CGI mode, port 81) failed to reach the top speed of the 100mbps network. Specialized imgsrv is connected through a different port (currently listens to 8081) and writes GET responses directly to the socket (reading image data from the [[Circbuf|circbuf]] using zero-copy memory mapping mmap), reaching 9-10MB/sec - virtually the full bandwidth of the network. '''This server does not provide any control over the sensor or FPGA compressor operation, its only purpose is to get data acquired to the (currently 19 MB) circular buffer in the system RAM'''. It is intended to have the functionality similar to the camera video streamers that also deal with the data already being acquired to the system buffer to be used when individual images are needed rather than the continuous video stream .<br />
<br />
The imgsrv makes use of the new functionality of the [[Circbuf|/dev/circbuf]] driver providing it with a convenient web front end. It serves JPEG images (with Exif data attached) as well as metadata and [[Circbuf|circbuf]] status formatting output as the xml files.<br />
<br />
=== imgsrv usage ===<br />
<br />
imgsrv listens to the camera http port (currently 8081) and parses the rest of the url string as a series of commands, i.e.:<br />
<nowiki>http://<camera_ip>:8081/towp/save</nowiki> <br />
<nowiki>http://<camera_ip>:8081/torp/wait/img/next/save</nowiki> <br />
<br />
The above command will be interpreted as the following sequences:<br />
<br />
First command (needed once):<br />
#set the current image pointer after the last image acquired;<br />
#save the pointer to the "global" (shared by all applications that use it) image pointer<br />
<br />
Second command (to be repeated for each image to be transfered):<br />
#set the current image pointer to the global read pointer stored in the driver;<br />
#wait for the image at that pointer to become available (it is possible that no waiting will actually take place if the image acquisition is ahead of the reading images out process. As far as the image readout process does not fall behind too far (by the size of the circbuf) it is OK.<br />
#transfer compressed image to the client<br />
#advance frame pointer to the next one<br />
#and finally - save the new pointer to the global read pointer, so that the same url can be used over and over each time providing the next acquired image<br />
<br />
If issued with empty arguments (just <nowiki>http://<camera_ip>:8081/</nowiki> ) imgsrv outputs a text file with the list of the valid commands.<br />
<br />
Commands are separated from the server url and from each other by the slashes ("/"), "?" and "&" also work. Each command is interpreted sequentially, from the left to the right. The /dev/circbuf file stays open for all the command sequence, so local image pointer stays valid from one command to the other.<br />
<br />
First group of the commands generates response data sent to the client, they are mutually exclusive and can appear only once in the command line (url). Each subsequent instances of such commands will be ignored. If none of the response-generating commands appear in the URL (but the url is not empty) the server will generate a minimalistic response - 1x1 pixel image. The commands of that group are the following:<br />
<br />
*'''img''' - send image at the current pointer (if it is the first command - use last acquired image - implied '''last''' command), if no image is available and the current pointer server will not wait for the image to be acquired (see '''wait ''' below) but rather immediately return 1x1 GIF image to the client;<br />
*'''bimg''' -same as above, but the whole image is stored in the camera outside of the circbuf before being sent to the client. It makes it safe from being overwritten by the new frames acquired by the camera. This option is useful when the camera is accessed from outside of the fast LAN over the slow network, it is safer and is recommended if the full frame rate is not required;<br />
*'''mimg''' - send a stream of images at the current pointer as MJPEG (HTTP header, ''Content-type: multipart/x-mixed-replace''); like '''img''' but for an MJPEG stream.<br />
*'''mbimg''' - same as above, but the images are stored in the camera outside of the circbuf before being sent to the client.<br />
*'''meta''' - send XML-formated metadata of the current frame instead of the image;<br />
*'''pointers''' - send XML-formatted data about the circbuf frame pointers.<br />
<br />
Next commands are designed on top of [[Circbuf|circbuf]] control commands:<br />
*'''torp''' - set frame pointer to the global read pointer, maintained by the camera driver. If frame at that pointer is invalid (i.e. overran by the next images), the '''scnd''' command (see below) is used instead;<br />
*'''towp''' - set frame pointer to hardware write pointer - position where next frame will be acquired;<br />
*'''prev''' - move to previous frame in buffer, nop if none are available;<br />
*'''next''' - move to the next frame in the buffer. Pointer will not go beyond write pointer that defines where the next frame will be acquired;<br />
*'''last''' - move to the most recently acquired frame, or to write pointer if there are none already acquiured. This command is automatically executed each time the imgsrv is called with a new line;<br />
*'''first''' - move to the oldest frame still available in the buffer. It is not safe to rely on it if more frames are expected - data might be overwritten at any moment and the output image/meta data will be corrupted;<br />
*'''second''' - move to the second oldest frame in the buffer - somewhat safer than the 'first' - there will be time for the "next" command at least before frame data (and pointer structures) will be overwritten;<br />
*'''save''' - save the current frame pointer as a global read pointer that holds it values between the server requests. This pointer is shared between all the clients and applications that use it;<br />
*'''wait''' - Delay execution until there will be a frame at the current pointer ready.<br />
<br />
=== imgsrv and Exif data ===<br />
<br />
imgsrv supports Exif format and includes frame metadata in the image header. The Exif headers are generated in several steps.<br />
*First, the Exif template (''/var/state/exif.template'') file is generated by the [[Exif_init.php|Exif_init.php]] script (during the system start up). The template generated is a binary file that is a valid Exif header itself. This script provides the "static" data (data that does not change between the frames), it also includes specific data that the script collects from various parts of the camera and camera software (like current firmware file name). Finally it provides a place holders for dynamic frame data to be replaced by the actual values by the imgsrv server;<br />
*Next step happens during initialization of the imgsrv. At that time the ''/var/state/exif.template'' is read in, parsed and the pointers to the Exif data that imgsrv is aware of are stored in as internal list together with the maximal string lengths that imgsrv may use.<br />
*Last step - imgsrv reads current frames meta data and uses it to fill the Exif fields at the pointers.<br />
You may find documentation about Exif tags in [http://www.exiv2.org/tags.html Exif tags] or download an official [http://www.exif.org/Exif2-2.PDF Exif2-2.PDF]<br />
The fields that are currently updated by imgsrv are the following (all the other fields are preserved as they are generated by the [[Exif_init.php|Exif_init.php]]):<br />
<br />
{| border="1" cellpadding="2"<br />
|-<br />
| Tag || IFD || Key || Type|| Description<br />
|-<br />
|0x0132||IFD0 ||DateTime||ASCII||Date/time of the image last modified. This field is likely to be modified later by image-processing software<br />
|-<br />
|0x9003||IFD1 ||DateTimeOriginal||ASCII||Date/time of the image acquisition. Here - start of the frame readout (or start of the exposure where applicable)<br />
|-<br />
|0x9291||IFD1 ||SubSecTimeOriginal||ASCII||Fractional seconds (digits after the decimal point) to be added to DateTimeOriginal field, 6 digits<br />
|-<br />
|0x829a||IFD1 ||ExposureTime||RATIONAL|| This field consists of 2 unsigned shorts that make exposure time (in seconds) as a rational number (the nominator divided by the denominator). With the current software denominator is a constant of 10000, imgsrv only updates the nominato<br />
|-<br />
|0x927c||IFD1 ||MakerNote||BYTE|| This custom field is defined in the camera as 36 bytes, they are filled with raw frame metadata - structure ''frame_params_t'' defined in [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/include/asm-cris/elphel/c313a.h?view=markup include/asm-cris/elphel/c313a.h]. Bytes go in CPU order, so the data is little-endian (the rest is big-endian)<br />
<br />
|-<br />
|}</div>Dimitrioshttps://wiki.elphel.com/index.php?title=Imgsrv&diff=11265Imgsrv2012-02-11T01:10:33Z<p>Dimitrios: Added undocummented commands mimg and mbimg</p>
<hr />
<div>== [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/web/imgsrv/imgsrv.c?view=markup imgsrv] - Simple and fast HTTP server to provide still images and metadata acquired by the camera ==<br />
<br />
=== Overview ===<br />
This server was developed to increase the transfer rate of individual images acquired by the Elphel 353 series cameras as the CGI (and even fastCGI applications) connected through the universal web servers ([http://www.boa.org Boa], included with Axis SDK, currently on the default port 80 in camera and [http://www.lighttpd.net/ lighttpd] - now used in Elphel cameras together with php in fast CGI mode, port 81) failed to reach the top speed of the 100mbps network. Specialized imgsrv is connected through a different port (currently listens to 8081) and writes GET responses directly to the socket (reading image data from the [[Circbuf|circbuf]] using zero-copy memory mapping mmap), reaching 9-10MB/sec - virtually the full bandwidth of the network. '''This server does not provide any control over the sensor or FPGA compressor operation, its only purpose is to get data acquired to the (currently 19 MB) circular buffer in the system RAM'''. It is intended to have the functionality similar to the camera video streamers that also deal with the data already being acquired to the system buffer to be used when individual images are needed rather than the continuous video stream .<br />
<br />
The imgsrv makes use of the new functionality of the [[Circbuf|/dev/circbuf]] driver providing it with a convenient web front end. It serves JPEG images (with Exif data attached) as well as metadata and [[Circbuf|circbuf]] status formatting output as the xml files.<br />
<br />
=== imgsrv usage ===<br />
<br />
imgsrv listens to the camera http port (currently 8081) and parses the rest of the url string as a series of commands, i.e.:<br />
<nowiki>http://<camera_ip>:8081/towp/save</nowiki> <br />
<nowiki>http://<camera_ip>:8081/torp/wait/img/next/save</nowiki> <br />
<br />
The above command will be interpreted as the following sequences:<br />
<br />
First command (needed once):<br />
#set the current image pointer after the last image acquired;<br />
#save the pointer to the "global" (shared by all applications that use it) image pointer<br />
<br />
Second command (to be repeated for each image to be transfered):<br />
#set the current image pointer to the global read pointer stored in the driver;<br />
#wait for the image at that pointer to become available (it is possible that no waiting will actually take place if the image acquisition is ahead of the reading images out process. As far as the image readout process does not fall behind too far (by the size of the circbuf) it is OK.<br />
#transfer compressed image to the client<br />
#advance frame pointer to the next one<br />
#and finally - save the new pointer to the global read pointer, so that the same url can be used over and over each time providing the next acquired image<br />
<br />
If issued with empty arguments (just <nowiki>http://<camera_ip>:8081/</nowiki> ) imgsrv outputs a text file with the list of the valid commands.<br />
<br />
Commands are separated from the server url and from each other by the slashes ("/"), "?" and "&" also work. Each command is interpreted sequentially, from the left to the right. The /dev/circbuf file stays open for all the command sequence, so local image pointer stays valid from one command to the other.<br />
<br />
First group of the commands generates response data sent to the client, they are mutually exclusive and can appear only once in the command line (url). Each subsequent instances of such commands will be ignored. If none of the response-generating commands appear in the URL (but the url is not empty) the server will generate a minimalistic response - 1x1 pixel image. The commands of that group are the following:<br />
<br />
*'''img''' - send image at the current pointer (if it is the first command - use last acquired image - implied '''last''' command), if no image is available and the current pointer server will not wait for the image to be acquired (see '''wait ''' below) but rather immediately return 1x1 GIF image to the client;<br />
*'''bimg''' -same as above, but the whole image is stored in the camera outside of the circbuf before being sent to the client. It makes it safe from being overwritten by the new frames acquired by the camera. This option is useful when the camera is accessed from outside of the fast LAN over the slow network, it is safer and is recommended if the full frame rate is not required;<br />
*'''mimg''' - send a stream of images at the current pointer as MJPEG ('''Content-type: multipart/x-mixed-replace'''); like '''img''' but for an MJPEG stream.<br />
*'''mbimg''' - same as above, but the images are stored in the camera outside of the circbuf before being sent to the client. *'''meta''' - send XML-formated metadata of the current frame instead of the image;<br />
*'''pointers''' - send XML-formatted data about the circbuf frame pointers.<br />
<br />
Next commands are designed on top of [[Circbuf|circbuf]] control commands:<br />
*'''torp''' - set frame pointer to the global read pointer, maintained by the camera driver. If frame at that pointer is invalid (i.e. overran by the next images), the '''scnd''' command (see below) is used instead;<br />
*'''towp''' - set frame pointer to hardware write pointer - position where next frame will be acquired;<br />
*'''prev''' - move to previous frame in buffer, nop if none are available;<br />
*'''next''' - move to the next frame in the buffer. Pointer will not go beyond write pointer that defines where the next frame will be acquired;<br />
*'''last''' - move to the most recently acquired frame, or to write pointer if there are none already acquiured. This command is automatically executed each time the imgsrv is called with a new line;<br />
*'''first''' - move to the oldest frame still available in the buffer. It is not safe to rely on it if more frames are expected - data might be overwritten at any moment and the output image/meta data will be corrupted;<br />
*'''second''' - move to the second oldest frame in the buffer - somewhat safer than the 'first' - there will be time for the "next" command at least before frame data (and pointer structures) will be overwritten;<br />
*'''save''' - save the current frame pointer as a global read pointer that holds it values between the server requests. This pointer is shared between all the clients and applications that use it;<br />
*'''wait''' - Delay execution until there will be a frame at the current pointer ready.<br />
<br />
=== imgsrv and Exif data ===<br />
<br />
imgsrv supports Exif format and includes frame metadata in the image header. The Exif headers are generated in several steps.<br />
*First, the Exif template (''/var/state/exif.template'') file is generated by the [[Exif_init.php|Exif_init.php]] script (during the system start up). The template generated is a binary file that is a valid Exif header itself. This script provides the "static" data (data that does not change between the frames), it also includes specific data that the script collects from various parts of the camera and camera software (like current firmware file name). Finally it provides a place holders for dynamic frame data to be replaced by the actual values by the imgsrv server;<br />
*Next step happens during initialization of the imgsrv. At that time the ''/var/state/exif.template'' is read in, parsed and the pointers to the Exif data that imgsrv is aware of are stored in as internal list together with the maximal string lengths that imgsrv may use.<br />
*Last step - imgsrv reads current frames meta data and uses it to fill the Exif fields at the pointers.<br />
You may find documentation about Exif tags in [http://www.exiv2.org/tags.html Exif tags] or download an official [http://www.exif.org/Exif2-2.PDF Exif2-2.PDF]<br />
The fields that are currently updated by imgsrv are the following (all the other fields are preserved as they are generated by the [[Exif_init.php|Exif_init.php]]):<br />
<br />
{| border="1" cellpadding="2"<br />
|-<br />
| Tag || IFD || Key || Type|| Description<br />
|-<br />
|0x0132||IFD0 ||DateTime||ASCII||Date/time of the image last modified. This field is likely to be modified later by image-processing software<br />
|-<br />
|0x9003||IFD1 ||DateTimeOriginal||ASCII||Date/time of the image acquisition. Here - start of the frame readout (or start of the exposure where applicable)<br />
|-<br />
|0x9291||IFD1 ||SubSecTimeOriginal||ASCII||Fractional seconds (digits after the decimal point) to be added to DateTimeOriginal field, 6 digits<br />
|-<br />
|0x829a||IFD1 ||ExposureTime||RATIONAL|| This field consists of 2 unsigned shorts that make exposure time (in seconds) as a rational number (the nominator divided by the denominator). With the current software denominator is a constant of 10000, imgsrv only updates the nominato<br />
|-<br />
|0x927c||IFD1 ||MakerNote||BYTE|| This custom field is defined in the camera as 36 bytes, they are filled with raw frame metadata - structure ''frame_params_t'' defined in [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/include/asm-cris/elphel/c313a.h?view=markup include/asm-cris/elphel/c313a.h]. Bytes go in CPU order, so the data is little-endian (the rest is big-endian)<br />
<br />
|-<br />
|}</div>Dimitrioshttps://wiki.elphel.com/index.php?title=PHP_and_Gamma_values&diff=11261PHP and Gamma values2012-02-09T01:08:36Z<p>Dimitrios: Fixed an error in frames ahead</p>
<hr />
<div>=How to change Gamma values in an Elphel camera=<br />
<br />
Changing Gamma and BlackLevel values at present requires some special treatment. Here is a short PHP script that does it:<br />
<br />
<?php<br />
<br />
// Set default frame ahead<br />
if (!array_key_exists("ahead",$_GET))<br />
$ahead=3;<br />
<br />
// Special treatment for the gamma values and blacklevel.<br />
// Get exising gamma values if a gamma parameter is requested<br />
if (array_key_exists("gamma",$_GET) || array_key_exists("black",$_GET)) {<br />
$gammas=array(<br />
"GTAB_R__0816"=>"",<br />
"GTAB_G__0816"=>"",<br />
"GTAB_GB__0816"=>"",<br />
"GTAB_B__0816"=>"",<br />
"GTAB_R__0824"=>"",<br />
"GTAB_G__0824"=>"",<br />
"GTAB_GB__0824"=>"",<br />
"GTAB_B__0824"=>""<br />
);<br />
// get existing gamma values<br />
$gammas= elphel_get_P_arr($gammas);<br />
}<br />
<br />
foreach($_GET as $key=>$value) {<br />
<br />
if(strtolower(substr($s, 0, 2))=="0x")<br />
$value= hexdec($value);<br />
switch ($key) {<br />
case "gamma":<br />
// set gammas array and postpone setting values in the camera<br />
$value = intval($value);<br />
$gammas["GTAB_R__0816"]=$value;<br />
$gammas["GTAB_G__0816"]=$value;<br />
$gammas["GTAB_GB__0816"]=$value;<br />
$gammas["GTAB_B__0816"]=$value;<br />
break;<br />
case "black":<br />
// set gammas array and postpone setting values in the camera<br />
$value = intval($value);<br />
$gammas["GTAB_R__0824"]=$value;<br />
$gammas["GTAB_G__0824"]=$value;<br />
$gammas["GTAB_GB__0824"]=$value;<br />
$gammas["GTAB_B__0824"]=$value;<br />
break;<br />
}<br />
// If any gamma value was set, set all gamma values in the camera.<br />
// Was postponed earlier<br />
if ($gammas != NULL) {<br />
// values are taken from the green color<br />
elphel_gamma_add($gammas["GTAB_G__0816"]/100, $gammas["GTAB_G__0824"]);<br />
// Apply the values at the frame ahead<br />
elphel_set_P_arr($gammas, elphel_get_frame() + $ahead);<br />
}<br />
//<br />
// Add code to form the output here<br />
}<br />
<br />
?><br />
<br />
The code looks for HTTP query parameters ''black'' (level of black) and ''gamma'' and sets them at the same time. <br />
<br />
The parameters should be integers: ''1 < gamma <= 100'' and ''0 <= black <= 50''.<br />
<br />
The undocumented function '''elphel_gamma_add(int gamma, int black)''' is used, where the value of ''gamma'' for this function must be a float ''0.1 < gamma <= 1.0''. Without it the gamma values are not effected. Relative code can be found in the file ''camvc.php'' in ''/mnt/flash/html'' in the camera.</div>Dimitrioshttps://wiki.elphel.com/index.php?title=PHP_and_Gamma_values&diff=11257PHP and Gamma values2012-02-08T19:51:48Z<p>Dimitrios: </p>
<hr />
<div>=How to change Gamma values in an Elphel camera=<br />
<br />
Changing Gamma and BlackLevel values at present requires some special treatment. Here is a short PHP script that does it:<br />
<br />
<?php<br />
<br />
// Set default frame ahead<br />
if (!array_key_exists("ahead",$_GET))<br />
$ahead=3;<br />
<br />
// Special treatment for the gamma values and blacklevel.<br />
// Get exising gamma values if a gamma parameter is requested<br />
if (array_key_exists("gamma",$_GET) || array_key_exists("black",$_GET)) {<br />
$gammas=array(<br />
"GTAB_R__0816"=>"",<br />
"GTAB_G__0816"=>"",<br />
"GTAB_GB__0816"=>"",<br />
"GTAB_B__0816"=>"",<br />
"GTAB_R__0824"=>"",<br />
"GTAB_G__0824"=>"",<br />
"GTAB_GB__0824"=>"",<br />
"GTAB_B__0824"=>""<br />
);<br />
// get existing gamma values<br />
$gammas= elphel_get_P_arr($gammas);<br />
}<br />
<br />
foreach($_GET as $key=>$value) {<br />
<br />
if(strtolower(substr($s, 0, 2))=="0x")<br />
$value= hexdec($value);<br />
switch ($key) {<br />
case "gamma":<br />
// set gammas array and postpone setting values in the camera<br />
$value = intval($value);<br />
$gammas["GTAB_R__0816"]=$value;<br />
$gammas["GTAB_G__0816"]=$value;<br />
$gammas["GTAB_GB__0816"]=$value;<br />
$gammas["GTAB_B__0816"]=$value;<br />
break;<br />
case "black":<br />
// set gammas array and postpone setting values in the camera<br />
$value = intval($value);<br />
$gammas["GTAB_R__0824"]=$value;<br />
$gammas["GTAB_G__0824"]=$value;<br />
$gammas["GTAB_GB__0824"]=$value;<br />
$gammas["GTAB_B__0824"]=$value;<br />
break;<br />
}<br />
// If any gamma value was set, set all gamma values in the camera.<br />
// Was postponed earlier<br />
if ($gammas != NULL) {<br />
// values are taken from the green color<br />
elphel_gamma_add($gammas["GTAB_G__0816"]/100, $gammas["GTAB_G__0824"]);<br />
// Apply the values at the frame ahead<br />
elphel_set_P_arr($gammas,$ahead);<br />
}<br />
//<br />
// Add code to form the output here<br />
}<br />
<br />
?><br />
<br />
The code looks for HTTP query parameters ''black'' (level of black) and ''gamma'' and sets them at the same time. <br />
<br />
The parameters should be integers: ''1 < gamma <= 100'' and ''0 <= black <= 50''.<br />
<br />
The undocumented function '''elphel_gamma_add(int gamma, int black)''' is used, where the value of ''gamma'' for this function must be a float ''0.1 < gamma <= 1.0''. Without it the gamma values are not effected. Relative code can be found in the file ''camvc.php'' in ''/mnt/flash/html'' in the camera.</div>Dimitrioshttps://wiki.elphel.com/index.php?title=PHP_and_Gamma_values&diff=11256PHP and Gamma values2012-02-08T19:28:48Z<p>Dimitrios: </p>
<hr />
<div>=How to change Gamma values in an Elphel camera=<br />
<br />
Changing Gamma and BlackLevel values at present requires some special treatment. Here is a short PHP script that does it:<br />
<br />
<?php<br />
<br />
// Set default frame ahead<br />
if (!array_key_exists("ahead",$_GET))<br />
$ahead=3;<br />
<br />
// Special treatment for the gamma values and blacklevel.<br />
// Get exising gamma values if a gamma parameter is requested<br />
if (array_key_exists("gamma",$_GET) || array_key_exists("black",$_GET)) {<br />
$gammas=array(<br />
"GTAB_R__0816"=>"",<br />
"GTAB_G__0816"=>"",<br />
"GTAB_GB__0816"=>"",<br />
"GTAB_B__0816"=>"",<br />
"GTAB_R__0824"=>"",<br />
"GTAB_G__0824"=>"",<br />
"GTAB_GB__0824"=>"",<br />
"GTAB_B__0824"=>""<br />
);<br />
// get existing gamma values<br />
$gammas= elphel_get_P_arr($gammas);<br />
}<br />
<br />
foreach($_GET as $key=>$value) {<br />
<br />
if(strtolower(substr($s, 0, 2))=="0x")<br />
$value= hexdec($value);<br />
switch ($key) {<br />
case "gamma":<br />
// set gammas array and postpone setting values in the camera<br />
$value = intval($value);<br />
$gammas["GTAB_R__0816"]=$value;<br />
$gammas["GTAB_G__0816"]=$value;<br />
$gammas["GTAB_GB__0816"]=$value;<br />
$gammas["GTAB_B__0816"]=$value;<br />
break;<br />
case "black":<br />
// set gammas array and postpone setting values in the camera<br />
$value = intval($value);<br />
$gammas["GTAB_R__0824"]=$value;<br />
$gammas["GTAB_G__0824"]=$value;<br />
$gammas["GTAB_GB__0824"]=$value;<br />
$gammas["GTAB_B__0824"]=$value;<br />
break;<br />
}<br />
// If any gamma value was set, set all gamma values in the camera.<br />
// Was postponed earlier<br />
if ($gammas != NULL) {<br />
// values are taken from the green color<br />
elphel_gamma_add($gammas["GTAB_G__0816"]/100, $gammas["GTAB_G__0824"]);<br />
// Apply the values at the frame ahead<br />
elphel_set_P_arr($gammas,$ahead);<br />
}<br />
//<br />
// Add code to form the output here<br />
}<br />
<br />
?><br />
<br />
The code looks for HTTP query parameters ''black'' (level of black) and ''gamma'' and sets them at the same time. <br />
<br />
The parameters should be integers: ''1 < gamma <= 100'' and ''0 <= black <= 50''.<br />
<br />
The undocumented function '''elphel_gamma_add(int gamma, int black)''' is used, where the value of ''gamma'' for this function must be a float ''0.1 < gamma <= 1.0''. Without it the gamma values are not effected. More can be found in the file ''camvc.php'' in ''/mnt/flash/html''.</div>Dimitrioshttps://wiki.elphel.com/index.php?title=PHP_and_Gamma_values&diff=11255PHP and Gamma values2012-02-08T19:12:08Z<p>Dimitrios: </p>
<hr />
<div>=How to change Gamma values in an Elphel camera=<br />
<br />
Changing Gamma and BlackLevel values at present requires some special treatment. Here is a short PHP script that does it:<br />
<br />
<?php<br />
<br />
// Set default frame ahead<br />
if (!array_key_exists("ahead",$_GET))<br />
$ahead=3;<br />
<br />
// Special treatment for the gamma values and blacklevel.<br />
// Get exising gamma values if a gamma parameter is requested<br />
if (array_key_exists("gamma",$_GET) || array_key_exists("black",$_GET)) {<br />
$gammas=array(<br />
"GTAB_R__0816"=>"",<br />
"GTAB_G__0816"=>"",<br />
"GTAB_GB__0816"=>"",<br />
"GTAB_B__0816"=>"",<br />
"GTAB_R__0824"=>"",<br />
"GTAB_G__0824"=>"",<br />
"GTAB_GB__0824"=>"",<br />
"GTAB_B__0824"=>""<br />
);<br />
// get existing gamma values<br />
$gammas= elphel_get_P_arr($gammas);<br />
}<br />
<br />
foreach($_GET as $key=>$value) {<br />
<br />
if(strtolower(substr($s, 0, 2))=="0x")<br />
$value= hexdec($value);<br />
switch ($key) {<br />
case "gamma":<br />
// set gammas array and postpone setting values in the camera<br />
$value = intval($value);<br />
$gammas["GTAB_R__0816"]=$value;<br />
$gammas["GTAB_G__0816"]=$value;<br />
$gammas["GTAB_GB__0816"]=$value;<br />
$gammas["GTAB_B__0816"]=$value;<br />
break;<br />
case "black":<br />
// set gammas array and postpone setting values in the camera<br />
$value = intval($value);<br />
$gammas["GTAB_R__0824"]=$value;<br />
$gammas["GTAB_G__0824"]=$value;<br />
$gammas["GTAB_GB__0824"]=$value;<br />
$gammas["GTAB_B__0824"]=$value;<br />
break;<br />
}<br />
// If any gamma value was set, set all gamma values in the camera.<br />
// Was postponed earlier<br />
if ($gammas != NULL) {<br />
// values are taken from the green color<br />
elphel_gamma_add($gammas["GTAB_G__0816"]/100, $gammas["GTAB_G__0824"]);<br />
// Apply the values at the frame ahead<br />
elphel_set_P_arr($gammas,$ahead);<br />
}<br />
//<br />
// Add code to form the output here<br />
}<br />
<br />
?><br />
<br />
The code looks for HTTP query parameters ''black'' (level of black) and ''gamma'' and sets them at the same time. <br />
<br />
The parameters should be integers: ''1 < gamma <= 100'' and ''0 <= black <= 50''.<br />
<br />
The undocumented function '''elphel_gamma_add(int gamma, int black)''' is used, where the value of ''gamma'' for this function must be a float ''0.1 < gamma <= 1.0''. Without it the gamma values are not effected. More can be found in the file ''camvc.php'' in ''/mnt/flash/html''.</div>Dimitrioshttps://wiki.elphel.com/index.php?title=PHP_and_Gamma_values&diff=11254PHP and Gamma values2012-02-08T18:58:04Z<p>Dimitrios: </p>
<hr />
<div>=How to change Gamma values in an Elphel camera=<br />
<br />
Changing Gamma and BlackLevel values at present requires some special treatment. Here is a short PHP script that does it:<br />
<br />
<?php<br />
<br />
// Set default frame ahead<br />
if (!array_key_exists("ahead",$_GET))<br />
$ahead=3;<br />
<br />
// Special treatment for the gamma values and blacklevel.<br />
// Get exising gamma values if a gamma parameter is requested<br />
if (array_key_exists("gamma",$_GET) || array_key_exists("black",$_GET)) {<br />
$gammas=array(<br />
"GTAB_R__0816"=>"",<br />
"GTAB_G__0816"=>"",<br />
"GTAB_GB__0816"=>"",<br />
"GTAB_B__0816"=>"",<br />
"GTAB_R__0824"=>"",<br />
"GTAB_G__0824"=>"",<br />
"GTAB_GB__0824"=>"",<br />
"GTAB_B__0824"=>""<br />
);<br />
// get existing gamma values<br />
$gammas= elphel_get_P_arr($gammas);<br />
}<br />
<br />
foreach($_GET as $key=>$value) {<br />
<br />
if(strtolower(substr($s, 0, 2))=="0x")<br />
$value= hexdec($value);<br />
switch ($key) {<br />
case "gamma":<br />
// set gammas array and postpone setting values in the camera<br />
$value = intval($value);<br />
foreach (array(<br />
"GTAB_R__0816",<br />
"GTAB_G__0816",<br />
"GTAB_GB__0816",<br />
"GTAB_B__0816"<br />
) as $key)<br />
$gammas[$key] = $value;<br />
break;<br />
case "black":<br />
// set gammas array and postpone setting values in the camera<br />
$value = intval($value);<br />
foreach (array(<br />
"GTAB_R__0824",<br />
"GTAB_G__0824",<br />
"GTAB_GB__0824",<br />
"GTAB_B__0824"<br />
) as $key)<br />
$gammas[$key] = $value;<br />
break;<br />
}<br />
// If any gamma value was set, set all gamma values in the camera.<br />
// Was postponed earlier<br />
if ($gammas != NULL) {<br />
elphel_gamma_add($gammas["GTAB_G__0816"]/100, $gammas["GTAB_G__0824"]);<br />
// Apply the values at the frame ahead<br />
elphel_set_P_arr($gammas,$ahead);<br />
}<br />
//<br />
// Add code to form the output here<br />
}<br />
<br />
?><br />
<br />
The code looks for HTTP query parameters ''black'' (level of black) and ''gamma'' and sets them at the same time. <br />
<br />
The parameters should be integers: ''1 < gamma <= 100'' and ''0 <= black <= 50''.<br />
<br />
The undocumented function '''elphel_gamma_add(int gamma, int black)''' is used, where the value of ''gamma'' for this function must be a float ''0.1 < gamma <= 1.0''. Without it the gamma values are not effected. More can be found in the file ''camvc.php'' in ''/mnt/flash/html''.</div>Dimitrioshttps://wiki.elphel.com/index.php?title=PHP_and_Gamma_values&diff=11253PHP and Gamma values2012-02-08T18:56:31Z<p>Dimitrios: Code to change gamma values in PHP</p>
<hr />
<div>=How to change Gamma values in an Elphel camera=<br />
<br />
Changing Gamma and BlackLevel values at present requires some special treatment. Here is a short PHP script that does it:<br />
<br />
<?php<br />
<br />
// Set default frame ahead<br />
if (!array_key_exists("ahead",$_GET))<br />
$ahead=3;<br />
<br />
// Special treatment for the gamma values and blacklevel.<br />
// Get exising gamma values if a gamma parameter is requested<br />
if (array_key_exists("gamma",$_GET) || array_key_exists("black",$_GET)) {<br />
$gammas=array(<br />
"GTAB_R__0816"=>"",<br />
"GTAB_G__0816"=>"",<br />
"GTAB_GB__0816"=>"",<br />
"GTAB_B__0816"=>"",<br />
"GTAB_R__0824"=>"",<br />
"GTAB_G__0824"=>"",<br />
"GTAB_GB__0824"=>"",<br />
"GTAB_B__0824"=>""<br />
);<br />
// get existing gamma values<br />
$gammas= elphel_get_P_arr($gammas);<br />
}<br />
<br />
foreach($_GET as $key=>$value) {<br />
<br />
if(strtolower(substr($s, 0, 2))=="0x")<br />
$value= hexdec($value);<br />
switch ($key) {<br />
case "gamma":<br />
// set gammas array and postpone setting values in the camera<br />
$value = intval($value);<br />
foreach (array(<br />
"GTAB_R__0816",<br />
"GTAB_G__0816",<br />
"GTAB_GB__0816",<br />
"GTAB_B__0816"<br />
) as $key)<br />
$gammas[$key] = $value;<br />
break;<br />
case "black":<br />
// set gammas array and postpone setting values in the camera<br />
$value = intval($value);<br />
foreach (array(<br />
"GTAB_R__0824",<br />
"GTAB_G__0824",<br />
"GTAB_GB__0824",<br />
"GTAB_B__0824"<br />
) as $key)<br />
$gammas[$key] = $value;<br />
break;<br />
}<br />
// If any gamma value was set, set all gamma values in the camera.<br />
// Was postponed earlier<br />
if ($gammas != NULL) {<br />
elphel_gamma_add($gammas["GTAB_G__0816"]/100, $gammas["GTAB_G__0824"]);<br />
// Apply the values at the frame ahead<br />
elphel_set_P_arr($gammas,$ahead);<br />
}<br />
//<br />
// Add code to form the output here<br />
}<br />
<br />
?><br />
<br />
The code looks for HTTP query parameters ''black'' (level of black) and ''gamma'' and sets them at the same time. The parameters should be integers: ''1 < gamma <= 100'' and ''0 <= black <= 50''.<br />
The undocumented function '''elphel_gamma_add(int gamma, int black)''' is used, where the value of ''gamma'' for this function must be a float ''0.1 < gamma <= 1.0''. Without it the gamma values are not effected. More can be found in the file ''camvc.php'' in ''/mnt/flash/html''.</div>Dimitrioshttps://wiki.elphel.com/index.php?title=PHP_in_Elphel_cameras&diff=11252PHP in Elphel cameras2012-02-08T13:00:36Z<p>Dimitrios: Corrected parameter ELPHEL_FP100S in example</p>
<hr />
<div>== Why PHP? ==<br />
One of the main objectives of Elphel products is to make them developer-friendly. Just opening of the camera internals (including source code, FPGA code, hardware schematics) is not enough without providing means to modify the cameras easily, and here [http://www.php.net PHP] comes to the rescue. It is powerful and efficient and is well known by many developers including those who may have problems to modify FPGA code or kernel drivers. It is much easier to try your custom applications written in PHP - just transfer the files to the camera (i.e. with ftp) and open them in the web browser.<br />
<br />
PHP supports custom extensions written in C and we'll work (and I hope not just we at Elphel) to provide more custom function to combine flexibility and ease of use of the PHP with efficiency of native compiled code.<br />
<br />
== PHP in Elphel cameras (models 353/363) ==<br />
Current version of PHP in Elphel cameras is 5.2.1, we will try to keep it (almost) current. PHP in the camera is working in [http://en.wikipedia.org/wiki/FastCGI Fast CGI] mode through [http://www.lighttpd.net/ Lighttpd]. Fast CGI mode does not restart applications (like traditional CGI does) for each HTTP request but rather keeps them alive to serve multiple requests. In the case of large application like PHP itself it makes a big performance difference and allows usage of the PHP scripts in the camera without the penalty of slow responses - something really undesirable for [http://www.linuxdevices.com/articles/AT5951285077.html AJAX applications].<br />
<br />
== How to use PHP in the camera ==<br />
It is very simple. It is the same as to try your HTML/JavaScript pages. You just need to ftp you script to one of the two locations (or their subdirectories) in the camera. Examples below assume you have the default camera IP='''192.168.0.9''':<br />
* '''/var/html''' (visible as '''http://192.168.0.9/var/''' in the web browser) - recommended for experiments, if something goes wrong you can just power-cycle the camera and all your changes will be gone<br />
* '''/usr/html''' (visible as ''http://192.168.0.9/''' in the web browser) - permanent (until next full firmware upgrade ) storage in the camera flash memory. This second location is more dangerous as you can change the installed files and rebooting will not restore the default behaviour. Flash memory has limited number of write cycles and can develop additional bad blocks during usage, so this location is recommended for "final" files, already tested in /var/html.<br />
<br />
You may also edit small text files with web-based editor. It does not allow to open non-existent file, but has an option to "Save As" - http://192.168.0.9/admin-bin/editcgi.cgi<br />
So you can try opening http://192.168.0.9/admin-bin/editcgi.cgi?file=/usr/html/phpinfo.php and then (modify and) save it to /var/html/test.php . When done - just open the following URL and watch the results of the script processing by in-camera PHP:<br />
<br />
'''http://192.168.0.9/var/test.php''' - run<br />
'''http://192.168.0.9/admin-bin/editcgi.cgi?file=/var/html/test.php''' - edit<br />
<br />
It is also possible to execute PHP scripts without the browser - camera startup scripts already use it for various initialization of the hardware. You can (silently) execute the same program in telnet session:<br />
php /var/html/test.php >/dev/null<br />
<br />
== Elphel PHP extension in the camera ==<br />
Since [[Release_notes|Elphel software version 7.1.6]] there is a custom extension module for PHP installed in the camera, you may also create your own extension as described [[PHP_in_Elphel_cameras#Creating_custom_PHP_extensions_for_Elphel_cameras|below]]. The existent extension exports several functions and defines constants.<br />
=== Constants, defined in ''elphel'' PHP extension ===<br />
see: [[Elphel_PHP_constants]]<br />
===''elphel'' extension functions ===<br />
<br />
''Note: Currently arguments (and array values) are supposed to be numbers, not strings - you may want to use $value+0 (instead of just $value) if $value may be a string (i.e. passed from _GET[])''--[[User:Andrey.filippov|Andrey.filippov]] 19:55, 14 December 2007 (CST)<br />
<br />
----<br />
==== elphel_get_P_value ====<br />
''long'' '''elphel_get_P_value''' (''long'' $address)<br />
<br />
This function returns value of one of internal camera parameters, as defined in [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/include/asm-cris/elphel/c313a.h?view=markup c313a.h] and documented in [[Elphel_PHP_constants]]. It is strongly recommended to use symbolic names as the numeric values may change in the future (as they already did multiple times). The values are maintained by the camera driver(s), usually they are updated when the driver programs the acquisition process.<br />
<br />
Example:<br />
echo elphel_get_P_value(ELPHEL_FP1000S)/1000; // will return current camera sensor frame rate in (frames per second);<br />
<br />
<br />
----<br />
==== elphel_set_P_value ====<br />
''void'' '''elphel_set_P_value''' (''long'' $address, ''long'' $data)<br />
<br />
Set a single camera parameter.<br />
<br />
Example:<br />
elphel_set_P_value(ELPHEL_QUALITY,100); // set JPEG compression quality to 100% - virtually lossless<br />
The elphel_get_P_value and elphel_set_P_value deal with different variables. Those that are read are validated to match the allowed values and may differ from those written (and they are only updated when sensor/compressor are programmed). You may read the parameters values that were written to the camera by adding ELPHEL_NUMBER to the parameter address, i.e<br />
echo elphel_get_P_value(ELPHEL_QUALITY+ELPHEL_NUMBER); // will output the compression quality as written<br />
<br />
<br />
----<br />
<br />
==== elphel_get_P_arr ====<br />
''array'' '''elphel_get_P_arr''' (''array'' $template)<br />
<br />
Read multiple camera parameters as an associative array, according to $template. $template should have elements with the key names matching the camera parameters names, same as defined [[Elphel_PHP_constants]], but without "ELPHEL_" prefix (all the elements with the other keys will be ignored). '''elphel_get_P_arr''' returns array, where element keys are the same as in $template (after removing of any unknown ones), and values are ''long'' values read from the camera.<br />
<br />
Example:<br />
$arr=array("foo"=>"", "WOI_LEFT" => "", "WOI_TOP" => "", "1", 3, "WOI_WIDTH" => 0, "WOI_HEIGHT" => 0);<br />
print_r ($arr);<br />
will return (5MPix sensor, full window):<br />
Array<br />
(<br />
[WOI_LEFT] => 0<br />
[WOI_TOP] => 0<br />
[WOI_WIDTH] => 2592<br />
[WOI_HEIGHT] => 1936<br />
)<br />
<br />
<br />
----<br />
<br />
==== elphel_set_P_arr ====<br />
''long'' '''elphel_set_P_arr''' (''array'' $input, ''long'' $frame, ''long'' $flag) )<br />
<br />
Write multiple camera parameters, provided as an associative array, where keys are parameter names same as defined [[Elphel_PHP_constants]], but without "ELPHEL_" prefix. Values should be numeric and integer, all other types are ignored.<br />
<br />
optional arguments:<br />
frame - frame number to write these parameters to - if not specified default framedelay (current frame + 3) is applied)<br />
flag - possible flags? <br />
<br />
Return value - frame number to which parameters were written <br />
<br />
Example:<br />
echo elphel_set_P_arr(array("WOI_LEFT" => 896, "WOI_TOP" => 672, "WOI_WIDTH" => 800, "WOI_HEIGHT" => 600));<br />
Will set 800x600 window in the center of the 5Mpix sensor and print frame number these changes where applied to<br />
<br />
<br />
----<br />
<br />
==== elphel_get_state ====<br />
''long'' '''elphel_get_state''' (''void'')<br />
There are multiple states defined in the camera, some are obsolete, the following are most common (no symbolic constants in PHP yet)<br />
* 0 - "reset" (i.e. no images yet acquired after power up)<br />
* 7 - "stopped" - sensor is constantly acquiring images (used for autoexposure), but compressor is stopped and no frames get to the [[Circbuf|circbuf]]<br />
* 8 - "running" - compressor is acquiring images to [[Circbuf|circbuf]]<br />
* 9 - "stopping" - compressor is compressing the last frame (transition from "running" to "stopped"<br />
*10 - "single_buffer" - compressor is acquiring full [[Circbuf|circbuf]] (plus one frame as it will notice the buffer is full after overrunning the original starting point) and then will stop<br />
<br />
<br />
----<br />
==== elphel_fpga_read ====<br />
''long'' '''elphel_fpga_read''' (''long $address'')<br />
<br />
Reads data from a certain fpga register address.<br />
<br />
Example:<br />
echo elphel_fpga_read(4); // outputs the data at address 4<br />
<br />
<br />
----<br />
==== elphel_fpga_write ====<br />
''void'' '''elphel_fpga_write''' (''long $address, long $data'')<br />
<br />
Writes data to a certain fpga register address.<br />
<br />
'''for Elphel 353 cameras these values can be the following (quoted from x353.h):'''<br />
187 #define X313_WA_WCTL 0 // write control register - 32<br />
188 #define X313_WA_DMACR 1 // DMA control register:<br />
189 // 17: DMA enable<br />
190 // 16: 0- raw, 1 - JPEG<br />
191 // 15-10: not used<br />
192 // 0-9: line length in long words<br />
193 #define X313_WA_SENSFPN 2 // Sensor/FPN control register:<br />
194 // [10] - testmode - if 1 generates gradient data (as Zoran chips) where pixel value = horizontal position<br />
195 // [9:7] - submode - subtract background (8 bits) mode (use di[7:0]):<br />
196 // 000 - no subtraction;<br />
197 // 001 - (finest) subtract 8 bit bkgnd from 12 bits pixels<br />
198 // 010 - shift 8bit bkgnd 1 bit left before applying<br />
199 // 011 - shift 8bit bkgnd 2 bits left before applying<br />
200 // 100 - shift 8bit bkgnd 2 bits left before applying<br />
201 // 101 - shift 8bit bkgnd 2 bits left before applying<br />
202 // fpn data to subtract should be a little less to add a "fat zero"<br />
203 // [6:4] - mpymode sensitivity correction mode (use di[15:8]):<br />
204 // 000 - no correction<br />
205 // 001 - fine correction (+/-3.125%)<br />
206 // 010 - fine correction (+/-6.25%)<br />
207 // 011 - fine correction (+/-12.5%)<br />
208 // 100 - +/- 25%<br />
209 // 101 - +/- 50%<br />
210 // [3] - wdth - word width: 0 - 8 bit, 1 - 16 bit (5 MSB == 0)<br />
211 // [2:0] scaling of 11 bit FPN result to fit in 8bit output:<br />
212 // 00 - default - use [9:1]<br />
213 // 01 - use [10:2] - to protect from saturation after applying mpymode<br />
214 // nominal range - 0..127<br />
215 // 10 - use [7:0] before saturation, "digital gain" == 4 (maximal)<br />
216 // 11 - use [8:1] before saturation, "digital gain" == 2<br />
217 <br />
218 // 31-8: not used<br />
219 // 7: 0 - normal, 1 - test mode (as Zoran)<br />
220 // 6-5: subtract FPN mode:<br />
221 // 0 - no subtraction<br />
222 // 1 (fine) - subtract 8-bit FPN from 10-bit pixel<br />
223 // 2 - multiply FPN by 2 before subtracting<br />
224 // 3 - multiply FPN by 4 before subtracting (full scfpcfale)<br />
225 // negative result is replaced by 0, decrease FPN data before applying for "fat 0"<br />
226 // 4-3: muliply by inverse sensitivity (sensitivity correction) mode:<br />
227 // 0 - no correction<br />
228 // 1 - fine (+/- 12.5%)<br />
229 // 2 - medium (+/- 25%)<br />
230 // 3 - maximal (+/- 50%)<br />
231 // 2: pixel depth:<br />
232 // 0 - 8 bits/pixel (needed for JPEG encoding)<br />
233 // 1 - 16 bits/pixel (only 11 LSBs are non-zero)<br />
234 // 1-0: scale (8 bit mode only):<br />
235 // 0 - full scale corresponds to sensor full scale if no correction was applied<br />
236 // 1 - divide by 2. This will guarantee against saturation after sensitivity correction was<br />
237 // applied. Nominal output range - 0..127<br />
238 // 2 - multiply by 4 (use 8 lower bits from sensor data)<br />
239 // 3 - multiply by 2<br />
240 // Result data is saturated by 255<br />
241 #define X313_WA_VIRTTRIG 3 // Virtual trigger threshold<br />
242 // 31-22 not used<br />
243 // 21-0 Trigger will fire if sum of pixels in a line<br />
244 // (after FPN processig) is more than this value.<br />
245 // Disabled if 0 - selected real (electrical) external trigger<br />
246 #define X313_WA_TRIG 4 // Sensor triggering<br />
247 // 31-3: not used<br />
248 // 2: Enable sensor (0 - abort at once)<br />
249 // 1: External Trigger (0 - internal)<br />
250 // 0: continuous acquisition (0 - single "frame" - actually number of lines specified)<br />
251 #define X313_WA_NLINES 5 // number of lines to acquire (afer trigger)<br />
252 // 31-11: not used<br />
253 // 10-0 : number of lines to acquire (in a frame or after the external trigger)<br />
254 //#define X313_WA_IRQM 6 // Interrupt mask (1 - enable, 0 - reset all but done)<br />
255 // 31-04: not used<br />
256 // 3: Done. Reset by writing to X313_WA_TRIG<br />
257 // 2: frame acquisition over<br />
258 // 1: external trigger<br />
259 // 0: frame sync (vacts)<br />
260 #define X313_WA_DCDC 7 // sensor DC-DC converter frequency settings<br />
261 // 31-05: not used<br />
262 // 4-0 0 - use internal clock (not sync)<br />
263 // 1..31 use divided pixel clock<br />
264 // for 20MHz use 5'h10,<br />
265 // else - N= (Fpix[MHz]/1.2)-1, if Fpix=20MHz,<br />
266 // N= 15.7->16=5'h10<br />
<br />
<br />
Example:<br />
elphel_fpga_write(4, 4); // Sets sensor triggering to an unused number and therefore disabling it -> acquire single frame to video buffer<br />
<br />
<br />
----<br />
<br />
==== elphel_reset_sensor ====<br />
''void'' '''elphel_reset_sensor''' (''void'')<br />
<br />
Reset the sensor settings, stop compressor (if it was running) and force sensor re-initialization.<br />
<br />
Example:<br />
elphel_reset_sensor();<br />
<br />
<br />
----<br />
==== elphel_program_sensor ====<br />
''void'' '''elphel_program_sensor''' (''long'' $nonstop)<br />
<br />
Applies written earlier (see [[PHP_in_Elphel_cameras#elphel_set_P_value|elphel_set_P_value]], [[PHP_in_Elphel_cameras#elphel_set_P_arr|elphel_set_P_arr]], [[PHP_in_Elphel_cameras#elphel_white_balance|elphel_white_balance]]) parameters to the cameras sensor and FPGA compressor. $nonstop determines if the acquisition should be restarted ($nonstop==0) or updated without stopping ($nonstop==1).<br />
<br />
'''Note:''' As of version 8.x, parameters are applied as they are set. Therefore, this function is no longer necessary.<br />
<br />
Example:<br />
elphel_program_sensor(0);<br />
<br />
<br />
----<br />
<br />
==== elphel_wait_frame ====<br />
''void'' '''elphel_wait_frame''' (''void'')<br />
<br />
Waits for the next frame to be compressed to the circular buffer - it is also the time when some other parameters (accessible with [[PHP_in_Elphel_cameras#elphel_get_P_value|elphel_get_P_value]], [[PHP_in_Elphel_cameras#elphel_get_P_arr|elphel_get_P_arr]]) are updated.<br />
<br />
Example:<br />
elphel_wait_frame();<br />
<br />
<br />
----<br />
<br />
==== elphel_wait_frame_abs ====<br />
''long'' '''elphel_wait_frame''' (''long'' frame)<br />
<br />
wait for absolute frame number (includes those that are not compressed) <br />
<br />
returns: frame number<br />
<br />
Example:<br />
elphel_wait_frame_abs(200);<br />
<br />
<br />
----<br />
<br />
==== elphel_skip_frames ====<br />
''long'' '''elphel_skip_frames''' (''long'' frames)<br />
<br />
skip some frames (includes those that are not compressed) - will work even if no frames are compressed <br />
<br />
returns: frame number<br />
<br />
Example:<br />
elphel_skip_frames(1);<br />
<br />
<br />
----<br />
<br />
==== elphel_compressor_run ====<br />
''void'' '''elphel_compressor_run''' (''void'')<br />
<br />
Turn the FPGA compressor on. Sensor should be already programmed ([[PHP_in_Elphel_cameras#|elphel_get_state] should return 7 (or higher) if tested prior to issuing ''elphel_compressor_run()'' command.<br />
<br />
Example:<br />
elphel_compressor_run();<br />
<br />
<br />
----<br />
==== elphel_compressor_stop ====<br />
''void'' '''elphel_compressor_stop''' (''void'')<br />
<br />
Stop camera compressor (will stop transferring more frames to the [[Circbuf|circular buffer]]. This command does not to be synchronized - compressor will finish current frame before stopping.<br />
<br />
Example:<br />
elphel_compressor_stop();<br />
<br />
<br />
----<br />
==== elphel_compressor_frame ====<br />
''void'' '''elphel_compressor_frame''' (''void'')<br />
<br />
Acquire one frame to the buffer (will apply written JPEG quality). Sensor should be already programmed - [[PHP_in_Elphel_cameras#|elphel_get_state]] should return 7 (or higher) if tested prior to issuing ''elphel_compressor_frame()'' command.<br />
<br />
Example:<br />
elphel_compressor_frame();<br />
<br />
<br />
----<br />
==== elphel_set_fpga_time ====<br />
''double'' '''elphel_set_fpga_time''' (''double'' seconds)<br />
<br />
Set FPGA internal timer that is used for time-stamping images and video frames. Internal counter has a 32-bit seconds counter and 12 bit microsecond one, so you may specify epoch - seconds since 01/01/1970.<br />
<br />
Returns time set as a ''double'' - it should match the input parameter after rounding to microseconds (resolution of the FPGA timer).<br />
<br />
Example:<br />
elphel_set_fpga_time(0x47565ad3);<br />
<br />
----<br />
==== elphel_get_fpga_time ====<br />
''double'' '''elphel_get_fpga_time''' (''void'')<br />
<br />
Copies current value of the FPGA timer registers to the global array (maybe read with several functions described above) and returns the the time as a ''double'' value, combining second as microseconds. The readout process guaranties that seconds and microseconds are sample simultaneously.<br />
<br />
Example:<br />
echo elphel_get_fpga_time();<br />
<br />
<!--<br />
----<br />
==== elphel_flush_cache ====<br />
''void'' '''elphel_flush_cache''' (''void'')<br />
<br />
This function is included to fight (hardware) cache coherency problems in mmap implementation for ETRAX FS processor. I'm not sure it will be really needed here - it needs some testing. If it will be proven it is needed - we'll incorporate it into appropriate functions that depend on it, if not it will just be removed.<br />
<br />
This function may be needed before [[PHP_in_Elphel_cameras#elphel_get_P_value|elphel_get_P_value]], [[PHP_in_Elphel_cameras#elphel_get_P_arr|elphel_get_P_arr]] to read data updated by the driver and/or before [[PHP_in_Elphel_cameras#elphel_program_sensor|elphel_program_sensor]], [[PHP_in_Elphel_cameras#elphel_compressor_run\elphel_compressor_run]], [[PHP_in_Elphel_cameras#elphel_compressor_frame|elphel_compressor_frame]] (if any of the parameters were changed with [[PHP_in_Elphel_cameras#elphel_set_P_value|elphel_set_P_value]], [[PHP_in_Elphel_cameras#elphel_set_P_arr|elphel_set_P_arr]] after the last call to elphel_flush_cache<br />
<br />
Example:<br />
elphel_flush_cache();<br />
--><br />
<br />
----<br />
==== elphel_white_balance ====<br />
''int'' '''elphel_white_balance''' ([''double'' thrsh [, ''double'' minfrac [, ''double'' rscale [, ''double'' bscale]]]])<br />
<br />
This function is designed to perform white balancing of the camera images. It relies on histogram calculation, "gamma" tables (curves) (both implemented in the FPGA) and the auto-exposure software in the camera (not yet included in this PHP extension, it is currently controlled through the separate CGI program). White balance uses the same window as auto-exposure, only data inside the specified rectangular window is processed.<br />
<br />
<br />
The goal of this function is to make the brightest areas in the image white (equal values of red, green and blue), it assumes that auto-exposure algorithm (operating after each frame acquired) already adjusted the brightness of the images so it uses all the 8-bit range and some pixel values are close to the maximal 255.<br />
<br />
<br />
The balancing is achieved by modification of the lookup tables ("gamma" tables, "curves") that map 12-bit (in 5MPix sensor, may be 10 or 14 bits with other devices) pixel data to the 8-bit pixel values used by the image/video compressor, the same values can be manually entered with [[PHP_in_Elphel_cameras#elphel_get_P_value|elphel_get_P_value]], [[PHP_in_Elphel_cameras#elphel_get_P_arr|elphel_get_P_arr]] functions applied to RSCALE and BSCALE parameters. The balancing is sensor-independent and it does not change sensor analog gains (where available), but if the required correction is significant, it is recommended to adjust those gains also, leaving only fine adjustment to the white balance algorithm - that will increase the dynamic range of the images.<br />
<br />
<br />
All function parameters are optional, but you can not skip the first one(s) if you would like to specify the next one(s), in that case default values should be explicitly entered.<br />
<br />
<br />
First parameter '''thrsh''' defines how bright should be pixels to be counted as white. Default value of '''0.98''' corresponds to 250 counts on 255 scale.<br />
<br />
<br />
Second parameter '''minfrac''' (default '''0.01''') tells how many pixels (at least) should be counted, as a fraction of the total number of the pixels in the specified window. If there are too few pixels with the brightness above the ''thrsh'', the ''thrsh'' will be lowered, to let more pixels to be counted.<br />
<br />
<br />
Next two parameters - '''rscale''' and '''bscale''' (both with default values of '''1.0''') can be used to apply manual bias to the automatically calculated values of red and blue scales (relative.to green)<br />
<br />
<br />
When this function is executed successfully it returns 0 (negative numbers indicate failure) in adjusts parameters (similar to manual [[PHP_in_Elphel_cameras#elphel_get_P_value|elphel_get_P_value]], [[PHP_in_Elphel_cameras#elphel_get_P_arr|elphel_get_P_arr]]), but that will propagate to the FPGA only after [[PHP_in_Elphel_cameras#elphel_program_sensor|elphel_program_sensor]] is executed. If you do not need to change any other parameters, you may use '''elphel_program_sensor(1)''' - in this case the image/video acquisition process will not be interrupted, frame timing will be preserved.<br />
<br />
<br />
As this function uses the histograms calculated from the previously acquired images, you actually need to acquire some. It is recommended you wait till the auto-exposure will adjust the brightness before executing elphel_white_balance. It also is not needed to run it as frequently as auto-exposure (for each frame), usually it is enough to call it only when the lighting conditions are changed.<br />
<br />
<br />
Examples:<br />
if (elphel_white_balance()>=0) elphel_program_sensor(1);<br />
or<br />
elphel_white_balance(0.98,0.01,1.0,1.2); // set bluish tint<br />
<br />
[http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/packages/web/353/php_top/whitebalance.php?view=markup whitebalance.php] is an example script that uses this function. It is installed in the camera and can be called as (provided camera has the default IP of 192.168.0.9):<br />
http://192.168.0.9/whitebalance.php<br />
or<br />
http://192.168.0.9/whitebalance.php?thrsh=0.98&minfrac=0.01&rscale=1.0&bscale=1.0<br />
<br />
----<br />
==== elphel_autoexposure_set ====<br />
''void'' '''elphel_autoexposure_set''' (''void'')<br />
<br />
This function controls auto-exposure in the camera. It is a quick modification that preserves the existent functionality (including interface) and just adds control from the PHP. This function itself does not take any parameters, it also does not return any data, It applies parameters that have to be already written by either of [[PHP_in_Elphel_cameras#elphel_set_P_value|elphel_set_P_value]], [[PHP_in_Elphel_cameras#elphel_set_P_arr|elphel_set_P_arr]], the current state of the auto-exposure algorithm can be read back using [[PHP_in_Elphel_cameras#elphel_get_P_value|elphel_get_P_value]], [[PHP_in_Elphel_cameras#elphel_get_P_arr|elphel_get_P_arr]] functions.<br />
<br />
===== auto-exposure software in the camera =====<br />
<br />
====== kernel space (driver) ======<br />
When the image from the sensor is acquired in the camera (even the compressor is off), software interrupt is generated and among others two things related to the auto-exposure control happen in the driver.<br />
* software prepares histograms calculated in the FPGA during the previous frame acquisition to be analysed by the user space application and make them available to the userspace applications through memory-mapped arrays (mmap) and<br />
* the previously calculated exposure is applied to the sensor to take effect during the next frame acquisition. Exposure time is the only parameter controlled automatically, you may also want to change analog gain(s) (sensitivity) to extend the range of the illumination levels that camera can handle. Most of this driver functionality is implemented in the [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/arch/cris/arch-v32/drivers/elphel/hist353.c?view=markup hist353.c].<br />
<br />
====== user space (daemon) ======<br />
User space application [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/autoexp/autoexp.c?view=markup autoexp.c] (running as a daemon) processes the histograms and calculates the corrected value of the exposure, the result value is sent to the driver that applies the required correction. <br />
<br />
In addition the histograms (four of them - individually for each of the 4 Bayer components, including 2 sets of green pixels), driver provides applications with the lookup ("gamma") tables that are used by the FPGA to convert sensor pixel value (12 bit for the 5MPix sensor) into the 8-bit range, usually - non-linearly, controlled by "gamma" parameter. This tables are needed when processing the histograms, as FPGA calculates them after the LUT are applied to the pixel values.<br />
<br />
The auto-exposure configuration (input) parameters and the current state (output) can still be accessed using the current CGI script [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/autoexp/autoexpos.cgi.c?view=markup autoexpos.cgi.c] (as used by camvc user interface), alternatively they are directly accessible through the [[PHP_in_Elphel_cameras#elphel_set_P_value|elphel_set_P_value]], [[PHP_in_Elphel_cameras#elphel_set_P_arr|elphel_set_P_arr]], [[PHP_in_Elphel_cameras#elphel_get_P_value|elphel_get_P_value]], [[PHP_in_Elphel_cameras#elphel_get_P_arr|elphel_get_P_arr]] functions.<br />
<br />
===== auto-exposure algorithm in the camera =====<br />
<br />
The goal of the auto-exposure algorithm is to use as much as possible of the sensor dynamic range in the area of interest. It tries to adjust the exposure of the sensor so the whole range of the image pixel values (up to 255) are used (small number of pixels are usually still allowed to overexpose and be return the 255 limit value). It is possible to maintain the brightest pixels (disregarding just few "super-bright") near 255, but the it has 2 disadvantages:<br />
* sometimes with the back light you want to have good reproduction of darker objects while allowing the bright background to saturate<br />
* it is difficult to calculate required correction when the exposure is too long (some areas are over-saturated), because there is no way to know how much are the pixels saturated (if the image is too dim, the required exposure increase is just the ratio of 255 and the brightest pixels in the image)<br />
For these reasons a slightly different algorithm is used - the software tries to maintain specified part of the pixels in the window of interest to be below the specified level (usually high, but less than the full scale). In this case if the brightness of the scene suddenly increases (up to the ratio of the full scale pixel value to the specified threshold), the exposure correction can be calculated and applied in a single step. You may experiment with this algorithm using GUI in ''camvc'' camera web interface.<br />
<br />
<br />
===== parameters that control auto-exposure in the camera =====<br />
The following are parameters (it is possible to both their names as array keys with functions [[PHP_in_Elphel_cameras#elphel_set_P_arr|elphel_set_P_arr]], [[PHP_in_Elphel_cameras#elphel_get_P_arr|elphel_get_P_arr]], [[PHP_in_Elphel_cameras#elphel_get_P_warr|elphel_get_P_warr]]. There are also [[Elphel_PHP_constants|constants]] defined that use the same names with "ELPHEL_"prefix (i.e. ELPHEL_AUTOEXP_ON), these constants are useful with the functions [[PHP_in_Elphel_cameras#elphel_set_P_value|elphel_set_P_value]], [[PHP_in_Elphel_cameras#elphel_get_P_value|elphel_get_P_value]]. All the parameter values are ''long'' (32-bit) integers, you may read them back (as written) with [[PHP_in_Elphel_cameras#elphel_get_P_warr|elphel_get_P_warr]] function call. Te value of ELPHEL_HIST_NOT_CHANGE (65536) for any of these parameters mean that values corresponding to these parameters will not be updated.<br />
<br />
* '''AUTOEXP_ON''' - when set to '''1''' enables automatic exposure control, when '''0''' - disables it<br />
* '''AUTOEXP_RWIDTH''', '''AUTOEXP_RHEIGHT''' - relative width and height (in %) of the auto-exposure window width and height. It is used for histogram calculation in the FPGA and so controls not only auto-exposure, but also [[PHP_in_Elphel_cameras#elphel_white_balance|white balance]] and manual histogram processing<br />
* '''AUTOEXP_RLEFT''', '''AUTOEXP_RTOP''' - position of the auto-exposure window center, in %, counted from the left and top respectively<br />
* '''AUTOEXP_EXP_MAX''' - maximal exposure time (in 1/10000 of a second) allowed for the auto-exposure algorithm. It is recommended to set it equal to the frame period when video is streamed or recorded, otherwise in the low-light conditions the frame rate may drop to accommodate longer exposure times (frame period may never be shorter than the exposure time)<br />
* '''AUTOEXP_OVEREXP_MAX''' (old algorithm) - amount of pixels (fraction of all the pixels in the auto-exposure window) that are allowed to be overexposed, measured in 1/100 or a percent. This parameter is used when both '''AUTOEXP_S_PERCENT''' and '''AUTOEXP_S_INDEX''' (see below) are 0. This algorithm can be slow to handle over-exposed images and is not recommended.<br />
* '''AUTOEXP_S_PERCENT''' - amount of pixels that are controlled to have value below the specified '''AUTOEXP_S_INDEX''' (below), measured in 1/100 of a percent. Example: AUTOEXP_S_PERCENT=9400 means that 94% of pixels should have value lower than '''AUTOEXP_S_INDEX'''<br />
* '''AUTOEXP_S_INDEX''' - threshold for the pixel values (on a 0..255 8-bit scale) used together with '''AUTOEXP_S_PERCENT'''<br />
* '''AUTOEXP_SKIP_PMIN''' - minimal calculated exposure correction that will be applied (in 1/100 of a %). Value of 500 (default) means that exposure value will not be modified if the calculated value differs less than by 5% from the current one<br />
* '''AUTOEXP_SKIP_T''' minimal absolute exposure correction (in exposure steps, currently 1 step is 1/10000 sec), default value = 2<br />
* '''AUTOEXP_SKIP_PMAX''' - maximal allowed exposure correction that algorithm is allowed to apply (in 1/200 of a %, default is 5000 - 50%). If calculated exposure correction exceeds this value, it will not be applied immediately, the algorithm will wait for the next frame to make sure it was not an instant flash (i.e from some camera)<br />
* '''AEXPWND_WIDTH''', '''AEXPWND_HEIGHT''', '''AEXPWND_TOP''', '''AEXPWND_LEFT''' (when written to) behave similarly to '''AEXPWND_RWIDTH''', '''AEXPWND_RHEIGHT''', '''RAEXPWND_TOP''' and '''AEXPWND_RLEFT''', but come into effect immediately, not waiting for the [[PHP_in_Elphel_cameras#elphel_autoexposure_set|elphel_autoexposure_set()]] call. Writing to AEXPWND_RWIDTH, AEXPWND_RHEIGHT, RAEXPWND_TOP and AEXPWND_RLEFT and calling [[PHP_in_Elphel_cameras#elphel_autoexposure_set|elphel_autoexposure_set()]] updates the AEXPWND_WIDTH, AEXPWND_HEIGHT, AEXPWND_TOP, AEXPWND_LEFT<br />
<br />
<!--<br />
<br />
[AUTOEXP_EXP] => 801<br />
[AUTOEXP_SKIP_PMIN] => 500<br />
[AUTOEXP_SKIP_PMAX] => 5000<br />
[AUTOEXP_SKIP_T] => 2<br />
[AEXPWND_WIDTH] => 80<br />
[AEXPWND_HEIGHT] => 80<br />
[AEXPWND_TOP] => 50<br />
[AEXPWND_LEFT] => 50<br />
<br />
[ELPHEL_AUTOEXP_ON] => 76<br />
[ELPHEL_AUTOEXP_RWIDTH] => 77<br />
[ELPHEL_AUTOEXP_RHEIGHT] => 78<br />
[ELPHEL_AUTOEXP_RLEFT] => 79<br />
[ELPHEL_AUTOEXP_RTOP] => 80<br />
[ELPHEL_AUTOEXP_EXM_MAX] => 81<br />
[ELPHEL_AUTOEXP_OVEREXP_MAX] => 82<br />
[ELPHEL_AUTOEXP_S_PERCENT] => 83<br />
[ELPHEL_AUTOEXP_S_INDEX] => 84<br />
[ELPHEL_AUTOEXP_EXP] => 85<br />
[ELPHEL_AUTOEXP_SKIP_PMIN] => 86<br />
[ELPHEL_AUTOEXP_SKIP_PMAX] => 87<br />
[ELPHEL_AUTOEXP_SKIP_T] => 88<br />
[ELPHEL_AEXPWND_WIDTH] => 89<br />
[ELPHEL_AEXPWND_HEIGHT] => 90<br />
[ELPHEL_AEXPWND_TOP] => 91<br />
[ELPHEL_AEXPWND_LEFT] => 92<br />
[ELPHEL_HIST_NOT_CHANGE] => 65535<br />
--><br />
<br />
== Creating custom PHP extensions for Elphel cameras ==<br />
<br />
The followings steps are needed to create a custom PHP extension to run in Elphel product:<br />
<br />
* Create subdirectory of this (ext) directory for the new extension<br />
* Create files in this new directory - at least<br />
** config.m4<br />
** <your name>.h<br />
** <yourname>.c<br />
<br />
You may use ext_skel script to automate this process or follow a nice tutorial by Sara Goleman '''[http://devzone.zend.com/node/view/id/1021 Extension Writing Part I: Introduction to PHP and Zend]''' . You may also like to read her book, "Extending and Embedding PHP".<br />
=== config.m4 ===<br />
<br />
PHP_ARG_ENABLE(hello, whether to enable Hello World support, [ --enable-hello Enable Hello World support])<br />
if test "$PHP_HELLO" = "yes"; then<br />
AC_DEFINE(HAVE_HELLO, 1, [Whether you have Hello World])<br />
PHP_NEW_EXTENSION(hello, hello.c, $ext_shared)<br />
fi<br />
<br />
=== php_hello.h ===<br />
<br />
#ifndef PHP_HELLO_H<br />
#define PHP_HELLO_H 1<br />
#define PHP_HELLO_WORLD_VERSION "1.0"<br />
#define PHP_HELLO_WORLD_EXTNAME "hello"<br />
PHP_FUNCTION(hello_world);<br />
extern zend_module_entry hello_module_entry;<br />
#define phpext_hello_ptr &hello_module_entry<br />
#endif<br />
<br />
=== hello.c ===<br />
<br />
#ifdef HAVE_CONFIG_H<br />
#include "config.h"<br />
#endif<br />
#include "php.h"<br />
#include "php_hello.h"<br />
static function_entry hello_functions[] = {<br />
PHP_FE(hello_world, NULL)<br />
{NULL, NULL, NULL}<br />
};<br />
zend_module_entry hello_module_entry = {<br />
#if ZEND_MODULE_API_NO >= 20010901<br />
STANDARD_MODULE_HEADER,<br />
#endif<br />
PHP_HELLO_WORLD_EXTNAME,<br />
hello_functions,<br />
NULL,<br />
NULL,<br />
NULL,<br />
NULL,<br />
NULL,<br />
#if ZEND_MODULE_API_NO >= 20010901<br />
PHP_HELLO_WORLD_VERSION,<br />
#endif<br />
STANDARD_MODULE_PROPERTIES<br />
};<br />
#ifdef COMPILE_DL_HELLO<br />
ZEND_GET_MODULE(hello)<br />
#endif<br />
PHP_FUNCTION(hello_world)<br />
{<br />
RETURN_STRING("Hello World", 1);<br />
}<br />
<br />
<br />
<br />
With the 3 files created you need to cd to the extension directory and run<br />
../../elphize<br />
That will generate support files (running phpize script) so you'll just need to run<br />
make install<br />
to have the new extension (as a dynamic library) installed in the target directory tree and included in the camera flash image.<br />
<br />
You will need to add "extension=<your_extension_name>" to the php.ini file to be activated.<br />
<br />
When troubleshooting extensions you may also want to try your scripts from the command line in the camera - in that case the stdout will be visible and PHP+your module will be able to complain about Segmentation faults (when invoked from the browser it you will get Error 500 at best if that happens). And you'll have to manually restart web server + PHP after module changes (remember - Fast CGI does not kill PHP after end of HTTP request?)<br />
<br />
== Known problems ==<br />
<br />
Function ''[http://us.php.net/manual/en/function.fread.php fread]'' in PHP always tries to read 8192 bytes even if the length parameter is <8192, that causes problems when read from devices (i.e. i2c) being too slow or causing side effects. It is considered [http://bugs.php.net/bug.php?id=21641 feature, not a bug].<br />
<br />
A quick fix will be to change the driver to always read minimal (1/2/3/4 bytes depending on the nature of the data) if the count passed to device read function is 8192.<br />
<br />
[[Category:Software]]<br />
[[Category:PHP]]</div>Dimitrioshttps://wiki.elphel.com/index.php?title=PHP_in_Elphel_cameras&diff=11079PHP in Elphel cameras2012-01-05T14:52:17Z<p>Dimitrios: </p>
<hr />
<div>== Why PHP? ==<br />
One of the main objectives of Elphel products is to make them developer-friendly. Just opening of the camera internals (including source code, FPGA code, hardware schematics) is not enough without providing means to modify the cameras easily, and here [http://www.php.net PHP] comes to the rescue. It is powerful and efficient and is well known by many developers including those who may have problems to modify FPGA code or kernel drivers. It is much easier to try your custom applications written in PHP - just transfer the files to the camera (i.e. with ftp) and open them in the web browser.<br />
<br />
PHP supports custom extensions written in C and we'll work (and I hope not just we at Elphel) to provide more custom function to combine flexibility and ease of use of the PHP with efficiency of native compiled code.<br />
<br />
== PHP in Elphel cameras (models 353/363) ==<br />
Current version of PHP in Elphel cameras is 5.2.1, we will try to keep it (almost) current. PHP in the camera is working in [http://en.wikipedia.org/wiki/FastCGI Fast CGI] mode through [http://www.lighttpd.net/ Lighttpd]. Fast CGI mode does not restart applications (like traditional CGI does) for each HTTP request but rather keeps them alive to serve multiple requests. In the case of large application like PHP itself it makes a big performance difference and allows usage of the PHP scripts in the camera without the penalty of slow responses - something really undesirable for [http://www.linuxdevices.com/articles/AT5951285077.html AJAX applications].<br />
<br />
== How to use PHP in the camera ==<br />
It is very simple. It is the same as to try your HTML/JavaScript pages. You just need to ftp you script to one of the two locations (or their subdirectories) in the camera. Examples below assume you have the default camera IP='''192.168.0.9''':<br />
* '''/var/html''' (visible as '''http://192.168.0.9/var/''' in the web browser) - recommended for experiments, if something goes wrong you can just power-cycle the camera and all your changes will be gone<br />
* '''/usr/html''' (visible as ''http://192.168.0.9/''' in the web browser) - permanent (until next full firmware upgrade ) storage in the camera flash memory. This second location is more dangerous as you can change the installed files and rebooting will not restore the default behaviour. Flash memory has limited number of write cycles and can develop additional bad blocks during usage, so this location is recommended for "final" files, already tested in /var/html.<br />
<br />
You may also edit small text files with web-based editor. It does not allow to open non-existent file, but has an option to "Save As" - http://192.168.0.9/admin-bin/editcgi.cgi<br />
So you can try opening http://192.168.0.9/admin-bin/editcgi.cgi?file=/usr/html/phpinfo.php and then (modify and) save it to /var/html/test.php . When done - just open the following URL and watch the results of the script processing by in-camera PHP:<br />
<br />
'''http://192.168.0.9/var/test.php''' - run<br />
'''http://192.168.0.9/admin-bin/editcgi.cgi?file=/var/html/test.php''' - edit<br />
<br />
It is also possible to execute PHP scripts without the browser - camera startup scripts already use it for various initialization of the hardware. You can (silently) execute the same program in telnet session:<br />
php /var/html/test.php >/dev/null<br />
<br />
== Elphel PHP extension in the camera ==<br />
Since [[Release_notes|Elphel software version 7.1.6]] there is a custom extension module for PHP installed in the camera, you may also create your own extension as described [[PHP_in_Elphel_cameras#Creating_custom_PHP_extensions_for_Elphel_cameras|below]]. The existent extension exports several functions and defines constants.<br />
=== Constants, defined in ''elphel'' PHP extension ===<br />
see: [[Elphel_PHP_constants]]<br />
===''elphel'' extension functions ===<br />
<br />
''Note: Currently arguments (and array values) are supposed to be numbers, not strings - you may want to use $value+0 (instead of just $value) if $value may be a string (i.e. passed from _GET[])''--[[User:Andrey.filippov|Andrey.filippov]] 19:55, 14 December 2007 (CST)<br />
<br />
----<br />
==== elphel_get_P_value ====<br />
''long'' '''elphel_get_P_value''' (''long'' $address)<br />
<br />
This function returns value of one of internal camera parameters, as defined in [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/include/asm-cris/elphel/c313a.h?view=markup c313a.h] and documented in [[Elphel_PHP_constants]]. It is strongly recommended to use symbolic names as the numeric values may change in the future (as they already did multiple times). The values are maintained by the camera driver(s), usually they are updated when the driver programs the acquisition process.<br />
<br />
Example:<br />
echo elphel_get_P_value(ELPHEL_FP100S)/100; // will return current camera sensor frame rate in (frames per second);<br />
<br />
<br />
----<br />
==== elphel_set_P_value ====<br />
''void'' '''elphel_set_P_value''' (''long'' $address, ''long'' $data)<br />
<br />
Set a single camera parameter.<br />
<br />
Example:<br />
elphel_set_P_value(ELPHEL_QUALITY,100); // set JPEG compression quality to 100% - virtually lossless<br />
The elphel_get_P_value and elphel_set_P_value deal with different variables. Those that are read are validated to match the allowed values and may differ from those written (and they are only updated when sensor/compressor are programmed). You may read the parameters values that were written to the camera by adding ELPHEL_NUMBER to the parameter address, i.e<br />
echo elphel_get_P_value(ELPHEL_QUALITY+ELPHEL_NUMBER); // will output the compression quality as written<br />
<br />
<br />
----<br />
<br />
==== elphel_get_P_arr ====<br />
''array'' '''elphel_get_P_arr''' (''array'' $template)<br />
<br />
Read multiple camera parameters as an associative array, according to $template. $template should have elements with the key names matching the camera parameters names, same as defined [[Elphel_PHP_constants]], but without "ELPHEL_" prefix (all the elements with the other keys will be ignored). '''elphel_get_P_arr''' returns array, where element keys are the same as in $template (after removing of any unknown ones), and values are ''long'' values read from the camera.<br />
<br />
Example:<br />
$arr=array("foo"=>"", "WOI_LEFT" => "", "WOI_TOP" => "", "1", 3, "WOI_WIDTH" => 0, "WOI_HEIGHT" => 0);<br />
print_r ($arr);<br />
will return (5MPix sensor, full window):<br />
Array<br />
(<br />
[WOI_LEFT] => 0<br />
[WOI_TOP] => 0<br />
[WOI_WIDTH] => 2592<br />
[WOI_HEIGHT] => 1936<br />
)<br />
<br />
<br />
----<br />
<br />
==== elphel_set_P_arr ====<br />
''long'' '''elphel_set_P_arr''' (''array'' $input, ''long'' $frame, ''long'' $flag) )<br />
<br />
Write multiple camera parameters, provided as an associative array, where keys are parameter names same as defined [[Elphel_PHP_constants]], but without "ELPHEL_" prefix. Values should be numeric and integer, all other types are ignored.<br />
<br />
optional arguments:<br />
frame - frame number to write these parameters to - if not specified default framedelay (current frame + 3) is applied)<br />
flag - possible flags? <br />
<br />
Return value - frame number to which parameters were written <br />
<br />
Example:<br />
echo elphel_set_P_arr(array("WOI_LEFT" => 896, "WOI_TOP" => 672, "WOI_WIDTH" => 800, "WOI_HEIGHT" => 600));<br />
Will set 800x600 window in the center of the 5Mpix sensor and print frame number these changes where applied to<br />
<br />
<br />
----<br />
<br />
==== elphel_get_state ====<br />
''long'' '''elphel_get_state''' (''void'')<br />
There are multiple states defined in the camera, some are obsolete, the following are most common (no symbolic constants in PHP yet)<br />
* 0 - "reset" (i.e. no images yet acquired after power up)<br />
* 7 - "stopped" - sensor is constantly acquiring images (used for autoexposure), but compressor is stopped and no frames get to the [[Circbuf|circbuf]]<br />
* 8 - "running" - compressor is acquiring images to [[Circbuf|circbuf]]<br />
* 9 - "stopping" - compressor is compressing the last frame (transition from "running" to "stopped"<br />
*10 - "single_buffer" - compressor is acquiring full [[Circbuf|circbuf]] (plus one frame as it will notice the buffer is full after overrunning the original starting point) and then will stop<br />
<br />
<br />
----<br />
==== elphel_fpga_read ====<br />
''long'' '''elphel_fpga_read''' (''long $address'')<br />
<br />
Reads data from a certain fpga register address.<br />
<br />
Example:<br />
echo elphel_fpga_read(4); // outputs the data at address 4<br />
<br />
<br />
----<br />
==== elphel_fpga_write ====<br />
''void'' '''elphel_fpga_write''' (''long $address, long $data'')<br />
<br />
Writes data to a certain fpga register address.<br />
<br />
'''for Elphel 353 cameras these values can be the following (quoted from x353.h):'''<br />
187 #define X313_WA_WCTL 0 // write control register - 32<br />
188 #define X313_WA_DMACR 1 // DMA control register:<br />
189 // 17: DMA enable<br />
190 // 16: 0- raw, 1 - JPEG<br />
191 // 15-10: not used<br />
192 // 0-9: line length in long words<br />
193 #define X313_WA_SENSFPN 2 // Sensor/FPN control register:<br />
194 // [10] - testmode - if 1 generates gradient data (as Zoran chips) where pixel value = horizontal position<br />
195 // [9:7] - submode - subtract background (8 bits) mode (use di[7:0]):<br />
196 // 000 - no subtraction;<br />
197 // 001 - (finest) subtract 8 bit bkgnd from 12 bits pixels<br />
198 // 010 - shift 8bit bkgnd 1 bit left before applying<br />
199 // 011 - shift 8bit bkgnd 2 bits left before applying<br />
200 // 100 - shift 8bit bkgnd 2 bits left before applying<br />
201 // 101 - shift 8bit bkgnd 2 bits left before applying<br />
202 // fpn data to subtract should be a little less to add a "fat zero"<br />
203 // [6:4] - mpymode sensitivity correction mode (use di[15:8]):<br />
204 // 000 - no correction<br />
205 // 001 - fine correction (+/-3.125%)<br />
206 // 010 - fine correction (+/-6.25%)<br />
207 // 011 - fine correction (+/-12.5%)<br />
208 // 100 - +/- 25%<br />
209 // 101 - +/- 50%<br />
210 // [3] - wdth - word width: 0 - 8 bit, 1 - 16 bit (5 MSB == 0)<br />
211 // [2:0] scaling of 11 bit FPN result to fit in 8bit output:<br />
212 // 00 - default - use [9:1]<br />
213 // 01 - use [10:2] - to protect from saturation after applying mpymode<br />
214 // nominal range - 0..127<br />
215 // 10 - use [7:0] before saturation, "digital gain" == 4 (maximal)<br />
216 // 11 - use [8:1] before saturation, "digital gain" == 2<br />
217 <br />
218 // 31-8: not used<br />
219 // 7: 0 - normal, 1 - test mode (as Zoran)<br />
220 // 6-5: subtract FPN mode:<br />
221 // 0 - no subtraction<br />
222 // 1 (fine) - subtract 8-bit FPN from 10-bit pixel<br />
223 // 2 - multiply FPN by 2 before subtracting<br />
224 // 3 - multiply FPN by 4 before subtracting (full scfpcfale)<br />
225 // negative result is replaced by 0, decrease FPN data before applying for "fat 0"<br />
226 // 4-3: muliply by inverse sensitivity (sensitivity correction) mode:<br />
227 // 0 - no correction<br />
228 // 1 - fine (+/- 12.5%)<br />
229 // 2 - medium (+/- 25%)<br />
230 // 3 - maximal (+/- 50%)<br />
231 // 2: pixel depth:<br />
232 // 0 - 8 bits/pixel (needed for JPEG encoding)<br />
233 // 1 - 16 bits/pixel (only 11 LSBs are non-zero)<br />
234 // 1-0: scale (8 bit mode only):<br />
235 // 0 - full scale corresponds to sensor full scale if no correction was applied<br />
236 // 1 - divide by 2. This will guarantee against saturation after sensitivity correction was<br />
237 // applied. Nominal output range - 0..127<br />
238 // 2 - multiply by 4 (use 8 lower bits from sensor data)<br />
239 // 3 - multiply by 2<br />
240 // Result data is saturated by 255<br />
241 #define X313_WA_VIRTTRIG 3 // Virtual trigger threshold<br />
242 // 31-22 not used<br />
243 // 21-0 Trigger will fire if sum of pixels in a line<br />
244 // (after FPN processig) is more than this value.<br />
245 // Disabled if 0 - selected real (electrical) external trigger<br />
246 #define X313_WA_TRIG 4 // Sensor triggering<br />
247 // 31-3: not used<br />
248 // 2: Enable sensor (0 - abort at once)<br />
249 // 1: External Trigger (0 - internal)<br />
250 // 0: continuous acquisition (0 - single "frame" - actually number of lines specified)<br />
251 #define X313_WA_NLINES 5 // number of lines to acquire (afer trigger)<br />
252 // 31-11: not used<br />
253 // 10-0 : number of lines to acquire (in a frame or after the external trigger)<br />
254 //#define X313_WA_IRQM 6 // Interrupt mask (1 - enable, 0 - reset all but done)<br />
255 // 31-04: not used<br />
256 // 3: Done. Reset by writing to X313_WA_TRIG<br />
257 // 2: frame acquisition over<br />
258 // 1: external trigger<br />
259 // 0: frame sync (vacts)<br />
260 #define X313_WA_DCDC 7 // sensor DC-DC converter frequency settings<br />
261 // 31-05: not used<br />
262 // 4-0 0 - use internal clock (not sync)<br />
263 // 1..31 use divided pixel clock<br />
264 // for 20MHz use 5'h10,<br />
265 // else - N= (Fpix[MHz]/1.2)-1, if Fpix=20MHz,<br />
266 // N= 15.7->16=5'h10<br />
<br />
<br />
Example:<br />
elphel_fpga_write(4, 4); // Sets sensor triggering to an unused number and therefore disabling it -> acquire single frame to video buffer<br />
<br />
<br />
----<br />
<br />
==== elphel_reset_sensor ====<br />
''void'' '''elphel_reset_sensor''' (''void'')<br />
<br />
Reset the sensor settings, stop compressor (if it was running) and force sensor re-initialization.<br />
<br />
Example:<br />
elphel_reset_sensor();<br />
<br />
<br />
----<br />
==== elphel_program_sensor ====<br />
''void'' '''elphel_program_sensor''' (''long'' $nonstop)<br />
<br />
Applies written earlier (see [[PHP_in_Elphel_cameras#elphel_set_P_value|elphel_set_P_value]], [[PHP_in_Elphel_cameras#elphel_set_P_arr|elphel_set_P_arr]], [[PHP_in_Elphel_cameras#elphel_white_balance|elphel_white_balance]]) parameters to the cameras sensor and FPGA compressor. $nonstop determines if the acquisition should be restarted ($nonstop==0) or updated without stopping ($nonstop==1).<br />
<br />
'''Note:''' As of version 8.x, parameters are applied as they are set. Therefore, this function is no longer necessary.<br />
<br />
Example:<br />
elphel_program_sensor(0);<br />
<br />
<br />
----<br />
<br />
==== elphel_wait_frame ====<br />
''void'' '''elphel_wait_frame''' (''void'')<br />
<br />
Waits for the next frame to be compressed to the circular buffer - it is also the time when some other parameters (accessible with [[PHP_in_Elphel_cameras#elphel_get_P_value|elphel_get_P_value]], [[PHP_in_Elphel_cameras#elphel_get_P_arr|elphel_get_P_arr]]) are updated.<br />
<br />
Example:<br />
elphel_wait_frame();<br />
<br />
<br />
----<br />
<br />
==== elphel_wait_frame_abs ====<br />
''long'' '''elphel_wait_frame''' (''long'' frame)<br />
<br />
wait for absolute frame number (includes those that are not compressed) <br />
<br />
returns: frame number<br />
<br />
Example:<br />
elphel_wait_frame_abs(200);<br />
<br />
<br />
----<br />
<br />
==== elphel_skip_frames ====<br />
''long'' '''elphel_skip_frames''' (''long'' frames)<br />
<br />
skip some frames (includes those that are not compressed) - will work even if no frames are compressed <br />
<br />
returns: frame number<br />
<br />
Example:<br />
elphel_skip_frames(1);<br />
<br />
<br />
----<br />
<br />
==== elphel_compressor_run ====<br />
''void'' '''elphel_compressor_run''' (''void'')<br />
<br />
Turn the FPGA compressor on. Sensor should be already programmed ([[PHP_in_Elphel_cameras#|elphel_get_state] should return 7 (or higher) if tested prior to issuing ''elphel_compressor_run()'' command.<br />
<br />
Example:<br />
elphel_compressor_run();<br />
<br />
<br />
----<br />
==== elphel_compressor_stop ====<br />
''void'' '''elphel_compressor_stop''' (''void'')<br />
<br />
Stop camera compressor (will stop transferring more frames to the [[Circbuf|circular buffer]]. This command does not to be synchronized - compressor will finish current frame before stopping.<br />
<br />
Example:<br />
elphel_compressor_stop();<br />
<br />
<br />
----<br />
==== elphel_compressor_frame ====<br />
''void'' '''elphel_compressor_frame''' (''void'')<br />
<br />
Acquire one frame to the buffer (will apply written JPEG quality). Sensor should be already programmed - [[PHP_in_Elphel_cameras#|elphel_get_state]] should return 7 (or higher) if tested prior to issuing ''elphel_compressor_frame()'' command.<br />
<br />
Example:<br />
elphel_compressor_frame();<br />
<br />
<br />
----<br />
==== elphel_set_fpga_time ====<br />
''double'' '''elphel_set_fpga_time''' (''double'' seconds)<br />
<br />
Set FPGA internal timer that is used for time-stamping images and video frames. Internal counter has a 32-bit seconds counter and 12 bit microsecond one, so you may specify epoch - seconds since 01/01/1970.<br />
<br />
Returns time set as a ''double'' - it should match the input parameter after rounding to microseconds (resolution of the FPGA timer).<br />
<br />
Example:<br />
elphel_set_fpga_time(0x47565ad3);<br />
<br />
----<br />
==== elphel_get_fpga_time ====<br />
''double'' '''elphel_get_fpga_time''' (''void'')<br />
<br />
Copies current value of the FPGA timer registers to the global array (maybe read with several functions described above) and returns the the time as a ''double'' value, combining second as microseconds. The readout process guaranties that seconds and microseconds are sample simultaneously.<br />
<br />
Example:<br />
echo elphel_get_fpga_time();<br />
<br />
<!--<br />
----<br />
==== elphel_flush_cache ====<br />
''void'' '''elphel_flush_cache''' (''void'')<br />
<br />
This function is included to fight (hardware) cache coherency problems in mmap implementation for ETRAX FS processor. I'm not sure it will be really needed here - it needs some testing. If it will be proven it is needed - we'll incorporate it into appropriate functions that depend on it, if not it will just be removed.<br />
<br />
This function may be needed before [[PHP_in_Elphel_cameras#elphel_get_P_value|elphel_get_P_value]], [[PHP_in_Elphel_cameras#elphel_get_P_arr|elphel_get_P_arr]] to read data updated by the driver and/or before [[PHP_in_Elphel_cameras#elphel_program_sensor|elphel_program_sensor]], [[PHP_in_Elphel_cameras#elphel_compressor_run\elphel_compressor_run]], [[PHP_in_Elphel_cameras#elphel_compressor_frame|elphel_compressor_frame]] (if any of the parameters were changed with [[PHP_in_Elphel_cameras#elphel_set_P_value|elphel_set_P_value]], [[PHP_in_Elphel_cameras#elphel_set_P_arr|elphel_set_P_arr]] after the last call to elphel_flush_cache<br />
<br />
Example:<br />
elphel_flush_cache();<br />
--><br />
<br />
----<br />
==== elphel_white_balance ====<br />
''int'' '''elphel_white_balance''' ([''double'' thrsh [, ''double'' minfrac [, ''double'' rscale [, ''double'' bscale]]]])<br />
<br />
This function is designed to perform white balancing of the camera images. It relies on histogram calculation, "gamma" tables (curves) (both implemented in the FPGA) and the auto-exposure software in the camera (not yet included in this PHP extension, it is currently controlled through the separate CGI program). White balance uses the same window as auto-exposure, only data inside the specified rectangular window is processed.<br />
<br />
<br />
The goal of this function is to make the brightest areas in the image white (equal values of red, green and blue), it assumes that auto-exposure algorithm (operating after each frame acquired) already adjusted the brightness of the images so it uses all the 8-bit range and some pixel values are close to the maximal 255.<br />
<br />
<br />
The balancing is achieved by modification of the lookup tables ("gamma" tables, "curves") that map 12-bit (in 5MPix sensor, may be 10 or 14 bits with other devices) pixel data to the 8-bit pixel values used by the image/video compressor, the same values can be manually entered with [[PHP_in_Elphel_cameras#elphel_get_P_value|elphel_get_P_value]], [[PHP_in_Elphel_cameras#elphel_get_P_arr|elphel_get_P_arr]] functions applied to RSCALE and BSCALE parameters. The balancing is sensor-independent and it does not change sensor analog gains (where available), but if the required correction is significant, it is recommended to adjust those gains also, leaving only fine adjustment to the white balance algorithm - that will increase the dynamic range of the images.<br />
<br />
<br />
All function parameters are optional, but you can not skip the first one(s) if you would like to specify the next one(s), in that case default values should be explicitly entered.<br />
<br />
<br />
First parameter '''thrsh''' defines how bright should be pixels to be counted as white. Default value of '''0.98''' corresponds to 250 counts on 255 scale.<br />
<br />
<br />
Second parameter '''minfrac''' (default '''0.01''') tells how many pixels (at least) should be counted, as a fraction of the total number of the pixels in the specified window. If there are too few pixels with the brightness above the ''thrsh'', the ''thrsh'' will be lowered, to let more pixels to be counted.<br />
<br />
<br />
Next two parameters - '''rscale''' and '''bscale''' (both with default values of '''1.0''') can be used to apply manual bias to the automatically calculated values of red and blue scales (relative.to green)<br />
<br />
<br />
When this function is executed successfully it returns 0 (negative numbers indicate failure) in adjusts parameters (similar to manual [[PHP_in_Elphel_cameras#elphel_get_P_value|elphel_get_P_value]], [[PHP_in_Elphel_cameras#elphel_get_P_arr|elphel_get_P_arr]]), but that will propagate to the FPGA only after [[PHP_in_Elphel_cameras#elphel_program_sensor|elphel_program_sensor]] is executed. If you do not need to change any other parameters, you may use '''elphel_program_sensor(1)''' - in this case the image/video acquisition process will not be interrupted, frame timing will be preserved.<br />
<br />
<br />
As this function uses the histograms calculated from the previously acquired images, you actually need to acquire some. It is recommended you wait till the auto-exposure will adjust the brightness before executing elphel_white_balance. It also is not needed to run it as frequently as auto-exposure (for each frame), usually it is enough to call it only when the lighting conditions are changed.<br />
<br />
<br />
Examples:<br />
if (elphel_white_balance()>=0) elphel_program_sensor(1);<br />
or<br />
elphel_white_balance(0.98,0.01,1.0,1.2); // set bluish tint<br />
<br />
[http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/packages/web/353/php_top/whitebalance.php?view=markup whitebalance.php] is an example script that uses this function. It is installed in the camera and can be called as (provided camera has the default IP of 192.168.0.9):<br />
http://192.168.0.9/whitebalance.php<br />
or<br />
http://192.168.0.9/whitebalance.php?thrsh=0.98&minfrac=0.01&rscale=1.0&bscale=1.0<br />
<br />
----<br />
==== elphel_autoexposure_set ====<br />
''void'' '''elphel_autoexposure_set''' (''void'')<br />
<br />
This function controls auto-exposure in the camera. It is a quick modification that preserves the existent functionality (including interface) and just adds control from the PHP. This function itself does not take any parameters, it also does not return any data, It applies parameters that have to be already written by either of [[PHP_in_Elphel_cameras#elphel_set_P_value|elphel_set_P_value]], [[PHP_in_Elphel_cameras#elphel_set_P_arr|elphel_set_P_arr]], the current state of the auto-exposure algorithm can be read back using [[PHP_in_Elphel_cameras#elphel_get_P_value|elphel_get_P_value]], [[PHP_in_Elphel_cameras#elphel_get_P_arr|elphel_get_P_arr]] functions.<br />
<br />
===== auto-exposure software in the camera =====<br />
<br />
====== kernel space (driver) ======<br />
When the image from the sensor is acquired in the camera (even the compressor is off), software interrupt is generated and among others two things related to the auto-exposure control happen in the driver.<br />
* software prepares histograms calculated in the FPGA during the previous frame acquisition to be analysed by the user space application and make them available to the userspace applications through memory-mapped arrays (mmap) and<br />
* the previously calculated exposure is applied to the sensor to take effect during the next frame acquisition. Exposure time is the only parameter controlled automatically, you may also want to change analog gain(s) (sensitivity) to extend the range of the illumination levels that camera can handle. Most of this driver functionality is implemented in the [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/os/linux-2.6-tag--devboard-R2_10-4/arch/cris/arch-v32/drivers/elphel/hist353.c?view=markup hist353.c].<br />
<br />
====== user space (daemon) ======<br />
User space application [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/autoexp/autoexp.c?view=markup autoexp.c] (running as a daemon) processes the histograms and calculates the corrected value of the exposure, the result value is sent to the driver that applies the required correction. <br />
<br />
In addition the histograms (four of them - individually for each of the 4 Bayer components, including 2 sets of green pixels), driver provides applications with the lookup ("gamma") tables that are used by the FPGA to convert sensor pixel value (12 bit for the 5MPix sensor) into the 8-bit range, usually - non-linearly, controlled by "gamma" parameter. This tables are needed when processing the histograms, as FPGA calculates them after the LUT are applied to the pixel values.<br />
<br />
The auto-exposure configuration (input) parameters and the current state (output) can still be accessed using the current CGI script [http://elphel.cvs.sourceforge.net/elphel/elphel353-7.1/apps/autoexp/autoexpos.cgi.c?view=markup autoexpos.cgi.c] (as used by camvc user interface), alternatively they are directly accessible through the [[PHP_in_Elphel_cameras#elphel_set_P_value|elphel_set_P_value]], [[PHP_in_Elphel_cameras#elphel_set_P_arr|elphel_set_P_arr]], [[PHP_in_Elphel_cameras#elphel_get_P_value|elphel_get_P_value]], [[PHP_in_Elphel_cameras#elphel_get_P_arr|elphel_get_P_arr]] functions.<br />
<br />
===== auto-exposure algorithm in the camera =====<br />
<br />
The goal of the auto-exposure algorithm is to use as much as possible of the sensor dynamic range in the area of interest. It tries to adjust the exposure of the sensor so the whole range of the image pixel values (up to 255) are used (small number of pixels are usually still allowed to overexpose and be return the 255 limit value). It is possible to maintain the brightest pixels (disregarding just few "super-bright") near 255, but the it has 2 disadvantages:<br />
* sometimes with the back light you want to have good reproduction of darker objects while allowing the bright background to saturate<br />
* it is difficult to calculate required correction when the exposure is too long (some areas are over-saturated), because there is no way to know how much are the pixels saturated (if the image is too dim, the required exposure increase is just the ratio of 255 and the brightest pixels in the image)<br />
For these reasons a slightly different algorithm is used - the software tries to maintain specified part of the pixels in the window of interest to be below the specified level (usually high, but less than the full scale). In this case if the brightness of the scene suddenly increases (up to the ratio of the full scale pixel value to the specified threshold), the exposure correction can be calculated and applied in a single step. You may experiment with this algorithm using GUI in ''camvc'' camera web interface.<br />
<br />
<br />
===== parameters that control auto-exposure in the camera =====<br />
The following are parameters (it is possible to both their names as array keys with functions [[PHP_in_Elphel_cameras#elphel_set_P_arr|elphel_set_P_arr]], [[PHP_in_Elphel_cameras#elphel_get_P_arr|elphel_get_P_arr]], [[PHP_in_Elphel_cameras#elphel_get_P_warr|elphel_get_P_warr]]. There are also [[Elphel_PHP_constants|constants]] defined that use the same names with "ELPHEL_"prefix (i.e. ELPHEL_AUTOEXP_ON), these constants are useful with the functions [[PHP_in_Elphel_cameras#elphel_set_P_value|elphel_set_P_value]], [[PHP_in_Elphel_cameras#elphel_get_P_value|elphel_get_P_value]]. All the parameter values are ''long'' (32-bit) integers, you may read them back (as written) with [[PHP_in_Elphel_cameras#elphel_get_P_warr|elphel_get_P_warr]] function call. Te value of ELPHEL_HIST_NOT_CHANGE (65536) for any of these parameters mean that values corresponding to these parameters will not be updated.<br />
<br />
* '''AUTOEXP_ON''' - when set to '''1''' enables automatic exposure control, when '''0''' - disables it<br />
* '''AUTOEXP_RWIDTH''', '''AUTOEXP_RHEIGHT''' - relative width and height (in %) of the auto-exposure window width and height. It is used for histogram calculation in the FPGA and so controls not only auto-exposure, but also [[PHP_in_Elphel_cameras#elphel_white_balance|white balance]] and manual histogram processing<br />
* '''AUTOEXP_RLEFT''', '''AUTOEXP_RTOP''' - position of the auto-exposure window center, in %, counted from the left and top respectively<br />
* '''AUTOEXP_EXP_MAX''' - maximal exposure time (in 1/10000 of a second) allowed for the auto-exposure algorithm. It is recommended to set it equal to the frame period when video is streamed or recorded, otherwise in the low-light conditions the frame rate may drop to accommodate longer exposure times (frame period may never be shorter than the exposure time)<br />
* '''AUTOEXP_OVEREXP_MAX''' (old algorithm) - amount of pixels (fraction of all the pixels in the auto-exposure window) that are allowed to be overexposed, measured in 1/100 or a percent. This parameter is used when both '''AUTOEXP_S_PERCENT''' and '''AUTOEXP_S_INDEX''' (see below) are 0. This algorithm can be slow to handle over-exposed images and is not recommended.<br />
* '''AUTOEXP_S_PERCENT''' - amount of pixels that are controlled to have value below the specified '''AUTOEXP_S_INDEX''' (below), measured in 1/100 of a percent. Example: AUTOEXP_S_PERCENT=9400 means that 94% of pixels should have value lower than '''AUTOEXP_S_INDEX'''<br />
* '''AUTOEXP_S_INDEX''' - threshold for the pixel values (on a 0..255 8-bit scale) used together with '''AUTOEXP_S_PERCENT'''<br />
* '''AUTOEXP_SKIP_PMIN''' - minimal calculated exposure correction that will be applied (in 1/100 of a %). Value of 500 (default) means that exposure value will not be modified if the calculated value differs less than by 5% from the current one<br />
* '''AUTOEXP_SKIP_T''' minimal absolute exposure correction (in exposure steps, currently 1 step is 1/10000 sec), default value = 2<br />
* '''AUTOEXP_SKIP_PMAX''' - maximal allowed exposure correction that algorithm is allowed to apply (in 1/200 of a %, default is 5000 - 50%). If calculated exposure correction exceeds this value, it will not be applied immediately, the algorithm will wait for the next frame to make sure it was not an instant flash (i.e from some camera)<br />
* '''AEXPWND_WIDTH''', '''AEXPWND_HEIGHT''', '''AEXPWND_TOP''', '''AEXPWND_LEFT''' (when written to) behave similarly to '''AEXPWND_RWIDTH''', '''AEXPWND_RHEIGHT''', '''RAEXPWND_TOP''' and '''AEXPWND_RLEFT''', but come into effect immediately, not waiting for the [[PHP_in_Elphel_cameras#elphel_autoexposure_set|elphel_autoexposure_set()]] call. Writing to AEXPWND_RWIDTH, AEXPWND_RHEIGHT, RAEXPWND_TOP and AEXPWND_RLEFT and calling [[PHP_in_Elphel_cameras#elphel_autoexposure_set|elphel_autoexposure_set()]] updates the AEXPWND_WIDTH, AEXPWND_HEIGHT, AEXPWND_TOP, AEXPWND_LEFT<br />
<br />
<!--<br />
<br />
[AUTOEXP_EXP] => 801<br />
[AUTOEXP_SKIP_PMIN] => 500<br />
[AUTOEXP_SKIP_PMAX] => 5000<br />
[AUTOEXP_SKIP_T] => 2<br />
[AEXPWND_WIDTH] => 80<br />
[AEXPWND_HEIGHT] => 80<br />
[AEXPWND_TOP] => 50<br />
[AEXPWND_LEFT] => 50<br />
<br />
[ELPHEL_AUTOEXP_ON] => 76<br />
[ELPHEL_AUTOEXP_RWIDTH] => 77<br />
[ELPHEL_AUTOEXP_RHEIGHT] => 78<br />
[ELPHEL_AUTOEXP_RLEFT] => 79<br />
[ELPHEL_AUTOEXP_RTOP] => 80<br />
[ELPHEL_AUTOEXP_EXM_MAX] => 81<br />
[ELPHEL_AUTOEXP_OVEREXP_MAX] => 82<br />
[ELPHEL_AUTOEXP_S_PERCENT] => 83<br />
[ELPHEL_AUTOEXP_S_INDEX] => 84<br />
[ELPHEL_AUTOEXP_EXP] => 85<br />
[ELPHEL_AUTOEXP_SKIP_PMIN] => 86<br />
[ELPHEL_AUTOEXP_SKIP_PMAX] => 87<br />
[ELPHEL_AUTOEXP_SKIP_T] => 88<br />
[ELPHEL_AEXPWND_WIDTH] => 89<br />
[ELPHEL_AEXPWND_HEIGHT] => 90<br />
[ELPHEL_AEXPWND_TOP] => 91<br />
[ELPHEL_AEXPWND_LEFT] => 92<br />
[ELPHEL_HIST_NOT_CHANGE] => 65535<br />
--><br />
<br />
== Creating custom PHP extensions for Elphel cameras ==<br />
<br />
The followings steps are needed to create a custom PHP extension to run in Elphel product:<br />
<br />
* Create subdirectory of this (ext) directory for the new extension<br />
* Create files in this new directory - at least<br />
** config.m4<br />
** <your name>.h<br />
** <yourname>.c<br />
<br />
You may use ext_skel script to automate this process or follow a nice tutorial by Sara Goleman '''[http://devzone.zend.com/node/view/id/1021 Extension Writing Part I: Introduction to PHP and Zend]''' . You may also like to read her book, "Extending and Embedding PHP".<br />
=== config.m4 ===<br />
<br />
PHP_ARG_ENABLE(hello, whether to enable Hello World support, [ --enable-hello Enable Hello World support])<br />
if test "$PHP_HELLO" = "yes"; then<br />
AC_DEFINE(HAVE_HELLO, 1, [Whether you have Hello World])<br />
PHP_NEW_EXTENSION(hello, hello.c, $ext_shared)<br />
fi<br />
<br />
=== php_hello.h ===<br />
<br />
#ifndef PHP_HELLO_H<br />
#define PHP_HELLO_H 1<br />
#define PHP_HELLO_WORLD_VERSION "1.0"<br />
#define PHP_HELLO_WORLD_EXTNAME "hello"<br />
PHP_FUNCTION(hello_world);<br />
extern zend_module_entry hello_module_entry;<br />
#define phpext_hello_ptr &hello_module_entry<br />
#endif<br />
<br />
=== hello.c ===<br />
<br />
#ifdef HAVE_CONFIG_H<br />
#include "config.h"<br />
#endif<br />
#include "php.h"<br />
#include "php_hello.h"<br />
static function_entry hello_functions[] = {<br />
PHP_FE(hello_world, NULL)<br />
{NULL, NULL, NULL}<br />
};<br />
zend_module_entry hello_module_entry = {<br />
#if ZEND_MODULE_API_NO >= 20010901<br />
STANDARD_MODULE_HEADER,<br />
#endif<br />
PHP_HELLO_WORLD_EXTNAME,<br />
hello_functions,<br />
NULL,<br />
NULL,<br />
NULL,<br />
NULL,<br />
NULL,<br />
#if ZEND_MODULE_API_NO >= 20010901<br />
PHP_HELLO_WORLD_VERSION,<br />
#endif<br />
STANDARD_MODULE_PROPERTIES<br />
};<br />
#ifdef COMPILE_DL_HELLO<br />
ZEND_GET_MODULE(hello)<br />
#endif<br />
PHP_FUNCTION(hello_world)<br />
{<br />
RETURN_STRING("Hello World", 1);<br />
}<br />
<br />
<br />
<br />
With the 3 files created you need to cd to the extension directory and run<br />
../../elphize<br />
That will generate support files (running phpize script) so you'll just need to run<br />
make install<br />
to have the new extension (as a dynamic library) installed in the target directory tree and included in the camera flash image.<br />
<br />
You will need to add "extension=<your_extension_name>" to the php.ini file to be activated.<br />
<br />
When troubleshooting extensions you may also want to try your scripts from the command line in the camera - in that case the stdout will be visible and PHP+your module will be able to complain about Segmentation faults (when invoked from the browser it you will get Error 500 at best if that happens). And you'll have to manually restart web server + PHP after module changes (remember - Fast CGI does not kill PHP after end of HTTP request?)<br />
<br />
== Known problems ==<br />
<br />
Function ''[http://us.php.net/manual/en/function.fread.php fread]'' in PHP always tries to read 8192 bytes even if the length parameter is <8192, that causes problems when read from devices (i.e. i2c) being too slow or causing side effects. It is considered [http://bugs.php.net/bug.php?id=21641 feature, not a bug].<br />
<br />
A quick fix will be to change the driver to always read minimal (1/2/3/4 bytes depending on the nature of the data) if the count passed to device read function is 8192.<br />
<br />
[[Category:Software]]<br />
[[Category:PHP]]</div>Dimitrioshttps://wiki.elphel.com/index.php?title=User:Dimitrios&diff=11078User:Dimitrios2012-01-05T14:51:13Z<p>Dimitrios: Added link to tclepeg in github</p>
<hr />
<div>Some notes that could be useful:<br />
<br />
=Recording and live preview=<br />
<br />
Is there a way to record and, at the same time, watch a reduced resolution version in a cheap tablet or portable PC / notebook?<br />
<br />
'''epeg''' is a super-fast library for resizing jpegs. It offers an improvement of at least an order of magnitude over other known libraries like ImageMagick. I just compiled a command line version and these are the results:<br />
<br />
$ time ./resize test.jpeg test.jpg<br />
<br />
real 0m0.063s<br />
user 0m0.060s<br />
sys 0m0.000s<br />
<br />
$ time convert -resize 426x640 test.jpeg test.jpg<br />
<br />
real 0m1.158s<br />
user 0m1.048s<br />
sys 0m0.052s<br />
<br />
The improvement in the above case 18 times faster.<br />
'''resize''' is a little C program crafted for resizing a 2592x3888 image to a 426x640 one using the epeg library. Convert is ImageMagick's convert utility. It took resize '''63 msec''' against '''1158 msec''' for ImageMagick.<br />
<br />
If this functionality is included in the camera it could do jpeg resize in-memory on-the-fly and spare even more by avoiding the read/write to disk that is involved in the above test.<br />
<br />
'''epeg''' was a stand-alone utility that is now included in Enlightenment. The [http://maemo.gitorious.org/maemo-af/epeg Maemo] sources for epeg compile without a change in Kubuntu. There is also a [http://github.com/rsky/php-epeg PHP extension] for epeg.<br />
<br />
<br />
'''epeg''' does not decode the JPEG, it only decodes the DCT coefficients needed to reconstruct an image of the size desired.<br />
<br />
From the README:<br />
<br />
What is Epeg?<br />
<br />
An IMMENSELY FAST JPEG thumbnailer library API.<br />
<br />
Why write this? It's a convenience library API to using libjpeg to load JPEG<br />
images destined to be turned into thumbnails of the original, saving<br />
information with these thumbnails, retrieving it and managing to load the image<br />
ready for scaling with the minimum of fuss and CPU overhead. <br />
<br />
This means it's insanely fast at loading large JPEG images and scaling them<br />
down to tiny thumbnails. It's speedup will be proportional to the size<br />
difference between the source image and the output thumbnail size as a<br />
count of their pixels.<br />
<br />
It makes use of libjpeg features of being able to load an image by only<br />
decoding the DCT coefficients needed to reconstruct an image of the size<br />
desired. This gives a massive speedup. If you do not try and access the pixels<br />
in a format other than YUV (or GRAY8 if the source is grascale) then it also<br />
avoids colorspace conversions as well.<br />
<br />
In the '''libepeg''' library, there is a function epeg_memory_open() that reads a JPEG image from memory instead of a file. Then the resize can be applied and the result can be sent out instead of the original JPEG.<br />
<br />
The C program that does the resize is this:<br />
#include <stdio.h><br />
#include <stdlib.h><br />
#include <stddef.h><br />
#include <dirent.h><br />
<br />
#include "Epeg.h"<br />
<br />
int<br />
main(int argc, char **argv)<br />
{<br />
Epeg_Image *im;<br />
<br />
if (argc != 3)<br />
{<br />
printf("Usage: %s input.jpg thumb.jpg\n", argv[0]);<br />
exit(0);<br />
}<br />
im = epeg_file_open(argv[1]);<br />
if (!im)<br />
{<br />
printf("Cannot open %s\n", argv[1]);<br />
exit(-1);<br />
}<br />
<br />
epeg_decode_size_set (im, 426, 640);<br />
epeg_quality_set (im, 75);<br />
epeg_thumbnail_comments_enable (im, 1);<br />
epeg_file_output_set (im, argv[2]);<br />
epeg_encode (im);<br />
epeg_close (im);<br />
<br />
return 0;<br />
}<br />
<br />
There is also a '''tclepeg''' package allowing the use of the epeg library from TCL, for the Linux i386 platform [http://github.com/dzach/tclepeg]</div>Dimitrioshttps://wiki.elphel.com/index.php?title=Wishlist&diff=11017Wishlist2011-12-31T17:33:07Z<p>Dimitrios: </p>
<hr />
<div>As user I noticed some things I wanted to have on my camera, I hope anyone that has ideas can add them here. <br />
What features are you waiting for?<br />
What software components are still missing that you cannot live without?<br />
<br />
<br />
==Software==<br />
If a project has been completed just add the developer that did it, or is busy on it.<br />
=== Sensor ===<br />
* [[Dead/Hot pixel correction]]<br />
<br />
=== Compass ===<br />
* '''DONE''' [[Implement calibration]]<br />
<br />
=== Networking ===<br />
* [[DHCP (timeouted) and DNS-SD]]<br />
* [[GigaBit ethernet]]<br />
* Zeroconf (Rendezvous) for LAN device announcing<br />
* [[http://opensoundcontrol.org OpenSound Control]] [[http://en.wikipedia.org/wiki/OpenSound_Control OpenSound Control on wikipedia]], [[http://www.linuxjournal.com/content/introduction-osc introduction to OSC on linuxjournal]]<br />
* CF Ethernet card support [[http://www.pocketpcfaq.com/peripherals/cfethernet.htm CF 10/100 Ethernet cards list]]<br />
* CF WiFi card support [[http://www.google.ru/url?sa=t&source=web&ct=res&cd=1&url=http%3A%2F%2Fwww.linksys.com%2Fservlet%2FSatellite%3Fchildpagename%3DUS%252FLayout%26packedargs%3Dc%253DL_Product_C2%2526cid%253D1115416826419%26pagename%3DLinksys%252FCommon%252FVisitorWrapper&ei=2CkjSb2pB4PG0gXtx92CAg&usg=AFQjCNFGaaRKL7uwQ7UNQQsxbdf9mrsoeA&sig2=wYBsCu8pfOyTJt57UW57EA WCF54G]]<br />
* CF USB card support [[http://www.twin-paradox.com/SEPDA.html SolarExpress]] [[http://www.ratocsystems.com/english/products/CFU2U.html CFU2]]<br />
* External USB Display support [http://gizmodo.com/5116061/mimo-um+750-7+inch-usb-display-lightning-review Mimo UM-750 7-inch].<br />
<br />
=== Fastest Boot ===<br />
* [[Fast Boot]]<br />
<br />
=== APIs ===<br />
* [[C API]]<br />
* [[SOAP API]]<br />
<br />
=== UDMA support ===<br />
* Enable [[UDMA]] in the Axis kernel. Needed to support most fast CF cards, will also boost speed on SATA.<br />
<br />
=== Debayer Algorithmn ===<br />
* Higher image quality debayer algorithmn FPGA implementation -> [http://scien.stanford.edu/class/psych221/projects/99/tingchen/algodep/vargra.html VNG]<br />
<br />
==Hardware==<br />
What will the next elphel camera most likely entitled '''Elphel 373''' be like?<br />
<br />
===Power Supply===<br />
* optional 5-36V supply over additional jack [http://focus.ti.com/docs/prod/folders/print/tps5430.html DC/DC] [http://focus.ti.com/docs/prod/folders/print/tps23750.html POE] [http://www.rlocman.ru/review/article.html?di=52247 TI Article]<br />
<br />
===Sensor===<br />
* Vignetting hardware correction<br />
* Lens distortion hardware correction<br />
* Fixed pattern noise (FPN) correction<br />
* Flash mode for rolling shutter<br />
* Make image thumbnails (binning 8x8 from DCT[0,0] data)<br />
'''Position adjustment'''<br />
*initial focus/pan/tilt sensor adjustment<br />
*Square shaped SFE and equidistant holes for easy change of orientation<br />
<br />
'''Interface'''<br />
*group VLDS pairs in flexible cable from sensor to board<br />
*[[CCD table|CCD sensors]]<br />
<br />
'''Sony IMX021'''<br />
*designed for DSLRs (possibly the sensor used in Nikon D300 / D90)<br />
*12.4 MPix<br />
*5.5 µm pixel<br />
*0.18 µm technology<br />
*28mm x 22.2 mm APS-C sized 1.8" image area (28.4 mm diagonal)<br />
*12 bit column ADC<br />
*10.4 fps in 12.4 MPix mode<br />
*on-chip noise reduction<br />
*parallel A/D for every pixel coloumn<br />
<br />
===CPU===<br />
*USB2.0 Support<br />
<br />
===External data sensors support===<br />
*'''DONE''' GPS<br />
*'''DONE''' Compass<br />
*Dry contact (simply switch event)<br />
*'''DONE''' RFID<br />
*Proximity<br />
*Environment sensors: Temperature/Humidity/Pressure/Illuminance/Loudness/.. [http://www.catnip.co.uk/wx Open Weather], [http://www.sciproj.com/FeaturedVendorProduct.aspx?uid=1208227 EL-USB-RT], [http://www.raphnet.net/electronique/usbtenki/index_en.php USBTenki], [http://www.sparkfun.com/commerce/product_info.php?products_id=8311 USB Weather Board], [http://www.farnell.com/datasheets/129494.pdf CY3271-EXP1 (PSoC Environmental Sensing Kit)]<br />
*Futaba servo captute interface (for robots)<br />
<br />
===External control===<br />
*USB3.0 Support<br />
*Futaba servo control interface (for robots) [http://www.parallax.com/Store/Accessories/MotorServoControllers/tabid/160/CategoryID/35/List/0/Level/a/ProductID/346/Default.aspx?SortField=ProductName%2CProductName PSC] [http://www.endurance-rc.com/pantilt.html Pan&Tilt] [http://www.openservo.com/ OpenServo] [http://www.embeddedrelated.com/usenet/embedded/show/46581-1.php Verilog solution] [http://www.sparkfun.com/commerce/product_info.php?products_id=8897 Polulu]<br />
*Relay control<br />
*CAN support [http://www.qprotos.com/quickcan.htm quickcan] [http://www.gridconnect.com/usbcanin.html USB CAN Adapter]<br />
*DMX512 support [http://en.wikipedia.org/wiki/DMX-512 DMX512]<br />
*Secure Digital support [http://www.delkin.com/products/adapters/sd-to-cf/sd-to-cf.html CF-SD]</div>Dimitrioshttps://wiki.elphel.com/index.php?title=Wishlist&diff=11016Wishlist2011-12-31T17:29:32Z<p>Dimitrios: </p>
<hr />
<div>As user I noticed some things I wanted to have on my camera, I hope anyone that has ideas can add them here. <br />
What features are you waiting for?<br />
What software components are still missing that you cannot live without?<br />
<br />
<br />
==Software==<br />
If a project has been completed just add the developer that did it, or is busy on it.<br />
=== Sensor ===<br />
* [[Dead/Hot pixel correction]]<br />
<br />
=== Compass ===<br />
* '''DONE''' [[Implement calibration]]<br />
<br />
=== Networking ===<br />
* [[DHCP (timeouted) and DNS-SD]]<br />
* [[GigaBit ethernet]]<br />
* Zeroconf (Rendezvous) for LAN device announcing<br />
* [[http://opensoundcontrol.org OpenSound Control]] [[http://en.wikipedia.org/wiki/OpenSound_Control OpenSound Control on wikipedia]], [[http://www.linuxjournal.com/content/introduction-osc introduction to OSC on linuxjournal]]<br />
* CF Ethernet card support [[http://www.pocketpcfaq.com/peripherals/cfethernet.htm CF 10/100 Ethernet cards list]]<br />
* CF WiFi card support [[http://www.google.ru/url?sa=t&source=web&ct=res&cd=1&url=http%3A%2F%2Fwww.linksys.com%2Fservlet%2FSatellite%3Fchildpagename%3DUS%252FLayout%26packedargs%3Dc%253DL_Product_C2%2526cid%253D1115416826419%26pagename%3DLinksys%252FCommon%252FVisitorWrapper&ei=2CkjSb2pB4PG0gXtx92CAg&usg=AFQjCNFGaaRKL7uwQ7UNQQsxbdf9mrsoeA&sig2=wYBsCu8pfOyTJt57UW57EA WCF54G]]<br />
* CF USB card support [[http://www.twin-paradox.com/SEPDA.html SolarExpress]] [[http://www.ratocsystems.com/english/products/CFU2U.html CFU2]]<br />
* External USB Display support [http://gizmodo.com/5116061/mimo-um+750-7+inch-usb-display-lightning-review Mimo UM-750 7-inch].<br />
<br />
=== Fastest Boot ===<br />
* [[Fast Boot]]<br />
<br />
=== APIs ===<br />
* [[C API]]<br />
* [[SOAP API]]<br />
<br />
=== UDMA support ===<br />
* Enable [[UDMA]] in the Axis kernel. Needed to support most fast CF cards, will also boost speed on SATA.<br />
<br />
=== Debayer Algorithmn ===<br />
* Higher image quality debayer algorithmn FPGA implementation -> [http://scien.stanford.edu/class/psych221/projects/99/tingchen/algodep/vargra.html VNG]<br />
<br />
==Hardware==<br />
What will the next elphel camera most likely entitled '''Elphel 373''' be like?<br />
<br />
===Power Supply===<br />
* optional 5-36V supply over additional jack [http://focus.ti.com/docs/prod/folders/print/tps5430.html DC/DC] [http://focus.ti.com/docs/prod/folders/print/tps23750.html POE] [http://www.rlocman.ru/review/article.html?di=52247 TI Article]<br />
<br />
===Sensor===<br />
* Vignetting hardware correction<br />
* Lens distortion hardware correction<br />
* Fixed pattern noise (FPN) correction<br />
* Flash mode for rolling shutter<br />
* Make image thumbnails (binning 8x8 from DCT[0,0] data)<br />
'''Position adjustment'''<br />
*initial focus/pan/tilt sensor adjustment<br />
*Square form for easy change of orientation<br />
<br />
'''Interface'''<br />
*group VLDS pairs in flexible cable from sensor to board<br />
*[[CCD table|CCD sensors]]<br />
<br />
'''Sony IMX021'''<br />
*designed for DSLRs (possibly the sensor used in Nikon D300 / D90)<br />
*12.4 MPix<br />
*5.5 µm pixel<br />
*0.18 µm technology<br />
*28mm x 22.2 mm APS-C sized 1.8" image area (28.4 mm diagonal)<br />
*12 bit column ADC<br />
*10.4 fps in 12.4 MPix mode<br />
*on-chip noise reduction<br />
*parallel A/D for every pixel coloumn<br />
<br />
===CPU===<br />
*USB2.0 Support<br />
<br />
===External data sensors support===<br />
*'''DONE''' GPS<br />
*'''DONE''' Compass<br />
*Dry contact (simply switch event)<br />
*'''DONE''' RFID<br />
*Proximity<br />
*Environment sensors: Temperature/Humidity/Pressure/Illuminance/Loudness/.. [http://www.catnip.co.uk/wx Open Weather], [http://www.sciproj.com/FeaturedVendorProduct.aspx?uid=1208227 EL-USB-RT], [http://www.raphnet.net/electronique/usbtenki/index_en.php USBTenki], [http://www.sparkfun.com/commerce/product_info.php?products_id=8311 USB Weather Board], [http://www.farnell.com/datasheets/129494.pdf CY3271-EXP1 (PSoC Environmental Sensing Kit)]<br />
*Futaba servo captute interface (for robots)<br />
<br />
===External control===<br />
*USB3.0 Support<br />
*Futaba servo control interface (for robots) [http://www.parallax.com/Store/Accessories/MotorServoControllers/tabid/160/CategoryID/35/List/0/Level/a/ProductID/346/Default.aspx?SortField=ProductName%2CProductName PSC] [http://www.endurance-rc.com/pantilt.html Pan&Tilt] [http://www.openservo.com/ OpenServo] [http://www.embeddedrelated.com/usenet/embedded/show/46581-1.php Verilog solution] [http://www.sparkfun.com/commerce/product_info.php?products_id=8897 Polulu]<br />
*Relay control<br />
*CAN support [http://www.qprotos.com/quickcan.htm quickcan] [http://www.gridconnect.com/usbcanin.html USB CAN Adapter]<br />
*DMX512 support [http://en.wikipedia.org/wiki/DMX-512 DMX512]<br />
*Secure Digital support [http://www.delkin.com/products/adapters/sd-to-cf/sd-to-cf.html CF-SD]</div>Dimitrioshttps://wiki.elphel.com/index.php?title=User:Dimitrios&diff=11000User:Dimitrios2011-12-18T02:25:21Z<p>Dimitrios: Created page with "Some notes that could be useful: =Recording and live preview= Is there a way to record and, at the same time, watch a reduced resolution version in a cheap tablet or portable P..."</p>
<hr />
<div>Some notes that could be useful:<br />
<br />
=Recording and live preview=<br />
<br />
Is there a way to record and, at the same time, watch a reduced resolution version in a cheap tablet or portable PC / notebook?<br />
<br />
'''epeg''' is a super-fast library for resizing jpegs. It offers an improvement of at least an order of magnitude over other known libraries like ImageMagick. I just compiled a command line version and these are the results:<br />
<br />
$ time ./resize test.jpeg test.jpg<br />
<br />
real 0m0.063s<br />
user 0m0.060s<br />
sys 0m0.000s<br />
<br />
$ time convert -resize 426x640 test.jpeg test.jpg<br />
<br />
real 0m1.158s<br />
user 0m1.048s<br />
sys 0m0.052s<br />
<br />
The improvement in the above case 18 times faster.<br />
'''resize''' is a little C program crafted for resizing a 2592x3888 image to a 426x640 one using the epeg library. Convert is ImageMagick's convert utility. It took resize '''63 msec''' against '''1158 msec''' for ImageMagick.<br />
<br />
If this functionality is included in the camera it could do jpeg resize in-memory on-the-fly and spare even more by avoiding the read/write to disk that is involved in the above test.<br />
<br />
'''epeg''' was a stand-alone utility that is now included in Enlightenment. The [http://maemo.gitorious.org/maemo-af/epeg Maemo] sources for epeg compile without a change in Kubuntu. There is also a [http://github.com/rsky/php-epeg PHP extension] for epeg.<br />
<br />
<br />
'''epeg''' does not decode the JPEG, it only decodes the DCT coefficients needed to reconstruct an image of the size desired.<br />
<br />
From the README:<br />
<br />
What is Epeg?<br />
<br />
An IMMENSELY FAST JPEG thumbnailer library API.<br />
<br />
Why write this? It's a convenience library API to using libjpeg to load JPEG<br />
images destined to be turned into thumbnails of the original, saving<br />
information with these thumbnails, retrieving it and managing to load the image<br />
ready for scaling with the minimum of fuss and CPU overhead. <br />
<br />
This means it's insanely fast at loading large JPEG images and scaling them<br />
down to tiny thumbnails. It's speedup will be proportional to the size<br />
difference between the source image and the output thumbnail size as a<br />
count of their pixels.<br />
<br />
It makes use of libjpeg features of being able to load an image by only<br />
decoding the DCT coefficients needed to reconstruct an image of the size<br />
desired. This gives a massive speedup. If you do not try and access the pixels<br />
in a format other than YUV (or GRAY8 if the source is grascale) then it also<br />
avoids colorspace conversions as well.<br />
<br />
In the '''libepeg''' library, there is a function epeg_memory_open() that reads a JPEG image from memory instead of a file. Then the resize can be applied and the result can be sent out instead of the original JPEG.<br />
<br />
The C program that does the resize is this:<br />
#include <stdio.h><br />
#include <stdlib.h><br />
#include <stddef.h><br />
#include <dirent.h><br />
<br />
#include "Epeg.h"<br />
<br />
int<br />
main(int argc, char **argv)<br />
{<br />
Epeg_Image *im;<br />
<br />
if (argc != 3)<br />
{<br />
printf("Usage: %s input.jpg thumb.jpg\n", argv[0]);<br />
exit(0);<br />
}<br />
im = epeg_file_open(argv[1]);<br />
if (!im)<br />
{<br />
printf("Cannot open %s\n", argv[1]);<br />
exit(-1);<br />
}<br />
<br />
epeg_decode_size_set (im, 426, 640);<br />
epeg_quality_set (im, 75);<br />
epeg_thumbnail_comments_enable (im, 1);<br />
epeg_file_output_set (im, argv[2]);<br />
epeg_encode (im);<br />
epeg_close (im);<br />
<br />
return 0;<br />
}</div>Dimitrioshttps://wiki.elphel.com/index.php?title=Talk:10369&diff=10999Talk:103692011-12-16T19:55:32Z<p>Dimitrios: </p>
<hr />
<div>Clicking this:<br />
<br />
http://192.168.0.9/i2c.php?width=8&bus=1&adr=0x5102<br />
<br />
returns this:<br />
<br />
<nowiki><i2c><br />
<width>8</width><br />
<bus>1</bus><br />
<slave>0xa2</slave><<br />
<adr>20738</adr><br />
<hex_adr>0x5102</hex_adr><br />
<data>68</data><br />
<rdata>68</rdata><br />
<hex_data>0x44</hex_data><br />
</i2c></nowiki><br />
<br />
However, seconds cannot be '68', can they? It looks like the hex_data value is the actual seconds but presented in decimal not hex. 'data' and 'rdata' jump up when hex_data changes decade.<br />
----<br />
When clicking this link:<br />
<br />
http://192.168.0.9/i2c.php?cmd=readCMOS<br />
<br />
I get:<br />
<br />
<nowiki><i2c><br />
<error>"Address (adr or raw) or width are not specified or are not positive."</error><br />
<usage>"open URL: i2c.php?width=www&bus=bbb&adr=aaa&data=ddd"</usage><br />
</i2c></nowiki></div>Dimitrioshttps://wiki.elphel.com/index.php?title=Talk:10369&diff=10998Talk:103692011-12-16T19:45:47Z<p>Dimitrios: </p>
<hr />
<div>When clicking this link:<br />
<br />
http://192.168.0.9/i2c.php?cmd=readCMOS<br />
<br />
I get:<br />
<br />
<i2c><br />
<error>"Address (adr or raw) or width are not specified or are not positive."</error><br />
<usage>"open URL: i2c.php?width=www&bus=bbb&adr=aaa&data=ddd"</usage><br />
</i2c></div>Dimitrioshttps://wiki.elphel.com/index.php?title=Talk:10369&diff=10997Talk:103692011-12-16T19:42:51Z<p>Dimitrios: Created page with "When clicking this link I get: <i2c> <error>"Address (adr or raw) or width are not specified or are not positive."</error> <usage>"open URL: i2c.php?width=www&bus=bbb&adr=aa..."</p>
<hr />
<div>When clicking this link I get:<br />
<br />
<i2c><br />
<error>"Address (adr or raw) or width are not specified or are not positive."</error><br />
<usage>"open URL: i2c.php?width=www&bus=bbb&adr=aaa&data=ddd"</usage><br />
</i2c></div>Dimitrios