MICROCHIP TECHNOLOGY RN52 Class 2 Bluetooth Module User Manual RN 52 Bluetooth Audio Module Data Sheet

Microchip Technology Inc. Class 2 Bluetooth Module RN 52 Bluetooth Audio Module Data Sheet

Users Manual

www.rovingnetworks.com Version 1.1 3/19/13 page 1Advanced InformationRN52-DSRN52 Bluetooth Audio ModuleFeatures:• Fully qualified Bluetooth® version 3.0 module, fully compatible with Bluetooth version 2.1+EDR, 1.2, and 1.1• Software configurable through commands over UART console interface• Dedicated GPIO pins enable MCUs to access control and status functions efficiently• Postage-stamp-sized form factor, 13.5 x 26.0 x 2.7 mm• Embedded Bluetooth stack profiles: A2DP, AVRCP, HFP/HSP, and SPP• Dual-channel, differential audio input and output for highest quality audio• Supports iAP profile to discover iOS devices and apps (requires a special firmware build)• Integrated amplifier for driving 16 Ω speakers• UART (SPP) data connection interfaces• External audio CODECs supported via S/PDIF and I2S interface • Castellated SMT pads for easy and reliable PCB mounting• Environmentally friendly, RoHS compliant• Certifications: FCC, ICS, CE• Bluetooth SIG certified Applications:• High-quality, 2-channel audio streaming• Wireless stereo headsets• Automotive hands free audio• Wireless audio docking station for smartphones• Wireless speakers• Intercom push-to-talk audio connection• Remote control for media player• Medical devices• Computer accessoriesRN52 Block Diagram:PCB AntennaBluetooth 3.0RF BasebandRN52UARTUSBI2SS/PDIF11 GPIO Pins1 AIO16-Bit RISC MCUAudio DSP16-Bit StereoCODEC16-MBit Flash2 LEDsMICMICSpeakerSpeaker
www.rovingnetworks.com Version 1.1 3/19/13 page 2Advanced InformationRN52-DS1.0 DEVICE OVERVIEWRoving Network’s RN52 Bluetooth audio module pro-vides a highly integrated solution for delivering high-quality stereo audio in a small form factor. It combinesa class 2 Bluetooth radio with an embedded DSP pro-cessor. The module is programmed and controlled witha simple ASCII command language. The RN52 module complies with Bluetooth specifica-tion version 3.0. It integrates RF, a baseband controller,etc., making it a complete Bluetooth subsystem. TheRN52 supports a variety of profiles including HSP/HFP,A2DP, AVRCP, SPP, and iAP. It provides a UART inter-face, several user programmable I/O pins, stereospeaker outputs, microphone inputs, and a USB port. Table 1-1 provides the general specifications for themodule. Tab l e 1 - 2 and Table 1-3 provide the module’sweight, dimensions, and electrical characteristics.Figure 1-1 shows the module’s dimensions andFigure 1-2 shows recommended landing pattern andlayout. TABLE 1-1: GENERAL SPECIFICATIONSSpecification DescriptionStandard Bluetooth 3.0, class 2Frequency Band 2.4 ~ 2.48 GHzModulation Method GFSK, PI/4-DQPSK, 8 DPSKMaximum Data Rate 3 Mbps RF Input Impedance 50 ohmsInterface UART, GPIO, AIO, USB, SPI, speaker, microphoneOperation Range 10 meters (33 feet)Sensitivity -85 dBm at 0.1 % BERRF TX Power 4 dBmTABLE 1-2: WEIGHT & DIMENSIONSSpecification DescriptionDimensions 26.0 mm x 13.5 mm x 2.7 mmWeight 1.2 gTABLE 1-3: ELECTRICAL CHARACTERISTICSSpecification DescriptionSupply Voltage 3.0 ~ 3.6 V DCWorking current Depends on profiles, 30 mA typical Standby current (disconnected) < 0.5 mATemperature -40ºC to +85ºCESD JESD22-A224 class 0 productHumidity 10% ~ 90% non-condensing
www.rovingnetworks.com Version 1.1 3/19/13 page 3Advanced InformationRN52-DSFIGURE 1-1: MODULE DIMENSIONSFIGURE 1-2: RECOMMENDED PCB FOOTPRINT0.002.550.853.754.956.157.358.559.7510.9512.6513.500.026.00PCB Outline: +/- 0.13 mmPCB Thickness: +/- 0.100 mmTolerances:(Top View)Dimensions are in millimeters21.20 21.4020.0018.8017.6016.4015.2014.0012.8011.6010.409.208.006.805.604.403.202.00(Side View)26.0021.400.700.000.000.802.700.7512.750.8mm1.6mm0.80mmDimensions are in millimeters0.002.550.853.754.956.157.358.559.7510.9512.6513.500.026.0021.20 21.4020.0018.8017.6016.4015.2014.0012.8011.6010.409.208.006.805.604.403.202.003.254.656.057.458.8510.2520.70Ground Pads0.8 x 1.0 mmHost Ground Plane Edge(See Mounting Details)(Top View)
www.rovingnetworks.com Version 1.1 3/19/13 page 4Advanced InformationRN52-DSFigure 1-3 shows the pinout and Ta b l e 1 - 4 describesthe module’s pins.FIGURE 1-3: PIN DIAGRAMRN52Top ViewGNDGPIO7GPIO6PWRENVDDPCM_INPCM_OUTPCM_SYNCPCM_CLKGNDGNDGPIO3GPIO2AICO0GPIO4GPIO5GPIO12GPIO13GPIO11GPIO10GPIO9USBD-USBD+UART_RTSUART_CTSUART_TXUART_RXGNDSPKR_L+SPKR_R+SPKR_L-SPKR_R-AGNDMIC_R-MIC_L-MIC_R+MIC_L+MIC_BIASLED0LED1SPI_MOSISPI_SCKSPI_MISOSPI_SSGNDGNDGNDGNDGNDGND1234567891011121314151617444342414039383736353433323130292818192021222324252627504948474645TABLE 1-4: PIN DESCRIPTION (PART 1 OF 3) Note 1Pin Symbol I/O Type Description Direction Default1GND Ground. Ground.2GPIO3 Bidirectional with program-mable strength internal pull-up/down.This pin enters device firmware update (DFU) mode at bootup if a USB device powers VBUS. GPIO3 requires 47 kΩ to ground and 22 kΩ to the USB VBUS signal if the USB VBUS is supply-ing power to the main board.Input Low3GPIO2 Bidirectional with program-mable strength internal pull-up/down.Reserved, event register. Toggles from high to low for 100 ms to indicate that the module’s state has changed. A microcontroller can enter com-mand mode and poll the state register using the Q action command.Output High4AIO0 Bidirectional. Analog programmable input/output line. I/O5GPIO4 Bidirectional with program-mable strength internal pull-up/down.Factory reset mode. To reset the module to the factory defaults, GPIO4 should be high on power-up and then toggle low, high, low, high with a 1 second wait between the transitions.Input Low
www.rovingnetworks.com Version 1.1 3/19/13 page 5Advanced InformationRN52-DS6GPIO5 Bidirectional with program-mable strength internal pull-up/down.Programmable I/O. I/O High7GPIO12 Bidirectional with program-mable strength internal pull-up/down.Programmable I/O. I/O High8GPIO13 Bidirectional with program-mable strength internal pull-up/down.Programmable I/O. I/O High9GPIO11 Bidirectional with program-mable strength internal pull-up/down.Programmable I/O. I/O High10 GPIO10 Bidirectional with program-mable strength internal pull-up/down.Programmable I/O. I/O High11 GPIO9 Bidirectional with program-mable strength internal pull-up/down.When you drive this signal low, the module’s UART goes into command mode. If this signal floats high, the UART is in data mode. Reserved. Not available for use at runtime.Input High12 USBD- Bidirectional. USB data minus. I/O13 USBD+ Bidirectional. USB data plus with selectable internal 1.5-Kohm pull-up resistor.I/O14 UART_RTS CMOS output, tri-state, with weak internal pull-up.UART request to send active low. Output15 UART_CTS CMOS input with weak internal pull-down.UART clear to send active low. Input16 UART_TX CMOS output, tri-state, with weak internal pull-up.UART data output. Output17 UART_RX CMOS input with weak internal pull-down.UART data input. Input18 GND Ground. Ground.19 GPIO7 Bidirectional with program-mable strength internal pull-up/down.Driving this pin low sets the UART baud rate to 9,600. By default the pin is high with a baud rate of 115,200.I/O High20 GPIO6 Bidirectional with program-mable strength internal pull-up/down.Programmable I/O. I/O High21 PWREN Analog. Pull high to power up RN52.22 VDD 3.3-V power input. 3.3v power input.23 PCM_IN CMOS input, with weak internal pull down.Synchronous data input, configurable for SPDIF_IN or SD_IN (I2S).Input24 PCM_OUT CMOS input, with weak internal pull down.Synchronous data input, configurable for SPDIF_OUT or SD_OUT (I2S).Input25 PCM_SYNC Bidirectional with weak internal pull down.Synchronous data sync; WS (I2S). I/O26 PCM_CLK CMOS input, with weak internal pull down.Synchronous data clock; SCK (I2S). InputTABLE 1-4: PIN DESCRIPTION (PART 2 OF 3) Note 1Pin Symbol I/O Type Description Direction Default
www.rovingnetworks.com Version 1.1 3/19/13 page 6Advanced InformationRN52-DS1.1 Audio Interface Circuit DescriptionThe RN52 audio interface circuit consists of:• Stereo audio CODEC• Dual audio inputs and dual outputs• Configurable S/PDIF and I2S interfaceThe audio input circuitry has a dual audio input that canbe configured as single-ended or fully differential andprogrammed for microphone or line input. It has ananalog and digital programmable gain stage so that itcan be optimized for different microphones. SeeFigure 1-4.1.1.1 STEREO AUDIO CODEC INTERFACEThe stereo audio CODEC interface has stereo andmono analog input/output for voice and audio bands. Itsupports the IEC-60958 stereo digital audio bus stan-dards, e.g., S/PDIF and AES3/EBU.The built-in CODEC uses a fully differential architecturein the analog signal path, which results in low noisesensitivity and good power supply rejection while effec-tively doubling the signal amplitude. It operates from a1.5 V single power supply and uses a minimum ofexternal components. See Figure 1-5.27 GND Ground. Ground.28 SPI_SS CMOS input with weak internal pull-up.Chip select for Synchronous Serial Interface active low.Input29 SPI_MISO CMOS output, tri-state, with weak internal pull-down.Serial Peripheral Interface (SPI) output. Output30 SPI_CLK Input with weak internal pull-down.SPI clock. Input31 SPI_MOSI CMOS input, with weak internal pull-down.SPI input. Input32 LED1 Open drain output. Drives an LED. For the RN-52-EK board, this signal drives the red LED.Output33 LED0 Open drain output. Drives an LED. For the RN-52-EK board, this signal drives the blue LED.Output34 MIC_BIAS Analog. Microphone bias. Output35 MIC_L+ Analog. Microphone input positive, left. Output36 MIC_R+ Analog. Microphone input positive, right. Output37 MIC_L- Analog. Microphone input negative, left. Output38 MIC_R- Analog. Microphone input negative, right. Output39 AGND Analog. Ground connection for audio.40 SPK_R- Analog. Speaker output negative (right side). Output41 SPK_L- Analog. Speaker output negative (left side). Output42 SPK_R+ Analog. Speaker output positive (right side). Output43 SPK_L+ Analog. Speaker output positive (left side). Output44 GND Ground. Ground.45 GND Ground. RF ground.46 GND Ground. RF ground.47 GND Ground. RF ground.48 GND Ground. RF ground.49 GND Ground. RF ground.50 GND Ground. RF ground.Note 1: All GPIO pins default to input with weak pull-down.TABLE 1-4: PIN DESCRIPTION (PART 3 OF 3) Note 1Pin Symbol I/O Type Description Direction Default
www.rovingnetworks.com Version 1.1 3/19/13 page 7Advanced InformationRN52-DSFIGURE 1-4: RN52 AUDIO INTERFACE BLOCK DIAGRAMFIGURE 1-5: STEREO CODEC AUDIO INPUT/OUTPUT STAGESSPK_L+SPK_L-SPK_R+SPK_R-MIC_L+MIC_L-MIC_R+MIC_R-MIC_BIASRN52AudioPAMIC &BiasSystemMainboardS/PDIF & I2SSPK_L+SPK_L-MIC_L+MIC_L-InputAmplierOutputAmplierSPK_R+SPK_R-MIC_R+MIC_R-InputAmplierOutputAmplierΣΔ-ADCΣΔ-ADCLP FilterLP FilterDigitalCircuitryDACDACRN52
www.rovingnetworks.com Version 1.1 3/19/13 page 8Advanced InformationRN52-DS1.1.2 ANALOG-TO-DIGITAL CONVERTER (ADC)The ADC consists of two second-order sigma delta(SD) converters, resulting in two separate channelswith identical functionality. Each ADC supports the fol-lowing sample rates:• 8 kHz• 11.025 kHz• 16 kHz• 22.05 kHz• 24 kHz• 32 kHz• 44.1 kHzThe ADC analog amplifier is a two-stage amplifier. Thefirst stage selects the correct gain for either micro-phone or line input. See Figure 1-6.FIGURE 1-6: ADC ANALOG AMPLIFIER BLOCK DIAGRAM1.1.3 DIGITAL-TO-ANALOG CONVERTER (DAC)The DAC consists of two third-order SD converters,resulting in two separate channels with identical func-tionality. Each DAC supports the following samplerates:• 8 kHz• 11.025 kHz• 16 kHz• 22.05 kHz• 24 kHz• 32 kHz• 44.1 kHz1.1.4 MICROPHONE INPUTThe RN52 audio input is intended for use from 1 μA at94 dB SPL to about 10 μA at 94 dB SPL, which requiresmicrophones with sensitivity between –40 and –60dBV. MIC_BIAS requires a minimum load to maintainregulation. MIC_BIAS maintains regulation within0.199 and 1.229 mA. Therefore, if you use a micro-phone with specifications below these limits, the micro-phone output must be pre-loaded with a large valueresistor to ground.–+–+PNGain 0:7Line Mode/Microphone ModeMicrophone Mode Input Impedance = 6 kΩLine Mode Input Impedance = 6 kΩ to 30 kΩBypass or 24-dB Gain -3 to 18 dB GainPN
www.rovingnetworks.com Version 1.1 3/19/13 page 9Advanced InformationRN52-DS2.0 APPLICATIONSThe following sections provide information on design-ing with the RN52 module, including restoring factorydefaults, using the LED interface, minimizing radiointerference, solder reflow profile, typical application,etc.2.1 Minimizing Radio InterferenceWhen laying out the host PCB for the RN52 module,the areas under the antenna and shielding connectionsshould not have surface traces, ground planes, orexposed via (see Figure 2-1). For optimal radio perfor-mance, the RN52 module’s antenna end should pro-trude at least 31 mm beyond any metal enclosure.Figure 2-2 shows examples of good, bad, and accept-able positioning of the RN52 on the host PCB.FIGURE 2-1: MINIMIZING RADIO INTERFERENCEFIGURE 2-2: PCB EXAMPLE LAYOUT21.4 mm4.6 mm(Top View)Dimensions are in millimetersKeep area around antenna(approximately 31 mm) clearof metallic structures forbest performance31 mm31 mmEdge of Ground PlainRN52RN52RN52 RN52GoodAcceptableAcceptableBad
www.rovingnetworks.com Version 1.1 3/19/13 page 10Advanced InformationRN52-DS2.2 LED InterfaceThe RN52 includes two pads dedicated to driving theLED indicators. The firmware can control both termi-nals, and the battery charger can set LED0. The termi-nals are open-drain outputs; therefore, the LED mustbe connected from a positive supply rail to the pad inseries with a current limiting resistor. You should oper-ate the LED pad (LED0 or LED1 pins) with a pad volt-age below 0.5 V. In this case, the pad can be thought ofas a resistor, RON. The resistance—together with theexternal series resistor—sets the current, ILED, in theLED. The current is also dependent on the externalvoltage, VDD, as shown in Figure 2-3.FIGURE 2-3: LED INTERFACEThe LEDs can be used to indicate the module’s con-nection status. Ta b l e 2 - 1 describes the LED functions. 2.3 Device Firmware UpdatesThe module has a device firmware update (DFU) modein which you use the USB interface to update the firm-ware. ImplementingImplementing the DFU feature isrecommended highly because firmware updates offernew features and enhance the module’s functionality.Follow the reference design shown in Figure 2-7 tosupport this mode.FIGURE 2-4: USB DFU PORT & GPIO3 SCHEMATIC2.4 Restore Factory Defaults with GPIO4You should connect the GPIO4 pin to a switch, jumper,or resistor so it can be accessed. You can use this pinto reset the module to its factory default settings, whichis critical in situations where the module has been mis-configured. To reset the module to the factory defaults,GPIO4 should be high on power-up and then togglelow, high, low, high with a 1 second wait between thetransitions.TABLE 2-1: STATUS LED FUNCTIONSBlue LED Red LED DescriptionFlashing Flashing The RN52 module is discover-able.Off Flashing The module is connected.Flashing Off The module is connectable.VDDLED ForwardVoltage, VFResistor VoltageDrop, VRPad Voltage, VPADRLED|LEDLED0 or LED1RON = 20 ΩNote: A 47 KΩ pull-down resistor (R2 inFigure 2-4) is required on GPIO3 even ifyou do not use the USB for DFU.GND5D+3D-2VBUS1MTAB 6J2VBUS(3.3V)USBD-USBD+47kR222kR1GPIO3 MBR120D110nFC4USB Mini B Connector(JAE DX2R005HN2E700)
www.rovingnetworks.com Version 1.1 3/19/13 page 11Advanced InformationRN52-DS2.5 Solder Reflow ProfileThe lead-free solder reflow temperature and times are:•Temperature—230° C, 60 seconds maximum, peak 245° C maximum•Preheat temperature—165° ± 15° C, 90 to 120 seconds•Time—Single pass, one timeTo reflow solder the module onto a PCB, use an RoHS-compliant solder paste equivalent to NIHON ALMITpaste or OMNIX OM-310 solder paste from Alpha met-als. See Ta b l e 2 - 2 .Figure 2-5 and Figure 2-6 show the solder reflow tem-perature profiles.FIGURE 2-5: SOLDER REFLOW TEMPERATURE PROFILENote: Use no-clean flux and DO NOT waterwashTABLE 2-2: PASTE SOLDER RECOMMENDATIONSManufacturer Alpha Metalshttp://www.alphametals.comNIHON ALMIT Co. LTDhttp://almit.co.jpPart Number OMNIX OM-310 LFM-70W INPMetal Composition SAC305 (96.5% Sn, 3% Ag, 0.5% Cu) 88% Sn, 3.5% Ag, 0.5% Bi, 8% InLiquidus Temperature ~220°C ~215°C
www.rovingnetworks.com Version 1.1 3/19/13 page 12Advanced InformationRN52-DSFIGURE 2-6: SOLDER REFLOW CURVE
www.rovingnetworks.com Version 1.1 3/19/13 page 13Advanced InformationRN52-DS2.6 Typical Application SchematicFigure 2-7 shows a typical application circuit with LDO,stereo audio/microphone PA, USB/UART, AVRCPswitches, and LED0/LED1. FIGURE 2-7: TYPICAL APPLICATION CIRCUIT FOR A2DP AUDIO STREAMING & AVRCP REMOTE CONTROLVBUSVBUSRESET 183V 3OU T 16USBDP 14USBDM 15GND17CBUS210 CBUS121VCCIO 1CBUS311CBUS49CBUS022GND20RI3DCD7DSR6DTR31 CTS8RTS32 RXD2TXD30VCC 19OSCI 27OSCO 28AGND24TEST26GND4THPAD33FT232RQU1GND5D+3D-2VBUS1MTAB 6USB Mini B / CSR UARTJ1123456J4SPI MASTERSPI _MI SOSPI _MOSISPI _SCKSPI _SS3.3VUART_RXUART_TXUART_CTSUART_RTSVin1GND2Vout 3Tab4TC1262- 3.3V U21uFC61uFC7VBUS 3.3V100nFC3100nFC1100nFC2Blue LEDD3Red LEDD2S2Vol DownS3Play / PauseS6NextS1PrevS4Vol UpBTN_VOL UPBTN_VOL DOWNBTN_NEXTBTN_PL AYBTN_PREVI OUS47RR8470R93.3VGND5D+3D-2VBUS1MTAB 6USB Mini B / RSVD USBJ2GPIO4 5GPIO5 6GPIO12 7GPIO13 8GPIO11 9GPIO10 10GPIO9 11USBD- 12USBD+ 13UART_RTS 14UART_CTS 15UART_TX 16PCM _CLK 26SPI _SS28SPI_MISO29SPI_SCK30PCM _IN 23VDD 22L ED033MIC_BIAS34MIC_L+35MIC_R+36MIC_L-37MIC_R-38PCM _OUT 24GPIO7 19PCM _SY NC 25SPI_MOSI31L ED132PWREN 21GPIO6 20UART_RX 17AIO0 4GPIO2 3AGND39SPKR_R-40GND 1GND 18GND 27GND44GPIO3 2SPKR_L-41GND50GND49GND48GND47GND46GND45SPKR_R+42SPKR_L +43M1RN52 ModulePI O7PI O6L ED0L ED1L ED0L ED1VBUSUSBD-USBD+SPI _MI SOSPI _MOSISPI _SCKSPI _SS3.3VSPKR_R-SPKR_L -SPKR_R+SPKR_L +S5Wake3.3VPCM_CL KPCM_SYNCPCM_OUTPCM_INSPKR_R-SPKR_L -SPKR_R+SPKR_L +VBUS47kR222kR1PI O31uFC211uFC221uFC131uFC141uFC122k2R72k2R647nFC847nFC1047nFC1147nFC9MI C_LMI C_R1uFC1822kR1722kR1547kR1122kR1347kR1447kR1047kR1622kR121 23 45 67 89 1011 1213 1415 16J3EXT ConnectorPCM_CL KPCM_SYNCPCM_OUTPCM_I N3.3VIN1+3IN1-2Vo2 9BYPASS4IN2-8IN2+7SHUTDOWN 6GND5VDD 10Vo1 1PAD11U4TPA6112100uFC23100uFC20100uFC17100uFC1910uFC15100nFC16MBR120D110nFC4VBUSPI O93.3VBTN_VOLDOWNBTN_PREVI OUSBTN_PLAYBTN_NEXTBTN_VOLUPPI O2PI O6PI O712J8MI CL12J6MI CRMI C_LMI C_R12J11BatteryVBUS123456789101112J101 23 45 67 89 10J7PI O4PWRENPWRENSPKR_R-SPKR_L -SPKR_R+SPKR_L +MI C_BI ASMI C_L +MI C_R+MI C_L -MI C_R-MI C_L +MI C_R+MI C_L -MI C_R-MI C_BI ASAI O0UART_RXUART_TXUART_CTSUART_RTSUSBD-USBD+BTN_VOL UPBTN_VOL DOWNBTN_NEXTBTN_PLAYBTN_PREVI OUSPI O3PI O9PI O2PI O4AI O0MI C_L +MI C_R+MI C_L -MI C_R-MI C_BI AS35421J5Mic35421J9Headphones2k2R70UART_RXUART_TXDeviceFirmwareUpdate
www.rovingnetworks.com Version 1.1 3/19/13 page 14Advanced InformationRN52-DS3.0 REGULATORY APPROVALThis section outlines the regulatory information for theRN52 module for the following countries:• United States• Canada• Europe• Australia• New Zealand3.1 United StatesThe RN52 module has received Federal Communica-tions Commission (FCC) CFR47 Telecommunications,Part 15 Subpart C “Intentional Radiators” modularapproval in accordance with Part 15.212 ModularTransmitter approval. Modular approval allows the enduser to integrate the RN52 module into a finished prod-uct without obtaining subsequent and separate FCCapprovals for intentional radiation, provided nochanges or modifications are made to the module cir-cuitry. Changes or modifications could void the user’sauthority to operate the equipment. The end user mustcomply with all of the instructions provided by theGrantee, which indicate installation and/or operatingconditions necessary for compliance.The finished product is required to comply with all appli-cable FCC equipment authorizations regulations,requirements and equipment functions not associatedwith the transmitter module portion. For example, com-pliance must be demonstrated to regulations for othertransmitter components within the host product; torequirements for unintentional radiators (Part 15 Sub-part B “Unintentional Radiators”), such as digitaldevices, computer peripherals, radio receivers, etc.;and to additional authorization requirements for thenon-transmitter functions on the transmitter module(i.e., Verification, or Declaration of Conformity) (e.g.,transmitter modules may also contain digital logic func-tions) as appropriate.3.1.1 LABELING AND USER INFORMATION REQUIREMENTSThe RN52 module has been labeled with its own FCCID number, and if the FCC ID is not visible when themodule is installed inside another device, then the out-side of the finished product into which the module isinstalled must also display a label referring to theenclosed module. This exterior label can use wordingas follows:A user’s manual for the product should include the fol-lowing statement:Additional information on labeling and user informationrequirements for Part 15 devices can be found in KDBPublication 784748 available at the FCC Office of Engi-neering and Technology (OET) Laboratory DivisionKnowledge Database (KDB) http://apps.fcc.gov/oetcf/kdb/index.cfm. 3.1.2 RF EXPOSUREAll transmitters regulated by FCC must comply with RFexposure requirements. OET Bulletin 65, EvaluatingCompliance with FCC Guidelines for Human ExposureContains Transmitter Module FCC ID: T9J-RN52orContains FCC ID: T9J-RN52This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operationThis equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equip-ment generates, uses and can radiate radio fre-quency energy, and if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the follow-ing measures:• Reorient or relocate the receiving antenna.• Increase the separation between the equipment and receiver.• Connect the equipment into an outlet on a circuit different from that to which the receiver is con-nected.• Consult the dealer or an experienced radio/TV technician for help.
www.rovingnetworks.com Version 1.1 3/19/13 page 15Advanced InformationRN52-DSto Radio Frequency Electromagnetic Fields, providesassistance in determining whether proposed or existingtransmitting facilities, operations or devices complywith limits for human exposure to Radio Frequency(RF) fields adopted by the Federal CommunicationsCommission (FCC). The bulletin offers guidelines andsuggestions for evaluating compliance.If appropriate, compliance with exposure guidelines formobile and unlicensed devices can be accomplishedby the use of warning labels and by providing userswith information concerning minimum separation dis-tances from transmitting structures and proper installa-tion of antennas.The following statement must be included as a CAU-TION statement in manuals and OEM products to alertusers of FCC RF exposure compliance:If the RN52 module is used in a portable application(i.e., the antenna is less than 20 cm from persons dur-ing operation), the integrator is responsible for perform-ing Specific Absorption Rate (SAR) testing inaccordance with FCC rules 2.1091.3.1.3 HELPFUL WEB SITESFederal Communications Commission (FCC):http://www.fcc.govFCC Office of Engineering and Technology (OET) Lab-oratory Division Knowledge Database (KDB):http://apps.fcc.gov/oetcf/kdb/index.cfm 3.2 CanadaThe RN52 module has been certified for use in Canadaunder Industry Canada (IC) Radio Standards Specifica-tion (RSS) RSS-210 and RSSGen. Modular approvalpermits the installation of a module in a host devicewithout the need to recertify the device.3.2.1 LABELING AND USER INFORMATION REQUIREMENTSLabeling Requirements for the Host Device (from Sec-tion 3.2.1, RSS-Gen, Issue 3, December 2010): Thehost device shall be properly labeled to identify themodule within the host device.The Industry Canada certification label of a moduleshall be clearly visible at all times when installed in thehost device, otherwise the host device must be labeledto display the Industry Canada certification number ofthe module, preceded by the words “Contains transmit-ter module”, or the word “Contains”, or similar wordingexpressing the same meaning, as follows:User Manual Notice for License-Exempt Radio Appara-tus (from Section 7.1.3 RSS-Gen, Issue 3, December2010): User manuals for license-exempt radio appara-tus shall contain the following or equivalent notice in aconspicuous location in the user manual or alterna-tively on the device or both:Transmitter Antenna (from Section 7.1.2 RSS-Gen,Issue 3, December 2010): User manuals for transmit-ters shall display the following notice in a conspicuouslocation:To satisfy FCC RF Exposure requirements for mobile and base station transmission devices, a separation distance of 20 cm or more should be maintained between the antenna of this device and persons dur-ing operation. To ensure compliance, operation at closer than this distance is not recommended.The antenna(s) used for this transmitter must not be co-located or operating in conjunction with any other antenna or transmitter.Contains transmitter module IC: 6514A-RN52This device complies with Industry Canada license-exempt RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause interference, and (2) this device must accept any interference, including interference that may cause undesired operation of the device.Le présent appareil est conforme aux CNR d'Indust-rie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorisée aux deux con-ditions suivantes: (1) l'appareil ne doit pas produire de brouillage, et (2) l'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d'en compromettre le fonctionnement.Under Industry Canada regulations, this radio trans-mitter may only operate using an antenna of a type and maximum (or lesser) gain approved for the trans-mitter by Industry Canada. To reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropi-cally radiated power (e.i.r.p.) is not more than that necessary for successful communication.Conformément à la réglementation d'Industrie Can-ada, le présent émetteur radio peut fonctionner avec une antenne d'un type et d'un gain maximal (ou inférieur) approuvé pour l'émetteur par Industrie Can-ada. Dans le but de réduire les risques de brouillage radioélectrique à l'intention des autres utilisateurs, il faut choisir le type d'antenne et son gain de sorte que la puissance isotrope rayonnée équivalente (p.i.r.e.) ne dépasse pas l'intensité nécessaire à l'établissement d'une communication satisfaisante.
www.rovingnetworks.com Version 1.1 3/19/13 page 16Advanced InformationRN52-DSThe above notice may be affixed to the device insteadof displayed in the user manual.3.2.2 HELPFUL WEB SITESIndustry Canada: http://www.ic.gc.ca/ 3.3 EuropeThe RN52 module is an R&TTE Directive assessedradio module that is CE marked and has been manu-factured and tested with the intention of being inte-grated into a final product. The RN52 module has been tested to R&TTE Directive1999/5/EC Essential Requirements for Health andSafety (Article (3.1(a)), Electromagnetic Compatibility(EMC) (Article 3.1(b)), and Radio (Article 3.2) and aresummarized in Table 3-1: European Compliance Test-ing. A Notified Body Opinion has also been issued. Alltest reports are available on the RN52 product webpage at http://www.microchip.com.The R&TTE Compliance Association provides guid-ance on modular devices in document Technical Guid-ance Note 01 available at http://www.rtteca.com/html/download_area.htm. 3.3.1 LABELING AND USER INFORMATION REQUIREMENTSThe label on the final product which contains the RN52module must follow CE marking requirements. TheR&TTE Compliance Association Technical GuidanceNote 01 provides guidance on final product CE mark-ing.3.3.2 ANTENNA REQUIREMENTSFrom R&TTE Compliance Association document Tech-nical Guidance Note 01:Provided the integrator installing an assessedradio module with an integral or specific antennaand installed in conformance with the radio mod-ule manufacturer’s installation instructionsrequires no further evaluation under Article 3.2of the R&TTE Directive and does not require fur-ther involvement of an R&TTE Directive NotifiedBody for the final product. [Section 2.2.4]3.3.3 HELPFUL WEB SITESA document that can be used as a starting point inunderstanding the use of Short Range Devices (SRD)in Europe is the European Radio CommunicationsCommittee (ERC) Recommendation 70-03 E, whichcan be downloaded from the European Radio Commu-nications Office (ERO) at: http://www.ero.dk/. Additional helpful web sites are:• Radio and Telecommunications Terminal Equip-ment (R&TTE):http://ec.europa.eu/enterprise/rtte/index_en.htm• European Conference of Postal and Telecommu-nications Administrations (CEPT):http://www.cept.org• European Telecommunications Standards Insti-tute (ETSI):http://www.etsi.org• European Radio Communications Office (ERO):http://www.ero.dk• The Radio and Telecommunications Terminal Equipment Compliance Association (R&TTE CA):http://www.rtteca.com/Note: To maintain conformance to the testinglisted in Ta b l e 3 - 1 , the module shall beinstalled in accordance with the installa-tion instructions in this data sheet andshall not be modified.When integrating a radio module into acompleted product the integratorbecomes the manufacturer of the finalproduct and is therefore responsible fordemonstrating compliance of the finalproduct with the essential requirements ofthe R&TTE Directive.
www.rovingnetworks.com Version 1.1 3/19/13 page 17Advanced InformationRN52-DS3.4 AustraliaThe Australia radio regulations do not provide a modu-lar approval policy similar to the United States (FCC)and Canada (IC). However, RN52 module RF transmit-ter test reports can be used in part to demonstrate com-pliance in accordance with ACMA Radiocommunications “Short Range Devices” Standard2004 (The Short Range Devices standard calls up theAS/NZS 4268:2008 industry standard). The RN52module test reports can be used as part of the productcertification and compliance folder. For more informa-tion on the RF transmitter test reports, contact Micro-chip Technology Australia sales office.To meet overall Australian final product compliance, thedeveloper must construct a compliance folder contain-ing all relevant compliance test reports e.g. RF, EMC,electrical safety and DoC (Declaration of Conformity)etc. It is the responsibility of the integrator to know whatis required in the compliance folder for ACMA compli-ance. All test reports are available on the RN52 productweb page at http://www.microchip.com. For more infor-mation on Australia compliance, refer to the AustralianCommunications and Media Authority web sitehttp://www.acma.gov.au/. 3.4.1 HELPFUL WEB SITESThe Australian Communications and Media Authority:www.acma.gov.au/. 3.5 New ZealandThe New Zealand radio regulations do not provide amodular approval policy similar to the United States(FCC) and Canada (IC). However, RN52 module RFtransmitter test reports can be used in part to demon-strate compliance against the New Zealand “GeneralUser Radio License for Short Range Devices”. NewZealand Radio communications (Radio Standards)Notice 2010 calls up the AS / NZS 4268:2008 industrystandard. The RN52 module test reports can be usedas part of the product certification and compliancefolder. All test reports are available on the RN52 prod-uct web page at http://www.microchip.com. For moreinformation on the RF transmitter test reports, contactMicrochip Technology sales office.Information on the New Zealand short range deviceslicense can be found in the following web links:http://www.rsm.govt.nz/cms/licensees/types-ofli-cence/general-user-licences/short-range-devices andhttp://www.rsm.govt.nz/cms/policy-and-planning/spec-trum-policy-overview/legislation/gazette-notices/prod-uct-compliance/radiocommunications-radiostandards-notice-2010. To meet overall New Zealand final product compliance,the developer must construct a compliance folder con-taining all relevant compliance test reports e.g. RF,EMC, electrical safety and DoC (Declaration of Confor-mity) etc. It is the responsibility of the developer toknow what is required in the compliance folder for NewZealand Radio communications. For more informationon New Zealand compliance, refer to the web sitehttp://www.rsm.govt.nz/. 3.5.1 HELPFUL WEB SITESRadio Spectrum Ministry of Economic Development:http://www.rsm.govt.nz/. TABLE 3-1: EUROPEAN COMPLIANCE TESTINGCertification Standards Article Laboratory Report Number DateSafety EN 60950-1:2006+A11:2009+A1:2010 (3.1(a))Health EN 50371:2002-03EMC EN 301 489-1 V1.8.1 (2008-04) (3.1(b))EN 301 489-17 V2.1.1 (2009-05) Radio EN 300 328 V1.7.1 (2006-10) (3.2)Notified Body OpinionDoC
www.rovingnetworks.com Version 1.1 3/19/13 page 18Advanced InformationRoving Networks, Inc.102 Cooper CourtLos Gatos, CA 95032+1 (408) 395-5300www.rovingnetworks.comCopyright © 2013 Roving Networks. All rights reserved. Roving Networks is a registered trademark of Roving Networks. Apple Inc., iPhone, iPad, iTunes, Made for iPhone are registered trademarks of Apple Computer. Roving Networks reserves the right to make corrections, modifications, and other changes to its products, documentation and services at any time. Customers should obtain the latest relevant information before plac-ing orders and should verify that such information is current and com-plete. Roving Networks assumes no liability for applications assistance or cus-tomer’s product design. Customers are responsible for their products and applications that use Roving Networks components. To minimize cus-tomer product risks, customers should provide adequate design and oper-ating safeguards. Roving Networks products are not authorized for use in safety-critical applications (such as life support) where a failure of the Roving Networks product would reasonably be expected to cause severe personal injury or death, unless officers of the parties have executed an agreement specifi-cally governing such use.RN52-DSThis device has not been authorizedas required by the rules of the FederalCommunications Commission. Thisdevice is not, and may not be, offeredfor sale or lease, or sold or leased,until authorization is obtained.4.0 ORDERING INFORMATIONTa b l e 4 - 1 provides ordering information for the RN52module.Go to http://www.rovingnetworks.com for current pric-ing and a list of distributors carrying Roving Networksproducts.5.0 DOCUMENT REVISION HISTORY5.1 Version 1.1• Updated pin information.• Added more details on RN52 layout o host PCB.5.2 Version 1.0Initial release.TABLE 4-1: ORDERING INFORMATIONPart Number DescriptionRN52-I/RM Standard application firmware (A2DP/AVRCP/SPP) master and slave).For other configurations, contact Roving Networks directly.

Navigation menu