![background image](http://html1.mh-extra.com/html/aim/afdx-arinc-664/afdx-arinc-664_reference-manual_2871730217.webp)
Reference Manual AFDX / ARINC 664 Application Interface Library
205
Section 4 – Function Reference: Receiver Functions
Value:
Description:
FDX_MON_CC_QUEUE_CREATE
Create queue, associated chronological buffer
FDX_MON_CC_QUEUE_DELETE Delete
Queue
A
A
i
i
U
U
I
I
n
n
t
t
3
3
2
2
u
u
l
l
_
_
Q
Q
u
u
e
e
u
u
e
e
I
I
d
d
Queue Identifier to delete (only needed if the Queue Control Code is set to
FDX_MON_CC_QUEUE_DELETE
.
A
A
i
i
U
U
I
I
n
n
t
t
3
3
2
2
u
u
l
l
_
_
Q
Q
u
u
e
e
u
u
e
e
M
M
e
e
m
m
o
o
r
r
y
y
S
S
i
i
z
z
e
e
Memory which shall be used for the internal global Monitor Buffer for the BIU firmware in
Global RAM. Setting this value to 0 will force to use an internal defined value for this size.
A
A
i
i
U
U
I
I
n
n
t
t
3
3
2
2
u
u
l
l
_
_
T
T
i
i
m
m
e
e
o
o
u
u
t
t
Defines a time out value in milliseconds to force data transmission to the host. This value shall
be in a range form 1 to 0xFFFFFFFF ms. For a value higher than 10ms you would get a high-
performance by setting a value which is dividable by 10.
A value of 0 will result in no Timeout what means received data will be transferred if a quarter
of the internal global Monitor Buffer for the BIU firmware is filled. This is a quarter of
ul_GlobMonSize which is retuned by this function.
A
A
i
i
U
U
I
I
n
n
t
t
3
3
2
2
u
u
l
l
_
_
T
T
r
r
i
i
g
g
g
g
e
e
r
r
T
T
C
C
B
B
I
I
n
n
d
d
e
e
x
x
Number of a Trigger Control Block which shall force data transmission to the host. This
assumes that this Trigger Control Block is correctly set up before referencing here. Valid
numbers for Trigger control blocks are in range from 1 to 253.
A value of 0 indicates no usage of a Trigger Control Block.
T
T
Y
Y
_
_
F
F
U
U
N
N
C
C
_
_
P
P
T
T
R
R
_
_
F
F
D
D
X
X
_
_
C
C
O
O
N
N
T
T
_
_
C
C
A
A
P
P
_
_
C
C
A
A
L
L
L
L
B
B
A
A
C
C
K
K
p
p
f
f
_
_
C
C
a
a
p
p
t
t
u
u
r
r
e
e
C
C
a
a
l
l
l
l
b
b
a
a
c
c
k
k
Callback function provided by the user for signaling completion of reception of data for one
provided buffer. This function will be called after received date is transferred by DMA from the
board to the host memory.
If this function gets called and this buffer was not marked with parameter
FDX_CC_MEM_REUSABLE, the user should provide a new buffer to the board with function
FdxCmdMonContCapProvideMemory
.
The following parameters will be passed to that call back function.
A
A
i
i
U
U
I
I
n
n
t
t
3
3
2
2
u
u
l
l
_
_
H
H
a
a
n
n
d
d
l
l
e
e
Id which was generated as identifier for this Queue. See output parameter of this function
FdxCmddMonQueueContinuousCaptureControl
.
T
T
Y
Y
_
_
F
F
D
D
X
X
_
_
M
M
O
O
N
N
_
_
C
C
O
O
N
N
T
T
C
C
A
A
P
P
_
_
P
P
R
R
O
O
V
V
I
I
D
D
E
E
_
_
M
M
E
E
M
M
x
x
_
_
C
C
o
o
n
n
t
t
C
C
a
a
p
p
B
B
u
u
f
f
f
f
e
e
r
r
I
I
n
n
f
f
o
o
This structure is a copy of the information to the memory buffer which was provided with
the function
FdxCmdMonContCapProvideMemory
. All the information will be passed
through for identification of the buffer. Excepting the parameter ul_BufferSize. This will be
modified with the real size of data copied to this buffer.
A
A
i
i
U
U
i
i
n
n
t
t
3
3
2
2
u
u
l
l
_
_
I
I
n
n
f
f
o
o
This parameter gives additional information about the Data Transfer or the buffer.
Value:
Description:
FDX_MON_CC_QUEUE_INF_NO
No additional information
FDX_MON_CC_QUEUE_INF_TRUNC
Data is truncated and must be followed by a
next buffer.
FDX_MON_CC_QUEUE_INF_CONTINU Data
is a continuation of a preceded buffer
which was truncated.
FDX_MON_CC_QUEUE_INF_CONTRUN
This is a combination of the values
FDX_MON_CC_QUEUE_INF_TRUNC and
FDX_MON_CC_QUEUE_INF_CONTINU
which means this is a fragment of a buffer
preceded with a buffer before and followed by
the next buffer.
Summary of Contents for AFDX / ARINC 664
Page 2: ......