1 / 13

Answers to DCS questions Detector: SPD

Answers to DCS questions Detector: SPD. PV1: 2 people (M. Caselle, L. Vinogradov) in contact with P. Chochula PV2: at least with PVSS 2.12.1, ARCHIVE configuration POOR EXTRACTION of archived data to perform offline analysis (?) TREND configuration option POOR and SLOW

malachi-hood
Download Presentation

Answers to DCS questions Detector: SPD

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Answers to DCS questionsDetector: SPD • PV1: 2 people (M. Caselle, L. Vinogradov) in contact with P. Chochula • PV2: at least with PVSS 2.12.1, • ARCHIVE configuration POOR • EXTRACTION of archived data to perform offline analysis (?) • TREND configuration option POOR and SLOW • PV3: Most of our experience with PVSS 2.12.1 • framework v. 1.2.3 • components v. 1.2.8 • ELMB v.1.0 components • some additional patches for PVSS 2.12.1 ALICE Week / DCS Workshop - Sep 23, 2004

  2. Answers to DCS questionsDetector: SPD • PV4: see PV2 • PV5: Starting to use PVSS 3.0, better behaviour wrt the issues mentioned in PV2 ALICE Week / DCS Workshop - Sep 23, 2004

  3. Answers to DCS questionsDetector: SPD • OPC1: • CAEN SY1527 – HV A1519 board • CAEN HV OPC Server - Rel. 2.7 (July_03) • SY 1527firmware version 1.14.03 • Network Interface Card + TCP/IP protocol • WIENER PL500 – LV PS • SLiC OPC server (Mark Beharrell) • Wiener OPC server v.1.6, currently under test with PVSS 3.0 • CANbus adapter: PCI-CAN Kvaser card • ELMB – LV regulator board • OPC20CanOpen.OPC v.2.5 (currently under test v.2.5+) • CANbus adapter: PCI-CAN Kvaser card • OPC2: OPC servers used with the Framework ALICE Week / DCS Workshop - Sep 23, 2004

  4. Answers to DCS questionsDetector: SPD • OPC3: • CAEN HV OPC server:OK! • WIENER PL500: • SLiC OPC server • requires to set up a proper config file • PVSS implementation depends on this config file! • Wiener OPC server hopefully much more stable … • ELMB: • CANopen OPC Server v.2.5 • Configurable so there are several items (i.e. ports and channels that can be customized) • v.2.5+ has improved performances combined with the new framework components fwElmb 2.0.4 ALICE Week / DCS Workshop - Sep 23, 2004

  5. Answers to DCS questionsDetector: SPD • ELMB (cont’d) • Some incorrect functioning have been observed: • 1) ELMB is not configuring (write outputs) from INIT section (while it should to do this, after command “129”, according to the manual ) • 2)‘SAVE’ command doesn’t work not only from INIT section of the server but even in a situation when the server was already been started. It is possible to do this in a pre-operational mode after command “129” from Applicom client. • 3)The connection is not reliable: gets lost. • The chain looks like following: ELMB – CANserver – PVSSopcCLIENT. • I switch on ELMB power supplies, start PVSS application(panel) – all is working for many hours.If I switch OFF ELMB power supply the connection is lost. How to resume the application work?Sometimes(!) helps the following: to stop and to run PVSSopcClient manager from the console or to restart PVSS.Sometimes it is necessary to switch off and on the ELMB several times trying to resume the work of the full chain. • It helps to have in parallel to PVSSopcClient another client (like Applicom). • So there is any procedure for restarting application after power supply failure. • It sounds not so regular you must work with additional manipulations with other Software tools. ALICE Week / DCS Workshop - Sep 23, 2004

  6. SPD DCS COOLING HVPS FERO LVPS HV Crate LV Crate Sector 1 10 SPD Sectors A1519 board 12 chs LV-1 HV-1 VR board 12 VRs HV Half-Sect 1 LV Half-Sect 1 Soft-interlock Answers to DCS questionsDetector: SPD • FSM1: • DCS hierarchy ALICE Week / DCS Workshop - Sep 23, 2004

  7. Answers to DCS questionsDetector: SPD • FSM2: switching off HV if LV trips and (safer) also switching off LV if HV trips • FSM3: if more channels in the Half-Sector trip that could require disabling of the full corresponding HV-board and VR board etc • FSM4: reasonable FSM diagrams both for HV and LV, • no need of the REPAIR processes • different ramp-up/down speeds maybe needed ALICE Week / DCS Workshop - Sep 23, 2004

  8. Answers to DCS questionsDetector: SPD • CO1: OS for DCS will be WinXP • CO2: additional applications like OPC servers, Root, MS Office (e.g. if we will use Excel Reports) • CO3: monitoring (occasionally) • CO4: calibration data ~300 MB/scan. Strategy not yet defined, but the frequency of scans will remain low (like ~once per week…) • CO5: lxplus, interface to offline for analysis of scanfiles ALICE Week / DCS Workshop - Sep 23, 2004

  9. Answers to DCS questionsDetector: SPD • DB1: • power supplies: standard archiving • VR boards: I,V per half-stave (240 parameters in total) • temperature monitoring: 240 temperature probes in total, read once per second. Temperatures are expected to stay stable, so data will be archived only in case of instabilities • MCM parameters (4 parameters)x120 are readout every 5 seconds, values are expected to remain stable, archival only if out of range values • DB2: as described in the URD ALICE Week / DCS Workshop - Sep 23, 2004

  10. Answers to DCS questionsDetector: SPD • FE1: Once per run or less • FE2 • Full reconfiguration of SPD is needed to read back the FERO settings. In this case the SEU detection will be made by offline: no action from DCS is expected since the reconfiguration cures the SEU • In case of SEU in sensitive DAC the run must be stopped and SPD must be reconfigured. Expected frequency is once per ~200 hours (or even less) ALICE Week / DCS Workshop - Sep 23, 2004

  11. Answers to DCS questionsDetector: SPD • FE3: • See DB1 and URD for list of parameters • In case of dangerous temperature trend the power has to be switched off. This could happen only if cooling fails, which will anyway trigger the DCS action. • FE4: • Calibration (threshold scan) is done automatically by router cards. DCS will trigger this procedure and read back the calibration data. TRG and DAQ must be stopped during this procedure. • SPD will be autocalibrated very rarely (like ~once per week, to be defined later) ALICE Week / DCS Workshop - Sep 23, 2004

  12. Answers to DCS questionsDetector: SPD • RS1: no plan to use serial interfaces • LV1: depending on the final solution • PS sources with Voltage Regulators: • Finest grain at the level of the regulator board • PS will power in a single board, i.e. 20 channels @ 5V/50A • PS sources without VR: • 120 channels @ 1.8/7A, 120 channels @ 2.5/0.5A • E.g. 20 A3009 modules (CAEN EASY3000), 12 ch. each • LV2: no need to change voltage remotely ALICE Week / DCS Workshop - Sep 23, 2004

  13. Answers to DCS questionsDetector: SPD • PL1: • Current pre-installation plan: • Final tests, ITS integration Feb ’06 – May ’06 • Prepare for install. in the pit May ’06 – Jun ’06 • Ready for install. in UX25 Jun ‘06 • DCS functionality needed: • FERO, cooling, LV, HV, database (config.) Feb ’06 • Powered racks, network, … May ’06 • PL2: • Start SPD-DCS installation May ’06 ALICE Week / DCS Workshop - Sep 23, 2004

More Related