- This topic has 7 replies, 2 voices, and was last updated 5 years, 3 months ago by
.
-
Posts
-
Greetings,
I’m having some problems getting DisplayCal to work with i1Display Pro. When I try to run any calibrations it gives me “Error – new_disprd failed with “Instrument Access Failed”. I have Xrite Device Services Manager stopped and the device is connected through USB 2.0.
DisplayCAL 3.7.1.4
Argyll 2.0.1
19:11:00,092 ——————————————————————————–
19:11:00,092 Calibrate & profile
19:11:00,150
19:11:00,177 Detecting output levels range…
19:11:00,180 ——————————————————————————–
19:11:00,180 Session log: 0_16
19:11:00,180
19:11:00,181 Working directory:
19:11:00,181 c:\
19:11:00,183 users\
19:11:00,183 tessa\
19:11:00,183 appdata\
19:11:00,184 local\
19:11:00,184 temp\
19:11:00,184 DisplayCAL-sw5uib\
19:11:00,184
19:11:00,184 Command line:
19:11:00,184 C:\Argyll\Argyll_V2.0.1\bin\dispread.exe
19:11:00,186 -v
19:11:00,186 -D8
19:11:00,186 -k
19:11:00,186 “C:\Program Files (x86)\DisplayCAL\linear.cal”
19:11:00,187 -d1
19:11:00,187 -c1
19:11:00,187 -yn
19:11:00,187 “-P0.499621498864,0.54261954262,1.86604361371”
19:11:00,187 0_16
19:11:00,187
19:11:00,486 DisplayCAL: Starting interaction with subprocess
19:11:00,497 get_a_display called with ix 0
19:11:00,499 MonitorEnumProc() called with hMonitor = 0x10001
19:11:00,499 MonitorEnumProc() set initial monitor info: 0,0 1920,1080 name ‘\\.\DISPLAY1’
19:11:00,499 MonitorEnumProc() called with hMonitor = 0x10003
19:11:00,500 MonitorEnumProc() set initial monitor info: -2560,6 2048,1152 name ↲
↳ ‘\\.\DISPLAY2’
19:11:00,500 get_displays about to get monitor information for 0
19:11:00,500 Mon 0, name ‘\\.\DISPLAY1\Monitor0’
19:11:00,500 Mon 0, string ‘Generic PnP Monitor’
19:11:00,500 Mon 0, flags 0x3
19:11:00,500 Mon 0, id ‘MONITOR\AOC2701\{4d36e96e-e325-11ce-bfc1-08002be10318}\0004’
19:11:00,500 Mon 0, key ↲
↳ ‘\Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325 ↲
↳ -11ce-bfc1-08002be10318}\0004’
19:11:00,500 EnumDisplayDevices failed on ‘\\.\DISPLAY1’ Mon = 1
19:11:00,502 get_displays added description ‘DISPLAY1, at 0, 0, width 1920, height 1080 ↲
↳ (Primary Display)’ to display 0
19:11:00,502 get_displays about to get monitor information for 1
19:11:00,502 Mon 0, name ‘\\.\DISPLAY2\Monitor0’
19:11:00,502 Mon 0, string ‘Generic PnP Monitor’
19:11:00,503 Mon 0, flags 0x3
19:11:00,503 Mon 0, id ‘MONITOR\VSC2034\{4d36e96e-e325-11ce-bfc1-08002be10318}\0002’
19:11:00,503 Mon 0, key ↲
↳ ‘\Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325 ↲
↳ -11ce-bfc1-08002be10318}\0002’
19:11:00,503 EnumDisplayDevices failed on ‘\\.\DISPLAY2’ Mon = 1
19:11:00,503 get_displays added description ‘DISPLAY2, at -2560, 6, width 2048, height ↲
↳ 1152’ to display 1
19:11:00,503 Selected ix 0 ‘\\.\DISPLAY1′ DISPLAY1, at 0, 0, width 1920, height 1080 ↲
↳ (Primary Display)’
19:11:00,503 Argyll ‘V2.0.1’ Build ‘MSWin 32 bit’ System ‘Windows V10.0 SP 0’
19:11:00,505 new_icompath: called with mask 0x1ffff
19:11:00,505 icoms_refresh_paths: called with mask = 0x1ffff
19:11:00,505 icoms_refresh_paths: looking for HID device
19:11:00,505 hid_get_paths: called
19:11:00,506 found HID device ‘\\?\hid#vid_0765&pid_5020#7&25f8ccc4&0&0000#{4d1e55b2 ↲
↳ -f16f-11cf-88cb-001111000030}’, inst 1 that we’re looking for
19:11:00,506 icompaths_add_hid ‘(null)’ got dctype 0x0
19:11:00,506 icompath_set_usb ‘hid:/1 (X-Rite i1 DisplayPro, ColorMunki Display)’ ↲
↳ returning dctype 0x10004
19:11:00,506 found HID device ↲
↳ ‘\\?\hid#vid_04d9&pid_a0f8&mi_01&col01#7&fb62a0a&0&0000#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’, inst 2 but not one we’re looking for
19:11:00,506 found HID device ↲
↳ ‘\\?\hid#vid_0c45&pid_652f&mi_01&col01#7&236090bf&0&0000#{4d1e55b2-f16f- ↲
↳ 11cf-88cb-001111000030}’, inst 3 but not one we’re looking for
19:11:00,506 found HID device ↲
↳ ‘\\?\hid#vid_0c45&pid_652f&mi_01&col02#7&236090bf&0&0001#{4d1e55b2-f16f- ↲
↳ 11cf-88cb-001111000030}’, inst 4 but not one we’re looking for
19:11:00,507 found HID device ↲
↳ ‘\\?\hid#vid_04d9&pid_a0f8&mi_00#7&2779b64f&0&0000#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’, inst 5 but not one we’re looking for
19:11:00,509 found HID device ‘\\?\hid#vid_046d&pid_c232#2&15f744c8&0&0000#{4d1e55b2 ↲
↳ -f16f-11cf-88cb-001111000030}’, inst 6 but not one we’re looking for
19:11:00,509 found HID device ↲
↳ ‘\\?\hid#vid_0c45&pid_652f&mi_01&col03#7&236090bf&0&0002#{4d1e55b2-f16f- ↲
↳ 11cf-88cb-001111000030}’, inst 7 but not one we’re looking for
19:11:00,510 found HID device ↲
↳ ‘\\?\hid#vid_0c45&pid_652f&mi_01&col04#7&236090bf&0&0003#{4d1e55b2-f16f- ↲
↳ 11cf-88cb-001111000030}’, inst 8 but not one we’re looking for
19:11:00,512 found HID device ↲
↳ ‘\\?\hid#vid_04d9&pid_a0f8&mi_01&col02#7&fb62a0a&0&0001#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’, inst 9 but not one we’re looking for
19:11:00,513 found HID device ↲
↳ ‘\\?\hid#vid_04d9&pid_a0f8&mi_02#7&338d67cc&0&0000#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’, inst 10 but not one we’re looking for
19:11:00,513 found HID device ↲
↳ ‘\\?\hid#vid_04d9&pid_a0f8&mi_01&col03#7&fb62a0a&0&0002#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’, inst 11 but not one we’re looking for
19:11:00,513 found HID device ‘\\?\hid#vid_0d8c&pid_0066&mi_02#7&67cdb4a&0&0000#{4d1e55b2 ↲
↳ -f16f-11cf-88cb-001111000030}’, inst 12 but not one we’re looking for
19:11:00,513 found HID device ‘\\?\hid#vid_046d&pid_c231#2&a02f33&0&0000#{4d1e55b2-f16f- ↲
↳ 11cf-88cb-001111000030}’, inst 13 but not one we’re looking for
19:11:00,513 found HID device ↲
↳ ‘\\?\hid#vid_046d&pid_c084&mi_01&col01#8&1e23a9b5&0&0000#{4d1e55b2-f16f- ↲
↳ 11cf-88cb-001111000030}’, inst 14 but not one we’re looking for
19:11:00,513 found HID device ↲
↳ ‘\\?\hid#vid_046d&pid_c084&mi_01&col02#8&1e23a9b5&0&0001#{4d1e55b2-f16f- ↲
↳ 11cf-88cb-001111000030}’, inst 15 but not one we’re looking for
19:11:00,515 found HID device ‘\\?\hid#vid_046d&pid_c084&mi_00#8&5b3940d&0&0000#{4d1e55b2 ↲
↳ -f16f-11cf-88cb-001111000030}’, inst 16 but not one we’re looking for
19:11:00,515 found HID device ↲
↳ ‘\\?\hid#vid_046d&pid_c084&mi_01&col03#8&1e23a9b5&0&0002#{4d1e55b2-f16f- ↲
↳ 11cf-88cb-001111000030}’, inst 17 but not one we’re looking for
19:11:00,515 found HID device ↲
↳ ‘\\?\hid#vid_046d&pid_c084&mi_01&col04#8&1e23a9b5&0&0003#{4d1e55b2-f16f- ↲
↳ 11cf-88cb-001111000030}’, inst 18 but not one we’re looking for
19:11:00,515 found HID device ↲
↳ ‘\\?\hid#vid_046d&pid_c084&mi_01&col05#8&1e23a9b5&0&0004#{4d1e55b2-f16f- ↲
↳ 11cf-88cb-001111000030}’, inst 19 but not one we’re looking for
19:11:00,516 found HID device ‘\\?\hid#vid_0c45&pid_652f&mi_00#7&5f7d36a&0&0000#{4d1e55b2 ↲
↳ -f16f-11cf-88cb-001111000030}’, inst 20 but not one we’re looking for
19:11:00,516 icoms_get_paths: returning 1 paths and ICOM_OK
19:11:00,516 icoms_refresh_paths: looking for USB device
19:11:00,516 usb_get_paths opening device ‘\\.\libusb0-0001’
19:11:00,516 usb_get_paths opening device ‘\\.\libusb0-0002’
19:11:00,516 usb_get_paths opening device ‘\\.\libusb0-0003’
19:11:00,516 usb_get_paths opening device ‘\\.\libusb0-0004’
19:11:00,517 usb_get_paths opening device ‘\\.\libusb0-0005’
19:11:00,517 usb_get_paths opening device ‘\\.\libusb0-0006’
19:11:00,517 usb_get_paths opening device ‘\\.\libusb0-0007’
19:11:00,517 usb_get_paths opening device ‘\\.\libusb0-0008’
19:11:00,519 usb_get_paths opening device ‘\\.\libusb0-0009’
19:11:00,519 usb_get_paths opening device ‘\\.\libusb0-0010’
19:11:00,519 usb_get_paths opening device ‘\\.\libusb0-0011’
19:11:00,519 usb_get_paths opening device ‘\\.\libusb0-0012’
19:11:00,519 usb_get_paths opening device ‘\\.\libusb0-0013’
19:11:00,519 usb_get_paths opening device ‘\\.\libusb0-0014’
19:11:00,519 usb_get_paths opening device ‘\\.\libusb0-0015’
19:11:00,519 usb_get_paths opening device ‘\\.\libusb0-0016’
19:11:00,519 icoms_refresh_paths: now got 1 paths
19:11:00,520 icoms_refresh_paths: looking for serial ports
19:11:00,520 serial_get_paths: called with mask = 131071
19:11:00,520 serial_get_paths: looking up the registry for serial ports
19:11:00,520 serial_get_paths: There don’t appear to be any serial ports
19:11:00,522 icoms_refresh_paths: we now have 1 devices and are about to sort them
19:11:00,522 icompaths_make_dslists ‘hid:/1 (X-Rite i1 DisplayPro, ColorMunki Display)’ ↲
↳ dctype 0x10004
19:11:00,522 icoms_refresh_paths: returning 1 paths and ICOM_OK
19:11:00,522 Number of patches = 3
19:11:00,523 Setting up the instrument
19:11:00,523 new_inst: called with path ‘hid:/1 (X-Rite i1 DisplayPro, ColorMunki ↲
↳ Display)’ type ‘i1D3’
19:11:00,523 new_icoms ‘hid:/1 (X-Rite i1 DisplayPro, ColorMunki Display)’ itype ‘i1D3’ ↲
↳ dctype 0x10004
19:11:00,523 icom_copy_path_to_icom ‘hid:/1 (X-Rite i1 DisplayPro, ColorMunki Display)’ ↲
↳ returning dctype 0x10004
19:11:00,525 i1d3_init_coms: called
19:11:00,526 i1d3_init_coms: About to init HID
19:11:00,526 icoms_set_hid_port: About to set HID port characteristics
19:11:00,526 hid_open_port: about to open HID port ‘hid:/1 (X-Rite i1 DisplayPro, ↲
↳ ColorMunki Display)’ path ↲
↳ ‘\\?\hid#vid_0765&pid_5020#7&25f8ccc4&0&0000#{4d1e55b2-f16f-11cf-
19:11:00,528 88cb-001111000030}’
19:11:00,604 hid_open_port: Failed to open path ↲
↳ ‘\\?\hid#vid_0765&pid_5020#7&25f8ccc4&0&0000#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’ with err 24
19:11:00,605 hid_open_port: Failed to open path ↲
↳ ‘\\?\hid#vid_0765&pid_5020#7&25f8ccc4&0&0000#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’ with err 24
19:11:00,605 i1d3_init_coms: set_hid_port failed ICOM err 0x20000
19:11:00,605 init_coms returned ‘Communications failure’ (Communications failure)
19:11:00,605 new_disprd failed because init_coms failed
19:11:00,605 icoms_del: called
19:11:00,605 dispread: Error – new_disprd failed with ‘Instrument Access Failed’
19:11:00,605
19:11:00,711 DisplayCAL: Reached EOF (OK)
19:11:00,713 …aborted.Thank you!
Calibrite Display Pro HL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.Hi, please use the ArgyllCMS development snapshot from the respective sticky thread and attach (do not paste) the resulting log from using that. Thanks.
As detailed in the in the thread you posted I too have removed all traces of X-Rite Software with Revo Uninstaller. i1Profiler or it’s associated services are not on my system ATM. Good suggestion though, I’ll check my system event log.
Hello again, so I tracked it down to KinectServices.exe and after I uninstalled the SDK from Microsoft the device was able to initialize the calibration. However I am having a new problem where program crashes after I begin a test measurement. I have attached the log, thank you!
