WinProp Software - AWE-Communications

AWE Communications GmbH - Department: Research & Software Development 12/19/2002 

WinProp Software 

AWE Communications GmbH 

• Modifications and Improvements of Software Modules 

• Content of new Updates 

• History of Changes 

Definitions: 

Month, Day, 2002 

 

 

 

 

 

Bugfix 

A bug (error) in the software was corrected. 

Different prediction results might occur between new and former release. 

Code-Modification 

A modification of the source code was made which should lead to no effect. This 

message is only for information if the software shows a different/wrong behavior. The 

user should not see this modification and the software should be identical to the former 

release. 

Modification 

A modification of a sub-routine was made because of new scientific results. 

Different prediction results might occur between new and former release. 

Extension 

Extension of the software by adding new features. This allows additional control or 

additional processing of predictions. If the new features are not enabled in the dialog, 

the new version of the software will lead to the same prediction results as the former 

version. 

New Release 

New version was released. 

- Page 1 of 28 -


December, 17, 2002 

ProMan 

 

CNP: Combined result file not correct inside buildings 

During a CNP prediction WinProp saves immediately the indoor prediction results after 

each building is predicted (and frees the required RAM to avoid swapping if large 

databases are used). Additionally a second (temporary) result file is always stored. 

This file contains not only the power - it contains additionally information about the 

status of the pixels (not computed, outside building, inside wall, etc.). 

After all buildings are predicted, the final result file (with outdoor and indoor prediction 

in one figure) is generated. During this process the temporary indoor result files are 

read and integrated into the outdoor prediction result. 

This worked well with the first CNP versions. But in the meantime an improvement of 

the result file format was introduced to save memory on the hard disk. Now the number 

of required bits for the values of the matrix is determined. Before the improvement was 

enabled always 32 bit integers were used to save the results. But if the range of the 

values is between -327.67 and +327.67 a 16 bit integer would be sufficient to save the 

result values (after multiplying them with 100 to include 2 decimals). Same idea for 

other ranges. This is very efficient and reduces the file sizes significantly. 

And now comes the reported problem. As mentioned above, the temporary indoor 

result file contained additional bits to describe the pixel (see above). But the number of 

required bits per pixel to save the result in the new file format was only determined 

based on the values and not on these additional bits. While saving the data, the 

algorithm detected the problem and multiplied all result values with 0.1 to obtain the 

required headroom for the additional bits. Therefore all values lost their decimals and 

the first digit. Only values like 80.0, 90.0 100.0 were possible (we save field strength in 

dBuV/m in the temporary result file). And so only these values were integrated from the 

indoor results in the final result file. So the indoor result was too much rounded...... 

The bug is now fixed and exactly the same results are now inside the buildings in the 

final result and in the individual result files. 

 

 

 

Result files and topo/clutter databases: Accelerated reading 

Accelerated reading functions for faster reading of the files. 

Result files and topo/clutter index databases: 

Files which have no value in the matrix which is not equal to “undefined value” (e.g. 

prediction results where no pixel is computed or index database which contains no 

defined value in the matrix) are no longer saved with the matrix. Only the header of 

the data is saved. This accelerates the reading of index databases (and reduces the 

total file size of all sub-files) if several sub-datafiles contain only “not defined” values. 

Urban IRT: Multiplication instead of division 

During the determination of the visibility relations several divisions for the scaling of the 

values (transformation float integer) were substituted with the corresponding 

multiplications to accelerate the algorithms. 

- Page 2 of 28 -



ProMan/WallMan 

 

Topo or Clutter Pixel Databases: Index Files during Conversion 

Status: To accelerate the handling of large databases index files can be used (also 

with WinProp). And index databases (Planet or NPS/X) can be converted to WinProp 

index databases. 

New: if large databases are converted, the user is asked during the conversion 

process if he wants to generate an index database: So all pixel databases which are 

non-index files in the original data format (e.g. Wizard, ASC or BIN) can be converted 

to index databases. 

With index databases the loading time is significantly faster (for display and/or 

computation) and, if large areas are undefined pixels, the file size of all index files and 

sub-files is smaller compared to a single database. 


WallMan 

 

Urban Databases: Negative Coordinates 

No longer possible to preprocess databases with negative coordinates. 

Urban Databases: Preprocessing height below 0 or equal to 0 

An error message appears and informs the user that the height of the preprocessing 

might be wrong if the value is 0.005 or below to avoid problems with unreasonable 

predictions in ProMan. 


ProMan 

 

Urban: Negative coordinates 

If buildings had negative coordinates (which is not allowed and it should not be 

possible to use these databases - but sometimes the user generates such databases) 

ProMan crashed during prediction. This is now solved (but problems might still occur if 

coordinates are negative….) 


ProMan 

 

Urban: Transition between COST and IRT only computed if IRT value available 

Transition between COST and IRT prediction value for a pixel was computed if IRT 

prediction was computed for this pixel even if no result was obtained. This is now 

modified. Transition is only applied if IRT prediction was completed successfully. 


ProMan 

 

Network Planning: Supports now also geodetic coordinates 

Now geodetic coordinates are possible with network planning projects (and no longer 

UTM only). 


ProMan 

 

CDMA Network Planning: Gain of MS 

Gain and losses of mobile stations not considered correctly in all scenarios. Bug now 

fixed. 

- Page 3 of 28 -



ProMan 

 

Rural: Individual loss for each Hata Submodel 

For each Hata-Okumura submodel (dense urban – medium urban – suburban – open 

area) an individual additional loss can be defined for each clutter/morpho class. This 

helps to calibrate the model easily. 


ProMan 

 

Rural: Hata-Okumra & dominant clutter class 

Dominant clutter class is additionally used to determine the Hata submodel (dense 

urban – medium urban – suburban – open area) for the prediction. 

Up to now only the value of the additional attenuation was used based on the dominant 

class determination between transmitter and receiver. Now additionally the selection of 

the Hata submodel (if enabled to use the submodels) is controlled with the dominant 

clutter class. 


ProMan 

 

Location Based Services: Multiple Antennas for each LMU 

Now multiple antennas for each LMU are possible. 


ProMan 

 

Rural: Ray Optical Two Ray Model 

Error in the computation of the path loss of the ground reflected ray (material 

properties not considered as expected). 

November, 29, 2002 

WallMan 

 

Export of urban building databases to MapInfo file format 

Urban building databases can now be saved in MapInfo file format to use the files with 

other programs. 


WallMan 

 

Abort of preprocessing 

If the Cancel button is pressed during the preprocessing, the user is asked if he really 

wants to terminate the preprocessing. 


WallMan 

 

Loading preprocessing projects 

If the building database used in a preprocessing project was renamed or moved to a 

different directory, the project could not be loaded (error message appeared). This is 

now changed. If the database is not in the directory where it is expected (where it was 

last time) a dialog appears and the user can select the database for the project. 

- Page 4 of 28 -



WallMan 

 

Loading preprocessing projects 

If the building database used in a preprocessing project was renamed or moved to a 

different directory, the project could not be loaded (error message appeared). This is 

now changed. If the database is not in the directory where it is expected (where it was 

last time) a dialog appears and the user can select the database for the project. 


WallMan 

 

Simplification of urban buildings 

During the combination of buildings in the simplification mode it was possible to select 

whether the tallest or the lowest building properties are used for the new (combined) 

building. The lowest mode was not working properly (always tallest building mode was 

used). 

Additionally the thickness of the walls is now considered during the combination (as 

property of the newly generated buildings). 


ProMan 

 

Consideration of topography in COST 231 Walfisch-Ikegami prediction 

If topography is considered in the COST23 prediction the connecting reference line 

between the foot-point of the transmitter and the foot-point of the receiver defines now 

the zero level for the building heights. This means the heights of the buildings which 

intersect the vertical plane are referred to the height of the connecting reference line at 

the corresponding location. If the height of the building is below the height of the 

reference line then this building is neglected for the calculation of the average building 

height (and street width, etc.). So this procedure might lead to additional LOS areas 

with smaller path losses if the buildings intersecting the vertical plane are below the 

reference line. 


WallMan 

 

New DXF Converter 

New DXF converter (urban & indoor) to import DXF databases into WallMan available. 


ProMan 

 

Transition between IRT- and COST231 prediction area 

The function for the adaptation of the results at the border between the inner IRT-area 

and the surrounding COST231-area is modified (only relevant if the additional 

empirical prediction area is switched on). In the new solution the results of the 

COST231-area are adapted according to the difference between the IRT- and the 

COST231-model occurring at the border between both prediction areas. The new 

transition function modifies the COST231-predictions by evaluating the above 

mentioned difference and the distance between the border intersection and the 

receiver in a linear way (i.e. the adaptation decreases linearly with increasing distance) 

up to a given maximum distance (in m). This maximum distance is the only parameter 

for the control of this new transition function. If the maximum distance is set to 0.0 no 

adaptation is performed. 

- Page 5 of 28 -



ProMan 

 

Filter 

The functionality of the filter function within the project settings (which had no effect in 

the latest versions) is updated. A direct smoothing of the results is performed 

according to the selected filter order (median value). 


ProMan 

 

Two new color palettes for result display: Bright Rainbow and CMR 

Two new color palettes for result display were added. The classical rainbow palette is 

now available in two options: bright and dark. While dark is the former rainbow palette 

the new bright palette does not contain any gray elements leading to very bright 

pictures. 

Additionally the new CMR map rendering is added. This map maintains an 

aesthetically pleasing color image that automatically reproduces to a monotonic 

grayscale with discrete quantifiable saturation levels. 


WallMan 

 

Topo Database Converter integrated into WallMan 

DataMan converter for topographical (elevation) databases in different formats (MSI 

Planet, Agilent Wizard, Nokia NPS/X,…) is now integrated into WallMan GUI. 


ProMan 

 

 

Topo Database Converter integrated into ProMan 

DataMan converter for topographical (elevation) and clutter (morpho) databases in 

different formats (MSI Planet, Agilent Wizard, Nokia NPS/X,…) is now integrated into 

ProMan GUI. 

Topo Database Converter: Supporting a wide variety of coordinate systems 

The number of supported coordinate systems was significantly increased. 


ProMan 

 

CDMA Network Simulator: Definition of common channels possible 

Individual definition of common channels for the CDMA network simulator is now 

possible. Coverage plots for each common channel is possible. Reception of common 

channels (downlink) is additionally used to determine coverage area. 


ProMan 

 

CDMA Network Simulator: Display of BS performance (Throughput,…) 

Performance data of BS is written to MS EXCEL files and can be displayed either in 

area plots or with context sensitive menus (by clicking on the BS symbol). 

- Page 6 of 28 -



ProMan 

 

Display of large result files 

If the number of rooms or columns was larger than the number of pixels on the screen, 

the very top line and very right column of the prediction result were not displayed on 

the screen. This is now changed. 


ProMan 

 

Dynamic CDMA Network Simulator: Definition of traffic maps (arrival rates) 

Traffic maps can be used for the dynamic CDMA network simulator instead of 

assuming homogenous traffic distribution. Traffic maps can be drawn with ProMan or 

can be generated on the basis of morpho/clutter data. 

October, 31, 2002 

ProMan 

 

Dynamic CDMA Network Simulator: Output of max value files 

Max. required MS and BS power for each pixel is determined and saved in a result file. 

This summarizes the individual output of the MS and BS power results for each time 

step. 

October, 30, 2002 

ProMan 

 

Dynamic Network Simulator: Different types of mobile stations 

Different types of mobile stations can be defined for each service. If not defined, the 

default mobile station will be used. 

October, 29, 2002 

ProMan 

 

CDMA network simulator: Prediction of BS power 

Channel power required for dedicated user channel for each BS is written to a result 

file. 

October, 28, 2002 

ProMan 

 

CDMA Network Planning: Power of MS station 

Antenna gain and losses of MS station were not considered correctly due to a 

transformation error from log values to linear values. This is now fixed. Different 

results with smaller coverage will now be computed. 

October, 25, 2002 

ProMan 

 

Area of Rural Prediction Models 

If area of prediction is larger than database (topographical), then area of prediction is 

automatically reduced to the size of the topographical database. 

October, 18, 2002 

ProMan 

 

Output of MS power files in UMTS simulator 

Output of ASCII file with Tx powers of all MS during CDMA network planning. 

- Page 7 of 28 -


October, 16, 2002 

ProMan 

 

Horizontal polarization in rural prediction models 

Selection if either horizontal or vertical polarization is used for rural prediction models 

(ray optical model or parabolic equation model). 

October, 14, 2002 

ProMan 

 

Ray Optical Model for rural scenarios 

New ray optical model (direct ray and ground reflected ray) for rural prediction 

environments. 

October, 10, 2002 

ProMan 

 

3D Scattering for rural prediction models 

Consideration of scattered rays (scattering in 3D topography) as add-on for all rural 

prediction models (which are only based on vertical plane). 

September, 23, 2002 

ProMan 

 

Threshold for propagation delay results 

Propagation delays (see Sep, 16,2002) are now only considered if the path loss is 

below a given threshold (max. value). 


ProMan 

 

Wizard converter (Topo, Clutter, Project) 

Topographical (DEM) and clutter (morpho) data from Agilent’s Wizard Planning toll can 

be converted to WinProp data format. 

Additionally Wizard projects can be imported into ProMan (Sites, transmitters, 

channels,…). 


WallMan 

 

Building data converter (Geb data format) 

New building data converter for geb data format available (ASCII format used by T- 

Mobile). 


ProMan 

 

Output of path delay possible 

In urban or rural environments the delay of the shortest or strongest propagation paths 

can be written to a result file (fpt). 

August, 26, 2002 

ProMan 

 

Clutter classes between BS and MS 

Now the clutter classes between MS and BS can be considered instead of the clutter 

class at the receiver only. The weight of the classes depends on the distance to the 

MS and can be defined in the project settings. 

- Page 8 of 28 -


August, 26, 2002 

ProMan 

 

Clutter classes between BS and MS 

Now the clutter classes between MS and BS can be considered instead of the clutter 

class at the receiver only. The weight of the classes depends on the distance to the 

MS and can be defined in the project settings. 

August, 23, 2002 

WallMan 

 

WallMan: IRT Indoor: Progress bar 

Old version counted multiple times from 0 to 100% (separate counters for walls, 

segments, visibility relations, etc.). Now only one counter starting at 0% counts up to 

100%. 

August, 20, 2002 

ProMan 

 

ProMan: Rural Prediction Code 

The code of the rural prediction models was modified. Up to now a jump was made if 

am error occurred or if cancel was pressed. This is now modified and the jump is no 

longer required. 

August, 19, 2002 

ProMan 

 

ProMan: Urban: Output of propagation delay (time) 

The delay between the transmitter and the receiver can be determined in urban 

scenarios. Due to the ray-optical approach multiple rays are determined for each 

receiver. The user can select which type of delay (shortest ray or ray with max. power). 

August, 16, 2002 

ProMan 

 

 

ProMan: Rural: LOS Analysis possible 

New (output) prediction result is available for rural scenarios: LOS analysis. 

The output is either LOS or NLOS depending on the LOS condition between 

transmitter and receiver. 

For this result the clutter heights can be used additionally. 

ProMan: Rural: New display for clutter databases 

New display for clutter databases: No longer the class ID (number) is shown. Now the 

name of the class is shown and the color used for this class can be defined by the 

user. 

August, 15, 2002 

ProMan 

 

 

ProMan: Individual prediction areas 

In network projects for each transmitter an individual prediction area can be defined. 

So no longer the same area must be used for all transmitters. 

ProMan: Circular prediction areas 

In network projects circular prediction areas are possible for each transmitter, i.e. only 

the radius of the prediction area must be defined. 

- Page 9 of 28 -


August, 14, 2002 

ProMan 

 

ProMan: Local Measurement Unit (LMU) 

The new object LMU was introduced for network projects. LMUs can be placed with 

the mouse and are used to measure field strengths at arbitrary locations within the 

wireless network. Especially important for localization of users (location based 

services). 

Consideration of LMUs currently only possible with rural prediction models. 

August, 13, 2002 

ProMan 

 

ProMan: Urban: Vegetation: Offset for material properties 

Offset for material properties of vegetation objects was not considered correctly. 

August, 12, 2002 

ProMan/AMan 

 

ProMan: ERP power definition 

Definition of transmitter power was up to now always in EIRP. Now additionally ERP 

power is possible. But antenna patterns must be saved again with AMan to use ERP. 

August, 09, 2002 

ProMan 

 

ProMan GUI: Text related to antenna/transmitter 

In case of sector antennas the name of the antenna is now written on the display 

depending on the azimuth angle of the antenna. 

During the definition of a project the name is written in main direction of radiation (to 

have a clear assignment of cell and transmitter/antenna name in case of sites with 

multiple transmitters). If results are displayed the name is always “behind” the antenna 

(to see the main direction of radiation of the antenna without any text). 

The azimuth defined for isotropical antennas has the same influence on the location of 

the text on the display so the azimuth angle can be used for iso radiators to locate 

the name of the antenna at an arbitrary location (no influence on the prediction 

because of isotropical radiation). 

August, 08, 2002 

ProMan 

 

ProMan: Import of MSI PLANET projects 

Projects generated with MIS PLANET (or Siemens Tornado) can be imported into 

ProMan (sites, carriers, etc.) and then be used in ProMan. 

August, 07, 2002 

ProMan 

 

 

ProMan: Network Projects: Direct computation of propagation 

Up to now a network project was only based on prediction (propagation) results. Now 

the transmitters can be defined in the network project and the propagations are 

computed first and after this step the network parameters are computed. 

ProMan: Network Projects: Sites 

The new object Site was introduced for network projects. A site contains multiple 

transmitters. 

- Page 10 of 28 -


August, 05, 2002 

ProMan 

 

 

ProMan: Network Projects: Frequency Assignment via Carrier Table 

Now the frequency can only be defined via a frequency assignment table where each 

carrier gets is assigned its own frequency. 

ProMan: Rural: Index databases (Terrain & clutter/morpho) 

Besides the well-known terrain and clutter databases (single files) now additionally 

index databases (multiple files organized with an index file pointing on them) is 

possible. This is especially important for very large areas. 

August, 02, 2002 

ProMan 

 

 

ProMan: Output in Excel format (Indoor & Rural) 

If output in Excel format is selected and the project is computed, the application could 

crash (Null pointer assignment) when computing the Excel output in urban or rural 

scenarios. Bug is now fixed. 

ProMan GUI: Transmitter Index 

For each transmitter a index number is added to the proposed (default) name. The 

number is increased with each new transmitter. 

But if the project is saved, closed and re-opened this index is initialized with the 

number of transmitters, which is not always free of conflicts. E.g. if 4 transmitters are 

added (index 1…4 TRX 1, TRX 2, TRX 3, TRX 4) and after this the third one is 

deleted ( TRX 1, TRX 2, TRX4), the index for the next one will be 5 (to avoid the 

same names for transmitters TRX 5). But after saving the project, closing and reopening 

the index of a new transmitter will be 4 (TRX 4). But this name is already 

occupied by a different transmitter. This conflict is now solved by saving the index in 

the project file (so after re-loading the new transmitter would also get the index 5). 

August, 01, 2002 

ProMan 

 

 

ProMan: Additional output of results in ASCII format 

All prediction results of a propagation project (power, path loss, delay spread,…) can 

now be saved additionally in an ASCII file to simplify processing of these results with 

other software products. 

ProMan: Separation of results with different directories for each transmitter 

To simplify the handling and to reduce the learning effort of the user, ProMan can now 

save the results in different directories (each transmitter/antenna in an individual 

subdirectory in the central output directory) and the files are now named by their 

content (e.g. /Example/TRX 1/Power.fpp”). So the user does no longer have to learn 

the extensions and their meanings. The content of the file is obvious because of its 

name). 

July, 31, 2002 

ProMan 

 

ProMan: Default Transmitter/Antenna 

For each project the user can define a default antenna/transmitter. Each new 

antenna/transmitter added to the project will be initialized with the default properties. 

This is especially important for name, height (z-coordinate of antenna), antenna 

pattern, downtilt,.. 

- Page 11 of 28 -


July, 30, 2002 

WallMan 

 

WallMan & DataMan: Conversion of databases 

Due to the limited accuracy of databases (especially – but not limited to - urban 

databases with very high values for the coordinates), numerical problems led to a 

problem when determining the sequence of the corners (clockwise or counterclockwise) 

and when determining if the wedges of the walls have intersections. So the 

objects were deleted during the conversion of the data. It could also happen with 

indoor databases if they have not very accurate coordinates. 

This is now modified and an increased tolerance (0.00001 0.02) for the 

determination of the sequence of corners and intersection of wedges is used. 

July, 29, 2002 

WallMan 

 

WallMan: Auto-Simplification of Databases while Save and Load 

WallMan always tries to minimize the number of corners for each object (to save 

computation time during preprocessing). If three points (corners) are on the same line, 

the middle corner is deleted automatically when saving the database because it is not 

required to describe the object. 

The bug occurred when the first corner in the sequence of corners should be deleted 

(because it was the middle corner on the line from the last corner to the second 

corner). Then the first corner was not deleted and the last corner was deleted. 

Bug is now fixed and in the above mentioned case the first corner is now deleted. 

July, 26, 2002 

ProMan 

 

 

GUI: Prediction Parameter: Accuracy of coordinates related to mouse click 

Up to now the accuracy of the mouse (definition of transmitter location or prediction 

area) in case of UTM coordinates was one floating digit (e.g. “1.70”). This is now 

changed to two digits (e.g. “1.73”). 

GUI: Save of Settings file (*.wpi) 

Up to now always the properties (margins and thresholds related to margins) for all 

types of results (power, field strength, delay,….) were saved in the *.wpi settings file. 

But this makes no sense because the data is always the same and the properties of 

the margins of the other data types could not be modified in the dialogs. 

In some special cases ProMan could also crash while writing the margins of the other 

data types to the settings file. 

From now on only the margins of the current type of data is saved in the settings file 

(*.wpi). This reduces the size of the file and avoids crashes. 

July, 25, 2002 

WallMan 

 

 

WallMan: Indoor IRT: Preprocessing 

If it was not possible to determine the angle of incidence at a wedge due to mathematical 

problems (identical vectors => cross product is 0), WallMan crashed. This is 

now fixed. If this problem occurs, the visibility is not considered in the preprocessing. 

WallMan: Load of urban ASCII databases 

If an urban building is defined as a single line (with at least three corners) it could 

happen that WallMan crashes while loading this building (because it is not a 

building/polygon – it is only a line). This is now fixed. These objects are now removed 

while loading urban ASCII databases (*.oda). 

- Page 12 of 28 -


July, 23, 2002 

ProMan 

 

 

ProMan: CNP IRT 

The transmission loss of the wall (tile) separating outdoor indoor was not always 

considered due to numerical problems. This is now fixed. The ray from outdoor to 

indoor starting at the tile starts now 0.5 m behind the tile to get the transmission loss of 

the tile. 

ProMan: Network Planning 

Since the new TDMA modules were introduced (July, 02, 02) the outputs of cochannelinterference 

and superposition were no longer computed even if they were selected in 

the dialog. This is now fixed. 

July, 22, 2002 

ProMan 

 

ProMan: Empirical Reflection & Diffraction Model for IRT Modules 

An angle dependency for the empirical reflection model for urban and indoor IRT is 

now implemented. If the wave is parallel to the wall, the reflection loss is only 50% of 

the value (in dB) defined in the material properties. If the wave is perpendicular to the 

wall, the loss is 100% of the value defined in the material properties. Between the two 

values a linear interpolation is made. 

July, 19, 2002 

ProMan 

 

ProMan: Auto-Combination of CNP prediction results 

Combination of prediction results is now done automatically if indoor height is identical 

to prediction height of urban module. 

July, 18, 2002 

ProMan 

 

ProMan: Network Planning: Cancel button and Error handling 

The Cancel button and the error handling in the network planning module was redesigned 

without any longjmps to have a guarantee to free the whole memory when 

Cancel is pressed or an error occurs. 

July, 17, 2002 

ProMan 

 

ProMan: Improvement of CNP IRT Prediction Module 

CNP IRT prediction module was improved concerning computation time. Additionally 

output of propagation paths is now possible. 

July, 16, 2002 

ProMan 

 

ProMan: Urban IRT: Transmitter visibility for multiple transmitter projects 

Up to now the transmitter visibility was computed for all enabled transmitters in the 

project and after this step was completed the prediction started. 

To save memory this was modified. Now the prediction for a transmitter starts 

immediately after its visibility is computed. And after the prediction is completed the 

memory for this transmitter is freed and the transmitter visibility for the next transmitter 

is computed. So always only one transmitter visibility table is stored in the memory. 

- Page 13 of 28 -


July, 15, 2002 V5.50 

Release V5.45 

New release V5.45 of ProMan, WallMan and AMan. 

July, 15, 2002 

ProMan 

 

ProMan: Problems with Window Size in Registry 

As all other Windows applications ProMan saves the current size and position of the 

window when the application is closed in the Windows Registry. If the ProMan window 

was minimized and then directly closed, the new start of ProMan did only start the 

application minimzed and after resizing the window and closing it again the new 

window size was no longer saved in the registry –always the minimizedwindow size 

was saved. This is now fixed. And if the application is closed while it is minimized, the 

application opens with a standard display size when re-opened. 

July, 09, 2002 

ProMan 

 

ProMan: COST Prediction for Urban 

The COST prediction for urban environments was slightly modified to handle special 

cases with better accuracy 

- The next building behind the receiver (seen from transmitter) is now only 

considered for the determination of the street width of the receiver street if it is less 

than 200 m behind the receiver. 

- If the distance to the next building is more than 200 m (or if no building is found 

behind the receiver), the street width of the receiver street is set to the distance 

between the building in front of the receiver (towards the transmitter) and the 

receiver location. If this last street width is less than 20 m it is set to 20 m and if it is 

more than 200 m it is limited to 200 m. The old version did not limit the maximum 

value which could lead to extreme wide streets….. 

July, 05, 2002 

ProMan 

 

ProMan: Indoor: Transmitter inside wall 

If transmitter was located inside the wall, the prediction was computed. This is now 

modified. Prediction is only possible if transmitter is outside wall (including thickness of 

wall). 

July, 04, 2002 

WallMan 

 

Indoor IRT: Disable outdoor rays 

Up to now always rays inside and outside the building were determined during IRT 

preprocessing. Now the user has the option to disable rays leaving the building (in this 

case only rays which are totally indoor are used). 

July, 03, 2002 

ProMan 

 

Corrections in new file format 

The new file format, introduced in May, was not able to save a value of 0.01. After 

saving the file and re-loading the value was always set to “not computed”. This is now 

fixed. And additionally a bug while writing indoor result files is also fixed. 

- Page 14 of 28 -


July, 02, 2002 

ProMan 

 

TDMA Network Planning Module: Best Server 

Up to now only a best server plot based on channel numbers assigned to each 

transmitter during the path loss predictions was generated. If all transmitters had the 

same channel number the best server plot was useless. 

Now additionally a cell ID plot is generated. Each transmitter gets a number 

(depending on its position in the list of transmitters) and the plot shows the number of 

the transmitter (and not the channel ID). So this plot helps to visualize the cell layout in 

a more convenient way. 

June, 27, 2002 

ProMan 

 

Urban: Additional consideration of COST contribution for delay spread 

Up to now the delay spread was only based on ray-optical propagation paths. Now the 

contribution of the multiple diffracted ray in the vertical plane (computed with the COST 

model during the postprocessing) is additionally considered for the computation of the 

delay spread. The values are now significantly (up to 200 ns, depending on the Tx 

location) higher. 

June, 26, 2002 

ProMan 

 

 

Delay Spread predictions: Based either on field strength or on power 

Up to now the prediction of the delay spread was based on field strength only. Now the 

user has the option to decide to compute the delay spread either on power or on field 

strength. 

Delay Spread predictions: Consideration of bandwidth 

Up to now ideal impulses (with infinite bandwidth) have been used for delay spread 

predictions. Now a real bandwidth of 5 MHz is used for the computation of the delay 

spread leading to approx. 10…40 ns higher values in the prediction. 

June, 25, 2002 

ProMan 

 

TDMA Network Planning Module extended: Prediction of probability 

The probability of receiving the signal is not digital, i.e. if the received signal is above 

the threshold it works and if it is below it does not work. Due to fast fading the level of 

the received signal varies. 

Based on the Rayleigh distribution a probability is now given for receiving the signal 

based on the S/N ratio (see 06/24/02) . If the S/N is very high (i.e. the received level is 

very high above the threshold) the probability is nearly 100%. If it is below the 

threshold (S/N < 1 or negative (in dB)) the probability gets very small. 

June, 21, 2002 

ProMan 

 

TDMA Network Planning Module extended: Prediction of handover areas 

Now it is possible to obtain prediction results showing the number of possible 

alternatives for a handover in TDMA networks. 

- Page 15 of 28 -


June, 19, 2002 

ProMan 

 

TDMA Network Planning Module: Consideration of MS properties and many new 

output options (MS power, BS power, S/N, Number of received channels) 

Properties of mobile station (Noise figure, antenna gain, general loss, required fast 

fading margin,…) are now considered for TDMA network planning (up to now only 

used in CDMA planning). 

Based on this properties of the MS the min. required Tx power of the mobile station 

and the min. required Tx power of the base station are predicted. Also the max 

achievable S/N ratio and the number of channels which can be received (positive S/N 

ratio) is predicted. 

June, 17, 2002 

ProMan 

 

ProMan : Network Planning. Gain of MS antenna 

Gain of MS antenna, defined in propagation project and used for power or path loss 

predictions was included in prediction results and therefore used additionally when 

computing a network project. This is now modified. Network project reads propagation 

predictions without gain of MS antenna and used the gain of the MS antenna defined 

in the network project. 

June, 14, 2002 

ProMan 

 

ProMan: Urban: First transmitter disabled 

The software could crash when writing the results if the first transmitter is disabled 

(Write algorithm is based on area settings of first transmitter). This is fixed now (The 

first enabled transmitter is searched in list). 

If all transmitters are disabled a error message appears and the prediction is 

terminated. 

June, 13, 2002 

WallMan 

 

WallMan: Urban: Preprocessing: Relative or absolute height of buildings 

In WallMan it is now possible to handle relative (above ground level) or absolute 

(above sea level) building heights if topographical databases are additionally used. 

June, 07, 2002 

ProMan / WallMan 

 

 

WallMan: Preprocessing of indoor databases 

Preprocessing of indoor databases: Error message for all walls generated because 

walls were not planar. This bug entered the software due to a code modification on 

June, 03 rd and is removed now. 

ProMan: Indoor Prediction 

Predictions of indoor databases: Error message for all walls generated because walls 

were not planar. This bug entered the software due to a code modification on June, 

03 rd and is removed now. 

- Page 16 of 28 -


June, 03, 2002 

EMCMan 

 

ProMan: GUI: Zoom Decrease and Former Window 

Decrease zoom always led to the former zoom window (zoom factor). This is now 

modified. Decrease zoom leads to a smaller zoom factor independent of the former 

zoom factor. Additionally the new feature “Former zoom window” is implemented to 

allow the user to go back to the former zoom factor. 

May, 29, 2002 

EMCMan 

 

EMCMan: Sequence of tab positions in Mast dialog 

Sequence of tab stops in mast properties dialog is modified. 

May, 28, 2002 

ProMan 

 

 

ProMan: Increase Zoom 

When increasing the zoom (+), the upper right corner was not set correct according to 

the new window (kept old position). So the center of the display moved towards the 

lower left corner after multiple zoom increasing .. . 

This is now corrected. The zoom increases and the center coordinates of the display 

remain constant. 

ProMan: Display of building heights 

Display of building heights only possible if urban building data is available (because for 

indoor or rural data it makes no sense). 

May, 24, 2002 

WallMan 

 

 

 

 

WallMan: Close Window 

If a window was closed and the data was modified (but not saved) the user is now 

asked if he wants to save the data (or cancel the closing). This works in both modes of 

the documents (edit database and definition of preprocessing projects). 

WallMan: Save Indoor Databases 

If indoor databases were saved with the new version including the acceleration of the 

display (see April, 29 th , 2002) a problem could occur when loading the database again. 

This is now solved. 

WallMan: 3D View 

If the 3D view with the new version including the acceleration of the display (see April, 

29 th , 2002) is selected, some objects were missing in the display. This is now solved. 

WallMan: Selection of group of objects and deleting objects 

If a group of selected objects was deleted with the new version including the 

acceleration of the display (see April, 29 th , 2002), some objects were still in the 

database but not on the display. This is now solved. 

- Page 17 of 28 -


May, 21, 2002 V5.44 

Release V5.44 


May, 17, 2002 

WallMan 

 

WallMan: Selection of objects 

Selection of objects with the mouse worked not always correct (object could not be 

selected by clicking with left mouse button on object). This was due to the acceleration 

of the display (some days before). Bug now fixed. 

May, 16, 2002 

ProMan 

 

ProMan: Project Definition: Handling of Transmitters 

Transmitter page in all projects (rural/urban/indoor) was modified. Now a list appears 

and the user selects the transmitter he wants to edit from the list. The user can 

additionally click on the transmitter with the mouse (left button) and comes directly to 

the transmitter properties page. 

May, 15, 2002 

WallMan 

 

WallMan: Urban: Simplification of building databases 

Urban building databases can be simplified by combing adjacent buildings with a 

height difference below a definable threshold. This reduces the number of buildings 

significantly and accelerates prediction and preprocessing time. 

This feature is available in WallMan Edit menu as well as during the conversion 

process (conversion of external data formats). 

May, 14, 2002 

WallMan 

 

 

 

WallMan: Urban: Sequence of corners during conversion of building data 

The sequence of corners is now automatically correcteded during conversion and must 

not be done later in WallMan. 

WallMan: Urban: Building data converter for Mapinfo modified 

The *.mid-file which is required for the Mapinfo building data converter can now be 

selected in a dialogue (incl. the definition of the column with describing the height). 

WallMan: Urban: Building data converter for Aircom Enterprise / Nokia NetAct 

New database converter for Aircom Enterprise and Nokia NetAct was added to the list 

of available converters. 

May, 13, 2002 

DataMan 

 

DataMan: New topographical data format: NPS/X 

The topographical database format of NPS/X is now supported by the conversion 

algorithms in DataMan. 

- Page 18 of 28 -


May, 10, 2002 

ProMan 

 

 

ProMan: Rural: Knife Edge Models: Max. number of diffractions in project 

Max. number of interactions (diffractions) for Knife Edge models can be defined in 

project. Especially important if LOS-plots or coverage areas with max. one diffractions 

want to be analyzed. 

ProMan: Rural: Knife Edge Models: Min. number of diffractions in results 

Min. number of interactions (diffractions) for Knife Edge models can saved in an result 

file and displayed afterwards. Very important to analyze the LOS area and the area 

which can be reached with an allowed max. number of diffractions. 

May, 08, 2002 

ProMan 

 

 

ProMan: Rural: 2-Ray model: Consideration of antenna patterns 

Determination of antenna gain did not consider topographical height of transmitter and 

receiver correctly. This is now fixed. Topographical height for both (Tx and Rx) is used 

to determine the antenna gain. 

ProMan: Rural: Height (elevation) prediction data 

Height (elevation) prediction data is now relative to transmitter’s topographical height. 

Especially important if earth curvature is considered. 

May, 06, 2002 

ProMan 

 

 

ProMan: Rural: Handling of databases with undefined areas 

If a part of the topographical database is not available (pixels set to not defined) the 

prediction is computed for all other pixels where the undefined pixels are not needed. 

ProMan: Rural: Consideration of earth curvature 

For all rural models it is possible to consider the curvature of the earth surface. 

May, 03, 2002 

ProMan 

 

ProMan: Additional Layers in display 

Especially for rural networks: Additional data (streets, borders,…) can be displayed to 

make navigation easier in the prediction results. These data layers can be imported 

from open ASCII file formats and are stored together with the topographical database 

and the projects – so they are always visible in all prediction results. 

May, 02, 2002 

ProMan 

 

 

ProMan: Export of prediction results 

The text for “not computed” pixels was not written to the export file properly. In matrix 

mode there was always added “10” to the string. 

This is now fixed! 

ProMan: Rural: Hata Models 

The Hata model can now be modified according to the settings in the morpho classes 

(urban/suburban/open area) or by the user for the whole prediction area. 

- Page 19 of 28 -


April, 30, 2002 

WallMan 

 

WallMan: Acceleration of saving urban databases 

The tests required to save urban databases were reduced and accelerated so that 

saving the database is significantly faster than before. 

April, 29, 2002 

WallMan 

 

 

WallMan: Acceleration of display 

Acceleration of display by new algorithms to draw the database on the screen. 

Significantly improvement especially for large databases with many objects. 

WallMan: GUI: Settings: Draw not all objects 

The user can define a max. number of objects drawn on the screen for the definition of 

preprocessing projects to accelerate the display. E.g. if max. 1000 objects and 5000 

objects are in the database, each 5 th object in the list is drawn. 

April, 24, 2002 

WallMan 

 

 

WallMan: Load Database after conversion 

The database is no longer automatically loaded after the conversion with a database 

converter. The dialog for the selection of the converter for the database allows to 

enable/disable to load the database. This is especially suitable for larger databases (to 

save some time). 

WallMan: Display of urban databases during the preprocessing project definition 

Especially very large urban databases (more than 5000 buildings => which is not 

recommended) lead to a long delay when drawing the building data. For the definition 

of the preprocessing parameters it is not required to see all buildings. So the user can 

define a max. number of buildings and WallMan selects a subset of buildings to draw 

the database (e.g. 999 buildings in database. Max number is set to 100. Then each 

10 th building in the list of buildings is drawn Building 0, Building 10, Building 20,….). 

For the computation of the preprocessing all buildings are obviously considered! This 

feature is only to accelerate the display re-draw for very large databases….. 

April, 18, 2002 

ProMan 

 

 

ProMan: Distance Tool 

Distance is now always displayed in meters even if geographic coordinate systems are 

displayed. 

ProMan: More accuracy (floating point digits) for geographic data 

When using geographic databases the accuracy of the info view and all dialogs with 

coordinates is now increased. 

April, 16, 2002 

ProMan 

 

ProMan: Display of results: Plot with distribution of values 

The text for the x-axis of the distribution plot was always related to the default text for 

the prediction result and not to the definitions in the settings. This is now fixed. Now 

the text from the settings is used. 

- Page 20 of 28 -


April, 15, 2002 

ProMan 

 

ProMan: Rural: Geographic coordinate systems 

Now it is possible to work with more than 20 different geographic coordinate systems 

(e.g. WGS-84, WGS-72, WGS-66, WGS-60, Bessel, Clarke, Fischer, Everest, Airy, 

Helmert, GRS,…) with ProMan. Conversion of geographic coordinates to UTM no 

longer required for the predictions. 

April, 12, 2002 

DataMan 

 

DataMan: Topographical databases: Conversion of height lines 

If some pixels in the database are not defined the missing pixels are interpolated 

(double bi-linear interpolation). So the conversion of height lines leads to accurate 

topographical pixel databases even if the separation between the lines is several 10 m. 

April, 11, 2002 

ProMan 

 

 

ProMan: Display of results: Threshold button 

A new threshold button was introduced. The prediction result is displayed in two colors: 

Green if below threshold and red if above threshold. This helps to analyze the results if 

they must be above or below a given threshold. 

ProMan: Display of results: Symbol for directional antennas 

Now it is possible to define the symbol for directional antennas. Instead of the arrow 

also a cross (similar to omnidirectional antenna) is possible (especially important for 

linear antennas (diploes and monopoles) which have no directional radiation in the 

horizontal plane. 

April, 10, 2002 V5.42 

Release V5.42 


April, 09, 2002 

ProMan 

 

ProMan: Urban: Border of the prediction area 

If the empirical prediction area and the ray-optical prediction area are equal, the 

transition from IRT to COST at the border of the IRT prediction area was still made 

(but not required because no pixels outside the IRT area were predicted). 

Now the transition is only computed if both areas are not identical. If they are identical 

the IRT prediction is not reduced at the border due to the empirical COST prediction. 

April, 08, 2002 

ProMan 

 

 

Urban: Crash if Postprocessing is disabled 

If the postprocessing is disabled in the project, ProMan crashes when checking if Tx is 

active/enabled. This is fixed. 

ProMan: Toolbar for projects 

Prediction toolbar was renamed Project toolbar and is docked to the left side of 

ProMan’s window (instead of top) to make navigation in ProMan easier. 

- Page 21 of 28 -


April, 05, 2002 

ProMan 

 

ProMan: New Zoom Concept for results and projects in GUI 

In former versions only zoom window and reset window was possible. So the user 

had to reset the window and restart the zoom if the selected area was not the one he 

was interested in. 

Now a new zoom concept is available with Zoom+ and Zoom-. Additionally it is 

possible to move the selected part of the data matrix with the cursor keys (or with the 

mouse). So time-consuming zoom-in-and-zoom-out procedures are no longer required. 

April, 02, 2002 

ProMan 

 

 

 

 

 

Rural: Project Files 

If the unit of the transmitter was set to dBm, the value in the dialog was wrong after 

loading the project again (Value (in dBm) was converted to W, but unit was still dBm). 

The prediction used the correct value. 

GUI: Reading of prediction results with no data 

If prediction results with no data (0 lines and 0 columns) were read, ProMan crashed. 

This is now fixed. ProMan reports the problem in a message box and does not crash. 

Rural: Modification of the prediction area 

The upper right corner of the empirical and deterministic prediction area and the upper 

right corner of the empirical area were modified to correspond to the lower left corner 

of the empirical prediction area plus an integer multiple of the resolution. 

Network Planning: Error messages if prediction files are not available 

If the selected prediction files are not available, an error message appears. 

GUI: More details in error message if format of result files or databases is not 

supported 

More details in error messages 

March, 28, 2002 

ProMan 

 

Code Splitting in DLLs 

For easier development the code can be split in different DLLs, depending on the 

current requirements. E.g. the general prediction module (reading project files, writing 

& reading result files, …) can be combined to a DLL as well as module for network 

planning or module for the inputs of the network planning. 

Still possible to compile the GUIs in a single executable for easier handling of the 

software. 

March, 27, 2002 

ProMan 

 

New addressing of hardware keys / dongles 

Dongle is checked more frequently (after less calls of the functions) and variable 

queries are used instead of the predefined fixed queries. 

- Page 22 of 28 -


March, 25, 2002 V5.41 

Release V5.41 


March, 18, 2002 

ProMan 

 

ProMan: Urban/Indoor: Homogenous handling of material properties 

Up to now the source code for the handling of material properties for indoor and urban 

was different (different structures for the data). This was harmonized leading to the 

same structures and code elements for indoor and urban code. 

March, 15, 2002 

ProMan 

 

 

 

ProMan: New dialog for transmitter properties in projects 

The dialog for the transmitter properties in the projects was extended. It shows 

additionally the number of the transmitter and the transmitter can be enabled or 

disabled for the prediction. If the project is computed only enabled (active) transmitters 

will be computed. All other transmitters will not be computed to save computation time. 

ProMan: Urban IRT Predictions: Handling of Transmitters in Buildings 

If transmitters are located inside buildings, the prediction of the whole project is no 

longer stopped. Only the computation of the transmitter located in the buildings is 

skipped and the computations continues with the next transmitter. 

ProMan: Urban IRT Progress bar: Output of Tx number 

The number of the current transmitter and the total number of transmitters is 

additionally displayed in the progress bar to show the status of the prediction. This is 

especially important for projects with a high number of transmitters. 

March, 14, 2002 

WallMan 

 

 

WallMan: Urban databases: Definition of type of all buildings possible 

The type of all buildings (standard / vegetation / virtual / towers) can be modified via 

the menu EDIT SET TYPE OF ALL BUILDINGS. 

ProMan: Reading of result files 

The ProMan GUI and the prediction models/network planning tools used different code 

to read prediction results. This was harmonized. Now all result files are read with the 

same code. 

- Page 23 of 28 -


March, 13, 2002 

ProMan / WallMan 

 

 

ProMan: New file format for result files 

The file format for the result files was modified. Old files can still be used (but not in 

WWW evaluation version. There only new files are possible). . 

ProMan: New file format for topographical and morpho/clutter databases 

The file format for the topographical and morpho/clutter databases was modified. Old 

files can still be used (but not in WWW evaluation version. There only new files are 

possible). . 

March, 08, 2002 

DataMan 

 

DataMan: Conversion of ASCII DTM and clutter data 

When converting the ASCII DTM and clutter databases (*.asc) the lower left corner 

can be defined either by its center or by its corner. DataMan interpreted the information 

always as corner. This is now corrected. Now DataMan reads the *.asc file and uses 

either corner or center mode depending on the specification in the *.asc-file. 

March, 06, 2002 

WallMan 

 

 

 

ProMan: Urban: Display of Channel Impulse Response: Delay of COST path 

Plotted delay of COST 231 prediction path was too high (factor 10). 

Error was limited to display of channel impulse response only. Prediction of path loss 

with COST model was correct.. 

ProMan: Output of Propagation Paths and Channel Impulse Response 

Now additionally the number of interactions for each propagation path is stored in 

STR-file. 

ProMan: New File Format for Channel Impulse Responses 

Optional a new file format (*.cir) for channel impulse responses is available. The 

channel impulse response is saved in this ASCII file for each pixel. 

March, 05, 2002 

WallMan 

 

 

WallMan: Enter new objects 

If new objects overlap existing objects and if the immediate check of new objects is 

enabled, the objects were not drawn because they produced errors. This is correct. 

But no message was generated and so the user was not always aware about the 

reason. Now a message is generated to inform the user about the overlap of the new 

objects. 

WallMan: Paste objects at original coordinates 

After Cut or Copy operation the objects in the clipboard can be pasted with the mouse 

at their new location with the command Paste. 

But for some applications (e.g. copying objects from different databases into one 

database) the user wants to have the objects of the clipboard at their original 

coordinates. This is difficult to manage with the mouse (to click to the appropriate 

coordinate) and so the new command Paste at original coordinates is introduced. 

With this command the objects are pasted at their original coordinates in the new 

document. 

- Page 24 of 28 -


March, 01, 2002 V5.40 

Release V5.40 


February, 28, 2002 

ProMan 

 

 

 

ProMan: Urban: Indoor Coverage 

Empirical indoor coverage could lead to memory problems in special scenarios if 

buildings are only partly inside the prediction area. This is now solved. 

ProMan: Urban: Topography in COST model 

Transmitter in the COST postprocessing of an IRT prediction was determined to be 

inside the building because the topographical height of the transmitter was not 

considered (but the topo-height of the building was considered). This is now fixed. 

ProMan: Urban with Empirical Indoor Coverage 

If empirical indoor coverage is selected, the buildings are no longer filled when loading 

the prediction result (only for new computations). 


WallMan 

 

 

WallMan: Cut objects 

When the feature Cut objects from the Edit menu was selected, WallMan could crash 

in special cases. This is now fixed. 

WallMan: Paste Objects 

When pasting (one or several) objects the first corner of the object with the smallest 

number (in the list of objects to be pasted) was used as reference point. This could 

lead to a strange behavior of the software if the user is not familiar with the numbers of 

the objects. To avoid this confusion, a new approach is now implemented: 

Now a box (parallel to the axis of the coordinate system) is set around all objects to be 

pasted and the lower left corner of this box is the reference point for paste operations 

(when pasting objects the user defines the location of the reference point with the 

mouse click). 


ProMan 

 

ProMan: Dynamic CDMA Network Simulation 

The dynamic CDMA network simulator is now enabled for customers leading to new 

dialogs also for classical network planning module (Best Server, CCI, Maximum 

Value,…). 


ProMan 

 

ProMan: Extensions for CNP Urban/Indoor 

Multiple Indoor Heights are now possible and the button for CNP is only enabled if 

CNP data is available in the urban database (The CNP button is only visible if the CNP 

module is purchased to avoid confusion for the user). 

- Page 25 of 28 -



WallMan 

 

 

WallMan/ProMan: IRT Indoor 

Memory for the material properties of each tile and each segment was allocated. But 

material properties are identical for all tiles of a wall. So a pointer to the properties of 

the wall/subdivision is sufficient. This saves memory for preprocessing and prediction. 

ProMan: CNP Urban/Indoor for COST 

CNP (Combined Network Planning) predictions with the COST models (COST 231 W-I 

for urban and COST Multi Wall for indoor) for the transition Urban Indoor are now 

enabled for all customers in ProMan and WallMan. 


WallMan 

 

WallMan: Projects in Recent File List 

Sometimes it was not possible to open projects via the recent file list. This is now 

corrected and works properly. 


ProMan 

 

 

ProMan: Default threshold for discrete color legend 

Default margins/thresholds for result files were modified (e.g. path loss, probability, 

terrain and morpho data) to adapt the scale to the allowed range of the result values. 

ProMan: Number of result types 

New types of result files were added for UMTS network planning (coverage probability, 

cell ID, mobile transmitter power, soft handover and user distribution). 


WallMan 

 

 

WallMan: Dongle handling 

If very large databases are preprocessed, problems with the dongle might occur 

(WallMan sends a message that the dongle is not present and stops the computation 

of the preprocessing). This is solved now. 

WallMan: Run-Button in Preprocessing Toolbar 

The function of the RUN button in the preprocessing toolbar in WallMan is now similar 

to ProMan, i.e. the current project is saved and preprocessed. If no filename has been 

defined, the user is asked to define a filename. 

January, 21, 2002 

ProMan 

 

 

ProMan: Settings file 

Error in settings file possible (some margins for display (MS power, Probability and 

Angular spread) were not set properly). Now correct initialization of all variables of 

settings file. 

ProMan: Export of (prediction) data 

User can define the format of the export file with a dialog. Keywords and additional 

data (Geometry, transmitter properties) written to the file can be defined and enabled. 

The format of the values is either line-based (each value together with the coordinates 

in one line) or matrix-based. 

- Page 26 of 28 -


January, 18, 2002 

AMan 

 

AMan: 2D Interpolation of antenna patterns 

It was possible to define a non-integer interval for the interpolation. This is now 

changed. Only integer intervals are possible. 

January, 18, 2002 

ProMan 

 

 

 

 

ProMan: Urban: COST: Number of rays on display 

After the acceleration of the COST model in Dec. 2001, the ray of the COST model 

was shown twice on the display (one ray for transition with COST model and the 

second one for the COST prediction itself). This is now reduced to a single ray. 

ProMan: Urban: COST & IRT: Topography 

At the end of the prediction, a progress output (progressbar) is added to show the 

status of the progress of the free memory (for large areas it can take some time till the 

memory is free). 

ProMan: Rural/Terrain: Ground properties for Parabolic Equations 

It is now possible to consider the ground properties with the Parabolic Equation 

method. The ground reflection is now depending on the electrical properties of the 

ground. Setti8nmgs for the ground properties are controlled via the morpho/clutter 

classes. For each morpho/clutter class the dielectric properties (relative epsilon and 

conductivity in S/m) can be defined for different frequency bands. 

ProMan: Rural/Terrain: Two ray model 

Now a two ray model is available for rural environments. Based on the direct ray 

between transmitter and receiver (if line of sight) and on the ground reflected ray (if 

possible) the received power is predicted. The superposition of both rays is either 

possible by consideration of the phase or by uncorrelated addition (power). Both rays 

(direct and ground reflected) can be enabled separately. 

January, 16, 2002 

ProMan 

 

ProMan. Urban: SRT Predictions 

Predictions with urban SRT still required additionally the *.ocd and *.ocb files if the 

COST postprocessing is enabled in the project settings. This is now changed and the 

data is read directly from the *.osb and *.osd files. 

January, 11, 2002 

ProMan 

 

ProMan: Import Data 

If the imported pixels are outside the prediction data of the display, the display is 

extended (max. 2000 pixels in each of the four directions) to show all imported pixels. 

If the distance between the pixels and the prediction area is larger than 2000 * 

resolution, the display is not automatically extended, but the user is informed. 

- Page 27 of 28 -


January, 09, 2002 

ProMan 

 

 

 

 

ProMan: Rural/Terrain 

During computation the terrain database was shifted one pixel to east and one pixel to 

north. This is now corrected. 

ProMan: Rural/Terrain: Morpho Classes 

Total re-design of consideration of Morpho / Clutter data. 

Including database editor for morpho classes (assignment of frequency bands and 

attenuations to morpho classes). 

ProMan: Coordinate system of import data (e.g. measurement data) 

More than 20 different coordinate systems are now supported for the import of data 

(e.g. WGS 84, WGS 72, WGS 66, WGS 60, Clarke, Fischer 1968, Fischer 1960, 

Bessel 1841, GRS 1980, GRS 1967, Everest, Airy, Helmert, Hough, Krassovsky,….). 

All coordinates are converted to the UTM system of the (building or terrain) database. 

ProMan: Level of import data (e.g. measurement data) 

Not only level can be imported. Additionally a conversion from GSM RX_LEV to power 

levels (in dBm) can be selected if the measurement data is only RX_LEV data. 

January, 04, 2002 

ProMan 

 

ProMan: Indoor: Delay Spread (IRT) 

Delay Spread was always computed for all pixels in total (empirical prediction) area. 

Now delay spread is only computed for pixels in ray-optical prediction area. 

January, 03, 2002 

ProMan 

 

 

 

 

 

ProMan: Colors in legend 

If the margins for the colors are higher (factor of 10) than the max. data in the file, the 

text for the margin on the display was “not computed” and the color was white. 

Now the margins can have arbitrary values. They are always written correctly on the 

display and assigned to the appropriate color. 

ProMan: Urban: Delay Spread (IRT) 

Memory problems if delay spread is not computed were solved. 

Delay Spread computation now possible with logarithmic or linear power levels of the 

rays. Default are linear values. 

ProMan: Indoor: Delay Spread (IRT) 

Delay Spread computation now possible with logarithmic or linear power levels of the 

rays. Default are linear values. 

ProMan: GUI: Definition of margins for the colors 

Settings of margins (for colors) modified. Values of the margins are not longer checked 

(Check if the values are in the range of the data was removed). So arbitrary legends 

can be defined. 

ProMan: Urban DLL: Indoor Coverage 

If the urban DLL is used and the computation of the indoor coverage is enabled in the 

project, the empirical prediction area is always enabled automatically to avoid problems 

with not computed pixels around buildings. 

- Page 28 of 28 -

WinProp Software - AWE-Communications

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?