This action might not be possible to undo. Are you sure you want to continue?
2 Release Note
1 About This Release
Release date: 2011-09-22
© Ascom (2011). All rights reserved.
TEMS is a trademark of Ascom. All other trademarks are the property of their respective holders.
All customers using DRT 4301A+ scanners for LTE or WiMAX measurements must upgrade to firmware version 02.03.02 or later. Customers are referred to the DRT 4301A+ Miniature Receiving System manual for installation instructions. Contact DRT support for additional information regarding upgrading to newer firmware. Also note the following restrictions on compatibility: Firmware versions 02.02.xx and earlier are not compatible with TEMS Investigation 12.1.x and later. Firmware versions 02.03.xx and later are not compatible with TEMS Investigation 12.0.x and earlier.
Bugs Corrected in TEMS Investigation 13.0.2
Sierra Wireless USB 308 Shockwave “4G” M3_0_10_13AP (in fact an HSPA+ device) did not detect in TEMS Investigation 13.0. – Bug fixed in UEDescription.xml. RSSI scanning: On selecting multiple bands and a channel range that matched channels on band A but no channels on band B, the application started scanning on band A but also issued a “fail” message for band B, preventing the user from stopping the band A scan (without deactivating the scanner altogether). When doing GSM scanning with PCTel scanner in TEMS Investigation 13.0/13.0.1, BSIC was not decoded even if BSIC option was enabled. LTE: EARFCN 3050 misrepresented by TEMS Investigation as 3049. – EARFCN calculation error fixed. LTE: Neighbor cell RSRP abnormal for Qualcomm devices in TEMS Investigation 13.0.1. – Processing of Qualcomm reports modified.
NT11-18532, 3.0, 9/15/2011
LTE: “PDSCH Resource Block” information elements not populated with Qualcomm LTE device. MME Group Id. CSFB Call Established.0. EUTRAN Reselection Time After CSFB Call. RACH Reason. LTE scanning: Band 17 channels not selectable for PCTel EX LTE scanner in TEMS Investigation.9/15/2011 . and MME Code. Preamble Step Size. LTE: EMM State not presented with Qualcomm LTE device. EUTRAN RRC Connection Release Redirected Failure. 3. LTE scanning: TEMS Investigation 13. CSFB Call Setup. NT11-18532.1. RACH Result.0. Information element: Attach Type. 2 Support added for Sierra Wireless AC319U. – Code improved to handle corrupt performance counters gracefully. Inter-RAT events: EUTRAN RRC Connection Release Redirected.1 Concurrent FTP downloads failed because of failure to close the downloaded files after the first FTP loop.1 Enhancements Enhancements in TEMS Investigation 13. LTE scanning: PCTel EX LTE scanner supporting 5 bands treated in TEMS Investigation as supporting only 4 bands. Support added for Huawei E367. EUTRAN Attach Failure. which allows a terminal connected to EUTRAN to access the CS domain via GERAN or UTRAN.1 failed to display data from certain PCIs.2 New LTE information elements dealing with the LTE RACH procedure: RACH Type. RACH Preamble Responses with PUSCH Resource. Attach events: EUTRAN Attach Complete (new event info). Call setup events: CSFB Call Initiation. Incorrect positions assigned when exporting logfile in plain-text format from TEMS Investigation 13.00. defaulting to an erroneous PCI “768” in such cases. 3. CSFB Blocked Call.0. CSFB Call Attempt. TEMS Investigation crashed on trying to read Windows 7 performance counters that were corrupted.0.99. New events and one new information element related to the CS fallback mechanism. EUTRAN Detach Accept (new event info). EUTRAN RRC Connection Release Redirected Success. 4 4.2 Bugs Corrected in TEMS Investigation 13. Support added for PCTel MX EU firmware version 02.00. LTE cells sometimes not matched properly in XML cell file.0. PS Data Interruption Time Due To CSFB. Cell Reselection To EUTRAN.
Size Increase (frequency of jitter buffer size increases). Support added for ZTE MF682. Special Subframe Configuration. Timestamps given with 1 ms resolution in message windows and logfile text format export.1 PJSIP VoIP client added as alternative to CounterPath. UL/DL Configuration Type. MTSI Session Completion Failure Ratio (%). PBCH BLER. Support added for Samsung SCH-I510. More LTE information elements obtainable with Qualcomm chipset based devices: MAC PDU Handover Interruption Time. Possible to select AMR-NB or AMR-WB as VoIP speech codec. 9/15/2011 3 . NT11-18532. Support added for Sierra Wireless AC320U.0. nCCE Average/Min/Max.2 Enhancements in TEMS Investigation 13. Support added for Vodafone K5005. Improved VoIP testing: TD-LTE information elements introduced: Ack Reporting Mode. MTSI Session Setup Time (s). Overruns. Extensive set of VoIP jitter buffer metrics obtained as information elements: RFC 1889 Jitter. Support added for Samsung SGH-A307 (LTE part). Support added for ZTE AL611. UL/DL Configuration. PDSCH Transmission Distribution elements. Lost Packets. Support added for Samsung SCH-R380. Np and Np+1 Distribution.0. Underruns.4. Position of Minimum k Distribution. Support added for ZTE AL621. The KPI computation itself is done in TEMS Discovery or TEMS Automatic. MTSI Session Setup Failure Ratio (%). HSUPA: New information element “HS UL E-DCH TTI (ms)” indicating TTI length (2 ms or 10 ms). MTSI Registration Time (s). Average/Min/Max Playout Delay. Support added for Qualcomm TD9200 TDD. Events generated enabling computation of the following VoIP KPIs: MTSI Registration Failure Ratio (%). Decoding Errors. PCFICH CFI Information. Possible to select AMR speech codec rate. Support added for LG MN270. PUSCH Phy Throughput. Support added for LG FM300. 3.
it may take 10–20 minutes for the installation to complete (if . (This procedure can be automated by the use of Group Policies.1 VoIP testing: FR (Full Rate) speech codec option removed. If a network has been detected. this is indicated by the HASP key LED blinking.0 was not already present on the PC). On the Advanced tab. 6 6.) 4 NT11-18532.0. and from the Tools menu select Internet Options. While the upgrade is in progress. You then need to restart the Sentinel HASP License Manager service in Windows. the Sentinel HASP License Manager on the license server and client machines must be of the same version.0. Always crosscheck the versions manually to avoid attach/detach failures.NET Framework 4.2 Removed Features in TEMS Investigation 13.1.1 None Removed Features Removed Features in TEMS Investigation 13.5 5. If TEMS Investigation takes a long time to start up (more than about 45 seconds). it will be upgraded to SRM version 5. TEMS Investigation will not continue until this procedure times out.1 Known Bugs and Limitations PC Application Related Installation and Start-up When installing TEMS Investigation for the first time. under Security. a reboot may take place after the .0 installation. On some PCs.0.NET Framework installation. In the course of the TEMS Investigation 13. the firmware upgrade has failed. uncheck the option “Check for publisher’s certificate revocation” and click Apply. If the blinking does not stop within one minute. the delay may be caused by the OS trying unsuccessfully to check the application’s Verisign certificate. 3.1 6.2 5. There are two ways to remedy this: 1) Open up your proxy to enable access to the Certificate Revocation List. The details of how to accomplish this may vary between countries. if the HASP key contains HASP SRM version 4 firmware. For the license attach/detach mechanism in the Admin Control Center to work correctly. the OS will try to contact Verisign to verify that the certificate is not on the Certificate Revocation List (CRL).9/15/2011 . The application start-up time may be prolonged if slow network shares are mounted on the machine. 2) Turn off the certificate revocation check in Internet Explorer: Open Internet Explorer. or reboot the PC.
The temporary files are named according to the format “temsn” and created in the Windows temp directory (default: C:\path\tmp. Depending on the type and number of devices connected. however. TEMS Investigation will not recognize file paths such as C:\User\<user name>\. User-created workspaces from previous versions of TEMS Investigation need to be recreated. chapter 7. 9/15/2011 5 . any Map settings will be lost. if the application terminates abnormally. 3.0. Note. During logfile recording as well as during logfile replay. That is. 2) Navigate to HKEY_LOCAL_MACHINE > System > Current Control Set > Services > sermouse. however. This will prevent Windows from identifying the GPS device as a mouse. Some GPS units may be erroneously identified in Windows as an “MS Serial Ballpoint” device. If this occurs. choose Start > Run > regedit. 3) Locate the entry “Start” and double-click on it. the TMP variable can be modified from the Control Panel: System Properties > Advanced > Environment Variables). The XML cell file format permits only “YYYY-MM-DD” as date format. the number of windows in the workspace should be kept to a minimum to lower the CPU load. the hub may otherwise not be able to deliver sufficient power. the USB hub should not be powered through the USB port alone. This will prevent proper use of the application. the exact size depending on the number of devices activated in the application at recording time. 4) Change the value Data from 3 to 4. When using the Copy Worksheet function. It needs also to be stressed that an uninterrupted USB connection between PC and device is vital for successful recording of realtime measurement data. where the path is defined by the environment variable TMP. temporary files are created by the application to enable the user to browse the history of the logfile. When installing TEMS Investigation under Chinese or Japanese Windows.0 hub is strongly recommended for drive tests.. When many devices are used for data collection. this might not happen. perform the following steps: 1) With Administrator privileges on the PC. See the Getting Started Manual.1. The files must then be removed manually. where <user name> contains Chinese or Japanese characters.) 6.. These files can become very large (3–4 times the logfile size). in Windows XP. (Similar problems may occur with other non-ASCII characters. The temporary files are removed when you exit the application. It is also advisable to start a new logfile recording at least once every hour in order to reduce RAM consumption. NT11-18532.2 Application Use Note: PC settings and hardware capabilities that are checked by the Computer Diagnostics utility are not covered here. that leaving the setting Data = 4 will prevent you from identifying new mouse devices until you change the value back to 3. Make sure there is plenty of space on the disk where the temp directory resides.. New workspaces are supplied with the application. A separately powered USB 2.
You can either disable IP sniffing by setting ipSniffEnabled="false" (and consequently miss out on KPI data). you must click the Pinpoint button before starting logfile recording. the Logfile Progress indicator turns red. as soon as you pinpoint close to the edge of the Map window. not the other way around. and the message “No records written to file” appears. or you can ignore failure to start IP sniffing and go ahead with the execution anyway: ignoreIPSniffError="true". and paste material in text fields.config. The Swap Logfiles function does not work properly if used during scanning. After swapping logfiles. cut. any user names and passwords (e. for FTP or HTTP servers) given in commands are saved with the file (encrypted). Service Control Designer: To copy. If your data collecting device is unable to perform the IP sniffing (example: Sierra Wireless USB 306/307 connected via NDIS under Windows 7). and it may be necessary to swap logfiles more often than once every hour to prevent RAM usage from becoming excessive. a restricted form of IP sniffing is started which is performed continuously for the sake of collecting input to KPI calculations. After a few updates.0. a script run from one of them could fail. You cannot zoom or manually pan the map (using the Map window toolbar buttons) while pinpointing. Service Control Designer: In a script workflow. NT11-18532. etc. logfile swapping should be done in idle mode. the map will scroll automatically. which by default reads: <dataServicesConfiguration ipSniffEnabled="true" ignoreIPSniffError="false" />. cannot be used for this purpose. use the context menu in the text field.exe. you can work around the problem by editing a line in the file <TEMS Investigation install dir>\Application\Investigation. TEMS Pocket 8. 3. Logfile Progress is indicated correctly. When using the pinpointing function. so that the TAB file cannot be opened in TEMS Investigation.g. Only the Parallel activity as a whole can be collapsed. it is not possible to collapse the individual branches (Sequence activities) of a Parallel activity. If you swap logfiles while running the Status Control Monitor. the data volume logged will be huge. Logfiles merged with uplink data (MTR) files may contain internal reports with erroneous timestamps. When you save a Service Control script to file. The keyboard accelerators Ctrl + C. Whenever possible.9/15/2011 6 .) When turning on all extended logs for Sony Ericsson and Qualcomm chipset based devices (without turning off something else). (However. Service Control Designer: If multiple Service Control Designers are open simultaneously.x (HTC) logfiles are not positioned correctly using the TEMS Pocket Positioning Tool. a Network Connect activity must be recorded at the beginning of the new one for average throughputs to be calculated. When a Network Connect activity is executed in a Service Control script. By the latter method you obtain KPIs normally for all devices where the IP sniffing does not fail. The workaround is to create a new TAB file manually in TEMS Investigation using the Position Map function. Note that another user who runs your script will be accessing the server using the same user name and password.
During video streaming. it will cause TEMS Investigation to crash. try changing the color setting to 16 colors in the Windows display settings.0. IP packet capture/analysis may stop after less than one minute when using multiple CDMA phones. The Channel Verification tool causes the Sony Ericsson W600i phone to be deactivated. 3. When using the serving cell indication in the Map window to show the strongest scanned CPICH. If Iperf is installed on a Linux/Unix server. PESQ drops which do not correlate to radio or other network problems may sometimes occur. if stripes appear in the picture. make sure the default setting for passwords (PasswordAuthentication yes) is used in the configuration file on the SSH server /etc/ssh/sshd_config. During CS voice testing.1. 9/15/2011 7 . Full IP sniffing is not recommended in high data rate scenarios (say. During VoIP testing with CounterPath. IP sniffing (unless restricted using the “Optimized Performance” option) cannot be turned on while doing data service testing at throughputs above 25 Mbit/s. then to enable the use of passwords in Iperf testing. > 25 Mbit/s). this works only for the 1st UMTS frequency (the one decoded into the information elements named “1st”). UDP upload testing causes very high CPU load. When running video telephony from a Service Control script. (This limitation does not apply to VoIP. Full IP sniffing can only be done with one device at a time. section 8. PESQ is not computed for the AMR-WB speech codec.) The phone must be locked to GSM when performing GSM Channel Verification with a WCDMA capable phone. SMS and MMS testing with Service Control scripts does not work for CDMA devices that do not support AT commands. NT11-18532. due to the low resolution of the Iperf process. How to set this lock (on Radio Access Technology) is described in the User’s Manual. If full IP sniffing with more than one device is attempted. the network port on that server must be mapped to terminal vt100.6. TEMS Investigation will stop working correctly. and moreover it cannot be reactivated until the application has been restarted. If Iperf is installed on a Linux/Unix server. The waveform in Network Bandwidth line charts will be jagged and not smooth. If turned on. the phone needs to be locked on WCDMA. Map the port by editing a line in /etc/profile: tset -I -Q -m network:vt100 An incorrect mapping will cause the following error: tset: unknown terminal type network Terminal type? If Iperf is installed on a Linux/Unix server. the PS1 variable must be changed to PS1=”>” in the Unix shell Bash in order for Iperf information to be correctly displayed.
It may also need to be disabled for other reasons. It may also need to be disabled for other reasons. however.3 Windows 7 Specific Under 64-bit Windows 7 (x64). Qualcomm FFAs. Pantech UML 290. depending on its configuration. Huawei E398. The problem does not arise with 32-bit (x86) Windows 7 installations. the Investigation. 6.6 Mbit/s Network delay = 500 ms 8 NT11-18532. some issues with poor uplink and downlink throughput can be resolved by manually adjusting the TCP window size.2 6.2. the connection manager must be started to enable the Network Connect activity in Service Control.1. Here is an example showing how to do the calculation. Note that when the network connect is performed manually. Suppose that: Maximum bit rate = 3.9/15/2011 .1 Device Related Network Connect Some LTE devices must be connected to the network manually. 3. 6. This applies to: Samsung R900 (in LTE mode) Most Qualcomm LTE devices (e. This setting is found in the registry under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ The ideal TCP window size for a given maximum bit rate is dependent on the network delay. The information element LTE Total RS Power is valid only for the bandwidths 5 MHz and 10 MHz. ZTE) For Samsung GT-B3710 without AT port.exe file may have to be excluded from virus scanning to avoid a known issue with the Sentinel HASP driver.2 General In Windows XP. using their connection managers.0.2. 6.gst files can still be created. User Access Control needs to be turned off to allow IP trace.g. 6. a Network Connect activity must still be included in the Service Control script for the subsequent data service activities to execute correctly. . depending on its configuration. an error message about writing to the Windows registry appears. rather than automatically in the Service Control script.1.4 Windows Vista Specific User Access Control needs to be turned off to allow IP trace. When starting the GeoSet Manager.
Certain connectable devices respond to very few AT commands. before starting TEMS Investigation. Check whether that function is enabled as follows: 1) Open a Command Prompt using the Run As Administrator option (right-click the Command Prompt item on the Start menu).000 bits. 6.3.800. To obtain the optimum scaled RWIN. One example is the Samsung SPH-M320. the optimum RWIN = TCP Receive Window is 256. multiply the unscaled RWIN by 2 repeatedly until the BDP is reached: 64. give the command netsh interface tcp set global autotuninglevel=<autotunelevel> to enable it.3. 9/15/2011 9 . The value of <autotunelevel> should be “highlyrestricted” if the server you are contacting does not have RFC1323 implemented or does not support the TCP receive window scaling factor. Otherwise. Windows Vista and Windows 7 have a function for automatic tuning of TCP settings.960 (> BDP).240 × 2 = 128.6 × 106 bit/s × 500 × 10–3 s = 1. 6.3 6. When all devices have installed. given the above assumptions.535 / 1460) = 44.240 bytes is a good configuration for a connection with MTU = 1500 and MSS = 1460.800.0. install the devices one at a time to avoid problems with driver mix-up in Windows.1 Phone Related General If you intend to use a USB hub for connecting multiple devices. Thus. 44 segments totaling 44 × 1460 = 64.960 bytes.480 (< BDP) 128. or 1. 2) Type netsh interface tcp show global and inspect the value returned for Receive Window Auto-Tuning Level. <autotunelevel> should have the value “normal”.480 × 2 = 256.Maximum Segment Size (MSS) = Maximum Transmission Unit (MTU) – header size = 1500 – 40 = 1460 bytes Then: Bandwidth-delay product (BDP) = 3. That is. It is wise to do this in the office.2 Sony Ericsson (Android) General instructions for Xperia arc and Xperia X10: NT11-18532. 3.000 bytes Unscaled TCP Receive Window (RWIN) = floor(Max Buffer Size / MSS) = floor(65. start TEMS Investigation and check that all devices are detected properly and can be activated in the application. 3) If this parameter is disabled. You will need to restart Networking in Windows XP for the new TCP window size to take effect.000 / 8 = 225.
1 and 2.) When connecting a USB hub with Sony Ericsson phones to a Windows Vista PC. Click Next. the Network Connect activity in the TEMS Investigation script.0. USB 1. USB 1. so that the detect may take some time to complete. C702 and W760. Right-click the first “SEMC HSUSB Device” and select Update Driver Software > Browse my computer for driver software. (Look at the status indicator on the Navigator’s Equipment tab to view the current detect status for the device.) Activate USB debugging so that all relevant ports become visible: Press the Menu button.9/15/2011 . 3) Unplug and insert again to make the memory stick driver install. the phone with the lowest port number in the USB hub is sometimes not detected. do as follows when first connecting the phone: 1) Insert the USB cable. note that 32-bit and 64-bit Windows must be distinguished. device drivers can take a while to get running after you plug in a Sony Ericsson phone.3. when the automatic driver installation fails. Instructions for driver installation: Connect the Xperia phone to the PC. 3. open the Device Manager on your computer.1 default Sony Ericsson phones are: Z750.0 (High Speed) and USB 1. Example of path: . The driver software for the memory stick needs to be installed on the PC to avoid problems when connecting a phone that is turned off. Make sure no APN is set in the phone: Press the Menu button. which tries to set the APN. (If an APN is already present in the phone.. 2) Wait for drivers to install. 6. and make sure nothing is set..1 (Full Speed) Sony Ericsson phones.3 Sony Ericsson (R13) Avoid mixing USB 2. then choose Settings > Applications > Development. and make sure USB debugging is enabled. we recommend that you plug the phones into the USB hub one at a time.\Drivers\Sony Ericsson\x10\Win64. This is solved by unplugging and reinserting the phone.0 changeable Sony Ericsson phones are: C905 and W995. When using a USB hub with a Windows Vista PC for connecting Sony Ericsson phones. Browse all the way to the directory where the applicable driver for your operating system is stored. Repeat the procedure for the remaining “SEMC HSUSB Device” items. Locate the Xperia phone with missing drivers under Device Manager > Other devices. If the K790/K800 has a memory stick. as doing so will cause some SEMC devices not to communicate correctly over AT with TEMS Investigation. 10 NT11-18532. In Windows Vista. Windows will try to find drivers. will fail. then choose Settings > Wireless & networks > Mobile networks > Access Point Names.
3. Qualcomm FFAs of chipset families with LTE capability (MDM9200 and MDM9600) are autodetected in TEMS Investigation as “Unknown MDM9x00”. If a Sony Ericsson TEMS Pocket phone is activated in TEMS Investigation and the USB cable is pulled. To enable detection of the Ericsson Fixed Wireless Terminals. When AMR-WB speech coding is used. The hardware information and the number of devices used are sometimes missing in the logfile information (accessed by clicking the Information [“i”] button on the Replay toolbar). the signal strength measurements will become invalid for other cells.0. or seem to be locked to GSM. the number of characters is severely limited (worst case: max 23 characters). GSM channel verification: 1) The phone must be on GSM before start of test. 3. When sending SMS messages from Sony Ericsson phones such as Z750 and W760. See the User’s Manual. HTC Touch Pro2 phones with TCP router need special configuration to be usable with TEMS Investigation.4 for details on how to operate this utility. TEMS Pocket will remain disabled until either 1) the phone is restarted. Ascom is not authorized to change this behavior. section 7. The device may then be impossible to activate in TEMS Investigation.3. 9/15/2011 .4 Qualcomm Chipset Based Phones and PC Cards Some Qualcomm chipset based commercial UEs may not have test reporting activated. or 2) the phone is activated again in TEMS Investigation and then deactivated normally in the application. although it is built on a supported chipset. otherwise the test will stall and after 20 seconds an error “BCCH Lost” will be displayed. When an Ericsson Fixed Wireless Terminal is activated. you must restart the application for the change to take effect. it is necessary to disable the keylock first. Sony Ericsson K600/W600: If CKPD is going to be used to execute video calls.config. it is not possible to do data service testing with any other devices at the same time. Please contact the UE vendor. the Sony Ericsson phone is unable to measure GSM C/I.3. Care needs to be taken when using the NV interface to write to a Qualcomm chipset based device. 6. If TEMS Investigation is running. 11 NT11-18532. If a Qualcomm chipset based device is not detected by TEMS Investigation. When locking the phone on a WCDMA cell. since an inappropriate NV write may damage the device.Equipment.3. See the User’s Manual. section 7. but this does not work for phones prior to W760i and C702. 2) The channel verification function attempts to disable handover on the phone. uncomment the line containing "QualcommNetworkDetector" in the file <TEMS Investigation install dir>\Application\Configuration\Investigation. you can run the Manual UE Configuration utility to help TEMS Investigation recognize the device.3. AT commands in Service Control scripts are not always executed by Qualcomm chipset based devices. a base type with only LTE reporting. and/or only deliver low-level reports.
SMS Send works. 3. video call dialing is not supported. When locking the Nokia phone on a band. Sierra Wireless AC319U: Repeated network connects/disconnects must be avoided for this device.9/15/2011 12 .6 Nokia NTM3 Phones When the Nokia phone switches from GSM to WCDMA. The best course of action is to set ignoreIPSniffError="true" in the file <TEMS Investigation install dir>\Application\Investigation. If you encounter problems activating a Nokia NTM3 phone in TEMS Investigation. but may generate error messages. Furthermore. it is recommended that you restart the phone before locking on a different WCDMA band or releasing the band lock. this action should be preceded by disabling the band lock. however. NT11-18532. if you do not want to wait through the 20-minute period. 6. High data throughput may cause the Nokia C7 phone to reboot (see Nokia release notes). GSM values remain in TEMS Investigation presentation windows. For the above reasons.1. rather.3. the phone will lock on all bands that you have selected at some point. Service testing with Samsung SPH-M320 does not work. there is a need for a power reboot of the phone.config. sending of SMS messages will not work. if the phone is locked on a WCDMA band and you lock on a different band. If the default setting True is retained. The Network Connect activity must therefore not be placed inside a loop in a Service Control script. Samsung Omnia II does not answer incoming voice or video calls. When WCDMA band lock is enabled. IP sniffing does not work with Sierra Wireless devices such as USB 306/307. then release that lock. These are old values and linger because Nokia NTM3 phones stop reporting on GSM after the switch. To run the SMS Send script activity on a Nokia 6720. Therefore you cannot immediately go back to the band you were on before applying the band lock (or to a cell on that band). the video call capability of the Nokia C7 is not supported in TEMS Investigation. To restore RF data delivery you need to disconnect and reconnect the device. For Samsung Metro GT-S5350. answering a video call is possible. it should be performed only once at the beginning. FTP does not work with Samsung Omnia SCH-i910. you will get no substantial phone logs for 20 minutes. Sierra Wireless AC503 stops sending RF logs after 10–20 minutes of dual data session testing. 6.0.exe. any attempt to access a cell on any other WCDMA band will result in that cell being barred for approximately 20 minutes. Also. If you click OK between selections of different bands.3.2. you must set the parameter Request Delivery Report to False. see this item in section 6.5 Samsung Devices Based on Samsung Chipset The event IP Interruption Time cannot be generated for Samsung chipset based devices.
If such failures occur frequently. 2) For all LTE scanning methods. 3. and some bandwidths may not be at all applicable to the band in question. Failures of this kind are also recorded in the logfile in the form of error messages indicating that the connection to the AQM module has been lost. PESQ calls may fail with error message “3 AQM Module errors”. the PC application may need to be restarted to enable reactivation of phones. or to restart the module by powercycling it. This can be caused for example by the module being physically disconnected from the USB port or by the module not responding. Automatic swapping of logfiles is not recommended. If the USB connection is broken during AQM measurement. as this can cause the merge mechanism to fail. When running AQM measurements. 6.0. the set of channel numbers available for scanning is dependent on the bandwidth selected.4 AQM Module Related The drivers for AQM modules are not signed.1 Scanner Related General Starting several scans in rapid succession (e. This is done from the Navigator’s Equipment tab (bottom pane. The AQM module then needs to be paired once again with its phone.5 6. The workaround is to wait until one scan starts returning data before starting another.g. Example (EUTRA Band 7): RSSI scan: 100 kHz bandwidth.4 MHz bandwidth: N/A 3 MHz bandwidth: N/A 5 MHz bandwidth: available channels 2772–3428 10 MHz bandwidth: available channels 2795–3405 15 MHz bandwidth: available channels 2817–3383 13 NT11-18532. This message is shown when the PC application has tried to contact the AQM module three times and failed on all occasions. available channels 2750–3449 Signal scan: 1. Activities “subtab”) by right-clicking the PESQ Device Pairing item and choosing the correct AQM module in the setup dialog. so that warning messages will appear during installation. it is recommended to use the Start Recording and Stop Recording activities in the script to ensure that each logfile contains a full call sequence. pilot scan and RSSI scan) may cause TEMS Investigation to stop updating scan data. LTE scanning: 1) For RSSI scans. The proper procedure when this happens is either to reset the AQM module using the reset button located on the back of the module. 9/15/2011 .5. and possibly even hang the application.6. the bandwidth must always be set to 100 kHz. this indicates a bad USB connection or power cable.
causing the pipeline to overfill. all fields in the setup dialog must have some value set.5.1. NT11-18532. Scan data is dropped automatically when the scanner is scanning faster than the data can be delivered through the data link. To solve the problem. When plugging in a PCTel SeeGull LX scanner that uses a serial connection. The scanner API does not support multiple connections. stop the Mobile Broadband Service and preferably set startup type to “disable”.9/15/2011 14 . otherwise you cannot click OK.x and earlier. It is crucial to supply the SRUs with adequate power. Restrictions on compatibility: Firmware versions 02. if you remove the cable from the serial port without first deactivating the scanner in the application. 6. For example.5. the “Use Pilot Increment” option is not available. The scanner uses this message to tell the host how many scan data messages were dropped and not delivered through the data link.4 PCTel SeeGull LX/EX If you do not deactivate the scanner properly from within TEMS Investigation. and when it is connected to the port again the activation might fail.03. Enter dummy values in the dialog as needed. With some PCTel scanners only 2560 measurement points can be allocated for spectrum scanning. Swap logfile cannot be used while scanning with a DRT scanner.2 SRU Always install new drivers from the TEMS Investigation driver installation CD and not from the internal SSD drive.xx and earlier are not compatible with TEMS Investigation 12. When setting up a follow phone scan in CDMA. 20 MHz bandwidth: available channels 2840–3360 6. turn the scanner off and on and the activation function will work again. click the Refresh button on the Navigator’s Equipment tab to ensure that the scanner is detected. Firmware versions 02. which may hold older drivers.x and later. It may be necessary to use the accompanying 12 V adapter.0. To prevent problems detecting the SRUs in TEMS Investigation. problems may arise when you try to activate it again.3 DRT 4301/4301A/4301A+ The DRT scanner will reboot after a period of time if it is connected via a LAN and is detected by multiple TEMS Investigation users. 6.5. The PCTel scanners may sometimes report many scan drop messages. For EV-DO scanners. measurements will continue to run in the scanner.02. 3.xx and later are not compatible with TEMS Investigation 12.0. since each logfile must contain a scan start. even though the scanner in fact has more measurement points available.
then if the scanner is activated in TEMS Investigation and you pull its cable. 6. The USB cable must be connected at startup in order for the scanner to boot correctly. the scanner should be rebooted. rather. section 26.5.1. (To make use of the “invalid” positions you need to turn on an option in the GPS window properties. Garmin Street Pilot 2650 labels its calculated positions as invalid in the PC interface yet presents the positions on its display without any such indication. If this problem occurs. you may need to restart TEMS Investigation to be able to activate the device in the application. When a PCTel LX MM2 scanner is connected to TEMS Investigation you cannot use the Activate All function. If the scanner is turned off during use. If the power is lost on a Bluetooth GPS device.) To activate the Nokia LD-3W Bluetooth GPS device. first start up TEMS Investigation. Wait for the application and computer to establish the pairing. Do not install any driver provided on PCTel’s web site.0. then restart TEMS Investigation. The reason is as follows: If you have PCTel’s own driver installed. disable the “Intel Active Management Technology – SOL” driver if it exists on the PC. 6. The positions calculated by dead reckoning are indeed mostly useful and enable TEMS Investigation to plot the route reasonably correctly when GPS coverage is temporarily lost. version 2. you must activate each device separately. you must exit TEMS Investigation and repeat bullets 2 and 3 above before you can connect the scanner again. the scanner port will not disappear from Windows and thus not from the TEMS Investigation user interface either. If a Bluetooth GPS cannot be found.5 PCTel SeeGull MX Detection of PCTel SeeGull MX scanner: After the driver has installed and Windows has detected the device for the first time. 6.0 and later. be sure to install the driver delivered with TEMS Investigation. A “Refresh equipment” operation may be needed in the Navigator if the device still does not appear. Only after this can the GPS be successfully activated on the Navigator’s Equipment tab. For the PCTel SeeGull EX scanner. Then connect the GPS logically in Windows. After powering on the scanner. 15 NT11-18532. see the User’s Manual.6 GPS Related While in dead reckoning mode. always wait for its bootup procedure to complete (LED turns dark green) before starting TEMS Investigation. try to restart the GPS. 9/15/2011 .0.6 PCTel SeeGull PCT The PCTel SeeGull PCT scanner may not be detected on some PCs. during which time the LED is pale green or orange. 3. This can take up to 90 seconds.5.1. outside of the TEMS Investigation application. The driver delivered with TEMS Investigation contains a modification that removes the scanner port in the situation just described.
If the tool is not installed. download and install Windows Management Framework Core package (Windows PowerShell 2.sourceforge. 3.7 Call Generator Related The Call Generator installation requires an English-language edition of Windows. 6. Start the service.microsoft.0) from Microsoft (download link: support. For the Call Generator Windows Server 2003 to function correctly. make sure you have Powershell installed. type: ipconfig/renew. This project can be found on the Internet at http://libusbwin32.net.6. 16 NT11-18532. The libusb-win32 project retains all rights and copyrights to the libusb-win32 code.9/15/2011 .com/networktesting 8 Appendix OPEN SOURCE LICENSING INFORMATION The USB driver (libusb0) used for AQM module is part of the open source libusb Windows project. choose Start > Run > Powershell. With Administrator privileges on the PC.0. please visit our website on the Internet: www. Start the service.0 and WinRM 2. Plug in the internet cable. do one of the following (the two procedures have the same effect): 1) Remove the internet cable. The LGPL and GPL license text can be found on TEMS Investigation driver installation CD.com/kb/968930). At the command prompt. 2) Open a command prompt and type ipconfig/release.8 TEMS UDP Server Related If the following error message appears when the server is starting up: “Error 1053: The service did not respond to the start or control request in a timely fashion”. 7 Contact Information For customer support contact information. The source code for libusb-win32 is freely available and can be found on the TEMS Investigation driver installation CD. The library (DLL) is distributed under the terms of the GNU Lesser General Public License (LGPL) and the driver is distributed under the terms of the GNU General Public License (GPL).ascom.