Minutes from the 7/7/04 LCLS SLC IOC meeting. Next Meeting: 7/14/04 in B5, Rm 211. (1) People availability: Deb - on other projects until Aug (2) Prototype: SLC message service on the IOC. Diane has ASCII messages transferred over TCP from unix client to unix IOC ("micro" name = XL01). She is now looking at transferring structures and data conversion. To test on SCP, some additional setup work on VMS must be done by either Ron MacKenzie this week or Ken Underwood next week. She has examined the Xnet code (that converts SLCNET/Ethernet messages to usable messages) and is paring it down to what's needed. Due date remains unchanged. ACTION: Diane and KenU DUE: July 23 (3) Work: CMLOG client on the IOC. No action. Due date increased a month. ACTION: Diane DUE: Aug 30 (4) New Work: Procedure for adding a SLC IOC to the VMS micro list is required. Possibly some small changes to code on VMS to take care of micro online/offline and other micro "state" logic. ACTION: RonC/RonM/KenU DUE: July 14 (5) New Work: Decide on a few devices (BPMs and magnets) in XL01 and create database files for next DBGEN. ACTION: RonC/JoanP DUE: July 14 (6) Possible New Work: If fast feedback is required where ethernet communication between SLC micros and SLC IOCs is required, then existing SLC micro code (mcom) will need changing to support ethernet data transfer. ACTION: None yet DUE: Later (7) Decision: If we decide the SLC IOC will have a copy of its part of the SLC database, then no special effort will be done to allow a download of a new database with new devices on-the-fly (ie, without an IOC reboot). (8) Decision: No SLC klystron messages or klystron micro job functionality will be provided on the SLC IOC. Dayle says the LLRF (PIOP) will use the existing camac micro interface. Everything else is straight EPICS. (9) Functional Requirements: The following subsystems will be supported in the SLC IOC and I've added the people assigned to come up with a list of functional requirements. By July 14, we should have an estimate on how long it will take us to generate such a list. The SLC IOC web page is being populated with pointers to amy pertinent existing documentation: (1) Gated ADCs: BPMs, Toroids, Wire-Scanners, Profile Monitors: Steph (2) Controlled Devices: Power Supplies, Stepper Motors: Dayle (3) Fast Feedback: TBD (4) Timing RonC (5) Shared Utilities RonC (a) SLC Database (b) SLC Message Service (c) Asynchronous Update (d) Miscellaneous Library Routines ACTION: Estimate of time by July 14, ACTION: Func reqts done by ~Aug 27 The following areas will NOT be supported by the SLC IOC: (1) MPS Module Configuration (2) MPS Algorithm Processing and Rate Control (3) BitBus Power Supply Control (4) KISnet Communication (5) Micro-to-Micro Communication via Alpha (6) Crate Monitoring (7) Analog Signal Monitoring (8) Digital Input/Output (9) Klystron (10) SLC-Style Error Logging (use CMLOG instead) (11) Direct Hardware Access (ie, CAMCOM) (12) Debugging from VMS (13) Video Interface (catcart) (14) Other specialized SLC-style diagnostics (15) Multibus Exerciser (16) Special purpose (non-fast-feedback) feedback (10) Micro Code Source: Source resides on slcs1 or slcs2 solaris machine under /mccdev/nfs_ref/rmx and /mccdev/nfs_ref/rmx2. The following directories are of interest bpm : Gated ADCs: BPMs, Toroids, Wire-Scanners, Profile Monitors mgnt: Controlled Devices: Power Supplies, Stepper Motors fbck: Fast Feedback time: Timing dbs: SLC Database slclib: SLC Message Service async: Asynchronous Update slclib, reentrant: Miscellaneous Library Routines The following directories can be ignored: anlg, bcom, cam, catcart, cow, crate, diagnostics, fb30, b31, fb69, fb73, fb88, fbpl, fbpt, fdbk, fusion, klys, linkboot, mbe, mcom, md86, md86vax, md286, md286vax, mgnt_oct89, mgnt_old, mpg, mpsc, nucleus, plmvax, ram86, slcnet, stat, test, verex Stephanie