[argyllcms] Re: Problem accessing HCRF probe

  • From: Frédéric <frederic.mantegazza@xxxxxxxxxxx>
  • To: argyllcms@xxxxxxxxxxxxx
  • Date: Fri, 24 Aug 2007 08:44:09 +0200

On Friday 24 August 2007 05:14, Graeme Gill wrote:

> I'm not sure I can help. I found the HCFR USB interface to be quite
> unreliable at times, and often had to open the box up and hit the reset
> switch a couple of times to get it recognized. On some platforms some
> very subtle changes in the sequence of USB operations (interface resets
> etc.) would cause it to work or not work. As far as I know it works on
> all three platforms I've tested on currently. The fact that it says it's
> a serial device causes problems on OS X, requiring a codeless kernel
> extension to be installed to prevent it being captured by the operating
> system. The above diagnostic sequence is what you see when it simpy
> isn't responding.

I'll make some tests with the reset button...

> I'd leave the unit with it's default (wide open) arrangement for
> a projector - this is what it was designed for, and it will
> get more light and be faster this way.


> I suspect it's a UNIX only thing, and I'm working cross platform,
> and libusb is cross platform. All the other instruments I'm
> dealing with need direct USB communication (ie. they don't
> say they are a serial device), and I have a library built on top
> of libusb for dealing with cross platform and instrument issues. It's
> just too much trouble to support some other special access method that
> will be different on each platform for the HCFR.

Oh, I thought that libusb was UNIX only, and you where using other drivers 
unders win32 and MacOS...

If I can't make it run with libusb, I'll try to patch your code to use the 
cdc-acm driver.



Other related posts: