[argyllcms] Re: DTP94 problem
- From: Fabrizio Levati <fabrizio.levati@xxxxxxxxxxxxxx>
- To: argyllcms@xxxxxxxxxxxxx
- Date: Thu, 9 Dec 2010 06:41:27 +0100
Finally I found the time to give it a try but with no luck :-(
C:\Documents and Settings\fabrizio>spotread_fix -D5
usb_get_paths about to look through devices:
usb_check_and_add() called with VID 0x1d6b, PID 0x2
Get config desc. 0 failed
usb_check_and_add() called with VID 0x1d6b, PID 0x1
Get config desc. 0 failed
usb_check_and_add() called with VID 0xe0f, PID 0x3
Is a libusb HID device
usb_check_and_add() called with VID 0xe0f, PID 0x2
usb_check_and_add() called with VID 0x765, PID 0xd094
usb_check_and_add() found known instrument
dtp92: About to init coms
dtp92Q/dtp94: About to init USB
icoms: About to set usb port characteristics
icoms: About to open the USB port
icoms: USB port needs opening
icoms: About to open USB port 'usb:/bus1/dev3/ (Xrite DTP94)'
icoms: USB port is now open
icoms: Clearing any USB errors
icoms: usb port characteristics set ok
icoms: Write_Read called with '0PR^M'
icoms: About to write '0PR^M' ICOM err 0x0
icoms: Read called
icoms: About to return read '<1B>' ICOM err 0x0
icoms: Write_Read Write_Read success, returning '<1B>'
icoms: Write_Read called with 'CE^M'
icoms: About to write 'CE^M' ICOM err 0x0
icoms: Read called
icoms: About to return read '<00>' ICOM err 0x0
icoms: Write_Read Write_Read success, returning '<00>'
icoms: Write_Read called with '0PR^M'
icoms: About to write '0PR^M' ICOM err 0x0
icoms: Read called
icoms: About to return read '<1B>' ICOM err 0x0
icoms: Write_Read Write_Read success, returning '<1B>'
icoms: Write_Read called with 'CE^M'
icoms: About to write 'CE^M' ICOM err 0x0
icoms: Read called
icoms: About to return read '<00>' ICOM err 0x0
icoms: Write_Read Write_Read success, returning '<00>'
icoms: Write_Read called with '^M'
icoms: About to write '^M' ICOM err 0x0
icoms: Read called
icoms: About to return read '<00>' ICOM err 0x0
icoms: Write_Read Write_Read success, returning '<00>'
icoms: Write_Read called with '0PR^M'
icoms: About to write '0PR^M' ICOM err 0x0
icoms: Read called
icoms: About to return read '<1B>' ICOM err 0x0
icoms: Write_Read Write_Read success, returning '<1B>'
icoms: Write_Read called with 'CE^M'
icoms: About to write 'CE^M' ICOM err 0x0
icoms: Read called
icoms: About to return read '<00>' ICOM err 0x0
icoms: Write_Read Write_Read success, returning '<00>'
dtp92: init coms has failed
spotread_fix: Warning - Got error Hardware Failure (Offset drift calibration
checksum failed) on attempting to communicate with instrument.
Got Offset Drift Cal error. Will try re-writing it
icoms: Write_Read called with 'SD^M'
icoms: About to write 'SD^M' ICOM err 0x0
icoms: Read called
icoms: About to return read 'NaN ^M<00>' ICOM err 0x0
icoms: Write_Read Write_Read success, returning 'NaN ^M<00>'
spotread_fix: Error - Unable to parse offset drift value
Any other idea/suggestion?
All the best
Fabrizio
Il giorno 01/dic/2010, alle ore 23.42, Graeme Gill ha scritto:
> Fabrizio Levati wrote:
>> Now the question is: is this enough to think the colorimeter is working
>> properly? Since I doubt that, do you know of any command that I can run in
>
> I'm surprised it doesn't reject the instrument because of the
> error code from it.
>
>> ToolCrib shell to test the instrument? As far as I can see, nothing seems to
>> indicate malfunctioning in ToolCrib...
>
> Interestingly, on looking through the source code, it seems that this exact
> problem
> has been reported once before, in October 2006. It may be a firmware checksum
> problem, and would hint that X-Rite have a rare but systematic issue in this
> area. It appears that the error is only reported on reset, so if the driver
> ignores errors on reset it can continue.
>
> The source code I came across attempts to read and then write the offset drift
> calibration value, in the hope that 1) the read value is valid, and 2)
> that writing it will make the error go away.
>
> In <http://www.argyllcms.com/spotread94fix.zip> is a MSWin version of
> spotread that has the fix code in it. If it detects an offset drift error
> it conducts a dialog to ask you if you want to write the offset drift
> value back to the instrument. (For reference, the offset drift value
> of my DTP94 is 0.124420. If the read value is valid, I'd imagine it
> will be similar).
>
> If you dare, you can run this and attempt to fix your instrument. (But
> I can make no guarantees it won't make things worse!)
>
> Graeme Gill.
>
Other related posts:
