Martin Diers wrote: > Ok. Now we seem to have a different issue - this time tidy the i1d3. > > I was able to calibrate my brightness, and so was getting reading there, but > I could > not get any readings on curves. Log follows: > i1d3_command: Sending cmd 'Measure2' args '02 20 00 18 00 16 00 07' > i1d3_command: ICOM err 0x0 > i1d3_command: Reading response > i1d3_command: response read failed with ICOM err 0x4000 > read_sample returned 'Communications failure' (Communications failure) Hmm. It timed out, which is unexpected. > i1d3_command: major cmd not echo'd != 0x01 = 0x00 > i1d3_command: got '00 00 00 00 00 00 00 00 00 00 00 00 00 00' ICOM err 0x0 > read_sample returned 'Communication protocol breakdown' (Message from > instrument didn't echo command code) > i1d3_command: Sending cmd 'GetDiffuserPositio' args '94 00 00 00 00 00 00 00' > i1d3_command: ICOM err 0x0 > i1d3_command: Reading response > i1d3_command: got '00 01 03 00 00 00 02 00 00 00 02 00 00 00' ICOM err 0x0 > i1d3_get_diffpos: got 1 > read_sample returned 'Wrong Sensor Position' (Ambient filter should be > removed) And then the messages back from the instrument have got out of sequence. I've increased the timeout slightly, as well as attempted to make the recovery from error a bit more robust. See if you have more success with this: http://www.argyllcms.com/disptools_osx64.tgz> Graeme Gill.