TEMS Investigation 14.6.4 update link

**hp3hp3** · 2013-07-29, 05:38 PM

TEMS Investigation 14.6.4 update link

install 14.6.2 and update it to 14.6.4

http://www.4shared.com/zip/tPapaiBi/...60-0047_R.html
http://www.4shared.com/rar/McbGfOhj/...ation1464.html

**Finetopix** · 2013-07-29 05:38 PM

**comateo** · 2013-08-06, 10:56 AM

Can we use this version without hard key?

**www.nodongle.biz** · 2013-09-29, 04:20 PM

New Features in TEMS Investigation 14.6.5

· In scripted logfile recording it is now possible to record only GPS data from a scanner and not its scan data. To do this, select the device as preferred GPS and do not include it among the devices to record (Equipment property in Start Recording activity).

· From TEMS Investigation 14.0 onward, presentation windows are cleared (by design) when you start recording a new logfile as well as when a device is deactivated. To enable viewing of the entire route driven during a testing session, a new map layer “Track Layer” has been added in which GPS positions are plotted. This layer is never cleared while recording is in progress (only when a logfile is opened or TEMS Investigation is closed). By default the Track Layer is hidden

_____________________________________________________________________

Corrected Bugs

· No line to CDMA serving cell/active set drawn in Map window.

· Network disconnect occasionally took a very long time to execute on Samsung Galaxy S II Skyrocket i727. – The DHCP release was what stalled the procedure; this step has been disabled for the Samsung device in question.

· In a script while loop with Start Recording and Stop Recording, a new recording was occasionally started without the previous one having been stopped, resulting in duplication of data.

· During multicarrier operation, EV-DO Rx Power was sometimes wrong in connection with inter-frequency changes in EV-DO active set.

· Non-existent SIB11bis messages appeared in decoding of UMTS signaling. – Previously, when lacking adequate scheduling information, the decoder tried to guess the identity of certain common SIB messages, a procedure which was fallible. The guessing has now been reduced to a single case: If only one type of SIB has been seen in the entire session or logfile, then a doubtful SIB is assumed to be of the same type. The SIB detection algorithm has also been improved, so that SIB type is determined with higher accuracy.

· TD-SCDMA cells in cell file were not handled correctly in TEMS Investigation 14.x.

· Message windows did not update after changing devices in a worksheet (such as the preconfigured ”Signaling” worksheet). Reload of the logfile was required. – Behavior changed so that message windows are automatically refreshed with data from the new device. It should be noted that for large logfiles, this takes a non-trivial amount of time.

· Unreasonable values sometimes presented for EV-DO Ec/Io and Ec.

· RTP messages from Qualcomm IMS ICD logs were not handled properly.

· Qualcomm ERRC Layer 3 signaling was not handled properly.

· WCDMA SIB19 from Qualcomm chipset based device was not decoded.

· Merging of uplink PESQ into logfiles failed. – More robust handling of invalid (NaN) MOS scores introduced.

· After R&S TSMW scanner stopped measuring because of low signal strength, TEMS Investigation kept recording the last valid measurement.

· For PCTel, a GSM RSSI scan could be configured and started with System Information decoding selected even if the scanner did not have the System Information option (0x00050001) installed. – TEMS Investigation user interface corrected.

· Issues with WCDMA CPICH scan of UARFCNs belonging to different bands using PCTel MX scanner.

· Presentation of PCTel MX scanner data was faulty in TEMS Investigation 14.6.2 and 14.6.4.

· LTE SIB10 incorrectly decoded as SIB12.

· No Dropped Call event generated in connection with CM Re-establishment Request in GSM. – Logfile did not contain the preceding call setup; event generation has been modified to deduce call state in the absence of such information.

· Pinpoints in old logfiles did not display in Map window.

· Error message “Not enough bits left for operation” appeared in plain-text decoding of RRC message.

· No data shown for LTE PUSCH Phy Throughput. – Bug fixed in determination of RRC state (assumed to be Idle when it was in fact Connected).