WinProp is a complete suite of tools in the domain of wireless propagation and radio network planning. With applications
ranging from satellite to terrestrial, from rural via urban to indoor radio links, WinProp’s innovative wave propagation models combine accuracy with short computation time.
View the typical workflows when working with propagation simulations in specific scenarios, how to add a network planning
to a propagation simulation, include a receiver pattern, set up a time-variant scenario, include multiple-input multiple-output
(MIMO) at both the base station and the mobile station, connectivity analysis of sensor networks and optimization.
Use AMan to generate, edit and analyze a single antenna. Superimpose multiple antennas radiating similar signals to determine
the actual antenna pattern while taking into consideration the local environment.
WinProp includes empirical and semi-empirical models (calibration with measurements possible), rigorous 3D ray-tracing models
as well as the unique dominant path model (DPM).
In WinProp various air interfaces and applications are pre-defined: broadcasting, cellular, wireless access, WiFi, sensor networks,
ICNIRP and EM compliance.
The Launcher utility is a single application that allows you quick access to the shortcuts for the Feko components, WinProp components, newFASANT, WRAP components, documentation, Altair license utility and updating parallel credentials. Pin the application to the taskbar for quick launching.
The feko_update_gui utility and the feko_update utility allows you the flexibility to install an update containing features, minor software enhancements and bug fixes
on top of an existing base installation for Altair Feko(which includes Feko, newFASANT and WinProp).
Each major release, upgrade or update is assigned a version number. A version number contains a unique set of numbers assigned
to a specific software release for identification purposes. You can determine from the version number if its an initial
release, update or upgrade.
Updating and upgrading refers to the process of installing a new version containing features, minor software enhancements
and bug fixes on top of an existing base installation.
The feko_update_gui utility and feko_update utility (GUI and command line) use the system proxy by default, although it may be changed or the use of a proxy
suppressed.
Create a local Feko update repository to allow users to update without internet access or to limit the list of update versions that users
can use. Local update repositories can also be used to reduce the amount of data being downloaded by downloading
a repository once and making it available to many local machines or compute clusters.
The feko_update_gui utility and the feko_update utility allows you the flexibility to install an update containing features, minor software enhancements and bug fixes
on top of an existing base installation for Altair Feko(which includes Feko, newFASANT and WinProp).
Update (or upgrade) from a local repository using the graphical user
interface.
Open the Updater using the Launcher utility.
On the Altair Feko update dialog, click the
Settings tab.
Under Update from, click Local
repository to update from a local repository.
Under Local repository, select one of the
following:
If the local repository contains extracted archives or multiple zipped
archives, select Folder (with extracted or zipped
archives) and specify the folder.
The path for the local
Feko update repository must be an
absolute file path which can point to an unmapped network share
(Windows), mapped (mounted) network share or a directory on a local
drive.
Warning: Point the local repository path to the
root folder of the updates.
Example: The Feko updates for the Windows and Linux
platforms were extracted and merged to
C:\Updates. The path to the
local repository points to
C:\Updates.
If the local repository contains a single zipped archive, select
File (zipped archive) and specify the zip
file.
Click Save to save the local repository settings.
Update or upgrade to a new version.
Trouble:Error 16700: Unable to find the file 'XX/YY/manifest.xml.gz'
in the local repository.
Error 16700 indicates that
the path to the local repository is incorrect. The path must point to the root
folder of the local update repository and the folders should not be
modified.