USAXS to extend your range

I22s long tube would have needed to be 10x longer to measure the USAXS range...
I22s long tube would have needed to be 10x longer to measure the USAXS range...

A while ago, I had the pleasure of enjoying the hospitality of the wonderful people at the i22 beamline at the Diamond Light Source in the UK, with a visit from our colleagues from DUBBLE at ESRF. Over the course of 9 days, we debugged and tested the latest iteration, version 3, of the ongoing USAXS project (which started in 2012). Here’s some of the details of what we managed to do so far…

The USAXS platform as viewed from the front, with the synchrotron beam going from right to left.
The USAXS platform as viewed from the front, with the synchrotron beam going from right to left.

The installation had been in preparation for a few weeks, so the motors had been integrated in EPICS already, as had the encoders that are there to provide feedback on the fine yaw rotations (we didn’t use the USAXS electronics in the end..). These fine yaw rotations provide the ultra-small rotations of the crystals that allow for the ultra-small-angle scattering to be probed. With the addition of a small PIN-diode detector, we could align the upstream crystal, the sample stage, and the downstream crystal in turn. This was not without its own issues, though.

It turns out that it is very easy to “lose” the beam in the process: with an unfamiliar instrument — most of whose components have to be lined up for a good beam to pass through — if any component becomes misaligned, you usually need to go all the way back to the beginning of the alignment. Until the moment we automated the alignment, and before we found out how to avoid accidental misalignment, the alignment was a tedious and quite labour-intensive process. Secondly, with motors on both crystal towers sharing very similar names, accidentally moving a motor on one tower when you meant to move the one on the other tower led to more than a few delays. Thirdly, most motors didn’t have encoders on them, so you tell the motor to move and you cross your fingers that it actually does, and does to such an amount as you specified.

The USAXS platform as viewed from the rear, with the synchrotron beam going from left to right. The arms, actuators and encoder strips are clearly visible.
The USAXS platform as viewed from the rear, with the synchrotron beam going from left to right. The arms, actuators and encoder strips are clearly visible.

An additional issue emerged due to a conceptual misunderstanding. This instrument is supposed to sit on a good SAXS instrument, where the USAXS stages are moved in and out to capture the USAXS range only. Being the smart alecs we thought we were, we designed the crystals with opposite cuts: since each channel-cut crystal shifts the beam, we thought one would shift the beam out, and the second crystal would shift the beam back to (more or less) the original position. Having perused the literature, seeing a diagram of a Bartels monochromator (which has a similar design), I preemptively concluded this was a viable option. It turns out, however, that opposite cuts like this are great for monochromating, but not much good for USAXS experiments. The rocking curves we got through both these crystals were about 10 times wider and 10 times lower in intensity than they should be, and, after first trying to blame the hardware, we went to the resident crystal specialist. He took a brief look at the design, saw the conceptual flaw, and had to spend quite some time teaching us about what opposing cuts do different than parallel cuts. Fortunately, we had also brought a spare set of crystals from USAXS instrument version 2. The cost of this mistake? One day of beamtime, and a few thousand euros worth of oppositely-cut crystal…

Another day was spent debugging strange motor motions. This was one of the critical fine yaw rotations that we need for the USAXS experiment, and so could not be omitted. This whole saga appeared to start with me trying to fix a working system: I wanted to put oil on the contact point between the linear actuator and the arm, which went fine. Right after this, however, we got strange results as the linear actuator moved twice as far as the control system said it did! Fast forward a few hours, and we had completely messed up the motor settings beyond recovery, in an attempt to find a wrong setting. Together with the Diamond motion experts, we spent another several hours debugging the motions and the accompanying encoder strip. The culprit? Nothing to do with my oiling of the contact point or the motor settings, but a dodgy encoder input in the motor controllers! Other evidence also showed that the encoder readout might have started doing weird things even before my oily escapade.

After that, it was more regular debugging: gaining an order of magnitude on dynamic range on the PIN diode by swapping the diode for one with a non-holey foil, gaining another by swapping the coaxial cable with a thicker, lower noise variant, and disconnecting practically unnecessary motor cables to avoid them placing additional torque on the rotation arm.

During the beamtime, we also got started on the manuscript using Overleaf. This made us see some gaps in the measurements that would otherwise have gone unnoticed. It is not a silver bullet, though, as we later found another flaw in a set of measurements that really should be there (see the encoder troubles), but working on the manuscript certainly helped to put ourselves in the publication mindset to get a better overview of what’s missing.

While the measurements were progressing, Tim Snow managed to implement a few custom USAXS 1D-data processing methods in DAWN. This meant that we now have data corrected for:

  • darkcurrent
  • offset along the scattering axis (zeroed on the direct beam)
  • transmission correction
  • folding over the symmetry axis and averaging
  • conversion to a Q scale

As discussed in the previous two data correction papers, we are not going to attempt desmearing this data, but instead use fitting programs with smearing capabilities. SasView is one, and we’re testing the same functionality in McSAS.

USAXS scan of a 1-micron spacing between the supports of a SiN grating.
Figure 1: USAXS scan of a 1-micron spacing between the supports of a SiN grating. Direct beam appears below q<1e-4 (1/Ångström).

Without background subtraction, there are two “cool” datasets to show: one of a grating available at I22, whose support ribs are spaced about 1 micron apart (Figure 1), and a dataset from packed 500 nm silica spheres (Figure 2).

USAXS scan of packed, dry 500-nm silica spheres.
Figure 2: USAXS scan of packed, dry 500-nm silica spheres.

These two measurements extend a bit further than what this platform is intended to measure. Anything beyond q ≈ 0.004 1/Å (0.04 1/nm) can be measured with a decent SAXS instrument, such as the one that happens to be installed at I22.

I22s long tube would have needed to be 10x longer to measure the USAXS range...
I22s long tube would have needed to be 10x longer to measure the USAXS range…

That large flight tube in the last picture is one of I22’s longer settings, which lets them measure down to about q ≈ 0.002 1/Å with 18 keV photons. The SAXS data range thus overlaps nicely with the USAXS data (due to the lack of desmearing, we did not do this in a single graph).

We did some final tests where the two were interleaved: a 10-minute USAXS measurement combined with a <1-second SAXS measurement, and the repeatability is remarkably good. Although I see you are looking at the 10-minute figure… yes, that is a bit long for a synchrotron measurement, but we estimate this can be reduced significantly in the future with some special beamline magic.

So, now you’re all up to speed on the latest and greatest experiment. The USAXS saga is far from finished, but hopefully we’ll be able to submit a publication in not too much time now. Stay tuned!

3 Trackbacks / Pingbacks

  1. Detectors for good SAXS – Looking At Nothing
  2. Page not found – Looking At Nothing
  3. SAXS and USAXS, and smearing in McSAS – Looking At Nothing

Leave a Reply

Your email address will not be published.


*


*

This site uses Akismet to reduce spam. Learn how your comment data is processed.