OVERVIEW OF TESTBED
Contents
• Test Bed overview
1. Block diagram of Test bed.
2. Data flow diagram
• Daemons, libraries and simulations.
• Adding new signals to test bed.
A small HSI test setup
Host System USB Cable BDM/JTAG BDM/JTAG Cable Target
Tool
Industrial PC
with RT
Tester S/W Serial RS-232
PCI-7444 DO
128 ch DO Card
DI
PCI-7433HIR 64 ch. DI
64 ch DI Card
64 ch. DO
EXC-2000PCI 20 ch. DI
ARINC – 429, 5 ch
ARINC-429,
CAN 4 ch
CAN Card
Test Rig LRU Emulator
Test bed
Test bed
Hardware components
Introduction to ASTS
Data Flow diagram
Daemons, Libraries and Simulations
Overview of Daemons
1. What is daemon?
• A Daemon is a process, which runs permanently on a designated
PC to simulate connected components and stimulate the system under
test.
• Daemons is used for communication between interface hardware and
RTTester tests.
• Available Daemons: CAN, AFDX, Digital I/O, RS232.
Daemons contd..
• The access to the hardware interfaces of the Target board is provided
by daemon processes running on the cluster nodes that contain the
respective hardware interface card.
• The daemon processes are started at boot time of the cluster node
and provide persistent access and stimulation of the hardware
interfaces.
• The hardware interfaces can be accessed through the shared memory
interface of the daemon process without any interface module or test
procedure being executed. This is an advantage if a hardware
interface should be monitored manually for debugging purposes.
Interface modules(IFM)
• The interface modules of a HSI test procedure connect either
directly to the interface hardware or to an interface daemon.
• They offer channels to all abstract machines, which can be
used to either read data from the interface or stimulate the
interface behavior. The RTTester channel communication
establishes the communication between the abstract machines
and interface modules. As soon as an IFM or AM (Abstract
machine) produces an interface event on one of the channels,
the message is communicated instantly to all other AMs or
IFMs, which are listening on this channel.
Libraries
Library Overview
• Provide service functions often needed.
• Ease implementation of checkers.
Contents of ASTS Library for A340
• VOL support: Get volumes, get switch and filter state
• AUD support: Get handset states, use handsets (incl. CPT),
get connection states.
• ACP support: Get ACP lamp state, get ACP signals
Libraries-Usage of Lib Functions
Confinc sets up AM
Include the particular library function in *.conf file of TP
Library confinc
Libraries contd..
Implementation of checkers using library functions.
Example : VOLUME CHECKING
Objective- Check amplifier and chime volumes set by CIDS against
• CAM configuration and specified application logic.
• Derive individual amplifier/chime volumes from CAM.
• Perform some volume related activities.
(e.g. PA call, OLL, start engine)
• Derive volume modifications according to CAM and TP logic.
Libraries contd..
Simulations
• Simulation is the imitation of some real thing available.
• Some hardware interfaces of the Target board can be
simulated by simulations. These simulate the concrete
hardware and allow for testing without actually connecting
to this hardware.
Simulations contd..
Simulations with respect to A330f test bed
• Simulators are not part of the testbed
• But some are predened for the following reason:
1. Some have to be implemented on daemon layer because
they require time critical responses.
Predefined Simulations:
• EPSU/ASPSU/IPCU
• CMC/CMS Simulation
• Smoke related: S/D simulation, DMB INLINK, Serial INLINK
Simulations: CMS/CMC Simulation
• Transmission of flight context data in normal mode to CIDS
• Analyzing of the normal mode data sent from CIDS to CMS
• Simulation button presses on the MCDU
• Handling of interactive mode protocol
• Displaying of MCDU pages
Simulation example
CMC simulation to be shown in citrix.
What is a Signal?
Signal Characterization
• Communicated global variable
• Data exchange between AMs and SUT
Signal definition File
• [Link] contains the definitions of all signals.
Signal definitions
Test bed updation
Adding a new signal
• Set-up of local signals.
• Set-up of Global signals.
1. Adaption of existing interface to
implement new signal
Set-up local signal
• Add new signal to
$RTT_TESTCONTEXT/sigdef/[Link]
Declare usage of this signal in config file:
• SIGNALSET ; <..>.sig
• Use signal in test procedure like standard signal
• Local signals are not mapped to any interface of the SUT
• Local signals do not have a communication direction,
can be read and written by any AM
• Local signals are also communicated between cluster nodes
Set-up of local signal
Set-up of global signal
Adding a new DISCRETE signal
No change of ifm_disc.rts necessary for that.
Add discrete Signal LGCIU1_NGC_IN
Start Signal Editor (Excel).
Adding discrete signal
Adding discrete signal
Implementing Top line output signal
• Implement signal Passenger_Temper.
• For direction ASTS to Director we assume that the topline bits
2 : : : 9 transmitted in direction DEUA to DIR on port 5 to has
been assigned to functionality \Passenger_Temper". Now the
signal named \Passenger_Temper "shall be provided in the
test bed.
• Signal declaration in [Link], definition in .rts file.
Top line specification
Add Topline Output signal to [Link]
Topline: Selected signal parameter
?
Creating Business Impact
Providing Expert Solutions
Thank You
Delivering Quality Consistently
Thank You
Building Partnerships Globally
35
