![Aim AFDX / ARINC 664 Скачать руководство пользователя страница 79](http://html1.mh-extra.com/html/aim/afdx-arinc-664/afdx-arinc-664_reference-manual_2871730079.webp)
Reference Manual AFDX / ARINC 664 Application Interface Library
67
Section 4 – Function Reference: Transmitter Functions
void *pv_WriteBuffer
Pointer to the data buffer providing the Entries to write. The size of this buffer
should correspond to
ul_WriteBytes
.
One Entry specifies one Frame + Header Information. This means one complete MAC frame
plus a fixed sized Header. The Header contains information about the manner in which the
frame should be sent on the network.
Layout of one Queue Entry:
Entry Layout
Fixed Header
Fixed Frame Header
Layout dependent on
ul_HeaderType
and
uc_FrameType
parameter
(see following description)
AFDX Fr
ame
AFDX- FRAME data to transmit
(dependent on the Payload Buffer and Payload Generation mode, see description below)
( 802.3 defines: 64 to 1518 bytes)
For Header Type
FDX_TX_FRAME_HEADER_REPLAY
refer to the frame buffer layout
described in function
FdxCmdMonQueueRead
.
Note: The replay mode does not reproduce any recorded physical error conditions, but
is tolerant to protocol errors as well as size violations. A packet will be
discarded by the firmware if any of the following error conditions is detected:
PHY, PRE, TRI, CRC, IFG, SFD. The following error types are tolerated and will
be replayed: IPE, MAE, LNG (up to frame length of 2000 bytes), SHR (from
frame length of 40 bytes), VLS, SNE, TNS.