![background image](http://html1.mh-extra.com/html/aim/afdx-arinc-664/afdx-arinc-664_reference-manual_2871730193.webp)
Reference Manual AFDX / ARINC 664 Application Interface Library
181
Section 4 – Function Reference: Receiver Functions
4
4
.
.
4
4
.
.
3
3
.
.
2
2
F
F
d
d
x
x
C
C
m
m
d
d
M
M
o
o
n
n
G
G
e
e
t
t
S
S
t
t
a
a
t
t
u
u
s
s
Prototype:
AiReturn FdxCmdMonGetStatus ( AiUInt32 ul_Handle
TY_FDX_E_MON_STATUS *pe_MonStatus,
TY_FDX_MON_REC_STATUS *px_MonRecStatus);
Driver Command:
FDX_MON_GET_STATUS (0x00008095)
Purpose:
This function returns the status of the selected receiver monitor port.
Input:
None
Output:
TY_FDX_E_MON_STATUS *pe_MonStatus
A pointer to an enumerated variable which indicates the status of the Monitor
typedef enum _mon_status {
FDX_MON_OFF,
FDX_MON_WAIT_FOR_TRIGGER,
FDX_MON_TRIGGERED,
FDX_MON_STOPPED,
FDX_MON_FULL,
FDX_MON_OVERLOAD
} TY_FDX_E_MON_STATUS;
The following states are defined:
Status:
Description
FDX_MON_OFF
Monitor is not running.
Captured data from a previous capturing session in
the buffer is available.
FDX_MON_WAIT_FOR_TRIGGER
Monitor is waiting for Start Trigger. Data capturing is
active
FDX_MON_TRIGGERED
Start Trigger occurred. Data will be captured.
FDX_MON_STOPPED
Capturing is stopped (e.g. if Selective Capturing
mode has been selected and Start Trigger Condition
has become false)
FDX_MON_FULL
The monitor buffer is full and no more data will be
captured
FDX_MON_OVERLOAD
Onboard firware was not able to store data to the
associated buffers. This can happen in continuous
capture mode if traffic is to fast.
Note:
In the mode continuous capturing, the state FDX_MON_FULL never
will be reached.
Figure 4.4.3.2-1 shows the chronological monitor states and the junction between
the states. The state Off can be reached from each other state by intervention of
the user.
Summary of Contents for AFDX / ARINC 664
Page 2: ......