RN Nemo Outdoor 7.0.0.9 18th April 2013

RELEASE NOTES FOR NEMO OUTDOOR 7.0.0.
9
th
18 of April 2013
Yrttipellontie 10 | FI-90230 Oulu | Finland | tel. +358 50 395 7700 | www.anite.com/nemo
Introduction .............................................................................................................................................................. 5
New Features ............................................................................................................................................................ 6

2.1
Facebook Testing............................................................................................................................................... 6
2.2
Support for Windows 8 Operating System ........................................................................................................ 9
2.3
Audio Quality Signal Status with Voice Quality Measurement ......................................................................... 9
2.4
Kodiak InstaPoC Push-to-Talk Calls............................................................................................................... 11
2.5
AMR Codec Mode Forcing with Qualcomm Based UEs................................................................................... 12
2.6
Automated QChat PTT Calls ............................................................................................................................ 12
2.7
Nemo FSR1 Scanner Handler Enhancements .................................................................................................. 12
2.7.1
LTE MIMO Measurements ...................................................................................................................... 12
2.7.2
Support for Specifying Channel Bandwidth per Channel in LTE Scanning .............................................. 14
2.8
R&S TSMW Scanner Handler Enhancements ................................................................................................. 14
2.8.1
LTE Time Offset and Delay Spread Measurements ................................................................................ 14
2.8.2
2.9
PcTel MX and EX Scanner Handler Enhancements.......................................................................................... 15
2.9.1
LTE MIMO Measurements ...................................................................................................................... 15
2.9.2
LTE BCCH Message Decoding ................................................................................................................. 15
2.9.3
LTE Carrier RSSI Results per Antenna Port ............................................................................................. 15
2.9.4
2.10
User Interface .................................................................................................................................................. 16
2.10.1
Starting and Stopping Scripts Separately per Test Device ...................................................................... 16
2.10.2
Exporting Route Plan to MapInfo Maps ................................................................................................. 16
2.10.3
Measurement Service Setting Profiles ................................................................................................... 16
2.10.4
Sending Measurement Files Automatically to FTP Server ...................................................................... 16
2.10.5
Support for BSIC in Octal and Hexadecimal Format in BTS Files ............................................................ 16
2.10.6
Miscellaneous ......................................................................................................................................... 16
2.11
Handler Enhancements ................................................................................................................................... 17
2.11.1
LTE to HSPA and HSPA to LTE User Plane Handover Time with Qualcomm ........................................... 17
2.11.2
LTE EPS Bearer Events and Statistics with Qualcomm............................................................................ 17
2.11.3
Support for Network Interface Selection with Application Tester Handler ........................................... 17
2.11.4
Miscellaneous ......................................................................................................................................... 17
Error Corrections and Version History .................................................................................................................... 17
New Devices ............................................................................................................................................................ 17

4.1
Handsets and USB Modems ............................................................................................................................ 18
4.2
Scanning Receivers .......................................................................................................................................... 18
4.3
Nemo Outdoor 7.0.0.9 New Devices and Licenses ......................................................................................... 19
Qualcomm-based WCDMA and CDMA2000 Terminals and Data Cards ................................................................. 19
Computer Hardware and Software Requirements ................................................................................................. 19
Device Configuration and Workspace Files ............................................................................................................. 20
Installation............................................................................................................................................................... 20
8.1
Supported Operating Systems ........................................................................................................................ 20
8.2
First-time Installation ...................................................................................................................................... 20
8.3
Update/Upgrade ............................................................................................................................................. 20
8.4
Uninstallation .................................................................................................................................................. 21
8.5
HASP Dongle Runtime Drivers ......................................................................................................................... 21
Limitations with Windows 8 Operating System ...................................................................................................... 22
10
Limitations and Issues with Windows 7 Operating System .................................................................................... 22
11
File Format Changes ................................................................................................................................................ 23
12
Known Issues ........................................................................................................................................................... 24

12.1
General & User Interface ................................................................................................................................ 24
12.2
UEs................................................................................................................................................................... 25
12.2.1
Altair-based UEs ..................................................................................................................................... 25
12.2.2
Cassidian Handsets ................................................................................................................................. 25
12.2.3
Datang/Leadcore Handsets .................................................................................................................... 26
12.2.4
Motorola Handsets ................................................................................................................................. 26
12.2.5
Nokia Handsets ....................................................................................................................................... 26
12.2.6
Samsung Chipset-based UEs ................................................................................................................... 29
12.2.7
Qualcomm GSM/WCDMA-based UEs .................................................................................................... 29
12.2.8
Qualcomm (MDM9200/ 9600)-based UEs ............................................................................................. 34
12.2.9
LG LTE Modems (LG1000/ LG 2000) ....................................................................................................... 44
12.2.10
Qualcomm 3GPP2-based UEs ................................................................................................................. 44
12.3
Scanner Receivers ........................................................................................................................................... 44
12.3.1
Anritsu Scanners ..................................................................................................................................... 44
12.3.2
Nemo FSR1 Scanner................................................................................................................................ 44
12.3.3
PCTEL Scanners ....................................................................................................................................... 45
12.3.4
Rohde & Schwarz Scanners .................................................................................................................... 46
12.4
Nemo Invex ..................................................................................................................................................... 47
12.4.1
General ................................................................................................................................................... 47
12.4.2
Nemo Invex USB Isolation Module ......................................................................................................... 47
12.4.3
Nemo Invex UIC Module......................................................................................................................... 47
12.5
Other Devices .................................................................................................................................................. 48
12.5.1
GPS receivers .......................................................................................................................................... 48
12.5.2
TerraTec DMX 6Fire & Maya44 USB Sound Cards .................................................................................. 48
12.5.3
12.6
Beceem BCS200/BCSM 250/3300 Wimax .............................................................................................. 50
Applications & Protocols ................................................................................................................................. 50
13
Troubleshooting Device Connectivity Issues ........................................................................................................... 52
14
Troubleshooting Data Transfer Issues ..................................................................................................................... 53

14.1
PS Connection Works but No Data .................................................................................................................. 53
14.1.1
UAC Settings ........................................................................................................................................... 53
14.1.2
Antivirus Filtering ................................................................................................................................... 54
14.2
Low Data Throughputs .................................................................................................................................... 54
14.2.1
All Windows Versions ............................................................................................................................. 57
14.2.2
Windows XP ............................................................................................................................................ 58
14.2.3
Windows Vista/Windows7 ..................................................................................................................... 58
14.3
Issues with HTTP Browsing Testing ................................................................................................................. 60
1 Introduction
Nemo Outdoor is a pioneering and leading-edge network measurement, optimization, and benchmarking solution for
perfecting the air interface of wireless networks. It collects measurement results and geographical coordinates, and
these measurement results further provide valuable information for network planning, roll-out, tuning, verification,
optimization, maintenance, and benchmarking purposes. Nemo Outdoor is always among the first-to-market with
support for the very latest technologies, such as, LTE FDD and TDD, HSPA+ dual cell, CDMA, 1xEVDO, GSM, WCDMA,
WiMAX, iDEN, TETRA, and TD-SCDMA measurements.
Nemo Outdoor provides our customers with the flexibility and choice to meet the specific and growing needs of the
ever-evolving markets. Its powerful platform is expandable beyond current trends to those of the future, and all of
this materializes on a single platform. With Nemo Outdoor you can perform not only drive testing but also QoS and
benchmarking measurements on every standard network technology and on multiple simultaneous data connections.
This empowers the operators to reach both optimal network performance and time and cost-effectiveness.
Nemo Outdoor is extremely easy to set up, configure and use. Furthermore, Nemo Outdoors utterly customizable and
smooth user interface offers the users the possibility to customize data views and workspaces for their specific needs
at any given time. This flexibility further manifests itself in the open file format (ASCII) which enables customers to
integrate in their optimization processes the use of not only the upscale Anites post-processing tool Nemo Analyze,
but also those of third-party vendors. In addition, Nemo Outdoors import/export feature allows for all user settings to
be transferred to or from another computer.
Through our close cooperation with several mobile and scanner manufacturers we ensure that our customers always
get to select amongst the latest test equipment. Currently Nemo Outdoor supports more than 270 test terminals and
scanning receivers, a figure which is constantly on the increase to meet the rapidly changing customer needs for
optimal satisfaction.
2 New Features
2.1 Facebook Testing
Facebook is a social networking service launched in February 2004, owned and operated by Facebook, Inc.[5] As of
September 2012, Facebook has over one billion active users, [6] more than half of them using Facebook on a mobile
device. [7] In 2012 Facebook was the number one mobile application ranked in the U.S. Facebook users produce large
quantities of data sent over cellular networks when , for example, uploading pictures and sending messages. Social
networking is a relatively low-bandwidth pursuit, but when combined with other applications, such as, cloud storage
etc., it has the potential to drive significant levels of traffic. Because the Facebook social networking service is so
popular, it is worth taking it as the reference social networking service with Nemo tools.
With Nemo Tools users can perform manual or automated Facebook testing and use their Facebook account similar to
regular users. Users must register before using the site, after which they may create a personal profile, add other
users as friends, and exchange messages, including automatic notifications when they update their profile.
Following operations are initially supported:
Login (USER_ACCESS_TOKEN)
o
Post (text + image, HTTP Post)

o
Messages and photos can be uploaded to users profile
Friend list retrieval (friends.get)

o
Login with real user account using a browser-based access token.
Returns the Facebook user IDs of the current user's Facebook friends
User field retrieval (Get wall feed)

o
Place on a profile, page, or group where Facebook users post messages for others to see
Figure 1. Facebook operations in Nemo Outdoor.

Following information is logged for each operation:
Operation type
Attempt/ success/failure
Time elapsed
Amount of data received/sent
Content information (logged to data content event )
With session settings user name and user access token can be defined via Nemo Outdoor user interface. Transfer
settings contain text field for status update and also photo can be included. User can set a limit for feed retrievals.
Facebook testing is supported with single and multi configurations with a single CPU. Routing table modification must
be enabled with multi configuration. It should be noted that when routing table modification is enabled information
about the picture sizes cannot be decoded to DCONTENT event. This functionality is supported only when routing
table modification is disabled.
Figure 2. Facebook configuration.

The following events and statistics are available for Facebook testing:
Events:
Facebook Transfer Attempts

o
Facebook Transfer Success

o
Data transfer failure (DAF) event. Trigger point: User Access Token is invalid or expired
Data Transfer Request

o
Data transfer connect (DAC) event. Trigger point: User Access Token is valid
Facebook Transfer Failures

o
Data transfer attempt (DAA) event. Trigger point: Checks validity of User Access Token
DREQ event. Trigger point: JSON call to get user wall feed/friend list/HTTP post
Data Transfer Completed

o
DCOMP event. Trigger point: Return success if the retrieval is OK or HTTP POST with the image data
is successfully uploaded
Statistics:
Facebook connection attempts
Facebook connection success
Facebook connection failures
Facebook connection attempt success rate
Facebook connection success rate
Facebook connection time
Facebook disconnects (dropped)
Facebook disconnects (normal)
Facebook transfer attempts
Facebook transfer failures
Facebook transfer success
Facebook transfer success rate
Facebook transfer time
The start and stop trigger points for all operators are Data Transfer Request (DCOMP) and Data Transfer Complete
(DCOMP) events respectively. In addition to trigger points, application data throughput for both uplink and downlink
direction are recorded.
[5] Eldon, Eric (December 18, 2008). "2008 Growth Puts Facebook In Better Position to Make Money". VentureBeat
(San Francisco). http://venturebeat.com/2008/12/18/2008-growth-puts-facebook-in-better-position-to-makemoney/. Retrieved December 19, 2008
[6] Gavin, Clarke (July 2010). "Facebook re-write takes PHP to an enterprise past Remember C++? They do". Archived
from the original on 2012-05-30. http://archive.is/20120530/http://www.lextrait.com/Vincent/implementations.html.
Retrieved 2 February 2010
[7] Sengupta, Somini (May 14, 2012). "Facebook's Prospects May Rest on Trove of Data". The New York Times.
http://www.nytimes.com/2012/05/15/technology/facebook-needs-to-turn-data-trove-into-investor-gold.html.
Retrieved May 15, 2012.
2.2 Support for Windows 8 Operating System

Nemo Outdoor 7.0 is the first version compatible with Microsoft Windows 8 operating system. Both 32- and 64 bit
versions are supported. The following devices & configurations have been tested and approved with the Windows 8
64- bit operating system.
Device
Number of UEs/ CPU
Driver/ Notes
Huawei E392/ E398
Driver version: 23.003.07.00.03
Nokia C7-00
Driver version: 7.1.101.0
Nokia 500
Nokia Lumia 920
Driver version : Qualcomm HS-USB Modem 9001 v2.1.0.5 (modem
(RM-821)
port driver), Qualcomm Drivers for Windows v1.0.15 (add/remove

programs)
Samsung Galaxy S
Driver version: Kies version 2.3.3.12085_7, driver version 1.5.18.0
III GT-i9305
Sierra 320U
2.3 Audio Quality Signal Status with Voice Quality Measurement

End users are experiencing random audio muting during phone calls. When a call is answered, only silence can be
heard. When audio is lost during a phone call, it usually remains silent until the end of the call. These calls can also be
seen by observing Audio quality MOS scores as the score drops significantly during silent calls. The Mute Call
Detection functionality in Nemo Outdoor makes it easy to analyze phone calls where a low MOS score is caused by a
silent call or a muted call. A new parameter called Audio Quality Signal Status is shown real-time to indicate if audio
is present or not. During RX mode the voice quality measurement system continuously monitors the energy of the
received signal for each received audio frame and writes the audio quality signal status to the measurement file. If the
energy of the received signal drops below the specified threshold for a specified amount of time, the audio quality signal
state is set to Not detected. If the energy of the received signal goes above the specified threshold for a specified
amount of time, the audio quality signal state is set to Detected. The threshold values are fixed.
Audio Quality Signal Status can be observed in different views, such as, line graphs. Detection starts when the phone
audio mode is in reception (RX) mode. The synchronization tone can be seen at the beginning of the RX mode followed
by the actual received audio sample file. Depending on the reference sample file it is normal that during the reception of
the received sample file, audio is not necessarily detected all the time. For example, the case sample file includes a pause
in audio longer than the threshold value used for the detection.
Figure 3. Audio RX mode. Normal situation.
Audio lost
Figure 4. Silent call. Audio not detected.
Audio lost.
Muted call
Figure 5. Muted call. Audio lost during call. DL MOS scores as low as 1.49MOS.
10
Figure 6. Audio gap. Lost audio frames during RX mode.
2.4 Kodiak InstaPoC Push-to-Talk Calls

Kodiak InstaPoC, the next generation Push-to-Talk (PTT) technology based on the OMA PoC v2 standard, sets up calls
at sub-second speeds.
Kodiak InstaPoC, technology is developed by Kodiak Networks (http://www.kodiaknetworks.com). Kodiak InstaPoC
handsets and server software allow users to connect instantaneously with other Kodiak InstaPoC users anywhere in
the network. It enables one-to-one (private) and one-to-many (group) calls over the 3G/ 4G networks. Both call
modes are supported with Nemo Outdoor and Kodiak PTT calls can be done manually or automatically using scripts.
Normal call events and statistics are written when attempting or ending PTT calls. Different states of PTT calls, such as
idle, getting ready to receive, receiving, and transmitting are written to the VCHI event. Kodiak InstaPoC is supported
with Qualcomm and application tester handler with several handsets connected to same CPU. Please see the file
format specification for further information. Support for Kodiak PTT calls is an optional feature in Nemo Outdoor and
requires the license option 320081-21 and a Kodiak InstaPoC compatible handset, such as, Samsung SGH-I547C Galaxy
Rugby LTE.
11
2.5 AMR Codec Mode Forcing with Qualcomm Based UEs

With the AMR codec mode forcing functionality users can force a UE to use a certain AMR codec mode. The following
options are available:
-
None
GSM AMR FR
GSM AMR WB
GSM AMR HR
WCDMA AMR WB
Selection can be done in the Nemo Outdoor Measurement Properties dialog. Option is shown only for UEs supporting
voice calls. For example, when a UE is forced to the WCDMA AMR WB codec, it can freely use any WB AMR codec
from 6.6 kbps to 23.85 kbps. Please see the Nemo Outdoor Qualcomm data sheets for further information about
verified UEs.
2.6 Automated QChat PTT Calls

QChat PTT calls with manual commands and script files can be done via the Nemo Outdoor user interface. Verified
handsets are Kyocera Duramax and Huawei U3220.
2.7 Nemo FSR1 Scanner Handler Enhancements

2.7.1
LTE MIMO Measurements
Nemo FSR1 scanner provides the condition number and rank information to Nemo Outdoor once per second. MIMO
scanning results are reported for up to 32 cells (PCI) simultaneously. Condition number and other parameters shown
in the figure 7 are logged for each cell separately and contain scanning results per physical resource block.
MIMO parameters are logged to PRBSCAN event. Please note that a MIMO capable Nemo FSR1 down converter is
required to be able to make MIMO measurements. Furthermore, Nemo FSR1 firmware version 4.0 is required.
12
Figure 7.Supported Nemo FSR1 MIMO parameters

2.7.1.1
Indoor Measurement Mode
A new measurement option has been added to the Nemo Outdoor UI to enable the indoor measurement mode with
Nemo FSR1 scanner. In indoor measurement mode, the Nemo FSR1 scanner is synchronized with automatic frequency
control (AFC) instead of GPS time. This makes it possible to do indoor scanning without a GPS receiver. Indoor mode is
suitable for up to 10km/h (6 MPH) speeds and can be used for GSM, WCDMA, and LTE measurements. Nemo FSR1
firmware version 4.0 is required.
Figure 8. Nemo FSR1 scanner advanced properties.
13
2.7.2
Support for Specifying Channel Bandwidth per Channel in LTE Scanning
User can set LTE IF bandwidth (channel style) per selected channel via Nemo Outdoor Measurement Properties. Nemo
FSR1 wide band down converter and FSR1 firmware version 4.0 are required.
2.8 R&S TSMW Scanner Handler Enhancements

2.8.1
LTE Time Offset and Delay Spread Measurements
Time offset is the difference between the actual received P-SCH primary synchronization signal and the expected point
in time derived from the GPS reference time. The unit of the parameter is 32.552ns that is the same as the Ts
parameter defined by 3GPP TS 136.211 subclause 4. Range is 0 307199. To be able to measure LTE time offset, a GPS
antenna must be connected to the scanner.
The delay spread width is determined by the time difference (in chips) between the arrival of the first multi-path peak
component and the arrival of the last multi-path peak component. Delay spread measurement can be enabled via
Nemo Outdoor Measurement Properties dialog. The unit of the parameter is 32.552ns that is the same as the Ts
parameter defined by 3GPP TS 136.211 subclause 4. Range is 0 1023.
2.8.2
User can set LTE IF bandwidth (channel style) per selected channel via Nemo Outdoor Measurement Properties.
14
2.9 PcTel MX and EX Scanner Handler Enhancements

2.9.1
LTE MIMO Measurements
PcTel MX receivers provide information about the condition number, estimated CQI, and estimated throughput.
Estimated values are calculated based on RF measurements. The following new MIMO parameters are logged with
Nemo Outdoor. Values are written to PRBSCAN event. Requires MX LTE (FDD) 2x2 MIMO option OP530 (315016-06).
Figure 9.Supported PcTel MX MIMO parameters

2.9.2
LTE BCCH Message Decoding
LTE BCCH message decoding can be enabled via Nemo Outdoor Measurement Properties. When this option is
enabled, the scanner decodes MIB and SIB 1- SIB 13 messages. Requires MX Layer 3 option FD-LTE OP522-FD-LTE
(315016-10) and/ or MX Layer 3 option TD-LTE OP522-TD-LTE (315016-11).
2.9.3
LTE Carrier RSSI Results per Antenna Port
By default LTE carrier RSSI is logged per antenna port with PcTel MX and EX scanner receivers.
2.9.4
User can set LTE IF bandwidth (channel style) per selected channel via Nemo Outdoor Measurement Properties with MX
and EX scanner receivers.
15
2.10 User Interface

2.10.1
Starting and Stopping Scripts Separately per Test Device
User is able to stop and start script files of individual UEs while recording, allowing the other devices to stay connected
and run their specific scripts. With UEs not running a script, it is possible to manually control the UEs. Please see the
user manual for further details.
2.10.2
Exporting Route Plan to MapInfo Maps
Route plans can be exported to MapInfo maps via the map window by selecting Save Route Plan as MapInfo TabFile. Exporting is not supported with OpenStreet Maps. NOTE! Mapinfo indoor maps use pixel coordinates instead of
real latitude and longitude values. The exported route plan must be opened as a separate layer with the same tab file
as it was exported. If the resulting files are opened on another map, the coordinates will not be correct.
2.10.3
Measurement Service Setting Profiles
User can save measurement settings for different services as profiles. Profiles can be easily assigned for different test
devices without defining device port settings. It is also possible to export and import individual service profiles. Please
see further details from the user manual.

2.10.4
Sending Measurement Files Automatically to FTP Server
A new measurement option has been added that enables the automatic measurement file sending and allows the user to
specify the FTP and network connection settings. Automatic sending at the end of the measurement can be performed
also with measurement lists. Files are sent to an FTP server after a measurement list is completed.
2.10.5
Support for BSIC in Octal and Hexadecimal Format in BTS Files
BSIC number format (Radix) can be specified by BSIC_NUMBER_FORMAT keyword in BTS files. Valid values are: "OCT",
"DEC" and "HEX", case is insensitive. If this keyword is not specified, the decimal value DEC is used by default.
Example: BSIC_NUMBER_FORMAT "Oct". BTS file format updated to version 1.13.
2.10.6
Miscellaneous
Displaying GPS quality in the device information window for GPS devices
Displaying parameter and event descriptions from file format documentation
Marker file is saved when a marker is added or moved to/from a map
16
2.11 Handler Enhancements

2.11.1
LTE to HSPA and HSPA to LTE User Plane Handover Time with Qualcomm
Defines the time from the last packet in the old cell to the first packet in the new cell. Minimum value: 0
Unit: ms. Written to Handover Information (HOI) event.
2.11.2
LTE EPS Bearer Events and Statistics with Qualcomm
New measurement events for LTE EPS bearer activation and deactivation have been added. EPS bearer type (default,
dedicated) and release cause are logged to packet bearer events.
Packet bearer allocation attempt (PBA)
Packet bearer allocation success (PBC)
Packet bearer allocation failure (PBF)
Packet bearer release (PBD)
Please see the Nemo file format version 2.16 for further information. Statistical information can be seen in the user
interface.
2.11.3
Support for Network Interface Selection with Application Tester Handler
Previously the Application Tester handler had a single <LAN> packet connection entry that used the default network
connected. This has been changed so that the packet connection list shows all available network interfaces and data
connections and associated with the selected interface.
2.11.4
Miscellaneous
New parameters added for LTE PCI mod 3 and PCI mod 6
Support for average and maximum transport block size parameters in LTE
3 Error Corrections and Version History

Please see the readme.html file for further details. By default it can be found from C:\Program Files (x86)\Anite\Nemo
Outdoor\ readme.html.
4 New Devices
For a complete list of supported devices, please see the separate document Nemo Outdoor 7.0.0.9 Compatible
Devices.pdf.
17
4.1 Handsets and USB Modems
Nokia Lumia 920 (RM-821)
Full L1/ L2/ L3 trace capabilities
Supported with Qualcomm handler
GSM 850 / 900 / 1800 / 1900
HSDPA 850 / 900 / 1900 / 2100
LTE 700 MHz/ 2100/ 2100AWS (RM-820)
LTE 800/ 900/ 1800/ 2100/ 2600 (RM-821)
GPRS Class 12 (4+1/3+2/2+3/1+4 slots), 32 - 48 kbps
EDGE Class up to 236.8 kbps
HSDPA, 42.2 Mbps; HSUPA, 5.76 Mbps
LTE, Cat3, 50 Mbps UL, 100 Mbps DL
Samsung Galaxy Rugby (SGH-I547C)
GSM/ GPRS/ EDGE 850/ 900/ 1800/ 1900
WCDMA/ HSPA+ 850/ 1900/ 2100
HSDPA 21.1Mbps (Cat 14)/HSUPA 5.76Mbps (Cat 6)
LTE 700/ 2100AWS, E-UTRA bands 4 and 17
4.2 Scanning Receivers

No new devices.
18
4.3 Nemo Outdoor 7.0.0.9 New Devices and Licenses

Product
Device
Firmware Version
License
Handler
Driver
Code
Max. # of
Verified
Devices/
CPU
Not available
Nokia Lumia
M8960A-AAAANAZM-1.0.202075
Qualcomm
via Anite
920 (RM-821)
(AAAAANAZ Dec 7 2012 10:03:50)
LTE FDD
Qualcomm
Qualcomm HS-USB Modem 9001
v2.1.0.5 (modem port driver),
Finland
Qualcomm Drivers for Windows

v1.0.15 (add/remove programs)
Not available
via Anite
Samsung Galaxy
M8960A-AAAANAZM-1.5.361201
Rugby, SGH-I547C
(AAAAANAZ Sep 26 2012 18:02:27)
Qualcomm
Qualcomm
Kies_2.3.3.12085_7_5.exe
LTE FDD
Finland
5 Qualcomm-based WCDMA and CDMA2000 Terminals and Data Cards

Nemo Outdoor is compatible with all devices labeled as CDMA by Qualcomm or QUALCOMM 3G CDMA using the
Qualcomm chipsets. However, Anite Finland Ltd cannot guarantee full functionality when a test terminal is used with
a Qualcomm-compatible handler. Video calls, for example, might not work. Please see the separate document Nemo
Outdoor 7.0.0.9 Compatible Devices.pdf. for a list of verified Qualcomm-based CDMA and WCDMA terminals.
CDMA terminals with or without RUIM card purchased from Anite Finland Ltd must be registered with a local CDMA
operator. Anite Finland Ltd does not take any responsibility if a local operator restricts the registration of test
terminal(s) supplied by Anite Finland Ltd.
6 Computer Hardware and Software Requirements
PC (Lenovo or Dell recommended) with Windows XP (32- bit) Professional, Windows 7 Professional (32/ 64bit) Windows 8 Professional (32/ 64- bit). Windows 7 Professional is highly recommended
Pentium III processor, minimum 1GHz, preferably 1.7 GHz for single mobile measurements
For multi data measurements Intel Core Duo processor T2500 2.00GHz or higher required
For voice quality measurements with up to four channels with USB sound card Intel Core Duo processor T2500
2.00GHz or higher required
For up to six channel voice quality measurements with USB sound card Intel Quad Core processor Q9100
2.26GHz or higher required
512MB RAM minimum, 1GB RAM recommended
For multi data measurements with HSPA+ devices Intel Quad Core processor Q9100 2.26GHz or higher required
100 MB of free hard disk space for installation and use; 1 GB recommended
One USB port for copy protection module
One USB port per mobile
19
Depending on the scanner used, one USB port or serial port or RJ45 or FireWire port per scanner
One serial port for each voice quality audio module or one USB port per sound card
One USB port for an external GPS receiver
Display resolution 1400 x 900 recommended
Internet Explorer for viewing the help file
7 Device Configuration and Workspace Files

Device configuration and workspace files made by Nemo Outdoor 6.4.2.09 are fully compatible with Nemo Outdoor
7.0.0.9.
8 Installation
8.1 Supported Operating Systems
Supported operating systems are Windows XP (32/ 64-bit), Windows 7 (32/ 64-bit) and Windows 8 (32/ 64-bit).
Windows 7 Professional is highly recommended.
8.2 First-time Installation
Note that for Windows XP, Windows 7 and Windows 8 the installation must be run under Administrator
account or other user account with administrative privileges.
Start Windows and insert the Nemo Outdoor CD-ROM in your CD drive (e.g., drive D). Select Start | Run in the
Windows Status bar. Type D:\Nemo Outdoor 7\Nemo Outdoor x.xx.x in the Open field (xx refers to the version
number). Run the setup.exe and click the OK button. After the installation program starts, follow the instructions on
your screen. NOTE! When the Nemo Outdoor software installation is complete, you will need to restart the computer.
With Nemo Outdoor 6.30 onwards copy protection module is not needed during installation.
8.3 Update/Upgrade
Note that for Windows XP and Windows 7 and Windows 8, the installation must be run under Administrator
account or other user account with administrative privileges. Note that if the existing Nemo Outdoor version is
6.2.1.x or older it must be uninstalled via add or remove programs before the Nemo Outdoor 7.0.0.7 installation
can be ran. During Sentinel HASP driver installation, you are prompted to restart the computer. Press Restart
later to continue with the Nemo Outdoor 7.0 installation.
Start Windows and insert the Nemo Outdoor CD-ROM in your CD drive (e.g., drive D). Select Start | Run in the
Windows Status bar. Type D:\Nemo Outdoor7\Nemo Outdoor x.xx.xx in the Open field (xx refers to the version
number). Run the setup.exe and click the OK button. After the Installation program starts, follow the instructions on
your screen. NOTE! With Nemo Outdoor 6.21 or earlier version the copy protection key must be attached to USB port
20
during the installation and uninstallation when asked. When the Nemo Outdoor software installation is complete, you
will need to restart the computer.
8.4 Uninstallation
Note that for Windows XP, Windows 7 and Windows 8 the uninstallation must be run under Administrator
account or other user account with administrative privileges.
Nemo Outdoor application must be uninstalled via Add or Remove Programs. NOTE! With Nemo Outdoor versions
5.80- 6.21 the copy protection key must be attached to USB port during the uninstallation. With Nemo Outdoor 6.3.x
onwards copy protection module is not needed during uninstallation. When the Nemo Outdoor software
uninstallation is complete, you will need to restart the computer.
8.5 HASP Dongle Runtime Drivers
Note that the Nemo Outdoor setup includes the required HASP dongle runtime driver compatible with the
application. The driver should not be updated, for example, with Windows update or using a separate driver
setup downloaded from the internet. It is recommended not to install any other applications using the HASP
dongle runtime driver as different versions can conflict. In case the HASP dongle runtime driver is updated and
it conflicts with Nemo Outdoor, an uninstallation of the current driver should be done via Uninstall or change
program. Locate the application called Sentinel HASP Run- Time and uninstall it. Re-install Nemo Outdoor
application.
21
9 Limitations with Windows 8 Operating System
Windows 8 operating system has been tested and verified with a limited number of test devices.
Device
Number of UEs/ CPU
Driver/ Notes
Huawei E392/ E398
Driver version: 23.003.07.00.03
Nokia C7-00
Nokia 500
Nokia Lumia 920
Driver version : Qualcomm HS-USB Modem 9001 v2.1.0.5 (modem
(RM-821)
port driver), Qualcomm Drivers for Windows v1.0.15 (add/remove

programs)
Samsung Galaxy S
Driver version: Kies version 2.3.3.12085_7, driver version 1.5.18.0
III GT-i9305
Sierra 320U
Terratec DMX 6Fire sound card is not compatible with Windows 8 operating system at the time of release
10 Limitations and Issues with Windows 7 Operating System

The following limitations with Windows 7 operating system have been noticed and verified by Anite Finland or
informed by the vendors:
ZTE MF820T modem with Windows 7 OS. Device is conflicting with the Sentinel HASP key driver used with
Nemo Outdoor application. After ZTE modem is installed, Sentinel HASP key cannot be detected by Nemo
Outdoor. A workaround is to change the auto tuning settings to normal immediately after the ZTE modem is
installed. Please see section 14.2.3 for further details on how to change the auto tuning mode
Devices not supporting Windows 7 operating system:

o
PCTEL LX tri- band scanning receiver
Other limitations:
o
IP packet capturing via Nemo Outdoor does not work with Windows 7 64-bit version. Packet
capturing must be done using third party application
Debug logging needs administrative privileges if User Account Control Settings (UAC) is enabled. Its
recommended to change UAC settings to Never notify. This can be done via User Account Control
Settings
If UAC is set to always notify it might cause issues with data testing. PS connection can be
established but data transfer cannot be done. Its recommended to change UAC settings to Never
notify. This can be done via User Account Control Settings
22
Figure 10. UAC settings.
11 File Format Changes

Nemo Outdoor version 7.0.0.9 supports Nemo file format version 2.16. Nemo Analyze version 6.40.1 is compatible
with Nemo file format version 2.15. The following additions have been done:
Added support for Kodiak. (CAA, CAC, CAF, CAD, VCHI, MSGA, MSGS, MSGF, #KODIAK)
Added support for Facebook testing. (DAA, DAC, DAF, DAD, DREC, DCOMP, DRATE, DCONTENT)
Added support for EPS bearer allocation with LTE. (PBA, PBF, PBC, PBD)
Added support for average and maximum transport block size with LTE. (PLAID, PLAIU)
Added support for WLAN 2.4, 3.6, 4.9, and 5.0 GHz band information and WPA2 security modes.
Added support for audio signal detection during audio quality testing. (AQRX)
Added support for cdmaOne, CDMA 1x, and EVDO band and system lock. (LOCK)
Added support for scanning results per LTE physical resource block with Nemo FSR1 scanner. (PRBSCAN)
Added support for condition number, cqi, and throughput scanning results with PCTEL scanner. (PRBSCAN)
Added support for RSSI per antenna port scanning results. (OFDMSCAN)
Added support for MIMO scanning option. (SCANCONFIG)
Added support for handover user plane interruption time for LTE to HSDPA handover. (HOI)
Renamed HSDPA UE category to HSDPA used UE category. (PCHI)
Renamed 2x2 and 2x4 MIMO rank estimation parameters to 2x2 and 2x4 MIMO rank estimation/PRB. (PRBSCAN)
Renamed 2x2 and 2x4 MIMO condition number parameters to 2x2 and 2x4 MIMO condition number/PRB.
(PRBSCAN)
Fixed a problem that caused the test system failure value to be missing from the data disconnect and connection
failure status parameters. (DAF, DAD)
23
12 Known Issues
12.1 General & User Interface
Note that if there is a system that measures acceleration in the laptop and which causes the hard disk to stop
when jolted, it should be turned off. Otherwise there may be breaks in the measurement files. With voice
quality testing this can be seen with missing MOS scores, and with other test devices with gaps in the
measurement results.
Figure 11. Lenovo active protection system properties.
Download stops responding. Applies to Windows XP, Windows Vista and Windows 7 operating systems. When
you try to download a file, the download stops responding and then times out. The problem occurs when you use
a USB modem that has a data transfer speed that is faster than or equal to 240 kilobits per second (Kbps). The
problem occurs because of a limitation in the current USB modem driver (Usbser.sys). The hotfix download is
available from http://support.microsoft.com/kb/925681
Please select View and request hot fix downloads and follow the instructions to download the appropriate file.
Files can be found also from the DVD supplied by Anite (Nemo Outdoor 6.0\Setup\Microsoft hot fix). Please note
that for each operating system there is a separate file available:
o
Windows 7, Windows6.1-KB925681-x86.msu
Windows Vista, Windows6.0-KB925681-x86.msu
Windows XP, WindowsXP-KB925681-x86-ENU.exe
It is highly recommended not to use the User Parameters functionality during multi device testing as the decoding
of L3/ RRC messages will cause a high CPU load. If performance problems are found, it is recommended to
remove all user parameters from the user interface.
If the message Server Busy is displayed on the screen, it is recommended that the packetmon.exe be killed
using the task manager. Packetmon.exe is used by the Microsoft Network Monitor. Microsoft Network Monitor is
needed only with the video streaming quality or IP packet capturing functionalities. If IP packet capturing or video
streaming quality measurements are not required its recommended to not install Microsoft Network Monitor.
24
12.2 UEs
12.2.1
Altair-based UEs
Harris MBC-100: UE frequently has gaps in the trace messages during idle mode even power saving is
disabled. Issue is seen with the firmware ALT3100_04_00_02_00_32_TF. Issue has been reported to chipset
vendor
NSN USB-lte 7210:

o
NSN connection manager application must be closed when the UE is used with Nemo Outdoor. When
the UE is connected to a USB port, the connection manager is automatically launched. This can be
avoided by changing the file name. Browse to "C:\Program Files\NSN LTE Connection Manager and
rename the nsnltecm.exe to nsnltecm.exe_"
Power saving for UE should be disabled using the ADCC application provided by Altair with UEs having
firmware version ALT3100_04_00_02_00_23_TF. UEs with the firmware ALT3100_04_00_02_00_32_TF
or later power saving can be disabled by sending the following AT command to UE:
AT%SETCFG="PW_IDLE","NONE"
This can be done e.g. using Nemo Outdoor application via measurement properties of the UE.
The modem gets extremely hot during measurements. When the UE is overheated, trace messages are
not reported but the data transfer continues normally.
UE frequently has gaps in the trace messages that occur about every 10s and last for 800ms.
To avoid performance issues with the modem, the following modification is recommended. By this
modification the Altair LogCreator standalone functionality is disabled. Browse to folder C:\Program
Files\NSN LTE Connection Manager\Tools\ Internals\LogCreator\ and open file RunLogCreator.bat with
Notepad. Modify the following string:
Original:
LogCreator.exe -SA -FN:"50" -E -Y4:"LOG_SOCK_IF" -D4:".\LoggerDB\LTELogDB.txt" D1:".\LoggerDB\PhyFWLogDB.txt" -Q:"50000"
Modified:
LogCreator.exe -E -Y4:"LOG_SOCK_IF" -D4:".\LoggerDB\LTELogDB.txt" D1:".\LoggerDB\PhyFWLogDB.txt" -Q:"50000"
12.2.2
Cassidian Handsets
MER value is not reported by the terminal
The terminal does not answer all incoming calls when call modes are semi duplex or duplex. Auto-answer can
be enabled in the following ways with THR880i and THR880.
o
THR880/ THR9i:
Plug in a headset (Nokia Headset Type HDC-9)
Settings / Enhancement Settings / Headset / Automatic Answer --> On
25
Settings / Profiles / Headset / Personalize / Incoming Call Alert: this must not be "Off".
Settings / Profiles / Headset / Activate
Reboot the phone.
THR880i: Before the terminal can be used with Nemo Outdoor, the field test mode of the terminal must
be activated by the Cassidian TETRA Prorgramming Tool. Tool is available only from Cassidian.
For THR880 the procedure is identical, except that there is a slightly different menu structure for the
steps. Instead of Settings | Profiles | Headset, the correct path is Profiles | Headset.
12.2.3
Datang/Leadcore Handsets
Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the Datang DTM8129 and Leadcore
LC 8130E handsets.
12.2.4
Motorola Handsets
Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the Motorola V9 handsets.
Motorola iDEN i886:

o
Handovers are not reported during packet session
CREL has incorrect old cell information (same as the new cell)
CELLMEAS writes the "Number of cells" to n-1, even though there are n cells reported. This causes
Outdoor not to show results for one reported cell.
12.2.5
Nokia Handsets
Nokia general issues:
o
Nokia connectivity cable driver with the Windows Vista operating system has been found to cause a
problem when establishing PDP context activation and also instabilities with test terminals.
Usage of WCDMA RLC messages will cause phone instability during high-speed PS data activity. This is a
performance restriction. By default, RLC messages are not enabled with Nemo Outdoor.
Terminals do not update the L1 counters (first 2 octets) in uplink SACCH PDUs that are reported to Nemo
Outdoor. These two octets always have value 0x00 0x00. This problem has been reported to Nokia.
Nokia 500:
o
Video calls are not supported by the handset
Charging problem: During measurements after battery is fully charged, charging stops and does not start
again. In this case it is possible that the battery runs out during a long test.
USSD testing is not supported
With voice quality tests handset must be charged with an AC/DC 110/ 220V charger
Nokia E7-00:
o
26
Concatenated SMS testing is not supported. Max. 160 charaters are supported.
Windows XP fix KB943198 (http://support.microsoft.com/kb/943198) is needed when using HSDPA

category 6 or higher data transfer speeds.
When the UE is locked to a WCDMA carrier, it only updates the intra-freq cell list and configured triggers
from SIB11 / SIB12 messages, and ignores the "measurement control" RRC messages updating intra-freq
measurement configuration.
During measurements, the battery might run out because the terminal can be charged only via a USB
charger. It is highly recommended to use separate charger during measurement.
During voice quality testing if separate charger cable is disconnected from terminal it can decrease MOS
score. It is recommend to unplug the charger after measurement is stopped.
To further increase stability, it is recommended to do the following from the UI:
Set Theme effects to OFF
Set Animated background to OFF
Set Call image to none
Set Screen saver to none
Delete additional home screens
Set widgets to offline mode
Set WLAN scanning to OFF
Set sensors to OFF
Nokia C7-00:
o
With multiRAB testing UE is crashing due to limited power.
Concatenated SMS testing is not supported. Max. 160 charaters are supported.

category 6 or higher data transfer speeds.
27
Set sensors to OFF
Nokia C5-00/ C5-00.2:

o

category 6 or higher data transfer speeds
measurement configuration
Nokia C5-03 (RM-697), C5-03 LAT (RM-719) and C5-04AWS (RM-720):

o
With Nokia C5-03 handsets, the screen of the handset should not be activated during voice quality calls.
Activating the screen causes interference to audio and decreases MOS scores.

category 6 or higher data transfer speeds
Video calls are not supported at the moment. This is a limitation of the test terminal.
28
Set sensors to OFF
Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the following Nokia handsets:
6720, 612x, N95, N80, N85, N96 and N97
Modems
Nokia 21M-02:
o
NDIS interface isn't working with Win7 operating system, dial-up connection must be used. NDIS works
with Windows XP
SMS testing is not currently supported
MultiRAB not supported
The following parameters are not supported: GSM RXQ sub/ full, FER, C/I, WCDMA RACH parameters,
HS-SCCH usage, MAC-hs block rate and number of Ack/ Nack messages
12.2.6
Samsung Chipset-based UEs

Samsung Droid Charge (SCH-i510):
o
If USB disconnects, the handler must be stopped before enabling the USB Tethering from the phone
again
MMS testing not supported
Only LTE system supported with Nemo Outdoor at the moment
CS voice calls not enabled as UE is supported with LTE system only at the moment
LTE link adaptation parameter statistics are reported only for one modulation / PRB allocation per
sample duration
The following parameters are not available: MAC Downlink/ Uplink Throughput, MAC Downlink/ Uplink
Block Rate, MAC Downlink/ Uplink Residual BLER, PDSCH Block Rate and Timing Advance
12.2.7
Qualcomm GSM/WCDMA-based UEs
General Issues:
USSD testing not supported with Huawei and Samsung UEs
29
Qualcomm-based WCDMA terminals do not report the L3 CHANNEL REQUEST and L3 MEASUREMENT
REPORT messages. RRC CONNECTION REQUEST message is missing occasionally. Extended channel type is
reported only in circuit switched mode. For example, PDTCH channel is not reported.
With HSPA+ USB modems it is recommended to use, if applicable, the original USB extension cable that
comes with the device to achieve higher data throughput. It has been noted that when a broadband device is
connected directly to the USB port of the computer, interference might lower data throughputs in some
cases
Some MDM 8200 based devices reports incorrect WCDMA RLC throughput for uplink direction. Issue is not
seen with all vendors.
12.2.7.1 Bandrich Modems
Bandrich Bandluxe C320:

o
Cell change during PS data transfer from GSM to UMTS can occasionally cause device reset. After this,
the device still reports GSM cell information with a constant RX level value despite the serving system
actually being UMTS. The measurement must be stopped and restarted.
12.2.7.2 Blackberry Handsets
Blackberry Torch 9810 (RDM71UW):

o
UE is not very stable
USSD testing not supported
Video call/ voice quality testing not supported
MultiRAB testing not supported. If CS is ended before data transfer ends, data transfer will end with
"timeout" immediately after the call is ended
Forcing functions are not supported
Auto answering does not function with application tester handler
GSM: RXQ and FER not available
12.2.7.3 Huawei Modems
Applies to all 3G and 4G Huawei USB modems. Huawei connection manager starts up every time when device
is plugged in. As a work around connection manager .EXE file can be renamed. It still gives some reinstall
warning when device is plugged in but this can be ignored.
Applies to all 3G and 4G Huawei USB modems . NOTE! Nemo Outdoor 6.31 enables automatic DHCP with
Qualcomm-based devices using NDIS interface. The following procedure is required only with Nemo Outdoor
version 6.30 or older. Before measurements can be done with Nemo Outdoor application, the Internet
protocol properties must be manually changed to automatic mode. This must be done always after modem is
disconnected/reconnected. Its required also if the device stops responding during measurement: Windows
XP: Go to Start | Control Panel | Network Connections, and right-click on Huawei Broadband Connection, and
30
select Properties. In the Local Area Connection Properties dialog, select Internet Protocol (TCP/IP) and click
on Properties. Select Obtain an IP address automatically. Select also Obtain DNS server address
automatically
Windows 7: Go to Start | Control Panel | Network and Internet | Network and Sharing Center. Select Huawei
Broadband Connection in the View your active networks list. In the Local Area Connection Status dialog,
select Properties. In the Local Area Connection Properties dialog that opens, select the Networking tab, and
Internet Protocol Version 4 (TCP/IPv4) in the This connection uses the following items view. Click on
Properties. Select Obtain an IP address automatically. Select also Obtain DNS server address automatically
Figure 12. TCP/ IP properties.
Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the following Huawei USB
modems: E270, E220, E1820, E169, E180, E367 and E372.
12.2.7.4 LG Terminals
Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the following LG handsets:
KF700 and P500.
12.2.7.5 Novatel Modems
Novatel Ovation MC545 USB modem:

o
Novatel connection manager application must be opened when device is connected to usb port of
computer. NOTE! Before starting Nemo Outdoor application connection manager application must be
closed. Otherwise device cannot be started.
Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the following Novatel USB
modems: MC996D, MC998D, 930D and 990D
12.2.7.6 Option Modems
Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the Option USB modems.
31
12.2.7.7 Samsung Handsets
Samsung Galaxy Ace:

o
Video calls are not supported
No indication of incoming SMS message
MMS testing is not supported
Multi RAB works only if PS connection is established after voice call connection
Device is shutting down when system lock is used
PDP context activations and deactivations with multiple Samsung/Qualcomm terminals occasionally
cause instability problems with dial-up connections. Avoiding these commands when using script files is
recommended.
International numbers starting with + do not work with Samsung terminals. It is advised to use 00 instead
of +.
Samsung Omnia 7/ Focus/ Galaxy Ace:

o
Multi RAB works only if PS connection is established before voice call connection
Device is rebooting when system lock is used
PDP context activations and deactivations with multiple Samsung/Qualcomm terminals occasionally
cause instability problems with dial-up connections. Avoiding these commands when using script files is
recommended.
International numbers starting with + do not work with Samsung terminals. It is advised to use 00 instead
of +.
Samsung SGH-A847:
o
USB mode must be set to "Samsung PC Studio" to have the ports available. (Can be set permanently from
Menu -> Settings -> Connectivity -> Select USB Mode -> Samsung PC Studio)
12.2.7.8 Sierra Wireless Modems
Sierra Wireless 312U/ 319U:

o
Occasionally the network adapter interface (NDIS) disappears and device cannot perform PS data
connection. Workaround is to use the modem with microSD card or by disabling microSD card from the
device. By default Sierra Wireless modems do not include microSD cards. The microSD can be
permanently disabled with either AT commands or via a command line utility. The command line utility
ItmTk.exe can be downloaded from the Nemo User Club under Drivers for Test Devices folder. For AT
commands use e.g. Hyperterminal.
AT!ENTERCND=A710
AT!CUSTOM=USBMSENABLE,x 0=disable 1=enable
32
Device is unstable with Win 7 operating system. Issue is seen especially with Lenovo computers. Issue is
seen with failed PDP context activations and it also causes Windows file corruption on all processes
under Windows 7 operating system. Measurement log file(s) might be empty or incomplete missing
footer information. This issue has been reported to vendor. It is recommended to use Windows XP SP3
operating system. Multi measurements with 319U are not supported at the moment with Lenovo
computers.
No indication of incoming MMS message
Sierra Wireless 312U/320U:

o
If Lenovo W510 or other computer with USB 3.0 ports is used with Sierra Wireless USB modems, the
computer crashes immediately after the second USB modem is connected to the USB 3.0 port. Problem is
experienced with all 3xx- series USB modems provided by Sierra Wireless.
The Watcher application must normally be running simultaneously with Nemo Outdoor in the
background if default settings of the application are used. However it is recommended to change the
default settings of the Watcher application to avoid any issues during measurements. If the user wants to
close the Watcher application but still wants to be able to conduct measurements with Nemo Outdoor,
the following settings from the Watcher application must be selected. NOTE! The option names seen in
the Watcher application depend on the application version. If multiple modems are used
simultaneously on the same computer, these settings must always be changed!
Figure 13. Watcher application.
Watcher autolaunch must be disabled. Select No
On exit, select Do nothing
Check for updates, select Never
MCC and MNC values reported by the device are occasionally incorrect.
Instabilities noticed with the GSM system; e.g., data connection fails more often in GSM.
It has been discovered that cell reselection from 2G to 3G does not necessary occur even when 3G
coverage is very good.
With multi-device configuration when Nemo multi (USB hub) is disconnected and connected again,
all devices cannot necessarily be recognized. Each device must be separately unplugged and plugged
33
again to the Nemo multi hub to get them to work. It is recommended to add each device separately
to multi configuration each time.
Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the following Sierra
Wireless USB modems: Aircard 885, 306, 307, 308, 309, 310U, Siptune 215.
12.2.7.9 Sony Ericsson Handsets
Sony Ericsson Xperia Arc S (LT-18i):

o
Phone is charged via a USB data cable and charging causes interference to audio when the serving
system is GSM. Interference is cyclic and it affects the uplink MOS score with Terratec sound card.
With a fully loaded battery, the UL MOS score decreases dramatically after a 30-minute phone call.
This lasts about 30 minutes. It is highly recommended that if used in voice quality testing, the
handset is used only for observing downlink MOS scores and phone calls are made between the
handset and a fixed line with Nemo Server. In mobile-to-mobile testing, the issue is also seen in
GSM. NOTE! The issue is not seen while the serving system is WCDMA
Multi RAB works only in this order: Voice call -> PDP context activation. If PDP context activation is
made before voice call, the test fails
When band lock is used, the phone reboots itself. Band lock is still functioning correctly
Driver supports Windows 7 32- bit version
12.2.7.10 ZTE Modems
ZTE MF668A modem:

o
MO voice call works when Trace option is selected from the device advanced properties. NOTE!
MTC calls are not supported
MultiRAB testing can be done only if packet connection is activated before a CS call
No indication of incoming MMS message with application tester handler
ZTE MF683 modem:

o
MO voice call works when Trace option is selected from the device advanced properties. NOTE!
MTC calls are not supported
MultiRAB testing is not supported
Device will restart and become unresponsive during the band lock command for a while, but will
recover soon
12.2.8
Qualcomm (MDM9200/ 9600)-based UEs
General Issues:
Listed cells are not reported in idle mode
RRC CONNECTION REQUEST message is missing occasionally
34
Requested throughput is not available
Occasionally WCDMA monitored set are shown is active set. Issue is seen with 92xx/ 96xx chipsets
Attach/detach commands should be avoided with LTE modems. Using these commands causes instabilities in
the UEs. UEs can also reset itself. Issue is fixed to Nemo Outdoor version 6.4.1.8 but if the issue is still
experienced, the following instructions should be followed. It is recommended to choose from User
Interface Properties -> Measurement -> Force detach when going to idle mode -> No. This will prevent the UE
from detaching. If attach/ detach commands are needed frequently, for example, with script files, it is
recommended that radio off/radio on commands are used instead of attach/detach.
Figure 14. User Interface properties.
MultiRAB testing. When a voice call is terminated, the PS data connection might be released with UEs using
the Trace interface call method to make voice calls. In such a case it is recommended to use Trace
interface 2 call method.
12.2.8.1 Apple Handsets
IPhone5:
o
Handset can be used with Application Tester Handler for data testing only. Voice calls cannot be
done via Nemo Outdoor user interface or logged
FTP data transfers must be done on passive mode
12.2.8.2 Huawei LTE Modems
Huawei E392/ E398 modem:

o
Huawei connection manager starts up every time when device is plugged in. As a work around
connection manager .EXE file can be renamed. It still gives some reinstall warning when device is
plugged in but this can be ignored.
Huawei E398 modem. NOTE! Nemo Outdoor 6.31 enables automatic DHCP with Qualcomm-based
devices using NDIS interface. The following procedure is required only with Nemo Outdoor version
6.30 or older.
35
Before measurements can be done with Nemo Outdoor application, the Internet
protocol properties must be manually changed to automatic mode. This must be done
always after modem is disconnected/reconnected. Its required also if the device
stops responding during measurement: Windows XP: Go to Start | Control Panel |
Network Connections, and right-click on Huawei Broadband Connection, and select
Properties. In the Local Area Connection Properties dialog, select Internet Protocol
(TCP/IP) and click on Properties. Select Obtain an IP address automatically. Select also
Obtain DNS server address automatically
Windows 7: Go to Start | Control Panel | Network and Internet | Network and Sharing
Center. Select Huawei Broadband Connection in the View your active networks list. In
the Local Area Connection Status dialog, select Properties. In the Local Area
Connection Properties dialog that opens, select the Networking tab, and Internet
Protocol Version 4 (TCP/IPv4) in the This connection uses the following items view.
Click on Properties. Select Obtain an IP address automatically. Select also Obtain DNS
server address automatically.
Figure 15. TCP/ IP properties.

o
No indication of incoming MMS message with application tester handler
PDP context activations and deactivations with multiple Huawei USB modems occasionally cause
instability problems with dial-up connections. Avoiding these commands when using script files is
recommended.
Huawei E392: LTE RSRQ listed not available
36
12.2.8.3 LG LTE Handsets
LG P930
o
The network adapter interface is not supported completely. The device can be used if the USB
tethering is enabled through the phone menu, and PS connection setting (in Nemo Outdoor) is set to
either dial-up or automatic
If the USB connection is disconnected (i.e. device unplugged), the USB tethering must be re-enabled
on the phone in order to use the data connection
When using the device in LTE, user must not issue manual packet session commands, instead, if the
connection needs to be torn down, user should use Radio On/Off commands
With voice calls user must issue an "ATS0=1" AT command to enable the incoming calls. This must be
done every time the phone is restarted.
No indication of incoming SMS
MMS cannot be sent/ received when packet session is activated already
12.2.8.4 Nokia Handsets
Nokia Lumia 920 (RM-821)

o
No indication of incoming MMS
Battery of the handset is not fully charged via USB data cable and can run out with long test periods.
If the battery is fully charged it will last about 6 hours and after that, the handset goes to battery
saving mode. Handset goes to Terminal radio off" state for a while and then recovers back to
"Terminal Radio On" state. This goes back and forth for the rest of the measurement.
Occasionally handler fails to start with the handset. In such an occasion, it is recommended to
reboot the handset.
Channel lock works partially. In case channel is not available then device uses available channel and
stays in service.
Occasionally during FTP data testing data transfer are start failing. Measurement must be stopped
and UE must be rebooted
Settings -> Mobile network -> Data connection has to be turned off to prevent mobile from making
unnecessary packet session activations automatically.
iPerf testing works only with TCP DL
12.2.8.5 Pantech LTE Modems
Pantech UML290 USB modem

o
NDIS interface can be used to make PS connection only while device is camping on LTE. NDIS
interface cannot be used with 2G or 3G connections. Instead of NDIS interface the dial up
connection should be used.
37
12.2.8.6 Samsung LTE Handsets
Samsung Galaxy S III (GT-i9305, EU)/ Samsung Galaxy S Note II (GT-N7105):

o
Occasionally UE reports GSM Cell ID incorrectly
If the UE is used with Nemo Handy prior to Nemo Outdoor, the UE must be power cycled
When the UE is used with Nemo Outdoor, other UEs cannot be used simultaneously in data testing if
the NDIS interface is used to activate PS data connection. For example, simultaneous data testing
with Huawei LTE modem and Samsung Galaxy S III handset is not possible. It should be noted that
the issue does not limit using multiple Galaxy S III UEs for simultaneous data testing or together with
non-NDIS UEs, such as, Nokia test terminals.
To be able to make voice calls the Trace interface 2 call method must be selected from Nemo
Outdoor user interface via advanced properties.
Manufacturer information cannot be read from the UE
Automatic answering to incoming calls can be done only when a headset is connected to the UE
Use the original headset included in the sales package. Connect the headset to the phone and from
the phone menu select: Settings -> Call Answering/ Ending-> Press arrow < on the left upper
corner to go back to previous menu. Select Settings -> Accessibility -> Call Settings -> Accessory
Settings For Call -> Automatic Answering. Automatic answering will operate only with the headset
connected.
Auto detection should not be used to add the device. Add the device manually. See the dial-up guide
for further instructions.
SMS/ MMS message testing not supported at the moment
Voice quality testing is supported with Nemo Invex platform
Call back request with Nemo Server cannot be used with UE
Radio On/ Off commands are not supported
UE is always online. This means that attach/ detach and PDP context activation/ deactivation
commands cannot be used via Nemo Outdoor. Access point name (APN) is recommended to be set
to the phone manually. The phone can choose an incorrect APN by itself (incorrect APN is sent in the
38
PDN Connectivity Request message). This can cause the packet session to fail (PDN Connectivity
Reject) message is recorded with Unknown or missing APN.
o
If data testing is done manually without script files, recording must be started before data protocols
can be accessed via Nemo Outdoor. Without recording, the data protocol options in the UI are not
available.
If data throughputs in LTE are lower than expected, it is recommended to adjust the buffer size via
Nemo Outdoor user interface, for example, to value 1024. It should be noted that buffer size must
be adjusted separately for each protocol (e.g. for FTP and HTTP).
Settings. The following settings should be activated from the phone:

Data testing:
Settings -> More settings -> Mobile networks -> Mobile data enabled-> Enable
Settings -> More settings -> Mobile networks -> Network Mode -> AUTO
With GT-N7105 select Settings -> More settings -> Mobile networks -> Network
Mode -> LTE/GSM/WCDMA (Auto)
Incorrect WCDMA RLC throughputs for uplink direction are reported
Samsung Galaxy S III (SGH-i747)/ Samsung Galaxy Rugby (SGH-I547C):

o
If the UE is used with Nemo Handy prior to Nemo Outdoor, the UE must be power cycled.
To be able to make voice calls the Trace interface 2 call method must be selected from Nemo Outdoor
user interface via advanced properties.
39
System lock not supported. UE must be locked to certain band
Incorrect WCDMA RLC throughput for uplink direction are reported
Samsung Galaxy S III (SGH-T999):

o
To be able to make voice calls the Trace interface call method must be selected from Nemo Outdoor
user interface via advanced properties. NOTE! When a voice call is terminated, the PS data connection is
released. MultiRAB testing is not recommended due to this reason.
System lock not supported. UE must be locked to certain band
Samsung Galaxy S III (SCH-i535, Verizon):

o
UE must be locked either to CDMA or LTE system when used with Nemo Outdoor. Multi system
measurements with single UE are not currently supported.
Band locking does not work with CDMA/EVDO
MOC voice call works only when the terminal is in CDMA/EVDO only mode. When device is in LTE,
calls do not go through.
MMS or SMS messaging not supported
Simultaneous voice calls and data connections do not work when UE is camping in CDMA and LTE
simultaneously. Simultaneous voice and data testing can be done only when UE is locked to CDMA
Do not use Tethering, it will disable modem and trace ports
EVDO TX Power is not reported
Turn off always-on packet data (Menu -> Settings -> Wireless and Network -> More Settings ->
Mobile networks -> uncheck "Use Packet Data"
Samsung Galaxy S III (SPH-L710, Sprint):

o
40
UE must be locked either to CDMA or LTE system when used with Nemo Outdoor. Multi system
measurements with single UE are not currently supported.
MOC voice call works only when the terminal is in CDMA/EVDO only mode. When device is in LTE,
calls do not go through.
Band locking does not work with CDMA/EVDO
MMS or SMS messaging not supported
Simultaneous voice calls and data connections do not work when UE is camping in CDMA and LTE
simultaneously. Simultaneous voice and data testing can be done only when UE is locked to CDMA
Packet connection occasionally fails when camping on CDMA
Do not use Tethering, it will disable modem and trace ports
Turn off always-on packet data (Menu -> Settings -> Wireless and Network -> More Settings ->
Mobile networks -> uncheck "Use Packet Data"
Sometimes the network adapter appears with a yellow exclamation mark. The device must be
reconnected to the USB
EVDO TX Power is not reported
Samsung Galaxy Rugby (SGH-I547C):

o
To be able to make voice calls the Trace interface 2 call method must be selected from Nemo Outdoor
user interface via advanced properties.
Samsung Galaxy S II Note (GT-N7105):

o
Occasionally UE reports GSM Cell ID incorrectly
When the UE is used with Nemo Outdoor, other UEs cannot be used simultaneously in data testing if
the NDIS interface is used to activate PS data connection. For example, simultaneous data testing
with Huawei LTE modem and Samsung Galaxy S III handset is not possible. It should be noted that
the issue does not limit using multiple Galaxy S III UEs for simultaneous data testing or together with
non-NDIS UEs, such as, Nokia test terminals.
To be able to make voice calls the Trace interface 2 call method must be selected from Nemo
Outdoor user interface via advanced properties.
41
Manufacturer information cannot be read from the UE.
Automatic answering to incoming calls can be done only when a headset is connected to the UE.
Use the original headset included in the sales package. Connect the headset to the phone and from
the phone menu select: Settings -> Call Answering/ Ending-> Press arrow < on the left upper
corner to go back to previous menu. Select Settings -> Accessibility -> Call Settings -> Accessory
Settings For Call -> Automatic Answering. Automatic answering will operate only with the headset
connected.
Auto detection should not be used to add the device. Add the device manually. See the dial-up guide
for further instructions.
SMS/ MMS message testing not supported at the moment
Voice quality testing is not supported with sound cards
Radio On/ Off commands are not supported
UE is always online. This means that attach/ detach and PDP context activation/ deactivation
commands cannot be used via Nemo Outdoor.
If data testing is done manually without script files, recording must be started before data protocols
can be accessed via Nemo Outdoor. Without recording, the data protocol options in the UI are not
available.
If data throughputs in LTE are lower than expected, it is recommended to adjust the buffer size via
Nemo Outdoor user interface, for example, to value 1024. It should be noted that buffer size must
be adjusted separately for each protocol (e.g. for FTP and HTTP).
Settings. The following settings should be activated from the phone:
42
Data testing:
Settings -> More settings -> Mobile networks -> Mobile data enabled-> Enable
Settings -> More settings -> Mobile networks -> Network Mode -> AUTO
Samsung Galaxy S II LTE (GT-I9210):

o
Autodetecting the device does not always choose the correct trace port. There are two ports with
same name and sometimes the correct port is chosen and sometimes not. Its recommended to add
device manually to Nemo Outdoor
Samsung Galaxy S II Skyrocket i727:

o
To enable auto-answering functionality, user must first initialize the terminal for auto-answer with
an AT-command "ATS0=1". This must be done only once when the phone is used for the first time.
12.2.8.7 Sierra Wireless LTE Modems
Sierra Wireless 330U USB modem:

o
In GSM UE is unstable
PDP context activations and deactivations cause instability problems. Avoiding these commands
when using script files is recommended
MMS message testing not supported
Sierra Wireless 313U/ 320U/ 330U:

o
With LTE max. DL data throughput is limited to ~50Mbps with 320U
Occasionally the network adapter interface (NDIS) disappears and device cannot perform PS data
connection. Workaround is to use the modem with microSD card or by disabling microSD card from
the device. By default Sierra Wireless modems do not include microSD cards. The microSD can be
permanently disabled with either AT commands or via a command line utility. The command line
utility ItmTk.exe can be downloaded from the Nemo User Club under Drivers for Test Devices
folder. For AT commands use e.g. Hyperterminal.
AT!ENTERCND=A710
AT!CUSTOM=USBMSENABLE,x 0=disable 1=enable
12.2.8.8 ZTE LTE Modems
ZTE MF820T/ MF820D/ MF880:

o
PDP context activations and deactivations cause instability problems. Avoiding these commands
when using script files is recommended
ZTE MF880:
o
UE does not work in GSM (FW: M9200B-SCAQTBZD-4.0.32 (SCAQTBZM Nov 15 2011 18:58:05)
43
o
12.2.9
TX Power PUCCH/ PUSCH not available
LG LTE Modems (LG1000/ LG 2000)

Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the following LG LTE USB
modems: LG L1000, LG 2000, LG G7, LG G13, LG G17, LG VL600.
12.2.10 Qualcomm 3GPP2-based UEs
If auto detection is used to add device to Nemo Outdoor the CS dial up connection should be manually
changed to not used. This can be done via device properties window.
Currently MMS send functionality is supported with CDMA terminals. Received MMS messages are not
detected.
FER F-SCH (supplemental channel) is not working correctly
12.2.10.1 LG Handsets
LG KX206:
o
Incoming calls are not automatically answered due to a limitation of the terminal.
12.2.10.2 Pantech Modems
Pantech UM175:
o
<automatic> for PS dial-up connection does not work with the device. A workaround is to create a
dial-up connection manually.
12.3 Scanner Receivers

12.3.1
Anritsu Scanners
Please see the Nemo Outdoor 6.31 Release Notes for the known issues found with the Anritsu scanner
receivers.
12.3.2
Nemo FSR1 Scanner

o
GPS antenna should always be connected to scanner receiver
GPS fix must be aqruided before starting CDMA/ EVDO scanning
GPS fix must be be aqruided once before BSIC can be decoded. After fix is aqruided GPS connection /
fix is not needed anymore with GSM measurements
Please read the separate Nemo FSR1 3.0/ 3.1 release note for further information
44
12.3.3
PCTEL Scanners
PCTEL EX scanner:
o
Stopping measurement fails occasionally with EX scanners. Due to this reason starting new
measurement is failing. Workaround is to power cycle scanner receiver
Pilot scanning works only in Top-N mode. This is a device feature
Timeslot scanning is not supported
The channel parameter is n/a when an empty PILOTSCAN measurement event is written
PCTEL EX Wimax scanner:

o
For Top-N preamble scanning to be successful, the scanning receiver must acquire a GPS fix at least
30 seconds before starting the Nemo Outdoor application in online mode. If the existing
configuration file includes a PCTEL WiMAX scanner, it is recommended to open the configuration file
in offline mode. If the scanner does not send any results after 30 seconds, it is recommended to
send a reset command to the scanner via the user interface.
PCTEL EX GSM/TD-SCDMA scanner:

o
PCTEL LX scanner:
o
Secondary frequency scanning is not supported by the scanning receiver
With the GSM/WCDMA scanner, the Internal GPS receiver should be activated only in UMTS mode
PCTEL MX scanner:
o
The scanner must not be added to Nemo Outdoor before the scanner LED turns green. During the
scanner start-up process the LED is amber. If the scanner is added to Nemo Outdoor in the middle of
the start-up process, it can cause Nemo Outdoor to crash.
When MX scanner receiver is used with a Nemo Invex UIC module, other devices must not be
connected to the same UIC module.
The power switch must remain in the Drive Test position at all times. The Indoor Test Mode is not
available at this time.
The GPS antenna needs to be connected before power up.
Occasionally scanner device does not accept scanning configuration sent by Nemo Outdoor
application even though status is scanning. Device is not reporting any scanning results. In such
situations it is adviced to open device measurement properties again and press ok. Issue have been
reported to the vendor.
Nemo Outdoor application does not detect if USB data cable is disconnected during the
measurement. Device is not responding message is not shown.
Detecting and connecting the PcTel MX scanning receiver for the first time takes a much longer time.
Time depends on the number of available COM ports installed in the computer. With Win XP
computers the required time is longer than with Win7 operating system. The required time is ~2min10 min. It is recommend to save the hardware configuration file with Nemo Outdoor after the first
45
connection to the scanner receiver. Starting device with an existing hardware configuration file is
much faster.
12.3.4
Rohde & Schwarz Scanners

TSML & TSMQ Windows 7 driver version 12.0.0.0. Please read the TSMx-NewFireWireDriver.pdf document
for further information about the installation process.
After starting the measurement it can take up to 10- 20 seconds before the scanner receiver starts reporting
the scanning results
The TSML and TSMQ devices might not work correctly when connected directly to the Firewire port of the
computer. If connection problems are experienced, it is recommended to use a PCMCIA express adapter card
Firewire Express card TSPC-FW1 (415010-00).Problems with some Dell Notebooks. Possible problems are
caused by some of the drivers installed on Dell systems by default. The problems can be solved out by
removing the original system and re-installing the operating system only with the components necessary to
operate with the scanners.
In addition, it has been recognized that the systems which only provide 1024 bytes Host rec. buffer size
(instead of 2048 bytes) can cause issues with the scanning receivers. This can be checked from the Rohde &
Schwarz TSMx Device driver properties tab. Dell Vostro 1014 model has been found to be incompatible with
the R&S TSML-GW scanner. GSM scanning cannot be performed.
Figure 16. TSMQ driver properties.
Rohde & Schwarz TSMQ:

o
EVDO measurements can only be performed properly when a CDMA2000 channel is measured as
well. In this way, the time relationship between the different PN offsets is resolved.
Rohde & Schwarz TSML-C:

o
EVDO measurements can only be performed properly when a CDMA2000 channel is measured as
well. In this way, the time relationship between the different PN offsets is resolved.
Simultaneous pilot scanning and spectrum scanning are not supported.
46
Rohde & Schwarz TSML-G:

o
Simultaneous frequency scanning and spectrum scanning are not supported.
Rohde & Schwarz TSML-W:

o
To be able to measure LTE Time Offset GPS antenna must be connected to receiver
Simultaneous pilot scanning and spectrum scanning are not supported
In case of abnormal behavior, it is recommended to restart Nemo Outdoor. It is also recommended

to power cycle the scanning receiver.
12.4 Nemo Invex

12.4.1
General
When shutting down the system, it is recommended to close Nemo Outdoor before turning power off from
the Nemo Invex chassis
It is highly recommended to set the event buffer size from 100000 to 50000 when Nemo Outdoor application
is used with Nemo Invex system. This can be done via user interface properties
12.4.2
Nemo Invex USB Isolation Module

Sierra Wireless 312/ 319 USB modem:
o
After power cycling the USB modem, there have been rare occasions when the USB modem is
recognized as a hard disk drive instead of USB modem. Temporary workaround is to eject the device
via system tray. Requires remote desktop connection to UIC . Issue appears also when the USB
modem is connected directly to the USB port of the UIC module
Device is unstable with Win 7 operating system. Issue appears with failed PDP context activations
and it also causes Windows file corruption on all processes under Windows 7 operating system. This
issue has been reported to vendor.
12.4.3
Nemo Invex UIC Module

Nemo Invex UIC module includes preinstalled Huawei E392/ E398 driver. When plugging in Huawei E392/
E398, the OS might ask the user to install a new driver. User should choose No to not install a new driver in
such occasion. In case a new driver is installed, the user must do the following:
o
Huawei connection manager starts up every time when device is plugged in. As a work around
connection manager .EXE file can be renamed. It still gives some reinstall warning when device is
plugged in but this can be ignored.
When the MX scanner is used with a Nemo Invex UIC module, other devices must not be connected to
the same UIC module
47
When the MX scanner is used with a Nemo Invex UIC module, it is required to wait that the
Status/Power LED of the MX scanner receiver switches to green before adding the scanner to Nemo
Invex. If the device is added to Nemo Invex before start up is completed, it can crash Nemo Invex.
12.5 Other Devices

12.5.1
GPS receivers
In case GPS fix is lost frequently during driver test, it is advisable to turn off the car radio to see if it is
generating spurious emissions that are interfering with the GPS receiver.
12.5.2
TerraTec DMX 6Fire & Maya44 USB Sound Cards
Currently Terratec DMX 6Fire driver does not support Windows 8 operating system
The sound card should be connected to a USB 2.0 port. Connecting the device to a USB 3.0 port may
cause missing MOS scores and distortion in audio, which decreases the MOS score .
If terminals report lower than expected MOS values in Voice Quality measurements, it may result from
too high CPU usage on the computer. First of all, an Intel Core Duo processor T2500 2.00GHz or higher
is required for voice quality measurements. If you suspect that the reported MOS values are too low
and you are using multiple terminals and a scanner simultaneously, try the following. First, if you have
many applications running on the laptop, try closing the unnecessary ones. Next, disconnect the
scanner and try testing with a single terminal to see if the MOS values improve. Proceed with testing
with 1-4 terminals without using the scanner simultaneously for optimal MOS results.
If a sound card is used as a standalone hardware connected to a laptop, the test handsets must not be
placed close to the sound card. This applies especially to GSM.
Turn off all sounds from the test handsets. From Windows OS, choose system sounds scheme as No
sound.
Note that if there is a system that measures acceleration in the laptop and which causes the hard disk to
stop when jolted, it should be turned off. Otherwise there may be breaks in the measurement files.
With voice quality testing this can be seen with missing MOS scores, and with other test devices with
gaps in the measurement results.
48
Figure 17. Lenovo active protection system properties.
Voice quality measurements using Nemo Multi Lite suitcases with Nokia terminals:
o
When a Nokia terminal is placed to the holder screen facing upwards, it might cause some
interference to a sound card located at the bottom of the suitcase. This is due to the fact that the
transmitting antenna is located on the rear side of the terminal. It is recommended to place the
terminal to the holder screen facing down as seen in the picture below
With voice quality tests Nokia 500, C5 variants, and 6720 handsets must be charged with an AC/DC
110/220V charger.
Figure 18. Nokia terminal facing down.
Wi-Fi must be turned off from the laptop. In case stationary tests are performed, for example, in the
office, Wi-Fi base station must not be located close to the measurement system.
With Nokia C5-03 handsets, the screen of the handset should not be activated during voice quality calls.
Activating the screen causes interference to audio and decreases MOS scores.
Voice quality echo testing:
49
The following reference sample files provided with Nemo Outdoor setup cannot be used due to too
low speech activity ratio for echo testing: 5s_nb.wav, 5s_wb.wav, 7s_nb.wav and 7s_wb.wav
12.5.3
Beceem BCS200/BCSM 250/3300 Wimax
With some Beceem-based devices it is required to use an API version newer than the one that is by
default included in the Nemo Outdoor installation package. If a diagnostics software from Beceem
(called Kannon) or a connection manager software corresponding to the firmware of the Beceem device
is available, it is sometimes possible to use the API from one of these softwares to get the device to
work properly with Nemo Outdoor. Search for a file called libxvi010.dll in Kannon or connection
manager installation directory. Back up your existing libxvi010_524.dll in Nemo Outdoor installation
folder (C:\Program Files\Anite\Nemo Outdoor) and then overwrite it with the new version. Next, run
regsvr32 Serial_Beceem_524.dll in the Outdoor installation folder. In Nemo Outdoor select the new
device "Beceem BCS200 (524)
RSSI & CINR values are not cleared when the level goes below -120dBm for RSSI and -32dB for CINR
Ubee Interactive U1900 Wimax
Connection manager software from the operator must be used to make the PS session
activation/deactivation. (FW: 5.2.3013, DRIVER: 5.2.139.0, LIB: 5.2.36. )
12.6 Applications & Protocols
VLC media player:

o
USSD testing:
o
Retrieving proper error messages (streaming cause codes) is missing.
USSD testing is not supported with Huawei and Samsung UEs.
FTP UL data transfers:

o
Occasionally FTP UL data throughput values can exceed the maximum value supported by the
network. This is seen at the beginning of data transfers. The root cause is that the operating system
can buffer the data.
VoIP testing:
o
Other PS data connections are not allowed at the same time with the same computer. Issue has
been reported to the vendor.
Only one VoIP connection per CPU can be done at the moment. Issue reported to the vendor.
With Nemo Outdoor 6.3 the required Microsoft Network Monitor version is 3.4.
IP packet capturing does not work with Windows 7/ Windows Vista 64- bit versions at the moment. Due
to this reason, video streaming quality measurements cannot be performed with these operating
systems.
50
If IP packet capturing is not required it is highly recommended to uninstall it, as it affects to the CPU
performance.
WAP testing. The WAP protocol stack used in Nemo Outdoor supports the following contents:
o
Content Type
WMLC
WML 1.1/1.2/1.2.1 text and binary yes
WMLScript 1.1/1.2/1.2.1 text and binary yes
Character Sets
WML Char-sets
US ASCII yes
UTF-8 yes
UCS-2 yes
ISO8859-1 (Latin) yes
ISO8859-2 to 10 (other European) yes
ISO8859-13 to 15 (other European) yes
SHIFT JIS (Japanese) yes
WSP 1.0 (5 July 2001)
WTP 0.0 (10-Jul-2001)
WTLS (06-April-2001)2
WP-HTTS (29-Mar-2001)
WAP 2.0 /MMS
It has been discovered that with high data rates (HSDPA 7.2Mbps), data throughput values with Nemo
Outdoor might be lower than expected. To fix the problem, it is recommended to install Windows hot
fix which is immediately available. Please see http://support.microsoft.com/kb/925681 for further
information. A too small TCP window size also lowers the maximum data throughput. By using the
TCPOptimizer utility software, it is possible to change the TCP window size and obtain better
throughputs. A good TCP window size should be 128,000 bytes. After the settings have been changed,
the computer must be rebooted to make the changes effective. The TCPOptimizer utility software can
be downloaded from the Nemo user club: (http://www.anite.com/nemo-wireless-networkmeasurement-solutions-anite.html?Itemid=59) You can also request it from Nemo Helpdesk
(Nemo.Helpdesk@Anite.com)
If data throughput problems are experienced with Windows Vista or Windows 7 operating systems and
you are using auto-tuning TCP receive window, please see article
http://blogs.msdn.com/wndp/archive/2007/07/05/receive-window-auto-tuning-on-vista.aspx or try to
set the auto-tuning level to highlyrestriced." Auto tuning can be restricted by running netsh interface
tcp set global autotuninglevel=restricted from the command prompt. We have found that the
51
restricted mode will often allow some of the benefits of auto tuning with a number of problematic
devices. Current auto tuning level can be shown with the command netsh interface tcp show global.
With MMS testing the data transfer status can occasionally show more than 100%.
Streaming (Catra). Nemo Outdoor cannot establish streaming with the Nemo Server Catra streaming
service. With Nemo Handy, streaming is working correctly with the included test files.
CDMA SMS end-to-end testing. To be able to calculate end-to-end delivery time, SMS testing must be
done using the same operator between two terminals. This is due to the fact that SMS message ID
changes from operator to operator.
MMS testing. In case of high MMS sending/receiving failures it is recommended to increase the default
time out time from 30 seconds e.g. to 60 seconds.
13 Troubleshooting Device Connectivity Issues

In general all power saving options should be disabled and high performance power settings should be used.
Battery stretch should not be used and USB port power saving option should be deselected.
Figure 19. Generic USB hub properties.
52
14 Troubleshooting Data Transfer Issues

14.1 PS Connection Works but No Data
14.1.1
UAC Settings
If UAC is set to always notify it might cause issues with data testing. PS connection can be established but
data transfer cannot be done. Its recommended to change UAC settings to Never notify. This can be done
via User Account Control Settings. If UAC settings cannot be changed its highly recommended to start Nemo
Outdoor application with administration rights by right clicking Nemo Outdoor icon and by selecting Run as
administration.
Figure 20. UAC settings.
53
14.1.2
Antivirus Filtering
Disable antivirus application and Windows firewall. If data transfer still does not work, please do the following:
Activate PS connection (activate PDP context)
Go to Network settings and choose appropriate connection assigned for device. Go to Connection properties
and check that antivirus NDIS filtering is unchecked.
Figure 21. Connections.
Figure 22. Antivirus NDIS Filter.
14.2 Low Data Throughputs

In case lower data throughputs are received with Nemo Outdoor compared to third-party applications, read this
document for troubleshooting throughput problems with various TCP based protocols.
In case low throughput values are monitored with Nemo Outdoor and also with third-party applications, the issue can
most likely be seen by observing link adaptation parameters.
rd
For example, low average CQI and high MAC-HS 3 retransmission rate indicate an area of bad coverage or high
interference. Low HS-SCCH usage rate (= high HSDPA DTX percentage ratio) points to capacity, server or transmission
problems.
In LTE networks, observe physical resource block allocation (PRB) and signal to noise ratio (SNR). PRB affects
throughput directly. Values less than maximum may indicate other users in the cell, a bottleneck in the transmission
network or not enough data to be sent (application does not need all the available bandwidth). If data throughputs in
54
LTE are lower than expected, it is recommended to adjust the buffer size via Nemo Outdoor user interface, for
example, to value 1024. It should be noted that buffer size must be adjusted separately for each protocol (e.g. for FTP
and HTTP).
Requested throughput much higher than the actual measured throughput may indicate that there are other users
sharing the radio resources of the cell or some other bottleneck in the network that prevents the mobile from getting
the maximum achievable throughput.
High PUSCH TX power values indicate a lack of uplink coverage.
When operating in the dynamic range of link adaptation, average BLER (PDSCH BLER) should be higher than 0, typically
10-20%, in order to achieve the gain of HARQ retransmission scheme
Residual BLER after all HARQ retransmissions should be 0%. Higher values indicate that the radio link is about to drop.
Observe the MAC downlink/uplink residual BLER (%) values.
Other things that could help troubleshooting:
Disable any firewall and/or antivirus software that could reduce the throughput. Some HSPA USB interfaces
may also install their own software which may affect to window size settings in registry.
Disable IP packet monitoring from the advanced properties
Figure 23. IP capture settings.
Try another FTP server for comparison.
Command prompt FTP throughput. This comparison is recommended because command prompt FTP does
not use any multithreading or other non-standard methods. For better results, keep Nemo Outdoor at the
background measuring the mobile network while making the transfers. Also try different servers.
For Nemo Outdoor 5.60 and older versions: Run a script with simultaneous FTP transfers to see if the
throughput increases. Does not work manually, script is always needed.
For Nemo Outdoor 5.70 and later versions: Use the multithread feature of the FTP protocol to test
simultaneous transfers. Works also manually.
55
For Nemo Outdoor 6.30 and later versions: Transmit/receive buffer size should not be mixed with the TCP
receive window size which is the global setting. TCP receive window size affects the TCP/ IP layer whereas
transfer buffer size affects the application layer. Transfer buffer size can be adjusted per socket. This means
that the transfer buffer size can be adjusted for each test UE separately. Transfer buffer size can be adjusted
with the FTP, SFTP, HTTP, POP3, SMTP, and IMAP protocols.
When buffer size is not checked from user interface, Nemo Outdoor checks if auto-tuning is on with Windows
7 or if there is a value in the registry with Windows XP. If auto-tuning is on, no values are set. Otherwise the
static value 64k is used. In Windows XP, if there is no value in registry, Nemo Outdoor uses the default buffer
values to receive/ transmit (256k/64k).
Normally default buffer values are acceptable. But if low data throughputs are still experienced, increasing
the receive/transmit buffer size may increase data throughput.
In uplink direction, transfer buffer size too high can be seen as high data throughput peak at the beginning of
the data session. For example, it is possible that measured data throughput peak is higher than what the
cellular system supports. In this case, decreasing the transfer buffer size in uplink direction will eliminate
high data throughput peaks.
Figure 24. Data transfer settings.
Make a comparison test between Nemo Outdoor and the connection manager used with the device. When
configuring a device with Nemo Outdoor, only the trace port should be defined. The modem port and dial-up
connection must be left blank. As ports are left blank it is not possible to perform a manual PDP context
activation or data transfer via Nemo Outdoor. However, a script file with data connection commands can be
used. Script files should include only data transfer commands, not Attach/detach or PDP context activation or
deactivation commands. Start a data transfer and observe the application data throughput value. Make the
same test again but this time make a connection using Nemo Outdoor.
56
14.2.1
All Windows Versions
How to check the TCP window size from packet logs:

Using Wireshark:
1. Check the .pcap file and look at the (non FTP-DATA) TCP traffic in the middle of the
transfer. Window size value tells the current TCP window size used.
Using Nemo Outdoor:

1.
Open a packet grid window in Nemo Outdoor.
2.
Look at the TCP traffic in the middle of an FTP transfer with PayloadLen=0:
3.
Double click the frame to get detailed frame info. Look at the Tcp tree. Window shows the current
value.
Using debug logs (for developers, help desk, etc.):

4.
Look for the GetWindowSizeFromRegistry() function.
TCP Window size set to n = Value found from registry.
TCP Window size set to default: n = Value not found from registry. Set to default.
TCP Auto-Tuning detected. Window size not set. = Windows Vista/7 is using auto-tuning TCP
window.
5.
A measurement file (.nmf) does not save window size info. Packet log and/or debug log is always
needed.
57
14.2.2
Windows XP
Check registry value of

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TcpipParameters\TcpWindowSize. Windows and Nemo
Outdoor both use it if it exists. The value can be changed manually or by using TcpOptimizer software. Increase value
the value if needed. If the registry value is missing, Nemo Outdoor will use its default window size which is 256 KB.
14.2.3
Windows Vista/Windows7
Windows Vista/7 does not use static window sizes from the registry. They rely on dynamic window size which is
handled by TCP auto tuning feature. However, if the same registry value that XP uses is set, Outdoor reads it and
adjusts the manual window size based on this value. In most cases, the registry has been edited by a third-party
software or a USB mobile interface driver/software. This registry entry can be removed.
If the TCP auto-tuning is disabled Nemo Outdoor will use its default window size 64 KB. Outdoor 5.40 and newer
checks the auto-tuning state and does not change any window sizes if auto-tuning is enabled.
How to check TCP auto-tuning state:
1.
Open command prompt by typing CMD to Search programs and files field.
2.
Type netsh interface tcp show global
3.
Receive Window Auto-Tuning Level shows the current state.
Please note that administrator rights are required to change auto-tuning settings.
58
4.
Open command prompt by typing CMD to Search programs and files field. Right-click and select
Run as administrator.
Figure 25. Run as administrator.
5.
To disable auto-tuning type netsh interface tcp set global autotuning=disabled. This limits the TCP
window size to 64KB. However, Outdoor sets its own default 256KB when auto-tuning is disabled.
6.
To increase the maximum TCP window size that auto-tuning uses, type netsh interface tcp set
global autotuning=highlyrestricted.
7.
Below are all the values of auto-tuning level with explanations:
disabled: Uses a fixed value for the TCP receive window. Limits to 64 KB (65535).
highlyrestricted: Recommended. Allows the receive window to grow beyond its default value,
very conservatively.
restricted: Recommended. Somewhat restricted growth of the TCP receive window beyond its
default value.
normal: Default value. Allows the receive window to grow to accommodate most conditions.
experimental: Allows the receive window to grow to accommodate extreme scenarios (not
recommended, it can degrade performance in common scenarios, only intended for research
purposes). It enables receive window values of over 16 MB.
Windows XP fix KB943198 (http://support.microsoft.com/kb/943198) is needed when using

HSDPA category 6 or higher data transfer speeds with Nokia test terminals
59
14.3 Issues with HTTP Browsing Testing

Selecting Automatic configuration or Proxy settings can cause problems with HTTP browsing testing, such as,
increase the page downloading time. In such a case automatic/ proxy settings should be disabled.
Figure 26. LAN settings.
60

RN Nemo Outdoor 7.0.0.9 18th April 2013

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

RN Nemo Outdoor 7.0.0.9 18th April 2013

Caricato da

Copyright:

Formati disponibili

RELEASE NOTES FOR NEMO OUTDOOR 7.0.0.

Yrttipellontie 10 | FI-90230 Oulu | Finland | tel. +358 50 395 7700 | www.anite.com/nemo

New Features ............................................................................................................................................................ 6

Support for Windows 8 Operating System ........................................................................................................ 9

Audio Quality Signal Status with Voice Quality Measurement ......................................................................... 9

Kodiak InstaPoC Push-to-Talk Calls............................................................................................................... 11

AMR Codec Mode Forcing with Qualcomm Based UEs................................................................................... 12

Automated QChat PTT Calls ............................................................................................................................ 12

Nemo FSR1 Scanner Handler Enhancements .................................................................................................. 12

LTE MIMO Measurements ...................................................................................................................... 12

R&S TSMW Scanner Handler Enhancements ................................................................................................. 14

LTE Time Offset and Delay Spread Measurements ................................................................................ 14

PcTel MX and EX Scanner Handler Enhancements.......................................................................................... 15

LTE MIMO Measurements ...................................................................................................................... 15

LTE BCCH Message Decoding ................................................................................................................. 15

LTE Carrier RSSI Results per Antenna Port ............................................................................................. 15

User Interface .................................................................................................................................................. 16

Starting and Stopping Scripts Separately per Test Device ...................................................................... 16

Exporting Route Plan to MapInfo Maps ................................................................................................. 16

Measurement Service Setting Profiles ................................................................................................... 16

Sending Measurement Files Automatically to FTP Server ...................................................................... 16

Handler Enhancements ................................................................................................................................... 17

LTE EPS Bearer Events and Statistics with Qualcomm............................................................................ 17

Error Corrections and Version History .................................................................................................................... 17

New Devices ............................................................................................................................................................ 17

Handsets and USB Modems ............................................................................................................................ 18

Scanning Receivers .......................................................................................................................................... 18

Nemo Outdoor 7.0.0.9 New Devices and Licenses ......................................................................................... 19

Yrttipellontie 10 | FI-90230 Oulu | Finland | tel. +358 50 395 7700 | www.anite.com/nemo

Qualcomm-based WCDMA and CDMA2000 Terminals and Data Cards ................................................................. 19

Computer Hardware and Software Requirements ................................................................................................. 19

Device Configuration and Workspace Files ............................................................................................................. 20

Supported Operating Systems ........................................................................................................................ 20

First-time Installation ...................................................................................................................................... 20

HASP Dongle Runtime Drivers ......................................................................................................................... 21

Limitations with Windows 8 Operating System ...................................................................................................... 22

Limitations and Issues with Windows 7 Operating System .................................................................................... 22

File Format Changes ................................................................................................................................................ 23

Known Issues ........................................................................................................................................................... 24

General & User Interface ................................................................................................................................ 24

Altair-based UEs ..................................................................................................................................... 25

Cassidian Handsets ................................................................................................................................. 25

Datang/Leadcore Handsets .................................................................................................................... 26

Motorola Handsets ................................................................................................................................. 26

Nokia Handsets ....................................................................................................................................... 26

Samsung Chipset-based UEs ................................................................................................................... 29

Qualcomm GSM/WCDMA-based UEs .................................................................................................... 29

Qualcomm (MDM9200/ 9600)-based UEs ............................................................................................. 34

LG LTE Modems (LG1000/ LG 2000) ....................................................................................................... 44

Qualcomm 3GPP2-based UEs ................................................................................................................. 44

Scanner Receivers ........................................................................................................................................... 44

Anritsu Scanners ..................................................................................................................................... 44

Nemo FSR1 Scanner................................................................................................................................ 44

PCTEL Scanners ....................................................................................................................................... 45

Rohde & Schwarz Scanners .................................................................................................................... 46

Nemo Invex ..................................................................................................................................................... 47

Nemo Invex USB Isolation Module ......................................................................................................... 47

Nemo Invex UIC Module......................................................................................................................... 47

Other Devices .................................................................................................................................................. 48

GPS receivers .......................................................................................................................................... 48

TerraTec DMX 6Fire & Maya44 USB Sound Cards .................................................................................. 48

Yrttipellontie 10 | FI-90230 Oulu | Finland | tel. +358 50 395 7700 | www.anite.com/nemo

Beceem BCS200/BCSM 250/3300 Wimax .............................................................................................. 50