Jump to content

046d:0896 Acer Orbicam (logitech)


Dag0n
 Share

21 posts in this topic

Recommended Posts

Evening Folks,

 

I like many others am having issues getting my Acer Orbicam to work within Macam.

 

Currently I am running

10.4.8 JAS and 8.8.1 Kernel (i dont want to update, every works and im happy)

 

So the current issue we are facing is upon running it detects the webcam as Logitech Orbicam[ B ] (or [A] depending on what acer it is) then when the play button is pressed it brings an error saying USB Communication problem.

 

I have opened the code within Xcode

 

and the run log states

 

QT call to dummy sgpn:kComponentOpenSelect
QT call resulted in 0
QT call to dummy sgpn:kComponentVersionSelect
QT call resulted in 10027161
QT call to dummy sgpn:kComponentCloseSelect
QT call resulted in 0
QT call to dummy sgpn:kComponentOpenSelect
QT call resulted in 0
QT call to dummy sgpn:kComponentRegisterSelect
QT call resulted in 0
QT call to dummy sgpn:kComponentCloseSelect
QT call resulted in 0
USB Library Version = 2.6.0
USB Family Version = 2.6.1
USB Interface ID = 261
[vc032x_probe_sensor:128] check sensor header 44
[vc0321_config:350] Find Sensor PO3130NC       // PLAY IS PRESSED HERE
Trying alt 0, return is 0
alt interface 0:
 pipe 0: ANY 0 CONTROL 64 0
 pipe 1: IN  1 INTERRUPT 8 7
 pipe 2: IN  2 ISOC 0 1
Trying alt 1, return is 0
alt interface 1:
 pipe 0: ANY 0 CONTROL 64 0
 pipe 1: IN  1 INTERRUPT 8 7
 pipe 2: IN  2 ISOC 128 1
Trying alt 2, return is 0
alt interface 2:
 pipe 0: ANY 0 CONTROL 64 0
 pipe 1: IN  1 INTERRUPT 8 7
 pipe 2: IN  2 ISOC 512 1
Trying alt 3, return is 0
alt interface 3:
 pipe 0: ANY 0 CONTROL 64 0
 pipe 1: IN  1 INTERRUPT 8 7
 pipe 2: IN  2 ISOC 1024 1
Trying alt 4, return is 0
alt interface 4:
 pipe 0: ANY 0 CONTROL 64 0
 pipe 1: IN  1 INTERRUPT 8 7
 pipe 2: IN  2 ISOC 1536 1
Trying alt 5, return is 0
alt interface 5:
 pipe 0: ANY 0 CONTROL 64 0
 pipe 1: IN  1 INTERRUPT 8 7
 pipe 2: IN  2 ISOC 2048 1
Trying alt 6, return is 0
alt interface 6:
 pipe 0: ANY 0 CONTROL 64 0
 pipe 1: IN  1 INTERRUPT 8 7
 pipe 2: IN  2 ISOC 2688 1
Trying alt 7, return is 0
alt interface 7:
 pipe 0: ANY 0 CONTROL 64 0
 pipe 1: IN  1 INTERRUPT 8 7
 pipe 2: IN  2 ISOC 3072 1
Setting alt to 7, (with packet-size = 3072), return is 0
Checking pipe status, return is 0
Checking pipe properties, return is 0
 pipe 2: IN  2 ISOC 3072 1
usbGetIsocFrameSize returning 3072
StartNextIsochRead-ReadIsochPipeAsync: Error: kIOReturnBadArgument - invalid argument

 

I have marked the point where play has been pressed.

 

Any help would be much appreciated.

 

Also I have raised this as an issue on the macam bug tracker here

 

Thanks in advance

 

E: also upon an little investigation this may be related to iousbfamily? however i cannot confirm this.

Link to comment
Share on other sites

after investigating in macam i have determined that the maker of the chip an camera is vimicro

 

from here you can download the drivers, however im having troubles editing the plist as expected this doesnt work straight off the pid and vid are in number form and do not know how to check this? any ideas?

Link to comment
Share on other sites

I did get this working prior with using a differnt Usbfamily kext but it was showing the bottom half as green, but i cant for the life of me remember what one it was, ill have a play later at it

 

also that component unfortunatly doesnt work.

Link to comment
Share on other sites

Well.. I dropped it on /Library/QuickTime .. but nothing happens....

 

Running just macam gives the USB thing...

 

The component is so that the camera is recognized by any quicktime application, so the camera should show up in photobooth, etc. even if it doesn't work with any of the applications.

Link to comment
Share on other sites

sorry to keep spamming my own thread, but i have tested 4 different IOUSBFAMILY.kext's and i don't seem to be getting the usb communication problem anymore...

 

with macam 0.9.1 i get a scrambled image, but with the latest CVS build i get the attached images.

 

goto http://developer.apple.com/hardwaredrivers...d/usbdebug.html

 

download and install either 235.4.0, 246.4.0, 256.4.2 (for intel).

 

Still have some more to test but i think that the rest is likely to be with macam...

 

ill keep you all updated.

post-99319-1203706252_thumb.jpg

post-99319-1203706262_thumb.jpg

Link to comment
Share on other sites

sorry to keep spamming my own thread, but i have tested 4 different IOUSBFAMILY.kext's and i don't seem to be getting the usb communication problem anymore...

 

with macam 0.9.1 i get a scrambled image, but with the latest CVS build i get the attached images.

 

goto http://developer.apple.com/hardwaredrivers...d/usbdebug.html

 

download and install either 235.4.0, 246.4.0, 256.4.2 (for intel).

 

Still have some more to test but i think that the rest is likely to be with macam...

 

ill keep you all updated.

 

Tnx for the info bro! hope macam fix it.

Link to comment
Share on other sites

ok so when i try macam my green light beside my webcam turns on for a sec then off and says usb connection error. When i then try PIP a program off the apple site for webcams my green light stays on the entire time, maybe PIP has something to it, ive heard of some ppl getting PIP to work with this webcam

Link to comment
Share on other sites

  • 2 months later...

Hi all-

 

Ive read this entire thread Interesting stuff. I have been attacking this issue a completely different way. I also have a different cam but it only has a slightly different issue. Take a look at my thread below. I believe this issue is with the UVC driver in OSX and less to do with the driver for the cam (at least with my system the cam is detected in about this mac). But I have no support in some of the apple apps. Except now I have fixed that partially. I hope to fix it all soon.

 

http://forum.insanelymac.com/index.php?showtopic=100897

Link to comment
Share on other sites

  • 4 weeks later...
after investigating in macam i have determined that the maker of the chip an camera is vimicro

 

from here you can download the drivers, however im having troubles editing the plist as expected this doesnt work straight off the pid and vid are in number form and do not know how to check this? any ideas?

 

Well I seem to have made something resembling progress although with this camera being as buggy as it is I have a feeling it may never work.

 

I downloaded the VM0321 driver off of the above site and installed it. Didn't seem to do anything. I then went in and edited the plist changing idProduct and idVendor from numbers to strings changing them from the vimicro values to the standard info the camera gives in system profiler.

   <key>idProduct</key>
  <string>0x0892</string>
  <key>idVendor</key>
  <string>0x046d</string>

I have noticed other product id's (0x0896 vs 0x0892) perhaps this is difference between Orbicam[A] and Orbicam

 

After making changes, the next time I boot I get this in the console.

 

Jun 15 21:43:38 gojiras-aspire-5670 kernel[0]: VM0321::probe(Camera)
  Jun 15 21:43:38 gojiras-aspire-5670 kernel[0]: VM0321::start(Camera) <1>
  Jun 15 21:43:39 gojiras-aspire-5670 kernel[0]: Camera: family specific matching fails
  Jun 15 21:43:39 gojiras-aspire-5670 kernel[0]: VM0321::probe(Camera)
  Jun 15 21:43:39 gojiras-aspire-5670 kernel[0]: VM0321::start(Camera) <1>
  Jun 15 21:43:39 gojiras-aspire-5670 kernel[0]: VM0321::start(Camera) <1> failed
  Jun 15 21:56:38 gojiras-aspire-5670 kernel[0]: Camera: family specific matching fails
  Jun 15 21:57:31 gojiras-aspire-5670 kernel[0]: Camera: family specific matching fails
  Jun 15 21:57:36 gojiras-aspire-5670 kernel[0]: Camera: family specific matching fails

Seems like the camera is found but refuses to work, I still don't get video in the handful of apps I've tried. I've about stretched the limits of what I can do with this kext. I leave it to others to experiment.

 

 

p.s. I have noticed that using the 180 swivel to rotate the camera will usually trigger a USB event. Whenever I flip the orbicam around macam crashes immediately (it also crashes randomly as well and still hasn't given me more than a blank screen). Might be useful info for anyone trying to test their camera.

Link to comment
Share on other sites

 Share

×
×
  • Create New...