Hardware Troubles » History » Version 1
Amber Herold, 04/23/2010 09:09 AM
1 | 1 | Amber Herold | h1. Hardware Troubles |
---|---|---|---|
2 | |||
3 | |||
4 | |||
5 | |||
6 | * <link linkend="PresetSendError">Microscope temporarily loses communication during |
||
7 | preset change</link> |
||
8 | |||
9 | |||
10 | * <link linkend="GIFoff">Leginon complains that it can not activate GIF |
||
11 | slit</link> |
||
12 | |||
13 | |||
14 | * <link linkend="stagebad">Compustage pole touch error causes the image acquired at |
||
15 | the wrong place</link> |
||
16 | |||
17 | |||
18 | |||
19 | |||
20 | |||
21 | |||
22 | |||
23 | h2. Preset manager fails to send a preset to the |
||
24 | microscope |
||
25 | |||
26 | |||
27 | |||
28 | Why: If Tecnai microscope is busy for reasons such as correcting a pole touch error, |
||
29 | Leginon can not comunicate with the scope until the latter is free. |
||
30 | |||
31 | |||
32 | Solution: Make sure the scope is not busy any more and send the preset to scope manually |
||
33 | to resume data collection. |
||
34 | |||
35 | |||
36 | Note: The immediate imaing condition may be wrong since manual preset sending does not |
||
37 | include extra image shift from the target, but it should recover in later process. |
||
38 | |||
39 | |||
40 | |||
41 | |||
42 | |||
43 | h2. Leginon can not activate GIF slit |
||
44 | |||
45 | |||
46 | |||
47 | Why: Unknown |
||
48 | |||
49 | |||
50 | Try these: |
||
51 | |||
52 | |||
53 | * Toggle the filtered button in the EFTEM menu a few times. |
||
54 | |||
55 | |||
56 | * Send tomography preset and then the square preset to scope. |
||
57 | |||
58 | |||
59 | * Make sure Gatan's GIF tracking program is off. |
||
60 | |||
61 | |||
62 | |||
63 | |||
64 | There is no fix for this bug. |
||
65 | |||
66 | |||
67 | |||
68 | |||
69 | |||
70 | |||
71 | |||
72 | h2. Image acquired at the wrong stage position |
||
73 | |||
74 | |||
75 | |||
76 | Commonly why: dirty or worn compustage parts |
||
77 | |||
78 | |||
79 | Solution: Call for scope service |
||
80 | |||
81 | |||
82 | * If this happens during grid atlas data collection, it has no impact on targets |
||
83 | selected on it. However, there is no way to patch to the intended location |
||
84 | easily. |
||
85 | |||
86 | |||
87 | * If this happens while a target is reacquired for drift correction, the drift |
||
88 | correction will be wrong. There is no fix except to "declare drift" in Drift Manager to |
||
89 | force another drift corection as soon as possible. |