ICD ARINC 818 ADVB Interface Control Document Template f system interoperability
Great River Technology 4910 Alameda Blvd NE Albuquerque NM 87113 www.greatrivertech.com Contact Infmation Telephone 1 (866) 478-4491 Company Fax (505) 883-1375 Email grt@greatrivertech.com Web Address www.greatrivertech.com
REVISION HISTORY: DATE REVISION SECTIONS DESCRIPTION APPROVAL 2/26/2008 REV - INITIAL RELEASE INITIAL RELEASE T. Keller Disclaimer: The content of this document is to be used f infmational purposes only and in conjunction with industry standard documents. Great River Technology makes every efft ensure that the content of this document is accurate and up to date. Great River Technology assumes no legal responsibility f the accuracy of this document and makes no warranty, express implied, related to the use of this guide in the design development of electronic equipment systems. 2
v Purpose of this Template v This template is intended to streamline the efft in developing an Interface Control Document (ICD) f ARINC 818 links. With care, designers can use this template as a starting point to achieve a concise and complete ICD that ensures interoperability between all equipment built to that ICD. v The template includes sections f imptant parameters that should be captured by the ICD. An efft was made to include all pertinent parameters required f compatibility, in me common ARINC 818 systems. However, f me complex systems, such as designs that use dual links, multiple interlaced containers on a single link, there may be parameters not discussed. v This template is intended f engineers sufficiently familiar with the ARINC 818 protocol who need to define a particular ARINC 818 implementation. F engineers unfamiliar with ARINC 818, it is best to review the ARINC 818 specification, the ARINC 818 Implementer s Guide, and www.fcav.info and www.arinc818.com. v Reference Documents v The following ARINC documents should be reviewed in the ICD development efft: ARINC Specification 818: Avionics Digital Video Bus ARINC Specification 801: Fiber Optic Connects ARINC Specification 802: Fiber Optic Cable ARINC Specification 803: Fiber Optic System Design Guidelines ARINC Specification 804: Fiber Optic Active Device Specification v The following specifications are useful f reference: Fibre Channel Audio Video (FC-AV) (ANSI INCITS 356-2002, 25 Nov 2002) Fibre Channel Framing and Signaling Interface (FC-FS) (ANSI / INCITS 373-2003) Fibre Channel Physical Interfaces (FC-PI) (INCITS 352-2002) v Notes f using the Template v In some instances the template includes blanks where parameter values are to be filled in. In these cases, example values are given; however, this ICD does not enumerate all possible values to be filled. Example values are italicized. (Example: 850nm multimode fiber) v In some instances, that template includes text that describes the intent of the section. This text is enclosed in brackets and is italicized. {This section should contain } v Where possible, referenced to the relevant ARINC 818 section are given in brackets. [See ARINC 818 Section 4.2] v The Template does not include a cover page, table of contents, revision blocks, other boilerplate pages. These must be added such that they meet the documentation requirements of the particular ganization developing the ICD. 3
1 Physical Medium and Speed Physical Medium [See ARINC 818 Section 4.2] Example: 850nm multimode fiber Connect Type: Example: LC type plug Link Speed: [See ARINC 818 Section 4.1] Example: 2.125 Gbps 2 Video Parameters 2.1 Video Fmat {This section should contain the basic attributes of the video being transmitted} The ADVB shall have the following video fmat: Video Resolution [see ARINC 818, Figure 3] o Active Image Size: pixels x lines o Visible Image Area: pixels x lines o Image Offset: pixels x lines (from upper left) Scan: [see ARINC 818, section 3.2.2.5.1.3] Example: Progressive (left to right, starting at top) Frame rate: Hz [see ARINC 818, Table 3] Pixel fmat: [see ARINC 818, Table 5] Example: RGB 8:8:8 2.2 Synchronization and Segmentation Class {This section identifies the synchronization and segmentation class of transmitters and receivers. Transmitters may be restricted in the way that Object 0 data and video payload is packetized (segmentation). Transmitters may also be restricted in the timing of packet deliver, thereby reducing the complexity of the receiver (Synchronization)} Asynchronous Frame Sync. Line Sync. Pixel Sync. A1 A2 A3 B1 B2 B3 C1 C2 D1 D2 D3 [See ARINC 818, Attachment C] Transmitter: Receiver: 4
2.2.1 Segmentation ARINC 818 ICD Template {This section states explicitly the rules f segmentation} All transmitted ADVB frames shall confm to the following segmentation rules f Object 0 and Object 2 & 3 video payload: The ADVB shall assign containers per video image. Object 0 shall be segmented into the first transmitted ADVB frame in each Video frame Object 2/3 frames shall have: o ADVB Frames total per container o Video lines per FC Frame 2.2.2 FC Frame and Video Timing {This section should specify all timing parameters associated with the ADVB packets as well as the timing of delivery of those ADVB packets)} [These timing requirements are explicit in, derived from ARINC 818, Attachment B] All transmitted ADVB frames shall confm to the following timing: 32 BIT CHARACTER TIME (ns) BYTES PER VIDEO LINE NUMBER OF LINES PER ADVB FRAME ADVB FRAME PAYLOAD SIZE (BYTES) NUMBER OF FC OBJ2 FRAMES The line synchronous timing shall be achieve using the following parameters: INACTIVE LINES (VERT. BLANKING) Pre FC 0 Post - FC 0 HORZ. LINE TIME (us) HORIZONTAL LINE RATE (khz) ACTUAL FRAME RATE(Hz) (with sync'ed lines) 5
TIMES tvft The above parameters lead to the following times: [See ARINC 818, Attachment B] Timing Parameters TIME 32-bit CHAR COUNT HORZ. LINES FC Frame 0 frame time (us) FC Frame 1 frame time (us) Nominal Video Frame Time SOFi TO SOFi (ms) tlt Nominal Video Line time (us) t0 SOFi TO SOFn(first) (us) t1 Line Time Tolerance (-us) t2 Line Time Tolerance (+us) SOFn(first) TO SOFnlast (us) SOFnlast TO SOFi (us) t3 Intraline IDLEs (us) t4 Interline IDLEs (us) t5 EOFt TO SOFi (us) t6 Video Frame Tolerance (-us) t7 Video Frame Tolerance (+us) 6
t=0 t=n*t LW t=2n*t LW t LT = Nominal Video Line Time (Example with two FC frames per video line) FC Frame 0 FC Frame 1 t3 t LT t0 t0 t0 Represents minimum time resolution = 40 bit times = Long Wd Time (T LW ) FC Frame 2...... t VFT = Nominal Video Frame Time t1 t2 t4 Video Line Time Tolerances FC Frame 3 FC Frame 5 FC Frame 6 t5 FC Frame 4 FC Frame 7 FC Frame 8 FC Frame N-1... t5 FC Frame N t4 t5......... t6 t7 FC Frame 0 Video Frame Time Tolerance = SOFi = EOFn = SOFn = EOFt Start of next video frame t LT = Nominal Line Time t VFT = Nominal Video Frame Time t0 = n0*t LW time from SOFi to first SOFn (+/- Tol) t1 = n1*t LW Video Line Tolerance (Faster than nominal) t2 = n2*t LW Video Line Tolerance (Slower than nominal) t3 = n3*t LW (intraline idle OS) (+/- Tol) t4 = n4*t LW (interline Idle OS - EOFn to SOFn) (+/- Tol) t5 = n5*t LW (interframe Idle OS) (+/- Tol) t6 = n6*t LW Video Frame Tolerance (Faster than nominal) t7 = n7*t LW Video Frame Tolerance (Slower than nominal) nx = number of dered sets Video Line Time = t LT with tolerance of (-t1 +t2) Video Frame Time = t VFT with tolerance of (-t6 +t7) Note: Timing parameters may be fixed values variable, depending on the class and implementation. Definition of Timing Parameters from ARINC 818 Attachment B 7
3 Ordered Sets ARINC 818 ICD Template [See ARINC 818, section 3.4 and Table 15] SOF Class: (1 3) Idle Characters: (nmal low emissions) 4 Headers & Ancillary Data {In this section, specific values f ADVB frame header and Object 0 data are defined} 4.1 ADVB Frame Header {Values in the ADVB Frame header can be user defined, (indicated by xxxx), ARINC 818 required constants (indicated a binary value, like 0100), unused (can be left 0000)} [see ARINC 818, Section 3.3] Wd Identifier Byte 0 Byte 1 Byte 2 Byte 3 1 Frame Header 2 Frame Header 3 Frame Header 4 Frame Header 5 Frame Header 6 Frame Header 0100 0100 (R_CTL) (CS_CTL) 0110 0001 60h=FC-AV 61h=ADVB (SEQ_ID) 1111 1111 (OX_ID) (Dest._ID) (Source_ID) 0011 x000 (bit 19=END_SEQ) (F_CTL) (DF_CTL) 1111 1111 (OX_ID) (Dest._ID) (Source_ID) 0000 000x (F_CTL) (SEQ_CNT) 1111 1111 (RX_ID) (Dest._ID) (Source_ID) 0000 x0xx (F_CTL) (SEQ_CNT) 1111 1111 (RX_ID) 8
4.2 Container Header ARINC 818 ICD Template {Container Header Values indicated by xxxx must be established f the ARINC 818 implementation} [See ARINC 818, Section 3.2] Wd Identifier Byte 0 (MSB) Byte 1 Byte 2 Byte 3 (LSB) 0 Container Count 1 Clip ID 2 Container Time Stamp 3 Container Time Stamp 4 Transmission Type 5 Container Type 0000 0100 6 Object 0 Class 0101 xxxx 1101 0000 7 Object 0 Size 8 Object 0 Offset 0101 1000 9 Object 0 Object Type Defined 10 Object 1 Class 0100 0000 1101 0000 11 Object 1 Size 0001 0000 12 Object 1 Offset 13 Object 1 Object Type Defined 14 Object 2 Class 0001 0000 1101 0000 15 Object 2 Size 16 Object 2 Offset 17 Object 2 Object Type Defined 18 Object 3 Class 0001 0000 1101 0000 19 Object 3 Size 20 Object 3 Offset 21 Object 3 Object Type Defined 9
4.3 Ancillary Data ARINC 818 ICD Template { Assumes standard sized ancillary data of 16 bytes. If the size of the Ancillary data is extended, as set by the Object 0 size in Wd 7 of the container header, then additional bytes will need to be defined. Ancillary data can also include items such as palette data curser control data} [See ARINC 818, Section 3.2.2.5] Wd 0 Byte 0 Byte 1 Byte 2 Byte 3 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Wd 1 Byte 0 Byte 1 Byte 2 Byte 3 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Wd 2 Byte 0 Byte 1 Byte 2 Byte 3 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Wd 3 Byte 0 Byte 1 Byte 2 Byte 3 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Wd 0 Wd 1 Wd 2 Wd 3 Ancillary Data Summary (hex values) Byte 0 Byte 1 Byte 2 Byte 3 10
5 Special Cases: Dual Link Time-Multiplexed Video {ARINC 818 includes the flexibility to send multiple video streams on a single link [see Section 3.5], and to use a dual link to send a single, high bandwidth video stream over two links [see Section 3.6]. This template does not cover these special cases. } 11