Subject: Re: 2.5m obslog 20030331 (MJD 52730)
Date: Tue,  1 Apr 2003 15:23:10 -0700 (MST)
From: sjnk@apo.nmsu.edu (Scot Kleinman)
I saw this once during my run as well; a grabInst -drop and grabInst
-handlers cleared the problem.
Also, Eric, why does part of IOP think it's NOCVS? Did something not get
checked in properly?
scot
>The following message was seen every time Atsuko's sop session (which had
>the instruemnt) checked the camera. The same IOP version has been
>used for many days now and I have not seen this this dark run.
>So I am quite puzzled.  Dropping the instrument and re-grabbing it did not
>reproduce the error.
>
>IOP running as Backup Relay Server
>requestListen: listening                                    5
>2003-04-01 00:17:01Z 9 sp1 camcheck
>2003-04-01 00:17:01Z 9 sp1 SHOWREADVOLTS
>2003-04-01 00:17:02Z 9 sp2 camcheck
>2003-04-01 00:17:02Z 9 sp2 SHOWREADVOLTS
>sp1: list element in quotes followed by ":" instead of space
>sp2: list element in quotes followed by ":" instead of space
>    invoked from within
>"camHandler"
>    invoked from within
>"if {([exposureRemaining -quiet] == 0 && [statusGet daqBusy] ==0)} {
>#      echo "Idle camHandler"
>      camHandler
>      return
>   }"
>    (procedure "camHandler_maybe" line 12)
>    invoked from within
>"camHandler_maybe 60"
>    ("eval" body line 1)
>    invoked from within
>"eval $procname $args"
>camHandler_maybe is scheduled, further errors sent to murmur
>2003-04-01 00:17:08Z: registered (addr8) listener sdsshost:observer:2053
>sp1>
>sp1> iopVersion
>NOCVS:v3_113_1:/p/iop/v3_113_1