[sane-devel] Getting Clever CAM 360 working

[kilgota at banach.math.auburn.edu]

On Wed, 14 Sep 2005, Martin wrote:

> I installed libgphoto2-2.1.6.
>
> Edited the source file pdc640.c in the directory, 
> libgphoto2-2.1.6/camlibs/polaroid/
>
> and added the lines,
>
> {"Clever CAM 360", 0x797, 0x8001, {
> jd350e,
> BAYER_TILE_BGGR,
> &jd350e_postprocessing_and_flip,
> "scope%04i.ppm"
> }
> },
>
> which is similar to the lines already there for,
> {"GrandTek ScopeCam", 0x797, 0x801c, {
> jd350e,
> BAYER_TILE_BGGR,
> &jd350e_postprocessing_and_flip,
> "scope%04i.ppm"
> }
> },
>
>
> and did a make and make install.
>
The command for getting photos out of the camera is

gphoto2 -P (all photos on the camera)

gphoto2 --summary (displays a summary screen of information)

gphoto2 --get-all-raw-data (dumps all photos' data in raw format, into 
files)

There is a man page for gphoto2, BTW

Oh... Perhaps you do not have gphoto2, either. It is the command front-end 
for the cameras supported by libgphoto2. Libgphoto2 just contains all of 
the data about how each camera works.

To install gphoto2 (which if you did not have it from your distro you 
will also need), you need to

1. Go back to the same place and get it.

2. Do ./configure. If you get an error message about PKG_CONFIG_PATH or 
something like that, then you need to add /usr/local/lib/pkgconfig to the 
path. OR in a pinch it might work to symlink the file 
/usr/local/lib/pkgconfig/libgphoto2(whatever) to /usr/lib/pkgconfig.

The significance of "pkgconfig" is that it is some new tool to help the 
compiler to know what libraries are in the system, and in what versions. 
Very important, no doubt, and also a little bit of a pain in the behind.

3. Make and make install.

Now, of course, you understand that in all likelihood something will not 
work quite right at this point. That would be a miracle. At the very 
least, the camera might give the photos with the colors wrong, or upsice 
down, or something (see all of those config options, some of which you 
just copied, guessing, for the new camera!). So you can always run

gphoto2 (option) --debug and get debug output. If you do

gphoto2 (option) --debug 2>debug it will put the debug output into a file 
in the current directory, called "debug" and then the file can be 
inspected at leisure.

Hope this helps.

Theodore Kilgore