June 23, 1987 | All That Fits is News to Print | Vol. 1, No. 6 |
Postscript version | TeX source |
Page contact and owner at end of this issue.
June 23, 1987
Author: Dave Wiser | Subsystem: SLC | User Impact: Minor |
Panel Changes: None | Documentation: None | Help File: None |
The password to the SLCOPS account was changed late last week. Anyone needing to use this account who does not know the new password should check with Operations to get the new password. This change also affected related accounts (e.g. SCP). The change was motivated because unusual file activity had been detected. People should bear in mind that the SLCOPS account is for control system related activities only. Anyone noticing any unusual activity in an SLC/MCC account should report it to the Software group.
June18,1987
Author: Ken Underwood | Subsystem: SLC | User Impact: Large |
Panel Changes: None | Documentation: No | Help File: None |
In order to accommodate additional database information, it was necessary to re-partition the database supertypes in DBSSHR. This change should have had no impact on users; however, it caused a problem by making OLDSOFT unusable. The problem has been fixed and OLDSOFT is now usable.
June 18, 1987
Author: Ralph Johnson | Subsystem: SLC | User Impact: none |
Panel Changes: none | Documentation: none | Help File: none |
The history buffer facility now monitors the commonly used feedback loops. The Signal (SGNL ), Command (CMND ), and Setpoint (SETP ) values are saved. Plots can be selected on the ``Feedback Loop Select'' panel. Please see John Zicker or John Silva for information regarding which loops are currently being monitored.
Currently, the SGNL and SETP plots are scaled to the Signal Limits SGLM values, the ``SGNL-SETP '' plot is scaled to twice the tolerance value, and the CMND plot to 10% more than the max/min of the data.
June 22,1987
Author: K. Thompson | Subsystem: SLC | User Impact: Minor |
Panel Changes: None | Documentation: No | Help File: No |
Certain feedback parameter buttons (group-wide BEAM and CNUM) can cause messages to be sent to both the production and development feedback processes if there are loops in both PROD and DEV mode in the selected group. The software has been changed so that no attempt is made to send such a message to the development feedback process if it is not currently running. Note that this change does not apply to parameters being changed at the loop level (as opposed to group-wide).
The single loop display had a bug in its display of the CNUM (configuration number) parameter that was fixed on about June 7, but accidentally got unfixed soon thereafter. It has been refixed. The CNUM in the display should again agree with what is shown on the CNUM button.
June 22, 1987
Author: Lou Sanchez-Chopitea | Subsystem: SLC | User Impact: Small |
Panel Changes: None | Documentation: No | Help File: None |
The logical names in the workstations and on MCC have been fixed to allow power steering and other modelling operations, and to provide a newsoft buffer for the power steering initialization files on MCC.
June 22,1987
Author: N. Spencer | Subsystem: SLC | User Impact: None |
Panel Changes: None | Documentation: No | Help File: None |
Analog and Digital Status code has been expanded to allow for more than 64 micros. Blank lines which had appeared every 5th line on Analog Status displays will now only appear to separate logical groups of channels.
June 22, 1987
Author: Tony Gromme | Subsystem: Final Focus BPS's | User Impact: Small |
Panel Changes: None | Documentation: None | Help File: None |
In the database, BPMS:MUXT can have one or two values. If present, the second value will include the additional offset (in PDU ticks) required for measuring outgoing beam. The BPM data acquisition software in the micro will use the second MUXT value (instead of the first MUXT value) if the second MUXT value is present and the %XYZOUT bit is set in DGRP:XYZ for the given micro in the given DGRP. This applies to FF01 and FF11 only. In FB69, wherever a single BPM can be used for measuring both incoming and outgoing beams, that BPM is represented twice in the database (as though it were two BPM's), and hence all BPMS:MUXT's in FB69 should be single-valued.
June 22, 1987 | Index Panel | Vol. 1, No. 6 |
Translated from original PlainTeX by index2html.pl.
*Links followed by an asterisk are limited to SLAC clients only. |