Integrating Externally Developed Systems for SNS Linac Cooling and - - PowerPoint PPT Presentation

integrating externally developed systems for sns linac
SMART_READER_LITE
LIVE PREVIEW

Integrating Externally Developed Systems for SNS Linac Cooling and - - PowerPoint PPT Presentation

Integrating Externally Developed Systems for SNS Linac Cooling and Vacuum P.S. Marroquin, Los Alamos National Laboratory, Los Alamos, NM 87545, USA pilar@lanl.gov ICALEPCS 2001, San Jose, CA, USA, Nov 27-30, 2001 Poster TUAP063 Work


slide-1
SLIDE 1

SNS Linac SNS Linac

1

Integrating Externally Developed Systems for SNS Linac Cooling and Vacuum

P.S. Marroquin, Los Alamos National Laboratory, Los Alamos, NM 87545, USA pilar@lanl.gov

ICALEPCS 2001, San Jose, CA, USA, Nov 27-30, 2001 Poster TUAP063

Work supported by the Office of Basic Energy Science, Office of Science of the US Department of Energy, and by Oak Ridge National Laboratory.

slide-2
SLIDE 2

SNS Linac SNS Linac

2

External contractors are developing the local cooling and vacuum control systems for the Spallation Neutron Source (SNS) linac. Soon these systems will be integrated into the facility-wide controls system. Allen-Bradley Logix5000 series programmable controllers, populated with appropriate input/output modules, were selected as the local controllers. These controllers will be interfaced to the facility-wide control system via VME systems with PowerPC processors running the Wind River VxWorks operating system and Experimental Physics and Industrial Control System (EPICS) front-end controller software. This paper describes the interface and integration issues driven by project, cooling system and vacuum system requirements and hardware selections.

Abstract

slide-3
SLIDE 3

SNS Linac SNS Linac

3 I/O

IOCs Programmable Controllers OPIs

DTL RCCS DTL Vacuum CCL RCCS CCL Vacuum

2 3 4 5 6

SNS DTL and CCL RCCS and Vacuum Control Systems

RGAs Other Devices 2 3 4 5 6 2 3 4 2 3 4 I/O I/O I/O I/O I/O RGAs Other Devices I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O I/O RS-485 RS-485 Event Link/RTDL MPS Ethernet Mod 1 Tank 1 Tank 1 Mod 1

H a r d w i r e I n t e r l

  • c

k s H a r d w i r e I n t e r l

  • c

k s

Intel based Linux EPICS Operator Screens Archiving Logging Alarm Management Boot Hosts PowerPC VME VxWorks EPICS IOC Channel Access Supervisory Control Alarm Checking MPS local inputs Event Link/RTDL EtherNet/IP to PLCs RS-485 AB ControlLogix I/O Modules Ladder Logic Local Control Closed Loop Control PID Interlocks EtherNet/IP to/from IOC

LLRF LLRF LLRF LLRF LLRF LLRF LLRF LLRF LLRF LLRF Monitor, Control, Interlocks Monitor, Control, Interlocks Monitor, Control, Interlocks Monitor, Control, Interlocks

Brief Background

slide-4
SLIDE 4

SNS Linac SNS Linac

4

Interface Between IOC and PLC

  • Selection of a communication protocol, EtherNet/IP
  • Creating and reaching agreement on signal lists
  • Mapping IOC process variables (PV) to PLC tags
  • IOC issuing commands in the form of requests
  • Creating and naming tags for transfer to IOC
  • Optimizing data transfer between PLC and IOC

Issues

slide-5
SLIDE 5

SNS Linac SNS Linac

5

Serial Based Devices

  • Decision to use serial ports on IOC rather than PLC
  • Device driver development
  • Serial type selected , RS-485, and network layout
  • Distributed control

Issues (continued)

slide-6
SLIDE 6

SNS Linac SNS Linac

6

Control loops over Ethernet

  • PID loops dispersed over IOCs and PLCs on non-dedicated

networks

Issues (continued)

slide-7
SLIDE 7

SNS Linac SNS Linac

7

EPICS displays vs. PLC displays

  • Cost, development and maintenance of local PanelView

displays

  • Redundant control screens on different platforms

Issues (continued)

slide-8
SLIDE 8

SNS Linac SNS Linac

8

Alarm Checking and Management

  • The IOC as the appropriate location for alarm checking

functions versus the PLC

  • Alarm limit parameter maintenance in one place

Issues (continued)

slide-9
SLIDE 9

SNS Linac SNS Linac

9

Conclusion

The criteria used to make these decisions include:

  • Meet system requirements
  • Provide reliable operation
  • Minimize equipment cost
  • Minimize development and maintenance efforts

By working closely with external systems integrators we are able to consider these issues from an integrated system perspective.