Aerospace and Electronic Systems - March 2019 - 13

Annighoefer et al.

Figure 7.
Maximum topology of the ACMS demonstrator limited by the available components.

are Intel Atom D510 computers at 1.6 GHz. The CPMs as
well as a test and virtualization computer are Intel Core
i7-4770 computers at 3.40 GHz. POSIX is used as the OS
API. In total, there are six SWIs, two CPMs, and four
IOMs physically available for building ACMS topologies.
The backbone network is Ethernet. The switches
have the same hardware as the IOMs. The switching
behavior is implemented in software. The ACMS relies
on unique IP addresses assigned by DHCP for topology discovery. Topic communication is implemented
as an UDP multicast.
Peripherals are common cabin peripherals, namely
three passenger service units (PSU), a flight attendance
panel (FAP), a light controller (LC), three cabin interphones (CIP), speakers (SP), a temperature sensor (TS),
and a door controller (DC). The only interface accepted
for peripherals is Ethernet. Local interface wrappers based
on Raspberry-PIs connect peripherals without a native
Ethernet interface. For the detection of peripherals, a
plug&play protocol was developed.
The CORG is an Intel Core i5-3470 CPU @ 3.20 GHz
2 GB RAM desktop computer. It provides the user interface to start and monitor the AAP self-configuration and
verification process as an interactive webpage.
In addition to the AAP modules and the CORG, a
test and virtualization computer (TEVIC) is connected
to the ACMS. The TEVIC is connected to all modules
with a separate Ethernet network. It has access to all
topics and internal states of all the partitions. It is used
for testing, live monitoring, and fault injection in the
ACMS demonstration. The TEVIC is not necessary for
NOP. Moreover, the TEVIC offers virtualization to
simulate virtual modules, switches, and peripherals on
the backbone network.
MARCH 2019

ARCHITECTURE OF THE ACMS DEMONSTRATOR
The architecture of the ACMS in principle can be composed arbitrarily from the modules available. In correspondence to real CMS, however, a few assumptions on
the architecture were made. 1) The ACMS is controlled
by a single redundancy group of CPMs running in master-
slave mode, i.e., each C-APPs runs in parallel on each
CPMs. 2) There must be at least two parallel backbone
networks, e.g., for two networks these could be the left
side and right side. Each backbone network must be accessible by each of the CPMs. 3) Each backbone network is a
daisy chain of SWI (S), i.e., with no cycles or branches.
The SWIs connect to the IOMs. 4) The last SWI in the
daisy chain has no IOM. It cross connects to the other
sides, i.e., left-right. This is used for automatic fault recovery. Figure 7 shows an example of an architecture built
with the ACMS components. It has the left and right
branch of the network. For this demonstration, the TEVIC
simulates two virtual SWIs and the door controller (DC).

APPLICATIONS OF THE ACMS DEMONSTRATOR
The following system function applications were implemented on the ACMS:
PC comprises the sensing of the call buttons at the
PSU, the control of a local indication light as well
the central indication and resetting an attendance
call at the FAPs.
Illumination (IL) comprises the setting of light
scenarios with a light controller and multi-color
LED stripes as well as the control of the reading
lights of the PSU. Reading lights can be

IEEE A&E SYSTEMS MAGAZINE

Aerospace and Electronic Systems - March 2019

Table of Contents for the Digital Edition of Aerospace and Electronic Systems - March 2019