From seymour at snf.stanford.edu  Thu Jun  5 08:35:25 2008
From: seymour at snf.stanford.edu (seymour at snf.stanford.edu)
Date: Thu, 5 Jun 2008 08:35:25 -0700
Subject: Comment tylan1 SNF 2008-06-05 08:35:23: checked TRANSLC and torch.
Message-ID: <mailman.563.1357938808.25926.tylan1-pcs@snf.stanford.edu>

Replaced translc bubbler and the torch was ok.



From lwchang at snf.stanford.edu  Sat Jun  7 01:38:55 2008
From: lwchang at snf.stanford.edu (lwchang at snf.stanford.edu)
Date: Sat, 7 Jun 2008 01:38:55 -0700
Subject: Shutdown tylan1 SNF 2008-06-07 01:38:54: I/O error
Message-ID: <mailman.564.1357938808.25926.tylan1-pcs@snf.stanford.edu>

There was an I/O error and the front panel key pad did not work....wafers are still inside.



From shott at stanford.edu  Sat Jun  7 11:32:12 2008
From: shott at stanford.edu (John Shott)
Date: Sat, 07 Jun 2008 11:32:12 -0700
Subject: Shutdown tylan1 SNF 2008-06-07 01:38:54: I/O error
In-Reply-To: <20080607083855.25F4D87BD9@smtp2.stanford.edu>
References: <20080607083855.25F4D87BD9@smtp2.stanford.edu>
Message-ID: <484AD42C.1070505@stanford.edu>

Ray and Ted:

I was able to get things reset enough so that I could manually unload 
Li-Wen's wafers.  So they have been removed and the boat is back in the 
tube.  However, I have not been able to figure out how to get the TCU 
I/O error to do away when I do a DI ST 1 on the Tycom.

Looking over the logs, it appears that over the last 4 months we've had 
repeated problems reported with TCU I/O errors and have replaced a bunch 
of boards and power supplies.  This leads me to think that we haven't 
yet identified the real problem

Suggestions?

John




From lwchang at stanford.edu  Mon Jun  9 14:51:40 2008
From: lwchang at stanford.edu (Li-Wen Chang)
Date: Mon, 9 Jun 2008 14:51:40 -0700
Subject: Shutdown tylan1 SNF 2008-06-07 01:38:54: I/O error
In-Reply-To: <484AD42C.1070505@stanford.edu>
References: <20080607083855.25F4D87BD9@smtp2.stanford.edu>
	 <484AD42C.1070505@stanford.edu>
Message-ID: <8ab79e460806091451x230fc62bl95b3490a60bec6f7@mail.gmail.com>

Hi,
Will tylan1 be up today?
I need to reserve other tubes if it won't be up today.

Thanks
Li-Wen

On Sat, Jun 7, 2008 at 11:32 AM, John Shott <shott at stanford.edu> wrote:

> Ray and Ted:
>
> I was able to get things reset enough so that I could manually unload
> Li-Wen's wafers.  So they have been removed and the boat is back in the
> tube.  However, I have not been able to figure out how to get the TCU I/O
> error to do away when I do a DI ST 1 on the Tycom.
>
> Looking over the logs, it appears that over the last 4 months we've had
> repeated problems reported with TCU I/O errors and have replaced a bunch of
> boards and power supplies.  This leads me to think that we haven't yet
> identified the real problem
>
> Suggestions?
>
> John
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://snf.stanford.edu/pipermail/tylan1-pcs/attachments/20080609/1f59add7/attachment.html>

From shott at snf.stanford.edu  Mon Jun  9 16:07:42 2008
From: shott at snf.stanford.edu (shott at snf.stanford.edu)
Date: Mon, 9 Jun 2008 16:07:42 -0700
Subject: Shutdown tylan1 SNF 2008-06-07 01:38:54: I/O error
Message-ID: <mailman.565.1357938808.25926.tylan1-pcs@snf.stanford.edu>

Ted reset the slave computer and the I/O error disappered.  At this poiint, it is unclear what caused that problem, but we will keep a close eye on things.
John



From gunjim at snf.stanford.edu  Tue Jun 10 16:14:50 2008
From: gunjim at snf.stanford.edu (gunjim at snf.stanford.edu)
Date: Tue, 10 Jun 2008 16:14:50 -0700
Subject: Problem tylan1 SNF 2008-06-10 16:14:50: I/O error message on tycom
Message-ID: <mailman.566.1357938808.25926.tylan1-pcs@snf.stanford.edu>




From gunjim at snf.stanford.edu  Tue Jun 10 16:17:00 2008
From: gunjim at snf.stanford.edu (gunjim at snf.stanford.edu)
Date: Tue, 10 Jun 2008 16:17:00 -0700
Subject: Shutdown tylan1 SNF 2008-06-10 16:16:59: I/O error
Message-ID: <mailman.567.1357938808.25926.tylan1-pcs@snf.stanford.edu>

I will shut down since no operation can proceed on tylan1.



From shott at snf.stanford.edu  Tue Jun 10 17:27:47 2008
From: shott at snf.stanford.edu (shott at snf.stanford.edu)
Date: Tue, 10 Jun 2008 17:27:47 -0700
Subject: Problem tylan1 SNF 2008-06-10 16:14:50: I/O error message on tycom
Message-ID: <mailman.568.1357938808.25926.tylan1-pcs@snf.stanford.edu>

When I went in, there was nothing lit on the part of the display that usually says "RUN" or "READY".  Resetting the TCU box (underneath the jungle didn't help.  Then I decided to do 2 things:
1. Make sure that the intermediate DB25 connections were tight.
2. Reset what I believe is the slave computer (underneath the load station).
After doing that, the system came back to life and I was able to successfully load the 800AN recipe.
While I'm not confident that I've really solved anything permanetnly, we are at least back on the air.  At the very least we should get a single, long serial cable that can go all the way from the Tycom to Bank 1 without intermediate connections.  Both of the connections near the burnbox look to be somewhat corroded.
Thanks,
John



From shott at snf.stanford.edu  Tue Jun 10 17:27:58 2008
From: shott at snf.stanford.edu (shott at snf.stanford.edu)
Date: Tue, 10 Jun 2008 17:27:58 -0700
Subject: Shutdown tylan1 SNF 2008-06-10 16:16:59: I/O error
Message-ID: <mailman.569.1357938808.25926.tylan1-pcs@snf.stanford.edu>

When I went in, there was nothing lit on the part of the display that usually says "RUN" or "READY".  Resetting the TCU box (underneath the jungle didn't help.  Then I decided to do 2 things:
1. Make sure that the intermediate DB25 connections were tight.
2. Reset what I believe is the slave computer (underneath the load station).
After doing that, the system came back to life and I was able to successfully load the 800AN recipe.
While I'm not confident that I've really solved anything permanetnly, we are at least back on the air.  At the very least we should get a single, long serial cable that can go all the way from the Tycom to Bank 1 without intermediate connections.  Both of the connections near the burnbox look to be somewhat corroded.
Thanks,
John



From seymour at snf.stanford.edu  Wed Jun 11 09:39:26 2008
From: seymour at snf.stanford.edu (seymour at snf.stanford.edu)
Date: Wed, 11 Jun 2008 09:39:26 -0700
Subject: Comment tylan1 SNF 2008-06-11 09:39:25: MFS460 had NO AUTO error and alarm
Message-ID: <mailman.570.1357938808.25926.tylan1-pcs@snf.stanford.edu>

I reset the MFS460 and checked the front panel and it was locked on function. I reset the slave computer and loaded DRY800 and checked tube status on the Tycom. the gasses were flowing to setpoint but the temp read 400? all zones. I did not see a TCU error message but when I checked the TCU board it had error 2 showing. I reset the TCU and all is well at this time



From gunjim at snf.stanford.edu  Wed Jun 11 12:04:48 2008
From: gunjim at snf.stanford.edu (gunjim at snf.stanford.edu)
Date: Wed, 11 Jun 2008 12:04:48 -0700
Subject: Shutdown tylan1 SNF 2008-06-11 12:04:47: I/O error
Message-ID: <mailman.571.1357938808.25926.tylan1-pcs@snf.stanford.edu>

again I/O error message on tycom.



From tberg at snf.stanford.edu  Wed Jun 11 12:49:48 2008
From: tberg at snf.stanford.edu (tberg at snf.stanford.edu)
Date: Wed, 11 Jun 2008 12:49:48 -0700
Subject: Comment tylan1 SNF 2008-06-11 12:49:48: REset system again
Message-ID: <mailman.572.1357938808.25926.tylan1-pcs@snf.stanford.edu>

It is working again. I think we should keep it down until we resolve the issue



From seymour at snf.stanford.edu  Wed Jun 11 15:25:48 2008
From: seymour at snf.stanford.edu (seymour at snf.stanford.edu)
Date: Wed, 11 Jun 2008 15:25:48 -0700
Subject: Comment tylan1 SNF 2008-06-11 15:25:47: tube alarming for no auto
Message-ID: <mailman.573.1357938808.25926.tylan1-pcs@snf.stanford.edu>

I turned off the slave computer and will trouble shoot the tube with Ted in the morning.



From seymour at snf.stanford.edu  Thu Jun 12 09:51:32 2008
From: seymour at snf.stanford.edu (seymour at snf.stanford.edu)
Date: Thu, 12 Jun 2008 09:51:32 -0700
Subject: Shutdown tylan1 SNF 2008-06-11 12:04:47: I/O error
Message-ID: <mailman.574.1357938808.25926.tylan1-pcs@snf.stanford.edu>

replaced slave CPU and slave IO board. Ran wet800 and tube completed recipe with no alarms. I will change status to problem as the errors have been intermitten in nature and time will tell if boards were cause of the problem 



From seymour at snf.stanford.edu  Thu Jun 12 09:53:39 2008
From: seymour at snf.stanford.edu (seymour at snf.stanford.edu)
Date: Thu, 12 Jun 2008 09:53:39 -0700
Subject: Problem tylan1 SNF 2008-06-12 09:53:38: keeping tube under observation
Message-ID: <mailman.575.1357938808.25926.tylan1-pcs@snf.stanford.edu>

Due to the intermitten nature of the NO AUTO error on this tube we will not put tube to green status.



From tberg at snf.stanford.edu  Tue Jun 17 06:05:26 2008
From: tberg at snf.stanford.edu (tberg at snf.stanford.edu)
Date: Tue, 17 Jun 2008 06:05:26 -0700
Subject: Problem tylan1 SNF 2008-06-12 09:53:38: keeping tube under observation
Message-ID: <mailman.576.1357938808.25926.tylan1-pcs@snf.stanford.edu>

Replaced Slave CPU and I/O board . still working fine



From tberg at snf.stanford.edu  Tue Jun 17 06:05:36 2008
From: tberg at snf.stanford.edu (tberg at snf.stanford.edu)
Date: Tue, 17 Jun 2008 06:05:36 -0700
Subject: Comment tylan1 SNF 2008-06-11 15:25:47: tube alarming for no auto
Message-ID: <mailman.577.1357938808.25926.tylan1-pcs@snf.stanford.edu>

Replaced Slave CPU and I/O board . still working fine



From tberg at snf.stanford.edu  Tue Jun 17 06:05:48 2008
From: tberg at snf.stanford.edu (tberg at snf.stanford.edu)
Date: Tue, 17 Jun 2008 06:05:48 -0700
Subject: Comment tylan1 SNF 2008-06-11 12:49:48: REset system again
Message-ID: <mailman.578.1357938808.25926.tylan1-pcs@snf.stanford.edu>

Replaced Slave CPU and I/O board . still working fine



From tberg at snf.stanford.edu  Tue Jun 17 06:05:59 2008
From: tberg at snf.stanford.edu (tberg at snf.stanford.edu)
Date: Tue, 17 Jun 2008 06:05:59 -0700
Subject: Comment tylan1 SNF 2008-06-11 09:39:25: MFS460 had NO AUTO error and alarm
Message-ID: <mailman.579.1357938808.25926.tylan1-pcs@snf.stanford.edu>

Replaced Slave CPU and I/O board . still working fine



From tberg at snf.stanford.edu  Tue Jun 17 06:06:22 2008
From: tberg at snf.stanford.edu (tberg at snf.stanford.edu)
Date: Tue, 17 Jun 2008 06:06:22 -0700
Subject: Comment tylan1 SNF 2008-06-05 08:35:23: checked TRANSLC and torch.
Message-ID: <mailman.580.1357938808.25926.tylan1-pcs@snf.stanford.edu>

noted



From latta at snf.stanford.edu  Wed Jun 18 14:42:12 2008
From: latta at snf.stanford.edu (latta at snf.stanford.edu)
Date: Wed, 18 Jun 2008 14:42:12 -0700
Subject: Comment tylan1 SNF 2008-06-18 14:42:12: June Process Quals
Message-ID: <mailman.581.1357938808.25926.tylan1-pcs@snf.stanford.edu>

WET900  00:39:00  50 wafer spread
Average all wafers = 853A  (expect about 920A)
Within-a-wafer = 1.5%  (expect less than 5%)
Wafer-to-wafer = 1.0% (expect less than 5%)



From latta at snf.stanford.edu  Wed Jun 18 14:42:25 2008
From: latta at snf.stanford.edu (latta at snf.stanford.edu)
Date: Wed, 18 Jun 2008 14:42:25 -0700
Subject: Comment tylan1 SNF 2008-05-06 16:27:39: May process quals
Message-ID: <mailman.582.1357938808.25926.tylan1-pcs@snf.stanford.edu>

New quals posted



From gunjim at snf.stanford.edu  Wed Jun 18 23:04:58 2008
From: gunjim at snf.stanford.edu (gunjim at snf.stanford.edu)
Date: Wed, 18 Jun 2008 23:04:58 -0700
Subject: Problem tylan1 SNF 2008-06-18 23:04:57: Down to standby
Message-ID: <mailman.583.1357938808.25926.tylan1-pcs@snf.stanford.edu>

Tube turned to "standby" mode during the run. Could not bring the sample out of the tube. Tycom displays 400C as output temperature but will not display the temperature on the display beside the tube. From the color of the desplay, I assume that the tube is still under high temperature.