PAMS Technical Documentation RAE-3 Series PDA 8. Troubleshooting Issue 1 06/01 Copyright 2001. Nokia Mobile Phones. All Rights Reserved.
PAMS RAE-3 8.
PAMS Technical Documentation RAE-3 8. Troubleshooting CONTENTS –Troubleshooting Page No Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RAE–3 System HW / UI Troubleshooting . . . . . . . . . . . . . . . . Tools needed for troubleshooting: . . . . . . . . . . . . . . . . . . . . General guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System HW / UI Troubleshooting Cases . . . . . . . . . . . . . . . . . . .
PAMS RAE-3 8. Troubleshooting Technical Documentation 2.13.3 Insert SIM card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.14 Memory Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.14.1 Memory Card Interface Troubleshooting . . . . . . . . 2.14.2 Memory card switch troubleshooting: . . . . . . . . . . . 2.15 Lid Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.15.1 Lid Switch Troubleshooting . . . . . . . . . . . . . . .
PAMS Technical Documentation 5.2.2 RX/TX Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.3 Front end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.4 Hagar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 EGSM Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General troubleshooting instructions . . . . . . . . . . . . . . . . . . 5.3.1 Path of transmitted EGSM signal . . . . . . . . . . . .
PAMS RAE-3 8. Troubleshooting Technical Documentation Introduction This document is intend to be a guide for localizing and repairing electrical faults in the RAE–3 device. First there is a brief guide for fault localizing. Then fault repairing is divided into troubleshooting paths. Before any service operation you must be familiar with the RAE-3 product and module level architecture.
PAMS RAE-3 Technical Documentation S Check visual display faults S Check that all connectors make good contacts 8. Troubleshooting – this might be the problem if the displays are dark or partially dark or if there are keyboard problems. Locate failed module (BL8, UL8, DL2) with the MJS–14 test jig. This is the basis of further troubleshooting.
PAMS RAE-3 8. Troubleshooting Technical Documentation System HW / UI Troubleshooting Cases 1. Troubleshooting of System HW/UI is divided to following cases: . . . . . . . . 1.1 Dead Device . . . . . . . . 1.2 Keypad problem 2. BL8 System HW related: . . . . . . . . 2.1 Flash programming troubleshooting . . . . . . . . 2.2 General Power Checking . . . . . . . . 2.3 Device does not stay ON . . . . . . . . 2.4 Charging checking . . . . . . . . 2.5 Backup Battery . . . . . . . . 2.
PAMS RAE-3 8. Troubleshooting Technical Documentation 4. UL8 Flex Related: . . . . . . . . 4.1 Audio troubleshooting . . . . . . . . 4.2 Display problem . . . . . . . . 4.3 Battery Removal Switch problem . . . . . . . . 4.4 UL8 related keyboard problems Nominal Current Consumption The following power consumption values (ref.Table 1 ) are measured from a complete RAE-3. Vbattery = 3.7 V. Measured nominal currents are drawn from the main battery.
PAMS RAE-3 8. Troubleshooting Technical Documentation 1 System HW / UI Troubleshooting Cases 1.
PAMS RAE-3 Technical Documentation 1.2 8. Troubleshooting Keypad problems 1. Connect the phone under test to Wintesla. 2. Select Testing –> User interface testing 3. Select the CMT to be tested from the ”Display” panel and click ”Start key test” (figure 1). The test starts and the button text changes to ”Stop key test”. 4. Click the ”Stop key test”. Result window (Figure 2) appears. . . . . . . . . All letters under the key names should show ”A”. . . . . . . . . If there is ”R”, the key is stuck.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 2. User interface test dialog Figure 3. CMT keypad test results Figure 4.
PAMS RAE-3 8. Troubleshooting Technical Documentation 2 BL8 System HW related 2.1 Flash programming troubleshooting 2.1.1 Flashing does not start FLASH programming does not work YES If the fault information from the prommer is: a) The Phone does not set Flashbus TXD line high after the startup b) The Phone does not set Flashbus TXD line low after the line has been high. The Prommer generates this error also when the Phone is not connected to the Prommer.
PAMS RAE-3 8. Troubleshooting Technical Documentation YES 2.1.2 Flash memory fault indicated YES FLASH programming does not work YES If the fault information from the prommer is: a) The flash manufacturer and the device IDs in the existing Algorithm files do not match with the IDs received from the phone. b) The External RAM test failed in the Phone. c) The Phone does not send acknowledge signal (ie. drop the Flashbus TXD line to low state) after the Prommer has sent the Algorithm code.
PAMS RAE-3 8. Troubleshooting Technical Documentation 2.1.3 Flash VPP Error FLASH programming does not work YES If the fault information from the prommer is: a) The erasing status response from the Phone informs about fail. The Prommer copies the Phone response contents to the preceeding FIASCO_GENERAL_INFO_IND message. b) The Prommer measures the PPD voltage level at flashing start. If the level is below the limit the Prommer returns the corresponding error code.
PAMS RAE-3 8. Troubleshooting 2.1.4 Technical Documentation Flash Erasing /Programming Error FLASH programming does not work YES If the fault information from the prommer is: a) The erasing status response from the Phone informs about failure. The Prommer copeies the contents of the response of the Phone into the preceeding FIASCO_GENERAL_INFO_IND message. b) The Phone has generated a NAK signal during data block transfer. c) The programming status response from the Phone informs about failure.
PAMS RAE-3 8. Troubleshooting Technical Documentation 2.2 General Power Checking Use BBL-3B service battery. Battery voltage must be 3.7 V. Switch power on Supply voltage drops when the power is switched on Short circuit in VBAT, VBB or VCORE line. Switch power off and measure with multimeter which of these voltages have a short circuit. Check visually components which are connected to short circuited voltage line. YES NO VB (C124) and VB_CCONT (C115) 3.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 10.
PAMS RAE-3 Technical Documentation 2.3 8. Troubleshooting Device does not stay ON If the device is switched off without any visible reason, there may be problems in the following areas: S CCONT watch dog problem S BSI or BTEMP line problem S Battery line problem S Soldering problem The most likely reason is CCONT WD (watchdog) problem, which turns the device off after about 32 s. This may be caused by SW problem, MadLinda problem, CCONT problem or memory problems.
PAMS RAE-3 8. Troubleshooting 2.4 Technical Documentation Charging checking Use the BLL–3 battery and the JBE-2 calibration unit to test charging. When you are charging totally empty battery, remember that start–up charging might take 2 minutes with ACP–9 charger and several minutes with ACP–7 charger. During this time display is blank. If charger is not NMP approved type and supported by phone then the software doesn’t start charging and display ’NOT CHARGING’.
PAMS RAE-3 8. Troubleshooting Technical Documentation Nothing happens when charger is connected Display information: NOT CHARGING R121 voltage NO is ~1.1V when charger is connected NO Check BLL–3, BSI resistor, X100, R121, R122 V_in voltage at R111 >0.4 V ? YES YES R123 voltage NO is ~0.5V when charger is connected Check BLL–3, X100, X450, F450, V450, L453.
PAMS RAE-3 8. Troubleshooting 2.5 Technical Documentation Backup Battery CAUTION Danger of explosion if the battery is incorrectly replaced. Replace only with the same or equivalent type recommended by the equipment manufacturer. Discard used batteries according to the manufacturer’s instructions. Figure 12. 2.5.1 Backup battery troubleshooting Main power supply to the device must be 3.7 V when used.
PAMS RAE-3 Technical Documentation 8. Troubleshooting 4. Check the backup battery connector X102 visually. 5. Measure voltage at terminal 1 of X102. It must be 2.82 V to 3.3V. –> if NOT OK, then N101 is faulty. 6. Insert the backup battery in the connector, make sure that the contact is good. 7. Measure voltage at terminal 2 of X102. It must be 1.8 V to 3.3V. This voltage increases because of charging if the battery is not fully charged. 8. Read the backup battery with WinTesla.
PAMS RAE-3 8. Troubleshooting 2.6 Technical Documentation Accessory Power Output Troubleshooting Accessory power output is connected to the system connector’s DCE_DTR pin inside the device.Accessory power output can be tested with MJS–14 test jig and Wintesla SW. There is a pushbutton called ACC VOLTAGE in MJS–14 test jig which is used to connecting load to DCE_DTR pin of the system connector. Following Figure 13 shows the connection in MJS–14 test jig (load side).
PAMS RAE-3 8. Troubleshooting Technical Documentation 2.6.1 No Accessory Voltage when needed – Power supply must be 3.7V. – MJS–14 Test Jig must be used. – Signals must be measured during Wintesla Accessory Power Output Test . Fail in WinTesla accessory power out test Check VACC = 3.3V ( Pin 5 of N104) Check X450, V451, R454, R310, V489 and C459 Yes No Check VB=3.
PAMS RAE-3 8. Troubleshooting 2.6.2 Technical Documentation Accessory Voltage ON all the time – Power supply must be 3.7V. – MJS–14 Test Jig must be used. – This fault can be seen also as serial interface problem. – Signals must be measured during Wintesla Accessory Power Output Test.
PAMS RAE-3 8. Troubleshooting Technical Documentation 2.7 Clocks 2.7.1 Clocks Troubleshooting When the flashing of the device does not succeed, but the powering is OK, follow these instructions. Note: The absence of clocks may indicate that the device is in sleep mode. Move the magnet away from the sensor to simulate cover open situation.
PAMS RAE-3 8. Troubleshooting Technical Documentation 1. Open the smaller RF shield metal can. Check Hagar RFC–out signal at V800. It should show sine wave of 1.2V amplitude, 13MHz frequency (see Figure 18 ). • If this is OK, the problem is in V800 transistor or in R834, R830, C834, L800. Figure 18. 13 MHz sine wave 2. Check VTCXO output at R833. This should be 26MHz sine wave (see Figure 19 ). • If this is OK, Check R835, C830 for shorts and bad connections.
PAMS RAE-3 Technical Documentation 2.8 Memory Tests 2.8.1 Test in boot up 8. Troubleshooting FLASHes 0 (D351), 1 (D352) and 2 D(353): – manufacturer and device id are read from each of the flashes then compared to value stored in FLASH 0. – id read program code is executed from API RAM – If FLASH 0 is broken the phone will not boot up properly (user test code resides in FLASH 0) i.e. probably not even blink CMT backlights.
PAMS RAE-3 8. Troubleshooting 2.8.2 Technical Documentation Test in PTS/WinTesla flashing These tests are in the beginning of device flashing. If any of these tests fail the flashing will be stopped and a notification will be shown on the monitor screen.
PAMS RAE-3 Technical Documentation 8. Troubleshooting 2.9 Memory Troubleshooting 2.9.1 Memory fails In Boot Up tests, CMT Backlight is blinking If the device won’t boot up and CMT display backlight is blinking ⇒ FLASH 0 (D351) probably ok ! To measure signals from D352, D353, D350 and D354 the device needs to rebooted up constantly since the lines are active only a short time in the beginning of the boot.
PAMS RAE-3 8. Troubleshooting 2.9.2 Technical Documentation CMT display backlight blinking 2 times in a loop CMT display backlight blinking 2 times in a loop (”Flash fault”): Manufacturer and device id read from FLASH 1 (D352) or FLASH 2 (D353) or from both fails. ID read from FLASH1 or FLASH2 fails Flash the device D352 ID read fails during flashing D353 ID read fails during flashing Check: negative pulses on J339 (1.8V) OK? Check: negative pulses on J340 (1.
PAMS RAE-3 8. Troubleshooting Technical Documentation 2.9.3 CMT display backlight blinking 3 times in a loop CMT display backlight blinking 3 times in a loop (”SDRAM fault”): D350 SDRAM test fails Check activity from SDRAM lilnes SDRRASX (J312): negative pulses (2.8V) SDRCASX (J313): negative pulses (2.8V) SDRWEX (J314): negative pulses(2.8V) SDRCLK (J310): 13MHz clock (2.8V) SDRAd6 (J348): postive pulses (2.8V) SDRDQML (J315): negative pulses (2.8V) SDRDQMU (J316): negative pulses (2.
PAMS RAE-3 8. Troubleshooting Technical Documentation SDRDa8 J349 Figure 22. SDRAM (D350) driven data line SDRDa8 (J349) SDRCLK J310 SDRRASX J312 SDRCASX J313 SDRWEX J314 Figure 23.
PAMS RAE-3 8. Troubleshooting Technical Documentation SDRCLK J310 SDRAd6 J348 SDRDQML J315 SDRCKE J311 Figure 24.
PAMS RAE-3 8. Troubleshooting 2.9.4 Technical Documentation CMT display backlight blinking 4 times in a loop CMT display backlight blinking 4 times in a loop (”Serial Flash fault”): D354 Serial Flash ID read test fails Check activity in serial FLASH lines SEPClk (J327):6.5MHz clock (2.8V) SEPO (J329): positive pulses (2.8V) SEPCSX (J337): long negative pulse (2.8V) EXT_SYS_RESETX (J301): high (2.8V) SER_FL_RBY(J346): high (D300 internal pull–up, use passive probe!) (2.
PAMS RAE-3 Technical Documentation 8. Troubleshooting SEPCLK J327 SEPO J329 SEPI J328 SEPCSX J337 Figure 26. Issue 1 06/01 Serial Flash (D354) id read sequence.
PAMS RAE-3 8. Troubleshooting 2.9.5 Technical Documentation Memory fails in PTS/WinTesla flashing 1. SDRAM id read test fails Refer to the previous ”SDRAM fault” chapter. 2. Flash manufacturer and device id read fails a) If id read from all of the three flashes (D351, D352 and D353) fails most likely the problem is in D300. Check D300 and control lines: S FLDa7 (J351): positive pulses (1.8V) S FLCS0X (J338): negative pulses (1.8V) S FLOEX (J341): negative pulses (1.
PAMS RAE-3 8. Troubleshooting Technical Documentation ID read from FLASH fails D351 id read fails D352 id read fails D353 id read fails Check if FLCS0X OK, J338 YES NO YES NO Check if FLCS1X OK, J339 Change D352 Problem with D300 YES Check if FLCS2X OK, J340 NO Change D353 Figure 27. Refer to the oscilloscope screen shots next page for what the signals should look like.
PAMS RAE-3 8. Troubleshooting Technical Documentation FLCS0X J338 FLOEX J341 FLWEX J342 Figure 28. Flash 0 (D351) manufacturer and device id read FLAd5 J350 FLDa7 J351 Figure 29. 2.9.6 the Flash address and databus signals Serial Flash id read test fails Refer to previous chapter ”Serial Flash fault” 2.1.
PAMS RAE-3 8. Troubleshooting Technical Documentation 2.10 Serial Interface Troubleshooting Serial Interface problem 1. Check Serial connector X450 spring contacts YES Flashing successful? NO 2. Check and replace ESD protection device V451 3. Check DCE_Tx (AccRxData) comp. R452, C458, R300 Activate WinTesla, observe ADC–readings 4. Check DCE_Rx (AccTxData) comp. R453, C457, R307 5. Check DCE_DCD (MBus) comp.
PAMS RAE-3 8. Troubleshooting Technical Documentation 2.95V 2.8V With DLR–2L C1, black: MAD end C5, green: syscon end 0.3V 0V Using DLR–2: GRP1, black: MAD end GRP2: System connector end Figure 31.
PAMS RAE-3 8. Troubleshooting Technical Documentation MBUS (clock) Signal during flashing (Figure 32): GRP1, black: MAD–end GRP2: system connector end Approx. 0.2V difference results from MBUS pull–up resistor (R309, 4k7) & serial resistor (R450, 270R) voltage slicing. Figure 32.
PAMS RAE-3 8. Troubleshooting 2.11 Technical Documentation CONTACT SERVICE in CMT display CONTACT SERVICE in CMT display (Self-tests with WinTesla) Display Information: ”Contact Service” This fault means that software is able to run and thus the watchdog of CCONT (N100) can be served. Self–test functions are executed when power is switched on and software is started to execute from flash. If any one of the self–tests fails (except no.
PAMS RAE-3 Technical Documentation 8. Troubleshooting Calculates 16 bit checksum out of Flash code and compares it to the one found in Flash. Items being checked are MADLinda <–> Flash data– and address lines FLDa0–15 and FLAd1–21, FLCS0X (CE0), FLCS1X (CE1), FLCS2X (CE2), FLWEX (WE), Vbb (Vcc), VCORE (Vccq), GND, and Flash internal functionality. Item no. 2 MCU EEPROM Interface: Checks current PMM error status. If this test FAILs, the PMM data is not valid anymore and should be formatted. Item no.
PAMS RAE-3 8. Troubleshooting 2.12 Technical Documentation CCONT Serial interface Troubleshooting If there are problems in CCONT’s serial control interface, self tests fail and there is ”Contact service” shown on the display. Wintesla shows this fail as ”CCONT Interface”. NOTE: Low level means 0V, high level means approximately 2.8V. Check GENSCLK line at J318 Square wave, Freq. 2.
PAMS RAE-3 8. Troubleshooting Technical Documentation MADLinda writes to CCONT. The data at sixth bit is ’0’ as marked with the cursors. The data after the read/write bit varies, just like the address before the bit. If you can see this kind of traffic, MADLinda side of the interface is functioning correctly. Figure 36. MADLinda reads from CCONT. The data at sixth bit is ’1’, marked with the cursors. There should be data seen after the ’read’ bit.
PAMS RAE-3 8. Troubleshooting Technical Documentation 2.13 SIM Card 2.13.1 SIM Card Error Troubleshooting The fault information ”SIM Card error” means most likely that the SIM locked phone has been inserted with a SIM which does not correspond to the lock code. Check the SIM lock status of the phone with WinTesla: ”SIM Card Error” message in display ? Set the phone in NORMAL mode View–> Quick/RF Info See ”SIM Lock Settings” field: NO Blank field? YES No SIM lock.
PAMS RAE-3 Technical Documentation 2.13.2 8. Troubleshooting SIM Card Rejected The fault information ”SIM Card rejected” means that the ATR message (Answer To Reset; the first message from SIM card to phone after SIM card power up) is sent, but it is corrupted somehow, eg. the dataline signal levels are wrong or factory set values (stored in the EEPROM) are not correct.
PAMS RAE-3 8. Troubleshooting Technical Documentation SIM CARD FAULT YES Check VSIM at SIM card pin 5V card:Check 5V charge pump components C107 V101 C110 VSIM= 2,8V min. with 3V 4.5V min.
PAMS RAE-3 Technical Documentation 2.13.3 8. Troubleshooting Insert SIM card The hardware of the SIM interface from the MADLinda (D300) to the SIM connector (X101) can be tested without SIM card. This leaves SIM connector (X101) contacts to be used as an measurement points.
PAMS RAE-3 8. Troubleshooting Technical Documentation Insert SIM card fault YES Check Voltage level between R121 and C126 When BSI resistor connected (included in service jig YES NO Check Volt.level R121, R122, <1.5V ? X100, C126 YES 5V card:Check 5V charge pump components C107 V101 C110 NO–5V NO– 3V VSIM at SIM card pin 2.8V min. with 3V card 4.
PAMS RAE-3 Technical Documentation 2.14 Memory Card 2.14.1 Memory Card Interface Troubleshooting 8. Troubleshooting Start with assembled device with a faultless memory card inserted. If necessary, proceed with tests in the jig with the faultless memory card inserted. Clk, Cmd and Data OK means that frequency, rise and fall timing are OK during various operating modes.
PAMS RAE-3 8. Troubleshooting Technical Documentation Memory card interface check Run WinTesla Memory card test YES Test OK? A faulty Memory Card used before ? SW corruption ? NO Run Memory Card cover Switch fault test Switch OK ? Assembled device Disassembled device in jig Measure VMMC J104 while re–running the MemCard test YES NO NO NO 2.9 – 3.
PAMS RAE-3 8. Troubleshooting Technical Documentation 2.14.2 Memory card switch troubleshooting: NOTE1: Memory card switch pressed (lid closed) => ADC reading ’Memory Card Cover Detection’ is in state ”0” => MMC_Switch – line = 0V Memory card switch released (lid opened) => ADC reading ’Memory Card Cover Detection’ is in state ”1” => MMC_Switch – line = 2.
PAMS RAE-3 8. Troubleshooting 2.15 Lid Switch 2.15.1 Lid Switch Troubleshooting Technical Documentation NOTE1: Lid signal (MAD pin P2 gendet) : Lid closed = ’Cover Detection’ from Wintesla ADC readings is state ”0” => V301 (HALL) output = 2.8V Lid opened = ’Cover Detection’ from Wintesla ADC readings is state ”1” => V301 (HALL) output = 0V Troubleshooting diagram Figure 42 next page.
PAMS RAE-3 8. Troubleshooting Technical Documentation Open Wintesla Select Testing –>ADC Readings Lid switch trouble– shooting Turn the phone power on Open the lid Wintesla: Lid Open OK (cover detection state ASSEMBLED DEVICE 1) ? NO Place magnet above the TAB key, note: pole toward the key ! then wait Refresh from Wintesla DEVICE IN JIG Check V301, C322 Wintesla: Lid Closed OK (ADC reading Cover switch= ”0” N301 pin 1 (Hall supply volt) 2.
PAMS RAE-3 8. Troubleshooting 2.16 Technical Documentation Battery Removal Switch troubleshooting NOTE1: Switch itself is not possible to test in service jig. NOTE2: Switch FREE position = Wintesla ADC–readings ’Battery Removal Switch’ is in state ”0” =>BATT_REM – line = 2.8V Switch CONNECTED position = Wintesla ADC–readings ’Battery Removal Switch’ is in state ”1” => BATT_REM – line = 0V NOTE3: Battery removal switch (latch spring) gets connected when battery latch is pressed during battery release.
PAMS RAE-3 8. Troubleshooting Technical Documentation Battery removal switch problem YES Open WinTesla Testing–> PDC readings OK Latch ”FREE” position NO Battery removal switch state =”0” ? Short circuit in switch lines (BATT_REM) Check Z401 YES Reading ”1” though latch position ”FREE” ? YES Keep latch in opposite position wait updated values from WinTesla NO State changes to NO ”1” ? YES Check B–to–B adapter JC4 pin 42: BATT_REM line: Faulty circuit D300 (MAD) YES Voltage high (=2.
PAMS RAE-3 8. Troubleshooting 2.17 Technical Documentation COBBA Control Interface troubleshooting NOTE: If there are problems in COBBA serial interface, self tests fail and there is ”Contact service” shown on the display. Wintesla shows fails at ”Cobba parallel”. Check COBBACLK line at J322 Square wave, Freq.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 46. COBBA read Figure 46 is a COBBA read. The MADLinda writes first the address to be read, deactivates the COBBACSX line and then activates the COBBACSX line again. Then the COBBA_GJP sends the requested data. There should be non–zero reads. If no non–zero reads from COBBA can be seen, COBBA (N200) may be faulty.
PAMS RAE-3 8. Troubleshooting 2.18 Technical Documentation COBBA PCM Interface Troubleshooting PCM interface transfers digital audio data. Problems in this interface result in missing or flawed audio in either or both in uplink and downlink directions. If Wintesla shows errors in ”COBBA serial interface”, PCM interface is faulty. Check PCMDClk signal at J309: 520 kHz square wave 50 per cent duty cycle Rising and falling edges about 3 to 5 ns Inactive state low? Ref. fig.
PAMS RAE-3 8. Troubleshooting Technical Documentation traffic in both directions. Audio play generates traffic in one direction only. Recording audio (voice recorder) generates traffic in the other direction. Issue 1 06/01 Figure 48. PCMDClk signal at J309 Figure 49. PCMSClk signal at J306.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 50. PCMRxData signal at J308. Figure 51. PCMTxData signal at J307 PCMTxData signal at J307 (Figure 51). This signal comes from the other end’s microphone or audio playing software (voice recorder, video player etc) and is targeted for the earpiece or hands free speaker. There should be activity during a call. Signal rise and fall times are around 4–7ns. Idle state is low.
PAMS RAE-3 8. Troubleshooting Technical Documentation 2.19 Audio troubleshooting 2.19.1 Both Mic and Earpiece/PHF faulty MIC and Earpiece /PHF faulty Check voltage at cap C208 HOOKDET without external audio devices NO OK Check R206 and R207, C208 HOOKDET 2,8V? Check voltage at cap C202 HEADDET without external audio devices NO OK HEADDET 2,8V? Check R203, R202, R200 C201, C202 Check frequency at J309 PCMDClk during a call OK * refer to section 2.17 in this document 520kHz square wave 2.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 53. Figure 54.
PAMS RAE-3 8. Troubleshooting Technical Documentation 2.19.2 Mic faulty MIC faulty Check microphone and mic connections to PWB Check digital PCM data atJ308 (PCMRxData) during a call OK Data OK? NO Faulty N200 (COBBA) Refer to COBBA control interface troubleshooting Check voltages : V202 pin 1 : 1.8V V202 pin 3: 0.17V during a call OK NO Voltages OK? Check R222, R218 C231, C224, C230 OK DC voltage at C234 and C235 1.4V during call ? * Mbias at R222 2.
PAMS RAE-3 8. Troubleshooting 2.19.3 Technical Documentation Earpiece faulty Earpiece faulty Check assembly of earpiece and gasket 1) Check connections from audio PWB to C229 and C228 OK Connection OK? NO Check Flex UL8 and B–to–B conn X400 pins 47, 48 Check digital PCM data at J307 (PCMTxData) during a call OK NO Faulty D300 (MAD) 2) Data OK? DC voltage at C228, C229 1.4V during call ? OK NO Voltages OK? Check R215, R216 and connections.
PAMS RAE-3 8. Troubleshooting Technical Documentation 2.19.4 PHF Speaker faulty PHF Spealer faulty Check assembly of HF speaker, springs and connection to flex UL8 Check connections from speaker pads to C236 and C237 NO OK Connection OK? Check Flex UL8 and B–to–B conn X400 pins 43 to 46 Check VAMP at R201, R204, R205, R221* OK NO Check R201, R204, R205, R221 C203, C204, C205, C206 * VAMP about VBATT ? AMP SHDN at V200 pin 2 2.
PAMS RAE-3 8. Troubleshooting Technical Documentation PHF speaker fault continued Check analog audio input signal XEAR at C220, min. some 10 mV OK Check R212, R213, C220, C241, C223, NO C217, C218 Signal amplified (ca. 10x) at N201 pins 5 and 8 ? NO Check R208, C213 and XEAR traces from C220 to N200 OK? Faulty N200 (COBBA) OK Faulty N201 (audio amp) OK Analog audio signal at C236 and C237? Check L200, L201, PWB connections NO OK? Figure 58.
PAMS RAE-3 8. Troubleshooting Technical Documentation 2.19.5 Headset out of order Headset out of order RAE–3 detects HS ? (CMT lcd reads ”headset”) OK Measurements in Service Jig NO OK Voltage at C202 (HEADDET) low ? D300 (MAD) faulty Check XMIC and SGND lines from System Conn. X450 pins 6 and 4 Check C202, R203, L452 C464. R460, L450, C462, R455, C460 C461, C452, C450 NO Head– set earpiece capsule OK ? OK OK NO AUXOUT voltage between R200 and R202 is 1.
PAMS RAE-3 8. Troubleshooting Technical Documentation Headset out of order, continues OK Remote control switch OK ? Measurements in Service Jig NO Check voltage at C208 while HS switch button is pushed Head– set faulty OK Voltage at C208 (HOOKDET) low ? D300 (MAD) faulty NO Check R207 and C208 Figure 60.
PAMS RAE-3 8. Troubleshooting Technical Documentation 2.20 RF Interface 2.20.1 Phone doesn’t register to the network or doesn’t make a call Phone does not register to the network or does not make a call NO C254 (VCOBBA)>2.7V ? Check N100 CCONT YES NO C100 (Vref) = 1.5V ? Check C100, R211 YES Check YES Reser at N600 pin1 =”1” ? YES NO Check supply voltage during RX slot: C101 (VCP) >4.8V C133 (VRX) >2.7V C135 (VSYN_1)>2.7V C134 (VSYN_2)>2.7V During TX slot: C136 (VTX) >2.
PAMS RAE-3 8. Troubleshooting 2.21 Technical Documentation IR Interface Troubleshooting diagram IR CHECK YES VBB (Vcc) OK? (N050/6) IR test OK? (Wintesla) IRED_A(Vled) (N050/1) OK? NO YES IrDA test OK NO R050, R052, R053, R054, C055, C050 OK? C052 – C054 OK? CANNOT BE MEASURED IN THE JIG IREN (Sd) OK? (N050/5) NO YES IRDI (Rxd) OK ? (N050/4) YES NO IRDO (Txd) OK ? (N050/3) NO Replace IR module IR Test OK? (Wintesla) NO CPU fault Figure 62.
PAMS RAE-3 Technical Documentation 2.22 8. Troubleshooting BL8 related Keyboard problems There may be several types of problems with keyboard. Usually some of the keys (CMT and PDA) are not working, or several key presses happen simultaneously. If CMT informs ”Please close cover”, see ”Lid switch problems” section.
PAMS RAE-3 8. Troubleshooting Technical Documentation Problem with QWERTY keypad _1 Put BL8 module in test jig, connect B–to–B adapter JC4. DO NOT connect the UI module or Flex, yet DO NOT switch power on. Refer to table 6. Check the resistance of Row and Col signals to GND.1) Resistance > 1 MOhm ? YES NO OK? Check, replace Z401 to Z404 Turn power on. DO NOT connect the UI module or Flex yet. Check Col signals at pins: 49, 62, 60, 59, 54, 55, 56, 61, 53, 51 Voltage around 2.
PAMS RAE-3 8. Troubleshooting Technical Documentation Problem with QWERTY keypad _2 Connect ROW0 to COL0 Measure the short circuit with oscilloscope Signal rise and fall times between 80 to 120 ns, constant activity? Repeat for each ROW– COL pair. YES OK? NO Cycle the power, retry If no activity or rise/fall times our of range check CSP filters Z401 to Z404 Connect Flex and UI module to the jig. Switch the power on, wait for reboot Push the faulty key, check the column signal.
PAMS RAE-3 8. Troubleshooting Technical Documentation Table 2.
PAMS RAE-3 8. Troubleshooting Technical Documentation 2.23 BL8 related PDA UI problems Problem with BL8 Put BL8 module in test jig, connect B–to–B adapter JC4. DO NOT connect the UI module or Flex yet. DO NOT switch power on. Check the resistances of display signals to the GND (1) Resistance > 1 MOhm ? YES OK? NO Check, replace CSP filters Z401 to Z404 if voltage < 1MOhm Connect the Flex and the UI module. Turn the power on. Check LCDDA0 to LCDDA11 signals at JC4 pin header. Pins nos.
PAMS RAE-3 8. Troubleshooting Figure 66. Technical Documentation LCDDA0–LCDDA11 signals on the pin header on JC4. The pins are 5, 7, 19, 20, 22–24, 26, 36–39. Figure 67. DispClk signal at pin 2 DispClk signal (Figure 67) at pin 2. Use at least 1MΩ probe for this. Note: The more critical values are high 1.8V, frequency 8.645MHz and +Width 42ns. If the signal high time is too small, it will cause errors.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 68. LLCLK signal at pin 40. Figure 69. Issue 1 06/01 FSP signal at pin 4.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 70. BackPWM signal at pin 31 This signal (Figure 70) is a PWM control for display backlight. The pulse width varies and is constant high for maximum intensity. Figure 71. LCDPWM signal at pin 10. This signal (Figure 71) is a PWM control for display contrast. The pulse width may vary significantly. Table 3: List of display signals Table 3. Display Signal List of display signals JC4 pin no. Display Signal JC4 pin no.
PAMS RAE-3 8. Troubleshooting Technical Documentation Table 3. Display Signal (continued) List of display signals JC4 pin no. Display Signal JC4 pin no. LCDDa6 37 LCDM 18 LCDDa7 22 LCD_PWR 6 LCDDa8 19 LCDPWM 10 LCDDa9 23 BackPWM 31 Table 4.
PAMS RAE-3 8. Troubleshooting 2.24 Technical Documentation BL8 related CMT UI problems Problem with CMT UI Put BL8 module in test jig, connect B–to–B adapter JC4. DO NOT connect the UI module or Flex yet. DO NOT switch power on. Check the resistances of display signals to the GND (1) Resistance > 1 MOhm, GENSDIO = 47kOhm? YES OK? NO Check, replace CSP filter Z401 Connect the Flex and the UI module. Turn the power on. Check GENSCLK, signal as in Fig.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 73. GENSCLK signal. GENSCLK signal (Figure 73 ). It should look like this when LCDEN signal is active. There is also a 2.16MHz clock signal, but it is targeted for CCONT. Table 5. Signals and pins Signal Pin no. LCDEN 12 GENSDIO 9 GENSCLK 11 LCDRSTX 14 Table above: Signals and corresponding pins.
PAMS RAE-3 8. Troubleshooting Technical Documentation 3 DL2 UI Troubleshooting 3.1 CMT and keypad illumination problems Each CMT–display and keypad LED has its own driver. If there is problems with one or more – Keypad–LED: check resistors R203–R208, transistors V213, V203, V204 and the LEDs. – CMT–LED: check resistors R200–R202, transistor V206 and the LEDs. If the illumination does not work at all, measure voltages VB and KBLIGHTS. VB should be the same as VBATT and KBLIGHTS approximately 2.
PAMS RAE-3 Technical Documentation 3.3 8. Troubleshooting No picture on PDA LCD or picture is faulty To start with, check that the flex connector (X001) from BL8 to UL2 is connected properly and that soldering joints are ok. Check also connectors X002 and X003. Check that PDA display is not mechanically damaged, i.e. pixels missing.
PAMS RAE-3 8. Troubleshooting Technical Documentation Start Section 1 Measure V5Y_1, should be appr.–15V Picture on LCD? NO V5Y_1 0V? YES Measure ST_INVOUT (Fig.79) OK? Check components L050, C068, V062 and V069 YES Check components C058 and R075 NO Check components V055 and V058 NO Check components R066, V061, R067, R076, V066, R078 and R081 ON ON YES NO See Section: bl8 related PDA UI problems See Section 3 NO Measure DD_P1 (Fig.80) OK? Measure BRIGHT (Fig.
PAMS RAE-3 8. Troubleshooting Technical Documentation Start Section 2 Measure V5Y(Fig.85) and VCCY (Fig.86) OK? NO Measure FRYS(Fig.84) OK? YES Check components between FRYS, V5Y and VCCY NO Display ASIC fault YES Check components C076,V072, N050, C075 and C101 Check components V060, R079 and C064 YES YES Measure VOY(Fig.85) OK? Measure VDD, it should be ~3.8V OK? NO NO Measure DD_P2 NO (Fig.86) OK? Display ASIC fault YES Measure NO DY(Fig.90) FRY(Fig.91) DY OK? YSCL(Fig.
PAMS RAE-3 8. Troubleshooting Technical Documentation NOTE!! See section 2.23. There are all the relevant pictures of the signals mentioned below. Measure these signals from UL2 side. This is to make sure that the problem is not in BL8 side. Start Section 3 Measure DispClk(J012), OK? YES Measure LLClk(J027), OK? YES NO Measure FSP(J020), OK? See section bl8 related PDA UI problems YES NO Measure DISPON(J021), 2.
PAMS RAE-3 8. Troubleshooting Technical Documentation Start Section 4 Measure D10,D11, D12 and D13(Fig.98) OK? NO Check component R087 NO Check component R088 NO Check component R090 NO Check component R089 YES Measure D00,D01, D02 and D03(Fig.98) OK? YES Measure D20,D21, D22 and D23(Fig.98) OK? Signals OK? NO Display ASIC(D054) fault YES Measure RES,LP and GOP (Figs.99, 100, 101 ) OK? YES Measure FR (Fig.102) OK? YES Check component R091 NO Display module fault YES Figure 78.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 79. ST_INVOUT signal Figure 80. Figure 81.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 82. Issue 1 06/01 V5Y signal Figure 83. VCCY signal Figure 84.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 85. VOY signal Figure 86. DD_P2 signal Figure 87.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 88. FRY signal Figure 89. YSCL signal Figure 90.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 91. DY_A signal Figure 92. FRY_A Figure 93.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 94. XSCL signal Figure 95. Data signal (Note!! There should be constant activity in the datalines and signals should look something like this.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 96. RES signal Figure 97.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 98. LP signal Figure 99.
PAMS RAE-3 8. Troubleshooting 3.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 101. DRAIN (no light) Figure 102.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 103. VCO_OUT (no light) Figure 104.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 105. DRAIN (light on) Figure 106.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 107. FEEDBACK (light on) Figure 108.
PAMS RAE-3 Technical Documentation 3.5 8. Troubleshooting DL2 related keyboard problems 1. Check the 50–way connector solderings and general condition 2. Check PDA softkey switches S250, S251, S260, S261 3. Check keyboard line capacitors C250–C263 (14 pieces) for shorts and breakages 4. Check the key pads for short circuits or dirt. Measure the resistance of each row against all columns and all rows and columns against ground. (Disconnect the 50–way connector first).
PAMS RAE-3 8. Troubleshooting Technical Documentation 4 UL 8 FLEX related 4.1 Audio troubleshooting Handsfree or/and Earpiece Audio not working Check soldering of 70 way connector YES NO OK? Resolder connector Check soldering of AF8 PWB NO YES Resolder OK? connector Check HF speaker gold pads NO Figure 109. OK? Replace part AF 8 illustrated below (Figure 110). Figure 110.
PAMS RAE-3 8. Troubleshooting Technical Documentation 4.2 Display problem PDA or CMT displays are missing lines or columns, or are not synchronised Corruption of PDA or CMT LCDs Check solderinf of 70 way connector YES NO OK? Resolder connector Check soldering of 50 way connector Resolder OK? connector Check hinge tracks for wear NO Replace part OK? Figure 111.
PAMS RAE-3 8. Troubleshooting 4.3 Technical Documentation Battery Removal Switch problem If the battery removal switch is not functional, check AF 8 for wear, illustrated below. (Check that the RAE-3 software supports the battery removal switch feature.) Figure 112. AF8 4.4 UL8 related keyboard problems 1. Check the 70–way and 50–way connector solderings and general condition. Re–solder if fault found. 2. Check the keypad surface for short circuits or dirt. 3. Replace the flex.
PAMS RAE-3 Technical Documentation 5 8. Troubleshooting RF related Introduction to troubleshooting Measurements must be done using Spectrum Analyzer with high–frequency high–impedance passive probe (LO–/reference frequencies and RF–power levels) and Oscilloscope with a 10:1 probe (DC–voltages and low frequency signals). The RF–section is build around one ASICS Hagar (N505). For easier troubleshooting, this RF troubleshooting document is divided into sections.
PAMS RAE-3 8. Troubleshooting Technical Documentation RF Key Component Placement Figure 113. Parts placement 1 Figure 114.
PAMS RAE-3 8. Troubleshooting Technical Documentation 5.1 EGSM Receiver General Instructions for troubleshooting Select Product Alt+p . . . . . . . . Open… RAE–3 Select: Select: Product Alt+p Band b EGSM e Testing Alt+e RF Controls RX Continuous r Alt+r Cont. Mode Ch: 60 Alt+o, 60 AGC Absolute: 8 Multislot on Alt+u, (if on remove checkmark) Apply The set–up should now look like this (Figure 115): Figure 115. Apply a 947.06771MHz (channel 60 + 67.
PAMS RAE-3 8. Troubleshooting Technical Documentation Measuring with an oscilloscope on “Hagar RXI” or “Hagar RXQ” this picture should be seen from a working EGSM receiver: Figure 116. Signal amplitude 390mV p–p DC offset 1,1V Frequency 67kHz If this picture is not seen, continue to the next section. 5.1.1 Troubleshooting diagram for EGSM Receiver EGSM Fault tree Apply –95dBm 947.
PAMS RAE-3 8. Troubleshooting Technical Documentation 5.1.2 EGSM Signal Path For easy error tracing it is important to know the signal path of the EGSM receiver. The components can be grouped into blocks and drawn as shown below (Figure 118) .
PAMS RAE-3 8. Troubleshooting 5.1.5 Technical Documentation Hagar The balanced RX signal is mixed with a signal from the local oscillator at the same frequency as the wanted RX signal. After mixing the signal is converted to a singleended signal in the DtoS (Differential to Singleended) amplifier. The signal is now filtered in a BIQUAD filter to provide channelseparation, amplified in the BB_Gain amplifier and DC compensated in DCN2.
PAMS RAE-3 8. Troubleshooting Technical Documentation 5.2 PCN Receiver General Instructions for troubleshooting Connect the phone to a PC with a DAU–9P cable Start Wintesla–Service–Software and Select Product Alt+p Open… RAE–3 Select: Product Alt+p b Band PCN Select: p Alt+e Testing RF Controls RX Continuous r Alt+r Cont. Mode Ch:700 Alt+o, 700 AGC Absolute: . . . . 8 Multislot on Alt+u, if on remove checkmark The set–up should now look like this (Figure 119): Figure 119. Apply a 1842.
PAMS RAE-3 8. Troubleshooting Technical Documentation Figure 120. Signal amplitude 350 mV p–p DC offset 1,1V Frequency 67kHz If this picture is not seen, continue to the next section. PCN Fault tree Apply –95 dBm 1842.
PAMS RAE-3 8. Troubleshooting Technical Documentation 5.2.1 PCN Signal Path For easy error tracing it is important to know the signal path of the PCN receiver. The components can be grouped into blocks and drawn as shown below.
PAMS RAE-3 8. Troubleshooting Technical Documentation to a single ended signal in the DtoS (Differential to Single ended) amplifier. The signal is now filtered in a BIQUAD filter to provide channel separation, amplified in the BB_Gain amplifier and DC compensated in DCN2.
PAMS RAE-3 8. Troubleshooting Technical Documentation 5.3 EGSM Transmitter General troubleshooting instructions Apply a RF–cable to the RF–connector to allow the transmitted signal to act as normal. RF–cable should be connected to measurement equipment or to at least a 10–dB attenuator, otherwise the PA may be damaged. Start Wintesla–Service–Software and Select: Alt+p Product Band b GSM Select: Testing Alt+e TX Continuos 5.3.
PAMS RAE-3 8. Troubleshooting 5.3.2 Technical Documentation Troubleshooting diagram for EGSM Transmitter EGSM TX troubleshooting YES Check with oscilloscope : R565:: VREF Vdc = 1.5V ? R700 & R740 VTX Vdc = 2.7 V? TPJ320 TXP Vdc>2.5 V ? C557 VRX Vdc = 2.7 V ? C561 VSYN_2 Vdc = 2.7 V ? C550 VXO Vdc = 2.7 V ? NO Check Baseband YES Check with oscilloscope : R546 & C640 TXQ_0 Vac= 0.4Vpp, Vdc=0.8V R546 & C640 TXQ_180 Vac=0.4Vpp, Vdc=0.8V NO Check Baseband R541 & C541 TXI_0 Vac=0.4Vpp, Vdc=0.
PAMS RAE-3 8. Troubleshooting Technical Documentation (EGSM TX troubleshooting continued) Spectrum analyzer: PA N702, pin 8 pwr>+1dBm, 902MHz NO Check V801, PA buffer R753 3dB att. Use WinTesla to select: TX_Data Type: Random TX power Level: 15 YES Spectrum analyzer: PA N702, pin 4 NO Check PA N702 Check Power Control Loop Check TXC NO Check Directional coupler L553 RX/TX switch Z670 Power = +21 dBm, 897, 6 MHz YES Spectrum analyzer: L502 Pout = +8dBm, 902 MHz YES GSM TX OK Figure 125.
PAMS RAE-3 8. Troubleshooting 5.4 Technical Documentation PCN Transmitter General troubleshooting instructions Apply a RF–cable to the RF–connector to allow the transmitted signal to act as normal. RF–cable should be connected to measurement equipment or to at least a 10–dB attenuator, otherwise the PA may be damaged. Start Wintesla–Service–Software and Select: Alt+p Product Band b PCN Select: p Testing Alt+e TX Continuos RF Controls r TX Power Level: BASE Alt+x, b . . . . . . . . . . . .
PAMS RAE-3 8. Troubleshooting Technical Documentation 5.4.2 Troubleshooting diagram for PCN Transmitter PCN TX Troubleshooting YES Check with oscilloscope : R565:: VREF Vdc = 1.5V ? R700 & R740 VTX Vdc = 2.7 V? TPJ320 TXP Vdc>2.5 V ? C557 VRX Vdc = 2.7 V ? C561 VSYN_2 Vdc = 2.7 V ? C550 VXO Vdc = 2.7 V ? NO Check Baseband YES Check with oscilloscope : R546 & C640 TXQ_0 Vac= 0.4Vpp, Vdc=0.8V R546 & C640 TXQ_180 Vac=0.4Vpp, Vdc=0.8V NO Check Baseband R541 & C541 TXI_0 Vac=0.4Vpp, Vdc=0.
PAMS RAE-3 8. Troubleshooting Technical Documentation (PCN TX troubleshooting continued) Use WinTesla to select: TX_Data Type: Random TX power Level: 5 YES Spectrum analyzer: PA N702, pin 4 NO Check PA N702 Check Power Control Loop Check TXC NO Check directional coupler L553 RX/TX switch Z670 Power = +18 dBm, 1747,6 MHz YES Spectrum analyzer: L502 Power = +20 dBm, 1747,6 MHz YES PCN TX OK Figure 128.
PAMS RAE-3 8. Troubleshooting Technical Documentation 5.5 Synthesizer There is only one PLL synthesiser generating frequencies for both Rx and Tx in both bands ( PCN and GSM). VCO frequency is divided by 2 or by 4 in HAGAR depending on which band is active. General troubleshooting instructions Start Wintesla–Service–Software and Select: Product Alt+p Band b EGSM Select: Testing e Alt+e RF Controls r RX Continuous Alt+r Cont.
PAMS RAE-3 8. Troubleshooting 5.5.3 Technical Documentation Troubleshooting diagram for PLL Synthesizer From WinTesla chose: Product> Band > EGSM Testing> RF Controls > Rx continuous > Ch 60 Spectrum Analyzer Oscilloscope No VCO output ( G800 out) 3788 MHz Yes VCTCXO Power Supply (G830 Vcc) 2,7 V No Yes PLL block functional Check CCONT Oscilloscope VCTCXO output (G830 out) 26 MHz, approx. 0.8 Vpp Oscilloscope VCO Power Supply (G800Vcc) 2.
PAMS RAE-3 8. Troubleshooting Technical Documentation If the phone goes ‘dead’ very short time after the power is turned ON, possible reason for this might be that 13 MHz system clock signal is not coming to the BB. Use the following chart to find the problem. Oscilloscope Oscilloscope Turn the phone ON and measure power supply fo r the VCTCX ( G800 Vcc) 2.7 V No Check CCONT, phone is ’dead’ Yes Oscilloscope Measure the output signal of the VCTCXO ( G830 out) appx.
PAMS RAE-3 8. Troubleshooting 5.5.
PAMS RAE-3 8. Troubleshooting Technical Documentation 5.6 Frequency lists Table 6. PCN frequencies and corresponding VCO frequencies CH 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 Issue 1 06/01 TX 1710.2 1710.4 1710.6 1710.8 1711.0 1711.2 1711.4 1711.6 1711.8 1712.0 1712.2 1712.4 1712.6 1712.8 1713.0 1713.2 1713.4 1713.6 1713.8 1714.0 1714.2 1714.4 1714.6 1714.8 1715.0 1715.2 1715.4 1715.6 1715.
PAMS RAE-3 8. Troubleshooting CH 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 Page 8 – 130 Technical Documentation TX 1717.6 1717.8 1718.0 1718.2 1718.4 1718.6 1718.8 1719.0 1719.2 1719.4 1719.6 1719.8 1720.0 1720.2 1720.4 1720.6 1720.8 1721.0 1721.2 1721.4 1721.6 1721.8 1722.0 1722.2 1722.4 1722.6 1722.8 1723.0 1723.2 1723.4 1723.6 1723.8 1724.0 1724.2 1724.4 1724.6 1724.8 1725.
PAMS RAE-3 8. Troubleshooting Technical Documentation CH 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 Issue 1 06/01 TX 1726.0 1726.2 1726.4 1726.6 1726.8 1727.0 1727.2 1727.4 1727.6 1727.8 1728.0 1728.2 1728.4 1728.6 1728.8 1729.0 1729.2 1729.4 1729.6 1729.8 1730.0 1730.2 1730.4 1730.6 1730.8 1731.0 1731.2 1731.4 1731.6 1731.8 1732.0 1732.2 1732.4 1732.6 1732.8 1733.0 1733.2 1733.
PAMS RAE-3 8. Troubleshooting CH 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 Page 8 – 132 Technical Documentation TX 1734.4 1734.6 1734.8 1735.0 1735.2 1735.4 1735.6 1735.8 1736.0 1736.2 1736.4 1736.6 1736.8 1737.0 1737.2 1737.4 1737.6 1737.8 1738.0 1738.2 1738.4 1738.6 1738.8 1739.0 1739.2 1739.4 1739.6 1739.8 1740.0 1740.2 1740.4 1740.6 1740.8 1741.0 1741.2 1741.4 1741.6 1741.
PAMS RAE-3 8. Troubleshooting Technical Documentation CH 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 Issue 1 06/01 TX 1742.8 1743.0 1743.2 1743.4 1743.6 1743.8 1744.0 1744.2 1744.4 1744.6 1744.8 1745.0 1745.2 1745.4 1745.6 1745.8 1746.0 1746.2 1746.4 1746.6 1746.8 1747.0 1747.2 1747.4 1747.6 1747.8 1748.0 1748.2 1748.4 1748.6 1748.8 1749.0 1749.2 1749.4 1749.6 1749.8 1750.0 1750.
PAMS RAE-3 8. Troubleshooting CH 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 Page 8 – 134 Technical Documentation TX 1751.2 1751.4 1751.6 1751.8 1752.0 1752.2 1752.4 1752.6 1752.8 1753.0 1753.2 1753.4 1753.6 1753.8 1754.0 1754.2 1754.4 1754.6 1754.8 1755.0 1755.2 1755.4 1755.6 1755.8 1756.0 1756.2 1756.4 1756.6 1756.8 1757.0 1757.2 1757.4 1757.6 1757.8 1758.0 1758.2 1758.4 1758.
PAMS RAE-3 8. Troubleshooting Technical Documentation CH 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 Issue 1 06/01 TX 1759.6 1759.8 1760.0 1760.2 1760.4 1760.6 1760.8 1761.0 1761.2 1761.4 1761.6 1761.8 1762.0 1762.2 1762.4 1762.6 1762.8 1763.0 1763.2 1763.4 1763.6 1763.8 1764.0 1764.2 1764.4 1764.6 1764.8 1765.0 1765.2 1765.4 1765.6 1765.8 1766.0 1766.2 1766.4 1766.6 1766.8 1767.
PAMS RAE-3 8. Troubleshooting CH 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 Page 8 – 136 Technical Documentation TX 1768.0 1768.2 1768.4 1768.6 1768.8 1769.0 1769.2 1769.4 1769.6 1769.8 1770.0 1770.2 1770.4 1770.6 1770.8 1771.0 1771.2 1771.4 1771.6 1771.8 1772.0 1772.2 1772.4 1772.6 1772.8 1773.0 1773.2 1773.4 1773.6 1773.8 1774.0 1774.2 1774.4 1774.6 1774.8 1775.0 1775.2 1775.
PAMS RAE-3 8. Troubleshooting Technical Documentation CH 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 Issue 1 06/01 TX 1776.4 1776.6 1776.8 1777.0 1777.2 1777.4 1777.6 1777.8 1778.0 1778.2 1778.4 1778.6 1778.8 1779.0 1779.2 1779.4 1779.6 1779.8 1780.0 1780.2 1780.4 1780.6 1780.8 1781.0 1781.2 1781.4 1781.6 1781.8 1782.0 1782.2 1782.4 1782.6 1782.8 1783.0 1783.2 1783.4 1783.6 1783.
PAMS RAE-3 8. Troubleshooting Technical Documentation CH 884 885 TX 1784.6 1784.8 vco 3569.2 3569.6 RX (TX+95) 1879.6 1879.8 VCO 3759.2 3759.6 Table 7. GSM frequencies and corresponding VCO frequencies CH TX vco RX (TX+95) VCO 975 880.2 3520.8 925.2 3700.8 976 880.4 3521.6 925.4 3701.6 977 880.6 3522.4 925.6 3702.4 978 880.8 3523.2 925.8 3703.2 979 881.0 3524.0 926.0 3704.0 980 881.2 3524.8 926.2 3704.8 981 881.4 3525.6 926.4 3705.6 982 881.6 3526.
PAMS RAE-3 8. Troubleshooting Technical Documentation Table 7. GSM frequencies and corresponding VCO frequencies CH TX vco RX (TX+95) VCO 1009 887.0 3548.0 932.0 3728.0 1010 887.2 3548.8 932.2 3728.8 1011 887.4 3549.6 932.4 3729.6 1012 887.6 3550.4 932.6 3730.4 1013 887.8 3551.2 932.8 3731.2 1014 888.0 3552.0 933.0 3732.0 1015 888.2 3552.8 933.2 3732.8 1016 888.4 3553.6 933.4 3733.6 1017 888.6 3554.4 933.6 3734.4 1018 888.8 3555.2 933.8 3735.
PAMS RAE-3 8. Troubleshooting Technical Documentation Table 7. GSM frequencies and corresponding VCO frequencies CH TX vco RX (TX+95) VCO 23 894.6 3578.4 939.6 3758.4 24 894.8 3579.2 939.8 3759.2 25 895.0 3580.0 940.0 3760.0 26 895.2 3580.8 940.2 3760.8 27 895.4 3581.6 940.4 3761.6 28 895.6 3582.4 940.6 3762.4 29 895.8 3583.2 940.8 3763.2 30 896.0 3584.0 941.0 3764.0 31 896.2 3584.8 941.2 3764.8 32 896.4 3585.6 941.4 3765.6 33 896.6 3586.4 941.
PAMS RAE-3 8. Troubleshooting Technical Documentation Table 7. GSM frequencies and corresponding VCO frequencies CH TX vco RX (TX+95) VCO 61 902.2 3608.8 947.2 3788.8 62 902.4 3609.6 947.4 3789.6 63 902.6 3610.4 947.6 3790.4 64 902.8 3611.2 947.8 3791.2 65 903.0 3612.0 948.0 3792.0 66 903.2 3612.8 948.2 3792.8 67 903.4 3613.6 948.4 3793.6 68 903.6 3614.4 948.6 3794.4 69 903.8 3615.2 948.8 3795.2 70 904.0 3616.0 949.0 3796.0 71 904.2 3616.8 949.
PAMS RAE-3 8. Troubleshooting Technical Documentation Table 7. GSM frequencies and corresponding VCO frequencies CH TX vco RX (TX+95) VCO 99 909.8 3639.2 954.8 3819.2 100 910.0 3640.0 955.0 3820.0 101 910.2 3640.8 955.2 3820.8 102 910.4 3641.6 955.4 3821.6 103 910.6 3642.4 955.6 3822.4 104 910.8 3643.2 955.8 3823.2 105 911.0 3644.0 956.0 3824.0 106 911.2 3644.8 956.2 3824.8 107 911.4 3645.6 956.4 3825.6 108 911.6 3646.4 956.6 3826.4 109 911.8 3647.
PAMS RAE-3 Technical Documentation 6 8. Troubleshooting Diagrams of Test Points Diagrams of test points are in a separate A3 document 09 Schematics.
PAMS RAE-3 8. Troubleshooting Technical Documentation This page intentionally left blank.
