- This topic has 5 replies, 2 voices, and was last updated 2 years, 6 months ago by
.
-
Posts
-
hi recently got a cheap MDSV Sensor 3 as i read others mentioning its a rebaged i1 Display Pro and it works with displaycal however upon plugging in, its white led blinks, no windows plug in chime and nothing in displaycal 3.8.9.3 instrument. I’m on win10 pro. i tried different usb2/3 ports but still the same.
Going to tools> instrument> install ArgyllCMS sits for about 40seconds before it closes with no Argy files installed anywhere? is argy required for this varient?
Calibrite Display Pro HL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.there’s also no sign of it showing up in device manager? which means i don’t think i can install ArgyllCMS manually if it’s not there, I’m not sure what others have done to get this working on their systems, hrm. ill try a laptop though it’s usbc to a usb3 hub breakout so I’m not certain that will work but worth a shot.
and nope, tired with both a laptop and then an old windows7 pc that only has various usb2 ports, same issue, blinking white led, nothing showing up in device manager. am i missing something or is the device faulty?
It does not need ArgyllCMS driver and its unlock code is listed in ArgyllCMS known codes.
First of all test if device is broken or at least detected. A fast way is “lsusb” in a Linux VM.
Another better way is to test a raw measurement in argyllcms sportead. Execute “spotread -?”, check -c list. Also run on high debug -D NUMBER.well that was a journey, I’ve never used linux before so i could still be doing something wrong but i intially tried debian with virtualbox but couldn’t get it fully installed, then tried mint Xfce with more success
installing argyll seems to detect nothing even after installing guest additions and adding the user to the vboxusers group, the VM usb devices also shows nothing extra
the original owner said they used it with mac and it was fine i dunno whats up with win7 and 10 on multiple pcs not picking it up though, i know the NEC ones supposidly have slightly changed firmware to talk to specific NEC monitors that have a usb port for it to calibrate standalone so is there some additonal step i might be missing to get it detected in windows?
