![background image](http://html1.mh-extra.com/html/aim/afdx-arinc-664/afdx-arinc-664_reference-manual_2871730019.webp)
Reference Manual AFDX / ARINC 664 Application Interface Library
7
Section 3 – Application Interfacing
3. A
PPLICATION
I
NTERFACING
3.1 General
To interface the user's application program to the target hardware, the application program is
required to call the basic functions of the FDX Application Interface Library.
Before any driver function can be executed the FDX Application Interface Library must be
initialized using the following function:
FdxInit( ... )
This function performs the basic initialization of the library and returns a list of servers found in
the network environment. The basic case is to find the server named ‘local’ which describes
the computer where the application is running (can also be a stand alone system without any
network).
FdxInit
shall be called as the first function.
Note: Using the Interface Modules in an environment, which does not support an automatic mapping and resource
assign, like PCI Plug&Play, specific Initialization functions are necessary, before the application can continue with the
FdxInit.
To get the number of boards and their configuration the following command should be
performed:
FdxQueryServerConfig( ... )
This function returns a list of available resources of one server, where a resource can be a
board or a physical port of one board.
To establish target communication for a specific resource the following function shall be called:
FdxLogin( ... )
This function must be called as part of the FDX device initialization procedure.
FdxLogin
returns a unique handle which identifies the selected resource for the calling application and
initializes an internal structure for communication. Upon successful execution of the
FdxLogin
function all driver functions related to the selected resource can be called in order to control the
required operation. So functionality is distinguished between board related and port related.
To execute board functionality the user must be logged in to a board resource. To execute port
functionality the user must be logged in to a port resource.
Any application program shall finish communication to a resource with the following function:
FdxLogout ( ... )
This function performs a cleanup of the specified FDX device and must be called as the last
function to shut-down communication for the specified resource. After calling this function, the
handle is invalid and it is not possible to use it for further function calls.
Summary of Contents for AFDX / ARINC 664
Page 2: ......