© Copyright EADS TEST & SERVICES 2006 Using Signals in TestDescription & Capability and a TestResults Example

© Copyright EADS TEST & SERVICES 2006 Signal Capture Generating 1641 Signals from a Product Acceptance Specification (PAS) Translation from the PAS to 1641 signals is reasonably straightforward –This is because PAS is written in terms of UUT –Extraction is a manual process E.g.: Monitor SK2-F with respect to 0V at SK2-s and verify that the voltage is +5.0V +/-0.2V Translates into: PAS 1641 Signals

© Copyright EADS TEST & SERVICES 2006 In older ATPs, this is often all that is available. Code, style & structure may be unfamiliar Contain ATE specific information. Extracting any large amounts of information manually is very laborious and, thus, prone to error. Irregular structure and ATE specifics mean that automatic extraction of signals is not possible –Without standardised extraction, the test program is being virtually re-written and must go through acceptance. Signal Capture Generating 1641 Signals from Existing Source Code Test Program 1641 Signals

© Copyright EADS TEST & SERVICES 2006 Test Description. < Signal ….

© Copyright EADS TEST & SERVICES 2006 Test Program ' Create EU Power Supply Signal Set psu = ate.Require("PSU") psu.Name = "PSU1" psu.ampl = "23.5 errlmt ±0.5V" psu.current_limit = "550mA" Set tw = ate.Require("TwoWire") tw.Name = "TW1" tw.In = "PSU1" tw.hi = "BatteryPos" tw.lo = "BatterNeg" psu.Out.Run ' Create Measuremnt Set monitor = ate.Require(" " & _ " " & _ " ") monitor.Out.Run 5000 monitor.Out.Stop Set monitor = Nothing.NET (e.g. TestBase) TestStand

© Copyright EADS TEST & SERVICES 2006 Capability The resource description of a Racal4152A DMM and associated connection to the UUT. : :

© Copyright EADS TEST & SERVICES 2006 Architecture

© Copyright EADS TEST & SERVICES 2006 Test Signal Run-Time System Signal Interface (RAI?) Test Requirement Test Program ATE TestResults Logger UUT Native Driver Native Driver Switch RFSynth Signal Interface Native Driver DMM General Architecture Using a Signal Interface

© Copyright EADS TEST & SERVICES 2006 TestResults Sample ==================== PROGRAM NUMBER M ISSUE 2 MY TEST PROGRAMME UUT SERIAL NUMBER :- DATE : T12:24:28 OPERATOR NAME :- MCORNISH ==================== ==================== TEST PASS HIGH SOURCE TEST T HL = MV = LL = ==================== TEST PASS HIGH SOURCE TEST T HL = MV = LL =

© Copyright EADS TEST & SERVICES 2006 Results Data Vs. Modelled Data No significant differences found between the native and 1641 r.f. test results (Aeroflex)

© Copyright EADS TEST & SERVICES 2006 Synthetic Instruments e e e e e e e

© Copyright EADS TEST & SERVICES 2006 Comparison of Effort Typical Effort to Generate Parametric Tests in the Power/Frequency Domain (Aeroflex) Port IVI Test to 1641 (TestStand) 1 month 1 week time Generate Native Test from General Documentation Port Native Test to IVI (TestStand) (given the presence of the 1641 elements) 1 Day

© Copyright EADS TEST & SERVICES 2006 Where Were Up To IEEE Std Signal & Test Definition –Signal-based test definition standard. –Requirement of MoD ATS Procurement Policy. –Utilised in areas of IEEE P1671 ATML. IEEE 1641 implementation studies: –Phase 1 - Analogue signals/3 test platforms - Racal Instruments. –Phase 2 - Complex RF and a Synthetic Test Platform – Aeroflex. –Phase 3 - Digital signals/ test platforms - under negotiation. –Phase 4 – Parallel development; comparison of traditional vs

© Copyright EADS TEST & SERVICES 2006 Conclusions IEEE Std has been shown to be capable of defining: –Portable analogue signals, –Typical RF parametric tests. Significant effort required to extract the information required to define a 1641 (platform independent) test, from an existing, non-standard or proprietary, test architecture. Though not a unique approach, 1641 represents a departure from many existing test methodologies. –Training would address many issues. No significant differences observed (existing vs. 1641) for: –Test results. –Speed of execution.