-
Notifications
You must be signed in to change notification settings - Fork 2
RIKEN PLC
Wiki > The Backend System > Specific Device IOC > PLCs > RIKEN PLC
The main PLC on RIKEN is responsible for controlling and monitoring the various systems on the beamlines, e.g. vacuum equipment and magnet cooling. The Schneider PLC IOC runs a CMD file specific to RIKEN which then loads a specific DB file to give access to designated PLC registers (memory addresses) via the ASyn MODBUS driver.
The groups of variables are defined in the document RIKEN PLC IBEX Specification (which can be found in the RIKEN FE ICP Discussions area of SharePoint) and are as follows: (all are readonly, apart from the vacuum valve controls, see below)
- Separator vacuum status
- Solenoid status
- Kickers water, vacuum and MOL (Magnet Off Light) status
- Kickers status and output (voltage and current)
- GH (Gauge Head) vacuum gauge status
- LV (Line Valve), AMGV (All Metal Gate Valve) and FSOV (Fast Shut Off Valve) vacuum valve status
- LV, AMGV, FSOV, control (writable ````from IBEX, but only to open the valves)
- BP (Backing Pump) and TP (Turbo Pump) vacuum pump status
- PIV (Pump Isolation Valve) interlock status
- LV, AMGV, FSOV, BPV1 interlock status
- BB (BeamBlocker) status and information
- Magnets Klixon interlock status (a Klixon is a thermal switch which opens/closes at a set temperature)
- Magnets cooling water flow status, rate and temperature
- RBox (Rectifier Box) and bypass interlock status
- MOL (Magnet Off Light) status (purely the status of the bulb, not the magnet state)
The PLC IOC also loads a separate DB file (TEMPMON) for monitoring temperatures of a selection of magnets (RQ1, RQ2, RB1) and is purely for logging purposes. This is at the request of the Electrical Controls Group who are performing an experimental analysis.
The PLC is connected to the ISIS Controls Network using a fixed/static IP address which is specified in the globals.txt file. Also in this file are macros to specify the connection type (TCP in this case) and which configuration (CMD file) to load. The PLC also has a "local" network to connect to its satellite nodes and HMI screens.
The DB file is generated using a set of template files which correspond to types of PLC variables and readback values. The substitutions file follows the structure of the Specifications document referenced above, and so it is advised to read them in parallel when required. See the DB area of the IOC directory.
The CMD file is located in the devicesdirectory of the IOC.