Home › Forums › Help and Support › Displaycal Windows Argyll 3.0.0 stuck after setting up instrument
- This topic has 17 replies, 9 voices, and was last updated 3 days, 1 hour ago by
Nik Bernadsky.
-
AuthorPosts
-
2023-10-29 at 17:40 #139530
i got same problem on diffent PC and laptop
Equipment:i1d3+display pro (I rent it)
WIN10+5900X+3080Ti
all of these will stop at “setting up instrument” in normal operation. But if i change back to 2.3.9, every problem solved.
after downgrading to Windows 10, I had the same problem as Mike. Turns out the error only happens with 64 bit version of argyll 3.0.0. using 32 bit version works. I’m not 100% sure if this is also the case with windows 11.
I am on Windows 10 64-bit using an i1Display Pro (i1d3) and always used DisplayCAL and Argyll 2.3.1 64-bit without issue. When I tried Argyll 3.0.0 64-bit and the current Argyll 3.0.2 64-bit, DisplayCal would always stop at “setting up instrument”. Switching to Argyll 3.0.2 32-bit fixed that stopping issue.
Calibrite Display Pro HL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.2023-11-16 at 3:49 #139740i got same problem on diffent PC and laptop
Equipment:i1d3+display pro (I rent it)
WIN10+5900X+3080Ti
all of these will stop at “setting up instrument” in normal operation. But if i change back to 2.3.9, every problem solved.
after downgrading to Windows 10, I had the same problem as Mike. Turns out the error only happens with 64 bit version of argyll 3.0.0. using 32 bit version works. I’m not 100% sure if this is also the case with windows 11.
I have the same issue as above with the 64 bit build of ArgyllCMS 3.0.2 with DisplayCAL 3.8.9.3 on Windows 10 22H2 on a Thinkpad X250 with Intel HD 5500 graphics, it works fine with the 32 bit build. (Edit: Puck is a Colormunki Display)
-
This reply was modified 2 weeks, 5 days ago by
Æþelræd.
2023-12-02 at 8:33 #139920For i1 Pro on Win11 and 64 bit Argyll 3.x.x, the log looks like this:
23:25:55,332 Command line: 23:25:55,335 C:\Argyll_V3.1.0\bin\spotread.exe 23:25:55,335 -v 23:25:55,335 -e 23:25:55,335 -c1 23:25:55,336 -yl 23:25:55,336 -H 23:25:55,336 23:25:55,960 DisplayCAL: Starting inter action with subprocess 23:25:55,961 Connecting to the instrument .. 23:25:56,322 Instrument Type: GretagMacbeth i1 Pro 23:25:56,322 Serial Number: 338602 23:25:56,326 Firmware version: 505 23:25:56,326 CPLD version: 999 23:25:56,329 Date manufactured: 15-9-2009 23:25:56,334 U.V. filter ?: No 23:25:56,335 Measure Ambient ?: Yes 23:25:56,338 Tot.Measurement Count: 102292 23:25:56,342 Remission Spot Count: 5377 23:25:56,345 Remission Scan Count: 27749 23:25:56,351 Date of last Remission spot cal: Fri Jun 23 13:55:30 2023 23:25:56,355 Remission Spot Count at last cal: 5325 23:25:56,358 Total lamp usage: 77378.890625 23:25:56,364 Display/calibration type ignored - instrument doesn't support it 23:25:56,390 Init instrument success ! 23:25:56,390 23:25:56,392 Spot read needs a calibration before continuing 23:25:56,394 23:25:56,401 Place the instrument on its reflective white reference S/N 338602, 23:25:56,403 and then hit any key to continue, 23:25:56,405 DisplayCAL: Waiting for send buffer
//here is something wrong. No buffer sending.
23:26:09,210 DisplayCAL: Trying to end subprocess gracefully... 23:26:09,256 DisplayCAL: Sending buffer: '\x1b' 23:26:09,257 or hit Esc or Q to abort: 23:26:09,257 23:26:09,263 Spot read got abort or error from calibration 23:26:09,502 DisplayCAL: Reached EOF (OK) 23:26:09,503 spotread exitcode: -1 23:26:09,503 ...aborted.
No buffer was sent.
Ignoring device self-calibration (opted out) one can start measurement process by pushing keys manually – but only if console window is active. Otherwise the process hangs waiting for buffer sending. When process is started, one ca n see huge measurement delays, about 3-4 seconds (3.7 sec actually), even not in debug mode. On v. 2.3.1 everything runs fast and smooth.
In debug mode device calibrates itself but for extreme long time. And it hangs waiting for instrument and pressing any key:00:11:05,872 config_inst_displ succeeded 00:11:05,872 new_dispwin called 00:11:05,872 new_dispwin: About to open display ↲ ↳ '\\.\DISPLAY2' 00:11:05,872 W indows display RASTERCAPS 0x7e99, ↲ ↳ BITSPIXEL 32, PLANES 1, NUMCOLORS -1, COLORRES 24 00:11:05,872 new_dispwin: fdepth 8, rdepth 8, ndepth ↲ ↳ 8, edepth 16 00:11:05,872 new_dispwinabout to create window 00:11:05,872 new_dispwin window created 00:11:05,872 dispwin_get_ramdac called 00:11:05,872 dispwin_get_ramdac returning OK 00:11:05,872 Saved original VideoLUT 00:11:05,872 dispwin_set_color called on disp ↲ ↳ '\\.\DISPLAY2' 00:11:05,872 dispwin_set_ramdac called 00:11:05,872 dispwin_set_ramdac returning OK 00:11:05,872 dispwin_set_color about to paint color ↲ ↳ 0.501961 0.501961 0.501961 00:11:05,872 dispwin_set_color paint done 00:11:05,872 dispwin: update delay 200 msec = ↲ ↳ patch_delay 200 + disp_settle 0 - inst_reaction 0 00:11:05,872 dispwin_set_color delaying 200 msec 00:11:05,872 new_dispwin: returnsuccessfully 00:11:05,872 i1pro_imp_ get_n_a_cals: checking mode 3 00:11:05,872 i1pro_imp_get_n_a_cals: returning ↲ ↳ n_cals 0x0, a_cals 0x400 00:11:05,872 Placeinstrument on test window. 00:11:05,872 new_disprd failed because user aborted ↲ ↳ when placing device 00:11:05,872 i1pro_del called 00:11:05,872 i1pro_touch_calibration touching file ↲ ↳ 'C:/Users/user/AppData/Roaming/Cache/ArgyllCMS/.i1p_338602.cal' 00:11:05,873 i1pro_update_log: skipped as EPRom ↲ ↳ writeis disabled 00:11:05,873 i1pro_terminate_switch: called 00:11:05,873 icoms_usb_control: message 40, d0 000 3 ↲ ↳ 0000 0008 00:11:05,873 writing data ff ff ff ff fc ee 12 00 00:11:05,873 icoms_usb_control_msg_w0: type 0x40 req ↲ ↳ 0xd0 size 8 00:11:05,873 icoms_usb_control_msg_w0: returning err ↲ ↳ 0x0 and 8 bytes 00:11:05,873 ? ? icoms_usb_control: returning ICOM err 0x0 00:11:05,873 i1pro_terminate_switch: done, ICOM err 0x0 00:11:05,873 i1pro terminate switch thread failed, canceling I/O 00:11:05,873 coms_usb_transaction: returning err 0x10000 and 0 bytes 00:11:05,873 icoms_usb_rw: returning 0 bytes, ICOM ↲ ↳ err 0x10000 00:11:05,873 i1pro_waitfor_switch_th: failed with ↲ ↳ ICOM err 0x10000 (22984 msec) 00:11:05,873 Switch handler triggered with rv 114, ↲ ↳ th_term 1 00:11:05,874 Switch thread returning 00:11:05,874 i1pro switch thread terminated 00:11:05,874 icoms_del: called 00:11:05,874 icoms_del: closing port 00:11:05,874 usb_close_port_w0: called 00:11:05,874 usb_close_port_w0: usb port has been ↲ ↳ released and closed 00:11:05,874 dispwin_del called 00:11:05,874 dispwin_set_ramdac called 00:11:05,874 dispwin_set_ramdac returning OK 00:11:05,874 ? ? dispwin_set_ramdac called 00:11:05,874 dispwin_set_ramdac returning OK 00:11:05,874 Restored original ramdac
In no debug mode application waits for manual any key pressing after each step of measurement process and resumes after that only if console window (hidden one) is active.
It’s a kind of magic…When using colorimeter, debug log looks a bit different but with the same effects:
Seems that the app cannot see a device reading response.
14:20:02,113 ####################################################################### 14:20:02,113 Argyll 'V3.1.0' Build 'MSWin 64 bit' System 'Windows V10.0 SP 0' 14:20:02,113 new_icompath: called with mask 0x1ffff 14:20:02,113 icoms_refresh_paths: called with mask = 0x1ffff 14:20:02,113 icoms_refresh_paths: looking for HID device 14:20:02,113 hid_get_paths: called 14:20:02,113 found HID device ↲ ↳ '\\?\hid#vid_258a&pid_0016&mi_01&col07#9&2734e9b8&0&0006#{4d1e55b2-f16f- ↲ ↳ 11cf-88cb-001111000030}', inst 1 but not one we're looking for 14:20:02,113 found HID device ↲ ..................................................... 14:20:02,117 icompaths_add_hid '(null)' got dctype 0x0 14:20:02,117 icompath_set_usb 'hid:/19 (X-Rite i1 DisplayPro, ColorMunki Display)' ↲ ↳ returning dctype 0x10004 14:20:02,117 icoms_get_paths: returning1 paths and ICOM_OK
//after while device seems to be found, but response looks abnormal:
14:20:02,216 i1d3_command: Sending cmd 'GetDiffuserPosition' args '94 00 00 00 00 00 00 ↲ ↳ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 14:20:02,217 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ↲ ↳ 00 00 00 00 00 00 00 00 00 00 00 00 00 00' 14:20:02,217 icoms_hid_write: 64 bytes, tout 1.000000 14:20:02,217 icoms_hid_write: wrote 64 bytes, ICOM err 0x0 14:20:02,217 i1d3_command: ICOM err 0x0 14:20:02,217 i1d3_command: Reading response 14:20:02,217 icoms_hid_read: 64 bytes, tout 1.000000 14:20:02,217 icoms_hid_read: About to return hid read 64 ↲ ↳ bytes, ICOM err 0x0 14:20:02,217 i1d3_command: got '00 00 00 00 00 00 00 00 ↲ ↳ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ↲ ↳ 00 00 00 0 14:20:02,217 0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ↲ ↳ 00 00' ICOM err 0x0 14:20:02,217 i1d3_get_diffpos: got 0
…………………………………….
//about 150 identical blocks follow:14:20:02,370 i1d3_command: Sending cmd 'GetDiffuserPosition' args '94 00 00 00 00 00 00 ↲ ↳ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ↲ ↳ 00 0000 0 14:20:02,370 0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ↲ ↳ 00 00 00' 14:20:02,371 icoms_hid_write: 64 bytes, tout 1.000000 14:20:02,371 icoms_hid_write: wrote 64 bytes, ICOM err 0x0 14:20:02,371 i1d3_command: ICOM err 0x0 14:20:02,371 i1d3_command: Reading response 14:20:02,371 icoms_hid_read: 64 bytes, tout 1.000000 14:20:02,371 icoms_hid_read: About to return hid read 64 bytes, ICOM err 0x0 14:20:02,371 i1d3_command: got '00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ↲ ↳ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ↲ ↳ 00 00 00 14:20:02,371 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00' ICOM err 0x0 14:20:02,371 i1d3_get_diffpos: got 0
//stopping application running
What I actually see is that output string formatting differs from one version to another.
//In version 2.3.1 init block looks like this:
14:17:15,652 hid_open_port: HID port is now open 14:17:15,652 usb_install_signal_handlers: called 14:17:15,652 usb_install_signal_handlers: done 14:17:15,652 icoms_set_hid_port: HID port characteristics set ok 14:17:15,652 i1d3_command: Sending cmd 'GetStatus' args '00 01 00 00 00 00 00 00' 14:17:15,652 icoms_hid_write: 64 bytes, tout 1.000000 14:17:15,652 icoms_hid_write: wrote 64 bytes, ICOM err 0x0 14:17:15,652 i1d3_command: ICOM err 0x0 14:17:15,652 i1d3_command: Reading response 14:17:15,652 icoms_hid_read: 64 bytes, tout 1.000000 14:17:15,652 icoms_hid_read: About to return hid read 64 bytes, ICOM err 0x0 14:17:15,652 i1d3_command: got '00 00 00 08 00 00 00 00 00 00 00 00 00 00' ICOM err 0x0 14:17:15,652 i1d3_check_status: got OK 14:17:15,652 i1d3_init_coms: suceeded
//some dozens strings of successful echo
14:17:15,667 i1d3_get_diffpos: got 0 14:17:15,667 new_dispwin: return successfully 14:17:15,667 i1d3_command: Sending cmd 'GetDiffuserPosition' args '94 00 00 00 00 00 00 00' 14:17:15,667 icoms_hid_write: 64 bytes, tout 1.000000 14:17:15,667 icoms_hid_write: wrote 64 bytes, ICOM err 0x0 14:17:15,667 i1d3_command: ICOM err 0x0 14:17:15,667 i1d3_command: Reading response 14:17:15,667 icoms_hid_read: 64 bytes, tout 1.000000 14:17:15,667 icoms_hid_read: About to return hid read 64 bytes, ICOM err 0x0 14:17:15,667 i1d3_command: got '00 00 00 00 00 00 00 00 00 00 00 00 00 00' ICOM err 0x0 14:17:15,667 i1d3_get_diffpos: got 0 14:17:15,667 icoms_hid_write: 64 bytes, tout 1.000000 14:17:15,667 icoms_hid_write: wrote 64 bytes, ICOM err 0x0 14:17:15,667 i1d3_command: ICOM err 0x0 14:17:15,668 i1d3_get_diffpos: got 0 14:17:15,668 i1d3_command: Sending cmd 'GetDiffuserPosition' args '94 00 00 00 00 00 00 00' 14:17:15,668 icoms_hid_write: 64 bytes, tout 1.000000 14:17:15,668 icoms_hid_write: wrote 64 bytes, ICOM err 0x0 14:17:15,668 i1d3_command: ICOM err 0x0 14:17:15,668 i1d3_command: Reading response 14:17:15,668 icoms_hid_read: 64 bytes, tout 1.000000 14:17:15,668 icoms_hid_read: About to return hid read 64 bytes, ICOM err 0x0 14:17:15,668 i1d3_command: got '00 00 00 00 00 00 00 00 00 00 00 00 00 00' ICOM err 0x0 14:17:15,668 i1d3_get_diffpos: got 0 14:17:15,668 new_disprd succeeded
//all the procedures successfully ended
//and in version 3.x.x:
14:20:02,118 hid_open_port: HID port is now open 14:20:02,118 usb_install_signal_handlers: called 14:20:02,118 usb_install_signal_handlers: done 14:20:02,118 icoms_set_hid_port: HID port characteristics set ok 14:20:02,118 i1d3_command: Sending cmd 'GetStatus' args '00 01 00 00 00 00 00 00 00 00 00 ↲ ↳ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ↲ ↳ 00 00 00 14:20:02,118 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00' 14:20:02,118 icoms_hid_write: 64 bytes, tout 1.000000 14:20:02,118 icoms_hid_write: wrote 64 bytes, ICOMerr 0x0 14:20:02,118 i1d3_command: ICOM err 0x0 14:20:02,118 i1d3_command: Reading response 14:20:02,118 icoms_hid_read: 64 bytes, tout 1.000000 14:20:02,118 icoms_hid_read: About to return hid read 64 bytes, ICOM err 0x0 14:20:02,118 i1d3_command: got '00 00 0008 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ↲ ↳ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 ↲ ↳ 00 00 14:20:02,118 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00' ICOM err 0x0 14:20:02,118 i1d3_check_status: got OK 14:20:02,118 i1d3_init_coms: succeeded
//some dozens strings of successful echo
14:20:02,215 i1d3_get_diffpos: got 0 14:20:02,215 new_dispwin: return successfully
//and something went wrong:
14:20:02,215 i1Pdl3a_cceo mimnasntdr:u mSeenntd ionng tcemsdt 'wGientdDoiwf.f
14:20:02,215 uHsietr PEossci toiro nQ' taor ggsi v'e9 4u ↲
↳ p0,0 a0n0y 0o0th0e0r 0k0e y0 0t o0 0c o0n0t i0n0u e0:0 00 00 00 00 00 00 ↲
↳ 00 00
14:20:02,215 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ↲
↳ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00'
14:20:02,215 icoms_hid_write: 64 bytes, tout 1.000000 14:20:02,215 icoms_hid_write: wrote 64 bytes, ICOM err 0x0 14:20:02,215 i1d3_command: ICOM err 0x0 14:20:02,215 i1d3_command: Reading response 14:20:02,215 icoms_hid_read: 64 bytes, tout 1.000000 14:20:02,215 icoms_hid_read: About to return hid read 64 ↲ ↳ bytes, ICOM err 0x0 14:20:02,216 i1d3_command: got '00 00 00 00 00 00 00 00 ↲ ↳ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ↲ ↳ 00 00 00 0 14:20:02,216 0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ↲ ↳ 00 00' ICOM err 0x0
//infinite cycle
14:20:02,370 i1d3_command: Sending cmd 'GetDiffuserPosition' args '94 00 00 00 00 00 00 ↲ ↳ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ↲ ↳ 00 0000 0 14:20:02,370 0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ↲ ↳ 00 00 00' 14:20:02,371 icoms_hid_write: 64 bytes, tout 1.000000 14:20:02,371 icoms_hid_write: wrote 64 bytes, ICOM err 0x0 14:20:02,371 i1d3_command: ICOM err 0x0 14:20:02,371 i1d3_command: Reading response 14:20:02,371 icoms_hid_read: 64 bytes, tout 1.000000 14:20:02,371 icoms_hid_read: About toreturn hid read 64 bytes, ICOM err 0x0 14:20:02,371 i1d3_command: got '00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ↲ ↳ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ↲ ↳ 00 00 00 14:20:02,371 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00' ICOM err 0x0 14:20:02,371 i1d3_get_diffpos: got 0
//about 10 minutes of identical string blocks
//process terminated-
This reply was modified 3 days, 1 hour ago by
Nik Bernadsky. Reason: Text block markup was incomplete
Attachments:
You must be logged in to view attached files. -
This reply was modified 2 weeks, 5 days ago by
-
AuthorPosts