From maurice at stanford.edu Thu Oct 18 08:25:39 2012 From: maurice at stanford.edu (maurice stevens) Date: Thu, 18 Oct 2012 08:25:39 -0700 Subject: Tubes down for TGO prroblem Message-ID: <226DBFA5-70DF-4761-AFE6-BC635168B79A@stanford.edu> Hi All, Yesterday afternoon our Toxic Gas monitoring system gave a fault for a silane monitoring point. This fault means the system cannot collect information from the silane sensor at that location. We have shutdown the tools using that silane line and shutoff the gas at the cabinet. The tools that use this silane line will need to stay shutdown until we can safely monitor it. We will contact the field service for the TGO system this morning and hope to resolve the issue today. Look for an update on this issue later today. From maurice at stanford.edu Thu Oct 18 16:46:36 2012 From: maurice at stanford.edu (maurice stevens) Date: Thu, 18 Oct 2012 16:46:36 -0700 Subject: Tubes down for TGO problem/Update1 In-Reply-To: <226DBFA5-70DF-4761-AFE6-BC635168B79A@stanford.edu> References: <226DBFA5-70DF-4761-AFE6-BC635168B79A@stanford.edu> Message-ID: <08CEDF14-0F87-4EAC-9B6A-7100DF91874E@stanford.edu> Hi All, Our TGO field service guys have been on the phone and sending emails to John Shott and Ray all day and just came by as well. They have not found a cause for the earlier fault. We are not seeing the fault now. We will leave the gas off overnight and continue to monitor it. If it has no faults overnight we will probably turn everything back on in the morning. Sorry for the continued inconvenience. We will update you tomorrow. -m On Oct 18, 2012, at 8:25 AM, maurice stevens wrote: > Hi All, > > Yesterday afternoon our Toxic Gas monitoring system gave a fault for a silane monitoring point. This fault means the system cannot collect information from the silane sensor at that location. We have shutdown the tools using that silane line and shutoff the gas at the cabinet. The tools that use this silane line will need to stay shutdown until we can safely monitor it. > > We will contact the field service for the TGO system this morning and hope to resolve the issue today. > > Look for an update on this issue later today. > > > > From maurice at stanford.edu Fri Oct 19 09:20:03 2012 From: maurice at stanford.edu (maurice stevens) Date: Fri, 19 Oct 2012 09:20:03 -0700 Subject: Tubes up In-Reply-To: <08CEDF14-0F87-4EAC-9B6A-7100DF91874E@stanford.edu> References: <226DBFA5-70DF-4761-AFE6-BC635168B79A@stanford.edu> <08CEDF14-0F87-4EAC-9B6A-7100DF91874E@stanford.edu> Message-ID: <24E79322-461C-4B15-AC60-2B5A60191C47@stanford.edu> Good Morning, We have open the SiH4 at the cabinet and released the shutdown on the tools. These four tubes are now up for labmembers to use. We didn't have any SiH4 faults last night. But we have not found the cause of the problem? yet. We are still in contact with our Toxic Gas system vendor and are close monitoring the sensor. We will communicate any additional information (problems or solutions) we uncover. -m On Oct 18, 2012, at 4:46 PM, maurice stevens wrote: > Hi All, > > Our TGO field service guys have been on the phone and sending emails to John Shott and Ray all day and just came by as well. They have not found a cause for the earlier fault. We are not seeing the fault now. We will leave the gas off overnight and continue to monitor it. If it has no faults overnight we will probably turn everything back on in the morning. > > Sorry for the continued inconvenience. > > We will update you tomorrow. > > > -m > On Oct 18, 2012, at 8:25 AM, maurice stevens wrote: > >> Hi All, >> >> Yesterday afternoon our Toxic Gas monitoring system gave a fault for a silane monitoring point. This fault means the system cannot collect information from the silane sensor at that location. We have shutdown the tools using that silane line and shutoff the gas at the cabinet. The tools that use this silane line will need to stay shutdown until we can safely monitor it. >> >> We will contact the field service for the TGO system this morning and hope to resolve the issue today. >> >> Look for an update on this issue later today. >> >> >> >> >