News: Lambda 12b vs 24b, PiLC data in cont. scans, Lambda RDY vs. BSY, GpMonitor from ExpPcs, improvement of Spock logging feature, Gnome desktop broken, frozen GUIs

• The Lambda should behave in 12b mode as in 24b mode as far as the external trigger is concerned. Current status: 12b mode: 10 triggers create 9 frames, 24b mode: 10 trigger create 10 frames.

  Status: FS-DS will look into this matter.

• Currently the PiLC stores the first counter values in index 1 instead of 0.

  Status: Implemented, will be tested at P06.

• Lambda output signal should be BSY instead of RDY.

  David: The current implementation is that the output is high when the detector is ready to receive a trigger signal. This isn't quite the same as having high output when the detector is idle, since for example it will remain low after the end of the acquisition.

  Unfortunately, we only have one output and one input in the LAMBDA housing, primarily due to space limitations. This issue for me is that different users may want different options, and it’s difficult to find one option that’s suitable for all. Changing the existing implementation might also cause confusion. It might be possible to add a range of output options to the detector which could be changed by changing a variable in the Tango server. However, this would require more work ...

• To run the GpMonitor tool from ExpPcs. So far only on pal.

  Status: DONE

• Spock log file including called macros, spock output and datum. Documentation can be read here in section Spock/Logging.

• Gnome desktop broken: the what-to-do-if section of the Spock manual was extended by a fixup procedure.

• Frozen GUIs: Qt GUIs, including Taurus, may freeze, if they use threads. A what-to-do-if explains how that can be avoided, see here.