Escolar Documentos
Profissional Documentos
Cultura Documentos
Note
version 5.4
Copyright 2012
Mentum 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, Mentum Fusion, Mentum CellPlanner, and
Mentum LinkPlanner are registered trademarks owned by Mentum S.A. MapInfo
Professional is a registered trademark of PB MapInfo Corporation. iBwave 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 on March 21, 2012
Introduction
This document accompanies the release of Mentum Planet 5.4. It describes the new
features and enhancements contained in the release. It also contains a list of the
issues that have been resolved in this release as well as a list of known issues and
limitations.
This document contains the following information:
n
Issue resolutions
Known issues
Known limitations
System requirements
Documentation
version 5.4
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
multi-band antennas.
multi-beam antennas, used in single sector or multi-sector
configurations.
electrical tilt, azimuth, beamwidth.
remote control units.
explicit definition of antenna ports
polarizations, including cross-pole and quad-pole.
a 3D antenna viewer was implemented.
Support for multi-band network analyses and Monte Carlo simulations for
WiMAX, LTE TDD and LTE FDD.
For fixed subscriber analyses, it is now possible to force a given
subscriber to be served by a specific sector, as opposed to assuming that
the subscriber is always served by the optimal sector.
Mentum Cell Planner GSM projects can be migrated to Mentum Planet 5.4.
TEMS Route Reader 7.0 is integrated with Mentum Planet 5.4, in order to
allow the import of native-format TEMS Investigations files.
The Installation Guide has been renamed the Getting Started Guide and
now includes a section on basic usage.
You can now access Technical Notes, as well as User Guides, from the
Help menu.
The average power per physical resource element has been slightly
modified. It now represents the average power over all the physical
resource elements of the frame.
Support for polarization in antenna definition files.
The co-installation of Mentum Planet 5.4 and either Mentum Planet 5.3.X
or 5.2.X is supported.
A new Start Page is available where you can view the latest Mentum
news as well as open a project or create a new project.
You can now access the training schedule and news from the Help menu.
New About dialogs for Mentum Planet and the Mentum Planet Migrator.
version 5.3.2
n
You can now edit neighbor plans using the Neighbor Plan Graphical Editor.
The neighbor priority and distance are now displayed in the Site Editor.
Case 25550, 25999
The neighbor list merge function has been enhanced. Now, when you
merge, the current neighbor priority of a sector is maintained and
neighbors (from the neighbor plan) that do not currently exist in the
neighbor list of a sector are added at the bottom (e.g., with the lowest
priority level). Case 25996
You now have the ability to add/remove neighbors from a sectors
neighbor list by clicking sectors displayed in a Map window. Case 25997
You now have the option to force neighbor mutuality. For instance, if
sector A has three neighbors (sectors B, C and D), clicking the Add All
Mutual Neighbors option will ensure that sector A is on the neighbor list of
sectors B, C and D. Case 25998
You now have the ability to sort neighbors in the Site Editor. by distance.
Case 26000
Support for EV-DORev. B has been added. EV-DO Rev. B provides you
with the ability to use the 64-QAM modulation as well as to aggregate
data rates on multiple carriers.
It is now possible to have cells of different EV-DO revisions in the same
Mentum Planet project.
The Planet API now supports the following functions: Case 25265
n
n
n
n
n
version 5.3.1
n
You now have the option of creating a new antenna system when a
sector is cloned. To enable this setting, check the Create New Antenna
System on Cloning Sector option on the Miscellaneous panel in the User
Preference dialog box. Case 21320
In previous versions of Mentum Planet, the Physical Cell ID Planning tool
reserved PCIDs that were considered for all sectors regardless of
whether they already had an assigned PCID or not. Now, you have the
option of applying reserved PCIDs to all sectors (previous behavior) or
only to sectors that do not already have a PCID assignment. Case 21023
An impersonation option has been implemented that allows the RPE
service to be configured to use the client's credentials to obtain access
to the necessary objects. This feature resolves issues whereby
predictions could not be generated when the application was operated in
a Citrix environment in cases where the account under which the Planet
Radio Propagation Engine (RPE) service operated did not have the
required access rights. For more information, contact Mentum Customer
Care. Case 22745
version 5.3
n
n
n
n
n
n
n
n
n
n
n
The scanner survey data import now supports of TEMS_LOG files (for all
technologies).
Migration of WCMDA/HSPA, LTE FDD and LTE TDD Mentum Cell Planner
projects to Mentum Planet.
Ability to select sectors to be modified upon import of data with the
import/export tool.
Mentum Planet now supports the import of Cell Planner 10.0 projects.
n
n
Project Explorer now enables you to filter sites and antennas directly in
the data window.
Traffic Map Generator redesign:
n
n
You can now create a traffic map from a fixed subscriber table.
You can now quickly and easily compare site set data to network data.
You can also compare two site sets.
Ability to compare data when importing data with the Import/Export
tool.
Interference matrix generation algorithms:
n
n
n
You can now define base station types in the network settings that
encompass the modulations supported as well as the neighbor plan
criteria.
Single Site Optimization tool that allows for the optimization of antenna
configurations for a single Base Station. This tool is available for all the
technologies supported in Mentum Planet. In the Single Site
Optimization tool, you can also directly visualize the impact of
parameter changes, by displaying signal strength and C/(N+I) grids.
These grids are automatically updated when you change antenna
parameters.
A new Carrier Code display tool is available for all supported
technologies for better visualization of carrier (or channel) reuse, color
code (e.g., PCID, scrambling code, PN offset) reuse, and neighbor list
relationships.
Mentum Planet now includes the Predict -Air propagation model, which
you can use to model high-altitude (aircraft-to-ground) communication.
It can also be used when you want to define an AMSL receiver height.
Support for the co-existence of Data Manager Server 5.4 with other
versions of Data Manager Server.
The commands on the Tools menu have been re-organized with the
introduction of a new Optimization menu.
Option to generate FCC contours based on PA power. Case 4572
The 'Save settings and generate output' option is now the default option
in the Network Analysis Wizard. Cases 19005, 22551
Ability in the WiMAX AFPP to keep existing Preamble assignments when
Preambles are defined on a per-channel basis.
The Antennas tab in Tabular Editor (and in a file exported to MS Excel)
now contains a new column that identifies the sector(s) which reference
a given antenna. Case 19525
The Select tables to import panel on the Project Data Import Wizard now
provides a horizontal scroll bar to allow you to adjust the view to read
long table names. Case 20531
You can now enable/disable the additional layer options (Project
Settings>Advanced Options) using Mentum Planet API's. Case 19824
You can now modify file path names (Project Settings>Folders) using
Mentum Planet API's. Case 19825
To improve performance, you can store only location information in the
site table.
The patch version is now displayed in the About Mentum Planet window
(accessible from the Help menu). Case 4572
A View Antennas function has been added to the Site Node in Project
Explorer. This option allows you to display connecting lines between site
and antenna locations. Cases 18480, 19866, 20464, 20796, 22210
The Edit Site tool now remains enabled once activated until another user
interface control is activated. Previously, that tool needed to be reenabled after each use. Case 3483
A read-only sector ID field was added in the Antennas tab of the Tabular
Editor and in the Excel spreadsheet exported by the Import/Export tool.
Upon project creation, the Antenna Algorithms defined in the <Mentum
Planet Installation>\Global folder are used instead of hard-coded
antenna algorithms.
performance improvements
support for indoor to outdoor de-penetration
improvements in the horizontal plan propagation estimation
improved modeling of propagation with elevated structures
(e.g., bridges).
Select All/Unselect All buttons have been added to the Bearers tab in the
Equipment Types section in the Subscriber Settings dialog box. Case
14211
The Point-to-Point Profile tool now provides an option to identify
transmitter and receiver sites using a distance filter. Case 13842
version 5.2.1
n
n
n
n
MapInfo 10.5
n
n
n
n
TDD de-synchronization
n
n
LTE enhancements
n
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, rightclick on an existing sector and select 'Clone'. All 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.2
In version 5.2 of Mentum Planet, the following new features and enhancements have
been included:
n
n
n
n
n
n
n
n
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
version 5.1.1
n
n
n
version 5.1
n
n
n
n
version 5.0.1
n
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
ReferenceC/(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
n
Support for WiMAX and LTE networksdetailed modeling of OFDMA airinterfaces and support for Advanced Antenna Systems (AAS)
Ease of useredesigned user interfaces, easy-to-use tabular editors
and new site management features
Better scalability and stabilityability to handle larger networks within
a single project due to a reduced memory footprint and improved
memory management
Future-proof platformready for on-going evolution of radio access
networks including OFDM technologies and advanced antenna systems
Improved APIsopen antenna format and API with support for
advanced antennas; improved iecon performance, and new APIs
available
Better performanceimproved performance in user interfaces, datarelated actions and import/export functions; furthermore, Mentum
Planet 5.0 includes a new prediction engine that generates predictions
faster than previously
MapInfo Professional 9.5.1Mentum 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:
n
n
n
n
n
Minor improvements
n
Support for 3D antenna diagrams in the Planet General Model and CRCPredict 4.0 propagation models.
Mentum Planet includes the Measurement Data Package, which
encompasses the following features:
n
Site management
Mentum Planet introduces a new Site Editor that facilitates the site management
workflow with an intuitive and easy-to-use interface.
n
Data management
Mentum Planet includes an advanced data management system including:
n
Other enhancements
The Mentum Planet release includes other new features including:
n
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:
n
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
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 Resolutions
The following issues have been resolved in this release:
version 5.4
n
Issue whereby the message 'Cannot find table 0' displayed when
attempting to import network data in Microsoft Excel format. The
problem occurred in cases where the name of the worksheet being
imported began with a number. Case 15830
Issue whereby the message 'Antenna coordinate system is not the
same as DEM coordinate system' displayed when attempting to run
network analysis. This issue occurred in cases where the project
geodata was changed and the new geodata had a different coordinate
system than the original geodata. Case 17034
Issue whereby local attachments were deleted after disconnecting from
Data Manager. Case 17898
Issue whereby the snap option did not function properly when creating a
new site using the Place Copy function. Case 18110
Issue whereby the message 'Error: Index was out of range. Must be
non-negative and less than the size of the collection' displayed when
attempting to generate a WiMAX frequency and preamble plan. This
problem occurred in cases where the number of required channels on a
sector was less than the number of allocated ones. Case 19243
Issue whereby the message 'Error opening filtered grid' displayed when
attempting to generate contours using the Smooth Contouring Tool.
Case 19751
Issue whereby the right-click (shortcut) menu is disabled when
accessed from the heights or clutter node in Project Explorer (Project
Data>Geodata). This problem occurred when the Layer Control window
was open and un-docked. Cases 21356, 21416, 22229, 28932
Issue whereby the Layer Statistics Analysis tool produced incorrect
results under certain conditions. The problem occurred in cases where
one or more grids being used as input were not properly aligned. Now, a
warning is shown when loading a project or when attempting to change
your project geodata to alert you to the fact that your data is not
properly aligned. If your data is not properly aligned you should contact
your geodata vendor to have it corrected. Case 21358
n
Issue whereby the Tabular Editor displayed files with text file (.txt)
extensions in the available propagation model list. Case 25289
Issue whereby the message 'Unable to open table' displayed when
attempting to display a prediction layer. The issue occurred in cases
where the site name contained Unicode characters. Unicode characters
are now supported for the following propagation models: PGM, PGM-A, Q9
and Longley-Rice. They are not supported for Predict 4 and Universal
Model. Cases 25185, 29231
Issue whereby the migration of a Mentum CellPlanner 10 WCDMA project
failed when a description field contained more than 255 characters. In
version 5.4.0, descriptions longer than 255 characters will be truncated to
255 characters during migration and a warning message will display.
Issue whereby an exception occurred during LTE FDD network analysis
when the 'Interference Coordination' analysis layer was selected. Case
25380
Issue whereby the message 'Propagation Model Analysis: An error
occurred while trying to compute the analysis. The error is: Vector File
too large => nbrecord (109975) > 100000 items' displayed when
attempting to generate a new propagation model analysis. Case 25312
Issue whereby the message 'Agilent error while dumping AOD file:
<FileName>' displayed while attempting to import an LTE AOD file. Cases
24660, 24457
Issue whereby the pilot power value associated to EV-DO sector-carrier
as displayed in the Tabular Editor was incorrect and not equal to the PA
power value. Case 25521
Issue whereby the message 'Exception of type
'System.OutOfMemoryException' was thrown" displayed when
attempting to run LTE Monte Carlo simulation. Memory management
improvements have been implemented in 5.4.0 that greatly reduce the
possibility of such an exception occurring. Case 25782
Issue whereby data exported based on a sector Group contained sectors
that were not in that Group. Case 25783
Issue whereby Fixed Subscriber Analysis results were missing from the
Microsoft Excel results file. This problem occurred in cases where the
'select prediction at CPE antenna height level' option was selected. Case
25918
n
Issue whereby the unit uses for MIMO B in the Microsoft Excel Fixed
Subscriber Analysis report incorrectly showed as dB instead of as a
percentage. Case 25919
Issue whereby the Project Explorer behaved erratically. This included
problems with scrolling operations, problems opening/closing groups
and issues with cursor movement. Changes implemented in version 5.4
make these issues much less likely to occur. Cases 25967, 26516,
26517,26584,26587, 26967,25698, 26963, 26637, 25294,27347,27618,
29251
Issue whereby the application hung when left idle for a while. This
problem occurred in cases where the user entered some characters in
the Sites filter in Project Explorer and then immediately changed the
focus to another application. When they returned the focus to Mentum
Planet they found the application had 'frozen'. Case 26684
Issue whereby changes made to a site's properties were incorrectly
being reflected in a copy of that site. Case 26162
Issue whereby the message 'GSM_Sectors Table: Sector <SectorID>
has invalid value' displayed when project data was being imported. The
problem occurred in cases where the GPRS Maximum Supported Coding
Scheme and EGPRS Coding scheme was blank for some sectors on the
import sheet. Case 26174
Issue whereby the message "<ModelName>. Internal error. There are
not enough 'float' parameters in the model for parameter
'OutputResolutionMeters'" displayed when propagation models were
being migrated. Cases 26226, 27087
Issue whereby the Tabular Editor did not allow you to allocate MAIO's
and HSN's when the FH type was set to BBH. Case 26294
Issue whereby the GSM Worst Offender C/A network analysis layer
failed to account for the adjacent channel interference rejection factor
and therefore did not show the correct values. Case 26316
Issue whereby the message 'sites locked by n/a' displayed
Unexpectedly in Data Manager. Case 26356
Issue whereby TDMA network analysis failed when one or more sites
considered for the analysis contained a period character in their name.
Case 28138
Issue whereby applying site selection changes (site activation or site
deactivation) did not always function properly. Case 28154
Issue whereby an antenna query based on central frequency wrongly
excluded some antennas from the results. Case 28155
Issue whereby the ACP site selection algorithm did not activate the
correct number of sites under given conditions. Case 28156
Issue whereby the message 'Index was outside the bounds of the array'
displayed when attempting to generate CDMA network analysis layers.
The problem occurred on projects that were migrated from a previous
version. Cases 28064, 28981
Issue whereby the number of subscribers indicated in the
Subscribers>Global report for WCDMA Monte Carlo simulations was
incorrect. Case 28284
Issue whereby the file generated when viewing a survey transmitting
location did not get stored in the project folder. Case 28255
Issue whereby the message 'UM: Memory allocation failure' displayed
when attempting to generate predictions using Universal Model. This
problem occurred in cases where the antenna correction option in the
model was enabled. Cases 27947, 28916
Issue whereby the application crashed when attempting to run batch
project migration. Case 28638
Issue whereby the message 'Warning: Unable to delete directory
<ProjectFolder\...\ColorCodePlanning>' displays when attempting to run
batch project migration. Case 28635
Issue whereby grid creation using interpolation was not possible (e.g. The
process failed with multiple error messages). Case 28595
Issue whereby the formula used to compute the number of control
channel resource elements for LTE FDD was incorrect. Case 28760
version 5.3.2
n
version 5.3.1
n
Issue whereby the message 'Please enter a value within the range [200,200]' displayed when adjusting PA power values even though the
value entered was within that range. Case 23846
Issue whereby Data Manager user group assignments were lost when the
Data Manager was re-started.
Issue whereby an exception was thrown when attempting to import TEMS
Investigation log files. The issue was detected on Windows XP 32-bit and
64-bit operating systems.
Issue whereby the free space loss curve in the survey regression tool
did not properly account for changes to the frequency parameter. Case
24297
Issue whereby the message 'Project cannot be loaded. There are no
licenses available for <technology type>' displayed upon project
opening. Case 24516
Issue whereby the Universal Model Horizontal Propagation option did
not remain enabled upon re-opening the model settings dialog box. Case
24792
Issue whereby the message 'Copy of <SiteName> failed: An item with
the same key has already been added' displayed when attempting to
generate predictions. The problem occurred in cases where the geodata
grids had negative eastings values. Cases 24723, 24608, 24790
Issue whereby the affected area values shown in a histogram
interference matrix were incorrect. This problem occurred in cases
where the interference matrix was generated based on service
probabilities. Case 24850
Issue whereby the message 'Prediction Post Processing failed for
<*>.ppf: Reading header data failed' when attempting to generate
predictions based on the Predict-Air propagation model. Case 24713
Issue whereby mobile allocation lists (MAL) containing carriers
(ARFCNs) from different sub-bands could not be imported. Case 24281
Issue whereby the cdma2000_Carrier_Antennas worksheet was missing
when project data was exported using the import/export tool. Case
24704
Issue whereby RSRP and RSRQ values for subscribers blocked because
of reference coverage were incorrect. Case 22673
version 5.3
n
Issue whereby map display did not update when a new sector was added
to a site in the Site Editor (e.g. newly added sector did not display in map
window). Case 13733
Issue whereby the application did not recognize predictions as valid when
the frequency band assigned to a sector changed. Case 14588
Issue whereby Prediction Manager did not consider filters based on Flags
or Groups. Case 16115
Issue whereby the Zoom Automatically on Viewed Site Selection option
did not function properly. Cases 16565, 21010, 24196
Issue whereby the creation and/or activation of site sets took a long
time. Performance in this area has been greatly enhanced in version
5.3.0. Cases 15828, 18165, 19896
Issue whereby an out of memory error displayed when attempting to
export to survey a scanner data file.Cases 17410, 19915
Issue whereby the Layer Statistics Analysis tool computed statistics
incorrectly when the input data layer contained negative values.Case
17743
Issue whereby the unit type selection list in the Grid Import tool was
incomplete. Case 18360
Issue whereby the migration rollback function did not work properly. Case
18346
Issue whereby the antenna file drop-down control in the Site Editor did
not take advantage of the auto complete option. Now, when you type
characters in this control, the list will scroll to the list item matching the
characters you have typed. Case 19019
Issue whereby you could not change the case of a character in the site
'Name' field in the Site Editor. For example, you could not change the site
name from 'Site_1' to 'site_1'. Case 19021
Issue whereby the Best Ec threshold value defined in the cdma2000
default analysis settings dialog was not properly migrated. During
migration, this value was improperly reset to the Mentum Planet default.
Case 18833
n
Issue whereby the message 'The server is not available. Verify the
Internet connection and try again' displayed when attempting to
download an antenna from the Mentum Antenna Server. Case 20601
Issue whereby the terrain height for repeaters incorrectly displayed as '999'. Case 20809
Issue whereby the message 'verticalBoresightDegree element is invalid'
displayed when attempting to load an antenna pattern. Case 20894
Issue whereby the message 'Cannot read coordinate system category'
displayed when attempting to create a new project. The problem occurred
when running Mentum Planet using the Japanese locale operating system
settings. Case 20630
Issue whereby an exception occurred when attempting to export project
data. The problem occurred in cases where an equipment type being
imported did not have a band assignment or if the bands assigned did not
exist in the project. In such cases, the first band for the technology of the
equipment type is assigned. Case 20998
Issue whereby the Mentum Planet application window hides itself after
carrying out certain actions (e.g. closing a dialog box, viewing predictions
etc...). Case 21018
Issue whereby shortcut (right-click) menu options in Project Explorer
were incorrectly disabled when the Layer Control window was floating.
Cases 21326, 21416, 22229
Issue whereby a the Flags or Groups map layer disappeared after
changing the network coordinates system. Case 21012
Issue whereby FFR usage values as displayed in the Site and Tabular
editors were inconsistent (e.g. In Site Editor FFR usage values displayed
as 20% whereas the same value displayed as 0.2% in the Tabular Editor).
Case 21367
Issue whereby traffic options incorrectly appeared in the TDMA/FDMA
Network Analysis Wizard. Case 21577
Issue whereby BCCH carrier numbers were not properly updated after
being imported. The problem occurred in cases where frequency hopping
was set to synthesized or baseband. Cases 21689, 22487
Issue whereby the Data Manager 'Display Differences Only' filter did not
function correctly. Cases 21659, 23209
Issue whereby project migration between version 5.2.0 and 5.2.1 was
very slow. Changes have been implemented in version 5.3.0 that greatly
improve performance in this area. Case 21749
Issue whereby statistics could not be generated based on .csv type data
imported using the Network Data tool. Case 21898
Issue whereby the message 'Cannot insert duplicate key in object
dbo.FileCategory' displayed when attempting to submit data to Data
Manager. Case 22104
Issue whereby the message 'The given key was not present in the
dictionary' displayed when attempting to generate a traffic map using
the Planet Open API. Case 22144
Issue whereby the message 'Traffic for sector XXX is negative' displays
when attempting to generate a traffic map using the Planet Open API.
The problem occurs in cases where the network data for the sector
equals zero erlangs. Case 22476
Issue whereby the message 'Cannot find item XXX in current visible
layer' displayed when attempting to Locate a site. The issue occurred in
cases where the site being located did not exist in the Group or Flag
layer currently displayed in map window. Now, if the site being located is
not part of the Group or Flag layer, the sites layer will be opened and the
site being located will be centered in the map window. Case 22692
Issue whereby clutter weighting was not considered when generating a
traffic map using the Planet Open API. Case 22543
Issue whereby the generation of predictions from the Flags node in
Project Explorer did not properly consider repeaters associated with
sectors belonging to the active Flags filter. Case 22466
Issue whereby an out of memory error displayed when attempting to run
cdma2000 network analysis. Performance has been enhanced in version
5.3.0 to reduce the likelihood of such a problem occurring. Case 21488
Issue whereby the Network Overlay tool did not import Flag and Group
settings. Case 23160
version 5.2.1
n
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 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 (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 reopened, 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 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 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
Known Issues
The 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.
The following list details limitations that are known to exist at the time of this release.
n
When importing project data the log window may erroneously indicate
that rows in the Optimization Constraints table have been modified. Case
29234
After exporting and then immediately re-importing project data (without
making changes) the Compare Data function indicates differences in
antenna location coordinates. This issue is due to rounding. This
differences will not require prediction re-generation. Case 29233
Issue whereby the message 'Error: Could not read network data file.
Syntax error in FROM clause' displays when attempting to generate a
traffic map based on network data. This problem is known to occur when
the name of a sheet within the network data contains an underscore
character. To workaround the issue, rename the worksheet so that it
does not include the underscore character. Case 28750
The EV-DO revision displayed for discrete subscribers when using the Info
tool may be incorrect in certain circumstances.
Issue whereby Project Explorer behaves erratically. This includes
problems with scrolling operations, problems opening/closing Groups and
issues with cursor movement. Cases 25967, 26516, 26517,26584,26587,
26967,25698, 26963, 26637, 25294,27347
Issue whereby the message 'Index was outside the bounds of the array'
displays when attempting to generate Automatic Frequency Plans (AFP).
To avoid this issue, ensure that your sites and sectors do not contain
comma characters when creating neighbor lists to be used as input to
AFP. Case 27551
Issue whereby the message '< site name> failed: Predict 4.0 Error: failed
write to BIN file' displayed when attempting to generate predictions. This
issue occurred in cases where the geodata (heights and/or clutter) was
not an integer. To work around the issue, re-size your geodata files to
an integer resolution using the re-sizer tool in Grid Manager. Case 27589
n
In order to import iBwave projects, you must install the iBwave viewer.
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 propagation model analyses, surveys must be in either:
n
Known Limitations
The following list details limitations that are known to exist at the time of this release.
n
Issue whereby the message 'No license available for Universal Model.
Please check the license file <PlanetDir>\Universal Model\Universal_
Model.lic' displayed when attempting to tune a Universal Model. This
issue occurs when attempting to use a standalone license on a server
machine. To avoid the problem, use a server license. Case 27358
For migration to work properly, there must be at least one site in your
project. Case 27835
Site templates do not store MIMO antenna settings. Case 25197
Some settings on the General panel in the Site Editor are hidden. This
issue applies to HSPA carriers only. To avoid the problem, increase your
screen resolution. Case 22236
There may be minor differences in predictions when compared with
Mentum Planet 4.5. These differences can be attributed to fixes that were
made to the Longley-Rice model that existed in Mentum Planet 4.5:
n
The AFPP tool button applies only to GSM/TDMA technologies. If you wish
to run AFPP on a technology other than GSM or TDMA you must launch the
tool from the Tools menu. Case 21072
The workflow of connecting a single local project to multiple Data
Manager projects is not supported. If such a workflow is attempted a
warning message will be displayed. Cases 8601, 8700, 8701
The 'Keep existing physical cell ID assignments' option in the LTE FDD
(and TDD) Automatic Frequency and Physical Cell ID Planning dialog box
is disabled when an existing plan is being updated. Case 21084
When migrating Universal Models from Mentum Planet 4.5, 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 running network analysis based on a Group or based on the active
Flags, repeater sites associated with sectors in the Group or Flags
selection are included in the analysis even though they are not part of
the Group or part of the Flag selection. If you wish to exclude repeater
sites from the analysis you must make the repeater 'inactive'. Case
19750
The Layer Statistics Analysis tool may produce incorrect results if any of
the input grids are 'misaligned' (e.g., do not have a (0,0) reference
point. The X-min and Y-min values on a properly aligned grid are equally
divisible by the bin resolution. To correct a grid mis-alignment problem,
re-size the grid to the same size using the Resizer tool in Grid Manager.
Case 21358
When creating a traffic map based on regions, your input data file
cannot have more than 65534 region objects. If your region files
contains more than this number of regions you must break it into parts
and perform traffic map generation separately for each region file. Cases
17030, 21542
MapInfo Workspace references are not migrated (General tab in Project
Settings) when migrating from Mentum Planet 4.5.1 to Mentum Planet
5.3.0. Furthermore, the Workspace format has changed between
versions. You must recreate your Workspace upon migrating to 5.3.0
and re-set the reference to it in Project Settings. Case 21839
In some cases, the project migrator is not able to migrate terrain height
values (shown on the General tab in the Site Editor). To correct this
problem, re-specify your heights file (in Project Settings) to a file other
than the original file then revert to the original file. This action will
update the terrain height values. Cases 23595, 23834
The message 'Classified grid does not have the same number of clutter
classes as the model' will display if you change your project clutter file
and that new file does not have the same class structure as the previous
file. To correct this problem open your propagation model(s) in the Model
Editor, select the Clutter Properties tab, click anywhere in the Properties
section then click OK. Case 18603
Universal model performance improvements introduced in this version
may introduce slight differences when compared to previous predictions.
Displaying Bing Aerial or Bing Hybrid map layers may cause a shift of
layers due to projection differences. To avoid this shift set Reprojection to
Optimized (Map>Map Options>Image Processing).
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
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 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 modeled 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 modeled 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.x, combined
antennas are not automatically converted to split antennas. The current
migration rules are in place to ensure predictions generated in Mentum
Planet 5.x 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
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.
Cascading hyperlinks in the Google Earth Properties window do not work
properly. This is a known issue in the latest release (6.1.0.5001) of
Google Earth.
Selecting a large number of sites from a group in the Sites category of
the Project Explorer and then using the scroll bar results in display
issues.
System requirements
The system requirements outlined in this section are general recommendations only
and are based on typical usage of Mentum Planet software. This section details the
system requirements for:
n
workstations
CAUTION: 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 3000sectors. You can work
with larger networks using this configuration but performance may be impacted.
Processor
2 GB
RAM
At least 20 GB free space
Hard disk
SVGA (16-bit), 1280x1024
Display
Windows XP 32-bit
Operating System
Minimum configuration
is recommended that you modify the Automatic Updates
settings so that they are not done automatically.
Required Software
Recommended configuration
This configuration is suggested for networks up to 15000sectors. You can work
with larger networks using this configuration but performance may be impacted.
Processor
RAM
4 GB
Hard disk
Display
Operating System
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
NOTE: 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.
NOTE: Windows XP 32-bits or 64-bits and Windows Vista 32-bits or 64-bits are
supported.
NOTE: For information about system requirements for the Data Manager Server,
see the Data Manager Server Administrator Guide
CAUTION: Requirements vary depending on the layout of the network, the number
of sites, and the work practices you adopt.
Recommended Configuration for a Small Deployment
A small deployment is one in which up to 5 simultaneous users are accessing
Mentum Planet installed on a single application server and using either Windows
Terminal Services or Citrix for remote access from client.
Processor
RAM
12 GB of RAM
Hard disk
1 TB of storage
Display
Operating System
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.
Processor
RAM
24 GB
Hard disk
2 TB of storage
Display
Operating System
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.
Recommended Configuration for a Large Deployment
A large deployment is one in which more than 10 simultaneous users are accessing
Mentum Planet.
Consult Mentum Customer Care.
Documentation
Mentum software includes an extensive array of resources that will help you use the
software effectively. This includes a variety of guides, technical notes, application
notes, release notes, and online Help. You can easily access User Guides and
Technical Notes from the Help menu.
For complete details, refer to the Resource Roadmap accessible from the online Help.
You can access Help from within Mentum Planet in two ways:
n
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 and Technical Notes are
also available in print-ready PDF format and are accessible from the Help menu.
TIP: You can access the Customer Care Knowledge Base directly from with Mentum
Planet by choosing the Knowledge Base command from the Help menu.