#54 Instrument Access failed with ColorMunki

None
out-of-date
None
1
2013-12-17
2013-01-14
Anonymous
No

Hi,

I am a novel user of ArgyllCMS and dispcalGUI, which I find very nice.

By using dispcalGUI, I obtain sometimes errors related to "Instrument Access Failed". How I reproduce the step:

1) I start the display calibration
2) During the calibration, I abort it
3) I start again the display calibration
4) the software prompts me to set the CM in sensor calibration position. At this point the calibration does not complete.
5) I abort the process
6) I start again the display calibration
7) Sensor calibration goes ok
8) I get the Access Failed error

At this point, the only way to resume operations is to quit dispcalGUI and start from scratch.

The log file is in italian. Is it useful to upload it here?

On the other hand, I NEVER got an Access failure message by using Argyll from the command-line on the same system.

This happens on a win7 pc.

Thanks

Marco
marco@irmafamily.net

Discussion

  • Florian Hoech

    Florian Hoech - 2013-01-15

    The logfile would be helpful, yes. Thanks.

     
  • Anonymous - 2013-01-15

    I am attaching here the log file. Please let me know if I can do anything to debug here.

    Thanks,

    Marco

     
  • Florian Hoech

    Florian Hoech - 2013-01-16

    At this point, the only way to resume operations is to quit dispcalGUI and start from scratch.

    I could not reproduce this. From the logs it always looks like the calibration was interrupted manually (e.g. by closing the window or hitting ESC or Q).

    On the other hand, I NEVER got an Access failure message by using Argyll from the command-line on the same system.

    Sounds unlikely. If you manually abort calibration, the last message from Argyll CMS is always “dispcal: Error - new_disprd() failed with 'Instrument Access Failed'”, e.g. cancelling device calibration with the i1 Pro (Argyll 1.4.0):

    dispcal -v -yl test
    Setting up the instrument
    Instrument Type:   Eye-One Pro
    Serial Number:     116370
    Firmware version:  202
    CPLD version:      2
    Date manufactured: 23-11-2004
    U.V. filter ?:     No
    Measure Ambient ?: Yes
    Tot. Measurement Count:           12588
    Remission Spot Count:             7726
    Remission Scan Count:             354
    Date of last Remission spot cal:  Wed Jun 22 18:48:25 2011
    Remission Spot Count at last cal: 7726
    Total lamp usage:                 23641.333984
    Display type ignored - instrument doesn't support display type
    Place cap on the instrument, or place in 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:
    
    Calibrate failed with 'User hit Abort Key' (No device error)
    The instrument can be removed from the screen.
    dispcal: Error - new_disprd() failed with 'Instrument Access Failed'
    

    The only thing I can do in dispcalGUI is suppress that message, because it may be irritating (in dispcalGUI you never see the “Calibrate failed with 'User hit Abort Key' (No device error)” message unless you check the log).

    There was one issue though, if device calibration failed for some reason (e.g. sensor in wrong position), it was not attempted again in case of the ColorMunki, leading to a measurement halt. This is fixed in the latest development snapshot:

    http://sourceforge.net/projects/dispcalgui/files/snapshot/dispcalGUI-1.2.0.0.zip/download

    Please try if it solves your issue.

     
  • Marco Presi

    Marco Presi - 2013-01-16

    Hi, you are partially right. Let me explain better. Indeed, I manually interrupt the calibration. But this is due to the fact that when I am in step 4) (refered to my first post), I put the CM in sensor calibration position (I checked that it is effectively in calibration position..) I press "OK" in the dialog and nothing happens. The sensor calibration does not complete. The only way to continue is manually interrupt the calibration wizard.

    After that, I run again the dispcalGUI calibration wizard, sensor calibration goes ok, and after that I get the reading error.

    Please note that after launching dispcalGUI everything runs fine. This problem occurs after the first time that I manually interrupt the calibration wizard.

    Let me make an example: weekly, I wanna check the profile. What I do is: first, run the calibration wizard so that I can bring back the monitor to the desired white point. I do this with the calibration wizard because I can use the interactive display adjustment. once the white point is ok, I manually interrupt the calibration wizard and run the "verify profile" wizard.

    Please note also that this bug occurs only if I run the calibration wizard twice, i.e. if I run the calibration wizard, set the white point, interrupt, then launch another wizard, all is fine. On the contrary, if I run the calibration, set the white point, interrupt, and then I run the calibration wizard again, the problem occurs.

    I may be just un-lucky, but I get this problem only if I run dispcalGUI. By using the command line, I never incurred in such a bug.

    Marco

    P.S: The problem is there also with the 1.2.0 snapshot.

     
    Last edit: Marco Presi 2013-01-16
  • Florian Hoech

    Florian Hoech - 2013-01-17

    Can you attach also the wexpect.log and wexpectconsolereader.log after a failed attempt? Thanks.

    To debug further, you could also launch dispcalGUI with the -t option (testing mode).

     
  • Anonymous - 2013-01-19

    Here it is. Please note that if I launch dispcalGUI with the -t option, the interactive adjust window does not appear (I can read the ArgyllCMS console output..) and the problem DOES NOT occur.

     
  • Marco Presi

    Marco Presi - 2013-01-19

    Here it is also wexpectconsolereader

     
  • Florian Hoech

    Florian Hoech - 2013-01-20

    Thanks. Did the two dialog boxes "Set the ColorMunki sensor to calibration position [...]" and afterwards "Place the instrument on the test window and click OK to continue" appear in test mode?

     
  • Marco Presi

    Marco Presi - 2013-01-24

    Sorry for the late reply. Yes they do appear.

     
  • Marco Presi

    Marco Presi - 2013-01-26

    Hi, I tested it. I launched the 1st calibration (I do the sensor calibration, then I start the measurement, then I stop it and then I close the adj-window. A message "Calibration not completed appears). Then I launch again the calibration: after the sensor calibration, I receive the message to put the CM on the test window, but at this time, both the "Start Measurement" and "Continue onto calibration" remain light grey and cannot be clicked.

    After closing the adj window I get again the msg "Calibration not completed".

    With this new build I don't get the "Access Instrument failed", but the problem seems to remain.

    I am attaching the log files.

     
  • Florian Hoech

    Florian Hoech - 2013-01-27

    Thanks. Hmm, this is very strange. The parser for the display adjustment window is really simple, it looks for the text "Press 1 .. 7" or "8) Exit" in the dispcal output and enables the buttons if the text is found. Is the text visible in the terminal window?

     
  • Marco Presi

    Marco Presi - 2013-01-28

    Thanks. I will test ASAP (I am quite busy at the moment, sorry).

    Marco

     
    • Florian Hoech

      Florian Hoech - 2013-02-15

      Hi, any update on this?

       
  • Florian Hoech

    Florian Hoech - 2013-04-28
    • assigned_to: Florian Hoech
    • Group: -->
     
  • Florian Hoech

    Florian Hoech - 2013-12-15

    I'm closing this now as it's out of date. If the problem still exists, feel free to re-open.

     
  • Florian Hoech

    Florian Hoech - 2013-12-15
    • status: open --> closed
     
  • Florian Hoech

    Florian Hoech - 2013-12-17
    • status: closed --> out-of-date
     


Anonymous

Cancel  Add attachments





Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks