Hi, I installed dispcal-0.7.0.7 that seems to work except that the buttons for calibration and caracterisation are greyed and do not operate. It happens that the author Florian Höch announced a bug on june 5 in this version dated 2011-05-29 (see http://hoech.net/dispcalGUI/). The bug has been corrected in the source (with same version nb) but I don't know if it has been modified in the gentoo version. I'm not sure if it is the reason of my pb though. I couldn't test an earlier version since none is available in Gentoo. Maybe I got something wrong in my setup. Reproducible: Always Steps to Reproduce: 1. Install dispcal-0.7.0.7 2. Setup. Activate sensor : OK. 3. Specify path to Argyllcms binaries Actual Results: Calibration and caracterization buttons are not working (greyed). Expected Results: Calibration and caracterization buttons are working (not greyed).
For me it worked fine but just in case, I removed the source archive ( rm /usr/portage/distfiles/dispcalGUI-0.7.0.7.tar.gz ) from my computer, re-emerged dispcalgui and it still works as expected. Usually when the calibration / profile buttons are grayed out, it means that your calibration device hasn't been detected. In the Instrument/Port field, does it have your calibration device or is it empty?
If I well remember, I had activated the sensor and the Instrument/Port field was showing the Spyder2 but the buttons were greyed. But today I tried again and the buttons are activated. I don't know what I did different (maybe a differrent usb port). However the measurement is still not possible, the console shows "Setting up the instrument" for a while and then displays these two messages "dispcal: Error - new_disprd() failed with instrument Access Failed" and "The calibration has not been finished" I also tried on my previous computer that is running Gentoo and dispcalGUI-0.6.2.2 : I emerged version dispcalGUI-0.7.0.7 and it works correctly. The problem I encounter is on my new computer and is probably related to some wrong settings. So I should probably close this bug item. ymi
Try to disconnect any other USB devices from your computer. I've found out that some can cause trouble to my colorimeter during the measurements. Also for Spyder 2 there is a special option in the tools menu (though I think you already know that). I have an Eye One Display 2 and although I have tested it and works fine in 5 PCs, there is 1 PC that no matter what, it won't work, neither in Linux nor in Windows. Dispcalgui will always give an error about accessing it with this PC.
yes, I knew this option and I also tried all possible configurations with the usb ports. It is really a problem with usb and Spyder2 as reported in several other posts I found. For me, on my new laptop (dell XPS L501x) it works only on Windows with the proprietary software but not with argyllcms neither on Linux nor Windows. Thanks for your help. I will close this bug item as it is not related to dispcalgui itself but for info here are some of the error messages that shows in the log window : .. Setting up the instrument usb_get_paths about to look through devices: usb_check_and_add() called with VID 0x1d6b, PID 0x2 usb_check_and_add() called with VID 0x1d6b, PID 0x2 usb_check_and_add() called with VID 0x1d6b, PID 0x3 usb_check_and_add() called with VID 0x8087, PID 0x20 usb_check_and_add() called with VID 0x8087, PID 0x20 usb_check_and_add() called with VID 0x408, PID 0x2fb1 usb_check_and_add() called with VID 0x85c, PID 0x200 usb_check_and_add() found known instrument failed to open serial "/dev/ttyS3" failed to open serial "/dev/ttyS2" failed to open serial "/dev/ttyS1" failed to open serial "/dev/ttyS0" spyd2: About to init coms spyd2: About to init USB icoms: About to set usb port characteristics icoms: About to open the USB port, tries 0 icoms: USB port needs opening icoms: About to open USB port 'usb:/bus3/dev2/ (ColorVision Spyder2)' icoms: USB port is now open icoms: Clearing any USB errors icoms: usb port characteristics set ok spyd2: init coms has suceeded spyd2: About to init instrument spyd2: Instrument reset Reset complete, ICOM code 0x0 spyd2: Get Status Get Status returns 3 ICOM err 0x0 spyd2: Get Status Get Status returns 1 ICOM err 0x0 spyd2: about to read all the EEProm values spyd2: Read EEProm addr 5, bytes 2 Read EEProm ICOM err 0x0 hwver = 0x307 spyd2: Read EEProm addr 8, bytes 8 Read EEProm ICOM err 0x0 serno = '00760698' spyd2: Read EEProm addr 16, bytes 108 Read EEProm ICOM err 0x0 ... snip..... pyd2: Read EEProm addr 372, bytes 4 Read EEProm ICOM err 0x0 Cal_A: Cal_A [0][0][0] = 0.000000 Cal_A [0][0][1] = 0.000000 Cal_A [0][0][2] = 0.013071 ...snip... al_F [6] = 0.002193 spyd2: all EEProm read OK spyd2: about to download the PLD pattern spyd2: Load PLD 8 bytes Load PLD returns ICOM err 0x0 ...snip... spyd2: Load PLD 8 bytes Load PLD returns ICOM err 0x0 spyd2: Get Status Get Status returns 0 ICOM err 0x0 spyd2: PLD pattern downloaded spyd2: Get Reading, clocks = 500, minfc = 0, maxfc = 0 Trigger Get Reading returns ICOM code 0x0 spyd2: Get Reading retry with ICOM err 0x2000 spyd2: Resetting end point Trigger Get Reading returns ICOM code 0x0 Get Reading Stat retry with ICOM err 0x2000 ...aborted. Calibration has not been finished. ______________________________________________
