When starting dispcal (or other programs needing instrument calibration), you run through this process: ********** Place the instrument on its reflective white reference Serial no. #######, and then hit any key to continue, or hit Esc or Q to abort: Calibration complete Place instrument on test window. Hit Esc or Q to give up, any other key to continue: ********** When running dispcal -v2 -d1 -c1 -m -qh -t5000 -b22.0 -g2.4 -f1.0 -k0 -A4.0 -B0.20 -H -Ibw "PA246 2013-07-27 0.2-22cdm² D5000 2.4 highQ highRes XYZLUT" ... it runs for quite a while, especially since someone is requesting a ridiculously low max 22cd/m², and with my monitor many of the patches during calibration require quite a few repeats, and some wind up failing. Not sure if my i1 Photo Pro 2 is triggering the need for re-calibration quicker than others, or if it is set to do that anyway after running for... 90 minutes? 2 hours? After running for that 90 minutes - 2 hours period, this process comes up: ********** Sample read failed because instruments needs calibration Place cap on the instrument, or place on a dark surface, or place on the white calibration reference, and then hit any key to continue, or hit Esc or Q to abort: Calibration complete ********** After hitting the key to signify that it's on the appropriate calibration surface, it reads for a second or two, states "Calibration complete", then a second later starts trying to read the patch on the screen. Can't get it back on the right spot on the screen fast enough. Would be awesome if the re-calibration process had a second hit any key, like the initial calibration process, giving you time to "Place instrument on test window." It's not the end of the world, as the reading it starts off the monitor winds up with a gigantic Delta E causing it to repeat, but it's a "skipped over" iteration of whatever it's iterating over in the Repeat/OK/Fail process.