Subject: Re: raith status sunday -- RE: RAITH EHT TRIP
From: James Conway <>
Date: Tue, 05 Jul 2005 17:41:39 -0700

Greetings Raith Users:

RE: RAITH EHT TRIP encountered this last weekend.

I checked out the gun and system vacuum levels before bringing the EHT 
up to 10 and then 20 kV.  I did not see any problems with FE-Gun 
stability other than a slight change upwards in Gun Vacuum as the EHT 
was run up.  Users were also working at 20 kV yesterday evening with no 
problems with arcing or EHT trips.  Emission is stable.  Gun vacuum is 
in the 2.0E-009 mbar area, slightly higher than I am targeting for.

Users are requested to be kind and gentle to the computers during their 
raith operations. Please ensure that all exits from the software 
applications are performed gracefully and allowing time for the system 
to log and write out the data files to disk upon exit. Please do not 
CTRL-ALT-DELETE to exit either any of the SW applications or the WIN 
2000 Pro OS. 

I just defragged these computers last week!

Thank you for your support!

James Conway

Luigi Scaccabarozzi wrote:

>Hi all,
>a few comments:
>1) This morning I found the raith software frozen and I had to kill it and
>restart it. The previous user most probably exited the LEO software after
>unloading, without waiting for the raith software to end normally the
>unload procedure. Restarting this morning was enough, but you may easily
>get errors that can be cleared only by an administrator.
>2) Teh problem that Dirk had with the logic was just due to the fact that
>the "beam" switch on the elphy was flipped down, reversing the logic. That
>switch must stay flipped up. it may have been flipped down accidentally by
>Dirk or another user, so be careful with that
>3) This morning I had a EHT trip which shut down the gun. I was working at
>10kV, and not even started imaging my sample. I was able to recover simply
>shutting down both computer and restarting.
>I'm writing right now and everything seemed ok. I'll write more if I
>encounter more problems or if the write is bad, otherwise you can assume
>the system if up and working.