ua_emulator

Simplify the tasks

 

UA Emulator is a powerful, flexible solution designed to work with PACE VAPS XT 661 and interface to third-party ARINC 661 CDS. Only minimal knowledge of ARINC 661 protocols is required to get up and running. With an intuitive interface designed for rapid message creation and detailed analysis, UA Emulator simplifies the tasks of widget debugging, ARINC 661 traffic log analysis, CDS Layer Design testing, and User Application emulation.

UA Emulator is extensible with open file formats for custom messaging and custom widget support

Each deployment of ARINC 661 is different and custom messages and bespoke widget types are often used to overcome real-world needs. UA Emulator adapts to meet real-world needs by loading data describing extensions to the ARINC 661 Protocol.

 

UA Emulator is extensible with open file formats for custom messaging and custom widget support

Each deployment of ARINC 661 is different and custom messages and bespoke widget types are often used to overcome real-world needs. UA Emulator adapts to meet real-world needs by loading data describing extensions to the ARINC 661 Protocol.

Key
Features

 

For CDS developers


  1. Easy-to-Use user interface – build messages quickly and accurately 
  2. Message auto-complete – concentrate on the data of interest as headers, footers, identifiers, etc. are filled in for you 
  3. Selectable widget instances and properties – use mouse to select message target, identifiers filled in automatically without referring back to documentation 
  4. Smart Value Editors – the most appropriate editor for the type of data being edited is automatically provided - including enumerated choices 
  5. Quickly build message scenarios to analyse how the CDS will look when it is being driven 
  6. ARINC 661 protocol knowledge only needed for advanced testing.

 

For Test Engineers


    1. Intuitive user interaces makes it easy to build test messages – without learning ARINC 661protocol firsts
    2. Intuitive user interaces makes it easy to build test messages – without learning ARINC 661 protocol first 
    3. Build scenarios: sequences of messages that can be saved and replayed 
    4. Simplify system integration activities, especially for projects with distributed development teams
    5. Save traffic history in comparable format 
    6. Copy and paste message bytes 
    7. Simulate multiple User Applications  
    8. Simulate a CDS to test a User Application. 

 

For software/System integrators


  1. Simulate any equipment ARINC 661 Message, e.g. when real equipment or CDS is not available 
  2. Test at the desk – reduces rig-time requirements 
  3. Analyse ARINC 661 message traffic logs – detect software faults without writing special message analysis code 
  4. Playback message sequences – repeat what happened at real time, in a test environment 
  5. Extensible, cater for messages sent outside the ARINC 661 protocol.

 

The technical details


  1. Windows 7 and 10 Based Development Environment
  2. Automatic Linkage to ARINC 661 Standards PDF 
  3. User definable Transport Plugin for connecting to real hardware 
  4. User extendable message configuration (allow custom messages outside of standard to be decoded) 
  5. Command line headless mode for automated testing 
  6. Compatible with VAPS XT 661 models files

Comprehensive
Toolset

A fast, reliable tool that simplifies testing in Cockpit Display System, widget, and User Application development

  1. Achieve complex widget interaction with minimal knowledge of ARINC 661 
  2. Analyze real-time runtime messages offline, and identify problems quickly 
  3. Build scenarios: sequences of messages that can be saved and replayed 
  4. Verify using messaging scenarios 
  5. Enter values in native data types (or HEX as required) 
  6. Plug and play: Apply your energies to delivering successful outcomes, rather than internal test tools

Supports custom messaging and custom widgets

  1. Find messages that do not conform to the protocol and allowed extensions
  2. Share extension information between users and across the supply chain
  3. Switch between permitted protocols when switching between projects
  4. Use a single tool to test different CDS; Simply change the message transport module

Load More >