From: sjnk@apo.nmsu.edu
Subject: Re: 2.5-m Obslog 20010427 (MJD 52027)
Date: Sat, 28 Apr 2001 13:49:25 -0600 (MDT)
>                             OBSERVING LOG
>                        Friday April 27, 2001
> ...I got the following error and trace
>(although it DID issue the command).  I restarted the GUI and the errors
>continued.  I exited sop and restarted and all seemed well.
>
>Error: can't read "TCC" no such variable, with the following trace:
>
>can't read "TCC": no such variable
>    while executing
>"puts -nonewline $TCC..."
>    (procedure "tccPut" line 3)
>    invoked from within
>"tccPut set inst=spectro"
>...
The only thing I can see that would cause this is that you did not have
an active TCC session open. This is the same error you'd get trying a TCC
command from the SOP CLI without doing a startDa -tcc. The procedure for
reversing out of this is to:
SOP>tccClose                          # Close any existing TCC sessions and
                                      # reset related variables
SOP>startDa -tcc                      # establish a (new) TCC session
SOP>tccPut blah_blah_blah             # Now you can talk to the TCC
Oh- I see now you say it DID issue the TCC command. Did it work? If so, ignore
the above, although it might have helped clear the internal variables if
they became confused.
Scot
>