View
213
Download
1
Category
Tags:
Preview:
Citation preview
Page1Framework Working Group 2007
ATML Use cases
Use of ATML by external agencies is gathering momentum
Page2Framework Working Group 2007
Agilent Instrument Database
Performing an independent evaluation into using the ATML instrument description and ATML capability to distribute their instrument information.
This is important because, if successful, there will be a lot of information in the ATML format – that will generate a lot of user based feed back on our trial use standard(s)
Dan Pleasant’s presentation Instrument Description Working Group Meeting Tuesday Morning 9:00
Page3Framework Working Group 2007
Synthetic Instrument defined using ATML
Synthetic Instrument Working Group has defined a general architecture for synthetic instruments.
Each component that makes up the synthetic instrument needs both software and hardware interchangability.
ATML Instrument Description has been chosen as the format to represent the description of the hardware specifications for the following components: Arbitrary Waveform Generator Digitizer Down Converter Up Converter
IVI Drivers have been selected for the software driver interchange format.
Page4Framework Working Group 2007
LXI Consortium
Investigating using ATML Capabilities as part of LXI Discovery
Page5Framework Working Group 2007
MoD Open System Architecture Approach
The MoD currently have a policy for ATS to use the IEEE 1641 ‘signal modelling’ standard.
Looking to standardise a common Open System Architecture approach
This process is expected to make heavy use of the ATML standards
Page6Framework Working Group 2007
Proposed Common OSA Standards
High degree of obsolescence coupled with a lack of commonality has resulted in:High in-service support costsRelatively low utilisation of test platforms
A common open standard is therefore vital to overcome these concerns. This must be encompassed within the common GPATE with the technology to achieve this capability.
Page7Framework Working Group 2007
Common Core ATS Architecture
Computer InstrumentationUnit Under TestHardware
Software
Operating System
Test Program
Test HeadCommon Core
Test Results
Page8Framework Working Group 2007
Common Core ATS Architecture GoalTPS Reuse & ATS Interoperability
TPS
Platform 1
Platform 2
Platform 3
Page9Framework Working Group 2007
Signal Interface
MoD - Signal Policy with ATML components
DRVTest
Results
Common UseStandard
Signal Library
SignalProgram
ATML Capability
TestDescription
DoD Framework Working Group
Page10Framework Working Group 2007
IEEE Std. 1641 and the DoD Automatic Test System Framework Elements
Framework Members:
Michael Malesich; Jennifer Fetherman; Chris Gorringe; Bob Fox; Tom Gaudette; Ron Taylors; Hugh Pritchett; John Sheppard; Joe Stanco; Ken Fox; Mukund Modi; Pat Kalgren
Page11Framework Working Group 2007
Instrument Interface Layer
Future TPS development - ATML Test Information Using Signal Models Enhancing Reusability
TestDescription
Test ProgramGeneration
Common UseSignal Library
ATE Capabilities
InstrumentDescription
Test StationDescription
TestAdaptor
TestProgram
InstrumentSignal
Mappings
RI3152 Ag38152a Elgar 115
1641 Elements
ATML Elements
Implementation
UUTDescription
ATS Software
TestResults
Page12Framework Working Group 2007
REQUIRED Common Use Standard Signal Library TSF Development
We need to develop standard Signal libraries to capture the test domain knowledge of what signals are required.
CASS ATLAS Signal Library
Already modelled certain signals and measurements in 1641(but never completed as TSFs)
SIWG measurement science & ‘signals’ methods ARGCS ATLAS Signal Libraries
Train users in using the common signal libraries in their field of operation rather than the user needing to know how specific signal are implemented.
TPS projects and field test engineers would then use these TSF signal definitions as reusable components, rather than continually build there own up from scratch
Provide a solid foundation for a standard common use signal library
Ability to use additional interchangeable Signal Libraries though TSFs New TSFs can be added into the standard at subsequent revisions
Page13Framework Working Group 2007
Instrument Interface Layer
Future TPS development - ATML Test Information Using Signal Models Enhancing Reusability
TestDescription
Test ProgramGeneration
Common UseSignal Library
ATE Capabilities
InstrumentDescription
Test StationDescription
TestAdaptor
TestProgram
InstrumentSignal
Mappings
RI3152 Ag38152a Elgar 115
1641 Elements
ATML Elements
Implementation
UUTDescription
ATS Software
TestResults
Page14Framework Working Group 2007
Instrument Interface Layer
Future TPS development - ATML Test Information Using Signal Models Enhancing Reusability
TPDUTR
Test ProgramGeneration
UTR, UDI
ATE Capabilities
IFP
TSFP
AFP
TestProgram
InstrumentSignal
Mappings
DRV Instrument Drivers
1641 Elements
ATML Elements
Implementation
UDI
ATSSoftware
MTD
Page15Framework Working Group 2007
DoD ATS Technical Framework RelationshipsDoD ATS Technical Framework Relationships
LEGEND
Resource or generic Level
Signal or independent Level
UUT Test Level
Instrument Functional &
Parametric DataIFP
Adapter Functional &
Parametric DataAFP
InstrumentCommunication
ManagerICM
Instrument DriverDRV
SystemFramework
FRM
Resource Management
ServicesRMS
DiagnosticServices
DIAS
Digital Test Format
DTF Test Program Documentation
TPDMultimedia
FormatsMMF
Test Station Functional &
Parametric DataTSFP
Maintenance Data & Services
MTD
Built In Test Data
BTD
Product DesignDataPDD
UUT Test Requirements
UTR
ATE Software
Switching & Wiring
Instruments
Resource Adapter
Interface RAI
Test Program
Diagnostics
Diagnostic DataDIAD
TestAdapter
Interface or hardware Level
UUT Device
Interfaces UDI(Hardware)
UUT Device
Interfaces UDI(Software)
Instrument or device Level
Information
Services or API
Data Networking
NET(TCP/IP)
Computer toExternal Env.
CXE(TCP/IP)
Data/Distributed
NetworkDNE
Run Time Services
RTS
Common Test Interface
CTI
Master Conformance
IndexMCI
Page16Framework Working Group 2007
DoD ATS Technical Framework ATML RelationshipsDoD ATS Technical Framework ATML Relationships
Instrument Functional &
Parametric DataIFP
Adapter Functional &
Parametric DataAFP
Test Program Documentation
TPD
Test Station Functional &
Parametric DataTSFP
Maintenance Data & Services
MTD
UUT Test Requirements
UTR
ATE Software
Switching & Wiring
Instruments
Test Program
Diagnostics
TestAdapter
UUT Device
Interfaces UDI(Software)
Run Time Services
RTSMaster Conformance
IndexMCI
Resource Adapter
Interface RAI
Product DesignDataPDD
Resource Management
ServicesRMS
Page17Framework Working Group 2007
DoD ATS Technical Framework SCC20 RelationshipsDoD ATS Technical Framework SCC20 Relationships
Instrument Functional &
Parametric DataIFP
Adapter Functional &
Parametric DataAFP
Test Program Documentation
TPD
Test Station Functional &
Parametric DataTSFP
Maintenance Data & Services
MTD
UUT Test Requirements
UTR
ATE Software
Switching & Wiring
Instruments
Test Program
Diagnostics
TestAdapter
UUT Device
Interfaces UDI(Software)
Run Time Services
RTSMaster Conformance
IndexMCI
Resource Adapter
Interface RAI
Product DesignDataPDD
Resource Management
ServicesRMS
DiagnosticServices
DIAS
Digital Test Format
DTF
Diagnostic DataDIAD
Common Test Interface
CTI
Page18Framework Working Group 2007
Fin
The Community wants our ATML standardsThey are a significant part of both the Mod and DoD
future solutionsThere is a commercial advantage in using ATMLWe need to get them out and balloted
Getting ATML!
Page19Framework Working Group 2007
No - I really have finished
Page20Framework Working Group 2007
RoadMap DoD - ATML Support Interfaces
ATS Software
ATML Capability
TestDescription
UUTDescription
InstrumentDescription
TestStation
TestAdapter
TestResults
Common UseStandard
Signal Library
Signal
Test Program
DRV
Page21Framework Working Group 2007
Signal Interface
RoadMap MoD - Signal Policy
DRVTest
Results
Common UseStandard
Signal Library
SignalProgram
ATML Capability
TestDescription
Page22Framework Working Group 2007
Station Software
Signal Interface
RoadMap Coalition Open Architecture
DRV
ATML Capability
TestDescription
UUTDescription
InstrumentDescription
TestStation
TestAdapter
TestResults
Common UseStandard
Signal Library
Signal
SignalProgram
Page23Framework Working Group 2007
Signal Modelling and the Framework
The term signal modeling is simply defining signals through models. A signal model includes signal sources, signal conditioning, signal based
measurement, digital, communications & busses, events, timing and even locations or combination of them.
The model is an executable specification that provide a means to define both behavior and interface parameters, and utilize both composition and hierarchy to allow building increasingly complex signal definitions, as reusable components
Regardless of the complexity of the signal, because they define behavior, signal models represent an ideal component of test requirement interchange.
Signal modeling can have a positive impact on several DoD (and MoD) objectives
Improve instrument Interchange Make ATE more adaptable with no penalty to requirements Faster technology insertion Improve TPS rehost Improve TPS interoperability Use model based programming techniques Modernize test programming environment Capture ‘design to test’ data
Page24Framework Working Group 2007
Framework Elements & ATML
UTR (UUT Test Requirements) IEEE 1641 Signal Libraries
TPD (Test Program Documentation) Test Description (ATML)
IFP, AFP, TSFP (Instrument Functional & parametric Information) Signal Capability ATML and IEEE 1641
UDI (UUT Device Interfaces) Signal Libraries (1641 TSFs)
MTD (Maintenance Test Data) IEEE 1636.1 ATML Test Results
RMS (Resource Management Services) IEEE Std. 1641 – Annex C Signal Resource Manager
RTS (Runtime Services) IEEE Std. 1671 Annex C
RAI (Resource Adaptor Interface) IEEE Std. 1641 - New Annex to Firm up UUT requirements and extract Connection & Timing to top level
MCI (Master Conformance Index) IEEE Std. 1641 – Annex C Signal Resource Manager
PDD (Product Design Data) UUT Description (ATML)
Recommended