1 / 15

Production Testing - an introduction

Production Testing - an introduction. Spirent Federal Simulator Users Conferences March 2006 Steve Hickling, Spirent Communications. Objectives of This Paper. Introduction to Production testing Discuss some examples Share best practice. Why test?.

earl
Download Presentation

Production Testing - an introduction

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Production Testing- an introduction Spirent Federal Simulator Users Conferences March 2006 Steve Hickling, Spirent Communications

  2. Objectives of This Paper • Introduction to Production testing • Discuss some examples • Share best practice

  3. Why test? "The causes of defects lie in worker errors, and defects are the results of neglecting those errors. It follows that mistakes will not turn into defects if worker errors are discovered and eliminated beforehand“ "Defects arise because errors are made; the two have a cause-and-effect relationship. ... Yet errors will not turn into defects if feedback and action take place at the error stage“ Shigeo Shingo 1986

  4. Types of Inspection • Inspection (of which testing is a special case) takes one of three forms: • Judgement inspection • Sorting good from bad – inspecting in quality • Information inspection • Process feedback - SPC • Source inspection • Identify sources of mistakes (Failure Modes Effects Analysis or FMEA) and mistake-proof…Poka Yoke

  5. Design of test Identify sources of error Conduct FMEA Design test to probe for error

  6. Examples of assembly error • Not connected up correctly • Wrong component or module installed • Coax crushed or kinked during installation • Software not installed or wrong

  7. Design (or specify!) for test • Assistance data • Scenario date and time • Test vectors / test port • Engineering page / GPS health page

  8. GSS6560 GSS6100 GSS6100 STR4500 STR4500 GSS4200 GSS4200 Capability and application overview Production test Maintenance Qualification IntegrationR&D Single channel Portable Commercial Fully flexible GPS / SBAS GBAS (LAAS) DR & Inertial Sensors GLONASS GALILEO

  9. GSS6100: Signal Generator • 1-channel L1 C/A or SBAS • Controlled by GPIB • Inputs/outputs for synchronisation • Can be fully ATE integrated • “Instant-on” mode • Standard Production Tests • Power level variation • Doppler shift can be changed • Ranging code selection and data message generation • Control of carrier and code phase generation

  10. GSS4200 : 6-channel simulator • Wireless A-GPS testing only • 6-channel L1 C/A code unit controlled by GPIB, USB or RS232 • Inputs/outputs for synchronisation • Tailored for Telecom production Tests • Generate an accurate position • Predefined scenarios (request via website) • 2 different calibrated power outputs (high and low level)

  11. STR4500 STR4500 : 12-channel simulator • 12-channel L1 C/A or SBAS chassis controlled by USB • Inputs/outputs for synchronisation • Controlled by SimPLEX software • Pre-defined scenarios • User actions (Manually or remotely) • Power level • Ramp on Pseudorange • Antenna pattern • Changing scenario

  12. GSS7730: L1/L2 production test • 4 Channel simulation at GPS L1 and L2 • Controlled via SimPLEX 30 software • User Defined Variables include: • Date/Time • Location • Duration • Satellite Power Levels • GPS nominal and also a high power RF output available • Remote control via SimREMOTE, over ethernet or IEEE-488

  13. GSS6100 GSS4200 STR4500 Production Testing - Examples • Check RF chain • Rx with diagnostics - single channel test • Without diagnostics – may need to navigate • L1/L2 • Independent RF chain • requires L1 and L2 • Potential for component mix-up • L1 & L2 • Errors designed out at source • L1 only may suffice

  14. Production test Vs Field Test • Production Test • Test tailored to check specific error sources • No characterisation of performance evaluation • Further investigation offline • Confidence test • Field Test • Wider range of potential failure • Performance assessment required • Diagnostics on the test station

  15. Questions?

More Related