This software might be dangerous. If you use this software, and it breaks your camera it is not my fault.
First, there was QVplay. This is an excellent set of programs by Ken-Ichi Hayashi. My first qv-300 webcam used this software, and a perl script that I put together. Due to odd problems, it has to take two pictures for each one sent, because I kept getting picture errors on the first picture. That, combined with slow Sun serial ports let me get about one picture per minute.
Next, there was the server push CGI. This CGI works by polling a file and noticing when it changes, then pushes it using the appropriate protocol. Note that the perl script had to be set up to copy the file to the web server, because NFS can't be trusted to update file modification times in a timely fashion.
Next, QVplay and my perl script were replaced with
my own standalone program. The jpeg code
came straight from QVplay, the rest was rewritten from scratch (but still
using QVplay as a reference) mainly for my own tinkering purposes. I
was able to eliminate the two-picture requirement, and speed the software
up in other ways also. It uses two include files from QVplay:
jpegtab_f.h, and
cam2jpgtab.h.
(Note that I also got a new Sun on my desk, a Sun Blade, and for a while
it refused to talk to the camera, but now that I have the latest patches,
it happily communicates at 115200 Baud, allowing me to get one image
every 15 seconds or so.)
Finally, I created a
script that handled the timestamping,
and copying of the file to the
various locations where it is needed either by the push or pull web pages.
Requires some NetPBM tools and cjpeg/djpeg for the timestamping.
Links
Fine's Home
Send Me Email