Difference: AMC13UserManual (25 vs. 26)

Revision 2607 Oct 2015 - EricHazen

Line: 1 to 1
THIS MANUAL IS INCOMPLETE but what is written here should be more accurate and up to date than the old "functional specification". Please e-mail me if you find mistakes/omissions here (Eric H).
Line: 229 to 227
  int getTTCHistoryCount(); // get TTC hsitory count

Monitor Buffer

The AMC13 can store up to 1024 event blocks in SDRAM memory pages (aka buffers) each occupying 512k bytes. The default mode at power-up is that up to 1024 blocks are stored (independent of DAQ outputs), storing stops and the bit STATUS.MONITOR_BUFFER.FULL is set. At any time the number of occupied buffers may be read from STATUS.MONITOR_BUFFER.UNREAD_EVENTS. Note that if any AMC payload is > 32k bytes the event will be segmented and the number of buffers will be greater than the number of events.

One buffer at a time may be read at MONITOR_BUFFER_RAM, which presents a window of up to 512k bytes (0x20000 32-bit words). Advance to the next buffer by writing to ACTION.MONITOR_BUFFER.NEXT_PAGE. Note that one buffer may contain only the first block of a segmented event. Generally a user should call AMC13::readEvent() to obtain the next event including all blocks/buffers as necessary. After reading an event the corresponding buffers are freed and new events may be stored.


Local Trigger Logic (DT)

The following section describes a local trigger implemented for the DT group according

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