1. Tests of new host and firmware August/September editions
Y. Favre, G. Mitev, E. Noah, S. Parsa
5th September 2017

2. Motivation for tests 5th September
Previously, with tests run up to August 11th , time limit auto stop was the only configuration that worked, file size limit auto stop did not work, the Host crashed.
>>>>> Motivation for these measurements today:
Check File size limit auto stop works!
Check operation with 2 MCRs works!
What is tested, what is not tested:
Note that we only check the host does not crash, so we don’t go into the detail of the error files, which show that we do have a variety of errors:
Gtrig Trailer not found for GTRIG header tag yyyy
FIFO Full detected at word read…
Gtrig Header tag is not equal to previous header tag +1
Gtrig Tariler tag differs from Header Tag

3. Guidelines for tests 5th September
See Slack postings under “4_team-electronics”:
16th August, 29th August and 5th September!
… we followed those guidelines
29th August
16th August
yfavre [10:36 AM] 
NEW HOST release v To be tested with single & multiple MCRs scripts 'daq-tdm-MCBonly-Applib.cs' & 'daq- tdm-SlaveOnly-Applib.cs' on  
Should fix File Size Limit auto-stop. Please test with Time Limit auto stop first and then File-Limit.  - Use MCR0 3 FEBs 1st, Slot0 = MCB - Then same MCR0 6 FEBs, Slot0 = MCB - Then the  MCR1 only with its 6 FEBs (own Slot0 = MCB) to check it is working - Then the 2 MCRs having 6 FEBs each, MCR0 having the Slot0 = MCB, MCR1 = slave of MCR0
yfavre [11:13 AM] NEW scripts for multiple MCRs launch on : => CAN BE USED on MULTIPLE MCRs while configuring MCB 1st, then all MCR slaves except MCB, finally MCR Slave containing MCB (the latter will start the DAQ) # - daq-tdm-MCBonly-Applib.cs MCB configuration preparing for TDM mode using App.TDM & App.Chain scripting utilities routines 1-TO BE called 1st before any multiple MCR new DAQ start # - daq-tdm-SlaveOnly-Applib.cs Slaves configuration preparing & slaves+MCB DAQ start for TDM mode using App.TDM & App.Chain scripting utilities routines 2-TO BE called after 'daq-tdm-MCBonly-Applib' script on all slaves EXCEPT MCB MCR 3-TO BE called FINALLY ON MCB MCR after 'daq-tdm-SlaveOnly- Applib' script(s) launched on MCR slaves NB : timeout must be set in order to let the time to launch all scripts of since they will wait for DAQ start launched by script of 3-
5th September
yfavre [11:07 AM] NEW HOST release v with scripting run from Socket server

4. Test setup in building 180 at CERN
Block #1
Clock fanout
MCR0
MCR1

5. Tests done on 5th September 2017
See Slack postings under “4_team-electronics”:
16th August, 29th August and 5th September!
… we followed those guidelines
Firmware version used: v (downloaded from
Uploaded to FEBs around 11th August
Host version used: V , downloaded from on 5th September
MCB
MCR0
# FEBs
MCR1
Time limit auto stop
File size limit auto stop
A. Case
MCR0, Slot0 3 OK
B. Case 6
C. Case
MCR1, Slot0
D. Case
Not yet OK
E. Case
Not tried

6. USB3 endpoint errors on host v…574
See slack for issue on USB3 endpoint errors for MCR1 connections (anything that is not MCR0 gives errors… probably) with the latest host version 574. Problem not seen with earlier host version 555.