O2OBTDVK110Bluetooth Developer Kit

94001620000 Rev. 1.2 TR special, 2002-12-06 72000 Bluetooth Development Kit User’s Guide Motorola reserves the right to make changes without further notice to any products herein. Motorola makes no warranty, representation or guarantee regarding the suitability of its products for any particular purpose, nor does Motorola assume any liability arising out of the application or use of any product or circuit, and specifically disclaims any and all liability, including without limitation consequential or incidental damages. “Typical” parameters which may be provided in Motorola data sheets and/or specifications can and do vary in different applications and actual performance may vary over time. All operating parameters, including “Typicals” must be validated for each customer application by customer’s technical experts. Motorola does not convey any license under its patent rights nor the rights of others. Motorola products are not designed, intended, or authorized for use as components in systems intended for surgical implant into the body, or other applications intended to support life, or for any other application in which the failure of the Motorola product could create a situation where personal injury or death may occur. Should Buyer purchase or use Motorola products for any such unintended or unauthorized application, Buyer shall indemnify and hold Motorola and its officers, employees, subsidiaries, affiliates, and distributors harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of personal injury or death associated with such unintended or unauthorized use, even if such claim alleges that Motorola was negligent regarding the design or manufacture of the part. The Bluetooth trademarks are owned by their proprietor and used by Motorola, Inc., under license. All other product or service names are the property of their respective owners. © Motorola, Inc. 2002. Motorola and are registered trademarks of Motorola, Inc. Motorola, Inc. is an Equal Opportunity/Affirmative Action Employer. How to reach us: USA/EUROPE/Locations Not Listed: Motorola Literature Distribution; P.O. Box 5405, Denver, Colorado, 80217. 1–303–675–2140 or 1–800–441–2447 JAPAN: Motorola Japan Ltd.; SPS, Technical Information Center, 3–20–1, Minami–Azabu, Minato–ku, Tokyo 106–8573 Japan. 81–3–3440–3569 ASIA/PACIFIC: Motorola Semiconductors H.K. Ltd., Silicon Harbour Centre, 2 Dai King Street, Tai Po Industrial Estate, Tai Po, N.T., Hong Kong. 852–26668334 Technical Information Center: 1–800–521–6274 HOME PAGE: http://www.motorola.com/semiconductors/ © Copyright Motorola, Inc., 2002 MOTOROLAContentsiii Preliminary Chapter 1 Introduction 1.1About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1.2Additional Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 1.3Downloads and Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 1.4System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 1.5Acronyms and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Chapter 2 Product Overview 2.1Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 2.2Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 2.3ICs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 2.4Software Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 2.4.1Bluetooth HCI Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 2.4.2Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 2.4.3DemoBench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 2.4.4RadioTest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 Chapter 3 Setup Chapter 4 Hardware 4.1Signal and Connection Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 4.2Environmental. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 4.3Mechanical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 4.4Electrical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 4.4.1Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13 4.4.2Reset Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13 4.4.3Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13 4.4.4Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14 4.4.5UART Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14 4.4.6CODEC Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14 4.4.7Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15 4.4.8100 mm² Module. . . . . . . . . . . . . . . . . . . . . .…

Text truncated - open the document above for the full version.

Close From: Chris Harvey To: Marianne Bosley Cc: Subject: FW: Digianswer MT#13094 Sent: 1/27/2003 12:02 PM Importance: Normal Please follow the instructions below. -----Original Message----- From: [email protected] [SMTP:[email protected]] Sent: Monday, January 27, 2003 11:56 AM To: [email protected] Subject: To: Christopher Harvey From: Richard Fabina [email protected] FCC Equipment Authorization Branch Re: FCC ID: O2OBTDVK110 Applicant: Digianswer A/S 731 Confirmation Number: TC329035 Date of Original Email: 01/27/2003 Based upon your email of January 14, 2003, we have set aside the dismissal of the above referenced grant of equipment authorization. To complete the record, please upload a copy of this correspondence to the application files and then correct the grant in the manner that you indicated. Information regarding your application and/or updating your application can be found by accessing www.fcc.gov, E-Filing, OET TCB/Accreditor Electronic Filing. Do NOT reply to this email using the reply button. In order for your response to be processed expeditiously, you must upload your response via the Internet at www.fcc.gov, E-Filing, OET TCB/Accreditor Electronic Filing, TCB Login, Submit Correspondence. Any questions about the content of this correspondence should be directed to the e-mail address listed below the name of the sender.

This document contains information on a product under development. Motorola reserves the right to change or discontinue this product without notice. © Motorola, Inc., 2002. All rights reserved. Preliminary With the development kit for the Bluetooth Platform Solution from Motorola, the company is launching yet another unique demonstration and development tool for its platform. The development kit contains all of the hardware, software, and documentation needed to evaluate the functionality of the following Motorola Bluetooth platform solution IC’s: •MC72000 Bluetooth Baseband Controller and Transceiver IC •MC13181 Wireless Power Management IC Also, you can develop software and hardware solutions around the platform chipset. The development kit makes it possible to easily and quickly set up and start demonstrating a Class 2 Bluetooth solution, and it provides an efficient layout for the RF on an FR4 PCB substrate. The primary applications of the development kit are: •Evaluation of the platform chipset and its features •Porting of a user Bluetooth stack to the Motorola Bluetooth hardware •Prototyping of a Bluetooth-enabled host device •Reference design for quick layout of a Bluetooth solution based on the MC72000 IC The development kit is Bluetooth 1.1 qualified and will be type approved in a great number of countries. See the section “Type Approvals“. For detailed information on the MC72000 and MC13181 IC’s, please refer to the technical brief for each. Technical Brief 94001480600 Rev. 1.1, 2002-08-05 MC72000 Development Kit for the Bluetooth Platform Solution from Motorola 1 Block Diagram . . . . . . . . 2 2 Signal and Connection Description 3 3 Environmental . . . . . . . . 4 4 Mechanical . . . . . . . . . . 4 5 Electrical . . . . . . . . . . . . 4 6 Interfaces . . . . . . . . . . . . 5 7 Antenna . . . . . . . . . . . . . 5 8 Development Tools . . . . 5 9 Documentation . . . . . . . 5 10 Sales Package Contents 6 11 Type Approvals . . . . . . . 6 2MC72000 Development Kit for the Bluetooth Platform Solution from Motorola Technical Brief MOTOROLA Block Diagram 1 Block Diagram Figure 1. Block Diagram 2 Signal and Connection Descriptions The development kit contains the following connections, switches, and indicators: •Power supply input •Modular jack 4/4 connector for mono-audio speaker and microphone (headset application) •RS232 interface •UART interface •Antenna connector •JTAG allowing interface to MC72000 production test •Reset switch •Three control buttons for eg. headset application •On/off switch •Status LEDs The power supplied for the development kit is DC with the ratings stated in the specifications. An analog audio signal to be transmitted over the Bluetooth connection can be fed into the development kit via the modular jack or as streaming audio through the host interface. It will be converted to digital data and transmitted through the Bluetooth link. A digital audio signal received from a connected Bluetooth device will be converted to an analog audio signal and available at the modular jack or as streaming audio through the host interface (UART, SSI, SPI). The MC72000 has a Bluetooth Audio Signal Processor (BTASP) for superior audio performance. The RS232/UART interfaces can be used to transfer data and audio between a host and the Bluetooth device. The firmware of the development kit can be upgraded through the RS232/UART interface. The CODEC is attached to the MC72000 via the SSI interface. RS232 DC Power Input UART RS232 Level Shifter CODEC Modular Jack MC72000 MC13181 Status LEDsReset Switch EEPROM Antenna Connector 13 MHz 32 KHz Environmental MOTOROLAMC72000 Development Kit for the Bluetooth Platform Solution from Motorola Technical Brief3 The antenna connector is an SMA 50 ohm connection. The reset switch can be activated to re-initialize the entire system. Three buttons are provided for embedded applications—Functions 1, 2, and 3. Four status LEDs are provided: •One application-specific LED •24 MHz/32 kHz •RX/TX •Power on 3 Environmental This section contains system level environmental information: •Storage temperature (degrees centigrade): —Min. -40 —Max +125 •Operating temperature (degrees centigrade): —Min. 0 —Max +85 4 Mechanical This section contains system level mechanical information: •Length: 75 mm •Width: 50 mm •Height (PCB with components): 20 mm •Layout, FR4, 4 layer: 1 mm 5 Electrical This section contains electrical information: •Input power supply requirements: 3.5-6.5 VDC •Audio input: 65m Vpp •Audio output: 1.6 Vpp, modular jack 4/4 connector The following table shows the current consumption measurements of the circuits of the MC72000 Bluetooth Baseband Controller and Tranceiver IC. 4MC72000 Development Kit for the Bluetooth Platform Solution from Motorola Technical Brief MOTOROLA Interfaces Note: The table contains typical values. 6 Interfaces The development kit features RS232 and UART interfaces: •RS232 interface: Programmable baud rate from 1200 to 921 Kbit. •UART interface: 5-pin header with RxD, CTS, RTS, and GND, 3.3 V signaling, programmable baud rate from 1200 to 921 Kbit, HCI UART transport layer. Note: The UART and RS232 interfaces cannot operate simultaneously. 7 Antenna The development kit contains an SMA 50 Ohm antenna connector. 8 Development Tools The development kit includes the following software tools: •HCI Terminal: This allows you to interact with your Bluetooth hardware. The interface is similar to that of an AT Terminal application when communicating with a modem. You can send HCI commands from a computer to a Bluetooth device, and receive HCI responses from a Bluetooth device. The HCI Terminal allows you to get hands-on experience with the HCI or test your own hardware. •Configuration Manager: This allows you to handle the development kit file system. You can download firmware patches and set up a number of baseband and radio parameters to exercise the board. All parameters will be restorable and default settings will be stored au…

Text truncated - open the document above for the full version.

EMC Measurement/Technical Report 4_Digi_0902_ERF_FCCa on 7 Layers AG Borsigstr. 11 40880 Ratingen Germany Note: The following test results relate only to the devices specified in this document. This report shall not be reproduced in parts without the written approval of the testing laboratory. Motorola Bluetooth ™ Development Kit BTDVK 110 Registergericht - registered in: Düsseldorf, HRB 44096 Aufsichtratsvorsitzende - Chairman of the Supervisory Board: Dr. Sabine Grobecker Vorstand - Board of Directors: Dr. Wolfgang Dahm Dr. Hans-Jürgen Meckelburg 7 layers AG, Borsigstrasse 11 40880 Ratingen, Germany Phone: +49 (0) 2102 749 0 Fax: +49 (0) 2102 749 350 http://www.7Layers.com Report Reference: TTI-P-G 178/99TTI-P-G 178/99 Table of Contents 0. Summary 0.1 Technical Report Summary 0.2 Measurement Summary 1. Administrative Data 1.1 Testing Laboratory 1.2 Project Data 1.3 Applicant Data 1.4 Manufacturer Data 3. Testobject Data 3.1 General EUT Description 3.2 EUT Main Components 3.3 Ancillary Equipment 3.4 EUT Setups 3.5 Operating Modes 4. Measurement Results Conducted Emissions Occupied Bandwidth Peak Power Output Spurious RF Conducted Emissions 5. Testequipment 6. Foto Report 7. Setup Drawings 3 3 4 6 6 6 6 6 8 8 9 9 9 10 11 - 11 14 17 29 32 34 35 Spurious RF Radiated Emissions 19 2. Product Labeling 2.1 FCC ID Label 2.2 Location of Label on the EUT 7 7 7 Dwell Time Power Density Channel Separation Processing Gain 23 25 27 28 - 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 8. Annex measurement plots25 Processing Gain Measurement5 Pages Pages Page 2 of 59Testreport Reference: 4_Digi_0902_ERF_FCCa 0 Summary 0.1 Technical Report Summary Type of Authorization Certification for an Intentional Radiator (Frequency Hopping Spread Spectrum) Applicable FCC Rules: Prepared in accordance with the requirements of FCC Rules and Regulations as listed in 47 CFR Ch.1 Parts 0 to 19 (10-1-98 Edition). The following subparts are applicable to the results in this test report. Part 2, Subpart J - Equipment Authorization Procedures, Certification Sections Part 15, Subpart C - Intentional Radiators § 15.201 Equipment authorization requirement § 15.207 Conducted limits § 15.209 Radiated emission limits; general requirements § 15.247 Operation within the bands 902-928 MHz, 2400-2483,5 MHZ and 5725-5850 MHz Summary Test Results: The EUT complied with all the applicable FCC rules as listed above. Note: The tests were selected and performed with reference to the FCC Public Notice DA 00- 705, released March 30, 2000 Page 3 of 59 Testreport Reference: 4_Digi_0902_ERF_FCCa 0.2 Measurement Summary § 15.247 (a) (1) (ii)FCC Part 15, Subpart C ANSI C63.41992 The measurement was performed according to Occupied BandwidthOccupied Bandwidth OP-ModeOP-ModeSetupSetupPortPortFinal ResultFinal Result setup 1op-mode 1antenna connectorpassed setup 1op-mode 2antenna connectorpassed setup 1op-mode 3antenna connectorpassed setup 1op-mode 4antenna connectorpassed setup 1op-mode 5antenna connectorpassed § 15.247 (b) (1)FCC Part 15, Subpart C FCC §15.3110-1-1998 The measurement was performed according to Peak Power OutputPeak Power Output OP-ModeOP-ModeSetupSetupPortPortFinal ResultFinal Result setup 1op-mode 1antenna connectorpassed setup 1op-mode 2antenna connectorpassed setup 1op-mode 3antenna connectorpassed setup 1op-mode 4antenna connectorpassed setup 1op-mode 5antenna connectorpassed § 15.247 (c)FCC Part 15, Subpart C FCC §15.3110-1-1998 The measurement was performed according to Spurious RF Conducted EmissionsSpurious RF Conducted Emissions OP-ModeOP-ModeSetupSetupPortPortFinal ResultFinal Result setup 1op-mode 1antenna connectorpassed setup 1op-mode 2antenna connectorpassed setup 1op-mode 3antenna connectorpassed § 15.247 (c), §15.35 (b), § 15.209FCC Part 15, Subpart C ANSI C63.41992 The measurement was performed according to Spurious Radiated EmissionsSpurious Radiated Emissions OP-ModeOP-ModeSetupSetupPortPortFinal ResultFinal Result setup 1op-mode 1enclosurepassed setup 1op-mode 2enclosurepassed setup 1op-mode 3enclosurepassed § 15.247(f)FCC Part 15, Subpart C FCC §15.3110-1-1998 The measurement was performed according to Dwell TimeDwell Time OP-ModeOP-ModeSetupSetupPortPortFinal ResultFinal Result setup 1op-mode 4antenna connectorpassed setup 1op-mode 5antenna connectorpassed § 15.247 (d)FCC Part 15, Subpart C Page 4 of 59 Testreport Reference: 4_Digi_0902_ERF_FCCa FCC §15.3110-1-1998 The measurement was performed according to Power DensityPower Density OP-ModeOP-ModeSetupSetupPortPortFinal ResultFinal Result setup 1op-mode 4antenna connectorpassed setup 1op-mode 5antenna connectorpassed § 15.247 (a) (1)FCC Part 15, Subpart C FCC §15.3110-1-1998 The measurement was performed according to Channel SeparationChannel Separation OP-ModeOP-ModeSetupSetupPortPortFinal ResultFinal Result setup 1op-mode 6antenna connectorpassed § 15.247 (f)FCC Part 15, Subpart C FCC §15.3110-1-1998 The measurement was performed according to Processing GainProcessing Gain OP-ModeOP-ModeSetupSetupPortPortFinal ResultFinal Result setup 2op-mode 7antenna connectorpassed Responsible for Accreditation Scope: Responsible for Test Report: Page 5 of 59Testreport Reference: 4_Digi_0902_ERF_FCCa 1. Administrative Data 1.1 Testing Laboratory Company Name: Address: The test facility is also accredited by the following accreditation organisation: Responsible for Accreditation Scope: 7 Layers AG Borsigstr. 11 40880 Ratingen Germany DAR-Registration no. TTI-P-G 178/99 Dipl.-Ing Bernhard Retka Dipl.-Ing Arndt Stöcker This facility has been fully described in a report submitted to the FCC and accepted in a letter dated February 07, 2000 under the registration number 96716. - Deutscher Akkreditierungs Rat 30.10.02 Dipl.-Ing. Thomas Hoell 11.11.02 31.10.- 06.11.02 Responsible for testing and report Receipt of EUT: Date of Test(s): Date of Report: 1.2 Project Data Digianswer A/S Mr. Tom Ringtved Skalhuse 5 DK-9240 Nibe Denmark please see Applicant data 1.4 Manufacturer Data Company Name: A…

Text truncated - open the document above for the full version.

Registergerichth registered in:Vorstandh Board of Directors:7 layers AG, Borsigstrasse 11 Ratingen HRB 3264Dr. Wolfgang Dahm40880 Ratingen, Germany AufsichtsratsvorsitzendehDr. Hans-Jürgen MeckelburgPhone: +49 (0) 2102 749 0 Chairman of the Supervisory Board:Fax: +49 (0) 2102 749 350 Dr. Sabine Grobeckerwww.7layers.com Annex Additional declaration part according FCC 15.247 for Bluetooth TM Devices Version: 2002-06-01 Annex - Additional declaration part according FCC 15.247 for Bluetooth devices Page 2 of 5 pages 1 Output power and channel separation of a Bluetooth device in the different operating modes: The different operating modes (data-mode, acquisition-mode) of a Bluetooth device don’t influence the output power and the channel spacing. There is only one transmitter which is driven by identical input parameters concerning these two parameters. Only a different hopping sequence will be used. For this reason the check of these RF parameters in one op-mode is sufficient. 2 Frequency range of a Bluetooth device: Hereby we declare that the maximum frequency of this device is: 2402 – 2480 MHz. This is according the Bluetooth Core Specification (+ critical errata) for devices which will be operated in the USA. This was checked during the Bluetooth Qualification tests (Test Case: TRM/CA/04-E). Other frequency ranges ( e.g. for Spain, France, Japan) which are allowed according the Core Specification are not supported by this device. 3 Co-ordination of the hopping sequence in data mode to avoid simultaneous occupancy by multiple transmitters: Bluetooth units which want to communicate with other units must be organised in a structure called piconet. This piconet consist of max. 8 Bluetooth units. One unit is the master the other seven are the slaves. The master co-ordinates frequency occupation in this piconet for all units. As the master hop sequence is derived from its BD address which is unique for each Bluetooth device, additional masters intending to establish new piconets will always use different hop sequences. 4 Example of a hopping sequence in data mode: Example of a 79 hopping sequence in data mode: 40, 21, 44, 23, 42, 53, 46, 55, 48, 33, 52, 35, 50, 65, 54, 67, 56, 37, 60, 39, 58, 69, 62, 71, 64, 25, 68, 27, 66, 57, 70, 59, 72, 29, 76, 31, 74, 61, 78, 63, 01, 41, 05, 43, 03, 73, 07, 75, 09, 45, 13, 47, 11, 77, 15, 00, 64, 49, 66, 53, 68, 02, 70, 06, 01, 51, 03, 55, 05, 04 Annex - Additional declaration part according FCC 15.247 for Bluetooth devices Page 3 of 5 pages 5 Equally average use of frequencies in data mode and behaviour for short transmissions: The generation of the hopping sequence in connection mode depends essentially on two input values: 1. LAP/UAP of the master of the connection 2. Internal master clock The LAP (lower address part) are the 24 LSB’s of the 48 BD_ADDRESS. The BD_ADDRESS is an unambiguous number of every Bluetooth unit. The UAP (upper address part) are the 24 MSB’s of the 48 BD_ADDRESS. The internal clock of a Bluetooth unit is derived from a free running clock which is never adjusted and is never turned off. For synchronisation with other units only offset are used. It has no relation to the time of the day. Its resolution is at least half the RX/TX slot length of 312.5 μs. The clock has a cycle of about one day (23h30). In most case it is implemented as 28 bit counter. For the deriving of the hopping sequence the entire LAP (24 bits), 4 LSB’s (4 bits) (Input 1) and the 27 MSB’s of the clock (Input 2) are used. With this input values different mathematical procedures (permutations, additions, XOR- operations) are performed to generate the sequence. This will be done at the beginning of every new transmission. Regarding short transmissions the Bluetooth system has the following behaviour: The first connection between the two devices is established, a hopping sequence was generated. For transmitting the wanted data the complete hopping sequence was not used. The connection ended. The second connection will be established. A new hopping sequence is generated. Due to the fact that the Bluetooth clock has a different value, because the period between the two transmission is longer (and it cannot be shorter) than the minimum resolution of the clock (312.5 μs). The hopping sequence will always differ from the first one. 6 Receiver input bandwidth and behaviour for repeated single or multiple packets: The input bandwidth of the receiver is 1 MHz. In every connection one Bluetooth device is the master and the other one is the slave. The master determines the hopping sequence (see chapter 5). The slave follows this sequence. Both devices shift between RX and TX time slot according to the clock of the master. Additionally the type of connection (e.g. single or multislot packet) is set up at the beginning of the connection. The master adapts its hopping frequency and its TX/RX timing according to the packet type of the connection. Also the slave of the connection will use these settings. Repeating of a packet has no influence on the hopping sequence. The hopping sequence generated by the master of the connection will be followed in any case. That means, a repeated packet will not be send on the same frequency, it is send on the next frequency of the hopping sequence. Annex - Additional declaration part according FCC 15.247 for Bluetooth devices Page 4 of 5 pages 7 Dwell time in data mode The dwell time of 0.3797s within a 30 second period in data mode is independent from the packet type (packet length). The calculation for a 30 second period is a follows: Dwell time = time slot length * hop rate / number of hopping channels *30s Example for a DH1 packet (with a maximum length of one time slot) Dwell time = 625 μs * 1600 1/s / 79 * 30s = 0.3797s (in a 30s period) For multislot packet the hopping is reduced according to the length of the packet. Example for a DH5 packet (with a maximum length of five time slots) Dwell time = 5 * 625 μs * 1600 * 1/5 *1/s / 79 * 30s = …

Text truncated - open the document above for the full version.

1 Marianne Bosley From: Ringtved Tom-TOMRIN1 [[email protected]] Sent: Monday, December 02, 2002 5:21 AM To: '[email protected]' Cc: [email protected] Subject: RE: Metrak #13094 FCC ID:O2OBTDVK110 4_Digi_0902_ERF_FC Cb_.PDF Hi Marianne 1) class B - test report attached 2) thanx for this info. It makes it much easier for us for coming projects. regards - Tom -------------------------------------------------------- Tom Ringtved Type appr./Cert. Manager Digianswer A/S - A Motorola Company Skalhuse 5 Phone : +45 96710000 DK-9240 Nibe Direct: +45 70241425 Denmark http://www.digianswer.com e-mail: [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: 1. december 2002 03:52 To: [email protected] Cc: [email protected] Subject: Metrak #13094 FCC ID:O2OBTDVK110 Hello Mr. Ringtved: The technical review for your project has been completed. There was one technical request (#1) and one FYI for you for the next project (#2). I know that you said in your first email that the 15B report was forthcoming, so once it comes we're probably ready to grant. Please clarify whether it will be Class A verification, DOC, or Class B certification. 1. The EUT has a serial port, thus, it is also a pc peripheral. Has Class A verification of the peripheral portion of the EUT been obtained? Or DoC? Or, is Class B certification sought? If so, please submit the required test report. 2. FYI - pursuant to the newest Part 15.247 requirements, a Bluetooth device is no longer considered a hybrid transmitter when operating in modes of operation that employ few than 75 hopping channels. This minimum number of hopping channels has been reduced to 15, thus, a Bluetooth device meets the definition of a Frequency Hopping Spread Spectrum system in all modes of operation. As a result, it is no longer necessary to submit power spectral 2 density or processing gain data for these devices. If you have any questions, please just let me know. Have a good day. Regards, Marianne

Note : This annex is only valid in combination with the above mentioned test report. The following results relate only to the devices specified in that report. This annex shall not be reproduced in parts without the written approval of the testing laboratory. Annex to Test Report 4_DIGI_0902_ERF_FCCa Processing gain Measurement for Motorola Bluetooth ™ Development Kit BTDVK110 Test Laboratory: 7 layers AG Borsigstrasse 11 D-40880 Ratingen Germany Annex to test report 4_DIGI_0902_ERF_FCCa Page 2 of 5 pages Introduction This report describes the results of the processing gain measurement for the Motorola Bluetooth Development Kit BTDVK110 using the FCC CW jamming margin method. Requirement Hybrid systems that employ a combination of both direct sequence and frequency hopping modulation techniques shall achieve a processing gain of at least 17 dB from the combined techniques. Modification of measurement method Despreading is accomplished by correlating the received bit stream with the bit pattern of the access code. Then with the value of the correlator output will be decided if the access code is valid or not. That means if the access code is not valid a “bit error” occurs for the Bluetooth device. For this reason in CW jamming margin method the ratio of invalid access codes (IACR) is used instead of the BER. Another reason to use this criteria is the fact, that the Bluetooth technology uses the access code to find the correct sampling point. That means if the access code cannot be found, all other bits in the transmission cannot be sampled successfully. System loss In the formula to calculate the processing gain the term system loss appears. In Bluetooth there are two major causes for the system loss: 1. The non optimal sampling time. The CW jamming method assumes that the optimal sampling time as determined before, in fact, as described above, will be determined via the access code. 2. Loss due to attenuation in the RF part. Although these two points produce a system loss which will be much greater than 2 dB, we took that value for the calculation, because this is the maximum which will be accepted by the FCC. Annex to test report 4_DIGI_0902_ERF_FCCa Page 3 of 5 pages Measurement Set-up To measure the IACR the following test set-up was used: 7 24 10 5 RF In/Out Step Attenuator High Pass Signal Generator RF Switch 1 6 dBCoupler 6 dBCouplerSignaling device 6 8 912 13 Device under test Spectrum Analyser Noise Source PowerAmplifier FixedAttenuator (approx. 20 dB) 11 RF block diagram Note: For detailed information about the equipment please see test equipment li…

Text truncated - open the document above for the full version.