ATLAS2K – The Framework for Precise and Extensible Signal Descriptions in Modern ATS Sqn Ldr Dick Delaney MSc RAF Chris Gorringe
Current ATLAS Strengths of ATLAS: – Test technology related Keywords – Formal syntax and semantics – Non proprietary – Portability of Test Specifications - UUT Orientated Weaknesses of ATLAS: – Lags behind advances in technology – Limited extend mechanisms – Perceived to be expensive to use
Aims of ATLAS 2K Builds upon the strengths of ATLAS: – Focuses on signal and event definitions – Align with modern programming practices – Object Orientation – Component Object Model technology – Usable within any COM enabled development environment – Test program portability at the ATS level
ATLAS 2K Layer Model Environment Layer Test Procedure Layer Native Code Language Neutral Description (LND) Test Technology Framework (TTF) ATLAS2K Basic Components Signal Methods Modeling Language (SMML)
Signal Methods and Modeling Layer • Signals described in mathematical terms • Only a small number required • Allows pictorial representation • Underpin the Basic Components
Basic Components • Lowest level available to user • Re-usable, formally described fundamental signal classes • Used to define all higher level signals • Centered towards real world entities giving bias towards engineering • Introduce real world elements such as connections • Generic name for fundamental signal class is SignalFunction
SignalFunction Diagram Attributes SignalFunction In ( Signal) Out Signal Name Sync ( Event) Value Types: Sources, Measurement Functions, EventConditioners, CNX
Test Technology Frameworks • The extensibility mechanism • Library of pre-configured signals - built up from ATLAS 2K Basic Components • Signals in a TTF are complex and comprise: – Two or more ATLAS 2K Basic Components – Some other combination of ATLAS 2K Basic Components and other TTF signals • Domain Specific signal definitions • Will permit existing users to migrate to ATLAS 2K in the future
ATLAS 2K TTF – Triangular Wave Signal lo_ampl hi_ampl period dc_ampl noise_ ampl density freq seed Noise Constant Triangular noise_signal DC_Offset Triangular_ Signal SUM Triangular_ Wave_Signal TRIANGULAR_ WAVE_SIGNAL Event Sequence Burst Trigger_burst Enable Delay Period Duration Repetition
Language Neutral Description • Written using an IDL • Type library that provides a method for specifying all of the ATLAS 2K Basic and TTF components • Information includes: – Name, property name, allowed name – Allowed values, enumerate value types • Removes any possibility of different behaviour due to language dependent features • Ensures consistent signal definitions across all implementations
Native Code layer • Could use this layer to write test programs • Can be the native programming language for a given ATS • Allows a complete specification of test requirements at this level. • Benefits: – Test programmers can combine ATLAS 2K signals with features in preferred language – Assists test program portability – Can use COTS compilers, debuggers etc
Test Procedure Layer • Defines Stylised English syntax and semantics to define an ‘all - textual’ test requirement • Equivalent to previous published ATLAS standards • Contains traditional ATLAS verbs such as SETUP, CONNECT, ARM, FETCH • The Standard will map the Test Procedure Layer onto the Native Code Layer and TTF models • This layer provides portability at the test specification level
Environment Layer • User’s Choice of graphical interface, carrier language and development tools • Components will be COTS items such as Microsoft Developers Studio • Different end-user applications can be developed using different development environments but the same ATLAS 2K signal components
ATLAS 2K Conclusions • Culmination of a radical review of ATLAS • Applicable to a wider user community • Designers may use signal definitions • Overall reduction in life cycle costs • User choose own operating environment, carrier language and tools • Signal definitions can be deployed in other ATS architecture standards such as IVI
ATLAS 2K Conclusions • Legacy link and portability of test specifications has been preserved through Test Procedure Layer • Native Code and Language Neutral Description Layers achieve portability at the test program level • TTFs and ATLAS 2K Basic Components ensure consistency of signal definitions and provide extensibility
QUESTIONS
ATLAS 2K TTF – Triangular Wave Signal Description A periodic wave whose instantaneous value varies alternately and linearly between two specified values (initial and alternate). The interval required to transition from the initial value to the alternate value shall be equal to the interval to transition from the alternate value to the initial value. Interface Properties Description Name Type Default Range Triangular Wave Signal low lo_amp Voltage | Current | Power amplitude Triangular Wave Signal high hi_amp Voltage | Current | Power amplitude Triangular Wave Signal Period period Time DC Offset dc_ampl Voltage | Current | Power 0(Note 1) Noise Signal amplitude noise_ampl Voltage | Power (Note 2) Noise Density density Voltage/Frequency| (Note 3) Power/Frequency Pseudo Random Noise Frequency freq Frequency Pseudo Random Noise Seed seed Real Number 0 > n < 1 Burst Enable Voltage | Current | Power (Note 4) Burst timing reference Delay Time 0 Burst Initiate Period Time 1 sec Burst Cease Duration Time 1 sec Burst Repeat Repetition Integer 1
ATLAS 2K TTF – Triangular Wave Signal Notes: 1. DC Offset is included in the model to allow this property to be mapped from pervious standards of ATLAS. 2. The default for Random Noise is White Noise (characterised by a flat frequency spectrum in the frequency range of interest), White Noise needs only one parameter to be specified: either Noise Signal Amplitude or Noise Amplitude/Power Density. 3. For Pseudo Random Noise, all parameters other than Noise Amplitude/Power Density need to be specified. 4. The default for burst provides 1 un-synchronised burst of infinite length, i.e. the signal is not subject to bursts.
ATLAS 2K TTF – Triangular Wave Signal Model Description Name Type Terminal Inputs Output Formula Triangular signal triangular<type> signal[out] triangular signal amp1 lo_amp amp2 hi_amp event_time period ET=period 2 dc_offset constant<type> signal[out] dc_ offset amp dc_ampl noise_signal noise<type> signal[out] noise_signal ampl noise_ampl density density freq frequency seed seed burst Event_sequence timing sequence[out] burst signal [in] Triangular_signal sync trigger_burst Enable Enable Delay Delay Period Period Duration Duration Repetition Repetition TRIANGULAR_WAVE_ sum signal[out] TRIANGULAR_W SIGNAL AVE_ SIGNAL signal [in] triangular_signal signal [in] dc_offset signal [in] noise_signal event [in] burst
Revolution in Thinking Without taking you Pen off the paper join the dots with no more that 4 straight lines
Build your Own Extensible Signals
Use of Atlas
Puzzle The Traditional Answer
Recommend
More recommend
