two new files - commands.txt and protocol2.txt

Hi guys!! :))

Hey Dennis, great that you joined CVS! Thanks for writing the first
code!

I can't wait until I can have a look at it!

Unfortunately I should be very busy with my project, so I can't spend as
much time with the camera as I would like.

Anyway, even if I shouldn't I spend the last hours writing two nice
files:

A command List and a new protocol file.

I know extracted all the important commands and think I know what they
mean.

Also: The file Format wich is coming from the camera is EXIF!

More details in the new Files I uploaded to CVS.

> First results, for you either all-nighters or early birds,

GREAT! :))

> Using usblib you don't have to worry about device descriptors or syntax of 
> setup messages etc, it's pretty straightforward to work with USB from it.

> I am able to get thumbs etc from a small C program, check for the camera, and 
> get this, I can see when you press the "Agfa Print" button on the camera! :-)

?? Really? How does this work? Since this button is probably pretty
useless under Linux, we could put some nice extra function on this
button... 

> But the biiiig question I have right now .. what the hell is the format for 
> the thumbnail data  ??????????

As above: The file that comes (from the flash card) is EXIF. This is a
special JPEG format containing BOTH, the picture and the thumbnail.

More details in the 2 new Files.

> You get 64 bulk packets (it tells you how many it is going to send), of 0x100 
> bytes each, for a grand total of 16384 bytes.
> 
> If you are using the lowest resolution (512x384 - but this is probably scaled 
> by the windows software !!) the resulting JPEG is 38259 bytes.
> AND there is no seperate picture, i.e. in low res mode (high quality mode has 
> 2 transfers) it only downloads ONE thing, which is used as both the thumbnail 
> AND as the resulting image.
> 
> But it is constructed from 16384 bytes. I don't really know where to start to 
> find out what format the received data is in.
> 
> The camera would not store it "raw", and it would also not do some custom 
> image compression if it can just store as jpeg. So somehow it is probably 
> JPEG data, but without the usual headers there would be in a JPEG file, at an 
> unknown resolution, which is scaled by the windows software to be a 512x384 
> image, 33Kb. 
> 
> Which is maybe why they don't really want to release the specs :-) They use 
> the excuse of trade secret or something like that, but basically they are 
> faking the whole thing :-)
> 
> I have attached (sorry) the raw data. The JPEG is probably useless since it is 
> scaled and only resembles the original graphically, but in no way in binary.
> 
> At least it was received from the camera completely in Linux, using "./a.out" 
> :-)

Hey, that's the first step! At least we received SOMETHING!!! :))

> Let me know what you guys think of this format !!!

I really have no idea what comes from the internal camera memory. There
are no headers at all, no readable characters. Since the transfer format
semms to be the same (just one transfer for pic and thumb) it might be
also EXIF

Hey, since I also found out, where the number of the total picture
stored on the camera is, we could write a basic program, which just
downloads all the pictures.

I hope the two new files help!

Cheers,
Phil


-- 
Wenn man keine Ahnung hat, einfach mal Fresse halten.