displaycal-py3
displaycal-py3 copied to clipboard
Error - new_disprd failed with 'Instrument Access Failed'
Describe the bug DisplayCAL unable to access the i1 display pro.
To Reproduce Steps to reproduce the behavior:
- Go to start measurements
Expected behavior Supposed to proceed with measurements
Versions (please complete the following information):
- OS: Windows 11
- Python Version: 3.11
- ArgyllCMS Version: 3.2.0
- DisplayCAL Version: 3.9.13 built from source following instructions
Initializing GUI...
input_value_clipping_bmp should have been hidden
output_profile_ctrl should have been hidden
...ok.
Ready.
Setting up scripting host at 127.0.0.1:15411
Check for application update...
DisplayCAL is up-to-date.
ArgyllCMS is up-to-date.
--------------------------------------------------------------------------------
Calibrate & profile
Detecting output levels range...
--------------------------------------------------------------------------------
Session log: 0_16
Working directory:
C:\
Users\
WINTER~1\
AppData\
Local\
Temp\
DisplayCAL-vmi9qczh\
Command line:
C:\Users\Wintermelon\AppData\Roaming\DisplayCAL\dl\Argyll_V3.2.0\bin\dispread.exe
-v
-k
C:\Users\Wintermelon\displaycal-py3\DisplayCAL\linear.cal
0_16
DisplayCAL: Starting interaction with subprocess
Number of patches = 3
Setting up the instrument
hid_open_port: Failed to open path '\\?\hid#vid_0765&pid_5020#6&c652c54&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' with err 32
hid_open_port: Failed to open path '\\?\hid#vid_0765&pid_5020#6&c652c54&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' with err 32
dispread: Error - new_disprd failed with 'Instrument Access Failed'
DisplayCAL: Reached EOF (OK)
dispread exitcode: 1
...aborted.
--------------------------------------------------------------------------------
Measure ambient
--------------------------------------------------------------------------------
Working directory:
C:\
Users\
WINTER~1\
AppData\
Local\
Temp\
DisplayCAL-vmi9qczh\
Command line:
C:\Users\Wintermelon\AppData\Roaming\DisplayCAL\dl\Argyll_V3.2.0\bin\spotread.exe
-v
-a
-x
-c1
DisplayCAL: Starting interaction with subprocess
Connecting to the instrument ..
hid_open_port: Failed to open path '\\?\hid#vid_0765&pid_5020#6&c652c54&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' with err 32
hid_open_port: Failed to open path '\\?\hid#vid_0765&pid_5020#6&c652c54&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' with err 32
Failed to initialise communications with instrument
or wrong instrument or bad configuration!
('Communications failure' + 'Communications failure')
DisplayCAL: Reached EOF (OK)
spotread exitcode: -1
...aborted.
--------------------------------------------------------------------------------
Calibrate & profile
Detecting output levels range...
--------------------------------------------------------------------------------
Session log: 0_16
Working directory:
C:\
Users\
WINTER~1\
AppData\
Local\
Temp\
DisplayCAL-ufm_n10r\
Command line:
C:\Users\Wintermelon\AppData\Roaming\DisplayCAL\dl\Argyll_V3.2.0\bin\dispread.exe
-v
-k
C:\Users\Wintermelon\displaycal-py3\DisplayCAL\linear.cal
0_16
DisplayCAL: Starting interaction with subprocess
Number of patches = 3
Setting up the instrument
hid_open_port: Failed to open path '\\?\hid#vid_0765&pid_5020#6&c652c54&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' with err 32
hid_open_port: Failed to open path '\\?\hid#vid_0765&pid_5020#6&c652c54&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' with err 32
dispread: Error - new_disprd failed with 'Instrument Access Failed'
DisplayCAL: Reached EOF (OK)
dispread exitcode: 1
...aborted.
Executing BaseApp.OnExit()
Running application exit handlers
Waiting for thread ScriptingHost.ConnectionHandler to exit
ScriptingHost.ConnectionHandler exited
Exiting __main__
Ran application exit handlers
I'm not sure if this is still needed under Windows, but normally ArgyllCMS requires its own drivers to be installed/used:
at www.argyllcms.com it says:
Please note that color measurement instruments are being driven by ArgyllCMS drivers, and that any problems or queries regarding instrument operation should be directed to the Argyll's author(s) or the Argyll mailing list, and not to any other party.
can you try running dispread to see if the problem persists.
Could you shoot me instructions for that? I ran through the build and install again, but it's the same.
Apparently the normal HID driver should work for i1 Display Pro without installing ArgyllCMS drivers, and people were complaining about getting the same error with different devices, all seems to be solved by upgrading/downgrading ArgyllCMS version.
So, let's try installing the newest ArgyllCMS:
- Download: https://www.argyllcms.com/Argyll_V3.3.0_win64_exe.zip
- Unzip
- Run DisplayCAL
- From File -> Locate ArgyllCMS Executables...
- Select the "ArgylCMS_v3.3.0\bin" folder.
- Try running again.
Apparently the normal HID driver should work for i1 Display Pro without installing ArgyllCMS drivers, and people were complaining about getting the same error with different devices, all seems to be solved by upgrading/downgrading ArgyllCMS version.
So, let's try installing the newest ArgyllCMS:
- Download: https://www.argyllcms.com/Argyll_V3.3.0_win64_exe.zip
- Unzip
- Run DisplayCAL
- From File -> Locate ArgyllCMS Executables...
- Select the "ArgylCMS_v3.3.0\bin" folder.
- Try running again.
This does not solve the issue.
If upgrading to the latest Argyll does not solve the problem, you can try the following 2 ways:
- Method 1:
- If you have Logitech software installed (keyboard, mouse, headset), stop the Logitech LampArray Service in Task Manager. Don't forget to try different USB ports (2.0 and 3.x)
- Method 2:
- Go to the Argyll folder /usb/ArgyllCMS.inf, remove the semicolon at the beginning of all lines that say Eye-One Display 3 (Argyll) and save.
- Restart Windows in Disable Driver Signature Enforcement mode
- Go to Device Manager, Human Interface Device, find the USB Input device with VID_0765
- Update its driver by pointing to the repaired ArgyllCMS.inf, select Install Driver Anyway when prompted
Maybe late. I had the same issue with the latest version. I found a post where the dev mentioned if one was using the correct HID device in device manager.
Since the HID was already in use, I suspect that it somehow malfunctioned. So the good ol turn it off and on again seemed to do the trick for me. No Driver update needed (assuming the latest is already installed).
I went to my i1Display3 device (view by container in device manager), disabled the HID device, Start DisplayCal and start a measurement. When it shows setting up device, re-enable the HID device. Fromt hat point acces is granted and you can measure away!
- Method 1:
- If you have Logitech software installed (keyboard, mouse, headset), stop the Logitech LampArray Service in Task Manager. Don't forget to try different USB ports (2.0 and 3.x)
This really did the trick for me at least since the logitech lamp array stuff just seems to install automatically if you plug in any logitech device even if you never used it or installed anything manually, just disabling the service does the Trick.
closing as it is not directly related to DisplayCAL.