>>> 'taurus' problem from jchung -- Sun Feb 12 13:35:24 1989 <<<

On Sunday 2/12 at 1:40pm, I noticed that despite argon and
the wand being up and apparently ok, most of the equipment
in the lab is enabled.  Perhaps, someone forgot to
re-enable the equipment controller after a system re-boot.

>>> 'taurus' problem from marilyn -- Mon Feb 13 08:58:41 1989 <<< [No Comment]
>>> 'taurus' problem from bob -- Fri Apr  7 08:03:01 1989 <<<

A user reports the taurus connection on the gcaws has failed. Steve
Hoagland brought the machine up late yesterday by shunting out the
taurus box. This problem needs service before the weekend.

>>> 'taurus' problem from phillip -- Fri Apr  7 10:44:02 1989 <<<

Replaced disorderly local taurus box on the gcaws.
The ws is on line on taurus once again.
The dysfunctional box will be remanded to jhopkin for
repair.

>>> 'taurus' problem from phillip -- Fri Apr  7 14:06:40 1989 <<<

Taurus test port from taurus computer to tech room repaired.
Techs: The taurus test line cord traverses the back of rnormans'
desk space in the tech room. PLEASE do not remove it (again).
From phillip Thu May 18 10:50:22 1989
Received: by argon (5.57/1.16)
	id AA08458; Thu, 18 May 89 10:50:16 PDT
Date: Thu, 18 May 89 10:50:16 PDT
From: phillip (Phill Guillory)
Message-Id: <8905181750.AA08458@argon>
To: /taurus-p, lab_equip_probs, parrish, phillip
Subject: dw problem
Status: R

P: Local taurus controller malfunctioning.
S: Replaced faulty male modular connector.
   The problem is remidied.


>>> 'taurus' problem from phillip -- Fri Jul  7 08:28:53 1989 <<<

RE: breact problem:
 Repaired intermittent pc board causing local taurus controller
to act up. Also, replaced 'on' lamp to one of greater visibility.

>>> 'taurus' problem from phillip -- Thu Jul 13 09:35:19 1989 <<<

The nanoduv is on taurus this day & hour.

>>> 'taurus' problem from phillip -- Thu Jul 13 09:37:15 1989 <<<

The 'nanoduv is on taurus this day & hour.

>>> 'taurus' problem from hoagland -- Mon Jul 24 16:57:06 1989 <<<

Cables were fabricated and the taurus expansion chassis has been
connected to the main control chassis.  Both units are powered up
and the additional ports should be operational.  All that remains
to do is route the ribbon cables as neatly or usefully as posssible-
I leave that to Phil.

>>> 'taurus' problem from phillip -- Fri Aug  4 14:36:53 1989 <<<

For an unknown reason  the taurus computer 'reset' itself
today about 1:30pm. 
 Once machines were disabled then enabled they came back on.
Investigation revealed no cause.

>>> 'taurus' problem from phillip -- Thu Aug 10 07:42:23 1989 <<<

Replaced intermittent problematic local taurus controller
for the 'topgun'.
From mudie Mon Jan 22 15:52:50 1990
Return-Path: <mudie>
Received: by argon.berkeley.edu. (4.1/SMI-4.0)
	id AA27128; Mon, 22 Jan 90 15:52:41 PST
From: mudie (David C Mudie)
Message-Id: <9001222352.AA27128@argon.berkeley.edu.>
To: msgs
Cc: microstaff
Subject: Locked equipment
Date: Mon, 22 Jan 90 15:52:38 PST
Status: R


Previously, when a problem was reported on a piece of lab
equipment, users still wishing to use the equipment were allowed
to override the warning message and enable the equipment
anyway.  Now, lab staff members have the ability to put an electronic
"lock" on a broken machine, disallowing its use completely
until the machine can be operated safely.

The previous warning/override system will still be in effect for 
minor problems reported, but a staff member will lock a machine if 
its operation poses a hazard to user or equipment.

"Locked" equipment is now displayed at the bottom of the
equipment status board.  If you attempt to enable a locked
equipment, for instance the nanospec, you will see any problem 
reported and then a warning notice:

    nanospec locked by bob Mon Jan 22 15:47:57 1990
    Enable of nanospec not allowed.

The equipment will not be activated, and you will not be charged
for its use.


From mudie Mon Jan 22 18:08:16 1990
Return-Path: <mudie>
Received: by argon.berkeley.edu. (4.1/SMI-4.0)
	id AA00115; Mon, 22 Jan 90 18:08:08 PST
From: mudie (David C Mudie)
Message-Id: <9001230208.AA00115@argon.berkeley.edu.>
To: microstaff
Subject: More on locking equipment 
In-Reply-To: Your message of Mon, 22 Jan 90 15:52:38 PST 
	     <9001222352.AA27128@argon.berkeley.edu.> 
Date: Mon, 22 Jan 90 18:08:04 PST
Status: R


At Katalin's suggestion, I did some rearranging of the staff's 
"Equipment" menu, moving some of the options to a new "Equipment 
Maintenance" menu and adding options to lock or unlock an
equipment.

In addition to the "manual" locking commands on the staff,
you (labstaff) will be asked if you want to lock the equipment
each time you report a problem.  When you report a fix for
an equipment, any lock on it is automatically removed.

Staff members can lock any piece of equipment, and can remove 
locks left by other staff.  Normal users can neither set nor
remove locks.  If a staff member tries to enable a locked equipment,
s/he will see the "equipment locked" warning message, but the
equipment will be activated anyway.

Please let me know if anything seems awry...

	-D-



>>> 'taurus' problem from evan -- Fri Mar  2 16:52:08 1990 <<<

The port address' of dport14-15,30-31,46-47 & 62-63 are reversed on the
new circuit board.  This is due to a motherboard error which was fixed with
little jumper wires on the old board.  Until the new board can be modified,
the equipment cables in these pairs of ports have been switched.  ie. if
you enable sink11, dport14, the circuit board will enable port15.  I put
the cable to sink11 into telco#15 so the right sink is enabled.
Except for a broken telco jack in #32, all the taurus problems reported
today were due to this reversal of control logic.
taurus is up 

>>> 'taurus' problem from rnorman -- Tue Mar  6 08:53:02 1990 <<<

The LED on the cpa taurus box is not lighting, but is enabling.
From phillip Tue Mar  6 11:10:19 1990
Return-Path: <phillip>
Received: by argon.berkeley.edu. (4.1/SMI-4.0)
	id AA22437; Tue, 6 Mar 90 11:10:12 PST
Date: Tue, 6 Mar 90 11:10:12 PST
From: phillip (Phill Guillory)
Message-Id: <9003061910.AA22437@argon.berkeley.edu.>
To: /taurus-p, debra, lab_equip_probs, parrish, phill, rnorman, tom
Subject: cpa problem
Status: R

Replaced expired visual illuminator on local taurus controller


>>> 'taurus' problem from rnorman -- Tue Mar  6 14:19:21 1990 <<<

Problem: LED on the cpa taurus not illuminating, but enabling.

Solution: Phil changed out the LED and now illuminates.

>>> 'taurus' problem from bob -- Wed Mar  7 10:18:33 1990 <<<

The taurus overide doesn't work. Equipment overide doesn't
function.

>>> 'taurus' problem from phillip -- Thu Mar  8 09:45:11 1990 <<<

P: The override function is not working properly because of the
   'temporary' state of the break-out box.

S: Added necessary wiring to 'temp' arrangement such that the 
   override function works a. when the office button is pushed
   and b. when the computer goes down.

The override feature works again as it should.
From mudie Thu Mar  8 18:34:06 1990
Return-Path: <mudie>
Received: by argon.berkeley.edu. (4.1/SMI-4.0)
	id AA02062; Thu, 8 Mar 90 18:34:04 PST
From: mudie (David C Mudie)
Message-Id: <9003090234.AA02062@argon.berkeley.edu.>
To: phillip
Subject: Re: taurus problem 
In-Reply-To: Your message of Thu, 8 Mar 90 09:48:07 PST 
	     <9003081748.AA12744@argon.berkeley.edu.> 
Date: Thu, 08 Mar 90 18:34:01 PST
Status: RO


I did some hand modifications to the old breakout panel to
allow the override to be reset by software -- I bent
out one pin of a logic IC so that port #1 is no longer
activated by the override.  I stuck a label "override"
on the IC.

dport#1 seems to have been appropriated for technics-c.
I assume this was intentional;  I hope my tweakings haven't
caused you any grief.  The connection removed from dport#1
to the relay may need to be grounded or something.

	-D-

-----------
     From:  phillip (Phill Guillory)
     Subject:  taurus problem
     P: The override function is not working properly because of the
        'temporary' state of the break-out box.

     S: Added necessary wiring to 'temp' arrangement such that the 
        override function works a. when the office button is pushed
        and b. when the computer goes down.

     The override feature works again as it should.


>>> 'taurus' problem from richard -- Thu Mar 22 13:29:17 1990 <<<

The taurus box for the excimer does not respond to either enabling
or the taurus override.

>>> 'taurus' problem from evan -- Thu Mar 22 16:51:23 1990 <<<

problem: excimer taurus box not working
cause: CG4 cable comming out of socket in taurus chase.  this also fixed the
terminal in GL-4.

>>> 'taurus' problem from evan -- Thu Mar 29 08:53:26 1990 <<<

The repaired original taurus port board was reinstalled.  The new one will
be returned to the electronics shop for rework.
