User Guide

ManualsBrandsNokia ManualsMobile Phones3320

Programmes After Market Services

NPC-1 Series Transceivers

Issue 1 10/01 ãNokia Corporation

Troubleshooting Instructions

Summary of content (34 pages)

PAGE 1
Programmes After Market Services NPC-1 Series Transceivers Troubleshooting Instructions Issue 1 10/01 ãNokia Corporation
PAGE 2
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Table of Contents Page No Troubleshooting Instructions ..........................................................................................1 Transceiver Troubleshooting ......................................................................................... 4 Baseband Troubleshooting ..........................................................................................4 General about testing........................................
PAGE 3
PAMS Technical Documentation NPC-1 Troubleshooting Instructions List of Figures Page No Fig 1 Power up sequence .....................................................................................................7 Fig 2 Fault tree, phone does not power up...........................................................................9 Fig 3 Fault tree, charging .....................................................................................................13 Fig 4 Fault tree, earpiece fail .............
PAGE 4
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Transceiver Troubleshooting The Troubleshooting instructions are divided into following sections: 1 How to check/fix the system/sleep clock. 2 How to check/fix the power supplies. 3 Contact service case. 4 How to check/fix the SIM faults. 5 How to check/fix the Audio faults. 6 How to check/fix the charger faults. The first thing to do is to carry out a thorough visual check of the module.
PAGE 5
PAMS Technical Documentation 1 NPC-1 Troubleshooting Instructions Pressing the power key. 2 Connecting the local/test mode resistors to the bsi/btemp lines and connecting the battery voltage to the phone. 3 Connecting a charger. 4 Phone’s internal functions (Real time clock alarm) In the local and test mode, the baseband can be controlled through MBUS or FBUS (FBUS is recommended) connections using Phoenix service software.
PAGE 6
NPC-1 Troubleshooting Instructions PAMS Technical Documentation 8 Infrared Power up faults Power up sequence 1 The UEM acts as a HW master during start up • Vbatt limits: 2.
PAGE 7
PAMS Technical Documentation NPC-1 Troubleshooting Instructions Note: In figure below, the RF_Clk frequency appears to be lower than 19.44MHz because of a too low oscilloscope sampling frequency (2kS/s). Figure 1: Power up sequence 1 Power key pressed • After 20ms UEM enters RESET MODE if VBAT>Vmstr+ • VFLASH1, Vana, Vcore, Vio and VR3 goes high. • VCTCXO enabled by VR3 -> RFClk 19.44 MHz running.
PAGE 8
NPC-1 Troubleshooting Instructions PAMS Technical Documentation • Default value for Vcore is 1.5 volts and, if the software is running, Vcore will rise to 1.8 volts. • Cbus (1.08MHz) clock starts running. Phone does not start up normally or does not stay on Note: In case of power up faults, it is not possible to force the phone on by disabling the watchdog.
PAGE 9
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Figure 2: Fault tree, phone does not power up Try to start phone to test or local mode OK Check the power key OK FAIL Measure Vflash1,Vana,Vio,Vcore ,VR3when pwr key pressed OK FAIL VANA & VR3 missing Check G790 (missing, misaligned) Check R202, R205, C217, C220 OK Check X101 OK FAIL Measure VBAT from C261 Check 19.44MHz RF-clock from C420 FAIL Check C420 OK OK OK Check Check FAIL 19.
PAGE 10
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Flash Programming does not work Flash programming procedure 1 The phone communicates with the prommer via the production test pattern, using the following signals: • FBUSTX(serial data to phone) • FBUSRX(serial data from phone) • MBUS(serial clock for FBUSRX) • VPP(External flashing voltage for speed up flashing) • The BSI line is also used when initializing flashing (battery connector).
PAGE 11
NPC-1 Troubleshooting Instructions PAMS Technical Documentation 11 The FLASH Program includes a package of MCU and DSP software and all default parameters for the phone. The tuning values will be added/rewritten during the Flash/Alignment phase. Flash programming error codes The various error codes can be seen from the "FPS-8 Flash" in Phoenix. The underlined text in the table below means that the item under consideration is being used for the first time in the flashing sequence. Table 2: Table 2.
PAGE 12
NPC-1 Troubleshooting Instructions PAMS Technical Documentation C383 C583 C683 "The Prommer has not received Phone acknowledge to the message." (C383-during algorithm download to target phone) (C583-during erasing) (C683-during programming) Flash UPP Signals between UPP-Flash C384 C584 C684 "The Phone has generated NAK signal during data block transfer.
PAGE 13
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Figure 3: Fault tree, charging Phone doesn't start charging Connect charger and check VCHARIN Fail Check F100,L100,V100,C105 OK OK Check ICHAR FAIL Check bottom connector - VIN - Charge control pin Check R202,R203,R205,C217, C220,C201,C202 and R200 OK Change the UEM Audio failures In case of audio failures, there are three possibilities to check the audio lines. 1 Make a phone call against tester and check audios.
PAGE 14
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Audio loop (Audio test/Hp In Ext Out) must be switched on by the Phoenix service software. This loop will connect audios only through the UEM. In this case, the UPP is not used. 3 Run the audio-loop self-test with Phoenix (BB Self Tests / ST_EAR_DATA_LOOP_TEST). This loop will test the ear-data/mic-data lines between the UPP and the UEM.
PAGE 15
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Microphone or XEAR line does not work Figure 5: Fault tree, microphone fail Microphone doesn't work Run audio-loop selftest with phoenix Fail Feed 1KHz to Mic by JBA-8 and measure from Xear Ok Fail Ok Check R156,C151,C152,C157,L164 Ok Check microphone Change UPP Ok Change UEM Accessory detection 1 Start the phone in the normal mode when checking for accessory detection.
PAGE 16
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Figure 6: Fault tree, accessory detection Accessory detection doesn't work normally Check HeadInt ad-value with Phoenix (No accessory connected) - HeadInt ~0 *) Ok Use the xmic- switch on MJS-18 and check hookint ad-value.
PAGE 17
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Figure 7: Fault tree, sleep clock Sleep mode not working Measure sleep clock from J204 Issue 1 10/01 Fail Measure sleep clock from B200 Fail Check C203 &C204 Ok Ok Ok Change UPP (D400) Change UEM (D200) Change B200 ãNokia Corporation Page 17
PAGE 18
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Display/Keyboard lights do not work Figure 8: Fault tree, Display/Keyboard lights. Display/Keyboard lights are not working Check R300 (Display) and R301 (Keyboard) FAIL Replace resistor(s) FAIL Replace LED(s) FAIL Replace UEM OK Check LEDs V300...V303 (Display) and V304...
PAGE 19
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Display does not work Figure 9: Fault tree, Display does not work Display does not work Check that phone powers up normally (current consumption, power up sequence) In any phase of display troubleshooting use Display Test in Phoenix to produce test patterns on display. FAIL Proceed to phone doesn't power up troubleshooting FAIL Replace display module Also check with a known good display module to see if it works.
PAGE 20
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Buzzer does not work Check spring connectors and C306. • No sound: Try using a known good buzzer instead. If there is still no sound, change the UEM (D200) • Weak sound: Use the Audio test in Phoenix to set the buzzer parameters (frequency, strength). If it does not effect the sound level, change the buzzer. Vibra does not work Check spring connectors and C307&C308. • No vibration: Try using a known good vibra instead.
PAGE 21
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Infrared does not work Figure 10: Fault tree, infrared Infra Red not working Measure Vflash1 from IR module VCC(pin6), should be 2.78V FAIL Change UEM(D200) FAIL Replace faulty component(s) OK Check R350, R356, C351 and V350 OK Use ST_IR_LOOP_TEST(in BB Self Tests) in Phoenix OK FAIL Measure Tx Data from IR module(pin3) 1.8V, 9.6/115.
PAGE 22
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Receiver Troubleshooting General instructions for RX troubleshooting Start the Phoenix-software and use it to start the required RX-mode of the mobile phone. The troubleshooting flowchart is divided into three steps: (1) general checking, (29 local checking and (3) RX- chain checking. Always use an RF-cable connected from an external RF-connector to the analyzer via (RF-power) attennuator.
PAGE 23
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Figure 11: Fault tree. AMPS Apply 881.49 MHz = ch 383 -116dBm , 8kHz dev, 1 kHz sine signal to external RF-connector X900. Note! These tests are done in local mode by using RF Test UI. Y Connect HS to cellular tester, open audio AF: 1 kHz sine signal, meas SINAD AF: >12 dB N Y AMPS RX-chain OK N N Check UHF Vc (from C773) V: 1.8 ...2.1 V Start synthesizer troubleshooting Y N Check RXVHF Vc (from C720). V: 0.7 ...1.
PAGE 24
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Note! Check input level at diplexer (Z907) input. N Change EXT RF Connector Check all soldering and components in antenna circuit before changing Y Check input level at duplex filter. You can also check level at diplexer output Note! N Change diplexer Z906 Check all soldering and discrete components of frontend. Y N Change duplex filter (Z906) Check input level at LNA input (J800).
PAGE 25
NPC-1 Troubleshooting Instructions PAMS Technical Documentation N N Check RF level at RX IF filter input at 135.54 MHz Check RF level at J751 and J752 at 2034.06 MHz Start synthesizer troubleshoot Y Y Note ! Change SAFARI (N801) Check all discrete components and voltages around SAFARI N Check RF level at RX IF filter output at 135.
PAGE 26
NPC-1 Troubleshooting Instructions PAMS Technical Documentation TDMA800 Since the same physical signal path is used for both analog and digital modes at the lower band, there is no need for additional troubleshooting in the digital mode. So if the digital mode at the lower band is not working properly, start the analog mode troubleshooting.
PAGE 27
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Figure 12: Fault tree. Transmitter troubleshooting AMPS, PL2, CH383 Visual check of TX block - PA and up converter -TX SAW - Duplex filter - Passive components OK Check LO-signal (1017.03 MHz)@up converter and TX VHF (361.08 MHz)@N750 NOK Start synth troubleshooting OK Check supply voltage - VR2 - VBATTRF - VR5 - IPA1 - TXP1 NOK Check UEM and UPP (Baseband) OK Check TXi/q signals Test points J901...
PAGE 28
NPC-1 Troubleshooting Instructions Check TX SAW input and output power IL: -3 dB PAMS Technical Documentation NOK Change TX SAW filter Z905 OK Is Itot 700...800 mA? NOK Check PA output power and gain. Output power: ~28 dBm Gain: ~30 dB Change PA N901 OK NOK Check PWRDET N930 insertion loss IL< 0.3 dB Change PWRDET N930 OK Check duplexer Z906 , diplexer Z907 and RF connector X900 insertion loss Dupl IL ~2.2 dB Dipl ~0.35 dB RF conn ~0.
PAGE 29
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Power control loop Basically, the power detection is done with the Power detector module and power control is done inside the SAFARI. Power detection is similar for both bands, except that both bands have their own coupler. Figure 13: Fault tree: Power control loop N Is PWRDET vs. output power OK? See chart below. Check VR2 and RFTEMP . Check C930, C931 and PWRDET module. Note ! See PWRDET vs. Output power curve Y N Is DAC value vs.
PAGE 30
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Figure 14: Detected voltages 2000 1800 Detected voltage [mV] 1600 1400 1200 800A 1000 800D 800 600 400 200 0 2 3 4 5 6 7 8 9 10 P o w e r le ve l Synthesizer Troubleshooting There are four oscillators generating the needed frequencies for RF-section. 19.44 MHz reference oscillator, 2GHz UHF VCO, TX VHF cascade amplifier VCO and RX VHF VCO integrated in Safari. RX VHF frequency is fixed 271.
PAGE 31
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Figure 15: Fault tree: 19.44 MHz oscillator 2 Change VCTCXO OK 2.No START HERE! Is VCTCXO oscillating? 19.44MHz 1.No OK! OK 1 Check voltage C792 2.78 V No OK Check resistor R792 RX VHF VCO The RX VHF VCO signal is used to generate receiver Intermediate frequency. RX VHF VCO has one fixed frequency 271.08 MHz. Operating frequency is locked in Phase locked Loop. RX VHF VCO output signal is fed to SAFARI.
PAGE 32
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Figure 16: Fault tree: RX VHF VCO 4 Change SAFARI No 3 Check loopifilter components: C720, R721, C721, R722, C722, R733, C733 check also R724 OK 3.No OK 1 START HERE Is oscillator locked to 271.08 MHz 2.No Yes OK! OK 2 Check resonator components: V725, C724, C725, L730 and DC block C726 TX VHF VCO The TX VHF VCO signal is used to generate transmitter Intermediate frequency. The frequency of the TX VHF VCO is 361.08MHz.
PAGE 33
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Figure 17: Fault tree: TX VHF VCO 4 Check components: 5 C740, C741, C742, R741, R742, R743 and C749, C750, L750 Change cascade amplifier N750 OK 6.No 5.No OK OK 4.No 3 Check resonator components: OK 3.No 1 START HERE Is oscillator locked to 361.08 MHz or 363.6 MHz Yes 6 Change SAFARI OK! V744, C745, L746, C747, C748 2.No OK 2 Check operating voltage: 4.
PAGE 34
NPC-1 Troubleshooting Instructions PAMS Technical Documentation Fault finding chart for UHF SYNTHESIZER Figure 18: Fault tree: UHF Synthesizer Change VCO OK 3. No 2. No Change SAFARI 4. No START HERE! No Is frequency locked? 2009.1 - 2059.02 MHz Yes Is EVM OK? YES OK! OK No Check loopfilter components and balun 1. No Page 34 1 Check loopfilter components OK Check VCO operatig voltage: 2.