TFE/K–1 Service Software ”WinTesla” is specially designed to facilitate the
servicing of first generation WLL terminals.
The software can be used to control the phone according to the user’s requirements merely by entering commands via the keyboard / mouse of a PC connected to the phone.
This section refers to Service Software Version 1.4 NMP After Sales will notify
service personnel about future upgrades via Technical Bulletins. Software upgrades will be available from your local NMP outlet.
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
– Operating System: DOS Version 5 & Microsoft Windows 3.1 or later
– Display: VGA based display
– Service Software for 3.5” disk (product code: 0774052) or for 5.25” disk
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 09/97
PAMS
TFE/K–1
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–4S and XCM–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.
Service Software Instructions
Original 09/97
Page 7
TFE/K–1
PAMS
Service Software Instructions
Attach the DAU–2T PC/MBUS adapter to the PC serial port, using an RS–232
9–pin to 25–pin adapter if necessary. Attach one end of the modular cable
XCM–1 to DAU–2T, and the other end to the system connector with the help of
the Service Adapter AFW–2.
Technical Documentation
Install Procedure
Start the phone by connecting the power supply to TFK–1. Switch PC power on.
To install software, proceed as follows:
1.If WinTesla has already been installed to PC, jump to step 5.
If not, Insert the WinTesla installation disk into drive A of your PC
2. Start the Installation program:select File –> Run from Program
3. Follow the Installation Software instructions.
4. Restart windows.
5. Remember to install WinTesla at least once before.
Insert the TFE/K–1 DLL installation disk into drive A of your PC.
6.Start Installation program:select File –> Run from Program
7. Follow the Installation Software instructions
manager menu, then type
A:INSTALL
manager menu, then type
A:INSTALL
and press OK button
and press OK button
Page 8
8.Start WinTesla by double clicking the WinTesla Icon
Original 09/97
PAMS
TFE/K–1
Technical Documentation
Service Software Instructions
Introduction to Service Software Package User
Interface
This chapter gives a short description of the Service Software properties.
Service Software Hardware Environment
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, receives 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.
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 laptops, the power saving feature
MUST be switched off.
Service Software Environment
Service Software user interface is intended for Microsoft Windows 3.1x 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 Microsoft Windows Version 3.1
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
Original 09/97
Page 9
TFE/K–1
PAMS
Service Software Instructions
can be done by using keyboard and/or mouse. When messages from phone
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 TFE/K–1 there are two dlls:
– Functionality DLL is TFEK1.DLL
– User Interface DLL is TFEK1EN.DLL.
Command Line Parameters
There are NO command line parameters.
Technical Documentation
Page 10
Original 09/97
PAMS
TFE/K–1
Technical Documentation
Service Software Instructions
Common Properties of the User Interface
This chapter describes how the User Interface CLF will appear to the user.
The User Interface is 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 box
When the Service Software application is invoked, by clicking the Service Software icon, the Login dialog box will be displayed on the screen.
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. All Rights Re-
served”.
Login Box edit box (–)
User Login ID edit box, where user enters his/her faultlog user name.
OK button (default key)
User name is stored in memory and dialog box is closed. When the dialog box
is closed, the application starts.
Original 09/97
Page 11
TFE/K–1
PAMS
Service Software Instructions
Cancel button (ESC)
The dialog box is closed and application is started, but the Faultlog feature is
disabled.
Help button (F1)
Activates the Windows Help application and displays context sensitive Help.
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
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
• Maximize button
• Minimize button
• Name of the application
• Restore button
The properties of these elements and their usage is described in Ref 3– Microsoft Windows Version 3.1 Users Guide chapter one (Windows Basics) and
chapter two (Application Basics).
is located at the top of the window.
Page 12
Original 09/97
PAMS
TFE/K–1
Technical Documentation
Menu bar
The
menu bar
The menu bar is a dynamic element and is dependent on the dongle type fitted
and whether a phone is connected.
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 desired menu. In that case, selection is done by pressing
Enter
.
Refer to section 3.3 – Menu bar for a detailed description of the contents of the
menu bar.
Menus can also be selected by using the mouse as described in Ref 3– Microsoft Windows Version 3.1 Users Guide.
Status bar
The
status bar
The status bar contains information about the menu selections and events.
The left area of the status bar describes actions of menu items as the user
uses the arrow keys to navigate through menus.
Service Software Instructions
is below the title bar and contains all available menu selections.
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-
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
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 09/97
Page 13
TFE/K–1
PAMS
Service Software Instructions
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:
roduct*
• P
onfigure*
• C
• Tuning
• Testing
• Software
ealer
• D
• View
• Help*
* – 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.
Technical Documentation
Product
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 an
OK button before the operation is performed.
The Product menu MUST contain the following menu items:
• N
ewCtrl+R
• Open...
• Close
• I
nitialize
• N
ormal ModeF5
ocal ModeShift+F5
• L
•F
aultlog
• A
ctivate Faultlog... F9
• E
dit Faultlog...
• E
xitAlt+F4
Page 14
Original 09/97
PAMS
TFE/K–1
Technical Documentation
Configure
The Configure menu MUST contain the following menu items:
• O
ptions...
• D
irectories...
aultlog...
• F
• Phone Type Specific configuration items (where applicable)
Tuning
The Tuning menu MUST contain the following menu sections:
• Receiver
• Transmitter
• Voltages
• Phone Type Specific tuning items (where applicable)
An example T
Service Software Instructions
uning menu is shown below:
Testing
• A
FC...
• R
SI (AGC)...
• Tx
Power...
• Tx IQ
• B
• C
• LCD
• L
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 MUST contain the following menu sections:
• Quick Tests
• Digital
• User Interface Flexi
• Transmitter
• Receiver
• Automatic Tests
• Phone Type Specific testing items (where applicable)
...
attery...
harger A/D...
A/D...
CD Display...
Original 09/97
Page 15
TFE/K–1
PAMS
Service Software Instructions
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 pop–up from the Receiver menu item.
sting menu is shown below:
Technical Documentation
Software
The Software menu MUST contain the following menu sections:
• Phone Identity/Numbers
• Flashing
• Phone Type Specific software items (where applicable)
An example S
• Phone I
• S
tart Up Self–Tests...
• Set Default V
• N
etwork Settings...
• L
A Settings...
• W
arranty State...
oftware menu is shown below:
dentity
alues...
Page 16
Original 09/97
PAMS
TFE/K–1
Technical Documentation
Dealer
The Dealer menu MUST contain 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
• U
ser Settings
• Reset UI Default V
• Q
uick Install
• S
etup code
• A
utomatic Area Code
View
Service Software Instructions
ealer menu is shown below:
alues
The View menu MUST contain the following sections:
• Service Windows
• Production Windows (where applicable)
• R&D Windows (where applicable)
An example V
• Q
uick RF Info...
• P
hone Identity...
Phone Identity Window
The Phone Identity window should contain, as a minimum, the following data:
• Software Version(s)
• Hardware Version(s)
• Serial Number(s)
• Product Code
iew menu is shown below:
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.
Original 09/97
Page 17
TFE/K–1
PAMS
Service Software Instructions
Help
The Help menu MUST contain the following menu items:
• I
ndex
• G
eneral Help
• U
sing Help
• A
bout WinTesla
Mouse Cursors
The standard 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 application has taken the control and any
actions from user will be ignored.
Technical Documentation
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
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
Page 18
Original 09/97
PAMS
TFE/K–1
Technical Documentation
Ctrl Hot Keys
KeyDescriptionDefined by
Ctrl+NFile – NewMicrosoft
Ctrl+OF
Ctrl+PF
Ctrl+RP
Shift Hot Keys
KeyDescriptionDefined by
Shift+F5Local ModeNMP
Key Strokes
KeyDescriptionDefined by
Service Software Instructions
ile – OpenMicrosoft
ile – PrintMicrosoft
roduct – NewNMP