|
|
Here is some useful info:
-
The DCT roms are:
-
-
Name
IP Address
Xyplex
Description
-
-
ROM040
Slot-1 Rom
-
ROM015
134.79.61.25 odf-dct
Blt/Ptd
-
ROM018
134.79.61.28 tt2-17
TsfX
-
ROM025
134.79.61.35 tt2-18
TsfY
-
-
Blt/Ptd Configuration:
-
-
Loads DAQ latencies for Blt and Ptd.
Loads Ptd lookup tables.
-
-
Tsf Configuration:
-
-
Loads DAQ latencies, checks whether and
which Tsf luts to load, sets CSRs for DAQ mode, and Playback/Record Enable
and Mode.
-
-
-
Blt/Ptd Feature extraction
-
-
Reads DAQ data from Blt/Ptd modules.
-
Checks for damage and prints message if
damage changes.
-
Prints a message every 10,000 events.
-
-
Tsf Feature extraction
-
-
Reads DAQ data from Tsf modules.
-
Checks framing of Tsf with Dch.
-
Resets framing of Tsf with Dch if detects
out of frame.
-
Prints a message every 10,000 events.
-
-
The control files for the dct reside in:
$ODF_ROOT/constants/dct
There are two links: csr_tsf and csr_bltptd
-
csr_tsf is a soft link to the tsf control
file. It has the following format:
-
1st Word: Lut
version to be used (set to 9904 = 0x26b0)
-
2nd Word: Lut
load control (set to 1)
-
3rd Word: Input
Playback Memory load control (0=don't load, 0!= load)
-
4th Word: DAQ
Latency (0xd for data taking, 0x1e for playback)
-
5th Word: DAQ
Mode (0=Raw Mode, 2= Best 1, 3= Best 2)
-
6th Word: Playback/Record
Enable (0x5=record in/out, 0x7=playback in +enable in/out)
-
7th Word: Playback/Record
Mode (set to 1)
csr_bltptd is a soft link to the blt/ptd
control file. It has the following format:
-
1st Word: Blt
DAQ Latency (0x7c8 for data taking)
-
2nd Word: Ptd
DAQ Latency (0x7e3 for data taking)
-
3rd Word: Playback/Record
Enable
4th Word:
Playback/Record Mode
The following files are loaded into
the rom
-
$ODF_ROOT/constants/dct/tsfX/tsfinput/TsfxLut.bin
-
$ODF_ROOT/constants/dct/tsfY/tsfinput/TsfyLut.bin
-
$ODF_ROOT/constants/dct/blt/blt_input/blt_chanmask
-
$ODF_ROOT/constants/dct/ptd/lut/ptd_lut.bin
The Dct has crate mask 0x800. Take
data following the normal run directions. If you want to run some
non-standard code contact Tom Dignan (x4199).
Some known problems:
Tsf goes out of frame with Dch when
Synch issued.
Using just a Dct trigger can cause
problems starting up if Tsf and Dch are not in frame and in Synch.
This due to the fact that Snyching and reFraming are detected during L1Accepts
and if the systems aren't in frame then they cannot produce trigger objects.
A classic Catch-22.
Ptd/Blt modules seem to be producing
damage on many events.
ODF_ROOT =/nfs/bbr-srv02/dataflow
>
|
|
