ColorMunki Photo: new_disprd() failed with 'Instrument Access Failed'

[Pascal de Bruijn]

Hi,

I recently noticed that the ColorMunki Photo no longer seems to work
reliably on Ubuntu 14.04 when doing local argyll 1.6.3 source builds. With
the prebuilt Argyll binaries it seems to work just fine.

The odd thing is that the ColorMunki Photo sometimes does work after it's
initially connected, but once it starts failing it generally seems to
continue to fail. And it doesn't take many attempts to get it to fail, most
typically it works for dispcal, and then fails for dispread...

This is the debug log I get when it's failing:

https://encrypted.pcode.nl/files/temp/argyll_163_colormunkiphoto_error.txt

I'm wondering whether this has anything to do with which version of libusb
argyll has been built against (which is 1.0.17 on ubuntu 14.04).

BTW, I've used a Huey, ColorMunki Smile and i1 Display Pro repeatedly just
fine with my own source build of argyll, this issue seems limited to the
ColorMunki Photo as far as I can tell at this point.

Regards,
Pascal de Bruijn

[Graeme Gill]

Post by Pascal de Bruijn
I'm wondering whether this has anything to do with which version of libusb
argyll has been built against (which is 1.0.17 on ubuntu 14.04).

Hi,

ArgyllCMS hasn't used libusb since V1.6.0. It's possible to build it
to use the old Argyll libusb, but I don't test it at all. At some
stage I'll remove even that.

So if you are building using exactly the same source code, it
seem like a puzzle. I have fixed a couple of bugs in the USB
code to do with timeouts, that particularly affected the DTP94
- you may want to build
<file:///D:/usr/graeme/www.argyllcms.com/Argyll_dev_src.zip>
and see if it behaves any differently.

(Note that colprof and other code has some issues with that
source, so you probably just want to use the instrument related
executables.)

Graeme Gill.

[Pascal de Bruijn]

Post by Pascal de Bruijn

Post by Pascal de Bruijn
I'm wondering whether this has anything to do with which version of

libusb

Post by Pascal de Bruijn
argyll has been built against (which is 1.0.17 on ubuntu 14.04).

Hi,
ArgyllCMS hasn't used libusb since V1.6.0. It's possible to build it
to use the old Argyll libusb, but I don't test it at all. At some
stage I'll remove even that.

Ah. That explains why I (using ldd) didn't see any linkage to libusb... I
presumed it was statically linked in...

Post by Pascal de Bruijn
So if you are building using exactly the same source code, it
seem like a puzzle. I have fixed a couple of bugs in the USB
code to do with timeouts, that particularly affected the DTP94
- you may want to build
<file:///D:/usr/graeme/www.argyllcms.com/Argyll_dev_src.zip>
and see if it behaves any differently.

Using the dev_src it seems after it has begun to fail, I get a 50%
success/failure ratio. Not just statistically, it seems to be like OK,
FAIL, OK, FAIL, OK, FAIL, ... fairly consistently...

When it's OK, I get the measurement patch quite quickly, like within a
second more or less.

When it FAILs, I do see dispcal being "stuck" for 4-5seconds.

Is there anything I can change to set the timeout to something ridiculous
to see if it's really a timeout issue?

Regards,
Pascal de Bruijn