Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Sometimes a map that has failed is still semi-active in the queue (so stuck in Resumed mode and the % is not 100) so it prevents you from running another one. Try stopping it and if this fails then : In GDA’s search bar (Quick Access on the top right) type and select Processing Queue. This produces another queue which you can clear by right click on any scan and selecting Clear Queue. NB: this will clear everything from the queue so if there is any information from previously ran scans that you want to retain, do this first and then Clear.

...

3. Stage Issues

To diagnose it helps if you have the EPICS (Synoptic) screen of the stage you are using open (T1 or T3).

...

To apply power repeat the above process in the reverse order.

...

4. If XANES/XAS scans don't run (or are flat) or acquiring an mca gives you nothing


If acquiring gives you zeros (or XAS scans are suspiciously flat) but you are sure you have beam etc there is an obscure bug that could be responsible. To get past it do a short map as this will kick the detector into action.

...

Then restart the GDA - see section 1

...


5. Maps don't display

if the map seems to be running but you are not getting any live display (also you only have one file instead of two per map in the Mapped data tree) then the Processing server might need restating.

...

What can also happen is that the elemental maps stop being updated, for example after a beam loss when the map restarts. This could be because the Processing that creates them has timed out. You can confirm the raw data are still been collected by inspecting the raw map (sum entry). The elemental maps can then be recreated offline.

...


6. Excalibur (Diffraction) Detector


Restarting and House keeping:

...

-From Synoptic : Excalibur and then Status:  In Housekeeping turn Low Voltage back on.

...

7. Spikes in FFI0

Assuming this is not due to mono glitches (ie spikes were not there from the begining) first check if FF and I0 separately have the same features. If not then the bug can be rid of by restarting the daserver (Synoptic: Hardware Status: click on proservcontr next to daserver...on the dialogue that opens click restart). Then restart GDA servers and client.

If they persist then they are sample related so try on another one.

...


8. Microscope Camera Problems

The online camera is controlled by EPICS so if you’ve got problems ie it doesn’t seem to be running or the image is too dark / light then find the VMA screen in the Synoptic :

...

Also keep in mind that the camera takes a couple of seconds to adjust to large changes of illumination so give it some time to adjust before you decide that Auto Exposure doesn’t work for you.

...

...


9. No beam on the sample but storage ring is ok: The feedback is lost


Symptoms


  • If the values in the S2 drain current window are all about zero and there is beam in the beamline (shutters are open, current in the ring, etc) then the feedback may have crashed.

...


The feedback can also be lost when moving filter D6A, if this occurs it may be necessary to move D6 to the 15 m Al value before trying again. Keep that filter in.

...



10. There is beam on the feedback but not in the ion chambers


As there is a pinhole of 200-400 microns diameter from which the beam goes through before reaching the sample if the ion chamber gets knocked for example when changing samples then you will not have any beam exiting.
The general idea is you have to roughly centralize the ion chamber without the pinhole and then finely centralize with the pinhole back in.
-First have a look of whether the ion chamber seems to be generally aligned with the beam exit which is a round window of kapton on the KB vessel behind the chamber.
Take out the pinhole (pull up the black metal frame at the back of the chamber).
Remove your sample as inspecting readings on the second ion chamber (Ion 2 on the Scaler screen in EPICS ) is needed for the alignment.
Do you now have a reading on Ion1 and Ion2 ?
If not it means the chamber has been moved quite a bit (visual inspection might suggest which direction and by how much) so first you need to manually move it in Epics to get some beam out:

...

You can start by setting a step of 0.5 and moving about in X and Y until you get beam on both Ion1 and Ion2. Once you get some beam on both chambers you can roughly centralize by finding the ranges that allow beam on Ion2 (as exit hole of the chamber is much smaller than entrance hole) and going in the middle. You can enter the position you want to go to by entering in the box with the blue numbers and hitting Enter.Then you need to do some coarse and fine alignment in GDA after putting the pinhole back in the ion chamber (there is only one way that it can freely slide in the chamber, don't push cause you will move the whole chamber again). Coarse Alignment :You scan the chamber by using the command line in the Jython Console of GDA . The command will look like :scan piny 8 11 0.1 pinx 8 11 0.1 counterTimer01 500 (8 start, 11 end , 0.1 step : for start and end choose +/- 1.5 mm from current positions you get from the EPICS screen). From the produced graphs in Plot choose I0 and It where the centre should be for X and Y. It is also useful to look at the chamber readings outputted in the Console as you will spot numbers going up in chamber 2 (or you can be looking at the Scalers Epics screen).Once you have beam in Ion Chamber 2 you can Interrupt the scan and move to the correct pinx and piny positions with the commands: pos pinx 8.5 andpos piny 8.5or by putting the right numbers in the Epics PIN screen.Fine Alignment: Finally two separate fine scans to centralize each motor :scan pinx 8 8.8 0.02 counterTimer01 500 (scan +/- 0.4 mm for current positions)scan piny 8 8.8 0.02 counterTimer01 500Again take pinx and piny to the correct numbers.

...


11. OLD: Restarting the CMOS diffraction camera


If the camera doesn't seem to respond try the following :

...

-If you give up on software restarts you can try a hardware reset: there are two whitish boxes at the end of the experimental table, one with a green and one with a blue LED. Power cycle them and then try again the software restarts

...



12. If you press the table emergency OFF

if the table emergency stop is pressed this will de-energise a number of motors around the experimental table. These include the sample stage and the motors that move the SiD detector.

...