---------------------------------------------------------

about this release

product: tems investigation

version: 6.1.3

---------------------------------------------------------
corrected functions in release 6.1.3:

data collection
- pctel triband scanners without the bsic option, fails to initiate in ti.
- missing signaling from motorola devices affecting l3 and event generation.
- rlc bler dl & ul not decoded with nokia 6230
- when doing multiple lock on rats with the r1a v800 (and the new tems z800)
you sometimes get error message
- spectrum scanned number of items is not available in the spectrum analyzer
bar chart
- in the windows with separate setup options for "properties" and "change ms"
the window forgets the ms that has been chosen
- wrong display of the list of sc in idle or fach for tm6200 (z107)

route analysis
- cell broadcast message displayed in wrong monitor in route analysis
- problems with the spider cursor in the route analysis map
- wrong session handling for ps data in route analysis when performing more
than two data sessions per ras dial.

---------------------------------------------------------
new features

- new hasp driver which allows installations from cd

- support for google earth kml format

- report enhancements in data collection html report

---------------------------------------------------------

known bugs and limitations

data collection:
- when using motorola devices, rach message tx is actually rach message tx
control power since motorola is calculating rach msg control power and not
rach msg power with this equation
- channel verification does not work with the s710 phone.
- l3 direction (ul/dl) is wrong for some messages when using qualcomm
devices.
- a timer will expire after 10 minutes when doing ftp downloads or uploads.
the error message that follows says: aborted by user, which is not correct.
- some customers experience problems with the tems investigation distributed
hasp4 driver, version 4.96, on windows xp in combination with the parallel
port or the pcmcia security keys. this has been solved by using the older
driver version, 4.85. that version may be received by taking contact with
tems support.
- tems phone verification 1.2 and tems investigation 6.x can not co-exist on
 the same computer.
- problems may arise when tems investigation is run on slow computers. the
symptoms of these problems are repeated disconnects of connected handsets
or long processing times.
- windows may have problems resolving all usb driver connections if multiple
ues are connected in a single action, e.g. through a usb hub. this will
show in the device manager as yellow exclamation marks. pulling the usb
cables from the ues and then plugging them back in one at a time might
solve the problem.
- on some computers, problems with the serial port will cause "resynch"
reports to appear in the mode report message window. to resolve these
problems, take the following steps:
- disable the computer's ir port.
- turn power management off. see the getting started manual, chapter 3.
- (dell computers only:) from the start menu, choose: programs > dell open
manage client > disable dell open manage client.
- reboot.
- do not install any software that periodically scans the com/usb ports on
computers to which you intend to connect tems equipment. the reason is that
these programs may cause difficult connect problems in tems investigation.
- firewalls and other security products may prevent the tems investigation
from running two or more data sessions at the same time.
- some gps units might be erroneously identified as a "ms serial ballpoint"
device in windows 2000. use the device manager to disable the device. note:
do not remove the device, as it will then be reinstalled at next reboot.
- virtual ir ports or virtual bluetooth ports should not be installed on the
computer.
- to run a command sequence with voice call commands (such as dial and end
call) with the motorola a835/a845 or the nokia 6650/7600/wcdma 1900, there
is a need to also connect dc1, e.g. the "a835/a845 data cable" device, to
the modem port.
- when you save a command sequence to a .csq file, an ftp or http server user
name and password given in a command are saved with the file (encrypted).
note that another user who runs your command sequence will be accessing the
server using the same user name and password.
- "wait (all)" in the command sequence works as follows: when a phone (or
whatever equipment is used in the sequence) reaches the wait (all) command,
a countdown begins which is specific to that device and independent of any
other devices. if another device reaches the wait (all) command at a
different time, its countdown will always be at a different stage.
therefore, as long as several devices are waiting simultaneously,
flickering of the counter might occur.
- when a blocked call occurs, or when the rf conditions are too bad to make a
video call, the command sequence will reach a state where it does not
continue.
- the handset control tool in data collection only works for sony ericsson
gsm phones (e.g. t610, t68).
- during logfile recording as well as during logfile replay, temporary files
are created by the application to enable the user to browse the history of
the logfile. these files can become very large (3-4 times the logfile
size), the exact size depending on the number of devices connected to the
application at recording time. the temporary files are named according to
the format “temsn” and created in the windows temp directory (default:
c\path\tmp, where the path is defined by the environment variable tmp; in
both windows 2000 and windows xp, the tmp variable can be modified from the
control panel: system properties > advanced > environment variables). make
sure there is plenty of space on the disk where the temp directory resides.
 -- the temporary files are removed when the application is exited; however,
if the application terminates abnormally, this might not happen. the files
must then be removed manually.
- negative frame numbers may occur occasionally during replay of older
logfiles. these frame numbers should be regarded as invalid.
- when using the serving cell indication in the map window to show the
strongest scanned cpich, this works only for the 1st umts frequency (the
one decoded into the information elements named “1st”).
- interpolation of gps positions does not work with the pctel seegull lx
scanner gps.
- using word as an editor in outlook on machines where tems investigation is
installed may completely disable all reading of e-mail. this situation is
solved by register the ole32.dll. click start and select run. type:
o regsvr32.exe %windir%\system32\ole32.dll
- when locking a nokia phone on a gsm control channel (e.g. rat state = gsm
and lock on frequency band), the phone stays only for a short while on the
arfcn it has been locked on, and then moves on to a different channel.

route analysis
- devices in logfiles from previous versions of tems investigation gsm/tems
investigation wcdma may not always be correctly identified. older samsung
phones, for example, may appear as “unknown clsid unsupported”.
- if one message causes more than one event to be generated, all presentation
windows will show only one of the events. only in the navigator, in the
tree structure within the logfile, all events appear.
- the legend in the map window flickers when items are selected/deselected.
whenever a checkbox in the legend tab is checked or unchecked, the contents
of that window pane are redrawn.
- changing the presentation in a slave map window sometimes adds an offset to
the plot in the master window from which the slave was created. (an easy
workaround is to close the slave, refresh the master, and open a new
slave.)
- it is possible to delete columns in message monitor windows but not to add
them again.
- the events window cannot show both ms and dc events at the same time.
- it is possible to do “show best/worst” on all information elements on the
map regardless if they are suited for it.
- care should be taken when comparing (for example) events in the ran tuning
report with events shown during replay in data collection, logfile report
and route analysis. ran tuning calculates statistics only on complete calls
and data sessions. calls and data sessions that are set up before the
logfile recording is started, or end after the logfile recording is
stopped, are not used for calculating statistics.

---------------------------------------------------------
contact information

for support in the use of tems investigation, please contact ericsson

according to the directions found at www.ericsson.com/tems under the link
“contacts”.

---------------------------------------------------------
copyright information

tems is a trademark owned by telefonaktiebolaget l m ericsson.

® 2005 ericsson tems ab

all rights reserved. no part of this program may be reproduced in any form
without the written permission of the copyright holder.