The NHE–1/3/4 Service Software is specially designed to facilitate the servicing of GSM cellular telephones.
The software can be used to control the phone according to the user’s requirements merely by entering commands via the keyboard or mouse of a PC connected to the phone.
This section refers to the Service Software Version 2.3. NMP After Sales will
notify service personnel about future upgrades via Technical Bulletins. Software
upgrades will be available from your local NMP outlet.
Minimum Required Servicing Equipment
– Computer: Intel 386/33 MHz or compatible with one unused serial port
(COM1 or COM2*), one parallel port (LPT1), hard disk recommended.
Technical Documentation
– Memory: 4 MB or more
– Operating System: DOS Version 5 & Microsoft Windows 3.11 or later
– Display: VGA based display (640 x 480)
– WinTesla Service Software: SWSA1 for 3.5” disk (product code: 0774046)
– Software Protection Key PKD–1 (product code 0750018)
– M2BUS interface cable DAU–2 (product code 0750006)
– RS–232 adapter, 9 to 25 pins (product code 4626170)
– Service cable SCS–1 (product code 0770010)
Page 6
*)
Note:A number of PC’s of an older generation use the Intel, National Semiconductor, or
United Microelectronics IC 8250 as the serial port UART. This is a comparatively
inefficient circuit for current purposes and does not necessarily support the
M2BUS adapter at 9600 baud. The newer UART’s NS16450 and NS16550AF of
National Semiconductor offer solutions for these problems.
Original 11/97
After Sales
Service Software Insructions
Technical Documentation
Mechanical Connections
Caution:Ensure that you have switched off the PC and the printer before
making connections !
Caution:Do not connect the PKD–1 to the serial port. This could damage
the PKD–1 !
The software controls the phone via a separate adapter connected to the serial
port of the PC and to the telephone’s M2BUS (DAU–2 and SCS–1).
Attach the protection key PKD–1 to parallel port one (25–pin female D–connector) of the PC. When connecting the PKD–1 to the parallel port be sure that you
insert the PC end of the PKD–1 to the PC (male side). If you use a printer on
parallel port one, place the PKD–1 between the PC and your printer cable.
The PKD–1 should not effect devices working with it. If some errors occur (errors in printing are possible) please try printing without the PKD–1. If printing is
OK without the PKD–1 please contact your dealer. We will offer you a new
PKD–1 in exchange for your old one.
NHE–1/3/4
Original 11/97
Page 7
Service Software Instructions
After Sales
NHE–1/3/4
Technical Documentation
Attach first the RS–232 adapter cable to the PC’s 9–pin serial port. Connect the
M2BUS adapter (DAU–2) to the RS–232 cable. Connect the service cable
SCS–1 to the M2BUS adapter (DAU–2) and attach the other end of the cable
to the bottom connector of the phone.
Start Up Procedure
Start the phone by pressing the power–on button of the handset. Switch PC
power on.
To installing software, proceed as follows:
1. Insert Service Software disk into
drive A of your PC
2. Start Windows:type
3. Start Installing program:select
4. Follow Installation Software
instructions
WIN
and press
File –> Run
menu, then type
press OK button
Enter
from Program Manager
A:INSTALL
and
Page 8
Original 11/97
After Sales
Service Software Insructions
Technical Documentation
Introduction to Service Software Package User
Interface
This chapter gives a short description of the Service Software properties.
Service Software/Hardware Enviroment
To run the Service Software, a parallel port software protection device (PKD–1)
has to be connected. The user can use the Service Software functions for testing all supported Phone Types. The functions send messages from the PC to
the phone, receive results and show them on the PC display. The messages
are sent via a low level NMP proprietary bus protocol. An example bus is an
M2BUS interface, which needs M2BUS adapter (DAU–2) connected to the PC
RS–232 port and special M2BUS cable.
NHE–1/3/4
The recommended minimum hardware standard to run the Service Software
package is any computer which is 386 33Mhz or greater with at least 4 MB of
memory and VGA type display (640x480). This assumes that only the Service
Software package is active, i.e. other Windows packages are not running in the
background.
Note: if the Service Software is to be run on a laptop, the power saving feature
MUST be switched off.
Service Software Enviroment
Service Software user interface is intended for Microsoft Windows 3.11 environment running in enhanced mode. For those who are familiar with Windows environment this application will be easy to use. Detailed information about Windows and application usage can be found from Ref 3– Microsoft Windows
Version 3.11 Users Guide chapter one (Windows Basics) and chapter two (Application Basics).
As an ordinary Windows application, the main idea in the user interface is that
selections are made with menus, push buttons and shortcut keys. Selections
can be done by using keyboard and/or mouse. When messages from phone
Original 11/97
Page 9
Service Software Instructions
After Sales
NHE–1/3/4
are received, they cause display updating in special display windows. There is
always a status bar displayed at the bottom of the main window which contains
information about current actions.
Service Software Executables
Only one executable is needed – WinTesla.
For NHE–1/3/4 there are two DLL’s:
– Functionality DLL is NH134.DLL
– User Interface DLL is NH134EN.DLL
Command Line Parameters
There are NO command line parameters.
Technical Documentation
Page 10
Original 11/97
After Sales
Service Software Insructions
Technical Documentation
Common Properties of the User Interface
This chapter describes how the User Interface CLF must appear to the user.
The User Interface MUST be capable of being driven without the use of a
mouse, as the service engineer rarely has space on the bench to use a mouse.
Login Dialog
When the Service Software application is invoked, by checking on the Service
Software icon, the Login dialog box will be displayed on the screen.
Nokia logo and
application name
NHE–1/3/4
Nokia logo and application name bitmap (–)
Displays Nokia logo and name of the application.
Application version static text (–)
Contains the name and version of the application.
Copyright notice static text (–)
Copyright is informed as: “Nokia Mobile Phones (c) 1996. AllRights Reserved”.
Application version
Copyright version
Login box
Login Box edit box (–)
OK button (default key)
Original 11/97
The user Login ID edit box, where the user enters his faultlog user
name. (See Faultlog User Guide)
Page 11
Service Software Instructions
After Sales
NHE–1/3/4
Cancel button (ESC)
Help button (F1)
Main Window
The application supports a
service software interface will present a
pearance.
Note: MDI is to allow for future expansion, e.g. R&D features.
Technical Documentation
The user name is stored in memory and the dialog box is closed.
When the dialog box is closed, the application starts.
The Dialog box is closed and application is started, but the Faultlog
feature is disabled.
Activates the Windows Help application and displays context sensitive Help.
Multiple Document Interface (MDI).
Single Document Interface (SDI)
However, the
ap-
Title bar
The
title bar
A title bar contains the following elements:
• Application Control–menu button
• Maximise button
• Minimise button
• Name of the application
• Restore button
The properties of these elements and their usage is described in Ref 3– Microsoft Windows Version 3.11 Users Guide chapter one (Windows Basics) and
chapter two (Application Basics).
Menu bar
menu bar
The
The menu bar is a dynamic element and is dependent on the dongle type fitted,
and whether a phone is connected.
is located at the top of the window.
is below the title bar and contains all available menu selections.
Page 12
Original 11/97
After Sales
Service Software Insructions
Technical Documentation
Underlined characters in menu names and options indicates that the menu
selection can be done by pressing
be selected by activating menu bar with
row–keys to highlight the desired menu. In that case, selection is done by
pressing
Menus can also be selected by using the mouse as described in Ref 3–Microsoft Windows Version 3.11 Users Guide
Status bar
The
The status bar contains information about the menu selections and events.
The left area of the status bar describes the actions of menu items as the user
uses the arrow keys to navigate through menus.
The status bar texts are explained in detailed in each of command’s description.
The right areas of the status bar indicate which of the following keys are
latched down:
IndicatorDescription
Enter
status bar
NHE–1/3/4
Alt+ underlined character
Alt
– key ( or
.
is displayed at the bottom of the Service Software main window.
F10
. Options can also
key ) and using ar-
USEREntered Login ID.
CAPThe Caps Lock key is latched down.
NUMThe Num Lock key is latched down.
SCRLThe Scroll Lock key is latched down.
Tool bar
The
tool bar
document.
is NOT defined and will not be implemented until specified by this
Original 11/97
Page 13
Service Software Instructions
After Sales
NHE–1/3/4
Menu Bar
The Service Software package will have two menu bar configurations. The first,
is an abbreviated version that contains the minimum number of menus that allows package configurations when a phone is NOT connected. The second is
described below:
The menu bar MUST only contain the follow menus for the Service Software
package when a phone is connected:
• P
• C
• T
• Te
• S
• D
• V
• H
Technical Documentation
roduct*
onfigure*
uning
sting
oftware
ealer
iew
elp*
Product
* – always displayed, even if no phone is connected.
A menu is broken down into sections that are indicated with menu separators.
Each sections identifies a logical difference from itself and other sections, i.e.
between transmitter and receiver. Any items that are required to be added to a
menu lists will be added on the bottom of the appropriate menu section list. If a
new item is to be added which is common to two or more phone types, then
that menu item will become a common menu item.
The menu lists will use the Microsoft [...] symbol after an item name to indicate
that selecting that item will NOT initiate an operation immediately, i.e. a dialog
box will be displayed for the user to select options or type in data and press the
OK button before the operation is performed.
The Product menu contains the following menu items:
• N
ewCtrl+R
• O
pen...
lose
• C
• I
nitialize
• Normal ModeF5
• Local ModeShift+F5
aultlog
•F
• Activate Faultlog... F9
• Edit Faultlog...
Page 14
• Ex
itAlt+F4
Original 11/97
After Sales
Service Software Insructions
Technical Documentation
Configure
The Configure menu contains the following menu items:
• O
ptions...
• D
irectories...
• F
aultlog...
• Phone Type Specific configuration items (where applicable)
Tuning
The Tuning menu contains the following menu sections:
• Receiver
• Transmitter
• Voltages
• Phone Type Specific tuning items (where applicable)
An example T
• AFC...
NHE–1/3/4
uning menu is shown below:
Testing
• R
SSI (AGC)...
• Tx
Power...
• Tx I/Q
• B
• Charger A/D...
Additional menu items may be added within the sections according to the
phone type being tuned, e.g. a Charger tuning menu item will be added after
the Battery tuning item, but not in the Transmitter tuning section.
The Testing menu contains the following menu sections:
• Quick Tests
• Digital
• User Interface Flexi
• Transmitter
• Receiver
...
attery A/D
• Automatic Tests
• Phone Type Specific testing items (where applicable)
Original 11/97
Page 15
Service Software Instructions
After Sales
NHE–1/3/4
Technical Documentation
An example Te
• Q
uick Testing (RF)...
• S
elf Tests
• A
DC Readings
• Au
dio
• D
isplay
• C
all Simulation...
• N
oise Sensitivity...
Additional menu items may be added within the sections according to the
phone type being tested.
Where a menu item consists of more than one test, a pop–up menu may be
added to identify the appropriate sub–tests, e.g. there may be two receiver
tests required for a particular phone type (Bit Error Rate and RSSI Monitoring).
These will be shown as a popup from the Receiver menu item.
sting menu is shown below:
Software
The Software menu contains the following menu sections:
• Phone Identity/Numbers
• Flashing
• Phone Type Specific software items (where applicable)
An example S
• Phone I
• Serial Number T
• P
roduct Profile...
• S
tart Up Self–tests...
• Set Default V
oftware menu is shown below:
dentity
ransfer...
alues
Page 16
Original 11/97
After Sales
Service Software Insructions
Technical Documentation
Dealer
The Dealer menu contains the following menu sections:
• Phone UI Data Editors
• Phone UI Data Transfer
• Phone Re–Initialization Functions
• Subscriber Data
• Phone Type Specific dealer items (where applicable)
An example D
• Short C
• U
ser Settings
• Set UI/DEV Default V
ode Memory
View
NHE–1/3/4
ealer menu is shown below:
alues ...
The View menu contains the following sections:
• Service Windows
• Production Windows (where applicable)
• R&D Windows (where applicable)
An example V
• Q
uick/RF Info...
• P
hone Information...
iew menu is shown below:
Original 11/97
Page 17
Service Software Instructions
After Sales
NHE–1/3/4
hone Identity Window
P
The Phone Identity window should contain, as a minimum, the following data:
• Software Version(s)
• Hardware Version(s)
• Serial Number(s)
• Product Code
This window will only be used as a display window and therefore will not allow
editing of the displayed data. This window will not contain any controls other
than a scroll bar.
Help
The Help menu contains the following menu items:
• I
ndex
Technical Documentation
• G
eneral Help
• U
sing Help
• A
bout WinTesla
Page 18
Original 11/97
After Sales
Service Software Insructions
Technical Documentation
Mouse Cursors
The standards Windows pointer will be used as the mouse cursor.
During time consuming tasks e.g. communication to phone, an hour glass will
be shown informing the user that a task is in progress. The application uses the
hour glass cursor to inform user that the application has taken the control and
any actions from user will be ignored.
When a function is initiated, the hour glass will be displayed and when the function has finished the mouse pointer will return to normal.
Reserved Keys
The following Hot keys and Short Cut keys are reserved either as Microsoft
standard keys or as part of the Common Look and Feel specified by this document.
Short Cut Function Keys
NHE–1/3/4
KeyDescriptionDefined by
F1Context Sensitive HelpMicrosoft
F5Normal ModeNMP
Shift+F5Local ModeNMP
F9Activate FaultlogNMP
F10Goto Menu BarMicrosoft
Ctrl+F4Close Active WindowMicrosoft
Alt Hot Keys
KeyDescriptionDefined by
Alt+F4Exit Active ApplicationMicrosoft
Alt+HHelpMicrosoft
Ctrl Hot Keys
KeyDescriptionDefined by
Ctrl+NFile – NewMicrosoft
Ctrl+OF
Ctrl+PF
Ctrl+RP
Original 11/97
ile – OpenMicrosoft
ile – PrintMicrosoft
roduct – NewNMP
aultlog Pop–upNMP
ctivate FaultlogNMP
dit FaultlogNMP
xit ApplicationNMP
onfigureNMP
ptionNMP
irectoriesNMP
aultlogNMP
uning MenuNMP
FCNMP
SSI(AGC)NMP
PowerNMP
atteryNMP
hargerNMP
NMP
Page 20
Alt+ETe
Alt+E,QQ
Alt+E,SS
Alt+E,AA
Alt+E,UAu
sting MenuNMP
uick Testing RFNMP
elf TestsNMP
DC ReadingsNMP
dioNMP
Original 11/97
After Sales
Service Software Insructions
Technical Documentation
Alt+E,DD
Alt+E,CC
Alt+E,NN
Alt+SS
Alt+S,IPhone I
Alt+S,TSerial Number T
Alt+S,PP
Alt+S,SS
Alt+S,VSet Default V
Alt+DD
Alt+D,CShort C
Alt+D,UU
Alt+D,VSet UI Default V
Alt+VV
The Help User Interface will be the standard Windows help tool called WinHelp.
The context sensitive help is activated with F1–key. Help contains also Using
Help which describes how to use help facility. Refer to the Windows manual for
detailed description on the Windows Help.
Dialog boxes
The Service Software application uses many different dialog boxes. Dialog
boxes are used to display data and prompt the user for input.
uick/RF InfoNMP
hone InformationNMP
elp MenuMicrosoft
ndexMicrosoft
eneral HelpMicrosoft
sing HelpMicrosoft
bout WinTeslaMicrosoft
Dialog boxes are opened from menus or with shortcut keys. Dialog boxes have
different properties but some features are common.
All service dialog boxes must be modal, that is, the user will not be able to start
another operation without first closing the present dialog box.
All dialog boxes will contain the following entities:
Original 11/97
Page 21
Service Software Instructions
After Sales
NHE–1/3/4
– Help button
– Title bar
– At least one button other than Help
– Application Control–menu Button
Common Dialog boxes
This sections describes the common dialog boxes used in the Service Software package, and the context in which they will be used.
Note Message Box
When the user has made an illegal selection, a
opened and message text is displayed. The message box is also opened when
the program has some information for the user. The size of the dialog box may
vary. An information dialog box is recognized by the !–icon.
Technical Documentation
note message box
dialog will be
The dialog box will also contain an OK button and a Help button.
OK button (default key):
Help button (Alt+H):
Query Message Box
Confirmations and questions are asked in
box is recognized by the ?–icon.
The dialog box will also contain a Yes button, a No button, and a Help button.
Yes button (Alt+Y or Y) (default key):
No button (Alt+N or N):
Acknowledge displayed information and continue. The dialog box is
closed after selection.
Opens context sensitive help as F1–key does.
a query message box
Accepts confirmation or question.
. A query dialog
Page 22
Denies confirmation or question.
Help button (Alt+H):
Opens context sensitive help as F1–key does.
The buttons may also be OK and Cancel. The operation of these buttons are
the same as in the Note dialog box.
Original 11/97
After Sales
Service Software Insructions
Technical Documentation
Error Message Box
Error message dialog boxes use the Stop–icon. When a “Stop”–dialog box is
shown, the current operation is terminated.
The dialog box has a description about the failed operation and reason. Pressing F1 (Help) application opens the appropriate help topic that gives information
about recommended actions.
The dialog box will also contain an OK button and a Help button.
OK button (default key):
Acknowledges displayed information and terminate current operation. The dialog box is closed after selection.
Help button (Alt+H):
Open context sensitive help as F1–key does.
NHE–1/3/4
Original 11/97
Page 23
Service Software Instructions
After Sales
NHE–1/3/4
Custom Dialog boxes
All custom dialog boxes will contain the predefined buttons as defined below in
the section –
tional button types, but the addition of these non–standard buttons should be
carefully considered to minimise any inconsistencies between implementations.
The buttons will be positioned down the right–hand side of the dialog boxes.
The default action will be OK, except where that default action could result in
an irretrievable failure.
All tuning dialogs that contain tuning results, will display the old tuned data read
from the phone before the tuning was performed, as well as the newly tuned
data.
List boxes will be used to display lists of data, such as tuning data, test results
etc.
The use of Radio buttons should be limited and carefully considered. The use
of radio buttons defines the number of possible choices available to the user,
which may be acceptable for one project, but not for another.
Buttons.
Technical Documentation
However, it is recognised that features may require addi-
Buttons
All buttons must be the Microsoft style of buttons.
In general, the default button will be the OK button, the Close button or the Yes
button, but this will depend on the context of the dialog box that the button is
associated with.
OK button:
Accepts and validates entered settings and values and closes the
dialog. If the values have not been changed, then no action will be
taken. The status bar will reflect the status. The user should only be
queried, if the settings or values accepted will over–write data that
CAN NOT be reproduced.
A greyed OK button indicates that settings selected by the user are
not acceptable.
Close button:
Closes the current dialog box. Does not send or store anything and
closes the dialog. The Close button is only used for dialogs that do
not set or change any data.
Cancel button (Esc):
Page 24
Cancel operation. Does not send or store anything and closes the
dialog box.
A greyed Cancel button indicates that it is not possible to quit from
this dialog box.
Original 11/97
After Sales
Service Software Insructions
Technical Documentation
Yes button (ALT+Y or Y):
Replies Yes to a question asked of the user.
No button (ALT+N or N):
Replies No to a question asked of the user.
Help button (ALT+H):
Opens context sensitive help as F1–key does.
Reporting Status
The status bar will be used to report the present status to the user. When a feature is initiated, the status bar will be updated with a brief description of the
function. The status bar will also be updated at key points in a time consuming
function.
If an error is to be reported to the user, it will be displayed in the status bar as
well as displayed in a common error dialog box. This will mean the user is not
delayed from progressing on to the next operation unless an error occurs, in
which case, the user will have to acknowledge the error by pressing the OK
button.
NHE–1/3/4
Original 11/97
Page 25
Service Software Instructions
After Sales
NHE–1/3/4
NHE–1/3/4 Specific Features
Menu Bar
The Service Software’s menus adopts the menu structure specified by CLF.
Product
New command
ActivationStatus Bar Text
Alt, P, NRescan a new phone
Ctrl+R
This command scans a new product. When phone is found a product specific
functionality module is loaded. If no phone or wrong phone/cellular type is detected, functionality is unloaded and user is informed.
Technical Documentation
This function is also started automatically when the application is started. The
user can also specify a regular poll which enables the WinTesla application to
scan the new phone periodically. If the phone is still the same, no changes are
done. If the phone is changed (with same phone type only the serial number is
changed), the phone will be initialized to a normal mode. If the phone is
changed to a different phone type, the current dlls are unloaded and new ones
are loaded for that phone.
The initialization routine checks the phone’s cellular type (GSM/PCN), and if an
unsupported phone is detected, the WinTesla application does not load the dlls.
If quick info view is open, the window will be automatically updated.
If phone identification view is open, the window will be automatically updated.
pen... command
O
ActivationStatus Bar Text
Alt, P, OForce load phone specific functionality
Enables the user to force load specific phone’s WinTesla dll’s. It also disables
further phone type detection with New command.
Page 26
Note: This selection is for applications that has reflashing functionality. Reflashing is not implemented for NH–1 phones.
Original 11/97
Loading...
+ 59 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.