Nokia 7650 Service Manual 11 nhl2 trouble
NHL-2NA Series Transceiver
Troubleshooting Instructions
Issue 2 11/02 Copyright ¤Nokia. All rights reserved
Troubleshooting Instructions CCS Technical Documentation
[This page left intentionally blank]
Page 2 Copyright ¤Nokia. All rights reserved. Issue 2 11/02
CCS Technical Documentation
Table of Contents
Baseband Troubleshooting............................................................................................. 3
Introduction ..................................................................................................................3
General guidelines for NHL-2NA system troubleshooting .........................................3
Troubleshooting paths .................................................................................................6
LG4 Baseband HW subarea troubleshooting ............................................................10
Energy management troubleshooting ........................................................................12
IR interface ................................................................................................................24
Sensors troubleshooting .............................................................................................26
Proximity Detector .....................................................................................................27
Ambient Light Detector .............................................................................................33
SIM card ....................................................................................................................39
Audio .........................................................................................................................43
Memory troubleshooting ...........................................................................................47
Baseband serial interface troubleshooting .................................................................48
Hall sensor troubleshooting .......................................................................................51
Display backlights troubleshooting ...........................................................................52
Bluetooth troubleshooting .........................................................................................53
Needed actions if ASIC is changed.............................................................................. 56
UEM changed ............................................................................................................56
AEM changed ............................................................................................................56
UPP_WD2 changed ...................................................................................................56
Flash0 changed ..........................................................................................................56
RF component changed .............................................................................................56
Test points and pin orders............................................................................................ 57
Test points in BaseBand area (LG4_06_02) ..............................................................57
Connectors pin order ..................................................................................................59
RF Troubleshooting ..................................................................................................... 63
Introduction ................................................................................................................63
RF Key component placement ...................................................................................64
Fault finding test point locations ...............................................................................65
Receiver .....................................................................................................................66
Transmitter .................................................................................................................73
Common ....................................................................................................................79
Receiver tunings ........................................................................................................85
Transmitter Tunings .................................................................................................100
Appendix.................................................................................................................... 108
Frequency mappings ................................................................................................108
UI Troubleshooting.................................................................................................... 117
Introduction ..............................................................................................................117
UI module troubleshooting cases .............................................................................117
Grip-Module Troubleshooting................................................................................... 121
Introduction ..............................................................................................................121
Backlight ..................................................................................................................122
Current Gauge ..........................................................................................................123
Vibra ........................................................................................................................124
Keyboard ..................................................................................................................125
Hall Sensor ...............................................................................................................126
Issue 2 11/02 ¤Nokia Corporation Page 1
CCS Technical Documentation
Camera Troubleshooting Instructions........................................................................ 127
Background, tools and terminology .........................................................................127
Image taking conditions effect to image quality ......................................................128
Camera construction ................................................................................................134
Image quality analysis .............................................................................................135
Fault finding trees ....................................................................................................141
Page 2 ¤Nokia Corporation Issue 2 11/02
CCS Technical Documentation
Baseband Troubleshooting
Introduction
This document is intended to be a guide for localising and repairing electrical faults in
the NHL-2NA device. First there is a brief guide for fault localising. Then fault repairing is
divided into troubleshooting paths.
Before any service operation you must be familiar with the NHL-2NA product and module level architecture. You also have to be familiar with the NHL-2NA specified service
tools such as the Phoenix service software, flashing tools and software.
General guidelines for NHL-2NA system troubleshooting
Tools needed for troubleshooting
• Service tools (as listed at service tools chapter in service manual)
• Laboratory power supply with current indicator
• Oscilloscope
• Digital multimeter
General guidelines
General notes about the NHL-2NA product:
• Large colour display
• Keyboard on grip part, rocker, two softkeys and application key under display +
side keys (power key and IHF enabling key)
• Flex cable carries signals between LG4 and LS4 boards. Battery and charger plug
is in grip part, so if the flex is damaged phone cannot be powered on.
• UI-module (display, backlights etc.) is also connected to LG4 module with flex
cable.
• If the component reference is under 100, component is located at the LS4 board.
And if the component reference is over 100, component is located at the LG4
board.
When you get a faulty NHL-2NA device and you start to troubleshoot it, first check the
following items:
• If the device cannot be turned on by any means, see “dead device” troubleshooting
• Current consumption (missing consumption) gives an idea wether the device is
able to start up.
• Dropping supply voltage or very large current consumption indicates a short circuit
• Check wether the connection with Phoenix works and what can be discovered
with Phoenix (ADC-readings, baseband selftest, bb-calibrations etc.)
• Check baseband selftests with Phoenix if “CONTACT THE RETAILER.” is shown on
the display.
• Check visually display and rocker faults
• Force phone to LOCAL mode and make keyboard test by phoenix
Issue 2 11/02 ¤Nokia Corporation Page 3
CCS Technical Documentation
• Check that board-to-board connector, hotbar and adapter connections are OK,
and connectors make good contacts.
• If liquid damage, stop repairing!
If some module (eg. Camera, display, grip) is not working:
• Try working module
If this not helping
• Check supply voltages for failed module
• Check clock(s) for failed module
=> Go to relevant chapter of this document
Flash phone before disassembling it if fault is not obvious and Phoenix connection is
OK.
Dissasemble phone:
Try to locate failed module, is it LG4, LS4, UI or camera module.
• Check failed module visually:
Mechanical damages?
Solder joints OK?
Continue with specific troubleshooting procedure for the module:
• If there is an obvious fault, repair it before reflashing the device
• Flash first if a fault is not obvious
If flashing is not working go to flashing troubleshooting
Due to CSP packages short circuits or broken solder joints are not easily seen. If the
examined signal seems to be continuously in low or high level, then measure for possible
short circuit to ground (signal low) or to supply voltage (signal high) Note that if a problem is not found from any visible contact/component it can be under CSPs where the signal is connected.
Care must be taken when assembling and disassembling the tranceiver. Failure to do this
may result in unnecessary damage to device.
NOTE! if some ASIC is changed see chapter Bluetooth troubleshooting
Nominal current consumption
NOTE: Service tools need some amount of current to work. (FLA-21: 1-2mA and MJF-9Q:
2-6mA
Page 4 ¤Nokia Corporation Issue 2 11/02
CCS Technical Documentation
The following current consumption values are measured from a complete NHL-2NA.
Vbatt = 3.8 – 4.2V
Measured nominal currents are drawn from the main battery.
Measurements have been made with a current probe connected to an oscilloscope.
Operating mode
Idle (BT off) 4-8 mA
2w audio call (backlights off) channel37 300-340mA
Viewfinder + nominal backlights 232mA
Current consumption
Issue 2 11/02 ¤Nokia Corporation Page 5
Troubleshooting paths
Dead or jammed device
CCS Technical Documentation
Page 6 ¤Nokia Corporation Issue 2 11/02
CCS Technical Documentation
Partially damaged device
If the device is working, but some functionality is missing try to localize where the problem is and see relevant part of this manual. If, for example, audio is not working see
chapter Audio Troubleshooting, if charging is not working see chapter Charging Troubleshooting, etc.
Most common symptoms reported by customer
In this section is described most common symptoms reported by customers when the
device is brought to service. Some tips where the trouble can be found are also given.
When troubleshooting use these tips and follow the given troubleshooting path.
Most common symtoms for audio problems can be:
“Earpice sound is missing”
”Handsfree sound is missing”
”Headset is not recognized”
”Microphone is not working”
”Volume cannot be adjusted”
” Ringing tones do not work”
”Audio volume too low”
If symptom is something like above see audio troubleshooting.
Most common symptoms for Irda and bluetooth problems can be:
“Irda does not work or it does not make a connection”
”Bluetooth does not work or connection cannot be established”
If symptoms are something like those, start to follow Irda or bluetooth
troubleshooting guidelines gave relevant chapters.
Symptoms related to energy management:
“Phone does not stay on”
”Charging is not working”
”Time is lost during battery change or short main battery removal”
”Charging takes too long”
”Operating time is very short”
These symptoms lead to relevant part of energy managemant troubleshooting
If the sensor/sensors are out of order description of symptoms can be like below:
“IHF is not disabled automatically when phone is put near ear”
“IHF cannot be enabled”
“Backlight is always ON or OFF”
“Backlight of display does not go OFF”
Issue 2 11/02 ¤Nokia Corporation Page 7
In cases above see Chapter Sensors Troubleshooting or Backlight Troubleshooting
Problems in UI-module:
“UI-module keypad is not working”
”Joystick is not working”
”Backlight is dim”
”Baclight not even”
”Backlight is blinking”
”Keypad or display backlight is not working”
”Display related problems”
See UI- module troubleshooting.
Most common RF related symptoms:
“Call cannot be made”
”Phone does not find signal”
”Call is often dropped”
CCS Technical Documentation
See RF troubleshooting
Problems with camera can cause symptoms as:
“Bad image quality”
”Picture cannot be taken”
See camera module troubleshooting
Problems in LS4 can cause symptoms below:
”Backlight of grip is dim”
”Baclight of grip not even”
”Backlight of grip is blinking”
”Grip keypad is not working”
”Vibra is not working or is noisy etc.”
See grip- module troubleshooting.
Contact the retailer” on display
“Contact the retailer.” on display (Self-tests by Phoenix)
Display information: “Contact the retailer”
Page 8 ¤Nokia Corporation Issue 2 11/02
CCS Technical Documentation
This fault means that software is able to run and thus the watchdog of UEM can be
served.
Selftest functions are executed when the phone is powered on and if one or more selftest functions fail, the message “Contact the retailer” is shown on the display.
MCU selftest cases can be split into two categories: The ones that are executed during
power up and the ones that are executed only with a PC connected. These tests and the
items included are as follows:
Figure 1: BB selftest-tool
If a selftest fails, see relevant chapter in this troubleshooting manual.
Issue 2 11/02 ¤Nokia Corporation Page 9
LG4 Baseband HW subarea troubleshooting
B
C
Flashing troubleshooting
NHL-2NA has three memory components installed on the main pwb. The best indication
of which one is causing problems can be obtained by flashing the device. It has to be
kept in mind that all three memory components are interfaced with UPP WD2 asic that
might itself have some problems. The necessary steps are described below. Phoenix error
messages during flashing greatly help on defining what is wrong. To be able to flash the
device, most device BB area components must function properly.
Flashing
faults
CCS Technical Documentation
C101 "Boot
timeout" or
C102 "boot start
txd fail"
message
?
No
C103
"Boot serial line
fail" message
?
No
C106
"Secondary
receive fail"
message
?
Yes
Yes
Yes
Measure BSI
pulse during
flash
programming
Is it ok?
Yes
Measure
I_FBUS_TX(J121)
line during flash
programming is it
1.8V?
Yes
No
Check connections
Check BB voltages
heck clocks
Check BSI line
attery connector, flex,
C239, Z383, R384
Change
UEM(D190)
No
Change UPP
WD2(D100)
No
Change UEM(D190)
Change
UPP_WD2(D100)
No
C202
"Algorithm
send" or C281
"phone message
chksum" fail
?
No
Sleep
clock(J101) ok ?
Yes
Yes
Flashing
faults page
2
Page 10 ¤Nokia Corporation Issue 2 11/02
CCS Technical Documentation
C
Flashing
faults page
2
No
C108
"Prommer
message about
sdram failure"
?
No
Yes and sdram
allready changed
Yes
No
Activity in sdram
clk(J108) pad?
Yes
Change
UPP_WD2(D100)
Change
SDRAM(D312)
A204
"Wrong
manufacturer ID
and device ID"
message
?
No
C385
"Data block
handling timeout"
message
?
No
C586
"Phone fail
responce" or C684
"Data blok Nak"
message
?
Yes
Yes
Yes
hange Flash Chip according
to Phoenix messages
If both chips report wrong
ID's -> change
UPP_WD2(D100)
Bluetooth module is unable to start
flashing ->
Check V590,R591,R593-596,C594
and C595 -> still not ok
-> change BT module
Check flash0 bypass caps, check
Vpp connection to flasher, Check
R314(4.7k)
Ok->Change flash0(D311)
No
Flashing
successful/Retest
Issue 2 11/02 ¤Nokia Corporation Page 11
Energy management troubleshooting
Device does not stay on
If the device is switched off without any visible reason, there may be problems in the following areas:
• UEM watchdog problem (WD is not updated by SW)
• BSI line problem (BSI line is floating => contact failure)
• Battery line problem
• Soldering problem
The most likely reason is UEM WD (watchdog), which turns the device off after about 32
seconds if SW is jammed.
This may be caused by a SW problem, UPP_WD2 problem (Not server by SW), UEM, AEM
or memory malfunctions.
The following tests are recommended:
CCS Technical Documentation
• General power checking
•Clocks
•Memory testing
• Serial Interface
If there is something wrong in BSI line, the device seems to be dead after the power key
is pressed. However the regulators of the device are on a few seconds before the powerdown.
This mode can easily be detected from the current consumption of the device. After a
few seconds the current consumption drops almost to 0 mA.
In this case check components listed below or soldering:
Battery connector X002
Grip connector X001 (especially pin number 27)
Hotbar soldering X380 (especially pin number 5)
EMI-filter Z383 (especially pins number A4 and E4)
UEM D190 (pin number C2)
If phone boots to TEST or LOCAL mode with normal battery, BSI or Btemp or both lines
are short circuited to ground. Check varistors, EMI-filter and filtering capacitors, which
are located to BSI and Btemp lines.
General power checking
Use service tool FLA-21. Battery voltage should be atleast 3.6V. After phone disassembly,
use module jig MJS-9Q.
Page 12 ¤Nokia Corporation Issue 2 11/02
CCS Technical Documentation
.
Issue 2 11/02 ¤Nokia Corporation Page 13
SMPS of AEM troubleshooting
CCS Technical Documentation
Page 14 ¤Nokia Corporation Issue 2 11/02
CCS Technical Documentation
Power key troubleshooting
Issue 2 11/02 ¤Nokia Corporation Page 15
Clocks troubleshooting
C
S
S
C
S
D
The main clock signal for the baseband is generated from the voltage and temperature
controlled crystal oscillator VCTCXO (G591). This 26 MHz triangle wave clock signal is
supplied to OSC_IN pin of HAGAR. Inside HAGAR the clock frequency is divided to 13
MHz and then fed to RFCLK pin of UPP_WD2 and Bluetooth.
In SLEEP mode the VCTCXO is off. UEM generates low frequency clock signal (32.768
kHz) that is fed to UPP_WD2, Bluetooth and AEM.
CCS Technical Documentation
RF
VCXO
RF-ASIC
(Hagar)
LPRF
RFClk
13 MHz
RFBusCl
Flash
Clk
FLASHes
UPP_WD2 UEM
leepClk
BusCl
BusCl
IMCl
SIM
AEM
DRAM
lk
CAMERA
SDRAM
When the flashing of the device does not succeed, but powering is OK, follow these
instructions.
Note: The absence of clocks may indicate that the device (put phone to LOCAL mode
when the sleep is not allowed or press buttons so that phone is not in sleep mode) is in
sleep mode. Make sure that the device is not in sleep during RF clock measuring.
Ω
IMPORTANT: Clock signals have to be measured with 1M
(or greater) probes!
Page 16 ¤Nokia Corporation Issue 2 11/02
CCS Technical Documentation
1 Measure signal from R596. This should be 26Mhz clock signal. See figure below.
If the clock not exist, check voltage from C662, it should be 2.78V (UEM regulator VR3). If voltage is OK, check G591 and other componets around it.
Figure 2: 26 Mhz clock
2 Check 13Mhz Rfclk from testpoint J100. See figure below. Offset should be
about 900mV. If the offset does not exist something is broken inside UPP_WD2
or DC-filtering capacitor in series on trace.
Figure 3: 13 MHz clock
Issue 2 11/02 ¤Nokia Corporation Page 17
CCS Technical Documentation
3 Check is the crystal oscillator (B190) oscillating at 32.768kHz frequency. If not
change B190. If OK measure sleepclk from testpoint J101. Frequency should be
the same 32.678kHz (see figure below.) If not change UEM.
Page 18 ¤Nokia Corporation Issue 2 11/02
CCS Technical Documentation
Charging checking
Use the BLB-2 battery and JBV-1 calibration set to test charging. (NOTE: power supply
cannot be charged if it not has a current sinking capability.) When you are charging
totally empty battery, remember that start-up charging might take a little bit longer time
than normal. During this time display is blank.
If charger is not NMP approved type and its current and voltage is not within NMP
charger window then software does not start charging and there is “NOT CHARGING” on
the display. Voltage should be between 5.5V - 9.3V and current between 200mA –
850mA
Remove and reconnect battery and charger few times before you start to measure
device. This check ensures that the fault really exists.
Issue 2 11/02 ¤Nokia Corporation Page 19
CCS Technical Documentation
Page 20 ¤Nokia Corporation Issue 2 11/02
CCS Technical Documentation
Issue 2 11/02 ¤Nokia Corporation Page 21
Energy management calibration
During energy management calibration A/D-converter, BSI, Btemp, Battery voltage,
Charger voltage and Charger current are calibrated. For detailed information and
instructions see EM-calibration instructions in service manual.
Troubleshooting tips:
ADC-offset over limits:
Inspect BSI line, connectors (hotbar and board to board connector) and components in it
(Varistor R008, EMI-filter Z383, Pull-up resistor R384). If these are OK, change UEM.
BSI Gain over limits:
Inspect BSI line, connectors (hotbar and board to board connector) and components in it
(Varistor R008, Capacitor C002, EMI-filter Z383, Pull-up resistor R384). If these are OK,
change UEM.
Btemp Gain over limits:
Inspect Btemp line, connectors (hotbar and board to board connector) and components
in it (Varistor R006, Capacitor C010, EMI-filter Z383, Pull-up resistor R383). If these are
OK, change UEM.
CCS Technical Documentation
Vbatt offset and Gain:
Inspect Vbatt lines and component in it.
Vchar over limits:
Inspect components which are connected Vchar line: Filtering capacitors C005, C006,
C011, TVS V009, L001 and Fuse F001. If those are OK, Change UEM
Ichar over limits:
Inspect components which are connected at Vchar line: Filtering capacitors C005, C006,
C011, TVS V009, L001 and Fuse F001. If those are OK, First change current sense resistor
(R190), if calibration is not still successful change UEM.
Calibration can be checked using ADC-redings. Known voltages, currents and resistances
are fed and read by ADC-readings, read values and known values can be compared.
Page 22 ¤Nokia Corporation Issue 2 11/02
CCS Technical Documentation
ADC-reading
Divided and scaled battery voltage, Charger voltage, Charger current, BSI and Btemp values can be read by this tool. Read values few times before you can be sure that results
are accurate.
Figure 4: ADC-readings view
Note:: If Vbatt Scaled and Divided unit results are different default calibration values
are used. In this case perform EM-calibration to get full performance of phone.
Maximum tolerances are:
Reading
Vbatt SCAL 4.2V ± 25mV
Vchar 8.4V ± 40mV
Ichar 500mA ± 20mA
BSI 68k(BLB-2) ± 1.3kohm
Btemp 273K(47k) ± 5K
Backup battery
Symptom of backup battery fault is:
Real Time Clock loses the correct time during short main battery removal.
The same syptom can also be seen when the backup battery is empty. About 5 hours is
needed to fully charge the backup battery in the device. NOTE: Backup battery is charged
only the same time with main battery charging. Or when the device is LOCAL or TEST
mode.
Check point Tolerance
Issue 2 11/02 ¤Nokia Corporation Page 23
CCS Technical Documentation
Always check that the backup battery visually for any leakage or any other visual defect.
Check that the backup battery is correctly mounted in the device before closing the
cover.
1 Check with Phoenix is backup battery OK
2 Measure the voltage of backup battery
• Normal operation when the voltage is > 2.0V
• Fully charged when the voltage is about 3.2V (because of large internal imped
ance voltage won’t stay above 3.0V a long time after charging is disabled)
3 Enable backup battery charging (start to charge main battery or boot device to
LOCAL or TEST mode)
4 Measure voltage of backup battery during charging, It should arise if it is not
3.2V, yet.
5 When the voltage is over 2.0V for sure, check backup battery with Phoenix.
-> If not OK then D190 is faulty.
6 Ensure that the RTC is running.
IR interface
0. IR test
1. IR test
s
e
y
2. IR ok
Re-flash,ifnot
working its
beyond
economical
repair
no 3. IR selftest
4. Remove Acover (refer to
disassebly
instructions)
5. Repeat IR
no
6. Replace IR
module, repeat
s
e
y
test
noyes
test
2. IR ok
o
n
e
y
s
4. Remove Acover
Replace A-
cover
5. Repeat IR
test
yes
soldering of
GND (pins 5
soldering of
serial resistors
and capacitors,
o
n
8. Check
Vcc and
and 8)
yes
10. Check
the rest of
the pins.
s
e
y
7. Replace
repeat test
7. Replace
serial resistors
and capacitors,
repeat test
no
Beyond
economical
repair
no
no
no
yes
9. Check
capacitors
C360-363
o
n
Fix and repeat
test
6. Replace IR
module and
test again
no
If test fails after
re-flash, phone
is beyond
economical
repair
2. IR ok
yes
PWB fail
s
e
y
no
Page 24 ¤Nokia Corporation Issue 2 11/02
CCS Technical Documentation
0. At this point it is supposed that problem is in HW
1. Send something to another phone or laptop
2. Everything is ok
3. Activate phones IrDA selftest
4. Take off phones A-cover
5. Start test again from the beginning, there might be more than one fault...
6. Solder a new IrDA module to phone, start test again.
7. Replace resistors R360 – R363 and capacitors C360-C363
8. Vcc in pin 5 should be connected to VMEMA
9. Check capacitors C360-363 for shorts and open contacts
10. Pin 1 (Anode) should be at battery voltage, pin 2 (Cathode) should be floating, pin 3
(Tx), pin 4 (Rx), pin 7 (mode) should be grounded.
Issue 2 11/02 ¤Nokia Corporation Page 25
Sensors troubleshooting
This part of document is written to help troubleshooting for proximity sensor and ambient light sensor in NHL-2NA. Both of them are calibrated in production, in FINUI tester.
AMS has possibility to calibrate proximity sensor at service points, ambient light sensor
is repaired in Bochum.
This document is ment to be used only in troubleshooting and does not provide information on basic functionality of the systems. Basic operating principle can be found in
chapter “System Module LG4 and Grip Module LS4”, calibration instructions can be
found in chapter “Service Software Instructions”.
CCS Technical Documentation
Page 26 ¤Nokia Corporation Issue 2 11/02
CCS Technical Documentation
Proximity Detector
General notes
In the production proximity detector problems are best located from calibration results.
Before starting troubleshooting with the help of this section, user should familiarize to
the calibration instructions.
When the user brings the phone to the service point complaining that handsfree won’t
turn on, the problem can be either in the handsfree speaker circuitry, or in the proximity
detector. This chapter gives instructions how to repair the problem in the proximity
detector.
A good indicator that the proximity detector has caused disabling of the loudspeaker is,
that the phone has switched the audio back to the earpiece. If the audio is not switched
to the earpiece but also loudspeaker is not on, the problem is most likely in the handsfree
circuitry.
When the problem is located on the proximity detector, always replace lens module
before proceeding to detailed troubleshooting.
If the problem is not this simple, the best way to look for the problem is to use PD calibration results.
Remember that Proximity Detector has to be calibrated always when optocomponents or
optics are replaced! Calibration also has to be done, if AEM ASIC is replaced or if calibration settings are lost from PMM.
Proximity Detector components
From now on Proximity Detector will be referred to as PD.
Main components of PD are lenses, emitter (IRED CL-200-IR, V334, 4860009), RSENSE
4R3 (R347), receiver (photodiode BPW34FS, V335, 4864911) and a control block, which is
located on AEM ASIC (N226). Three external capacitors are part of the control block:
100n (C275) and 220p (C273 and C274).
Issue 2 11/02 ¤Nokia Corporation Page 27
CCS Technical Documentation
Figure 5: Most important receiver and transmitter components
V334 V335
Handsfree shuts down automaticallly in sunshine
It is normal, if this behaviour occurs only in high ambient light conditions, e.g. direct
sunlight, and no repair actions are needed. If this problem occurs also in low ambient
light conditions (outdoors when the phone is not facing the sun), check that capacitors
C273, C274 and C275 are placed correctly. Replace the lens module and recalibrate the
system.
PD calibration
Proximity Sensor Calibration tool is shown in the Figure 4 Proximity Sensor Calibration
tool. Parameters that are calibrated and saved to PMM are gain, detection threshold and
fault detection threshold. When you start the calibration tool, the values in the PMM are
shown in the left column. Second column shows start values used in calibration, they
are defined by R&D. Calibration consists of two phases. First gain and detection threshold are calibrated. If this calibration is finished successfully, software starts fault threshold calibration; fault threshold cannot be calibrated alone. Offset value(s) are used to
adjust the thresholds to compensate possible wearing of the PD. To help troubleshooting
phone SW response is one of the 13 messages that are explained in the next chapter.
Successful gain and detect threshold calibration tells that optoelectrical components are
OK. Note! Values in this picture might change.
R347
C275
Figure 6: Proximity Sensor Calibration tool
Page 28 ¤Nokia Corporation Issue 2 11/02
Loading...