19.07.2012 Views

Preliminary Ttcbi

Preliminary Ttcbi

Preliminary Ttcbi

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

3.1 BST Message CONTENTS<br />

LHC Project Document No.<br />

LHC-BI-ES-XXXX.XX rev 0.0 Draft<br />

Page 7 of 18<br />

The size of the BST message is limited by several physical parameters such as the serial<br />

output bandwidth and the duration of message assembly process. A message of 32 Long format<br />

Commands/Data can cover all beam instrumentation needs. The 8-bit sub-address allows 256<br />

identified bytes of data to be sent. Table 1 defines the contents of each byte and its update<br />

frequency. This table is subject to change according to LHC operation or end users requirements.<br />

Bytes Description Data format Updated every<br />

0 Machine Mode Enumerated type: No beam, filling, ramping, physic,… On change<br />

1 Beam Type Enumerated type: Ion, Proton,… On change<br />

2 Beam Energy<br />

3 Beam Energy<br />

2 bytes in GEV On change<br />

4 Mean Current per Bunch<br />

5 Mean Current per Bunch<br />

2 Bytes * 10E11 ppp<br />

6 Number of injected Bunches<br />

7 Number of injected Bunches<br />

2 Bytes integer On change<br />

8 Next Batch to Inject 0 for no beam or 1 .. 12 On change<br />

9 GPS Absolute Time<br />

10 GPS Absolute Time<br />

11 GPS Absolute Time<br />

12 GPS Absolute Time<br />

13 GPS Absolute Time<br />

14 GPS Absolute Time<br />

15 GPS Absolute Time<br />

16 GPS Absolute Time<br />

64 bits UTC format On change<br />

17 Last Machine Timing Event<br />

18 Last Machine Timing Event<br />

2 Bytes : Machine Timing Event number On reception<br />

19 BI Predefined received Events<br />

20 BI Predefined received Events<br />

2 bytes : corresponding to 16 predefined events table On reception<br />

21 Main Trigger Byte 8 X 1 bit dedicated Trigger: warning injection, start post-mortem, … 1 Turn<br />

22 BI devices dedicated Bytes 10 Bytes device dedicated commands or triggers : 1 Turn<br />

23 BI devices dedicated Bytes<br />

24 BI devices dedicated Bytes<br />

25 BI devices dedicated Bytes<br />

26 BI devices dedicated Bytes<br />

27 BI devices dedicated Bytes<br />

28 BI devices dedicated Bytes<br />

29 BI devices dedicated Bytes<br />

30 BI devices dedicated Bytes<br />

31 BI devices dedicated Bytes<br />

Closed orbit capture, Single Turn trajectory measurement,….<br />

Bytes 0 to 20 (the data in blue) come from the new slow timing interface (TGR module) [7] where a<br />

time granularity of 1ms is adequate. Bytes 21 to 31(the data in green), where a time granularity of 1<br />

turn is required, come either from an external trigger (e.g. an injection warning) or a demand from<br />

an operator application process (e.g. a closed orbit acquisition). There is also a possibility of<br />

inserting a time stamp to allow the clear identification of measurements.<br />

4. TTCbi OVERVIEW<br />

The TTCbi is another key component of the BST system, and is the subject of this<br />

specification. It has the task of interfacing the TTC system with the beam instrumentation, and is<br />

found at the end of the TTC distribution network. A PMC format has been chosen for the TTCbi,<br />

allowing it to be plugged into different types of motherboard. Most beam instrumentation<br />

applications will be based on a standard VME bus, and the TTCbi will therefore reside on a<br />

dedicated PMC connector on the CPU itself, giving a direct connection of hardware signals to and<br />

from the VME P2 user I/O connector. The TTCbi is built around the TTC receiver ASIC (TTCrx) [5]<br />

and the basic features of the card depend on this chip. In addition to delivering the timing signals,

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!