Issue 1 Copyright Nokia Corporation. All Rights Reserved
Page 2
Customer Care Solutions
Technical Documentation
Amendment Record Sheet
Amendment NoDateInserted ByComments
09/2002J FraserIssue 1
Issue 1 Copyright Nokia Corporation. All Rights Reserved
Page 3
Customer Care Solutions
Technical Documentation
RH-10 Series Cellular Phones
Service Manual – Overall Manual Contents
Service Manual comprising
RH-10 Series Transceiver booklet comprising
Foreword
General
Parts
Service Software Instructions
Service Tools
Disassembly/Assembly
Troubleshooting
Troub leshooting-Antenna
System Module
Schematics
Issue 1 Copyright Nokia Corporation. All Rights Reserved
Page 4
This document is intended for use by qualified service personnel only.
Company Policy
Our policy is of continuous development; details of all technical modifications will be
included with service bulletins.
While every endeavour has been made to ensure the accuracy of this document, some
errors may exist. If any errors are found by the reader, Nokia Corporation should be notified in writing.
Please state:
Customer Care Solutions
Technical Documentation
IMPORTANT
Title of the Document + Issue Number/Date of publication
Latest Amendment Number (if applicable)
Page(s) and/or Figure(s) in error
Please send to: Nokia Corporation
CCS Technical Documentation
PO Box 86
FIN-24101 SALO
Finland
Issue 1 Copyright Nokia Corporation. All Rights Reserved
Page 5
Customer Care Solutions
Technical Documentation
Warnings and Cautions
Please refer to the phone's user guide for instructions relating to operation, care and
maintenance including important safety information. Note also the following:
Warnings:
1. CARE MUST BE TAKEN ON INSTALLATION IN VEHICLES FITTED WITH
ELECTRONIC ENGINE MANAGEMENT SYSTEMS AND ANTI-SKID BRAKING
SYSTEMS. UNDER CERTAIN FAULT CONDITIONS, EMITTED RF ENERGY CAN
AFFECT THEIR OPERATION. IF NECESSARY, CONSULT THE VEHICLE DEALER/
MANUFACTURER TO DETERMINE THE IMMUNITY OF VEHICLE ELECTRONIC
SYSTEMS TO RF ENERGY.
2. THE HANDPORTABLE TELEPHONE MUST NOT BE OPERATED IN AREAS LIKELY
TO CONTAIN POTENTIALLY EXPLOSIVE ATMOSPHERES EG PETROL STATIONS
(SERVICE STATIONS), BLASTING AREAS ETC.
3. OPERATION OF ANY RADIO TRANSMITTING EQUIPMENT, INCLUDING
Cautions:
1. Servicing and alignment must be undertaken by qualified personnel only.
2. Ensure all work is carried out at an anti-static workstation and that an
3. Ensure solder, wire, or foreign matter does not enter the telephone as
4. Use only approved components as specified in the parts list.
5. Ensure all components, modules screws and insulators are correctly
CELLULAR TELEPHONES, MAY INTERFERE WITH THE FUNCTIONALITY OF
INADEQUATELY PROTECTED MEDICAL DEVICES. CONSULT A PHYSICIAN OR
THE MANUFACTURER OF THE MEDICAL DEVICE IF YOU HAVE ANY
QUESTIONS. OTHER ELECTRONIC EQUIPMENT MAY ALSO BE SUBJECT TO
INTERFERENCE.
anti-static wrist strap is worn.
damage may result.
re-fitted after servicing and alignment. Ensure all cables and wires are
repositioned correctly.
Issue 1 Copyright Nokia Corporation. All Rights Reserved
The Nokia RH-10 is a dual band/dual mode radio transceiver unit for U.S. CDMA/ AMPs
800 MHz networks. The transceiver is fully based on DCT4 technology.
The transceiver consists of System/RF module, keypad module, LCD module, and assembly parts. The User Interface consists of normal number, talk, soft, and power keys in the
keymat. The NPW-3 has an internal antenna and the antenna connection is provided by
springs from the antenna to the PWB.
This section briefly describes how to install Phoenix and includes some basic information
on how to use the program. More detailed information can be found in the Phoenix Help
files. Each feature in Phoenix has its own Help file, which can be activated whil running
Phoenix. To activate a Help file while Phoenix is running, press the F1 key or the specific
feature’s Help button.
General Setup Procedure
Initial installation of Phoenix requires the complete Phoenix installation package. This
package, currently around 30 Megabytes in size, is provided on a CD-ROM disk. Because
of this large size, it is not recommended to download the file nor is it practical to provide
it on 3.5-inch floppy disks.
Install Phoenix by following the steps outlined on the material that comes with the disk.
It should be noted that installation of a Nokia dongle on the computer being loaded is
REQUIRED prior to beginning the installation of the software.
The software is packaged into an InstallShield executable bundle. When the user doubleclicks on this file, the installation program provides on-screen instructions on how to
proceed. Standard installation, provided by selecting all default choices, is highly recommended. You may do a custom installation and place Phoenix into a special location on
your hard drive, but this is only recommended for experienced users.
It is necessary to reboot the computer after installing the software. The program will not
be usable until a reboot is performed. After reboot, the Phoenix icon is displayed on the
computer desktop. Double-clicking on this icon launches the program.
Service Software InstructionsCCS Technical Documentation
Hardware Requirements for using Phoenix
Minimum Hardware Requirements
Processor233 MHz
RAM64 MB
Disk Space Needed50-100 MB
Supported Operating SystemsNotes
Windows 95Limited, no USB support
Windows 98
Windows NT 4.0no USB support
Windows 2000Professional version
Installing Phoenix
Before installing the software, verify:
• The dongle is attached to the parallel port for PKD version dongles, or an FLS-4 version
dongle is attached on either the parallel port or the USB port (if the computer supports
USB).
• Ensure that if the computer supports administrator rights (typically on Windows NT
and Windows 2000 installations) that access is enabled for the user performing the
Phoenix installation.
• If a previous version of Phoenix has been installed, it may be necessary to first properly
remove that program prior to installing the new version. If installation is performed,
be sure to reboot the computer prior to continuing. See the section Uninstalling
Phoenix for instructions on how to uninstall.
Installation Directions
• Insert the CD-ROM disk into the computer drive
• Access the drive and double-click on the Phoenix software package found on the CD.
• Follow the on-screen prompts to conclusion.
Note that rebooting the computer may be necessary when completed.
Software Support Bundles:
The Phoenix installation is auto-executable. You must obtain Software Support Bundles
to load software upgrade files to customer-specific phone models.
These bundles are created by PAMS and made available by AMS on the Partners Web
Page http://americas.partners.nokia.com
have not registered as a user, contact Nokia Central Service in Melbourne, Florida.
Similar to the Phoenix installation, these Software Support Bundles are InstallShield executable packages. Just double-click on the package and it will auto-install.
No rebooting of the computer is required.
. This web page is password-controlled; if you
Starting a Phoenix Session
Concepts
When referring to Phoenix, Product is the cellular phone attached to the computer.
More specifically, it is the particular type of phone.
Connection is the type of cable used to attach the phone and the port on the computer
where it is attached. Refer to Chapter 7-Service Tools for additional information.
The first time Phoenix is used, certain connection configurations must be made. Subsequent uses will rely on these selections and they will not need to be made again.
Initial Session with Phoenix
It is necessary to create the connection the first time Phoenix is used. Follow these simple steps:
Service Software InstructionsCCS Technical Documentation
Select Manage Connections… from the “File” drop-down menu.
Next click the A
When the Select Mode dialog box appears, you may then select either Wizard, which will
auto-detect your connection configuration, or Manual, which allows you to manually
select options to create the connection.
Once a connection is defined, make sure that the one to be used is moved to the top of
the list (use the up down arrows on the Manage Connections dialog box. Then click on
the Apply button. Close the window when finished.
You can now proceed with the normal initiation of a session by selecting a product or
scanning for a product.
Scanning for a Product
Many features of this program are product-specific. Therefore it is necessary to configure Phoenix for the product on which you will be working at the beginning of the session.
Scan Product – Choose Scan Product from the drop-down menu list and Phoenix will
automatically scan for product and select the necessary configurations. The status bar
at the bottom will indicate if the product was found and its type.
Using Components
When working with Phoenix, tasks are generally managed by specific software components. From the menu, select the desired component or task to be performed.
“Opening a component” is defined as opening a tool window within Phoenix. When this
window is opened, Phoenix also opens a toolbar for it and adds component-specific
menu items in the Window menu.
Using Profiles
Phoenix’s Profile feature allows product, connection and currently open components to
be stored into permanent storage by creating a profile file with a name of your choice
followed by an .nmp file extension for later retrieval.
Saved profiles makes it easy to configure Phoenix into a desired configuration with
favorite windows already opened and ready to go.
Service Software InstructionsCCS Technical Documentation
Opening and saving profiles is done via menu commands found in the File drop-down
menu: Open Profile and Save Profile.
Profiles are stored into a disk file with user-defined names. As a result, there can be
multiple profiles for different repeated tasks or user preferences.
Uninstalling Phoenix
As mentioned in the Installing Phoenix section, it may be necessary or desirable to
remove Phoenix. Care must be taken to follow this procedure. Failure to remove the
program properly will cause misconfiguration of the computer’s registry.
Uninstalling Phoenix version:
• Access the computer’s “Control Panel” section, selectable from the Start button or the
“My Computer” desktop icon
• Select the “Add/Remove Programs” icon
• Select the Phoenix version to be removed, and click the Add/Remove button
• Click on the OK button to begin the process of removal
This section briefly describes how to install Diego 2.0 and includes some basic information on how to use the program. More detailed information can be found in the Diego
Help files. Each feature in Diego has its own Help file, which can be activated while running Diego. To activate a Help file while Diego is running, press the F1 key or the specific
feature’s Help button.
Diego 2.0 is designed to be used by point of sales locations. Ease of use and minimal
operator decision-making were key factors in the design. Additionally, this Diego version
is compatible with current-generation phones (DCT3 versions such as 5185i, 5170i,
5180i, 6185i, and 3285) and the new generation phones currently being introduced
(DCT4 versions such as the 6385).
General Setup Procedure
Initial installation of Diego requires the complete Diego installation package. This package, currently around 18 megabytes in size, is provided on a CD-ROM disk. Because of
this large size, it is not recommended to download the file nor is it practical to provide it
on 3.5-inch floppy disks.
Install Diego by following the steps as outlined on the material that comes with the disk.
It should be noted that installation of a Nokia dongle on the computer being loaded is
REQUIRED prior to beginning the installation of the software.
The software is packaged into an InstallShield executable bundle. When the user double-clicks on this file, the installation program provides on-screen instructions on how to
proceed. Standard installation, provided by selecting all default choices, is highly recommended. You may do a custom installation and place Diego into a special location on
your hard drive; however, this is only recommended for experienced users.
It is necessary to reboot the computer after installing the software. The program is not
usable until a reboot is performed. After reboot, the Diego icon is included on the computer desktop. Double-clicking on this icon launches the program.
Service Software InstructionsCCS Technical Documentation
Hardware Requirements for using Diego
Minimum Hardware requirements
Processor233 MHz
RAM64 MB
Disk space needed50 - 100 MB
Supported Operating systemsNotes
Installing Diego
Before installing the software, verify:
• An FLS-4 version dongle is attached to either the parallel port or the USB port (if the
computer supports USB). An FLS-2D may be used; however, the FLS-2D does not support the new generation DCT-4 version phones.
• Ensure that if the computer supports administrator rights (typically on Windows NT
and Windows 2000 installations) that access is enabled for the user performing the
installation.
• If a previous version of Diego has been installed, it may be necessary to first properly
remove that program prior to installing the new version. If installation is performed,
be sure to reboot the computer prior to continuing. See Uninstalling Diego for
instructions on how to uninstall.
Windows 95limited, no USB support
Windows 98
Windows NT 4.0no USB support
Windows 2000Professional version
Installing:
• Insert the CD-ROM disk into the computer drive.
• Access the drive and double-click on the Diego software package found on the CD.
Note that rebooting the computer will be necessary when completed.
Software Support Bundles:
The Diego installation is auto-executable. You must obtain Software Support Bundles to
load software upgrade files to customer-specific models.
These bundles are created by PAMS and made available by AMS on the Partners Web
Page http://americas.partners.nokia.com . This web page is password-controlled; if you
have not registered as a user, contact Nokia Central Service in Melbourne, Florida.
Similar to the Diego installation, these packages are executable packages. Just doubleclick on the package, and it will auto-install.
No rebooting of the computer is required.
Starting a Diego Session
Concepts
When referring to Diego, Product is the cellular phone attached to the computer. More
specifically, it is the particular type of phone.
Connection is the type of cable used to attach the phone and the port on the computer
where it is attached. Refer to Chapter 7-Service Tools for more information.
The first time Diego is used, certain connection configurations must be made. Subsequent uses will rely on these selections and they will not need to be made again.
Initial Session with Diego and FLS-4S Dongle
You must configure the Virtual Port Connection in Diego the first time Diego is launched.
The FLS-4 dongle uses virtual port, which eliminates the need to use the serial port (as
the FLS-2D does). During the installation of the FLS-4 drivers (included in the Diego
installation package), a virtual COM port is set to the next available COM port number.
This port selection must be put into the Diego configuration.
Note: COM port settings can only be entered or changed if the auto-connection feature of Diego is
disabled (as indicated in the grey Status box). To disable the auto-connect feature, click on this icon in
the toolbar.
Select the Virtual COM port setting . Then press the Apply button.
You can now proceed with the normal initiation of a session.
Scanning for a Product
Many features of this program are product-specific. Therefore, it is necessary to configure Diego at the beginning of a session for the product on which you will be working.
Scanning of the product can be done manually or automatically. The default setting is
automatic. This setting can be changed to manual in the “settings” – “general” box. In
automatic mode, Diego will automatically scan for a product at a periodic rate. The scan
rate is defaulted to every 5 seconds, but it can be changed to a different frequency in the
Setup menu.
To manually scan for a product, click on the “Settings” icon as noted above.
Using Components
When working with Diego, tasks are generally managed by specific software components. From the icons displayed on the left side of the screen, select the desired component or task to be performed.
“Opening a component” is defined as opening a tool window within Diego. When this
window is opened, Diego also opens a task box for it, which includes component-specific menu items.
Uninstalling Diego
As mentioned in the Installing Diego section, it may be necessary or desirable to remove
for MBus, Fbus, RF, and audio
connections. This setup allows
connection between flash prommers. When the audio box is
connected, it has to be connected to the phone’s audio connector. The Docking Station can
be powered by FPS-8 or external
power supply.
maximum power supply for the
phone from an external power
supply. The Flash Adapter allows
Mbus/Fbus connections. The
Flash Adapter is protected
against over-voltage, over-current, and cross-connection. The
Flash Adapter provides a regulated voltage to the phone.
Note: The flash adapter is
designed for flashing only.
MJS-59 Module Jig0770366The purpose of the MJS-59 mod-
ule service jig is to provide a
method of component-level testing, by applying voltage from an
external power supply when the
phone engine is out of its
mechanics. The engine module
and UI module of RH-10 can be
tested with MJS-59.
RF connection is established
through a replaceable GAC-5
connector. Two SMA-type connectors are available for audio
testing using ADS-7 cables. This
type of connection eliminates
the need for external audio splitter.
Note: The nominal supply voltage
for the MJS-59 is +4.1V. The supply voltage must not exceed
+5.0V.
FPS-8 Flash Prommer0080321The Flash Prommer FPS-8 is used
for heavy flash.
Includes ACF-8 AC charger
(0680032).
Includes AXS-4 D9-D9 cable
(0730090).
ADS-6 Audio Cable0730241The Audio Cable connects to the
Audio Box JBA-8.
ADS-7 Audio Cable0730261ADS-7 Audio Cable is for use
with MJS-59 Module Jig. Audio
is split at the module jig, eliminating the need for a separate
audio box in this configuration.
hardware enabling the use of the
service software when connected
to the LPT (parallel port) of the
PC. A dongle is required for use
of the service software. A printer
or any such device can be connected to the PC through the
dongle, if needed.
Cautions: Make sure that you
have switched off the PC and the
printer before making connections. Do not connect the PKD-1
to the serial port. You may damage your PKD-1.
0775294The Docking Station and RF
Adapter RC1 are needed for
Mbus, Fbus, and RF connections.
The Docking Station also may be
used without RC1 if RF output is
not desired. The Docking Station
may be powered by the FPS-8
setup or by an external power
supply.
Note: Toggle the DC power supply
switch to correct mode before
applying power.
RC1 RF Adapter0775296Used with the Docking Station
JBU-11, above. The RC1 uses the
GAC-5 for RF interface.
XRS-5 RF Connector0730228XRS-5 (shown at left in drawing)
is used for readings, in conjunction with the BBS-10 service
battery.
Note: Use with protection grommet, pictured at lower right.
GAC-5 RF Connector0770473GAC-5 is used with JBU-11/RC1
and MJS-59 to make RF connections. This connector is included
with both tools; however, it is
available separately as a userreplaceable part in the event of
damage. The connector and both
jigs are designed to accept a
micro in-line attenautor. This
permits attenuation as close to
the source RF as possible.
Flashing, testing, tuning with covers on (Setups 2a, 2b, 2c, 2d)
Tightened performance specifications require more precise equipment and methods for
testing and alignment. Manual tuning can’t provide accurate results for RH-10 products,
which means that this task has to be automated.
These setups are intended to be used either with Phoenix or Darium SW. With the Phoenix SW, it is possible to do manual testing and automated tuning. With Darium, it is possible to do automated testing and tuning.
Note: Finger cots or gloves should be worn when phone is disassembled.
Note: ESD precautions should be strictly observed when handling unassembled phones.
A-Cover
(Disassemble) After removing the battery cover, grasp the bottom of the A-cover and the
bottom of the transceiver. Pull apart (photo below, left). The A-cover is hinged at the top;
do not force apart. The hinge releases when the bottom is fully separated from the transceiver.
(Assemble) Ensure that the keypad is properly seated in the A-cover, pressing at each of
the four guide pins with a fingertip (photo below, right). While holding the A-cover
approximately 30 degrees to the transceiver, engage the top hinge. Now push the bottom
of the A-cover towards the transceiver until it seats fully.
Disassembly / AssemblyCC S T echnica l Document a tion
Screws x 6 (4 x long top/bottom) (2 x short middle)
(Disassemble) Using a size T6 driver, remove all six screws.
(Assemble) Replace the screws in the order shown in the photo below left. Be sure to
apply pressure to the board with the other hand to ensure a flat fit for all spring contacts. The photo at right shows the different lengths of screws.
NOTE: Screw torque should be set at 16 Ncm +/-2 Ncm. This can only be achieved with a properly
calibrated torque driver. All torque drivers should have routine inspections for correct calibration and
proper performance.
UI Snap Fit
(Disassemble) Using a small, flat screwdriver or a pair of fine tweezers, gently disengage
one of the two snaps that hold the UI board to the B-cover (located on either side of the
phone, level with the bottom edge of the LCD). (Photo below, left, illustrates this.) The
second snap should disengage easily as the UI module is removed from the radio module
(photo below, right). Care should be taken to not damage the snaps.
(Assemble) Make sure the UI module is properly aligned with the radio module. Apply an
even, downward pressure to both snaps at once.
(Disassemble) The speaker may now be removed, if needed, by carefully lifting at the
open cavities for the speaker snap fits. A pair of offset tweezers may be used to grasp
both sides of the speaker (see photo, below); then simply lift the speaker straight up.
NOTE: DO NOT pierce with sharp object, or touch the spring contacts of the speaker or display.
(Assemble) It is recommended that offset tweezers be used to insert the speaker, avoiding contact with hands. It is important to keep the contacts safe.
NOTE: DO NOT touch the spring contacts.
Radio Module
(Disassemble) The radio module now is free to be removed.
NOTE: Be careful NOT to damage the springs of the battery contact or system connector while
removing the radio module.
(Assemble) Carefully install the radio module, using the guide pins on the B-cover for
position.
NOTE: Special care should be taken NOT to damage the spring contacts.
Disassembly / AssemblyCC S T echnica l Document a tion
System Connector
(Disassemble) Once the radio module has been removed, the system connector is free to
be removed from the B-cover.
NOTE: Take care NOT to touch the springs during assembly or disassembly. Also, do not lay aside
with contacts down.
(Assemble) See the NOTE above for precautions
RF Shield
(Disassemble) The RF shield is free to be removed by grasping at top and bottom (see
photo below), carefully lifting over the battery contact springs. Do not use the center of
shield for removal, as damage to shield springs or battery contact springs may occur.
(Assemble) Great care should be taken to avoid contact with the battery contact springs
and to avoid damage.
(Disassemble) Note two through-holes located in the bottom of the connector (photo,
below left). A small, blunt object may be inserted to help dislodge the microphone or
vibra motor. The motor may also be removed by gently lifting the vibra shaft. Do not
force the motor out; damage will occur. If the assemblies are to be reused, be careful not
to touch any spring contacts.
(Assemble) Use tweezers to reinsert (photo, below right), using the tip to fully seat.
NOTE: DO NOT use fingertips to seat! Overstress by pushing on spring contacts can lead to intermittent failures in time, even if the initial testing is okay.
Disassembly / AssemblyCC S T echnica l Document a tion
Battery Connector (also see Battery Connector Handling, which follows)
(Disassemble) Insert the tip of a very thin, flat-tip screwdriver (or similar instrument)
between the battery connector and the B-cover wall (at approximately the center of the
battery connector). Gently rock the handle of the screwdriver (see photo below) downward to disengage the two locking clips and to lift the battery connector upward.
(Assemble) Carefully place the connector in the B-cover. Then use a small screwdriver or
tweezer tip to push the center of the connector in order to fully seat. You should hear/
feel the locking mechanism engage.
Battery Connector Handling
The springs that make contact with the PWB can be easily bent while exposed or while
outside of an assembled phone. Take care NOT to touch these contacts at any time if the
connector is to be reused. Tweezers should be used to remove new connectors from tray.
(Disassemble) Insert a small screwdriver between the antenna and the B-cover next to
one of the two retaining snaps (indicated by blue - bottom two - arrows in the following
photo). Using the tool as a lever, gently disengage each of the two snaps. Care should be
taken NOT to damage the guide pin, positioned through the top portion of the antenna
(indicated by white - top - arrow in the following photo).
(Assemble) Position the antenna onto the B-cover guide pin (white - top - arrow in photo
below). Press straight down in the middle of the antenna until you feel/hear the snaps
engage, indicating that the assemblies are fully seated.
NOTE: Initial alignment and straight insertion is critical to keep from damaging the guide pin.
Volume Key
(Disassemble) With antenna removed, volume key is free and may be lifted off.
The Diva troubleshooting section includes tuning information, troubleshooting test,
probing points, and block diagrams.
Tuning Information
ST Batman VHFPLL
This is one of the phone’s self-tests, which gives either a Pass or Fail result only.
The VHFPLL is inside the Batman IC. The phone checks the VHFPLL’s lock detect bit. If this
bit indicates that the PLL is unlocked, the test will fail.
Manual Verification: Turn on the Cell or PCS receiver to any channel and probe at L701
(probing point 39 in Figure 2), using an RF probe connected to a spectrum analyzer tuned
to 256.2 MHz. If the PLL is locked, it will be stable in frequency. If it is unlocked, you may
have to use a wide span to see it since it may be far off frequency.
Troubleshooting: Check C701, C714, R703, R702, C715, R704, V701, C716, L701, and
C702. Check power supplies to Batman, particularly check for 2.7v on VR5 at C710 and
on VR7 at C708. Check for 1.8v on VIO. If no fault is found, replace N701 (Batman).
ST TX Detector Cell
This is one of the phone’s self-tests, which gives either a Pass or Fail result only.
The phone transmits at several power levels and checks the ADC value of the power
detector. The ADC value is measured first for a set of AGC values, and then each AGC
value is changed individually to ensure that the ADC changes as each AGC change is
made.
Manual Verification: Using Main Mode, turn on the Cell CDMA TX with the channel set to
384 and turn on IS95 modulation using CDMA control. Using the PDM window, set:
TX_IF_AGC to -100
TX_RF_AGC to -512
PA_AGC to +511
Record the TX signal power from the antenna connector, using a spectrum analyzer centered at 836.52 MHz. (The self-test measures the power detector reading instead, but at
the present time it cannot be done with Phoenix. An easy way to check functionality
without removing the covers is to check transmitted power.) Transmitter power should be
greater than 24 dBm. (PWR_OUT greater than 1.91v, which corresponds to the power
detector ADC=700.)
For each of the next three cases, TX power should be less than 24 dBm (less than 1.91v
on PWR_OUT).
Troubleshooting: If there is a failure associated with only some of the cases above, check
the AGC voltages and components of the associated PDMs as described in Tables 1 and 4.
For problems with the IF or RF AGC, also check Robin and supporting components. For PA
AGC problems, also check the PA and supporting components. If all the above cases fail,
troubleshoot the TX chain as described in this section.
If all the output powers pass, perhaps the test is failing because the ADC voltage is
wrong. The limit is 1.64v. If the voltages are wrong, then check the power detector at
R821, R801, R804, L801, C805, R806, R805, C803, V801, C804, and C807, and also Robin.
If the voltages are correct and it still fails, check the UEM (D200).
ST Robin VHFPLL Cell
This is one of the phone’s self-tests, which gives either a Pass or Fail result only.
The VHFPLL is inside the Robin IC. The phone checks the VHFPLL’s lock-detect bit. If this
bit indicates that the PLL is unlocked, the test will fail.
Manual Verification: Turn on the Cell CDMA receiver to any channel and probe at L611
(probing point 11, Figure 1), using an RF probe connected to a spectrum analyzer tuned
to 346.2 MHz. If the PLL is locked, it will be stable in frequency. If it is unlocked, you may
have to use a wide space to see it since it may be far off frequency.
2.7v on VR3 and VR6, and 1.8v on VIO. If no problems are found, replace Robin.
SN Cell PA Temp
This is one of the phone’s self-tunings, which reads the ADC voltage of thermistor R808,
and checks to make sure the phone is at room temperature. A phone should not be tuned
while it is either hot or cold.
The phone reports the ADC voltage value of the thermistor and it should be within the
set limits.
Manual Verification: Ensure the phone is cool by letting it cool down for several minutes.
Retest, keeping in mind that if there is a short circuit on the board, the phone will get
Troubleshooting: If the phone was recently transmitting in Cell band at full power for an
extended period of time, it is probably hot for that reason. Let it cool down for a few
minutes before proceeding. If it still fails, there may be either a short on the board or a
problem with the PA Temp circuitry. To check PA Temp circuitry, check R808, C232, R202,
and D200. If a short is suspected, check the Cell PA first. If an infrared camera is available, this is one of the easiest methods to detect a short.
SN Cell RX BB Filter
This is one of the phone’s self-tunings, which tunes the lowpass filter in the Batman IC
(N701), in Cell CDMA mode.
This self-tuning returns one of the filters tuned parameters, which should be within the
set limits.
Manual Verification: Use “RF Tuning” dialog box in Phoenix; set mode to Self Tune, and
choose this tuning.
Troubleshooting: Check Batman (N701) and supporting components.
SN Cell RX DC Offset I (or Q)
This is one of the phone’s self-tunings, which measures and adjusts the cell band CDMA
receiver DC offsets until they are within the set limits.
The DC offset is returned for I (or Q).
Manual Verification: Use “RF Tuning” dialog box in Phoenix; set mode to Self Tune, and
choose this tuning.
Troubleshooting: Check Batman (N701) and supporting components.
SN AMPS RX BB Filter
This is one of the phone’s self-tunings, which tunes the lowpass filter in the Batman IC
(N701), in AMPS mode.
This self-tuning returns one of the filters tuned parameters, which should be within the
set limits.
Manual Verification: Use the “RF Tuning” dialog box in Phoenix; set mode to Self Tune,
and choose this tuning.
Troubleshooting: Check Batman (N701) and supporting components.
SN AMPS RX DC Offset I (or Q)
This is one of the phone’s self-tunings, which measures and adjusts the cell band CDMA
receiver DC offsets until they are within the set limits.
Manual Verification: Using the “RF Tuning” dialog box in Phoenix, set mode to Self Tune,
and choose this tuning.
Troubleshooting: Check Batman (N701) and supporting components.
Test TX Start-up Current
This test turns on the AMPS transmitter (PCS transmitter for PCS-only phones) and measures current of the whole phone—which can detect some assembly errors.
Manual Verification: Set the phone to local mode and turn on the AMPS transmitter. Set
the PDM values as listed in Table 1a for AMPS Power Level 5 (for PCS, set output power
to +12dBm). Read the phone’s current on the power supply and check to see that it is
within the set limits. If the power supply does not display current draw, use a current
meter in series with the phone. If the phone powers down when the mode is set, it may
be that the phone is drawing more current than the current limit setting on the power
supply.
Troubleshooting: If current is very high, there may be a short circuit on the phone caused
by a solder bridge, a failed component that is internally shorted, a component placed
with the wrong rotation, or some other reason. Short circuits can be difficult to find, but
one of the easiest methods is to use a thermal camera and look for hot spots that are not
normally hot. Look for the hottests spots. A visual inspection can find solder bridges or
wrong component rotations. A failed component can be found by functional tests of the
phone’s sub-blocks.
Test TX Start-up Amplitude
This test turns on the AMPS transmitter and checks for the presence of a TX signal with
an amplitude within a specified range. A wide range is allowed since the transmitter is
not yet tuned.
Manual Verification: Set the phone to local mode and turn on the AMPS transmitter set
to channel 384. Set the AGC PDM values as in Test 17. Look for an output signal at
836.52 MHz with an amplitude within the set limits. The frequency of the signal may not
be accurate since the VCTCXO has not been tuned yet.
Troubleshooting: Check proper placement, rotation, and soldering of the components of
the TX chain, as shown in Figure 1. Check for the presence of LO tones as listed in
Table 2. Check for the presence of a TX signal at each point in the TX chain, probing
according to Table 2.
TN VCTCXO Frequency
The purpose of this tuning is to determine what the AFC DAC value needs to be in order
to center the VCTCXO frequency. The PCS transmitter is turned on and no TX baseband
modulation is provided. The carrier then is centered in frequency. This is done to the carrier after it has been mixed up to 1880 MHz, since it is easier to measure the tolerance of
1 ppm at 1880 MHz than it is at 19.2 MHz. Additionally, the tone at 1880 MHz can be
measured without taking the phone apart.
The result of this test is a PDM value for the AFC DAC, which must be within +/- 150,
corresponding to 2.2v on the VCTCXO control pin (pin 1) and the carrier centerd within
+/- 100Hz. The VCTCXO must be able to be centered within a certain voltage range in
order to allow for aging of the crystal (the centering voltage slowly drifts over time and
the phone will eventually run out of voltage range if it begins too close to the edge of
the range).
Manual Verification: Using the “RF Main Mode” dialog box in Phoenix, turn on the PCS
transmitter and set it to channel 600. Do not add any modulation. Using the RF Tuning
window, set Mode=RF Tuning, and choose this tuning. Look for a transmitted tone on the
spectrum analyzer at 1880 MHz. If no tone is present, proceed to Troubleshooting below.
Center the carrier to within +/- 100 Hz of 1880 MHz. (If sidetones are present, be careful
to center the carrier and not one of the sidetones.) The values you enter into the Values
edit box are the AFC values that control the VCTCXO frequency. Start with a value of “0”,
adjusting until it is centered, staying within the set limits.
Troubleshooting:
1If there is no tone, probe pin 3 of G501 for a tone at 19.2 MHz. If this is not
present, check power supplies, particularly ensuring 2.7v on VCTCXO Vcc pin,
pin 4 of G501. Also check the control pin (pin 1 of G501) for a voltage between
0.4 and 2.7v. If the voltages are correct, and soldering of all G501 terminals is
correct, replace G501. If 19.2 MHz tone is present but tone at 836.52 MHz is not,
troubleshoot Cell TX Chain section.
2If the carrier is present but the PDM needed to center it is outside of the +/- 150
range, or if it cannot be centered, there is a hardware problem.
3In the following procedure, performing frequency centering on the RF carrier at
1880 MHz will detect frequency errors due to the VCTCXO and supporting hardware, which will be the majority of the problems, but will not detect frequency
errors due to the hardware that mixes the VCTCXO tone at 19.2 MHz up to
1880 MHz. In order to also troubleshoot this hardware, frequency centering
should be performed on the 19.2 MHz tone to +/- 19.2 Hz on pin 3 of G501,
using a frequency counter. Then the VHF and UHF LOs should be checked. (Since
this will be time-consuming and will probably only account for a small percentage
of the failures, it is not recommended unless the situation justifies the time spent.)
The VHF LO is inside the Robin IC (N601) and troubleshooting of the Cell UHF LO
is according to Table 2.
4If the carrier can be centered, but the PDM is out-of-range, check the control
voltage on pin 1 of G501. If it is 2.2v (and pin 4 is at 2.7v and pin2 at 0v), then
the VCTCXO (G501) is working correctly but the circuit that delivers the control
voltage is not. Check soldering of all G501 terminals; also check R510, R511,
C503, and D200. If the control voltage on pin 1 of G501 is not 2.2v, but the carrier is centered, then there is a problem with the VCTCXO G501. If there is 2.7v on
pin 4 and the soldering is correct, then replace G501.
5If the carrier cannot be centered, check to see if you can adjust to 2.2v on pin 1
of G501. If you can, within the PDM range of +/- 150, then the circuitry that
delivers the voltage is working correctly, and the VCTCXO has a problem. Troubleshoot as described in the previous section. If you cannot adjust to 2.2v within the
accepted range, then the AFC circuitry has a problem. Troubleshoot it as
described in the previous section.
6If there is a fault with both the AFC circuitry and the VCTCXO, then several com-
binations of the previously described conditions are possible. Start by ensuring
2.2v on pin 1 of G501, using a PDM within the range of +/- 150. Then center the
phone.
TN TX DC Offset Reference Power
Both this tuning and the next (TN TX DC Offset Carrier Suppression) are to adjust the
DC offset voltages on the I and Q inputs to the modulator for minimal carrier
feedthrough (maximum carrier suppression). Initially, the DC offsets are set to a nominal
value, and the power of a tone offset in frequency 20 kHz from the carrier is measured in
dBm and recorded as a reference (in this tuning). Then, in the next tuning, the carrier
suppression (delta between center tone and tone that is offset 20 kHz) is measured. If it
passes, it is reported in that tuning. If not, the DC offsets are adjusted until it passes, and
the passing value is reported.
The reported result is the power in dBm of the tone that is offset 20 kHz from the carrier,
as measured on the antenna connector, with the nominal DC offsets applied.
Manual Verification: In Phoenix, use the RF Main Mode dialog box to set the AMPS
transmitter to channel 384. Using the RF Tuning dialog box, set the I and Q DC offsets to
0,0 by entering 0,0 in the Values edit box. Center the transmit signal on the spectrum
analyzer, set the span to 100 kHz. Lower the bandwidth so that the two sidetones can be
differentiated from the carrier. Measure the amplitude of the sidetone at 20 kHz above
the carrier. The amplitude of the sidetone will probably be higher than that of the carrier.
The amplitude should be within the test limits.
Troubleshooting: If the carrier is not present, troubleshoot the cell TX chain using the
“things to check” list and probing table/diagrams. If the two tones offset at 20 kHz are
not present, check for them with an oscilloscope on one of the four pads of probing
point 1 in Figure 1, being very careful not to short the pad to an adjacent pad. The frequency should be 20 kHz. If tone is not present on these four pads, then there is a problem with D200 (UEM). If the tones are present at probing point 1 but not on the TX
signal, check to see if they are on Robin output at L613 at 836.52 MHz + 20 kHz. If not,
there is a problem with N601 (Robin). Ensure power supplies to Robin (VR2, VR3, VR6,
and VIO) are correct. Check components around Robin. If still failing, replace Robin.
(See TN TX DC Offset Reference Power) tuning section. This step reports the delta
between the reference at 836.52 + 20 kHz and the minimum carrier level at 836.52 MHz.
The result is a delta in dB between the reference at 836.52 MHz + 20 kHz and the minimum carrier level at 836.52 MHz found by adjusting the DC offsets for I and Q individually. The delta should be at least 35 dB.
Manual Verification: Set up the phone as in the previous test, and record the reference
power of the offset tone. Measure the delta between the center and offset tones. If the
delta is 35 dB or greater, the phone passes. If less than 35 dB, vary the “I” DC offset on
the “Values” line in the RF Tuning dialog box, using the values listed below until the minimum carrier maximum delta is found. Leave Q at 0. On the “Values” line, enter “I,Q”. The
appropriate values (in decimal) are:
-560
-504
-448
-392
-336
-280
-224
-168
-112
-56
0
56
11 2
168
224
280
336
302
448
504
560
If the minimum is 35 dB or greater, the phone passes. If the minimum is less than 35 dB,
then vary Q in the same manner as I, using the above values, holding I constant at the
minumum value determined above, until the delta is at least 35 dB.
Troubleshooting: Check N601 (Robin), D200 (UEM), and associated components.
TN TX IF AGC Cell Po (O) [or (1), (2), (3), or (4)]
The IF gain curve is characterized by varying the TX_IF_AGC and measuring the transmit
power. This is only done once (in cell CDMA mode) since the same circuitry is used for
both cell.
The results are TX power readings in dBm of the transmitted signal corresponding to
given PDM settings of the Cell TX IF AGC.
Manual Verification: Set the phone in local mode; then program it to Cell CDMA RX/TX
mode on channel 384. Set modulation to IS95 voice. Set the Cell PA PDM to +218 decimal and the TX RF AGC to -512 decimal, using the sliders in the PDM dialog box under
the RF drop-down menu. Change the TX_IF_AGC to the settings in the following table
and measure the TX power levels, checking to see that they are within the specified
range.
PDM for TX IF AGCAcceptable range for output power (in dBm)
(a) +300 decimalcheck tuning
(b) +150results file
(c) 0for limits
Change the TX_RF_AGC PDM to +511. Leave the TX_IF_AGC at 0 and the PA_AGC at
+218. Measure the output power. Subtract this power from the power measured in (c)
above. This is the RF_AGC gain delta.
Leave the PA_AGC and TX_RF_AGC values as is; then enter the alues listed below for the
TX_IF_AGC. Measure the output power, then add to each the RF_AGC gain delta calculated above. Check that these sums are within the listed ranges.
PDM for TX IF AGC
-200check tuning results
-400file for limits
Acceptable range for sum:[output power +
RF_AGC gain delta], in dBm
Troubleshooting: Check Robin (N801) and supporting components. Also check D400,
which generates the PDM signals. Check AGC PDM voltages according to Tables 1 and 4.
Troubleshoot the rest of the transmitter chain, if necessary.
TN PA Gain Cal Cell Po (0) [or, (1), (2), (3), (4), or (5)]
These tunings model the cell PA gain curve by setting the PA AGC PDM to several values
and measuring output power. First, the TX PA AGC and the TX RF AGC are set to (approximately) their maximum used values (not the maximum possible values, but the maximum of the range over which they are used). Then, the TX IF AGC is set so that the
transmit power on the antenna connector is approximately +11 dBm (this power is
reported in the next tuning, TX TX IF 11 dBm Set CELL Po). Then, six PDM values are
written to the PA AGC and the output power is measured for each. These values are
reported in this tuning. The software then performs curve fitting to interpolate between
the measured data points.
The result is the transmitted power in dBm for each of the six PA AGC PDM settings
(results labeled 0 through 5).
Manual Verification: Turn on the cell CDMA transmitter in Phoenix, using the RF Main
Mode dialog box, and set it to channel 384. Set modulation to IS95 voice.
Set the TX_IF_AGC PDM to 0 decimal.
Set the PA AGC PDM to +218 decimal.
Set the TX RF AGC PDM to -512 decimal.
Adjust the TX IF AGC PDM so that the transmitted tone at 836.52 MHz measures
+11 dBm +/- 0.5 dB on the antenna connector, using a spectrum analyzer (use 0 as a
starting point).
Note the value obtained in the step above as it will be needed in other Troubleshooting sections.
Write the PDM values listed in the following table into the PA AGC and record the output
power. Check to see if the output power is within the ranges listed on the tuning result
printout. (Limits are not provided in this document as they may change.)
PDM for PA AGCAcceptable range for output power (in dBm)
+218 decimallimit range for Po(5)
-12limit range for Po(4)
-202limit range for Po(3)
-268limit range for Po(2)
-329limit range for Po(1)
-366limit range for Po(0)
Troubleshooting: If the power readings are low, check the AGC voltages as given in
Tables 1 and 4. You can also probe on the PA input as given in Table 2 to find out if the
power level is going into the PA, or if the power level is correct going into the PA but the
PA gain is too low. If the power level going into the PA is too low, probe the TX chain at
all the other points prior to the PA listed in the table to see where the gain is lacking.
When that point is identified, check the soldering of all related components, and replace
components until the fault is found. If the power on the PA input is not low and the PA
AGC voltage is correct, similarly probe the power at all points after the PA to find the
fault—being extremely careful not to short the probing point to ground because this will
instantly destroy the PA. Visually check soldering first, and probe on PA output as a last
resort.
TX TX IF 11 dBm Set CELL Po
See previous tuning (TN PA Gain Cal Cell Po (0) [or, (1), (2), (3), (4), or (5)]). This is
the part of the previous tuning when the TX IF AGC is adjusted so that the output power
is +11 dBm.
The result is a power in dBm. A perfect result would be +11.00 dBm.
This tuning characterizes the RF AGC curve by entering PDM values to the RF AGC and
measuring the output power.
The results are TX power readings in dBm of the transmitted signal measured for each of
the listed PDM settings of the Cell TX RF AGC.
Manual Verification: Set up the transmitter as described in tuning 24.3 above.
Set the Cell PA PDM to -329.
Set the TX_IF_AGC to the value determined in tuning 24.3 above to give +11 dBm on the
output.
Change the TX RF AGC to the settings in the following table, and measure the TX power
levels. Check to see that they are within the specified range.
PDM for TX RF AGCAcceptable range for output power, in dBm
-512 decimalcheck
-67 decimallimits
-22 decimalin tuning
+418results
+511file
Troubleshooting: Check Robin (N801) according to Tables 1, 2, and 4. Also check D400,
which generates the PDM signals. Check AGC PDM voltages according to Table 1. Troubleshoot the rest of the cell transmitter, if needed.
TN TX Gain Comp Cell Po MD (or LO, LM, ML, MH, HM, or HI)
Both this tuning and the next (TX IF dBm Set Cell Po) ensure that the value of TxdBCtr
correctly corresponds to the absolute TX output power. On the midchannel, with TxdBCtr
set to a specified value, G_Offset is adjusted so that the output power is -8 dBm and
that value of G-Offset is recorded (which is an absolute value) in the next tuning. (The
output power in dBm is recorded in this tuning.) After this is done on the midchannel,
the channel is changed to each of the other channels and output power is reported.
(G_Offset is not adjusted on the other channels as it was on the center channel — just
the output power is recorded.)
The result is the transmitted power in dBM, which should be -8.0 dBm +/- 0.5 dB on the
center channel.
Manual Verification: Set the phone to local mode and program it to Cellular (or PCS)
CDMA RX/TX mode on channel 384 (or 600 for PCS), using the Main Mode dialog box.
Using the Phoenix RF Tuning dialog box, choose “mode” = RF Tuning and choose this test.
Adjust G_Offset in the “values” dialog box line until the TX output power (measured on
the RF connector with a spectrum analyzer) is equal to -8.0 dBm +/- 0.5 dB. Use the
G_Offset limit range as a guide to which values to enter.
Once this is done on the center channel, change to each of the other channels and record
the power. Do not adjust G_Offset on the other channels—just record the power. It
should be within the limits listed in the tuning results file.
ChannelCell
Low991
LowMid107
MidLow245
Mid384
MidHigh512
HighMid660
High799
Troubleshooting: If -8 dBm cannot be attained, troubleshoot Cell TX.
TX IF 11 dBm Set CELL Po
See the previous tuning (TN TX Gain Comp Cell Po MD (or LO, LM, ML, MH, HM, or
HI)). This is the part of the previous tuning when the TX IF AGC is adjusted so that the
output power is +11 dBm.
The result is a power in dBm. A perfect result would be +11.00 dBm.
Manual Verification: See previous tuning.
Troubleshooting: See previous tuning.
TN TX RF AGC Cell Po (0) [or (1), or (2)]
This tuning characterizes the RF AGC curve by entering PDM values to the RF AGC and
measuring the output power.
The results are TX power readings in dBm of the transmitted signal measured for each of
the listed PDM settings of the Cell TX RF AGC.
Manual Verification: Set up the transmitter as described in tuning 24.3 above.
Set the TX_IF_AGC to the value determined in tuning 24.3 above to give +11 dBm on the
output.
Change the TX RF AGC to the settings in the following table, and measure the TX power
levels. Check to see that they are within the specified range.
PDM for TX RF AGCAcceptable range for output power, in dBm
-512 decimalcheck
-67 decimallimits
-22 decimalin tuning
+418results
+511file
Troubleshooting: Check Robin (N801) according to Tables 1, 2, and 4. Also check D400,
which generates PDM signals. Check AGC PDM voltages according to Table 1. Troubleshoot the rest of the cell transmitter, if needed.
TN TX Gain Comp Cell (or PCS) Po MD (or LO, LM, ML, MH, HM, or HI)
Both this tuning and the next (TN G_Offset Cell MD) ensure that the value of TxdBCtr
correctly corresponds to the absolute TX output power. On the midchannel, with TxdBCtr
set to a specified value, G_Offset is adjusted so that the output power is -8 dBm, and
that value of G_Offset is recorded (which is an absolute value) in the next tuning. (The
output power in dBm is recorded in this tuning.) After this is done on the midchannel,
the channel is changed to each of the other channels, and output power is reported.
(G_Offset is not adjusted on the other channels as it was on the center channel—just the
output power is recorded.)
The result is the transmitted power in dBm, which should be -8.0 dBm +/- 0.5 dB on the
center channel.
Manual Verification: Set the phone to local mode and program it to Cellular (or PCS)
CDMA RX/TX mode on channel 384 (or 600 for PCS), using the Main Mode dialog box.
Using the Phoenix RF Tuning dialog box, choose “mode” = RF Tuning, and choose this
test. Adjust G_Offset in the “values” dialog box line until the TX output power (measured
on the RF connector with a spectrum analyzer) is equal to -8.0 dBm +/- 0.5 dB. Use the
G_Offset limit range as a guide to which values to enter.
Once this is done on the center channel, change to each of the other channels and record
the power. Do not adjust G_Offset on the other channels—just record the power. It
should be within the limits listed in the tuning results file.
Troubleshooting: If -8 dBm cannot be attained, troubleshoot Cell TX.
TN G_Offset Cell MD
See previous tuning (TN TX Gain Comp Cell (or PCS) Po MD (or LO, LM, ML, MH, HM,
or HI)). This step reports G_Offset.
The result is the value of G_Offset, which gives -8.0 dBm transmitted power.
Manual Verification: See the previous tuning. This is the value of G_Offset needed to get
-8 dBm on the center channel.
Troubleshooting: If G_Offset is not within the limits, troubleshoot the Cell TX.
TN AMPS PL2 Po Mid (or Low, LowMid, MidLow, MidHigh, HighMid, or High)
This procedure tunes the AMPS transmit Power Level 0 on seven channels by adjusting
TxdBCtr. The channels are: Low=991, LowMid=107, MidLow=245, Mid=384,
MidHigh=521, HighMid=660, High=799. The algorithm then interpolates between the
measured points for frequency compensation.
The result is measured transmit power in dBm for power level 0 on each of the seven
channels.
Manual Verification: Set the phone to local mode and turn on the AMPS transceiver to
the channel that failed.
Using the Phoenix RF Tuning dialog box, set “mode”=RF Tuning, and select this test.
Adjust TxdBCtr in the “values” dialog box until the output power is within the limits
(adjusting for cable loss).
Troubleshooting: Troubleshoot the cell transmitter, setting the TX AGC values to those
listed for Power Level 0 in Table 1.
This procedure tunes power levels 3 through 7, all on the center channel. (Power level 0
was tuned in the previous test. Power levels 1 and 2 are the same as 0 for this phone.)
The result is measured trasmit power in dBm for power levels 3 through 7 on
channel 384.
Manual Verification: Use the same procedure as in the previous tuning (TN AMPS PL2
Po Mid (or Low, LowMid, MidLow, MidHigh, HighMid, or High)), but on channel 384
note that the limits are different from the previous tuning.
Troubleshooting: Trouble the cell transmitter, setting the AGCs as in Table 1 for the power
level that failed.
TN TX Limiting Po Cell IS95, Low channel (or LowMid, MidLow, Mid, MidHigh,
HighMid, or High channel)
This tuning provides an upper limit on the transmit power while in Cell IS95 mode. The
reason for this is to ensure that the phone never violates the SAR (Specific Absorption
Ratio) limit, which is a health and safety specification that limits the amount of radiation near the user’s head. The phone is set to transmit and TxdBCtr is adjusted for the
maximum transmit power.
The result is a power level in dBm, which is the maximum allowed. This is done on each
of the seven channels.
Manual Verification: Using Phoenix, set the phone to local mode; then turn on the Cell
transmitter set to each of the channels in the following list.
Using the RF Tuning dialog box, adjust TxdBCtr in the “values” dialog box until the TX
power—measured on the RF connector with a spectrum analyzer—is within the limits on
each of the following channels.
ChannelCell
Low991
LowMid107
MidLow245
Mid384
MidHigh512
HighMid660
High799
Troubleshooting: If the maximum cannot be reached, either a component in the transmitter has too much loss, or not enough gain. Troubleshoot the Cell transmitter with the
phone set to the same channel as the failed channel.
This is the same as the previous tuning (TN TX Limiting Po Cell IS95, Low channel (or
LowMid, MidLow, Mid, MidHigh, HighMid or High channel)), except that CDMA2000
(C2K) modulation is used instead of IS95.
For an explanation of result, see the previous tuning.
Manual Verification: Same as the previous tuning, except choose the CDMA2000 tuning
in the RF Tuning dialog box.
Troubleshooting: Same as previous tuning.
TS ACPR Cell — Low
See the description for PCS ACPR. In cell band, however, the offset is -0.9 MHz
(+0.9 MHz).
Manual Verification: Set up the measurement as described in section 42.3 but turn on
the Cell transmitter to channel 384. Likewise, use the TxdBCtr value for Cell TX Limiting
on channel 384 in IS95 mode. Measure at the center frequency of 836.52 MHz, and the
offset of +/- 0.9 MHz.
Troubleshooting: Refer to section 42.3 and also the Cell TX troubleshooting guide. Cell
band TX decoupling capacitors are C653, C633, C649, C648, C619, C841, C817, C810,
C811, C803.
TN RX IF AGC RXdBCtr (0) [or (1) or (2)]
This tuning calibrates the RX IF AGC curve, because the output power of the IF part of
the Batman IC is not a linear function of RX_IF_AGC. The tuner injects three known signal power levels into the phone’s receiver and, for each one, the phone’s AGC algorithm
adjusts the RX_IF_AGC to get the same amplitude at the output of Batman (although
different amplitudes are going in). From these three points, curve fitting is used to interpolate between measurement points.
The result is a value of RxdBCtr (which corresponds to a value of RX_IF_AGC) for each of
three CW input powers injected into the receiver:
-87.5 dBm, -57 dBm, and -18 dBm
Manual Verification: With the phone in local mode, use the Main Mode dialog to turn on
the AMPS receiver set to channel 384. Using the RF Tuning dialog, perform the manual
tuning three times—each time injecting the CW signal at the amplitudes listed above;
one amplitude per tuning. Each time, record RxdBCtr—which is returned by Phoenix during the manual tuning. For the manual tuning, use the RF Tuning dialog box with
“mode”= RF Tuning, and choose the appropriate tuning name. Ensure that the resulting
value of RxdBCtr is within the limits in the tuning results file.
Troubleshooting: While injecting a signal into the receiver, check the values of RSSI and
RX_IF_AGC PDM value and, if needed, voltage. RSSI should be within +/- 2 dB of the
actual power in dBm on the RF connector. The AGC will try to keep the same amplitude
on Batman output; therefore, if the AGC value is larger than normal, this indicates that
the AGC is compensating for loss in the chain prior to the variable gain amplifier.
After checking RSSI and AGC value, if it is still necessary to probe to pinpoint the source
of the error, use the AMPS probing tables.
This tuning records RxdBCtr (which is automatically adjusted to produce the same amplitude on the receiver output no matter what the input is) for the receiver with the LNA in
HighGain mode, and again with the LNA in LowGain mode. For AMPS, this is done only
on the center channel. For Cell and PCS, it is done over several channels.
The result is a value of RxdBCtr.
Manual Verification: Using Phoenix, choose this tuning in the RF Tuning dialog box.
Inject a CW signal that is 10 kHz offset from the center frequency of the channel that is
being tuned. For AMPS, set the amplitude to -65 dBm. For both Cell and PCS, set the
amplitude to -95 dBm. Record RxdBCtr, which is returned from Phoenix in the lowest
field in the RF Tuning dialog box.
Troubleshooting: Check Alfred and supporting components.
Final UI Test: Rho
Rho is a measure of CDMA transmit signal quality, which encompasses other transmitter
indicators such as phase error and magnitude error. Rho is measured with the phone in a
phone call, and is read directly from the call box. Rho is measured with the sector power
= -75 dBm. If Rho fails, check the signal purity of the LOs. Check synthesizer components
and power supply decoupling.
Final UI Test: Frame Error Rate (FER)
This measurement—also made while in a phone call—measures the frame errors of the
receiver in CDMA mode. A low amplitude signal (typically at a receiver sensitivity level of
-104 dBm), is injected into the receiver, and the FER is recorded. FER is measured in percentage (0.5% or lower is considered passing). Failures are most often caused by excess
loss/insufficient gain in the receiver chain. Failures may also be the result of excess noise
in the receiver. Check for correct signal levels and AGC values/voltages.
Final UI Test: SINAD
SINAD (Signal-to-Noise-and-Distortion) is similar to a sensitivity/FER measurement for
CDMA, but it is used in AMPS. A low-level signal (typically at sensitivity level of -116.0
dBm) is injected into the receiver, and SINAD is read off the call box. The passing limit is
12 dB.
When measuring CDMA transmit signals, if the spectrum analyzer does not have a CDMA
personality card, the CDMA signal power can be approximated by setting the resolution
bandwidth to 1 MHz and using the marker. CDMA signal power is measured by integrating power over a 1.23 MHz bandwidth while the marker measures power at only one frequency.
Probing is generally done in local mode, although situations may arise whereby the troubleshooter may need to probe while in a call. If this is done, be aware that in some cases,
probing may disturb the circuit so that the call drops.
The following tables list power levels for many combinations of AGC values; however, it
generally is only necessary to check one combination. Likewise, although probing points
and signal level information are given for each point in the receiver and transmitter
chains, the troubleshooter is not expected to probe each point on every phone. Only the
suspect trouble spots should be probed.
Absolute power measurements were made with an Agilent (HP) 85024A active high
impedance probe. While other probes may be used, it is strongly recommended that the
probe be high impedance so that the measurement does not load the circuit. Adjust
absolute measurements if the probe has a different gain or if a probe attenuator is used.
If a range is provided for loss, typically the higher loss occurs at the band edges.
Power depends on the impedance of the circuit. For example, if a circuit has a nominal
loss of 5 dB, then straightforward probing on the input and output, then subtracting,
might not result in 5 dB because the input impedance might be different from the output
impedance. However, after mathematically adjusting the power on either the input or
output to compensate for the difference in impedance, 5 dB is then calculated. Most
components in the RF section have the same input and output impedance (50 ohms), but
where this is not the case, absolute power is noted in the tables in dBm, rather than loss
or gain in dB.
When testing the CDMA receiver, it is easier to inject a CW tone into the receiver. The
gains and losses will be the same for a CW signal as for CDMA.
Table 1: Transmit Output Power and Associated AGC PDM values and voltages
channel 384
AMPS
TX RF AGCTX IF AGCProbed RF
PDM valuevoltagePDM valuevoltagePDM valuevoltage
typicalvtypicalvdBmtypicalvdBm
-4090.17-1020.70-11.2 +/- 3 dB-190.8425.5 (PL0)
-4090.17-890.72-13.2 +/- 3 dB-1230.6624.2 (PL3)
-4090.17-730.75-15.4 +/- 3 dB-3100.3419.9 (PL4)
-2490.44-630.77-19.2 +/- 3 dB-3300.3015.8 (PL5)
-1040.70-530.78-22.4 +/- 3 dB-3300.3012.5 (PL6)
370.95-480.79-27.9 +/- 3 dB-3300.308.2 (PL7)
-4030.17-1150.66-16 +/- 3 dB2201.2725
-4030.171161.08-42 +/- 3 dB-2700.40-2
2001.231241.09-58 +/- 3 dB-3310.29-23
4501.681241.09-65 +/- 3 dB-3310.29-39
5111.782071.24-75 +/- 3 dB-3310.29-50
power on
Balun Out
CELL CDMA
PA AGCRF power
on RF connector
Note: AGC PDM values will change (sometimes drastically) as the phone warms up. The table lists
PDM values for initial power up. After 10 minutes at full power, PDM values will be different.
Table 2: RF/Analog Probing for Transmitter
Where to start checking if RF
power not correct (soldering,
shorts, DC power applied if
active, correct voltage of DC
signals, otherwise replace)
D200, N601 (VR2,3,6,IO)
Probing Point
UEM (D200)
out=Robin (N601)
in
Probing
Location on
the board
1, Figure 1Use O-scope. For CDMA modula-
Probed Absolute Power (dBm) or
gain/loss (dB) or voltage (v)
tion turned on, 550 mV p-p, looks
like noise. For AMPS, with test tone
turned on.
4, Figure 1Gain = 12-16 dB through TomcatN603 (also ensure 3.6v on pin 5
5, Figure 1Loss = 2-3 dB through SAW filterZ604, N603, N801 (Vbat)
6, Figure 1.
Probing here
not recommended unless
necessary; best
to measure on
RF connector
Easiest to probe on balun output as
per Table 1. Nominal loss through
balun = 1 dB, but it will appear as
3-4 dB gain due to impedance difference. On Robin output, you may
see amplitude imbalance between
2 sides of probing point 2 due to
impedance differences (less in
Cell).
PA has variable gain, see Table 1.
Best to measure on RF connector.
N601 (ensure VREFRF02 is 1.35v.
Check AGC voltages/PDMs), T604,
L604, L603, C640, C642, C620,
N603 (including check for 3.6v on
pin 5), D400 (including AGC voltage)
L604, N601. C620, N603 (including: check PD_CELL high as in Table
2), N603 (including check for 3.6v
on pin 5 and 2.6v on pin 4)
and PD_CELL high as in Table 1b),
N601, C649, C639, Z604, N801
(Vbat)
Where to start checking if RF
power not correct (soldering,
shorts, DC power applied if
active, correct voltage of DC
signals, otherwise replace)
Probing Point
Probing
Location on
the board
Probed Absolute Power (dBm) or
gain/loss (dB) or voltage (v)
UHF LO at
1009.62 MHz for
channel 384
VHF LO at
346.2 MHz for cell
band, any channel
10, Figure 1.
Can probe on
top of plastic
to check for
presence of LO,
but won’t read
accurate
power
11, Fi g ur e 1
(You can touch
top of plastic
to verify presence of LO, but
this won’t
measure
amplitude
accurately.)
Power approx. -3 dBmIf LO is present but off freq (could
be off by hundreds of MHz), then
VCO G502 is at least putting out a
signal. If LO not present, check
G502, R507, R505, R515 first. Else,
check C511, C501, C532, C550,
R550, C509, R503, C508, R508,
C518, N501, R506, C516, C515,
C521, R513, C504. Lastly, check
R523, R519, R509.