I don't know if they are needed, but considering how old is it, something might be needed.
Basically i've found what seems to be an old webcam, altough it also works as a photocamera with its own memory. I've tried to search the name and model on the net, but for some reason nothing related comes out. Can you help me with some more information (maybe a more known name for the model) or with the necessary drivers that i have to use?
On Mac OS X, the utility "macam" works great. It's plug&play.
"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel
I'll have to look again.. it's been quite a while since I tried (just this thread reminded me of it)
I think I went down that route before, and didn't find anything that actually recognized the camera
(it seems to be something "special" for Lego) but I'll have to revisit to be sure.
Vendor ID 0x0957 is "Agilent Technologies, Inc." (which seems a bit odd since they mostly do lab measuring equipment? But maybe that's just a name clash); I haven' found a direct match for Product ID 0x0201, but its neighbours 0x0200 and 0x0202 are both used for an "E-Video DC-350 Camera", so that's what I'd look for next. Maybe drivers for those will work (possibly after messing with the PIDs in the installer).
Name doesn't bring anything up. How about connecting it to a PC so it can at least read the hardware IDs?
Here's the ID. I think it should be right.
So... no luck at finding something?
Adding to @elszgensa post, this might be worth a shot (try adding your ID to the Atusbcam.inf file)...
USB\VID_0957&PID_0200 & USB\VID_0957&PID_0202 point to Agilent Technologies USB cameras with 350 in the model name, commonly the Chicony DC-350 for which a driver is attached
DaveDDSwrote on 2024-12-29, 16:32:I'll have to look again.. it's been quite a while since I tried (just this thread reminded me of it) […] Show full quote
I'll have to look again.. it's been quite a while since I tried (just this thread reminded me of it)
I think I went down that route before, and didn't find anything that actually recognized the camera
(it seems to be something "special" for Lego) but I'll have to revisit to be sure.
The Concord EyeQ Go (not the wireless variant) looks similar and has drivers with the same hardware IDs, at quick glance as OP'S Netten webcam.
The attachment carmera2.jpg is no longer available
The attachment Screenshot_20241230-080016-907.png is no longer available
Their web site ( concordcam.com ) is long gone and drivers did not get archived on archive.org .
However, driverguide.com still has them and I have attached them here.
The attachment GO_v01.zip is no longer available
EDIT: For anyone interested, here is how I found them.
a) reverse image search on google to find similar looking products that might just be rebrands/reskins
b) find original web sites (or archives of them) for those products to verify similarities and possibly get drivers or at least driver file names
c) plug driver file names and keywords like driver or the product name into google or other search engines.
Good work darry ! Found a ref to the VID_046D&PID_0850 but has diff end sub.... is in the Quickcam 5.61 and 6.01 driver package...
you can still get those thru logitechs ftp site in the quickcam folder (internally the install Lvcam.inf is in the QCDriver data1.cab)
%USB\VID_046D&PID_0850.DeviceDesc%=PID_0850,USB\VID_046D&PID_0850&MI_00 ; Emerald ASIC
thought I saw similar in the QuickCam Pro 3000 6.0 installer....
Hate posting a reply and then have to edit it because it made no sense 😁 First computer was an IBM 3270 workstation with CGA monitor. Stuff: https://archive.org/details/@horun
Horunwrote on 2024-12-31, 03:38:Good work darry ! Found a ref to the VID_046D&PID_0850 but has diff end sub.... is in the Quickcam 5.61 and 6.01 driver package. […] Show full quote
Good work darry ! Found a ref to the VID_046D&PID_0850 but has diff end sub.... is in the Quickcam 5.61 and 6.01 driver package...
you can still get those thru logitechs ftp site in the quickcam folder (internally the install Lvcam.inf is in the QCDriver data1.cab)
%USB\VID_046D&PID_0850.DeviceDesc%=PID_0850,USB\VID_046D&PID_0850&MI_00 ; Emerald ASIC
thought I saw similar in the QuickCam Pro 3000 6.0 installer....
You read my mind @Horun (and TY) . For the Lego one, I still need to go through the decompressed Logitech installer, but I also think there is hope with the Logitech Quickcam 3000 Pro drivers.
So, i'vr tried both the drivers, the Agilent Technologies .inf file (which i modified) and the Concord EyeQ.
The first one doesn't work and during the installation it had to modify a dll file... which i affirmed. Hope it didn't fuck up some stuff. The second detects the camera and it doesn't seem to give any problem, but now i don't have any program to test if it works.
Hate posting a reply and then have to edit it because it made no sense 😁 First computer was an IBM 3270 workstation with CGA monitor. Stuff: https://archive.org/details/@horun
Hmm interesting ! Your picture shows Arcsoft Photo Impression 1.6 and Video Impression 2000 which may also have the drivers included (maybe only on that oem cdrom like some Nero, Windvd, etc oem cd's) but is worth looking for .
Your pointing to: https://archive.org/details/lego-mindstorms-v … set-9731-cd-rom for Dave looks good and internal does have the
%USB\VID_046D&PID_0850.DeviceDesc%=PID_0850,USB\VID_046D&PID_0850&MI_00 ; Emerald ASIC
It is driver version 5.3 from Logitech and has all the software to go with...
Hate posting a reply and then have to edit it because it made no sense 😁 First computer was an IBM 3270 workstation with CGA monitor. Stuff: https://archive.org/details/@horun
This is the bundle the EyeQ GO! shipped with (from a current ebay listing for the camera)...
The attachment Concord EyeQ GO Apps.jpg is no longer available
All the netten21 site mentions is a version of CyberView (presumably this handles capture, edit, and storage of images and videos)
And sadly it seems that the disc is not available on archive or something, so i might have to buy it.
Anyway i managed to restore to a previous state the pc, to null the installation of the non-working driver.