1.  Fritz, Neeti, Usha  Fritz had to cancel. He will make a presentation on Monday.  3 Communications paths u Direct connection u 50-wide T’n’F cable u 1553 bus < ---- concentrate on this  Monitoring & Control is presently carried out using Python applications applied over Epics and VxWorks running in d0olctl18(19)(34).  Communications are made to the control dsp on the control board. PDT Monitoring & Control

2. 1553 Bus Progress  There are thirteen 1553 busses. 10 are in operation. The other 2 don’t have any front-ends as of now.  Difficulty in maintaining stabilility u Weak signals lead to implementing a hardware option on the control board u Some control board failures can disable communications for every PDT on a bus (up to 9).

3. 1553 Bus Scan Test

4. Monitoring Application  PDT Interface (old picture) from Fritz u displays the 4 LVPS levels, board temperature, differential gas pressure and something labeled “status”.  ASCII file allows adding more PDT’s.  Not yet using this information to generate alarms.

5. Downloading  PDT’s have been ahead of other systems in downloading capability (until recently).  Pre-run procedure sets up PDT’s, loads channel enables, turns off pulsers, writes short multiblock including the module ID, and loads pipeline delay with a default pickle file u Comics.py & u ComicsTalk.py s set MUO.CMETP (for example) s set MUO.CMETP.FE.231 (for example) s quit  Above procedure exposes some timeout errors in Epics control.

6. Downloading  Sten and Herman have tested a control dsp program suitable for the larger multiblock (PDT 112) and loaded 3 others (032, 021, 124).  Usha/Neeti are creating pickle files that include a more substantial multiblock, including chamber-dependent information.  Going to the multiblock program on a widespread basis is best reserved for the two-week shutdown.  Finally, the PDT download could be implemented in the.xml files we use to define the triggers.

7. Summary  Some download and monitoring capability but …  There’s a long way to go.