ELOG DESPEC

AIDA GELINA BRIKEN nToF CRIB ISOLDE CIRCE nTOFCapture DESPEC DTAS EDI_PSA 179Ta CARME StellarModelling DCF K40

DESPEC

Fields marked with * are required

Entry time:

Tue Jun 28 10:11:35 2022

Author*:

Subject*:

11:11 Rebooted FEEs and changed aidacommon in /MIDAS/linux-ppc_4xx/startup to point to the new V10 DataAq that Patrick produced
      When using V9 the Merger statistics reported WR items at twice the rate of ADC data items.
      i.e for ever data item we were sending and info code 4 and info code 5 item sending 192 bits of data vs 64 for just the data word
      This was causing significant deadtime when FEEs were running in the range of around 200kHz. These WR items were not reported by the MIDAS Acquisition server but were in the Merger statistics

Patrick has produced V10 which removes these.

When running V10 we can confirm in the Merger statistics that this rate is no longer determined by the ADC data rate and instead controlled via Sync Rollover Target in GSI WhiteRabbit Control.
      WR items for 0xE - attachment 1
      WR items for 0x7 - attachment 2

However we see in the NewMerger terminal the message shown in attachment 3 frequently.
      Also we note that the merger time error counter is also going up.
      Our thoughts for this are we have a rollover issue (Is the merger expecting the rollover of the LSB to be one value when the MSB is updated but MIDAS is happening on another?)
      Are we having dead time issues which is causing time warps?

Does each buffer from the MIDAS Data Acq start with a full WR timestamp?

aidacommon has been changed back to point to V9 to not cause issues when we run the DAQ and forget we changed it to be this way?

Encoding: HTML ELCode plain
Suppress Email notification Resubmit as new entry

Attachment 1:

220628_1117_Rollover0xE.png Original size: 1919x489

Attachment 2:

220628_1119_Merger_Stats_0x7.png Original size: 1914x709

Attachment 3:

NewMerger_Dump.txt

MERGE Data Link (17671): block sequence error: ID 2, expected 462; received 0
MERGE Data Link (17669): block sequence error: ID 0, expected 461; received 0
MERGE Data Link (17672): block sequence error: ID 3, expected 462; received 0
MERGE Data Link (17670): block sequence error: ID 1, expected 462; received 0
MERGE Data Link (17674): block sequence error: ID 5, expected 463; received 0
MERGE Data Link (17676): block sequence error: ID 7, expected 462; received 0
MERGE Data Link (17675): block sequence error: ID 6, expected 461; received 0
MERGE Data Link (17673): block sequence error: ID 4, expected 462; received 0
MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

MERGE Actor (17699): Working with 0 from 8 data sources

Attachment 4:

Drop attachments here...

ELOG V3.1.4-unknown