Difference: DCC2DiagnosticTools (1 vs. 2)

Line: 1 to 1

META TOPICPARENT	name="WebHome"

If you see any funny behavior related to a DCC2 during a run, please try to do the following to capture information for debugging:

stop the L1A but do not destroy the configuration
log on to the relevant DAQ machine (see crate list if needed).
DCC2Tool.exe caen:0 10 -x ~ehazen/DCC2/DumpSafe.dcc | strings > dcc2_dump_12345.txt

Added:

>
>

If instructed to save VME data, do this also: DCC2Tool.exe caen:0 10 -x ~ehazen/DCC2/DumpData.dcc
- This creates a binary file data.dat which should be renamed to data_12345.dat (12345 is the run number) and posted with other stuff

Note: DCC2 are in slots 10, 20.

Line: 1 to 1

Added:

>
>

META TOPICPARENT	name="WebHome"

If you see any funny behavior related to a DCC2 during a run, please try to do the following to capture information for debugging:

stop the L1A but do not destroy the configuration
log on to the relevant DAQ machine (see crate list if needed).
DCC2Tool.exe caen:0 10 -x ~ehazen/DCC2/DumpSafe.dcc | strings > dcc2_dump_12345.txt
Post an eLog telling what happened and where to find the dump file.

Note: DCC2 are in slots 10, 20.

Also, if you have time, please save the HyperDAQ expert view.

Thanks!

-- EricHazen - 17 Apr 2009