Reference Manual AFDX / ARINC 664 Application Interface Library
9
Section 3 – Application Interfacing
3.3 Error Reporting
Each function of the FDX Interface Library has defined return values. For a successful function
call the function returns a zero. For an unsuccessful function call the function returns a negative
return value. These return values may be classified in prioritized groups of e.g. errors,
warnings and information.
In addition to the return value, a defined Error Handler for special error reporting will be invoked
by the Library. The error handler is an encapsulated function inside the Library with a defined
interface.
3.4 Necessary Files and Defines
For all platforms two C-syntax header files,
AI_CDEF.H
and
AIFDX_DEF.H,
are provided which
contain all information concerning constants, data types and function prototypes. The
application program only has to include
AIFDX_DEF.H
.
For VME platforms an additional C syntax header files is required:
AIVME_DEF.H
..
The application program must enter the following preprocessor definition (e.g. usually /D or -D
option of the C-compiler):
_AIM_FDX and _AIM_WINDOWS
For using the 32-Bit DLL (Windows applications) the
aim_fdx.lib
import library must be linked to the
application.
The calling convention for 32-Bit AIM_FDX Application Interface DLLs is
stdcall
.
The AFDX import library is generated with MICROSOFT Visual C/C++ compiler and is
available for 32-Bit applications.
_AIM_FDX and _AIM_VME
For using the Library in embedded VME environment,
running under any operating system.
__LYNX_OS__
Additional define, for using the Library under LynxOS
(supported version: 3.1.0) .
__VXWORKS__
Additional define, for using the Library under VxWorks.
HOST_ENDIAN_BIG or
HOST_ENDIAN_LITTLE
For switching endian order to support Little Endian and
Big Endian Systems.
_AIM_CPCI_VXWORKS
Additional define, for using cPCI under VxWorks.
e.g. AmcFdx on ACC carrier.
When using the Library in embedded VME environment, or LINUX the source code is provided.
