l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2001 Dec 30 17:10

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
[vox-tech] polaroid pdc700 - partial success
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[vox-tech] polaroid pdc700 - partial success

here is an email i sent to the gphoto developer's list.  if anybody knows
serial programming, can you answer the questions at the bottom of the email?

hello all,

i've had a (very) partial success getting the polaroid pdc700 recognized
under linux.   here is what i did:

gphoto2 --port "serial:/dev/ttyS0" --camera "Polaroid DC700" --summary --debug

here's the output:

1  gp_port: gp_port_write: (size=00005) DATA: 40 00 02 01 01 

using comlite32, i determined that the send string (line 1) is correct.
 . all commands begin with 0x40.
 . the next 2 bytes represents the number of bytes sent to the camera.
   in this case, "0x00 0x02" corresponding to the following "0x01 0x01".
 . the next 0x01 (i think) is the camera initialization string
 . the last 0x01 is the checksum of all bytes between the 2-byte length
   and the last (checksum) byte.  in this case, it's simply "0x01".

so far, so good.  now the camera responds...

2  gp_port: gp_port_read:  (size=00003) DATA: 40 03 00 
3  gp_port: gp_port_read:  (size=00001) DATA: 81 
4  gp_port: gp_port_read:  (size=00001) DATA: 01 

this is correct, except the camera's response always ends with "0x82", which
is missing.  this byte isn't being read.  in fact...

5  gp_port: gp_port_read: read timeout
6  gp_port: gp_port_set_settings: update ok

some kind of read error is occuring.

7  gp_port: gp_port_write: (size=00005) DATA: 40 00 02 01 01 
8  gp_port: gp_port_read: read timeout
9  gp_port: gp_port_set_settings: update ok

gphoto2 tries a 2nd time, but the camera is not responding.

10 gp_port: gp_port_write: (size=00005) DATA: 40 00 02 01 01 
11 gp_port: gp_port_read: read timeout
12 gp_port: gp_port_set_settings: update ok

and a 3rd time.

13 gp_port: gp_port_write: (size=00005) DATA: 40 00 02 01 01 
14 gp_port: gp_port_read: read timeout
15 gp_port: Closing port...
16 gPhoto2 reported the error 'Timeout reading from or writing to the port'

after a 4th try, gphoto is throwing its hands in the air and gives up.

looking through a bunch of windoze output, i noticed that the polaroid
software sends the initalization string anywhere between 1 and 5 times
before the camera responds.

i know nothing about serial programming.  if the baud is wrong, would there
be no communication at all or would there be "some" communication until the
program desyncronizes with the camera?  this is the only thing i can think of
that would be souring the communication midway between the handshake.

is there anything i should be looking for that would cause the last byte not
to be read?


"The following addresses had permanent fatal errors..."      p@dirac.org
                               -- Mailer Daemon              www.dirac.org/p

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Appahost Applications
For a significant contribution towards our projector, and a generous donation to allow us to continue meeting at the Davis Library.