Task #15052

Sum device for muon campus toroid (R:TOR703)

Added by John Diamond over 4 years ago. Updated over 3 years ago.

Start date:
Due date:
% Done:


Estimated time:
(Total: 0.00 h)
Spent time:


Request from Kyle:

with the Muon program coming online this year we’d really like to have a R:TOR703 sum device over the $E9 because they will be taking multiple extractions on the $F6.


Task #17764: More summation devices requestedNew


#1 Updated by John Diamond over 4 years ago

  • Assignee changed from John Diamond to Elliott McCrory
  • Estimated time changed from 4.00 h to 16.00 h

This is the request from Kyle that I brought up in our meeting yesterday. They are requesting a new sum for I:TOR852 as well (see #15051). I recommend addressing this one first because S60TOR is not operational yet. I'll add a couple of comments to this ticket to explain how the sum devices work and then feel free to stop by with any questions.

#2 Updated by John Diamond over 4 years ago

Most of the work is handled by the SumMgr class. SumMgr holds a table of sum devices that are created with the create(..) member function. Each device has an arm, trigger and disarm TCLK event. After receiving the arm event the trigger event is activated. For each trigger event the toroid is sampled (via a filter chain) and added to the sum after waiting for the given delay (usually 5ms). The trigger is disarmed when the disarm event arrives and the sum is reset to 0.

The SumMgr relies on a EvtTrigTclkEventGenerator object to deliver event notifications to a VxWorks message queue when the TCLK events occur. There is a task spawned by the SumMgr constructor that pends on the message queue waiting for the event messages to arrive, it then dispatches to one of the _handleXxx methods to arm/trigger/disarm.

Configuring the sum devices is done in the FE's startup script using the vmeintSumCreate(..) function defined in vmeintCommands.cpp.

The best example of an injection sum device is R:SE3853, which sums R:TOR853 on the $E3. There are related devices for the E0, E1, E2 and E9 cycles as well. Take a look at mi14tor's startup script to get an idea of how they're configured.

Finally, the sum's ACNET readout is handled via the SumAccessor class which just delegates to VMEInt::sumRead(..). The Sum ID (specified as the first argument to vmeintSumCreate(..)) is passed through the SSDN channel.

#3 Updated by Elliott McCrory about 4 years ago

These are ACNET Device Index = 0x000e (DEVICE_ID_INJ_SUM)

Examples are in the mi14tor startup scripts. The configuration for R:SE3853 is

vmeintSumCreate 0, 0, 0, 0xe3, 0xe6, 400, 6

These are interpreted as:

1. id        = 0
2. chainID   = 0
3. filterIdx = 0
4. arm_on    = $e3
5. disarm_on = $e6
6. trigger   = 400
7. delay     = 6

#4 Updated by John Diamond about 4 years ago

FYI - I created a filter chain for R:TOR703, id = 0x0.

Also available in: Atom PDF