Mentum Planet Release Note

Cover Page

>> Release Note

for version 5.2.1

Copyright © 2010Mentum S.A. All rights reserved.

Notice

This document contains confidential and proprietary information of Mentum S.A. and may not be copied, transmitted, stored in a retrieval system, or reproduced in any format or media, in whole or in part, without the prior written consent of Mentum S.A. Information contained in this document supersedes that found in any previous manuals, guides, specifications data sheets, or other information that may have been provided or made available to the user. This document is provided for informational purposes only, and Mentum S.A. does not warrant or guarantee the accuracy, adequacy, quality, validity, completeness or suitability for any purpose the information contained in this document. Mentum S.A. may update, improve, and enhance this document and the products to which it relates at any time without prior notice to the user. MENTUM S.A. MAKES NO WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THIS DOCUMENT OR THE INFORMATION CONTAINED HEREIN.

Trademark Acknowledgement

Mentum, Mentum Planet, Mentum Ellipse, and Mentum Fusion are registered trademarks owned by Mentum S.A. MapInfo Professional is a registered trademark of PB MapInfo Corporation. RF-vu is a trademark owned by iBwave. This document may contain other trademarks, trade names, or service marks of other organizations, each of which is the property of its respective owner.

Last updated October 19, 2010

Mentum Planet 5.2.1Release Note

IntroductionThis document accompanies the release of Mentum Planet 5.2.1. It includes information specific to Mentum Planet and supported technologies (i.e., LTE, WiMAX, cdma2000, WCDMA, TDMA-FDMA, and GSM). Depending on the licenses that you have purchased, some of this information may not apply.This document contains the following information:

■ New features and enhancements■ Issue resolutions■ Known issues■ Known limitations■ System requirements for workstations■ Documentation

■ Getting help

New features and enhancementsMentum Planet 5.2.1 now supports WCDMA and TDMA-FDMA/GSM. This release also introduces new enhancements to the Mentum Planet 5 platform.

1


version 5.2.1■ Support for LTE TDD

■ Support for LTE TDD frame configurations■ Support for special subframe configurations

■ Ability to generate fixed subscriber analyses■ Fixed subscribers analyses are now supported for

WiMAX TDD, LTE FDD and LTE TDD■ Support for fixed subscribers at different heights■ Fixed subscriber editor■ Ability to run analyses for a single subscriber

■ Enhanced Automatic Site Placement tool■ Ability to define a candidate site list and site priorities■ Support for network expansion■ Clutter weights

■ Support for the Longley-Rice propagation model■ Creation and analysis of Microwave Links within Mentum

Planet■ MapInfo 10.5

■ Integrated free Bing Maps layers■ Layered, geo-referenced and data-enriched PDFs■ Multiple zoom-dependent styles■ Custom composite point & line styles

■ TDD de-synchronization■ Interference matrix generation■ Network Analyses and Monte Carlo simulation

■ LTE enhancements■ Power recycling: when MIMO is used, some resource

elements are not used on specific antenna ports. In Mentum Planet 5.2, it was assumed that the power not used for those unused resource elements was lost. In Mentum Planet 5.2.1, users have the option to define if the power is “recycled” or not. This means that if MIMO is

2


used, this will impact transmitted powers, indirectly affecting network analyses and Monte Carlo simulations.

■ Downlink C/(N+I): in Mentum Planet 5.2, the Downlink C/(N+I) layer were computed for symbols on which there were reference signal resource elements. In Mentum Planet 5.2.1, the Downlink C/(N+I) layer is the average C/

3


(N+I) over all the symbols of an LTE frame. This means that the Downlink C/(N+I) layer will be impacted.

■ Antenna horizontal and vertical beamwidth are now shown in the Tabular Editor and in an export file. These read-only fields appear on the Sector Antennas tab.

■ You can now easily apply flag and group settings for one sector to all other sectors on a site. This can be done from the Sector>General tab in the Site Editor.

■ Terrain height is now displayed in the Site Editor. This field is read-only.

■ The size of the Point-to-Point Profile tool window is now saved. When you open the tool, the window size is the same as it was when the tool was last used.

■ The Planet Open API now supports the generation of traffic maps.

■ The width of flag conditions displayed in the Site Editor has been expanded. You can now view up to 30 characters (the maximum allowable) in the drop-down control.

■ Filtered surveys are now assigned to the same sectors as the original sectors.

■ The subscribers table generated through LTE Monte Carlo simulation now contains fields for RSRP, RSRQ and CQI.

■ You can now display a layer based on a Group and a layer based on Flags in a map window at the same time.

■ You can now export Total EIRP and Uplink Composite Noise Figure EIRP values for TDMA/FDMA sectors.

■ Propagation models are now sorted alphabetically in the Site Editor.

■ Project data import is now non case-sensitive. For instance, if you are importing flag conditions such as 'Active', 'ACTIVE' or 'active' all will be considered to be the same condition.

■ The survey filtering function now has options to 'Delete original survey' and 'Unassign original survey'. These options are implemented as check boxes in the Survey Filtering window.

■ You can now clone a sector from within the Site Editor. To do this, right-click on an existing sector and select 'Clone'. All

4


sector properties are copied to the new sector.■ Planet Universal Model now applies model tuning coefficients to

all geographic areas, including areas that fall outside the extents of the elevation file that was active when the model was tuned. Previously, tuning coefficients were only applied within the extents of the elevation file that was active when the model was tuned. Default coefficients were used outside that area.

■ You can access all user guide PDFs provided for Mentum Planet by choosing the Guides command from the Help menu.

■ When running propagation model analysis based on sectors, surveys with antenna properties that are different from the antenna properties on the sector to which they have been assigned are discarded. A small margin is allowed with respect to antenna height and power. The margin for antenna height is 10cm, the margin for antenna power is 0.01 dB. Case 17442

■ The Project Explorer is now part of the Mentum Planet application window. It can be docked and supports an auto-hide feature. When the Project Explorer is docked, you can no longer click within a node label. Instead, when you want to rename a node, you must type the full name of the object to be renamed.

version 5.2In version 5.2 of Mentum Planet, the following new features and enhancements have been included:

■ Support for UMTS/HSPA/HSPA+ with increased performance and scalability compared to previous Mentum Planet releases. HSPA+ support includes MIMO, 64 QAM modulation, and DC-HSDPA.

■ Beta-level support for GSM.■ Enhanced scrambling code planning, including better

algorithms, scrambling code group planning, and comprehensive management of scrambling codes.

■ Major LTE improvements, including■ Proportional Fair, Proportional Demand, and Maximum

Capacity schedulers■ Modulation Coding Schemes C/(N+I) to Spectral

Efficiency curves

5


■ Subscriber mobility support in network analyses and Monte Carlo simulations

■ Addition of antenna algorithms (up to 8 Tx and Rx antennas)

■ Simultaneous diversity and multiplexing■ PBCH Channel support■ The addition of two new layers displaying the maximum

spectral efficiency that can be reached, on the uplink and the downlink

■ Previously, in the Site Editor, the average power per reference signal resource element, as well as reference signal strength, were based on the assumption that the PA power defined was for a single antenna port. In Mentum Planet 5.2.1, if a MIMO antenna algorithm is assigned, the average power per reference signal resource element, as well as reference signal strength, are based on the assumptions that: 1) the PA power defined is the combined PA power of all the antennas and 2) if using MIMO the number of Tx antennas defined in the antenna assigned to the sector is used. This change affects the Reference Signal Strength, the RSRP and the reference C/(N+I) analysis layer. Depending on the settings that you defined, some other analysis layers may be directly impacted (e.g. DL CINR, if you used reference signal frequency hopping) and some may be indirectly impacted if based on reference C/(N+I). The change will also affect Monte Carlo simulation results.

■ Enhanced WiMAX support, including■ Proportional Fair, Proportional Demand, and Maximum

Capacity schedulers■ Interactive frequency and preamble planning■ Per-sector or per-channel preamble■ Modulation Coding Schemes C/(N+I) to Spectral

Efficiency curves■ The addition of two new layers displaying the maximum

spectral efficiency that can be reached, on the uplink and the downlink

6


■ Numerous improvements to automatic frequency and preamble planning and to existing WiMAX features

■ Support for user-defined TDMA/FDMA technologies, including■ Custom-defined TDMA/FDMA technologies■ Simulcast (P25, TETRAPOLE, and TDMA/FDMA

technologies)■ Land Mobile Radio / Private Mobile Radio networks

■ Advanced automatic site placement (ASP), allowing for smart placement of new sites using network dimensioning based on traffic and propagation characteristics.

■ Improvements to the measurement data package (MDP) to support the import of Agilent AOD files and the propagation model accuracy analysis tool.

■ Integration of MapInfo Professional 10.0 into Mentum Planet, introducing new features in Layer Control and layer management, as well as new menus and toolbars.

■ Introduction of a new version of the Universal Model (version 380). This new version includes:

■ support of Mentum Planet 5.2■ minor improvements and corrections

■ CPE coordinate units now respect the units specified in the Preferences window. Cases 11035, 12988, 15136

■ The Planet Open API now supports Monte Carlo simulation. Case 15498

■ The Link Configuration Editor can now be accessed from the Site Editor. Case 14364

■ Signal strength files are no longer kept permanently unless you specify them as an additional layer in the project settings. This change is meant to improve performance and reduce hard disk space requirements. As a consequence of this change, beginning with Mentum Planet version 5.2.0, signal strength files can no longer be shared. Case 12287

■ A new analysis layer has been added (for cdma2000 and WCDMA) that computes required mobile power based on the maximum achievable data rate. Case 12680

7


version 5.1.1■ Introduction of a new analysis generator tool that allows you to

select multiple network analyses of any technology to run in batch mode. Cases 12291 and 12717

■ Introduction of new functionality for interference matrices:■ the ability to import interference matrices■ the ability to merge interference matrices

■ Introduction of a new option (Apply Cell Loads to Selected Sectors) to the Monte Carlo Simulation node in Project Explorer. This option allows you to apply cell loads to a subset of sectors. This subset can be based on a map window selection, the flags filter, a sector group or a query. Case 13791

■ Introduction of a new version of the Universal Model (version 370.1475). This new version includes:

■ improved accuracy (e.g., clutter heights files are now computed to an accuracy of 0.25 m)

■ improved indoor penetration modeling, especially on the buildings border

■ a new version of the FLEXLM licensing software (version 11.8)

■ memory consumption improvements for large calculation areas

■ minor improvements and corrections■ Improvements to automatic frequency and preamble planning:

■ introduction of new constraints■ the ability to simultaneously view multiple plan

parameters in a Map window■ Improved scalability of Monte Carlo simulations. Case 13809■ Mobile antenna gain is now accounted for in signal strength

layers generated through Network Analysis. This change is applicable to all supported technologies. Case 10890

■ For LTE and WiMAX, antenna gain is now included in signal strength related network analysis layers. Antenna gain is also considered in LTE and WiMAX Monte Carlo simulations. Cases 12722 and 10890

8


version 5.1■ Support for cdma2000 radio access technology.■ Improved EV-DO Rev. A modeling with the introduction of

higher data rates bearers for both the forward and reverse link. In Mentum Planet 4.5, for EV-DO Rev A, 16-slot bearers were supported only. In Mentum Planet 5.1, higher data rates are supported with the ability to use bearers with 4, 8, 12 and 16 slots.

■ Support for a generic technology, providing a convenient way to manage candidate cells for which there are no detailed radio parameters.

■ Improved LTE network modeling with the introduction of an analysis layer for the RSRQ as well as improvements to the data rate layers in terms of the impact of the overhead channels on the effective data rates.

■ Improved LTE Frame Editor for inclusion of additional frame information.

■ Frequency and Physical Cell-Id ID Planning for LTE networks.■ In order to improve the performance of LTE and WiMAX

network analysis and Monte Carlo simulations in dense networks, Mentum Planet software code has been improved. The impact on the performance is project-specific; the performance

9


improvements will vary based on the number of sectors, the density of the sectors, etc.

■ Support for fiber and RF repeaters for LTE, WiMAX, and cdma2000.

■ Support for split sectors and distributed antenna systems (DAS), enabling a single logical cell to be transmitted over several service antennas.

■ Introduction of a new automatic site placement tool which enables the quick creation of networks based on a hexagonal cell structure.

■ Management of site/sector queries for private queries and shared collaborative queries.

■ Full support of antennas systems shared across multiple technologies.

■ A new Select Antenna File dialog is available from the General tab for a selected antenna in the Site Editor. The dialog box has

10


been designed to facilitate the selection of antenna patterns based on frequency bands or MIMO support, for example.

■ LTE-cdma2000 multi-technology neighbor list management. ■ The Measurement Data Package now supports LTE Test Mobile

and Scan Receiver data import, visualization, and conversion to survey data for use in model tuning

■ Ability to extract statistics for any report generated in Mentum Planet or, in the case of statistical analyses, statistics on statistics.

■ Introduction of the Mentum Planet Open API.■ Support for electronically controlled antennae (i.e., e-Tilt,

e-Azimuth and e-Beamwidth) at the cell level.■ The network overlay tool now supports input projects from

Mentum Planet 5.1, 5.0 as well as previous versions of Mentum Planet.

■ Redesigned FCC tools.■ New Select Sectors dialog box enables you to select sectors

based on groups, flags, or queries. It also includes a preview list that displays the sectors that will be selected.

■ Ability to generate site labels from the Tabular Editor and Report Preview dialog box based on selected data.

■ A new version of the Universal Model (version 370.1403). This new version includes:

■ Support for multi-threaded prediction calculation■ Support for all electronically controlled antennae

functions (e-Tilt, e-Azimuth and e-Beamwidth)■ Change of default model tuning options■ Removal of some warning message about morphologies■ Memory management improvements with high resolution

building data■ Minor improvements/corrections

11


version 5.0.1■ A new network analysis layer for the RSRP (Reference Signal

Received Power) has been introduced for LTE network analyses. This layer shows the average received power over the resource elements that carry reference signals. Case 11329

■ The calculation of the LTE reference signal was modified in Mentum Planet 5.0.1 such that it now represents the power used by the resource elements carrying the reference signal. This change naturally impacts the Reference Signal Strength network analysis layer. Other analysis layers, e.g.,the Reference C/(N+I) layer, and layers that depend on the Reference C/(N+I) (e.g., interference coordination) will be modified as well.

■ The range for the Useful Bits per Symbol value on the Modulations panel in the Network Settings dialog box has been extended so that any value between 0.01 and 10.0 can be entered.

■ The WiMAX AFPP tool has been modified to allow you to apply constraints that will force only adjacent channels to be assigned to sectors.

version 5.0■ Support for WiMAX and LTE networks—detailed modeling of

OFDMA air-interfaces and support for Advanced Antenna Systems (AAS)

■ Ease of use—redesigned user interfaces, easy-to-use tabular editors and new site management features

■ Better scalability and stability—ability to handle larger networks within a single project due to a reduced memory footprint and improved memory management

■ Future-proof platform—ready for on-going evolution of radio access networks including OFDM technologies and advanced antenna systems

■ Improved APIs—open antenna format and API with support for advanced antennas; improved iecon performance, and new APIs available

■ Better performance—improved performance in user interfaces, data-related actions and import/export functions; furthermore,

12


Mentum Planet 5.0 includes a new prediction engine that generates predictions faster than previously

■ MapInfo Professional 9.5.1—Mentum Planet 5.0 includes a MapInfo 9.5.1 OEM version with enhanced GIS functionalities.

Improved usability■ Many of the main dialog boxes in Mentum Planet have been

redesigned to support new technologies and improve the ease-of-use:

■ the Site Editor, which fully supports shared antennas and multi-technology sites

■ multiple tabular editors, which offer sorting, filtering, copying/pasting and mass editing capabilities

■ the Antenna Editor, which supports multi-band, RET, REA, and multiple antennas capabilities (e.g., MIMO and smart antennas)

■ the new Subscriber Settings dialog box, where you can define the multiple services, mobile equipment types, and subscriber types that are used in 4G analyses and simulations

■ the Environment Editor, which supports the activation and advanced settings of multiple radio environments

■ all new editors display visual cues to indicate changes to data

Improved propagation modeling■ New propagation engine offers improved prediction

performance with the inclusion of a multi-threaded prediction generator

■ Redesigned propagation model editor provides for intuitive and straight-forward editing of model parameters; furthermore, the

13


Planet model format has changed. Former .cpa and .dpm has been merged into an open xml format (.pmf).

■ Support for the following propagation models:■ Planet General Model (PGM)■ CRC-Predict 4.0 (CRC Predict 4.2 and 4.3 are included

for backwards compatibility with previous versions of Mentum Planet)

■ Universal Model, (version 365). This new version includes the following features:

New advanced model tuning algorithm that provides better robustness for tuned models

Optional pre-filtering of surveys before automated model tuning

Faster prediction computation times for very high resolutions

Correction and optimization of the building penetration option for better indoor prediction results with very large buildings

Minor improvements

■ Support for 3D antenna diagrams in the Planet General Model and CRC-Predict 4.0 propagation models.

■ Mentum Planet includes the Measurement Data Package, which encompasses the following features:

■ Support for Survey Prediction Tool, which enables you to merge measurement values with prediction values

■ Support for WiMAX Test Mobile and Scan Receiver data import, visualization, and conversion to survey data for use in model tuning

CRC-Predict version 2.0 is no longer supported. As a result, you must migrate to CRC-Predict 4.0. See the CRC-Predict 4 Emulation of

CRC-Predict 2 document.

14


Support for WiMAXMentum Planet introduces advanced support for Fixed and Mobile WiMAX RF planning and optimization through the following feature set:

■ Support for mobile WiMAX (802.16e) and fixed WiMAX (802.16d) technologies

■ Support for TDD and FDD duplexing■ Multi-technology support for WiMAX (mobile and fixed)■ Support for multiple bands and multiple WiMAX channels■ Support for adaptive uplink and downlink modulations■ Support for transmit and receive masks■ Support for multiple WiMAX frame configurations■ Support for segmentation and WiMAX permutation zones

(FUSC/PUSC)■ Support for variable WiMAX cyclic prefixes■ Support for smart antenna modeling■ Support for MIMO A (diversity), MIMO B (spatial

multiplexing) and WiMAX AMS (Automatic MIMO switching) modeling

■ Support for FFR■ Automatic preamble and channel planning■ Mobile WiMAX perm base planning (available in the Automatic

Frequency Preamble and Perm Base Planning tool)■ Automatic Frequency Planning for WiMAX■ Fixed subscribers table, editor, and management■ Support for RF environment modeling■ Support for multiple CPE equipment types■ Support for fixed CPE antennas■ Support for preamble CNIR or preamble signal-strength for best

server selection■ Uplink-limited best server selection■ Advanced WiMAX network analysis engine

15


■ Common and per-channel WiMAX analysis layer generation■ WiMAX Monte Carlo simulation■ Support for multiple scheduling algorithms■ Monte-Carlo report generation and discrete subscribers analysis

Support for LTE (Long Term Evolution)Mentum Planet introduces advanced support for LTE RF planning and optimization through the following feature set:

■ Support for LTE FDD technology■ Support for multiple bands and multiple LTE FDD carriers■ Support for adaptive uplink and downlink modulations■ Support for transmit and receive masks

■ Support for LTE frame configurations■ Support for variable LTE cyclic prefixes■ Support for smart antenna modeling■ Support for diversity, MIMO spatial multiplexing, and AMS

(Automatic MIMO switching) modeling■ Support for interference coordination/ FFR

■ Support for multiple scheduling algorithms for interference coordination

■ Support for RF environment modeling■ Support for multiple user equipment types■ Support for fixed user equipment antennas■ Support for reference signal CNIR or preamble signal-strength

for best server selection■ Advanced LTE network analysis engine■ Common and per carrier LTE analysis layers■ Support for other system interferences in LTE network analysis■ LTE Monte-Carlo simulation ■ Support for multiple scheduling algorithms■ Monte-Carlo report generation and discrete subscribers analysis

16


Site managementMentum Planet introduces a new Site Editor that facilitates the site management workflow with an intuitive and easy-to-use interface.

■ New Site Editor designed to support 4G technology sites with full management of shared antennas and advanced antenna systems.

■ Support of multi-technology base stations in the Site Editor provides the capability to manage multiple base stations using different radio technologies at the same site

■ New site set feature offers local versioning of network sites with the capability to merge or copy site sets

■ Site templates enable you to create and store multiple site templates thus streamlining the site creation process. Site templates can be shared using the Data Manager

■ Enhanced sector display schemes enable you to create sector display schemes based on user-defined statistical data. This provides flexible visualization of sector parameters and properties.

Data managementMentum Planet includes an advanced data management system including:

■ a Data Manager through which projects are stored and shared■ a flexible import/export tool through which you can import or

export:■ standard cell parameters■ mobile WIMAX, fixed WiMAX, LTE, and cdma2000-

specific parameters■ an Import / Export API for Mentum Planet (iecon command line)■ an Import / Export API for Data Manager (iecon command line)■ support for attachments to a project■ ability to manage local data versioning

17


Other enhancementsThe Mentum Planet release includes other new features including:

■ a Sector Query Editor, which enables you to query sector data using complex expressions.

Mentum Planet 5.0 included other important new features such as:■ the Network Overlay tool, which can be used to create WiMAX

or LTE networks in Mentum Planet 5.0 using sites from other Mentum Planet projects or from another data source

■ the Network Data tool, which includes a generic network data import, report review tool, sector display scheme creation ability, and traffic map creation using imported data

■ Embedded Microsoft Bing Maps™ Viewer (formerly known as Virtual Earth™), which supports Mentum Planet sites and MapInfo raster data visualization

■ a connection to the Mentum Antenna Server, which supports an antenna pattern search and download from a central antenna database repository

■ New Mentum Planet icons

Enhanced user documentationMentum Planet comes with a comprehensive documentation set including:

■ cdma2000 User Guide contains the information you need to begin creating projects and analysing networks.

■ WCDMA User Guide contains the information you need to begin creating projects and analysing networks.

■ LTE User Guide contains the information you need to begin creating projects and analysing networks.

■ WiMAX User Guide contains the information you need to begin creating projects and analysing networks.

■ Fixed WiMAX User Guide contains the information you need to begin creating projects and analysing networks.

18


■ TDMA-FDMA User Guide contains the information you need to begin creating projects and analysing networks.

■ OFDMA Collisions Technical Note contains information about the collision scenarios when in a WiMAX OFDMA mode of operation

■ LTE Analysis Layers Technical Note helps you better understand common LTE analysis layers and their intended use.

■ WiMAX Analysis Layers Technical Note helps you better understand common WiMAX analysis layers and their intended use.

■ Mentum Planet Extensions Application Note contains examples of how to extend Mentum Planet functionality using the new Extension Manager.

■ CRC-Predict 4 Emulation of CRC-Predict 2 document explains how to emulate tuned CRC-Predict 2 propagation models using CRC-Predict 4 in order to benefit from the improved overall accuracy of the new model and to provide access to the new multi-threaded prediction capabilities

In addition, you can access the Customer Care knowledge base directly from the Mentum Planet online Help or from the Help menu within Mentum Planet.

Issue resolutionsThe following issues have been resolved in this release of Mentum Planet.

version 5.2.1■ Issue whereby the current map display (based on a Group or Flag

selection) was lost after using the Find Site tool. Case 13852■ Issue whereby antenna mechanical tilt was not accounted for in

generated FCC contours.Case 17929■ Issue whereby the map layer that used to display connecting

lines between sectors and repeaters (SiteFile_Relation)

19


displayed in error. To display this layer, you must add it from the Layer Control window.Case 18892, 15659, 16415, 18744

■ Issue whereby the Workspace autosave option did not function properly. This has been resolved although it only works for a single workstation. Case 18405, 15952, 17364, and 17511

■ Issue whereby the message 'Only Auto prediction increment is supported' displayed when attempting to generate predictions. This message displayed because at least one sector had a prediction distance increment set to something other than 'auto' (distance increment = heights grid resolution). Mentum Planet 5.x no longer supports user-defined distance increments. The distance increment is set to be the same as the heights grid resolution by default. Distance increment values that do not follow this rule are converted during migration. Case 18387

■ Issue whereby some repeater properties (e.g., geographic coordinates, propagation distance, power values and antenna properties) did not appear when viewing the site table in a Browser window. Note that you must update your site file in order to view this data (right-click on the Sites node and select 'Update Site File'). Case 17878

■ Issue whereby the Query tool generated incorrect results when a query condition was based on antenna azimuth.Case 16126

■ Various issues related to project migration. Case 18075, 18246, 17508, 17989, 18298, 18323, 18539, 18914

■ Issue whereby an 'overflow' error occurred when attempting to view sector neighbors.Case 16312

■ Problem whereby the MapInfo 'Named Views' utility would not load and run properly. Case 11414

■ Issue whereby the Prediction Generator did not properly force prediction generation when building polygon data had changed. This issue only occurred when the Planet Universal Model was being used. Case 14107, 14302

■ Issue whereby the histogram, clutter distribution and regression analysis windows were not properly updated after survey points were removed. Case 14645

■ Issue whereby the Point-to-Point Profile tool froze under certain conditions forcing the user to re-start the application. The issue

20


occurred when a profile referenced a CRC Predict 4 propagation model where the clutter separation distance parameter on one or more clutter classes was set to a value of zero.Case 14581, 16243

■ Issue whereby the Data Manager 'View Differences Only' command did not function properly. In some case, differences did not display. Case 16082, 16764, 18711, 19013, 16402

■ Issue whereby changes to CDMA pilot power had differing impacts on control and traffic channel powers when made in the Site Editor as compared to the Import tool.Case 16700, 16236

■ Issue whereby long antenna names shown in the Site Editor were being truncated. Now, when you click the drop-down control the entire antenna name is displayed. Case 16410

■ Issue whereby sector Groups were not sorted in the Site Editor. Case 16407

■ Issue whereby project data import failed with an error. The issue occurred in cases where user was trying to import a repeater when that repeaters donor sector was not included in the import file. Now, a warning message is shown in the log window

21


(indicating that the repeater cannot be imported) but import will proceed. Case 16820

■ Issue whereby a Sector Display Scheme created based on the antenna horizontal beamwidth property did not properly depict the antenna beamwidth.Case 17352

■ Issue whereby survey nodes were improperly removed from Project Explorer following disconnection from Data Manager. Case 17367

■ Issue whereby the error 'Link configuration does not have sequential link budget indexes starting at 1' displayed when importing site data. Case 17400

■ Issue whereby some LTE layers were not properly supported by the Planet Open API. Case 17756

■ Issue whereby the message 'Object reference not set to an instance of an object' displayed when closing a project. Case 17746, 18467

■ Issue whereby local attachment files were incorrectly deleted following disconnection from Data Manager. Case 17898

■ Issue whereby antenna properties were not properly saved in Fixed WiMAX subscriber settings (equipment types). When a project was re-opened, antenna properties reverted to their original values. Case 17860

■ Issue whereby the pilot % of PA power value is set incorrectly when placing a CDMA EV-DO site using a site template. Case 18026, 19449

■ Issue whereby LTE Network Analysis layers based on the carrier could not be generated using the Planet API. Case 17884

■ Issue whereby the initialization of Capesso incorrectly utilized a Mentum Planet license. Case 18344

■ Issue whereby the MapInfo Coordinate Extractor tool did not automatically load when Mentum Planet was started (when that tool was configured to be 'autoloaded'). Case 18331, 18941

■ Issue whereby the site Locate function incorrectly added all sites to a map window after being executed. This issue occurred when

22


the Locate function was executed from within a sector Group. Case 18446, 18973, 18974

■ Issue whereby CDMA Best Ec values were different depending on the layer selection chosen when network analysis was run. Case 18425

■ Issue whereby the multicast delay spread analysis layer incorrectly displayed NULL values when the values should have been '0'. Case 18593

■ Issue whereby combined predictions could not be viewed when project was stored on a network drive. Case 18869

■ Issue whereby an error message displayed when using the Best Server Recolor tool. This issue occurred when attempting to recolor server areas base on the GSM LAC or RAC properties. Case 8176

■ Issue whereby an exception was thrown when attempting to view a propagation model analysis report immediately after it had been renamed. Case 17256

■ Issue whereby project data export was considerably slower in Mentum Planet 5.1 as compared to Mentum Planet 4.5. Case 15554

■ Issue whereby survey filter results changed after opening and closing the Curves window (after first loading a filter). Case 15159

■ Issue whereby an out of memory exception was thrown on some sectors during prediction generation. This issue was intermittent and related to Windows memory management. Memory management has been optimized in Mentum Planet 5.2.1 which greatly reduces the likelihood of this problem occurring. Case 15449

■ Issue whereby predictions based on Pilot power could not be viewed. This problem only occurred on split sectors. Case 17472

■ Issue whereby an exception was thrown when attempting to generate predictions. The exception occurred in cases where the sector for which a prediction was being generated fell outside the bounds of the project geodata (but inside the bounds of the

23


model-specific geodata). This issue only occurred when using the Planet Universal Model. Case 17581

■ Issue whereby an exception was thrown when attempting to run Monte Carlo simulation (for LTE sites) using the Planet API. Case 17901

■ Issue whereby the Neighbor List and Interference Matrix tools did not respect the units specified in the Preferences window. Case 16533

■ Issue whereby the Best Serving Sector Recolor Tool did not support CDMA network analysis layers. Case 16534

■ Issue whereby LTE network analysis did not properly respect environment settings (e.g. The analysis considered clutter classes even when they were disabled within the environment settings). Case 18018

■ Issue whereby the Tabular Editor did not display the proper sites/sectors when launched from a selection of two or more sector Groups. Case 18877, 17347

■ Issue whereby the message 'invalid view layer' displayed when the Layer Statistics Analysis report window was closed. Case 16303, 16381, 16007, 16463, 16850, 18432, 19355, 19527

■ Issue whereby Mentum Planet 4.x antenna patterns did not migrate properly to Mentum Planet 5.x format. Case 14965

version 5.2■ Issue whereby the MapInfo Professional Universal Translator

tool did not automatically load even though it was configured to do so in the MBX Loader utility. Note that the MBX Loader has been renamed to 'Tool Manager' and is now found on the GIS menu (GIS>Tools). Case 11309

■ Issue whereby changes made to Data Manager file categories after a project was initially submitted had no impact. Case 13262

■ Issue whereby information stored in the Antenna Band (Min and Max) and the Electrical Tilt fields did not get updated correctly. Case 13015

■ Issue whereby the generation of merged predictions failed with an error. This issue occurred only in cases where project data was stored on a network drive. Case 1452

24


■ The 3D Viewer and the ability to create a drape file have been removed.Case 11652

■ Issue in Data Manager where locks from one user cannot be transferred to another user although the users belong to different groups but with the same project and type permissions.

■ Issue whereby the Best Serving Sector Recolor tool did not support CDMA network analysis layers.Case 16534

■ Issue whereby selecting the wrong service in the Default Network Analysis settings window disabled the option to generate a network analysis. Case 14785

■ Issue whereby an exception was displayed attempting to open the Prediction Generator. The issue occurred in cases where project propagation models (migrated from a previous version) contained improper references to 'alternate' heights and/or clutter files. Case 14883

■ Issue whereby propagation models did not get migrated. The issue occurred in cases where the propagation model file extension contained capital letters (e.g. .DPM). The migrator has been modified so that it now ignores case. Case 14358

■ Issue whereby prediction values in coincident bins were different when predictions were generated using different propagation distances. This problem only affected values of bins located at the very outer limit of the prediction generated with a smaller radius. The majority of the differences have been eliminated; however, you may still notice some small differences due to interpolation. Case 12452

■ Issue whereby the application crashed while using Tabular Editor. This occurred in cases where a column filter was applied in the Tabular Editor and one or more records contained sectors where the Site_ID contained an apostrophe. Case 14991

■ Issue whereby the display of 'unassigned' antennas took a considerable amount of time. Performance has been improved substantially in version 5.2.0. Case 15108

■ Issue whereby sector display schemes were lost after Tabular Edit or Data Manager operations. Case 3905

■ Issue whereby the application crashed when the Layer Control window was closed. This issue occurred only after a grid layer

25


was closed through Grid Manager (while the Layer Control window was open). Case 5626

■ Issue whereby prediction generation failed (the Prediction Generator just hung when operating using a wireless connection). Case 12744

■ Issue whereby the EIRP value displayed in the Site Editor window was slightly incorrect. This issue occurred only with sectors that referenced electrically downtilted antennas set up using an antenna definition file. Case 12895

■ Issue whereby the Save All option in Antenna Editor did not work properly. Case 13252

■ Issue whereby the Save option in Antenna Editor did not work properly. Case 13255

■ Issue whereby the Antenna Editor incorrectly enforced the normalization of the cross-polarization (-45) pattern. Case 13611

■ Issue whereby the message 'String was not recognized as a valid Boolean' displayed while attempting to perform Layer Statistics Analysis. Case 13724

■ Issue whereby the RSRQ network analysis layer incorrectly showed dBm as its unit whereas it should have shown dB. Case 13775

■ Issue whereby the Planet AFP incorrectly ignored interfered areas when computing frequency plans. Case 14087

■ Issue whereby the message 'Site 'XXX' contains redundancy. Entity XXX:Marconi.Wnp.RFEntities.NetworkObjects.Site already exists, duplicates not allowed' displayed when attempting to switch site sets. Case 14113

■ Issue whereby the Crystal Reports application could not be accessed from within Mentum Planet. Case 14171

■ Issue whereby the project data import action did not correctly import antenna information. This issue occurred in situations where the frequency of an antenna being imported did not match

26


the network frequencies defined in the project. Cases 14200, 15693

■ Issue whereby the Fixed WiMAX CPE Azimuth network analysis layer did not display the correct information.Instead of showing the orientation a CPE needs to have in order to connect to the best server it displayed the azimuth from the best server to the CPE. Case 14303

■ Issue whereby an exception was thrown when opening the Subscriber Settings dialog after migrating a project from version 5.0.0 to version 5.1.0. The problem occurred in cases where the service maximum and minimum data rate was 0. Cases 14315, 15602

■ Issue whereby link configuration names got truncated in the Link Configuration dialog box. Case 14361

■ Issue whereby statistics shown in the model tuning report were not accurate in some cases.Case 14877

■ Issue whereby predictions viewed at the Site level incorrectly combined sector predictions of different bands. Now, users are presented with a choice of frequency band in situations where

27


multiple bands exist on a site for which combined predictions are requested to be displayed. Case 15061

■ Issue whereby the unit for the 2nd Best Server Reference Signal Strength network analysis layer was missing. Case 15101

■ Issue whereby the some network analysis layers could not be generated using the Planet Open API. Cases 15169, 15379, 15381, 15530, 16147

■ Issue whereby the message “Item has already been added. Key in dictionary: 'Unknown' Key being added: 'Unknown'” displayed when attempting to edit a propagation model. Case 15189

■ Issue whereby data validation during project data import failed with the 'Link configuration XXX does not have sequential link budget index starting at 1'. Case 15241

■ Issue whereby the Invert Selection function did not work properly. Case 15400

■ Issue whereby the Download File option in the Antenna Editor was not functional. Case 15652, 15940

■ Issue whereby an exception occurred when attempting to clone a sector. This issue occurred in cases where the sector belonged to a Group. Case 15664

■ Issue whereby the network analysis generator window could not be minimized. This issue occurred when the “Save settings and

28


generate outputs” option in the Monte Carlo simulation window was selected. Case 15705

■ Issue whereby the message 'Raster engine was unable to display image file format' displayed when attempting to display a large network analysis layer. Case15724

■ Issue whereby cdma2000 Monte Carlo simulations could not be generated when the input traffic map unit was kbps/sqkm. Case15770

■ Issue whereby the application froze when attempting to close the Find Site tool. The issue occurred in projects where there were a large number of sites/sectors. Cases 15773, 16380

■ Issue whereby the Prediction Manager showed the Status “out of date” for sectors when the propagation distance was in decimals. Case 15782

■ Issue whereby the message 'Object reference not set to an instance of an object' displayed after selecting the 'Calculate Optimal Value' option in the PN Offset Planning tool. Case 16890

■ Issue whereby batch analysis generation failed.Case 15822■ Issue whereby group assignments were lost after switching site

sets. Case 15915■ Issue whereby project migration failed indicating that link

budget loss values were out of range. The upper limit of the allowable range has been increased to 200 dB. Case 15953

■ Issue whereby sectors configured with distributed antenna systems were not properly migrated.Case 15991

■ Issue whereby antennas were not sorted in the Tabular Editor. Case 16119

■ Issue whereby the Mentum Planet WiMAX AFPP tool stops assigning channels with no indication why. The problem occurs when using the option to keep existing channel assignments and

29


a sector has more channels assigned than the number of channels required.Case 16542

■ Issue whereby network analysis layer outputs were incorrect after removing a sector from a group.Case 16671

■ Issue whereby the area values shown in a PN Plan Analysis report did not align with the area of the Analysis Area grid used as input for the generation of the PN Offset plan. Case 11514

■ Issue whereby the MSC and BSC fields contained in a version 4.5 CDMA project were not migrated. Case 14528

■ Issue whereby projects took an inordinate amount of time to open. Performance has been improved substantially in version 5.2.0. Cases 15829, 16836

■ Issue whereby some LTE network analysis layers incorrectly displayed all NULL values. Case 16838

version 5.1.1■ Issue whereby survey assignments did not properly upload to

Data Manager when a project was synchronized. Case 13489■ Issue whereby the message ‘System.OutOfMemoryException’

displayed when generating predictions and/or when running network analysis. Typically, this issue occurred when large antenna files were required to be loaded into memory. In these cases, the operating system did not properly allocate memory required to store the antenna information. Cases 13710 and 14646

■ Issue whereby Best Pilot Ec values (for cdma2000) were not properly computed for fiber type repeaters. Case 14599

■ Issue whereby an error message displayed when averaging survey data. This issue occurred in cases where the total number of survey data points being averaged was large and/or highly clustered. Cases 13912 and 13828

■ Issue whereby an exception occurred when attempting to launch the Capesso Create Optimization Environment window from Mentum Planet. The issue was caused by the failure of Mentum

30


Planet data export functions built to support the integration of Capesso. Case 14325

■ Issue whereby the message ‘Unable to export data from Planet: Unable to convert data from Planet, the conversion utility stopped with an error: Object cannot be cast from DBNull to other types.’ displayed when attempting to launch Capesso from within Mentum Planet. This problem occurred in situations where fiber type repeaters existed in the project. Case 14610

■ Issue whereby custom data fields did not get migrated when migrated a project from mP 4.5.1 to mP 5.1.0. Case 14234

■ Issue whereby the pilot power shown in the Site Editor did not display as 100% of the PA power. This issue affected cdma2000 EV-DO carriers only. Case 14398

■ Issue whereby the Undo button in the Tabular Editor did not work properly. In cases where the Undo action was performed following a copy/paste operation to multiple cells only the first item reverted to its original value. Case 13321

■ Issue whereby the message 'The carrier standard cannot be modified through import' displayed when attempting to import network settings. This issue occurred in cases where the network settings being imported contained CDMA EV-DO carriers. Case 13703

■ Issue whereby antenna ID numbers did not match sector ID numbers following migration from mP 4.5.1. Now, when migrating from mP 4.5.1 to mP 5.1.1, antenna ID numbers will be synchronized with sector ID numbers if the following 3 conditions are met: 1) The sector ID's are numeric; 2) The first sector ID is '1'; and 3) The sector ID's are consecutive (e.g. 1,2,3...). Antenna and sector ID numbers are not guaranteed to remain synchronized following the initial migration. Case 14477

■ Issue whereby the message 'Missing antenna file "XXX.dpa" , migration aborted' displayed when migrating a project from mP 4.5.1 to mP 5.1.0. The error occurred in cases where the frequency contained in the antenna file was not in the expected format. Mentum Planet will now proceed with migration in such cases and assign a default frequency range. A message indicating

31


the problem will be reported in the log file (View>Log). Case 14401

■ Issue whereby an project that was migrated from mP 4.5.1 could not be opened in mP 5.1.0. This problem was due to failed link budget migration on several sectors. In cases where link budget values cannot be migrated, a default link budget will be applied to the sector. A message indicating the problem will be reported in the log file (View>Log). Case 14649

■ Issue whereby the message 'Error migrating dpm file 'XXX.dpm': Unsupported mdl version 37 for UM version 370 (Universal_Model_masked). Expected at least mdl version 38 Planet Universal Model version 370' displayed during project migration. The problem occurred because migration of Planet Universal Model version 370 was not properly supported. Case 14790

■ Issue whereby the message 'You must provide a name' displayed during project migration from mP 5.0.1.17 to mP 5.1.0.108. The message displayed in cases where the \project\\Profiles\General\ColorProfiles.xml file was missing some entries. In such cases, the migrator now applies default values. Case 14896

■ Issue whereby the message 'overflow error' displayed when attempting to export scan receiver data to surveys. In such cases, the export survey did not appear in the correct geographic location. The problem occurred in cases where the project network coordinate system and scanner data coordinate systems were different. The application has been updated to ensure coordinate system consistency during such operations. Case 14788

■ Issue whereby the message 'An unhandled exception was caught' displayed when importing data. The message was observed when importing Network Settings (using Replace All Data option) for a second time. This problem occurred when importing Network Settings containing CDMA EV-DO bearers. Case 15054

■ Issue whereby the message 'SystemOutOfMemoryException' displayed when attempting to re-specify the project heights and/or clutter file in Project Settings. The issue occurred in cases where the geodata file being selected was greater than 2GB in

32


size. The application will now display a warning message when selecting geodata files larger than 2GB but will not display an out of memory exception. Case 15191

■ Issue whereby the import window remains open after an data import operation is complete. Case 15154

■ Issue whereby the message “Object 'ObjectID’ has been disconnected or does not exist at the server” displays when attempting to launch the Capesso optimization tool. This problem generally occurred in cases where the project contained a large number of sites. Case 11981

■ Issue whereby the Monte Carlo simulation algorithm did not re-locate subscribers placed in invalid locations (e.g. A subscriber classified as 'deep indoor' placed in an area classified as 'open'). The simulation algorithm now attempts to re-locate subscribers until they are placed in a valid location. Case 13384

■ Issue whereby the workflow to borrow/return Universal Model licenses did not work. Case 13412

■ Issue whereby a user-specified pilot increment value in the PN Offset Planning tool was not correctly verified. Now, this value is verified and a message is displayed if the value entered is not reasonable. Case 11313

■ Issue whereby the Mentum Planet installer did not check if the computer had Microsoft .NET 3.5 installed when performing an upgrade. Now the message “.NET Framework 3.5 SP1 is required to run Mentum Planet. Please install .NET framework 3.5 SP1 and run the installation again.” displays if the .NET framework 3.5 SP1 is not installed. Case 14505

■ Issue whereby a message prompting the user to specify the location of the Universal Model license file displayed during prediction generation. A software fix has been implemented to correct this problem. Users must also ensure that the Universal Model license file (Universal_Model.lic) exists in \Universal

33


Model folder within the Mentum Planet installation folder. Case 14441

■ Issue whereby the Universal Model maritime correction factor was not being applied correctly. Case 13043

■ Issue whereby the Use an area grid option in the Network Analysis settings dialog does not properly restrict analysis output layer coverage. Case 15366

■ Issue whereby survey files did not display in Project Explorer after project was synchronized with Data Manager. Case 13489

version 5.1This section lists the known issues and limitations that have been resolved in release 5.1 of Mentum Planet.

■ Issue whereby the antenna tilt conventions used in the Site Editor did not match the tilt convention used in the Data Manager. By default, antenna downtilt is now shown as a positive value in both the Site Editor and the Data Manager. Antenna uptilt is shown as a negative value. Case 10715

■ Issue whereby the message 'Internal error. Nullable object must have a value' displayed during a Monte Carlo simulation. The issue occurred in situations where no subscribers were generated during the simulation (based on the traffic distribution). Mentum Planet now provides proper messaging in this situation to notify the user of the problem. Case 11019

■ Issue whereby values shown in the Average Downlink and Uplink Data Rate by Served Subscriber columns in the WiMAX Throughput - Sector/Channel were incorrectly the same. Case 11162

■ Issue whereby the message 'The given key was not present in the dictionary' displayed when attempting to access Subscriber Settings. Case 11294

■ Issue whereby the Find Maximum Point tool was not functional. Case 11532

■ Issue whereby location coordinates displayed in the Point-to-Point Profile tool did not respect specified unit preferences

34


defined in the User Preferences dialog box (Edit ➤ Preferences). Case 11529

■ Issue whereby the message 'An unhandled exception was caught. External component has thrown an exception' displayed when attempting to use the Draw Angle tool. Case 11523

■ Issue whereby the message 'An unhandled exception was caught. External component has thrown an exception' displayed when attempting to use the Angle From Line tool. Case 11522

■ Issue whereby the Detach From Data Manager Project option in the Data Inspector utility was incorrectly disabled. Case 11799

■ Issue whereby network analysis did not proceed when warning messages displayed. Mentum Planet now writes warning messages to the Planet log file and proceeds with network analysis. This issue occurred when using the Universal Model. Case 11565

■ Issue whereby the message 'Error 55554' displayed when performing model tuning. Case 12975

■ Issue whereby the message 'An unhandled exception was caught. GetBandsAndElectricalTiltValues(), Antenna does not exist' when using the Point-to-Point Profile tool. This issue occurred in cases where the Mentum Planet default antenna pattern (default.paf) did not exist in the project folder. Cases 12239 and 12169

■ Issue whereby the option to display interference did not exist on the sector shortcut menu in Project Explorer. Case 10918

■ Issue whereby differences existed between signal strength predictions generated in Mentum Planet 4.5 versus Mentum Planet 5.0. These differences existed when using the CRC-Predict propagation model only. Case 12610

■ Issue whereby the message 'An item with the same key has already been added' displayed when attempting to generate

35


predictions based on an antenna with polarization set to 'Dual'. Cases 12622, 13115, 13558

■ Issue whereby the distribution of preambles assigned by the WiMAX Preamble Planning tool were not equivalent. Case 12627

■ Issue whereby the labelling of antennas in the Antenna Editor did not appear correctly when a remote electrical tilt (RET) value of 0.1 was used. Case 12888

■ Issue whereby the message 'Raster engine was unable to recognize image file format' displayed when attempting to open an image file. Cases 13160, 12389, 13459

■ Issue whereby the message 'Object reference is not set to an instance of an object' displayed when attempting to refresh the Project Explorer. Case 13292

■ Issue whereby the WiMAX Composite Coverage analysis layer was incorrect when the Uplink Coverage Required option for Best Server Selection (preamble C/(N+I)) was enabled. Case 13263

■ Issue whereby the message 'Cannot find column XX' displayed when the Tabular Editor was opened and some of the data sheets were unselected. Cases 13436 and 12271

■ Issue whereby the message 'The given key was not present in the dictionary. Before continuing with the Site Editor, you must resolve this issue' displayed when opening the Site Editor. Case 13549

■ Issue where by the message 'Internal error' displayed when generating a Monte Carlo simulation based on LTE sites. Case 13538

■ Issue whereby flag conditions were truncated during migration from version 4.5 to version 5.1. Mentum Planet now supports the

36


migration of flag conditions with up to 30 characters. Case 13656

■ Issue whereby you could not copy and paste a blank field value in the Tabular Editor. Case 12140

■ Issue whereby color profiles could not be assigned to analysis layers. Case 12260

■ Issue whereby the status bar did not close following the completion of project migration. Case 11296

■ Issue whereby the WiMAX Composite Coverage analysis layer displayed incorrect results when using the 'Uplink Coverage Required' option in the Best server selection based on section on the Analysis tab in the WiMAX Analysis Settings dialog box. Case 13263

■ Issue whereby the message 'A value is not in the range. Invalid bandwidth value 0.000000 for network BandName. Bandwidth has been set to 1.25' displays when the Capesso optimization tool is launched. This problem occurred in cases where carriers had the same center frequencies. Case 13578

Known issuesThe following list details important issues that are known to exist at the time of this release. These issues are being actively tracked and managed, and we expect to resolve them in the near future. These issues will be addressed as we progress through the software development and testing process.

■ Issue whereby the error index was out of range. Must be non-negative and less than the size of the collection' displays when attempting to generate a WiMAX frequency and preamble plan. This problem occurs in cases where the number of required channels for a given sector is less than the number of allocated channels. To workaround the problem, ensure that the number of required channels is equal to or greater than the number of initially assigned channels. Case 19243

■ Issue whereby Sector Display Schemes sometimes shade sectors with the incorrect color. There is no known workaround for this issue.Case 19277

■ Issue whereby an out of memory exception is thrown when attempting to contour a grid. This problem occurs in cases where

37


the grid is very large. To work around the issue, trim the grid into smaller pieces and/or resize it to a coarser resolution before contouring it. Case 17659

■ Issue whereby default network analysis settings are not migrated. Following migration, you must review and update your default network analysis settings. Case 18833

■ Issue whereby changing a sectors antenna assignment in the Tabular Editor takes a long time. This issue occurs in cases where the number of sectors loaded into the tabular editor is large. Case 17579

■ Issue whereby the antenna editor does not respect unit preferences defined in the Preferences dialog. Case 17334

■ Issue whereby an 'out of memory' error message displays when running Monte Carlo simulation. If you encounter this issue it may be resolvable through the configuration of some advanced configuration settings. Please contact Mentum Customer Care for assistance. Case 18487

■ Issue whereby creating a site subset based on a sector Group can take a considerable amount of time. The actual time is dependent on the number of sites/sectors within the Group. Case 15828

■ Issue whereby sector Groups are not sorted alphabetically in some application dialogs (e.g. Sector Display Schemes, Network Analysis, Neighbor List Tool etc...). Case 19223

■ Issue whereby the site name property cannot be changed directly in the Site Editor. This problem occurs when user is trying to change only the case of one or more characters in the site name (e.g. Changing the name 'Downtown' to 'downtown'). To workaround this issue, change the name to something different (e.g. 'downtown1') then to the desired name (e.g. 'downtown'). Case 19021

■ Issue whereby typing characters in the antenna list box (in Antenna Editor) does not move cursor focus to the correct item. For instance, if you type the characters 'B', 'R', 'X' in succession you would expect cursor focus to move to the first antenna that has a name beginning with the characters 'BRX'. Instead, the cursor focus moves to the first antenna that has a name beginning with the character 'X' (the last character typed). Case 19019

38


Known limitationsThe following list details limitations that are known to exist at the time of this release.

■ The Microwave Link Planning User Guide is not available at the time of release. It will be posted on the Mentum web site and customers notified once it is available.

■ The WiMAX Getting Started Tutorial is no longer installed with Mentum Planet. Contact Customer Care to obtain a copy of the tutorial as well as the associated dataset.

■ In order to import iBwave projects you must install the iBwave viewer.

■ The 'Use numeric grid' option in the Layer Statistics tool is designed to support grids with positive values. Statistics calculated based on grids with negative values will be incorrect. Case 17732

■ When viewing Bing Maps layers, a shift may occur in the grids and tables displayed on the map. To alleviate this effect, set the “Reprojection” to “Optimized”. To access this setting, select Map Options from the Map menu and click on Image Processing.

■ Sector symbol azimuths do not consider eAzimuth. Case 19207■ In Mentum Planet, traffic values are stored with 2-byte

precision. This means that traffic maps can utilize a maximum of 65 536 discrete values. If the actual range of traffic density values exceeds this number, the density values will be scaled to fit within the 2-byte range. For any given area, this means that it may not be possible to assign the bins within that area uniform traffic density values. Instead, in order to preserve the total amount of traffic within that area, it may be necessary to assign different traffic values to the bins within the area. In all cases, assigned traffic values will be a multiple of the 2-byte interval calculated through the scaling process. A 'speckled' pattern may be evident if colors assigned to density values in adjacent bins are different.Case 19072

■ When generating a traffic map based on region data, the maximum number of regions you may have is 65534. If your region files contains more than this number of regions you must

39


break it into parts and perform traffic map generation separately for each region file. Case 17030

■ When migrating Universal Models from Mentum Planet 4.5, the geodata files used by the models may need to be manually adjusted because after migration Universal Models are set to only use the project's heights and clutter files (i.e., additional heights, clutter, clutter heights, polygons, and railway tracks files are not selected by default).

■ When migrating Universal Models from Mentum Planet 5.0, 5.1, or 5.1.1, the geodata files used by the models may need to be manually adjusted because after migration Universal Models are set to only use the project's heights and clutter files (i.e., additional heights, clutter, clutter heights, polygons, and railway tracks files are not selected by default).

■ When generating propagation model analyses, surveys must be in either:

■ Lat/Long (WGS 84, or NAD 83, or GRS80), in which case the first column name must start with “long” or “x”, or “lat” or “y”.

■ The coordinate system of the Heights file, in which case, the first column name should not start with “long”, “x”, “lat” or “y”, but instead the first column must contain X coordinates, and the second column must contain Y coordinates.

■ When generating propagation model analyses, an “out of memory” exception may occur when saving large analyses. If such an error occurs, reduce the number of “distances” in the analyses settings. Network analyses generated in Mentum Planet version 4.x are not accessible from the Project Explorer in version 5.2. These analysis files can be found in the /ProjectName/Obsolete folder (in appropriate technology-dependent sub folder).

■ The message 'Marconi error #401' displays when attempting to export a large grid file to MapInfo Tab format. This error occurs in cases where the resultant Tab file would exceed the 2GB maximum size. Case 15521

■ The workflow of connecting a single local project to multiple Data Manager projects is not supported. If such a workflow is

40


attempted a warning message will be displayed. Cases 8601, 8700, 8701

■ Propagation model file are not automatically updated when the class structure of the clutter file they reference changes. You must open the model in the propagation model editor and add/modify the class structure, as required. Case 16681

■ The CRC Predict Air propagation model is not supported in Mentum Planet 5.2.1. This model will be supported in Mentum Planet version 5.3. Case 12059

■ The Prediction Generator dialog does not indicate whether a prediction for a given sector is 'merged' as it did in Mentum Planet 4.x. The reason for this is because, in Mentum Planet 5.x, individual rows in the Prediction Generator represent sites rather than sectors. The sectors on a given site may include a mix of modelled and merged predictions which would require different status indicators. If the status displays as 'OK' that means that all predictions for sectors on the site have been generated (either as type modelled or merged). Case 14789

■ Sector location offset values may vary slightly after migration from mP 4.x to mP 5.x due to differences in how the values are computed between versions. These differences should have no significant impact on the accuracy of predictions. Case 14464

■ On migration from Mentum Planet 4.x to Mentum Planet 5.1.1, combined antennas are not automatically converted to split antennas. The current migration rules are in place to ensure predictions generated in mP 5.1.1 are the same as those generated in mP 4.x. This would not be the case if combined antennas were automatically converted to split antennas. Case 14678

■ To use Mentum Planet 5.x, the language of your operating system and locale must be set to English. To verify this setting, open the Regional and Language Options dialog box from the Control Panel and select one of the English language choices on the Regional Options tab.

■ The supplied default Planet General Model was initially tuned for a specific frequency and market. For best results, you should modify the model settings to better reflect the location of interest. This is true for all propagation models.

41


System requirements for workstationsThe tables below detail the workstation configurations for Mentum Planet. For system requirements for application servers, see the Installation Guide.

Requirements vary depending on the layout of the network, the number of sites, and the work practices you adopt.

Minimum configuration

This configuration is suggested for networks up to 3 000 sectors. You can work with larger networks using this configuration but performance may be impacted.

Processor Workstation: Single Core Intel CPU (e.g., the Celeron 440, 2GHz clock) or equivalent

RAM 2 GB

Hard disk At least 20 GB free space

Display SVGA (16-bit), 1280x1024

Operating System Windows XP Professional (English Edition), Windows 7 (English Edition),Some Automatic Updates can cause your computer to reboot, which may interrupt operations in Mentum Planet. It is recommended that you modify the Automatic Updates settings so that they are not done automatically.

Required Software In order to use the Mentum Planet Import/Export tool, you must have Microsoft Excel 2000 or greater installed. In addition, you must have Adobe Reader installed to view the Mentum Planet user documentation.

Recommended configuration


Processor Workstation: Intel Core-2 Duo 2GHz or Dual-Core-2 Extreme or equivalent

RAM 2 GB

Hard disk A quick SATA model - 50 GB free space


42


Operating System Windows XP Professional (English Edition), Windows Vista (English Edition), Windows 7 (English Edition)Some Automatic Updates can cause your computer to reboot, which may interrupt operations in Mentum Planet. It is recommended that you modify the Automatic Updates settings so that they are not done automatically.


Optimal configuration


Processor Workstation: Intel Core-2 Quad 2.83 GHz or Intel Core-i7 or equivalent

RAM 4 GB

Hard disk A quick SATA or SCSI model - 200 GB free space


Operating System Windows XP Professional (English Edition), Windows Vista (English Edition), Windows 7 (English Edition)Some Automatic Updates can cause your computer to reboot, which may interrupt operations in Mentum Planet. It is recommended that you modify the Automatic Updates settings so that they are not done automatically.


An Internet connection is required to validate licenses. If there is no Internet connection, you can complete the offline registration form and

email it to Customer Care.

To run Mentum Planet, you must be a member of the “Power Users” group at a minimum. Regular “Users” must be granted write access

privileges to the <Mentum Planet installation> folder to run Mentum Planet.

Recommended configuration

43


Mentum Planet runs on the Microsoft .NET framework (version 3.5). If you do not have this software installed on your computer, you must download and install it from the Microsoft web site.

DocumentationMentum Planet includes an extensive array of resources that will help you use the software effectively. This includes user guides, technical notes, “What's this?” Help, “How to” Help, and a comprehensive glossary. For complete details, refer to the Resource Roadmap accessible from the online Help.You can access Help from within Mentum Planet in two ways:

■ Choose Help ➤ Help Topics ➤ Planet.■ By pressing the F1 key from within any Mentum Planet dialog box.

All tasks and information required by the RF engineer to plan and optimize a network using Mentum Planet is contained in the online Help. Online Help is available from all dialog boxes as well as from the Help menu. User Guides are also available in print-ready PDF format and are accessible from the online Help. In addition, you can access the Customer Care Knowledge Base directly from the Online Help by clicking the Knowledge Base button on the toolbar.

Getting helpIf you have any questions or concerns, contact our Customer Care Centers.You can get technical support by phone or email, or by visiting the Self-Service Portal on the Mentum website at http://www.mentum.com/index.php?page=customer-care&hl=en_US.

North AmericaPhone: +1 866 921-9219 (toll free), +1 819 483-7094 Fax: +1 819 483-7050Email: [email protected]: 9am – 7pm EST/EDT (Monday-Friday, excluding local holidays)

Windows XP 32-bits or 64-bits and Windows Vista 32-bits or 64-bits are supported.

For information about system requirements for the Data Manager Server, see the Data Manager Server Administrator Guide.

44

http://www.mentum.com/index.php?page=customer-care&hl=en_US

http://www.mentum.com/index.php?page=customer-care&hl=en_US

mailto:[email protected]


Europe, Middle East, and AfricaPhone: +33 1 39264642 (Paris)Phone: +46 706 27 06 81 (Stockholm)Fax: +33 1 39264601Email: [email protected]: 9am – 6pm CET/CEST (Monday-Friday, excluding local holidays)

Asia PacificPhone: +852 2593 1287Fax: +852 2593 1234Email: [email protected]: 9am – 6pm HKT (Monday-Friday, excluding local holidays)

When you call for technical support, ensure that you have your product ID number and know which version of the software you are running. You can obtain this information using the About command from the Help menu.When you request technical support outside of regular business hours, a Product Support Specialist will respond the next working day by telephone or email, depending upon the nature of the request.

45




46

Mentum Planet Release Note

Documents

Transcript of Mentum Planet Release Note