Difference between revisions of "Controls-status-8-aug-2008"
From GlueXWiki
m |
m |
||
| Line 5: | Line 5: | ||
This layer controls the hardware and contains all control loops. Main components are an Allen-Bradley PLC and the hardware it controls, and manufacturer-supplied ethernet-accessible devices (e.g. CAEN mainframe). | This layer controls the hardware and contains all control loops. Main components are an Allen-Bradley PLC and the hardware it controls, and manufacturer-supplied ethernet-accessible devices (e.g. CAEN mainframe). | ||
| − | |||
| − | |||
* Met again with Steve Lassiter, controls engineer. Discussed general aspects of A-B controllers, implementation strategy, and related concerns. | * Met again with Steve Lassiter, controls engineer. Discussed general aspects of A-B controllers, implementation strategy, and related concerns. | ||
| Line 18: | Line 16: | ||
This layer displays, archives, and alarms on data from the DCS layer. EPICS is our current choice for this layer, but as Elke has noted, we may not need EPICS as the functionality of the DCS and ECS layers grow towards each other. | This layer displays, archives, and alarms on data from the DCS layer. EPICS is our current choice for this layer, but as Elke has noted, we may not need EPICS as the functionality of the DCS and ECS layers grow towards each other. | ||
| − | |||
| − | |||
* Nothing new to report. | * Nothing new to report. | ||
| Line 27: | Line 23: | ||
This layer integrates run control and all slow controls into a coherent system. AFECS from the JLab DAQ group is our current choice. This layer implements high-level state machines using the AFECS scripting language COOL. | This layer integrates run control and all slow controls into a coherent system. AFECS from the JLab DAQ group is our current choice. This layer implements high-level state machines using the AFECS scripting language COOL. | ||
| − | |||
| − | |||
* Vardan has been testing and improving AFECS. | * Vardan has been testing and improving AFECS. | ||
* Run control worked fine with about 1000 components, but multiple servers were needed, and some new features are being added to the cMsg package to help with scalability. | * Run control worked fine with about 1000 components, but multiple servers were needed, and some new features are being added to the cMsg package to help with scalability. | ||
* Recent successful test involved DAQ setup and a Wiener (?) mainframe communicating via SNMP. Disruption of the operation of the mainframe was detected by Run Control. | * Recent successful test involved DAQ setup and a Wiener (?) mainframe communicating via SNMP. Disruption of the operation of the mainframe was detected by Run Control. | ||
Revision as of 15:43, 7 August 2008
Recall I presented a three-tier architecture at the System review:
Device Control System - DCS
This layer controls the hardware and contains all control loops. Main components are an Allen-Bradley PLC and the hardware it controls, and manufacturer-supplied ethernet-accessible devices (e.g. CAEN mainframe).
- Met again with Steve Lassiter, controls engineer. Discussed general aspects of A-B controllers, implementation strategy, and related concerns.
- If desired, he can give us an unused PLC from another manufacturer (not Siemans).
- General agreement that simple analog sensors/actuators (0-10V) and I/O modules are the best choice.
- Initiated discussion with Accelerator on fast-feedback from active collimator to steering magnets. Meeting planned for later in Aug.
- Discussed possibility of purchasing A-B equipment early to test with various magnet power supplies.
Supervisory Control and Data Acquisition - SCADA
This layer displays, archives, and alarms on data from the DCS layer. EPICS is our current choice for this layer, but as Elke has noted, we may not need EPICS as the functionality of the DCS and ECS layers grow towards each other.
- Nothing new to report.
Experiment Control System - ECS
This layer integrates run control and all slow controls into a coherent system. AFECS from the JLab DAQ group is our current choice. This layer implements high-level state machines using the AFECS scripting language COOL.
- Vardan has been testing and improving AFECS.
- Run control worked fine with about 1000 components, but multiple servers were needed, and some new features are being added to the cMsg package to help with scalability.
- Recent successful test involved DAQ setup and a Wiener (?) mainframe communicating via SNMP. Disruption of the operation of the mainframe was detected by Run Control.
