Test Report 2

FCC ID: S9E-RNGRBTWFR

Test Report

Download: PDF

FCCID_667065

Northwest
Revision History
EMC Revision 05/05/03

Revision
Description Date Page Number
Number

00 None

Report No. TRPO0022.1 3/28

Northwest
Product Description
EMC Revision 10/3/03

Party Requesting the Test
Company Name: Tripod Data Systems, Inc.
Address: 345 SW Avery Ave
City, State, Zip: Corvallis, OR 97333
Test Requested By: Bob Grant
Model: WMBGMR01 in Recon (Bluetooth Radio Portion)
First Date of Test: May 08, 2006
Last Date of Test: May 18, 2006
Receipt Date of Samples: May 04, 2006
Equipment Design Stage: Pre-Production
Equipment Condition: No visual damage.

Information Provided by the Party Requesting the Test

Clocks/Oscillators: Not provided.
I/O Ports: Serial, USB, Power

Functional Description of the EUT (Equipment Under Test):
The EUT is the Bluetooth portion of a WiFi – Bluetooth combo radio module hosted in the Recon, a
handheld data collector.

Client Justification for EUT Selection:
The product is a representative production sample.

Client Justification for Test Selection:
These test satisfy the FCC 15.247 requirements for the Bluetooth portion of the combo radio.

Report No. TRPO0022.1 7/28

Northwest
Configurations
EMC Revision 9/21/05

CONFIGURATION 1 TRPO0022

Software/Firmware Running during test
Description Version
BTCirroTest Unknown

EUT
Description Manufacturer Model/Part Number Serial Number
EUT - Bluetooth radio Tripod Data Systems, Inc. WMBGMR01 Unknown
EUT - 802.11(b/g) radio Tripod Data Systems, Inc. WMBGMR01 Unknown

Peripherals in test setup boundary
Description Manufacturer Model/Part Number Serial Number
Pocket PC Handheld Data
Tripod Data Systems, Inc. Recon Compliance Unit 2
Collector
DC Power Supply Cincon Electronics Co. TR30R050 N/A
GPS Trimble Unknown Unknown

Cables
Cable Type Shield Length (m) Ferrite Connection 1 Connection 2
DC Leads No 1.8 Yes Pocket PC Handheld Data Collector AC Power
Serial Yes 1.5 Yes Pocket PC Handheld Data Collector GPS
USB Yes 1.8 Yes Pocket PC Handheld Data Collector Unterminated
PA = Cable is permanently attached to the device. Shielding and/or presence of ferrite may be unknown.

Report No. TRPO0022.1 8/28

Northwest
Modifications
EMC Revision 4/28/03

Equipment modifications
Item Date Test Modification Note Disposition of EUT
Spurious Tested as No EMI suppression EUT remained at
1 5/08/2006 Radiated delivered to devices were added or Northwest EMC
Emissions Test Station. modified during this test. following the test.
AC
Tested as No EMI suppression
Powerline Scheduled testing
2 5/18/2006 delivered to devices were added or
Conducted was completed.
Test Station. modified during this test.
Emissions

Report No. TRPO0022.1 9/28

$I:\TRPO\TRPO0022\FCC 15.247 Bluetooth Report\BLUETOOTH APPROVALS - FCC Procedure 2-15-02.doc BLUETOOTH APPROVALS FCC Procedure Received from Joe Dichoso on 2-15-02 The following exhibit indicates the FCC Spread Spectrum requirements in Section 15.247 for devices meeting the Bluetooth Specifications in the 2.4 GHz band as of February 2001 operating in the USA. The purpose of this exhibit is to help expedite the approval process for Bluetooth devices. This exhibit provides items that vary for each device and also provides a list of items that are common to Bluetooth devices that explains the remaining requirements. The list of common items can be submitted for each application for equipment authorization. This exhibit only specifies requirements in Section 15.247, requirements in other rule Sections for intentional radiators such as in Section 15.203 or 15.207 must be also be addressed. A Bluetooth device is a FHSS transmitter in the data mode and applies as a Hybrid spread spectrum device in the acquisition mode. For each individual device, the following items, 1-7 will vary from one device to another and must be submitted. 1) The occupied bandwidth in Section 15.247(a)(1)(ii). 2) Conducted output power specified in Section 15.247(b)(1). 3) EIRP limit in Section 15.247(b)(3). 4) RF safety requirement in Section 15.247(b)(4) 5) Spurious emission limits in Section 15.247(c). 6) Processing gain and requirements for Hybrids in Section 15.247(f) in the acquisition mode. 7) Power spectral density requirement in Section 15.247(f) in the acquisition mode. For all devices, the following items, 1-12, are common to all Bluetooth devices and will not vary from one device to another. This list can be copied into the filing. 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 RF parameters in one op-mode is sufficient. 2 Frequency range of a Bluetooth device: The maximum frequency of the device is: 2402 – 2480 MHz. This is according the Bluetooth Core Specification V 1.0B (+ critical errata) for devices which will be operated in the USA. Other frequency ranges ( e.g. for Spain, France, Japan) which are allowed according the Core Specification must not be supported by the 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 organized 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 it’s BD address which is unique for every Bluetooth device, additional masters intending to establish new piconets will always use different hop sequences. 4 Example of a hopping sequence in data mode: Report No. TRPO0022.1 25/28$

$I:\TRPO\TRPO0022\FCC 15.247 Bluetooth Report\BLUETOOTH APPROVALS - FCC Procedure 2-15-02.doc 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 5 Equally average use of frequencies in data mode and 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 synchronization with other units, only the offsets 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 behavior: The first connection between the two devices is established, a hopping sequence is generated. For transmitting the wanted data, the complete hopping sequence is not used and the connection ends. 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, synchronization and 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 multi-slot packet) is set up at the beginning of the connection. The master adapts its hopping frequency and its TX/RX timing is according to the packet type of the connection. Also, the slave of the connection uses 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 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) Report No. TRPO0022.1 26/28$

$I:\TRPO\TRPO0022\FCC 15.247 Bluetooth Report\BLUETOOTH APPROVALS - FCC Procedure 2-15-02.doc For multi-slot 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 = 0.3797s (in a 30s period) This is according the Bluetooth Core Specification V 1.0B (+ critical errata) for all Bluetooth devices. Therefore, all Bluetooth devices comply with the FCC dwell time requirement in the data mode. This was checked during the Bluetooth Qualification tests. The Dwell time in hybrid mode is approximately 2.6 mS (in a 12.8s period) 8 Channel Separation in hybrid mode The nominal channel spacing of the Bluetooth system is 1Mhz independent of the operating mode. The maximum “initial carrier frequency tolerance” which is allowed for Bluetooth is fcenter = 75 kHz. This was checked during the Bluetooth Qualification tests (Test Case: TRM/CA/07-E) for three frequencies (2402, 2441, 2480 MHz). 9 Derivation and examples for a hopping sequence in hybrid mode For the generation of the inquiry and page hop sequences the same procedures as described for the data mode are used (see item 5), but this time with different input vectors: **For the inquiry hop sequence, a predefined fixed address is always used. This results in the same 32 frequencies used by all devices doing an inquiry but every time with a different start frequency and phase in this sequence. **For the page hop sequence, the device address of the paged unit is used as the input vector. This results in the use of a subset of 32 frequencies which is specific for that initial state of the connection establishment between the two units. A page to different devices would result in a different subset of 32 frequencies. So it is ensured that also in hybrid mode, the frequency is used equally on average. Example of a hopping sequence in inquiry mode: 48, 50, 09, 13, 52, 54,41, 45, 56, 58, 11, 15, 60, 62, 43, 47, 00, 02, 64, 68, 04, 06, 17, 21, 08, 10, 66, 70, 12, 14, 19, 23 Example of a hopping sequence in paging mode: 08, 57, 68, 70, 51, 02, 42, 40, 04, 61, 44, 46, 63, 14, 50, 48, 16, 65, 52, 54, 67, 18, 58, 56, 20, 53, 60, 62, 55, 06, 66, 64 10 Receiver input bandwidth and synchronization in hybrid mode: The receiver input bandwidth is the same as in the data mode (1 MHz). When two Bluetooth devices establish contact for the first time, one device sends an inquiry access code and the other device is scanning for this inquiry access code. If two devices have been connected previously and want to start a new transmission, a similar procedure takes place. The only difference is, instead of the inquiry access code, a special access code, derived from the BD_ADDRESS of the paged device will be, will be sent by the master of this connection. Due to the fact that both units have been connected before (in the inquiry procedure) the paging unit has timing and frequency information about the page scan of the paged unit. For this reason the time to establish the connection is reduced. 11 Spread rate / data rate of the direct sequence signal The Spread rate / Data rate in inquiry and paging mode can be defined via the access code. The access code is the only criterion for the system to check if there is a valid transmission or not. If you regard the presence of a valid access code as one bit of information, and compare it with the length of the access code of 68 bits, the Spread rate / Data rate will be 68/1. 12 Spurious emission in hybrid mode Report No. TRPO0022.1 27/28$

$I:\TRPO\TRPO0022\FCC 15.247 Bluetooth Report\BLUETOOTH APPROVALS - FCC Procedure 2-15-02.doc The Dwell in hybrid mode is shorter than in data mode. For this reason the spurious emissions average level in data mode is worst case. The spurious emissions peak level is the same for both modes. Report No. TRPO0022.1 28/28$

Document Created: 2006-06-06 13:18:04
Document Modified: 2006-06-06 13:18:04