180 likes | 313 Views
RF controls issues. Brief overview & status Requested from AB/CO Hardware, Timing, VME/FESA for LEIR, SPS, LHC Controls for LHC RF Power systems Interfacing of PLCs to control system Application development: “Operational” interface “Specialist control & diagnostic” applications.
E N D
RF controls issues Brief overview & status Requested from AB/CO Hardware, Timing, VME/FESA for LEIR, SPS, LHC Controls for LHC RF Power systems Interfacing of PLCs to control system Application development: “Operational” interface “Specialist control & diagnostic” applications AB/CO TC
RF group’s requests from AB/CO • LEIR • Power system (P. Maesen, M. Paoluzzi): • Schneider PLCs interfaced via IEPLC • Test EM written by FE section • Access via knob tested • Low-Level system • DSP hardware collaboration with BNL • Special VME64X crate • Specific software requirements: • Soft timings & GFAs • Digital DAQ & displays • DSP code loader & board driver (FESA) • Discussed in detail elsewhere • (M-E Angoletta’s presentation to AB/CO, 29 Jan 2004) AB/CO TC
RF group’s requests from AB/CO • SPS Timing • Integration of timing for RF systems into AB/CO infrastructure • TG3 timing receiver modules upgrade? AB/CO TC
Replacement of SPS RF TG3 modules • Present situation: • 140 G64 TG3 cards grouped in 16 crates • opto-isolation/pulse stretcher/fanout • Connected via MIL1553/specific crate controller • TG3s programmed directly via RF specialist software • “legacy timing” software fix for 2004 • Limitations of TG3 & current system • Memory layout by SPS “cycle type” • (... Julian?) • Proposition for upgrade (J. Lewis/J. Serrano) • Replace all TG3s with new CTRG • Retain existing crate & hardware infrastructure • Control in standard way via timing equipments (PTIM...) AB/CO TC
RF group’s requests from AB/CO • LHC • Deliverables agreed with R. Lauckner, A. Daneels, P. Charrue in September 2003 • VME hardware for low-level systems • for ACS + ADT + beam control + synchro systems • total of 55 VME PPC CPUs • special VME crates provided by AB/RF • Front-end software • First version of FESA for equipment tests • delivered and currently used by AB/RF for lab tests • Support including drivers (A. Gagnaire) • good support from FESA team • currently using simple direct VME access for tests AB/CO TC
RF group’s requests from AB/CO • LHC contd. • Timing • One GMT timing module per VME crate (CTRP) • No GMT required for PLCs (NTP for timestamping) • WorldFIP + Function Generators • 2 FGC crates in UX45 Faraday Cages • 1 FGC crate in SR4 • WorldFIP cabling currently being defined • etc. • see milestones table (LHC-CP Commissioning) AB/CO TC
LHC ACS 400MHz controls overview Note the clear separation between Low-Level (VME) and Power (PLC) systems CMW Front-end server (PC/FESA) Ethernet Power system Fast interlocks & timestamping Low-Level system PLC Schneider (20 units) VME (1 crate) VME (32 crates) FIPIO Interlocks BIC Analog Remote I/O AB/CO TC
LHC ADT Damper controls overview Architecture is identical to ACS system CMW Front-end server (PC/FESA) Ethernet Power system Fast interlocks & timestamping Low-Level system PLC Schneider (8 units) VME (1 crate) VME (8 crates) FIPIO Interlocks BIC Analog Remote I/O AB/CO TC
LHC RF Application software needs • 2 types of application software: • Standard “operational” applications • used to drive the accelerator in “normal” operation • access from generic control room applications • knobs, sequencers, etc. • needs to be very reliable • “Specialist” or “control & diagnostic” applications • detailed access to equipment parameters • synoptics & equipment-specific GUIs • used by operators as well as equipment specialists • more detail, less need of reliability • Discussions with various teams in AB/CO • Various solutions proposed AB/CO TC
LHC RF Power systems control • 2 inter-related issues: • PLC interfacing to the control system • IEPLC • OPC • UNICOS • Direct MODBUS-TCP/IP • Application software • Java • PVSS • LabView, Visual Basic, MatLab, .....? • PLC expert tools (Schneider PL7, Web interface) AB/CO TC
Present solution used in ACS test stands • PLCs connected via MODBUS-TCP/IP to OPC server (Windows 2000) • Java GUI applications via OPC/CMW gateway server (K. Kostro) • From master Excel file • PLC config file • CMW DB (via SQL script) • Generation of Java wrapper classes CMW config DB Java GUIs CMW (W2000) CMW/OPC gateway OPC server (Schneider) Ethernet + MODBUS-TCP/IP PLC Schneider (2 units) FIPIO Remote I/O AB/CO TC
A variety of proposed solutions • IEPLC + FESA + Java applications • “Standard” AB/CO • Lightweight at level of PLCs • Reliable • PPM • Difficult to develop synoptics, etc. • UNICOS/PVSS (cf. Cryo system) • Trending, logging, alarms, etc. • Comprehensive configuration tools • Heavy at level of PLCs AB/CO TC
A variety of proposed solutions • PVSS + direct MODBUS-TCP/IP (cf. QPS) • re-use packages developed for UNICOS, QPS, Vacuum • configuration tools • Lightweight at PLC level • requires some expert knowledge to configure • PVSS + OPC (cf. Vacuum system) • extra OPC server layer (Windows, managed by IT) • code re-use as above AB/CO TC
A variety of proposed solutions • OPC + .... • OPC is industry standard • configuration very easy • can easily interface to LabView, Visual Basic, etc. for rapid development in test systems • access from standard control system components possible via CMW • would require “operational” CMW/OPC gateway service AB/CO TC
A variety of proposed solutions • 2 communication channels in parallel according to type of application: • Operation • IEPLC + FESA + Java • simple interface • ON/OFF/STANDBY + a few settings + alarms • supported by AB/CO • Specialist • OPC + ... (PVSS, LabView, etc.) • detailed access to all equipment parameters • supported by AB/RF AB/CO TC
SPECIALISTS TOOLS OPERATION TOOLS ? LABVIEW PVSS JAVA CMW Alarms DB Log Operators Interfaces OPC Server (Windows) FESA Front-end server OPC SERVER (OFS) FESA Devices IT Support PLC OPC ALL PLC DATA R/W IEPLC Com Buffer [CMD] [AQN] [CONF] AB/CO Support AB/RF Support AB/CO TC
Conclusion • What support can we count on from the various AB/CO teams for • interfacing of PLCs? • application software development? • building blocks for logging, alarms, post-mortem • What solution(s) to choose for • “operational” applications? • “specialist” applications? AB/CO TC