Page Content
CMS380-400
A380 | A400M Central Maintenance System (CMS) Simulation
Application Scope
The CMS380-400 simulates a “standard B” Central Maintenance System communicating with up to four BITE interfaces of type 1 via AFDX®, Ethernet or ARINC 429.
The Normal Mode and the Interactive Mode are fully supported and comply with the latest specifications.
Data memorization, monitoring and error injection provide great benefits for testing or developing BITE systems.
Architecture
The CMS380-400 simulation runs in the ADS2 environment, using TechSAT’s product family of AFDX® and ARINC 429 boards.
Portability – the CMS380-400 simulation runs in every ADS environment, including System Integration Test benches as well as standalone PCs equipped with AFDX® hardware.
CMS architecture for standard B – besides the system on which the simulation is hosted, remote maintenance terminals can be used for maintenance messages and reports display as well as processing Interactive Mode tests.
Normal Mode
Visualization of data – display of encoded and elaborated failure message data (possibility to configure LRU and pin/connector tables for encoding update), encoded BITE status data and BITE system identification data.
Verification of data – display of hexadecimal view, transmission rate and data integrity for all Normal Mode data, and verification of transmission dynamics for failure messages (multiple transmission of specific messages).
Data recording – recording of data together with verification results (transmission rate and data integrity) in separate ASCII files, one for each BITE interface.
General parameters transmission – definition of the CMS general parameters data and transmission rate
Interactive Mode
Complete execution of tests / specific functions defined in XML specifications – web browser graphical interface used to display screens, allowing user interaction with the CMS.
Tracing / monitoring of the communication – display of content and structure of BITE/CMS commands (complete encoding of header and body), tracing of the communication dynamics with precise time-stamping.
Verification of BITE commands – verification of data integrity and commands consistency against the XML specification.
Error injection – configuration of the CMS behavior with deviations from the protocol specification (handshaking messages), transmission of non-coherent frames.
Test results recording – verification of test results integrity and sequencing, recording of data.
Scripting functionality – implementation of whole test procedures using the Python API, allowing execution of tests without user interaction
Test Recording / Replay – recording of tests traces (for graphical offline analysis), automatic repetition of recorded Interactive Mode tests without user interaction
