The camera is identified as,
idVendor 0x0797 Grandtech Semiconductor Corp.
idProduct 0x8001 SmartCam

What can I use to get the pictures downloaded from it to my computer?
Thanks.

Here is the output of,

lsusb -v

***********************************

Bus 001 Device 009: ID 0797:8001 Grandtech Semiconductor Corp. SmartCam
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x0797 Grandtech Semiconductor Corp.
idProduct 0x8001 SmartCam
bcdDevice 1.00
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 78
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 3
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 960
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 255
iInterface 4
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 0
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 0
Language IDs: (length=4)
0409 English(US)

***********************************

-- 
-------------- next part --------------
Skipped content of type multipart/related
From r...@exactcode.de  Mon Sep 12 15:35:33 2005
From: r...@exactcode.de (=?iso-8859-1?q?Ren=E9_Rebe?=)
Date: Mon Sep 12 15:37:11 2005
Subject: [sane-devel] HP 5730 / AV 600 - shifting imge issue patch for
        testing
Message-ID: <200509121735.39433.r...@exactcode.de>

Skipped content of type multipart/mixed-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20050912/0dc1685c/attachment-0001.pgp
From pie...@pirsoft.dnsalias.org  Mon Sep 12 15:59:18 2005
From: pie...@pirsoft.dnsalias.org (Pierre Willenbrock)
Date: Mon Sep 12 15:59:40 2005
Subject: [sane-devel] genesys backend
In-Reply-To: <200509112051.37440.stef...@modulonet.fr>
References: <42ffc607.9030...@pirsoft.dnsalias.org>     
<200509062156.50011.stef...@modulonet.fr>       
<4321c1a5.5080...@pirsoft.dnsalias.org>
        <200509112051.37440.stef...@modulonet.fr>
Message-ID: <4325a5d6.5060...@pirsoft.dnsalias.org>

Hi

While updating the gl841 patch for my website i noticed a small error
introduced while preparing the conversion patch.

St?phane VOLTZ schrieb:
>       Hello
> 
>       I got time to test, and have it work at 75 and 150 dpi. This let me 
> time scan 
> with both methods: got exactly the same time on my 850MHz Duron. Better, the 
> old function produced a slight bakctracking at the beginning of the scan, 
> with the new function, it's now gone. So I checked it in.
That was a small fix elsewhere. After detecting the slider is at begin
of scanning area there was a wait of 500ms(iirc), before checking if
there is data available. In 500ms the scanner fills its internal buffer,
and backtracks.
I can't imagine that the scanner would report more data to be available
than there actually is, so the slider position check may go away too.

>       600 dpi scan failed, so the new data reading function needs some fixes, 
> but 
> can be done later.
The function should consume the exact amount of data given in
dev->read_bytes_left. I'm sorry to be not very helpful with that problem.

Regards,
  Pierre
-------------- next part --------------
Index: genesys/genesys.c
===================================================================
RCS file: /cvsroot/sane/experimental/genesys/genesys.c,v
retrieving revision 1.34
diff -u -r1.34 genesys.c
--- genesys/genesys.c   11 Sep 2005 18:47:31 -0000      1.34
+++ genesys/genesys.c   12 Sep 2005 15:34:07 -0000
@@ -3601,7 +3601,7 @@
                      break;
              }
          } else {
-#if WORDS_BIGENDIAN
+#ifdef WORDS_BIGENDIAN
              if (depth == 16) {
                  status = genesys_reorder_components_endian_16(
                      work_buffer_src, work_buffer_dst,
From ger...@gkall.hobby.nl  Mon Sep 12 16:09:41 2005
From: ger...@gkall.hobby.nl (gerard klaver)
Date: Mon Sep 12 16:10:17 2005
Subject: [sane-devel] Getting Clever CAM 360 working
In-Reply-To: <pine.lnx.4.61.0509112139080.3...@banach.math.auburn.edu>
References: <43223760.9050...@ix.netcom.com> <1126340998.7659.3.camel@gk-lex3>
        <pine.lnx.4.61.0509101437460.2...@banach.math.auburn.edu>
        <4324e692.4000...@ix.netcom.com>
        <pine.lnx.4.61.0509112139080.3...@banach.math.auburn.edu>
Message-ID: <1126541382.6974.8.camel@gk-lex3>

On Sun, 2005-09-11 at 22:48 -0500, kilg...@banach.math.auburn.edu wrote:
> 
> On Sun, 11 Sep 2005, Martin wrote:
> 
> > The camera is identified as,
> > idVendor 0x0797 Grandtech Semiconductor Corp.
> > idProduct 0x8001 SmartCam
> >
> 
> Hmmm. I will make some comments, about the output of lsusb -v,
> below. The camera _may_ work with an existing driver, but it is not 
> obvious that it will...
> 
> Theodore
> 
> > What can I use to get the pictures downloaded from it to my computer?
> 
> Well, it is too early to tell the answer to that question, seems to me...
> 
> > Thanks.
> >
> > Here is the output of,
> >
> > lsusb -v
> >
> > ***********************************
> >
> > Bus 001 Device 009: ID 0797:8001 Grandtech Semiconductor Corp. SmartCam
> > Device Descriptor:
> > bLength 18
> > bDescriptorType 1
> > bcdUSB 1.10
> > bDeviceClass 255 Vendor Specific Class
> > bDeviceSubClass 255 Vendor Specific Subclass
> > bDeviceProtocol 255 Vendor Specific Protocol
> 
> 1. These three lines indicate that the camera is _not_ mass-storage, nor 
> is it PTP. Therefore, it needs to get support from libgphoto2.
> 
> 2. No existing driver supports this camera, unless something has been 
> added to the libgphoto2 CVS tree since I last downloaded it, a couple of 
> weeks ago.
> 
> 3. Going into libgphoto2/camlibs and doing
> 
> grep 797 */*
> 
> I got the following response:
> 
> polaroid/pdc640.c:      {"ScanHex SX-35a", 0x797, 0x8901, {
> polaroid/pdc640.c:      {"ScanHex SX-35b", 0x797, 0x8909, {
> polaroid/pdc640.c:      {"ScanHex SX-35c", 0x797, 0x8911, {
> polaroid/pdc640.c:      {"Typhoon StyloCam", 0x797, 0x801a, {
> polaroid/pdc640.c:      {"GrandTek ScopeCam", 0x797, 0x801c, {
> 
> which says that the indicated five cameras are supported by the "polaroid" 
> driver. And furthermore the various readme files in that directory do say 
> something about Grandtech chips. Looks like a possibility.
> 
> So I make two suggestions.
> 
>       1. try adding an entry in camlibs/polaroid/pdc640.c which 
> resembles the others, but lists the number as it is for yours. That is, 
> the third entry should be 0x8001. Just in order to see if it works at 
> all, I would suspect that you can just copy the rest of the lines for 
> that entry, down to the next "}". Then re-compile and re-install the 
> subdirectory libgphoto2/camlibs/polaroid by doing make, followed by make 
> install. (You do have or will get a source tree for libgphoto2? Since your 
> camera is not yet supported, I am afraid that you will have to go to the 
> source code because it needs some hacking done on it).
> 
> If this causes the camera to do anything positive, then one is on the 
> right track. I would say that the next thing to do, though, is to contact 
> the maintainer for the package, Marcus Meissner <mar...@jet.franken.de>
> who in that case will be the one responsible, from our project.
> 
>       2. If step one does not give any positive result, then it is 
> necessary to look deeper into the matter. It may be in that case necessary 
> to install the camera on Windows and install a USB traffic logger, to see 
> what the camera is doing. It may be seen that there is a lot of similarity 
> with the existing stuff in camlibs/polaroid, or it may be something 
> entirely different. At that point, only a direct comparison between the 
> log output and what is in the source files in camlibs/polaroid will tell 
> the story.
> 
> ------------------------------------------------------------
> 
> Gerard,
> 
> Now that I check into the matter more deeply, qbik.ch says you have a 
> possibly similar camera and gives a lead to your website. I think I have 
> seen that particular page before, when trying to learn more about the 
> Grandtech 8290 chip (which uses a somewhat screwed version of mass-storage 
> Bulk Transport and for which I ended up doing the kernel support).
> 
> But, sorry, I did not remember your webpage when I saw the letter on the 
> sane-devel list (which I still receive, having subscribed back when we 
> were working on the Canon N670U I got for Christmas a few years ago). Now, 
> after wading in on this, I think I see a reason why Martin contacted you. 
> Any further comments?
> 
> 
> Theodore Kilgore

I have the GrandTek ScopeCam", 0x797, 0x801c. For the webcam function i
started a SANE vidcam backend, see this page:
http://gkall.hobby.nl/gt8911-grandtech.html

Trying to read the images, no luck yet.
It's some time back so i don't know exactly what problems i had.

-- 
--------
m.vr.gr.
Gerard Klaver

Reply via email to