3
Tuesday, May 09, 2006Elcoteq Presentation / Jussi Savolainen3 Background Bluetooth RF conformance testing by far the most expensive (time and cost) of the conformance tests, because –off-the-shelf test systems > 1 M€ (cost) –response time using external test houses too long (time) Projects need a heap of test data in a short amount of time for statistical analysis, etc. Failing in type approval tests is expensive

4
Tuesday, May 09, 2006Elcoteq Presentation / Jussi Savolainen4 Research problem How to automatically perform the Bluetooth RF conformance tests according to Bluetooth Test Specification version 2.0+EDR in prequalification phase of the design How to perform the tests simultaneously for a number of devices How to support different Bluetooth products and product types

6
Tuesday, May 09, 2006Elcoteq Presentation / Jussi Savolainen6 Bluetooth essentials Bluetooth connects portable or fixed equipment, and it is a cable replacing technology, which is cheap and robust with low power consumption Technology initially developed at Ericsson in 1994 Bluetooth SIG established in 1998, first version of specification out same year Most recent version 2.0+EDR came out in 2004 with support to higher data rates than previously Operates on unlicensed (but not unregulated!) 2.4GHz ISM band M S S S M/S S piconet 1 piconet 2 psps sbsb psps Scatternet with two piconets

9
Tuesday, May 09, 2006Elcoteq Presentation / Jussi Savolainen9 Bluetooth RF measurements - basics Device Under Test (DUT) can be placed to test mode, which allows configuration and control of the DUT Some tests must be performed under extreme temperature and voltage conditions Tests divided in transmitter (TX), receiver (RX) and transceiver (TRC) measurements TX and RX tests according to Bluetooth RF test specification TRC tests according to ETSI EN

16
Tuesday, May 09, 2006Elcoteq Presentation / Jussi Savolainen16 Software implementation – data storage System creates ~50Mb/day of data  text files or excel sheets are not an option Writer (test system/test engineer) and reader (customer project/RF designer) are separated Graphs and reports must be easily extractable from database Short response time for new graphs and reports

17
Tuesday, May 09, 2006Elcoteq Presentation / Jussi Savolainen17 Conclusions and further work This type of system is never finished as interface to a new DUT must be built every time and data storage is updated Error handling updates Calibration Measurement equipment SW updates