Difference between revisions of "Field Bus and Controller Specifications"

From GlueXWiki
Jump to: navigation, search
m
m
Line 1: Line 1:
 
'''Introduction'''
 
'''Introduction'''
  
There are innumerable possibile choices for sensors, actuators, etc. for use in Hall D, independent of the slow controls framework chosen (EPICS, PVSS, DOOCS/TINE, etc).  These devices communicate via one of number of control networks (CAN, I2C, DEVICENET, ProfiBus, WorldFIP, TCP/IP, etc).  For practical reasons we need to minimize the number of network types we deploy in the hall.
+
There are innumerable possible choices for sensors, actuators, etc. for use in Hall D, independent of the slow controls framework chosen (EPICS, PVSS, DOOCS/TINE, etc).  These devices communicate using one of large number of control network systems (CAN, I2C, DEVICENET, ProfiBus, WorldFIP, TCP/IP, etc).  For practical reasons we need to minimize the number of network types we deploy in the hall.
  
Thus in the following I propose a minimal set of control networks for use in Hall D.  If some particular application needs a special sensor or controller that is not compatible with the set below, contact me and we will find a way to accomodate it.  The idea is that whenever possible detector and electronics designers should use devices compatible with the choices below.
+
Thus in the following I propose a minimal set of control networks for use in Hall D.  If an application needs a special sensor or controller that is not compatible with the set below, please contact me.
  
  
 
'''Note on PLC usage in Hall D'''
 
'''Note on PLC usage in Hall D'''
  
PLC's (Programmable Logic Controllers) are highly reliable process controllers that are in widespread use in industry, and are routinely used in critical applications.  They are not general purpose computers, and instead have a single purpose in life, to run a control loop at regular intervals.  Although other labs use them routinely, JLab does not, and I'm not sure why (speculation:  JLab is too EPICS-happy).  PLC's are typically programmed by trained controls engineers, not by scientists, as special languages and techniques are used (similar to how FPGA programming is done by specially trained electrical engineers).
+
PLC's (Programmable Logic Controllers) are highly reliable process controllers that are in widespread use in industry, and are routinely used in critical applications.  They are not general purpose computers, and instead have a single purpose in life, to run a control loop at regular intervals.  Although other labs use them routinely, JLab does not, and I'm not sure why (speculation:  JLab is too EPICS-happy, and early EPICS systems could not communicate with PLC's).  PLC's are typically programmed by trained controls engineers, not by scientists, as special languages and techniques are used (similar to how FPGA programming is done by specially trained electrical engineers).
  
JLab typically uses PLC's in cryo-control systems, and we plan to use one (Allen-Bradley, model to be chosen) for our solenoid.  We expect that the solenoid cryo-control system will use up less than one third of the PLC capacity, so we can use the PLC for other purposes.  Note that PLC programming can be highly prioritized, so that e.g. solenoid control will not be compromised by a lower priority control loop.
+
JLab typically uses PLC's in cryo-control systems, and we plan to use one for our solenoid (Allen-Bradley, model TBD).  We expect that the solenoid cryo-control system will use up less than one third of the PLC capacity, so we can use the PLC for other purposes.  Note that PLC control loops can be strictly prioritized, so that e.g. solenoid control will not be compromised by a lower priority control loop.
  
 
The PLC is ideal to control the following systems:
 
The PLC is ideal to control the following systems:
Line 18: Line 18:
 
* all gas systems
 
* all gas systems
  
An open question is what other systems might be controlled by the PLC.  As reprogramming the PLC takes some time and requires a trained engineer, it may not be appropriate for many systems, particularly simple ones with benign failure modes.  Further, we have to understand the cost of setting up a PLC-compatible system at a remote site (Tim and I are working on this).
+
An open question is what other systems might be controlled by the PLC.  As reprogramming the PLC takes some time and requires a trained engineer, it may not be appropriate for many systems, particularly simple ones with benign failure modes.  Further, we have to understand the cost of setting up a PLC-compatible system at a remote institution (Tim and I are working on this).
  
  

Revision as of 15:16, 28 January 2008

Introduction

There are innumerable possible choices for sensors, actuators, etc. for use in Hall D, independent of the slow controls framework chosen (EPICS, PVSS, DOOCS/TINE, etc). These devices communicate using one of large number of control network systems (CAN, I2C, DEVICENET, ProfiBus, WorldFIP, TCP/IP, etc). For practical reasons we need to minimize the number of network types we deploy in the hall.

Thus in the following I propose a minimal set of control networks for use in Hall D. If an application needs a special sensor or controller that is not compatible with the set below, please contact me.


Note on PLC usage in Hall D

PLC's (Programmable Logic Controllers) are highly reliable process controllers that are in widespread use in industry, and are routinely used in critical applications. They are not general purpose computers, and instead have a single purpose in life, to run a control loop at regular intervals. Although other labs use them routinely, JLab does not, and I'm not sure why (speculation: JLab is too EPICS-happy, and early EPICS systems could not communicate with PLC's). PLC's are typically programmed by trained controls engineers, not by scientists, as special languages and techniques are used (similar to how FPGA programming is done by specially trained electrical engineers).

JLab typically uses PLC's in cryo-control systems, and we plan to use one for our solenoid (Allen-Bradley, model TBD). We expect that the solenoid cryo-control system will use up less than one third of the PLC capacity, so we can use the PLC for other purposes. Note that PLC control loops can be strictly prioritized, so that e.g. solenoid control will not be compromised by a lower priority control loop.

The PLC is ideal to control the following systems:

  • solenoid
  • cryo-target
  • all gas systems

An open question is what other systems might be controlled by the PLC. As reprogramming the PLC takes some time and requires a trained engineer, it may not be appropriate for many systems, particularly simple ones with benign failure modes. Further, we have to understand the cost of setting up a PLC-compatible system at a remote institution (Tim and I are working on this).


Hall D Subsystem Slow Controls Specifications

Below I list choice of controls system or network for Hall D subsystems:

Subsystem Control System
solenoid A-B PLC
cryo-target A-B PLC
gas systems A-B PLC
high voltage x
low voltage x
VXS crates x
Cockroft-Walton bases x
goniomenter x
network devices x