[argyllcms] Re: Problem recognising chart. Argyle 1.0.4_DTP20_untethered

  • From: Rob Smith <rob@xxxxxxxxxxxxxxxxxxxxxxx>
  • To: argyllcms@xxxxxxxxxxxxx
  • Date: Thu, 07 Jan 2010 19:16:37 +0000

Trying again to read the DTP20 v1.02 chart, this time with 1.1.0rc2. Errors as follows:


rob@AntecHeron:/opt/argyle/Argyll_V1.1.0_RC2/bin/rob$ ../chartread -v -D ./k3_540_1a4
Steps in each Pass = 30
Passes in each Strip = 18
usb_get_paths about to look through buses:
usb_get_paths about to look through devices:
usb_check_and_add() called with VID 0x1d6b, PID 0x2
usb_get_paths about to look through devices:
usb_check_and_add() called with VID 0x1d6b, PID 0x1
usb_get_paths about to look through devices:
usb_check_and_add() called with VID 0x765, PID 0xd020
usb_check_and_add() found known instrument
usb_check_and_add() called with VID 0x1d6b, PID 0x1
usb_get_paths about to look through devices:
usb_check_and_add() called with VID 0x1d6b, PID 0x1
usb_get_paths about to look through devices:
usb_check_and_add() called with VID 0x4b8, PID 0x7
usb_check_and_add() called with VID 0x1d6b, PID 0x2
usb_get_paths about to look through devices:
usb_check_and_add() called with VID 0x1d6b, PID 0x1
usb_get_paths about to look through devices:
usb_check_and_add() called with VID 0x1241, PID 0x1111
usb_check_and_add() called with VID 0x1d6b, PID 0x1
usb_get_paths about to look through devices:
usb_check_and_add() called with VID 0x1d6b, PID 0x1
dtp20: About to init coms
dtp20: 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:/bus0/dev4 (Xrite DTP20)'
icoms: USB port is now open
icoms: Clearing any USB errors
icoms: usb port characteristics set ok
dtp20: Sending '0PR^M'response '<00>^M^J' ICOM err 0x0
dtp20: Sending '0PR^M'response '<00>^M^J' ICOM err 0x0
dtp20: Sending '^M'response '<00>^M^J' ICOM err 0x0
dtp20: Sending 'GI^M'response 'Instrument Type: DTP20^M^JSerial Number: 005541^M^JMain Date Code: F415^M^JMain Version: 1.02^M^JBoot Version: 1.02^M^J<00>^M^J' ICOM err 0x0
Instrument Type:       DTP20
Serial Number:         005541
Main Date Code:        F415
Main Version:          1.02
Boot Version:          1.02
dtp20: Got coms OK
dtp20: Sending '0PR^M'response '<00>^M^J' ICOM err 0x0
dtp20: Sending '0008CF^M'response '<00>^M' ICOM err 0x0
dtp20: Sending 'SV^M'response 'X-Rite DTP20 vF415^M<00>^M' ICOM err 0x0
dtp20: Sending '0101CF^M'response '<00>^M' ICOM err 0x0
dtp20: Sending '0005CF^M'response '<00>^M' ICOM err 0x0
dtp20: Sending '0207CF^M'response '<00>^M' ICOM err 0x0
dtp20: Sending '020ACF^M'response '<00>^M' ICOM err 0x0
dtp20: Sending '0518CF^M'response '<00>^M' ICOM err 0x0
dtp20: Sending '001ACF^M'response '<00>^M' ICOM err 0x0
dtp20: Sending '0416CF^M'response '<00>^M' ICOM err 0x0
dtp20: Sending '06BA^M'response '2^M<00>^M' ICOM err 0x0
The battery charged level is 50%
dtp20: Sending '00GM^M'response '4^M<00>^M' ICOM err 0x0
dtp20: Sending 'CS^M'response '01^M<00>^M' ICOM err 0x0
dtp20: Sending '00TS^M'response '<33>^M' ICOM err 0x33
dtp20: Sending '00GM^M'response '4^M<00>^M' ICOM err 0x0
Can't use saved spots because they don't match chart - got 4 patches, expect 540
About to read strip pass A
Trigger instrument switch or any key to start, Esc or Q to give up:dtp20: Sending 'CS^M'response '01^M<00>^M' ICOM err 0x0
dtp20: Sending '00030DS^M'response '<11>^M' ICOM err 0x11

Strip read failed due unexpected error :'Communication protocol breakdown' (Unrecognised command)
Hit Esc or Q to give up, any other key to retry:


Graeme Gill wrote:
Rob wrote:
e) Plug device into USB and execute 'chartread'

Sounds OK.

Would it be helpful if I reset & cleared the DTP20, then read in just the TID row and checked in debug to see if it was recognised? Can't think of anything much else I can do at the moment ...

Sounds like X-Rite added the extra status values for the 1.03 firmware.
You could upgrade the firmware (although the X-Rite tools to do this are
only available on MSWindows and OS X).

If you are compiling from source I could send you an update to the
DTP20 driver to possibly fix it. Otherwise you will have to wait for
the V1.1.0 RC2 release.

cheers,
    Graeme Gill.



Other related posts: