Cosmic RUn at ZEro Tesla CRUZET Takes place

Cosmic RUn at ZEro Tesla (CRUZET) • Takes place next week starting Tuesday • To do before… – Time in to global trigger timing (scheduled for tomorrow morning with I. Mikulec) – Find L 1 As for ME+4/1 CFEBs – Find and mask off chambers which cause DDU errors – Make sure response is correct to Run Control commands (configure, start, halt, etc. ) • TTC • FED (DAQ crates) • Peripheral Crates 29 Apr. 2008 G. Rakness (UCLA) 1

ALCT Firmware Database Checks which must be satisfied before any ALCT firmware can be downloaded: In xml file, to control directed access to ALCT… • VCC MAC address • TMB slot number In xml file, to make sure anybody mucking with xml file is doing it in a consistent manner: • Crate label (e. g. “VMEp 4_6”) • Chamber label (e. g. “ME+4/1/1”) • Chamber firmware type (ME 11, ME 12, ME 13, ME 21, ME 22, ME 31, ME 32, ME 41) • If ME 11, must have correct forward/backward, negative/positive specifications. Read of ALCT hardware to ensure that communication is OK, and that you have not mucked around with the xml file to force it to match: • FPGA ID type from ALCT (differentiates between 288/384 and 672 type of FPGA) For the expert, it is possible to ignore all checks by setting the xml crate name = "test_crate" and the xml chamber name = "test_chamber". This must never be done at point 5. 29 Apr. 2008 G. Rakness (UCLA) 2

Firmware Downloading Interface Running on test crate/chamber at 904: ALCT database check does not pass… 29 Apr. 2008 G. Rakness (UCLA) 3

Possible approach to upgrade triggering firmware • Firmware upgrades desired: – TMB – ALCT • Next week: make TMB software changes • At point 5, do changes on one crate (VME+2/1) (VME+3/1, as well? ) • Possible order: – – – Take one run (10 k events) with current firmware ALCT upgrade (should be minor upgrade) Take one run (10 k events) Upgrade software TMB upgrade (significant upgrade) Revert back both ALCT and TMB firmware (? ) 29 Apr. 2008 G. Rakness (UCLA) 4