Home
Appendix
Reference information is provided in the appendix.
Application Programming Interface (API)
The WinProp API enables you to run WinProp simulations from within other software.
Scripts and Application Programming Interface (API)
The WinProp application programming interface (API) enables flexible integration into other software tools or post-processing tools.
WinProp API Examples
A number of small examples is available that illustrates how to use the WinProp API.
Running an Example on Microsoft Windows
To run a WinProp API example using Microsoft Windows is a four-step process.
Setting the Path Environment Variable
The executable for the WinProp API example requires libraries located in the %FEKO_HOME%\bin folder. Set the Path environment variable to point to these libraries.

Welcome
Release Notes
See what's new in the latest release.
Get Started
The WinProp Getting Started Guide contains step-by-step instructions on how to get started with WinProp.
Examples
The Altair installation directory contains a collection of examples that shows you WinProp concepts and essentials.
Introduction to WinProp
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.
Typical Workflow in WinProp
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.
WallMan
The WallMan component offers a convenient facility to generate and edit vector building databases.
TuMan
The TuMan tool enables you to generate and modify tunnel scenarios.
AMan
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.
ProMan
The ProMan component includes wave propagation models for different scenarios and network planning simulators for various air interfaces.
Methods
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).
Main Applications
In WinProp various air interfaces and applications are pre-defined: broadcasting, cellular, wireless access, WiFi, sensor networks, ICNIRP and EM compliance.
WinProp Utilities
The WinProp utilities consist of the Launcher utility and the Updater.
Appendix
Reference information is provided in the appendix.
- Application Programming Interface (API)
  The WinProp API enables you to run WinProp simulations from within other software.
  - Scripts and Application Programming Interface (API)
    The WinProp application programming interface (API) enables flexible integration into other software tools or post-processing tools.
    - Introduction to Scripting and the WinProp API
      The programming language that is integrated with WinProp is C/C++. The application programming interface (API), allows you to control WinProp from an external program.
    - WinProp API Examples
      A number of small examples is available that illustrates how to use the WinProp API.
      - Example Prerequisites
        Before starting with the WinProp API examples, confirm that the minimum requirements are met.
      - Running an Example on Microsoft Windows
        To run a WinProp API example using Microsoft Windows is a four-step process.
        Using CMake to Generate the Microsoft Visual Studio Project
        CMake is an open-source, cross-platform tool that allows you to build and package software. It requires CMakelists.txt to generate build files.
        Using the Microsoft Visual Studio Project to Compile the Executable
        After CMake was used to generate the Microsoft Visual Studio project with all dependencies (linked libraries), build the project to create an executable.
        Setting the Path Environment Variable
        The executable for the WinProp API example requires libraries located in the %FEKO_HOME%\bin folder. Set the Path environment variable to point to these libraries.
        Running the Executable and Viewing the Results
        Run the example executable and view the simulation results.
      - Running an Example on Linux
        Run a WinProp API example using Linux.
  - Application Programming Interface (API)
    The WinProp API enables you to run WinProp simulations from within other software.
- FAQ
  A collection of frequently asked questions (FAQ) relating to advanced concepts are included.
- Summary of Files
  WinProp creates and uses many different file types. It is useful to know what is stored in the various files and weather they were created by WinProp and if it is safe to delete them. The files are grouped as either native files that have been created by WinProp or non-native files that are supported by WinProp. Non-native files are often exported by WinProp even if the formats are not under the control of the WinProp development team.

Setting the Path Environment Variable

The executable for the WinProp API example requires libraries located in the %FEKO_HOME%\bin folder. Set the Path environment variable to point to these libraries.

In Microsoft Windows, view the environment variables.
Edit the Path environment variable and add %FEKO_HOME%\bin.