Page History

...

* Dev board: quick tests of new firmware, new dev board status
* Status on getting the Test Run DAQ up and running in group C
* Hybrid production plans/discussion
* Proposal
* JLab DAQ integration status
* Status of APV25 trigger buffering
* Status of RCE and COB production for HPS
* AOB

...

Minutes 4/26/2013

...

* Status and plans of the firmware on dev board in group C

Ben has updated the firmware on the dev board to be consistent with what was used in the Test Run. The changes are the FIR filter and threshold blocks of the firmware.
Ben mentioned that chip 4/5 doesn't work while 4 worked under the old firmware. He had verified that the output from the APV25 was incorrect and thus didn't want to change the firmware to compensate for this. It was mentioned that chip 4 had a different gain than the others as well.

We should run on the gimp and also on a different good spare hybrid and compare it to "QA" data to make sure that the new firmware is ok.

There is a new board that has the same data path as the RTM which will be completed and tested in the coming week or two (to check that it was loaded similarly to the RTM). This will become the new development board. When ready, we should run tests with spare hybrid. We'd also want to compare it to the RTM; unfortunately we only tested hybrids that are in the detector with the RTM so we'd have to run one of those with this new board. We have to think what the best solution to do that is (adapter on flange is one possibility).

There is a new config file that should be used: devboard_new.xml. Ryan/Ben would change so that a file supplied on the command line can be set as default file.

* APV25 trigger buffering

Not done yet but Ben has a plan on how to do it. The main issue is that on the dev board there is no space to do this for all channels. It was suggested to do this for fewer than 5 buffered trigger and/or single apv25 channel(s) to circumvent that problem and allow for testing this feature.

The trigger rate also needs to be controlled in order to test this. At the moment the trigger rate is set to an average value. It should be possible to send multiple triggers for every trigger it normally sends to test the burst trigger acceptance?

There was also some discussion on how the trigger handshake between the SVT DAQ and JLab DAQ will be handled in relation to the trigger buffering. Ryan was gonna think about this.

* Status on getting the Test Run DAQ up and running in group C

We have booked wednesday as a tentative day to start setting up the DAQ.

* JLab DAQ integration plans/discussion

Postponed.

* Status of RCE and COB production for HPS

Going well and target is production boards ready in fall. Currently COB has been sent out and RCE will be sent shortly. We should expect boards to start being built in May.

* Collaboration meeting talks

Ben and Ryan will give talks. Might be an overview talk by Pelle if needed; depends on schedule.
There will be a 2-3 hours breakout session for DAQ discussion on Tue, Wed or Thu. Sergey has promised to organize time (Pelle will check).

* Proposal

DAQ section in good shape. Pelle will update the section describing the RCE configuration.

More info: there are 8 RCE's per COB and tentative plan is to handle 4 hybrids per RCE (there is a 10Gbit limit per RCE and a ~4Gbit rate from each hybrid). One of the things that was mentioned was the need for data reduction at high rates due to limited memory to read out full frames. Only time we expect to read out full frames are during calibration where manual low rates will be set.

Thus we need only 2 main boards in a single ATCA crate to handle 36 hybrids including the trigger interface module.

* Budget

Updated budget sent to Marco with specified nr of required/spare/prototype for each item.

- Changes: slight update on connector counts.
- Added PS to DAQ budget; incl. 1w of sho work for cabling

* AOB

Pelle will setup a TI discussion meeting with William at JLab during collar. meeting.

Hybrid production plans/discussion
* AOB

...

Minutes 5/3/2013