It's USB, the model numbers are 98376 to 98379 on the owner's manual, I can't find any reference to it online anywhere and do not know much about hardware, just bought it because it's a cheap temp while my other camera gets fixed. It's Sakar International Inc./Digital Concepts.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Okay ... tell me really quick how to get that info. This is all I know how to get:
[ 814.978206] usb 2-2: USB disconnect, address 3
[ 4080.564423] usb 2-2: new full speed USB device using uhci_hcd and address 4
[ 4080.813796] usb 2-2: configuration #1 chosen from 1 choice
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think the Ubuntu Synaptic is out of date, listing gphoto2 as only 2.4.0 but here it's 2.4.6 ... but when I try to compile on my system it keeps asking for the libtool library [libgphoto2 requires libltdl (the libtool dl* library)] which I have on my system but it doesn't seem to be finding it or some such error. This happens when I run the ./configure.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
this is in the jl2005c driver, which while we have basic access routines , is not yet able to deliver images since the compression algorithm is not known.
-> maintainer
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry to say, these particular cameras use a compression algorithm which we have been unable to figure out. he current libgphhoto2 driver can do everything with these cameras, except for the rather essential step at the very end. Namely, we can get the data for your photos out of the camera, but alas we do not know how to make a photo out of said (rather scrambled) data. This completely describes the current, very sad state of affairs with all of the Jeilin JL2005C cameras. This is the reason, incidentally, why we are willing to distribute what code we have written, but the driver does not get compiled by default. I have tried to explain completely what is the situation in the camlibs/jl2005c/README..jl2005c file, incidentally.
I am very sorry to have to tell you this. I wish that things were otherwise.
Theodore Kilgore
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Okay, thanks for the info Kilgota. I wish I was better at reverse engineering then I'd take a look at the raw data myself. The cameras do have a setting for uncompressed images, can it read those or would if be better to wait and hope someone figures it out?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No idea.
How is it detected on USB?
It's USB, the model numbers are 98376 to 98379 on the owner's manual, I can't find any reference to it online anywhere and do not know much about hardware, just bought it because it's a cheap temp while my other camera gets fixed. It's Sakar International Inc./Digital Concepts.
lsusb -v
But I have little hope given what I could read. You bought a Windows-only camera.
Crap. I am getting sick of Microsoft's contracts and loyalists.
But if you could give the info requested below, that could help us.
Okay ... tell me really quick how to get that info. This is all I know how to get:
[ 814.978206] usb 2-2: USB disconnect, address 3
[ 4080.564423] usb 2-2: new full speed USB device using uhci_hcd and address 4
[ 4080.813796] usb 2-2: configuration #1 chosen from 1 choice
As I said below, "lsusb -v"
Okay, thanks, I believe this is it:
Bus 002 Device 005: ID 0979:0227 Jeilin Technology Corp., Ltd
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0979 Jeilin Technology Corp., Ltd
idProduct 0x0227
bcdDevice 1.00
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 46
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 384mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 4
bInterfaceClass 0 (Defined at Interface level)
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 0
cannot read device status, Operation not permitted (1)
Sorry for being a bit dense, I was spoiled by Windoze for too long and still learning all the Linux commands.
and "gphoto2 --auto-detect" does not find it?
Nope, nothing.
weird, because there is a driver that list several Sakar cams with the same USB driver, but experimental (ie I'm not sure how well it work).
I think the Ubuntu Synaptic is out of date, listing gphoto2 as only 2.4.0 but here it's 2.4.6 ... but when I try to compile on my system it keeps asking for the libtool library [libgphoto2 requires libltdl (the libtool dl* library)] which I have on my system but it doesn't seem to be finding it or some such error. This happens when I run the ./configure.
this is in the jl2005c driver, which while we have basic access routines , is not yet able to deliver images since the compression algorithm is not known.
-> maintainer
Sorry to say, these particular cameras use a compression algorithm which we have been unable to figure out. he current libgphhoto2 driver can do everything with these cameras, except for the rather essential step at the very end. Namely, we can get the data for your photos out of the camera, but alas we do not know how to make a photo out of said (rather scrambled) data. This completely describes the current, very sad state of affairs with all of the Jeilin JL2005C cameras. This is the reason, incidentally, why we are willing to distribute what code we have written, but the driver does not get compiled by default. I have tried to explain completely what is the situation in the camlibs/jl2005c/README..jl2005c file, incidentally.
I am very sorry to have to tell you this. I wish that things were otherwise.
Theodore Kilgore
Okay, thanks for the info Kilgota. I wish I was better at reverse engineering then I'd take a look at the raw data myself. The cameras do have a setting for uncompressed images, can it read those or would if be better to wait and hope someone figures it out?