L2 I/O TransferSlide 2L2 Global InputsL2 Input Fiber, continuedFiber Input ConverterL1 CFT Outputs to FICByte (non-) swappingL2G Header/trailerL2G Header, Trailer MatchedL2G Header, Fixed WordFIC for raw data?Michigan State University01/13/19 1L2 I/O TransferJames T. LinnemannMichigan State UniversityTrigger MeetingFebruary 20, 1998Michigan State University01/13/19 2 L3MPMWo r ker AdminMBT Dec Alpha (Unix)VMECurrent StatusJTL, MSU 12/18/97128TCCVBDInputsMBus SCLOutputs to Global (preprocessors only)L2 AnswerL2 HWFW (Global only)8 VME slots minimumMichigan State University01/13/19 3L2 Global InputsL2 Global Inputs via MBT cardMBT: propose Fiber 160 Mb/s6Requires SLIC have one Fiber output6Question: is SCL Fanout Fiber or CopperAdvantages:6Simpler to set up than copper (balancer, transformer6Less fussy to make work6separation of grounds (if move out of MCH)Michigan State University01/13/19 4L2 Input Fiber, continuedDisadvantages of Fiber:6FIC needs fiber to serve MBT, copper for SLIC6more expensive: $60/channel or so–including cable/fiber? –Cost for both ends or one?6beware of finger prints6patch panel more complex/costly–needed to re-cable if L2 in Fixed Counting House and MCH movesMichigan State University01/13/19 5Fiber Input ConverterInputs:only g-link transfer from L1 CFT/PS6assuming 8/10 or 16/20 encoding for integrityg-link: 6Speed requirements of STT input6recycle engineering of VRB inputs (STT needs raw data)Outputs (Cypress)6160 Fiber (MBT)6160 Copper (SLIC)Michigan State University01/13/19 6L1 CFT Outputs to FICBegin and End Event as g-link Symbols6not as values of dataNot in Gray codePadded to 16 B3B Crossing number (to match L1 accept)Header and Trailer consistent with L2G input specsPS data on fibers separate from CFT fibersBytes produced so no swapping on FIC needed?Michigan State University01/13/19 7Byte (non-) swappingSource’s responsibility; NONE on MBT cardSend bytes to Cypress in order such that when assembled in Alpha, they have specified order (B1, B2, B3, B4)Will provide “final” spec so multi-byte quantities (3B crossing number, 2B eta, etc) come out right in AlphaDo L1CFT 2B quantities have fields crossing Byte boundaries?Michigan State University01/13/19 8L2G Header/trailer12B Header, 4B TrailerTradeoff:64B Header word fixed vs. 64B Trailer = one 4B Header wordOpinions?Michigan State University01/13/19 9L2G Header, Trailer Matched6H1: Length (1B), Format # (2B), Object Length(1B)6H2: Source(1B),Rotation(2B), Bunch(1B)6H3: Status(1B),Version(1B),Switches(1B),Nobj(1B) 6Trailer = H2Michigan State University01/13/19 10L2G Header, Fixed Word6H1: Length (1B), Format # (2B), Object Length(1B)6H2: Nobj(1B),Rotation(2B), Bunch(1B)6H3: Source(1B),Status(1B),Version(1B),Switches(1B)6Trailer:Source(1B),Rotation(2B), Bunch(1B)Michigan State University01/13/19 11FIC for raw data?More complex beast!6Gray Code conversion required6Need to generate/resynch crossing number–bus to all channels6Need to generate header/trailer6need to pad to 16B?6REQUEST g-link start/end symbols–else recognition task needed to count events in buffersConsiderable Escalation over L1 FIC6Defer design until proven to be