02.34
Admin
Petunjuk Penggunaan Digital Frequency Counter
Dalam dunia reparasi ponsel, penggunaan Frequency Counter mutlak diperlukan sebagai instrument pengukuran. Syarat kerja agar ponsel bisa hidup yaitu Tegangan, Clock, dan Data.
Untuk mengukur tegangan dapat digunakan AVO Meter, Data berhubungan Software dan analisa melalui PC dan Box Flasher. Sedangkan Clock harus diukur dengan Frequency Counter atau Oscilloscope. Frequency Counter dapat mengukur besaran clock dengan sangat akurat hingga 6 digit di belakang koma.
Clock dihasilkan oleh komponen pada ponsel yang bernama Crystal Oscillator (VCTCXO). Yang akan dikirimkan kepada RF IC selanjutnya oleh RF IC akan diolah menjadi RF Clock (System Clock) dan dikirim ke CPU sebagai syarat kerja CPU.
Komponen VCTCXO pada DCT3 dengan CPU MAD2PR1 = 13 Mhz (5110,3210), dan CPU MAD2WD1 sebesar 26 Mhz. (3310,8210,dsb) sedangkan pada DCT4 & WD2 VCTCXO = 26 Mhz, pada BB5 VCTCXO = 38,4 Mhz
Tanpa Frequency Counter, kita tidak dapat menganalisa kerusakan dengan tepat. Untuk itu marilah kita mulai belajar mengggunakan Frequency Counter tsb.
Kenali Panelnya :
TOMBOL
1. Tombol ON/OFF : Untuk Menyalakan/mematikan alat.
2. Tombol GATE TIME : Untuk memilih waktu tercapainya gelombang (dalam satuan detik). Ada 3 pilihan yaitu :
0,1 detik : Gelombang akan tercapai dalam waktu 0,1 detik
1 detik : Gelombang akan tercapai dalam waktu 1 detik
10 detik : Gelombang akan tercapai dalam waktu 10 detik
Berapapun Gate Time yg kita pilih, hasilnya sama saja. Hanya beda keakuratan digit dibelakang koma. Umumnya digunakan 0,1 atau 1 detik. Untuk 10 detik jarang digunakan karena terlalu lama menunggunya.
3. Tombol SELECTOR : Untuk Memilih Channel/saluran frequency yang akan digunakan. Ada 5 pilihan yaitu :
CH0 : Untuk mengukur frequency yang besarnya diatas 30 Mhz hingga 2,4 Ghz (LED Mhz & G akan menyala)
CH1 : Untuk mengukur frequency yang besarnya 1 Mhz hingga 30 Mhz (LED MHz saja yang menyala)
CH2 : Untuk mengukur frequency yang besarnya 10 Hz hingga 999 Khz (LED Khz saja yang menyala)
CH3 : Hanya berfungsi sbg Counter yang akan menghitung jika probe dipegang (LED OFF akan menyala)
CH4 : Untuk mengukur frequency crystal pasif yang dicolok ke socket C. (LED Khz & µS akan menyala)
4. Tombol FUNCTION : Sehabis memilih Gate Time & Channel tekan tombol ini untuk segera memulai pengukuran.
Bila tidak ditekan, pengukuran tetap akan tetap dilakukan namun menunggu selang beberapa detik.
5. Tombol REST : Hasil pengukuran pada layar dapat diberhentikan (Pause) dengan menekan tombol ini.
6. Tombol C XTAL : Jika ditekan, otomatis akan masuk CH4, akan mengukur Crystal yg ditancap di soket C.
SOKET
A. Pasang Kabel Probe di soket A untuk mengukur frequency yang besarnya 10 Khz s/d 30 Mhz
B. Pasang Kabel Probe di soket B untuk mengukur frequency yang besarnya diatas 30 Mhz s/d 2,4 Ghz
C. Tancap Crystal Pasif di soket C untuk mengukur langsung tanpa probe. Gunakan Selector CH4
LED INDICATOR
I. LED G : Akan menyala jika dipilih Channel 0
II. LED Mhz : Akan menyala jika dipilih Channel 1
III. LED Khz : Akan menyala jika dipilih Channel2
IV. LED OF : Akan menyala jika dipilih Channel3
V. LED µS : Akan menyala jika dipilih Channel4
KALIBRASI FREQUENCY COUNTER
Dibagian belakang Frequency Counter ini selain terdapat soket kabel Power untuk dihubungkan ke stop kontak PLN 220V, terdapat pula lubang Sample Frequency 6 Mhz. Berguna saat kita ingin mengetahui apakah Frequency Counter ini masih berfungsi akurat/tdk.
Caranya :
· Nyalakan FC, lalu Setting FC à GATE TIME = 0,1 detik, SELECTOR = CH1, Kabel Probe colok di Soket bawah (A)
· Tusuk Probe di soket bagian belakang FC tsb. Penjepit/ GND Probe tdk perlu digunakan.
· Lihat hasil tampilan pada layar FC, jika menunjukkan 6.000 Mhz, menunjukkan bahwa FC ini masih akurat.
CONTOH CARA-CARA PENGUKURAN PADA PONSEL
Selalu nyalakan Power Supply (PS) set 4V, pasang kabel VBAT,BSI, GND pada connector Battere, untuk memberikan tegangan pengganti batere ke ponsel, agar rangkaian pada ponsel bekerja. Sehingga dapat dilakukan pengukuran.
I. 1. Mengukur Sleep Clock Crystal 32 Khz (RTC = Real Time Clock Crystal)
I. 2. Mengukur RF Clock Crystal DCT3/DCT4 13 Mhz atau 26 Mhz
I. 3. Mengukur RF Clock Crystal BB5 38,4 Mhz
II. 4. Mengukur SYS Clock 19,2 Mhz untuk OMAP serta penanganannya
III. 5. Mengukur Flash Cloc, SDRAM Clock & Trouble shootingnya
IV. 6. Mengukur IF (Intermediate Frequency) 232 Mhz & 71 Mhz pada DCT3 dgn RF IC SUMMA & Mixer IC CRFU3
1.I. Mengukur Sleep Clock Crystal 32 Khz (RTC = Real Time Clock Crystal)
· Setting FC --> Gate Time = 1 second, SELECTOR Ch2, Kabel Probe (-) jepit ke GND PCB, jarum Probe tusuk ke Test Point (TP1) Pengukuran (salah satu kaki Crystal 32 Khz)
· Nyalakan ON/OFF HP, lihat hasil di FC. Jika terbaca 32,768 Khz, maka dipastikan 32 Khz Crystal OK
· Lalu jarum Probe ukur di TP2 Sleep Clock berdasarkan skema. Jika terbaca 32,768 Khz, bisa dipastikan IC Power OK (CCONT,UEM,RETU,AVILMA,GAZOO). Jika tdk terbaca hasilnya, cek IC Power tsb.
Phoenix Service Software 2011.08.005.45529 Cracked
Main component versions in the release:
? DK2 Driver Version 07.14.0.25
? Nokia Connectivity Cable USB Driver Version 7.1.39.0
? Flash Update Package 2011.010.000
? FLS-x Drivers Version 2.09.28
? FUSE Connection Manager v 2011.6.0.62
MAIN CHANGES & ERROR CORRECTIONS FROM PREVIOUS VERSION 2011.8.3.45122
New Products added
? RM-670
New features
? New version of FUSE connection Manager
? New version of Flash Update Package
? New version of Autotuning components
? New version of Product API
? New version of Tucson components. NOTE: Tucson operations combined with ?flash? ? option are now
handled in the same way as ?refurbishment?, which requires Mass Memory Content File to be available.
? Tucson components now support RM-704 and product using same engine
Error Corrections & changes
? Correction to RX-51 phone SW related error which caused security self test fail after combo memory
has been replaced and product is autotuned successfully
? Correction to DCT-4 Band Information writing
? Correction to use with USER rights. Connections and other configurations made with ADMIn rights can
now be used with USER rights
? Correction to RM-555 eMMC file programming during refurbishment flashing ( Genius Case #177026)
? Correction to hanging problem in Envira ? Tool ( ZIP ? file generator)
? Envira ? Tool can now collect Phoenix crash file ( Minidump.dmp) into the same ZIP ? file with other
log files
? FUSE ? Connection Manager now starts in NO CONNECTION ? state each time Phoenix is started. User
must always select the desired connection after starting Phoenix. This helps to avoid problems caused
by changes in tool setup which have been made while Phoenix was shut down.
? Change to Tucson menu items and their use with ?flash? option: Flashing is now handled in the same
manner as ?refurbishment? ? option in Firmware Update ? menu. This means that the use of Mass
Memory File is mandatory and it needs to be available in the product specific directory. if file is not
available, process will fail an it will be aborted.
? New common data package location in use.Please see document SR1315 in KICS Information Center
for further information.
? All Nokia Service Software Applications will use following location for product specific data:
- Windows XP: C:\Documents and Settings\All Users\Application Data\Nokia\Packages
- Windows 7: C:\Program Data\Nokia\Packages
? During installation, Data Packages should be installed in these directories, if they install to any other
location by default. Target folder for local data packages can be changed in the installation wizard
manually
? This version contains the latest Tucson components. Therefore it is not necessary to use Tucson
Add-On Installation Packages
? Before you start Phoenix or Care Suite installation to Windows 7 the User Account Control (UAC)
should be turned off from Windows Control Panel settings.
? For more information concerning new options in ?Firmware Update? ? menu and their use, Please see
document SR1313 in KICS Information Center.
? Product Code changes for USB Only ? phones (RX-51, RM-596 etc) work only when used with FPS-21
Flash Prommer and USB connection from prommer rear panel to phone. Please select USB as Product
Active Media
? Do not use Flash option simultaneously with product code change for USB Onbly phones, flash phone
separately with Firmware Update
? It is recommended to use FPS-21 flash prommer with TCPIP connection when refurbishing USB Only -
phones (RM-596 etc) due to mandatory optional MMC file size.
? Connection media to FLS-5 must be configured to be ?USB_FBUS?. After FLS-4 support has been
removed FBUS connection does not work anymore with FLS-5
KNOWN ERRORS & LIMITATIONS
? Software downgrade with Tucson system is only possible for BB 5.0 products supporting the Data
Package 2 concept.
? Flashing with setup FLS-5, SS-46 and product specific adapter is not supported anymore. FLS-5 can
be used with other product specific cables and adapters, but not with SS-46 Interface Adapter.
? If you install old DCT-4 data packages, Flash Update Package File installation path may be wrong. This
is caused by very old DCT-4 data packages which contain Flash Update Package and overwrite current
information during installation. If you experience problems when updating FPS-x prommers, please
check that Phoenix ?Prommer maintenance? is looking for the files from the correct location which is
?C:\Program Files\Common Files\Nokia\Tss\Flash?. If not, Phoenix will show error ?Update via ini ? file
failed?. In this case, select ?Update? from that Phoenix ?Prommer maintenance? ? UI, browse to correct
directory and select ?fpsxupd.ini? for all other prommers except the FPS-8.
? Refurbishment flashing and product code change for RX-51 product requires SX-4 card to be
available.
? FPS-21 flashing for RX-51 works only with TCPIP connection. FPS-21 prommer with new HW version
11 has been released to correct this. Sales pack code is 0089J83 , old HW version is not delivered
anymore
? Please refer to product specific documents and instructions concerning the limitations of the RX-51
product
? RX-51 flashing does not work when CU-4 is used
? RX-51 Product Code changes work only without FLASH option, please flash phone separately
? When version 2010_12_8_42304 or newer with FUSE connection manager is installed on top of older
Phoenix versions, there may be an additional delay of several minutes when you start Phoenix for the
first time. Please wait patiently; Phoenix will start after configuration is finished.
? When using Data Package download functions with online connection, download times may
occasionally be long. This is not caused by Phoenix (or Care Suite). The download speed from online
servers is occasionally is known to be slow, depending on how data is buffered on caching servers.
? After you close Phoenix, it may not restart. To rectify this:
- Use Windows Task Manager to manually shut down phoenix.exe and FuseService.exe processes, or
optionally restart your PC
? It is not possible to program Mass Media Content file to some devices over direct USB cable
connection, due to the large size of the file. For these models a feature called ?Media Check? has been
implemented. When this type of product is connected to service software / PC via direct USB cable the
refurbishment option will be disabled. Please use a flash prommer.
? To be able to use the help files in Windows 7 you need to install Windows Help program
(WinHlp32.exe) for Windows 7. Ways to locate WinHlp32.exe:
- Start Phoenix with online connection to Internet, select ?Help? and ?Phoenix help?. Click the
?Microsoft Help and Support? website link. Download WinHlp32 and install it.- Go to
Microsoft Corporation: Software, Smartphones, Online, Games, Cloud Computing, IT Business Technology, Downloads . Type ?WinHlp32″ to ?Search Microsoft.com? ? field. Locate
Windows Help program (WinHlp32.exe) for Windows 7 and install it
? When using flash prommers, only one connection type to one prommer is allowed. Please use either
NFPD USB or NFPD TCPIP connection to one prommer, not both connections to same prommer
Supported operating systems and user rights
? Windows XP Service Pack 1 or higher
? When installing Phoenix into Win XP you must have local admin rights.
? When using in Win XP, user must have power user rights.
? Windows 7 32 Bit version
? DK2 Driver Version 07.14.0.25
? Nokia Connectivity Cable USB Driver Version 7.1.39.0
? Flash Update Package 2011.010.000
? FLS-x Drivers Version 2.09.28
? FUSE Connection Manager v 2011.6.0.62
MAIN CHANGES & ERROR CORRECTIONS FROM PREVIOUS VERSION 2011.8.3.45122
New Products added
? RM-670
New features
? New version of FUSE connection Manager
? New version of Flash Update Package
? New version of Autotuning components
? New version of Product API
? New version of Tucson components. NOTE: Tucson operations combined with ?flash? ? option are now
handled in the same way as ?refurbishment?, which requires Mass Memory Content File to be available.
? Tucson components now support RM-704 and product using same engine
Error Corrections & changes
? Correction to RX-51 phone SW related error which caused security self test fail after combo memory
has been replaced and product is autotuned successfully
? Correction to DCT-4 Band Information writing
? Correction to use with USER rights. Connections and other configurations made with ADMIn rights can
now be used with USER rights
? Correction to RM-555 eMMC file programming during refurbishment flashing ( Genius Case #177026)
? Correction to hanging problem in Envira ? Tool ( ZIP ? file generator)
? Envira ? Tool can now collect Phoenix crash file ( Minidump.dmp) into the same ZIP ? file with other
log files
? FUSE ? Connection Manager now starts in NO CONNECTION ? state each time Phoenix is started. User
must always select the desired connection after starting Phoenix. This helps to avoid problems caused
by changes in tool setup which have been made while Phoenix was shut down.
? Change to Tucson menu items and their use with ?flash? option: Flashing is now handled in the same
manner as ?refurbishment? ? option in Firmware Update ? menu. This means that the use of Mass
Memory File is mandatory and it needs to be available in the product specific directory. if file is not
available, process will fail an it will be aborted.
? New common data package location in use.Please see document SR1315 in KICS Information Center
for further information.
? All Nokia Service Software Applications will use following location for product specific data:
- Windows XP: C:\Documents and Settings\All Users\Application Data\Nokia\Packages
- Windows 7: C:\Program Data\Nokia\Packages
? During installation, Data Packages should be installed in these directories, if they install to any other
location by default. Target folder for local data packages can be changed in the installation wizard
manually
? This version contains the latest Tucson components. Therefore it is not necessary to use Tucson
Add-On Installation Packages
? Before you start Phoenix or Care Suite installation to Windows 7 the User Account Control (UAC)
should be turned off from Windows Control Panel settings.
? For more information concerning new options in ?Firmware Update? ? menu and their use, Please see
document SR1313 in KICS Information Center.
? Product Code changes for USB Only ? phones (RX-51, RM-596 etc) work only when used with FPS-21
Flash Prommer and USB connection from prommer rear panel to phone. Please select USB as Product
Active Media
? Do not use Flash option simultaneously with product code change for USB Onbly phones, flash phone
separately with Firmware Update
? It is recommended to use FPS-21 flash prommer with TCPIP connection when refurbishing USB Only -
phones (RM-596 etc) due to mandatory optional MMC file size.
? Connection media to FLS-5 must be configured to be ?USB_FBUS?. After FLS-4 support has been
removed FBUS connection does not work anymore with FLS-5
KNOWN ERRORS & LIMITATIONS
? Software downgrade with Tucson system is only possible for BB 5.0 products supporting the Data
Package 2 concept.
? Flashing with setup FLS-5, SS-46 and product specific adapter is not supported anymore. FLS-5 can
be used with other product specific cables and adapters, but not with SS-46 Interface Adapter.
? If you install old DCT-4 data packages, Flash Update Package File installation path may be wrong. This
is caused by very old DCT-4 data packages which contain Flash Update Package and overwrite current
information during installation. If you experience problems when updating FPS-x prommers, please
check that Phoenix ?Prommer maintenance? is looking for the files from the correct location which is
?C:\Program Files\Common Files\Nokia\Tss\Flash?. If not, Phoenix will show error ?Update via ini ? file
failed?. In this case, select ?Update? from that Phoenix ?Prommer maintenance? ? UI, browse to correct
directory and select ?fpsxupd.ini? for all other prommers except the FPS-8.
? Refurbishment flashing and product code change for RX-51 product requires SX-4 card to be
available.
? FPS-21 flashing for RX-51 works only with TCPIP connection. FPS-21 prommer with new HW version
11 has been released to correct this. Sales pack code is 0089J83 , old HW version is not delivered
anymore
? Please refer to product specific documents and instructions concerning the limitations of the RX-51
product
? RX-51 flashing does not work when CU-4 is used
? RX-51 Product Code changes work only without FLASH option, please flash phone separately
? When version 2010_12_8_42304 or newer with FUSE connection manager is installed on top of older
Phoenix versions, there may be an additional delay of several minutes when you start Phoenix for the
first time. Please wait patiently; Phoenix will start after configuration is finished.
? When using Data Package download functions with online connection, download times may
occasionally be long. This is not caused by Phoenix (or Care Suite). The download speed from online
servers is occasionally is known to be slow, depending on how data is buffered on caching servers.
? After you close Phoenix, it may not restart. To rectify this:
- Use Windows Task Manager to manually shut down phoenix.exe and FuseService.exe processes, or
optionally restart your PC
? It is not possible to program Mass Media Content file to some devices over direct USB cable
connection, due to the large size of the file. For these models a feature called ?Media Check? has been
implemented. When this type of product is connected to service software / PC via direct USB cable the
refurbishment option will be disabled. Please use a flash prommer.
? To be able to use the help files in Windows 7 you need to install Windows Help program
(WinHlp32.exe) for Windows 7. Ways to locate WinHlp32.exe:
- Start Phoenix with online connection to Internet, select ?Help? and ?Phoenix help?. Click the
?Microsoft Help and Support? website link. Download WinHlp32 and install it.- Go to
Microsoft Corporation: Software, Smartphones, Online, Games, Cloud Computing, IT Business Technology, Downloads . Type ?WinHlp32″ to ?Search Microsoft.com? ? field. Locate
Windows Help program (WinHlp32.exe) for Windows 7 and install it
? When using flash prommers, only one connection type to one prommer is allowed. Please use either
NFPD USB or NFPD TCPIP connection to one prommer, not both connections to same prommer
Supported operating systems and user rights
? Windows XP Service Pack 1 or higher
? When installing Phoenix into Win XP you must have local admin rights.
? When using in Win XP, user must have power user rights.
? Windows 7 32 Bit version
