Safe Operation of the CSC Subdetector

To operate the detector safely:
  • Monitor DCS and respond appropriately to any errors, as outlined in the DCS Error Handling section below
  • Follow Emergency Procedures

Emergency Procedures

Your first priority is to protect the people and hardware at the experiment. When in doubt, do more rather than less to protect the system. It is much easier to turn things back on after a false alarm than to fix them after a real alarm.

Follow all CERN procedures for infrastructure or personnel emergencies.

Show Instructions Hide Instructions

CSC Emergency Procedures/Shutoff

  1. Turn OFF ALL of the CSC subsystem by switching the main STATE menu on the top page (CMS_CSC) to OFF
    • Global DCS shifter can do this independently or after consulting CSC shifter or Shift Leader
    • CSC Shifter can do this independently or after consulting Global DCS Shifter or Shift Leader
  2. If DCS is non-operative
    • CSC LV system: Manually turn off OPFC modules in S4F04 level 2 (-1) through elevator doors and to the right
      • If possible, have an expert or experienced person turn them off from the front of the rack
    • OR remotely trip the twidos for rack S4F04
    • NEVER turn them back on! Only an expert can do this safely!
  3. Turn OFF Racks with CSC equipment via Central DCS
    • If the racks are off because of DSS or Central DCS intervention, always do step 1
  4. Call the CSC CEO
  5. Leave CSC in the OFF state
    • A CSC expert team will be formed to assess the extent of the problem and organize a safe recovery

Evacuation Alarm

  • Follow all CERN/CMS procedures.
  • If possible, take the shifter's mobile with you to contact the CEO (161972)

Problems with the CSC Subsystem

  • Call CEO
  • Contact CMS Shift Leader

Water Flow Stop UXC S1 S2 S4
Water LEAK UXC S1 S2 S4
POWER OUTAGE IMMANENT UXC S1 S2 S4
POWER OUTAGE UXC S1 S2 S4
POWER RETURN UXC S1 S2 S4

-- CSC Action Matrix for DSS -- What does DSS do for an alarm in a CSC rack?

-- CSC Action Matrix for DCS -- What does DCS do for an alarm in a CSC rack? This alarm can come from Global DCS or CSC DCS.

Operating Instructions for the Old DCS Interface

Show instructions for the OLD DCS Interface Hide Instructions for the OLD DCS Interface

DCS Errors (Old Interface)

If you see anything in the red error state in DCS, take the following action:

High Voltage (HV) Trip
Show Instructions Hide Instructions

  • HV Channel Trip (first or second time)
    • Select the chamber in error from the summary panel
    • Click "force on"
    • The state should be "Ramping UP"
  • HV Channel Trip (~third time)
    • Mask out the channel by following these steps:
      • Select the chamber in error from the summary panel
      • Select the tripped channel
      • Uncheck "isEnabled" (note- the check is nearly invisible, but the button is green if enabled, gray if disabled)
      • "force on"
    • The tripped channel should now be disabled (the 'isEnabled' button should be gray)
    • Notify the CEO that the channel has been disabled.
    • Log the disabled channel in the ELOG and on the whiteboard.
  • Chamber HV Trip (no single tripped channel)
    • Check the boxes:
      • "Module Status" (bottom-right of the panel)
      • "MS_STATUS" (status of the master board. Bottom of the panel)
      • Click "Force on"
    • If the chamber HV must be masked (after repeated trips)
      • From the chamber's HV panel, click on the check-mark next to the STATE button
      • Select 'Disable'
      • Notify the CEO that the HV for this chamber has been disabled.
      • Log the disabled chamber in the ELOG and on the whiteboard.

Dubna HV Errors Summary (ME1/1)
Show Instructions Hide Instructions In case of a HV trip in the ME1/1 chambers, do the following in DCS:

  1. Select the chamber in error from the summary panel
  2. From the HV panel set the STATE to "OFF"
  3. Once it has turned off, set the STATE back to "ON"
If the chamber HV must be masked (after repeated trips)
  1. From the chamber's HV panel, click on the check-mark next to the STATE button
  2. Select 'Disable'
  3. Notify the CEO that the channel has been disabled.
  4. Log the disabled chamber in the ELOG and on the whiteboard.

Maraton LV Errors Summary
Show Instructions Hide Instructions A maraton trip is a serious problem. Each Maraton supplies LV Power for up to 3 Trigger Sectors (TS).

  1. Check how many Maratons have tripped:
    • If more than 2, call the CEO (161972) and inform the Shift Leader.
    • If there are two in the same UXC Rack, it's possible that the AC breaker in S4 has tripped. Call the CEO (161972) and inform the Shift Leader.
    • If a single maraton has tripped, either the OPFC in S4F04 or the maraton itself has tripped. If DCS can communicate with the maraton, the maraton itself has tripped. If not, the OPFC is probably tripped. Call the CEO (161972) and inform the Shift Leader.
  2. Action -- after reporting the trip take this action
    1. From DCS, turn OFF the 3 PCrates in the 3 trigger sectors fed by this maraton (see table below)
    2. From DCS, turn OFF the maraton.
      • If the PFC itself tripped, DCS cannot communicate directly with the maraton. Turn it off with DCS anyway.
    3. Leave the maraton and PCrates off, and wait for CEO or expert instructions.

Maraton to Peripheral Crate / Junction Box Mapping
Some notes:

  • The essential item in DCS for the Maraton link is the Maraton CANBUS ID. This ID is linked absolutely to the physical connections labeled below, regardless of whatever else may be marked on the buttons in DCS.
  • BE CAREFUL OF POSSIBLE REVERSED ORDERING OF "ID" numbers in the DCS panel

    YE+1      
ID DCS Name Rack Name PC = pcrate JB = junction box  
1 P1_CR1_LV_MRTN/id1 X4J31c PC+1/2 PC+1/12 PC+1/1
2 P1_CR2_LV_MRTN/id2 X4J31e PC+1/3 JB+1/3 JB+1/2
3 P1_CR4_LV_MRTN/id3 X4A31e PC+1/5 JB+1/7 JB+1/6
4 P1_CR3_LV_MRTN/id4 X4A31c PC+1/4 JB+1/5 JB+1/4
5 P1_CR6_LV_MRTN/id5 X2A33j PC+1/7 PC+1/9 PC+1/8
6 P1_CR5_LV_MRTN/id6 X2A33h PC+1/6 JB+1/9 JB+1/8
7 P1_CR7_LV_MRTN/id7 X2J31c PC+1/10 JB+1/11 JB+1/10
8 P1_CR8_LV_MRTN/id8 X2J31e PC+1/11 JB+1/1 JB+1/12
    YE+2      
ID DCS Name Rack Name PC = pcrate JB = junction box  
9 P2_CR1_LV_MRTN/id9 X4J41a PC+3/1 PC+2/6 PC+3/6
10 P2_CR2_LV_MRTN/id10 X4J41b PC+2/1 JB+3/1 JB+2/1
11 P2_CR4_LV_MRTN/id11 X4A41a PC+3/2 JB+3/3 JB+2/3
12 P2_CR3_LV_MRTN/id12 X4A41b PC+2/2 JB+3/2 JB+2/2
13 P2_CR6_LV_MRTN/id13 X2A41a PC+3/3 PC+2/4 PC+3/4
14 P2_CR5_LV_MRTN/id14 X2A41b PC+2/3 JB+3/4 JB+2/4
15 P2_CR7_LV_MRTN/id15 X2J41a PC+3/5 JB+3/5 JB+2/5
16 P2_CR8_LV_MRTN/id16 X2J41b PC+2/5 JB+3/6 JB+2/6
    YE+3      
ID DCS Name Rack Name PC = pcrate JB = junction box  
17 P3_CR1_LV_MRTN/id17 X4A51a PC+4/2 JB+4/2  
17     PC+4/3    
17     PC+4/4    
18 P3_CR2_LV_MRTN/id18 X2J52b PC+4/1 JB+4/4  
18     PC+4/6    
18     PC+4/5    
    YE-1      
ID DCS Name Rack Name PC = pcrate JB = junction box  
21 M1_CR-1_LV_MRTN/id21 X4V31a PC-1/2 PC-1/12 PC-1/1
22 M1_CR-2_LV_MRTN/id22 X4V31b PC-1/3 JB-1/3 JB-1/2
23 M1_CR-4_LV_MRTN/id23 X4S31a PC-1/5 JB-1/7 JB-1/6
24 M1_CR-3_LV_MRTN/id24 X4S31b PC-1/4 JB-1/5 JB-1/4
25 M1_CR-6_LV_MRTN/id25 X2S33a PC-1/7 PC-1/9 PC-1/8
26 M1_CR-5_LV_MRTN/id26 X2S33b PC-1/6 JB-1/9 JB-1/8
27 M1_CR-7_LV_MRTN/id27 X2V31a PC-1/10 JB-1/11 JB-1/10
28 M1_CR-8_LV_MRTN/id28 X2V31b PC-1/11 JB-1/1 JB-1/12
    YE-2      
ID DCS Name Rack Name PC = pcrate JB = junction box  
29 M2_CR1_LV_MRTN/id29 X4V41a PC-3/1 PC-2/6 PC-3/6
30 M2_CR2_LV_MRTN/id30 X4V41b PC-2/1 JB-3/1 JB-2/1
31 M2_CR4_LV_MRTN/id31 X4S41a PC-3/2 JB-3/3 JB-2/3
32 M2_CR3_LV_MRTN/id32 X4S41b PC-2/2 JB-3/2 JB-2/2
33 M2_CR6_LV_MRTN/id33 X2S41a PC-3/3 PC-2/4 PC-3/4
34 M2_CR5_LV_MRTN/id34 X2S41b PC-2/3 JB-3/4 JB-2/4
35 M2_CR7_LV_MRTN/id35 X2V41a PC-3/5 JB-3/5 JB-2/5
36 M2_CR8_LV_MRTN/id36 X2V41b PC-2/5 JB-3/6 JB-2/6
    YE-3      
ID DCS Name Rack Name PC = pcrate JB = junction box  
37 M3_CR1_LV_MRTN/id37 X4S51a PC-4/2 JB-4/2  
37     PC-4/3    
37     PC-4/4    
38 M3_CR2_LV_MRTN/id38 X2V52b PC-4/1 JB-4/4  
38     PC-4/6    
38     PC-4/5    

CRB LV Errors Summary
Show Instructions Hide Instructions These occasionally occur as spurious errors in DCS. Wait to see if it goes away on its own.
To confirm if it is a 'real' error, check to see if the TMB counters incrementing:
(To find the counters, go to Page 1 and click the 'PCrate Monitor Plus/Minus' heading to open the Cyan Page, then select 'TMB Counter View')

  • Yes:
    • DCS might be wrong. Log the error and contact the CEO
  • No:
    • You may have lost communication with the crate, and need to power-cycle the crate controllers.
      • DO NOT POWER CYCLE THE ENTIRE PCRATE.
    • If you don't know how to do this, don't. Call the CEO
    • If that didn't help, Call the CEO. Wait for CEO or Expert instructions

Chamber Boards LV Errors Summary
Show Instructions Hide Instructions These occasionally occur as spurious errors in DCS. Wait to see if it goes away on its own.
To confirm if it is a 'real' error, check to see if the TMB counters incrementing:
(To find the counters, go to Page 1 and click the 'PCrate Monitor Plus/Minus' heading to open the Cyan Page, then select 'TMB Counter View')

  • Yes:
    • DCS might be wrong. Log the error and contact the CEO
  • No:
    • You may have lost communication with the crate, and need to power-cycle the crate controllers.
      • DO NOT POWER CYCLE THE ENTIRE PCRATE.
    • If you don't know how to do this, don't. Call the CEO
    • If that didn't help, Call the CEO. Wait for CEO or Expert instructions

Chamber Boards Temperature Errors Summary
Show Instructions Hide Instructions Wait a few minutes to see if the error goes away on its own
What is the nature of the error?

  • Unreasonable: If the temperature is, ie, -50 or 290, this is probably a bug and the error can be safely ignored. Call the CEO to be sure.
  • No Reading: You may have lost communication with a crate.
    • Power cycle the crate controller
    • DO NOT POWER CYCLE THE ENTIRE PCRATE.
    • If you don't know how to do this, don't. Call the CEO
  • High Temperature: Check the COOLING status from the top-panel of DCS. Call the CEO.

Peripheral Crate Reading Problem
Show Instructions Hide Instructions

  • Wait a few minutes to see if the error goes away on its own
  • From Page 1, click the 'PCrate Monitor Plus/Minus' heading.
    • Click 'Check Crate Controllers' and wait a few minutes to see if that fixes the problem.
  • No Reading: You may have lost communication with a crate.
    • Power cycle the crate controller
    • DO NOT POWER CYCLE THE ENTIRE PCRATE.
    • If you don't know how to do this, don't. Call the CEO

CSC_GAS
Show Instructions Hide Instructions A Gas alarm is important but NOT time-critical. the CSC detector can operate without damage for some hours without gas flow.
HOWEVER, it is important that you contact the appropriate people right away.

  • Do the following, in order:
    • Contact the CEO (161972)
    • Contact the CMS shift leader
    • Call the Gas expert
  • NOTE that the chambers can operate for some hours without gas flow. However, after 24 hours data quality will be compromised. This is the point at which the DCS alarm is displayed.

CSC_COOLING
Show Instructions Hide Instructions

Other DCS Problems
Show Instructions Hide Instructions

  • The DCS Top-level window has disappeared from the screen
Show Instructions Hide Instructions
  1. Click on the tab in the taskbar labeled Vision_1: fwDeviceEditorNavigator at the bottom of the window (you may have to manually scroll down to see it)
  2. Select the FSM tab in the window
  3. Right-click on CMS_CSC, and in the pop-up menu select "View"
  4. Once you have the top-level window back, then right-click on the lock on the top-level tab and "Take"
  • The STATE fields have gone grey
Show Instructions Hide Instructions
You may have (inadvertently) restarted PVSS. The little lock next to the field CMS_CSC on the top is open.
  1. Single click on the open lock. A dialog pops up saying "CMS_CSC is Excluded".
  2. Click on 'Take'. The state fields should be colored.
back to top of page

Operating Instructions for the New DCS Interface

SKIP TO DCS Error Handling SECTION

  • As of 22 July, a new user interface (UI) has been implemented for the top-level DCS on a trial basis.
    • The detail-level windows are still the same as in the old interface.
  • The 'old' UI should still be running and present at all times.
  • Only one (the old or new interface) can control the devices at one time.
  • Please exercise the new interface. If you see any bugs, please report them as described below.

  • To start the new DCS UI:
    1. Click on the green 'DCS' icon in the lower left corner of the lower left monitor
    2. Wait for the new window to open, and the 'value monitor' (in the lower right) to finish updating
    3. Keep the display in the upper window, over the old DCS display
    4. NOTE: Starting the interface does not guarantee the new UI has control over the system!
  • To kill the new DCS UI:
    1. Close all open DCS windows within the new UI (not in the VNC window!)
    2. Click 'close' ('x') in the upper right of the new UI window (called 'CMS Endcap Muon System DCS')
    3. This should not disturb the old DCS top panel, which should remain on the monitor at all times
  • To toggle control between the interfaces (from the new UI):
    1. Give control to the new from the old:
      • Double-click on 'CMS_CSC' button in the lower left of the corner of the new DCS UI view
    2. Give control to the old from the new:
      • Double-click on 'CMS_CSC' button at the top of the new DCS UI view
  • If you see a bug:
    1. Take a screen shot (Prt Scrn button on keyboard)
    2. Record details of the bug along with the screenshot filename in the ELOG (attach screenshot to the entry if possible)
    3. Stop and restart the new DCS UI to clear the bug

Navigating through DCS:

  • Moving the mouse pointer over an item displays details for the item
  • Clicking on an item opens the DCS panel for that item (same panels used in the old interface)
    • If in 'General State' mode, this opens the panel for the whole chamber (HV, LV, Temp)
    • If in 'HV,' 'LV,' or 'Temp' mode, this opens the relevant sub-panel for that chamber

The new layout:

End view of detector stations (discs), each chamber (wedge) and peripheral crate (rectangles around stations) drawn
Major subsystems (cooling, gas, etc.) HV Primary Supplies LV Maraton power supplies Value monitor with chamber map

DCS View Modes (change using Change Mode button at top)

  • General State displays all information; This is the default view
  • High Voltage displays only HV information
  • Low Voltage displays only LV information
  • Temperature displays only temperature information

Error Handling in DCS:

  • If you see any error in red, click on it until you reach the detailed DCS display panel about the error.
  • Identify the error type in the list below and follow the relevant instructions.
  • If there is no documentation for the error, call the CEO.

High Voltage Trip
Show Instructions Hide Instructions

  • HV Channel Trip (first or second time)
    • Select the chamber in error
    • If the chamber is NOT in ME1/1:
      • Click "force on"
      • The state should be "Ramping UP"
    • If the chamber IS in ME1/1:
      • From the HV panel set the STATE to "OFF"
      • Once it has turned off, set the STATE back to "ON"
  • HV Channel Trip (~third time)
    • Mask out the channel by following these steps:
    • Select the chamber in error
    • If the chamber is NOT in ME1/1:
      • Select the tripped channel
      • Uncheck "isEnabled"
      • "force on"
    • If the chamber is NOT in ME1/1:
      • From the chamber's HV panel, click on the check-mark next to the STATE button
      • Select 'Disable'
    • Notify the CEO that the channel has been disabled.
    • Log the disabled channel in the ELOG and on the whiteboard.
  • Chamber HV Trip (no single tripped channel)
    • Check the boxes:
      • "Module Status" (bottom-right of the panel)
      • "MS_STATUS" (status of the master board. Bottom of the panel)
      • Click "Force on"
    • If the chamber HV must be masked (after repeated trips)
      • From the chamber's HV panel, click on the check-mark next to the STATE button
      • Select 'Disable'
      • Notify the CEO that the HV for this chamber has been disabled.
      • Log the disabled chamber in the ELOG and on the whiteboard.

LV Error (Maraton)
Show Instructions Hide Instructions A maraton trip is a serious problem. Each Maraton supplies LV Power for up to 3 Trigger Sectors (TS).

  1. Check how many Maratons have tripped:
    • If more than 2, call the CEO (161972) and inform the Shift Leader.
    • If there are two in the same UXC Rack, it's possible that the AC breaker in S4 has tripped. Call the CEO (161972) and inform the Shift Leader.
    • If a single maraton has tripped, either the OPFC in S4F04 or the maraton itself has tripped. If DCS can communicate with the maraton, the maraton itself has tripped. If not, the OPFC is probably tripped. Call the CEO (161972) and inform the Shift Leader.
  2. Action -- after reporting the trip take this action
    1. From DCS, turn OFF the 3 PCrates in the 3 trigger sectors fed by this maraton (see table below)
    2. From DCS, turn OFF the maraton.
      • If the PFC itself tripped, DCS cannot communicate directly with the maraton. Turn it off with DCS anyway.
    3. Leave the maraton and PCrates off, and wait for CEO or expert instructions.

Maraton to Peripheral Crate / Junction Box Mapping
Some notes:

  • The essential item in DCS for the Maraton link is the Maraton CANBUS ID. This ID is linked absolutely to the physical connections labeled below, regardless of whatever else may be marked on the buttons in DCS.
  • BE CAREFUL OF POSSIBLE REVERSED ORDERING OF "ID" numbers in the DCS panel

    YE+1      
ID DCS Name Rack Name PC = pcrate JB = junction box  
1 P1_CR1_LV_MRTN/id1 X4J31c PC+1/2 PC+1/12 PC+1/1
2 P1_CR2_LV_MRTN/id2 X4J31e PC+1/3 JB+1/3 JB+1/2
3 P1_CR4_LV_MRTN/id3 X4A31e PC+1/5 JB+1/7 JB+1/6
4 P1_CR3_LV_MRTN/id4 X4A31c PC+1/4 JB+1/5 JB+1/4
5 P1_CR6_LV_MRTN/id5 X2A33j PC+1/7 PC+1/9 PC+1/8
6 P1_CR5_LV_MRTN/id6 X2A33h PC+1/6 JB+1/9 JB+1/8
7 P1_CR7_LV_MRTN/id7 X2J31c PC+1/10 JB+1/11 JB+1/10
8 P1_CR8_LV_MRTN/id8 X2J31e PC+1/11 JB+1/1 JB+1/12
    YE+2      
ID DCS Name Rack Name PC = pcrate JB = junction box  
9 P2_CR1_LV_MRTN/id9 X4J41a PC+3/1 PC+2/6 PC+3/6
10 P2_CR2_LV_MRTN/id10 X4J41b PC+2/1 JB+3/1 JB+2/1
11 P2_CR4_LV_MRTN/id11 X4A41a PC+3/2 JB+3/3 JB+2/3
12 P2_CR3_LV_MRTN/id12 X4A41b PC+2/2 JB+3/2 JB+2/2
13 P2_CR6_LV_MRTN/id13 X2A41a PC+3/3 PC+2/4 PC+3/4
14 P2_CR5_LV_MRTN/id14 X2A41b PC+2/3 JB+3/4 JB+2/4
15 P2_CR7_LV_MRTN/id15 X2J41a PC+3/5 JB+3/5 JB+2/5
16 P2_CR8_LV_MRTN/id16 X2J41b PC+2/5 JB+3/6 JB+2/6
    YE+3      
ID DCS Name Rack Name PC = pcrate JB = junction box  
17 P3_CR1_LV_MRTN/id17 X4A51a PC+4/2 JB+4/2  
17     PC+4/3    
17     PC+4/4    
18 P3_CR2_LV_MRTN/id18 X2J52b PC+4/1 JB+4/4  
18     PC+4/6    
18     PC+4/5    
    YE-1      
ID DCS Name Rack Name PC = pcrate JB = junction box  
21 M1_CR-1_LV_MRTN/id21 X4V31a PC-1/2 PC-1/12 PC-1/1
22 M1_CR-2_LV_MRTN/id22 X4V31b PC-1/3 JB-1/3 JB-1/2
23 M1_CR-4_LV_MRTN/id23 X4S31a PC-1/5 JB-1/7 JB-1/6
24 M1_CR-3_LV_MRTN/id24 X4S31b PC-1/4 JB-1/5 JB-1/4
25 M1_CR-6_LV_MRTN/id25 X2S33a PC-1/7 PC-1/9 PC-1/8
26 M1_CR-5_LV_MRTN/id26 X2S33b PC-1/6 JB-1/9 JB-1/8
27 M1_CR-7_LV_MRTN/id27 X2V31a PC-1/10 JB-1/11 JB-1/10
28 M1_CR-8_LV_MRTN/id28 X2V31b PC-1/11 JB-1/1 JB-1/12
    YE-2      
ID DCS Name Rack Name PC = pcrate JB = junction box  
29 M2_CR1_LV_MRTN/id29 X4V41a PC-3/1 PC-2/6 PC-3/6
30 M2_CR2_LV_MRTN/id30 X4V41b PC-2/1 JB-3/1 JB-2/1
31 M2_CR4_LV_MRTN/id31 X4S41a PC-3/2 JB-3/3 JB-2/3
32 M2_CR3_LV_MRTN/id32 X4S41b PC-2/2 JB-3/2 JB-2/2
33 M2_CR6_LV_MRTN/id33 X2S41a PC-3/3 PC-2/4 PC-3/4
34 M2_CR5_LV_MRTN/id34 X2S41b PC-2/3 JB-3/4 JB-2/4
35 M2_CR7_LV_MRTN/id35 X2V41a PC-3/5 JB-3/5 JB-2/5
36 M2_CR8_LV_MRTN/id36 X2V41b PC-2/5 JB-3/6 JB-2/6
    YE-3      
ID DCS Name Rack Name PC = pcrate JB = junction box  
37 M3_CR1_LV_MRTN/id37 X4S51a PC-4/2 JB-4/2  
37     PC-4/3    
37     PC-4/4    
38 M3_CR2_LV_MRTN/id38 X2V52b PC-4/1 JB-4/4  
38     PC-4/6    
38     PC-4/5    

LV Error (CRB)
Show Instructions Hide Instructions These occasionally occur as spurious errors in DCS. Wait to see if it goes away on its own.
To confirm if it is a 'real' error, check to see if the TMB counters incrementing:
(To find the counters, go to Page 1 and click the 'PCrate Monitor Plus/Minus' heading to open the Cyan Page, then select 'TMB Counter View')

  • Yes:
    • DCS might be wrong. Log the error and contact the CEO
  • No:
    • You may have lost communication with the crate, and need to power-cycle the crate controllers.
      • DO NOT POWER CYCLE THE ENTIRE PCRATE.
    • If you don't know how to do this, don't. Call the CEO
    • If that didn't help, Call the CEO. Wait for CEO or Expert instructions

LV Error (Chamber)
Show Instructions Hide Instructions These occasionally occur as spurious errors in DCS. Wait to see if it goes away on its own.
To confirm if it is a 'real' error, check to see if the TMB counters incrementing:
(To find the counters, go to Page 1 and click the 'PCrate Monitor Plus/Minus' heading to open the Cyan Page, then select 'TMB Counter View')

  • Yes:
    • DCS might be wrong. Log the error and contact the CEO
  • No:
    • You may have lost communication with the crate, and need to power-cycle the crate controllers.
      • DO NOT POWER CYCLE THE ENTIRE PCRATE.
    • If you don't know how to do this, don't. Call the CEO
    • If that didn't help, Call the CEO. Wait for CEO or Expert instructions

Temperature Error
Show Instructions Hide Instructions Wait a few minutes to see if the error goes away on its own
What is the nature of the error?

  • Unreasonable: If the temperature is, ie, -50 or 290, this is probably a bug and the error can be safely ignored. Call the CEO to be sure.
  • No Reading: You may have lost communication with a crate.
    • Power cycle the crate controller
    • DO NOT POWER CYCLE THE ENTIRE PCRATE.
    • If you don't know how to do this, don't. Call the CEO
  • High Temperature: Check the COOLING status from the top-panel of DCS. Call the CEO.

Peripheral Crate Reading Problem
Show Instructions Hide Instructions

  • Wait a few minutes to see if the error goes away on its own
  • From Page 1, click the 'PCrate Monitor Plus/Minus' heading.
    • Click 'Check Crate Controllers' and wait a few minutes to see if that fixes the problem.
  • No Reading: You may have lost communication with a crate.
    • Power cycle the crate controller
    • DO NOT POWER CYCLE THE ENTIRE PCRATE.
    • If you don't know how to do this, don't. Call the CEO

CSC_GAS
Show Instructions Hide Instructions A Gas alarm is important but NOT time-critical. the CSC detector can operate without damage for some hours without gas flow.
HOWEVER, it is important that you contact the appropriate people right away.

  • Do the following, in order:
    • Contact the CEO (161972)
    • Contact the CMS shift leader
    • Call the Gas expert
  • NOTE that the chambers can operate for some hours without gas flow. However, after 24 hours data quality will be compromised. This is the point at which the DCS alarm is displayed.

CSC_COOLING
Show Instructions Hide Instructions

Other DCS Problems
Show Instructions Hide Instructions

  • The DCS Top-level window has disappeared from the screen
Show Instructions Hide Instructions
  1. Click on the tab in the taskbar labeled Vision_1: fwDeviceEditorNavigator at the bottom of the window (you may have to manually scroll down to see it)
  2. Select the FSM tab in the window
  3. Right-click on CMS_CSC, and in the pop-up menu select "View"
  4. Once you have the top-level window back, then right-click on the lock on the top-level tab and "Take"
  • The STATE fields have gone grey
Show Instructions Hide Instructions
You may have (inadvertently) restarted PVSS. The little lock next to the field CMS_CSC on the top is open.
  1. Single click on the open lock. A dialog pops up saying "CMS_CSC is Excluded".
  2. Click on 'Take'. The state fields should be colored.
back to top of page
Edit | Attach | Watch | Print version | History: r26 < r25 < r24 < r23 < r22 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r26 - 2020-08-18 - TWikiAdminUser
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox/SandboxArchive All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback