![background image](http://html1.mh-extra.com/html/aim/afdx-arinc-664/afdx-arinc-664_reference-manual_2871730084.webp)
72
Reference Manual AFDX / ARINC 664 Application Interface Library
Section 4 – Function Reference: Transmitter Functions
The following Table shows the necessary size of one Queue Entry dependent on the Payload Buffer
and Payload Generation Modes.
Payload Buffer Mode
Payload Generation Mode
Size of Queue Entry
FDX_TX_FRAME_PBM_STD FDX_TX_FRAME_PGM_USER
sizeof (TY_FDX_TX_FRAME_HEADER) +
uw_FrameSize
FDX_TX_FRAME_PBM_STD FDX_TX_FRAME_PGM_IP_PART
FDX_TX_FRAME_PGM_IP_PART_TT
sizeof (TY_FDX_TX_FRAME_HEADER) +
MAC-Header (14 Bytes) +
IP-Header (20 Bytes) +
UDP-Header (8 Bytes)
FDX_TX_FRAME_PBM_STD FDX_TX_FRAME_PGM_IP_FULL
FDX_TX_FRAME_PGM_IP_FULL_TT
sizeof (TY_FDX_TX_FRAME_HEADER) +
MAC-Header (14 Bytes)
FDX_TX_FRAME_PBM_FULL FDX_TX_FRAME_PGM_USER sizeof
(TY_FDX_TX_FRAME_HEADER)
Note: The full MAC Frame must be provided
in separate Buffer.
FDX_TX_FRAME_PBM_MAC FDX_TX_FRAME_PGM_USER
sizeof (TY_FDX_TX_FRAME_HEADER) +
MAC-Header (14 Bytes) +
IP-Version (1Byte) +
IP-Type of Service (1Byte)
Note: Remaining Data must be provided in
separate Buffer.
FDX_TX_FRAME_PBM_UDP FDX_TX_FRAME_PGM_USER
sizeof (TY_FDX_TX_FRAME_HEADER) +
MAC-Header (14 Bytes) +
IP-Header (20 Bytes) +
UDP Source Port (2Bytes) +
UDP Destination Port (2Bytes) +
UDP Length (2Bytes)
Note: Remaining Data must be provided in
separate Buffer.
Note:
For Timetag-Payload-Generation modes the Timetag Format in Payload is
started at Byte 44 (2 bytes after UDP-Checksum)
BYTE 44...47 – Timetag HI
Bit 5... 0
: Seconds of minute
Bit 11... 6
: Minutes of hour
Bit 16...12
: Hours of day
Bit 25...17
: Days of year
Bit 31...26
: reserved (0)
BYTE 48...51 – Timetag LO
Bit 19... 0
: Microseconds of second
Bit 25...20
: Seconds of minute
Bit 31...26
: Minutes of hour
A
A
i
i
U
U
I
I
n
n
t
t
3
3
2
2
u
u
l
l
_
_
B
B
u
u
f
f
f
f
e
e
r
r
Q
Q
u
u
e
e
u
u
e
e
H
H
a
a
n
n
d
d
l
l
e
e
In Payload Buffer Mode FDX_TX_FRAME_PBM_FULL, FDX_TX_FRAME_PBM_MAC or
FDX_TX_FRAME_PBM_UDP is used for this frame, a valid Buffer Queue Handle must
be set. This Buffer Handle is obtained via the function
FdxCmdTxBufferQueueAlloc
. If
Payload Buffer Mode is not used, it should be initialized with NULL. Dependent on the
Payload Buffer Mode, the allocated Buffer must contain the corresponding data
beginning with MAC payload or UDP payload.
Using Payload Buffer Mode FDX_TX_FRAME_PBM_UDP or
FDX_TX_FRAME_PBM_MAC would allow the user to change data associated with this
frame during run-time by the
FdxCmdTxBufferQueueWrite
and
FdxCmdTxBufferQueueCtrl
functions.
A
A
i
i
U
U
I
I
n
n
t
t
8
8
u
u
c
c
_
_
E
E
x
x
t
t
e
e
r
r
n
n
a
a
l
l
S
S
t
t
r
r
o
o
b
b
e
e
Control assertion of Trigger Strobe if this frame is transmitted. See the
FdxCmdTxTrgLineCtrl
for further information about the Trigger Lines.
Summary of Contents for AFDX / ARINC 664
Page 2: ......