Inputs
1. Steps to build and export a connector
1.1 Overview
In EXPORT / ADVANCED TOOLS / FORMAT area 3 steps are needed to build and export data in FMU format files:
- Select the test which will be performed for building data to be exported.
- Define the test configuration, that means the user inputs/outputs parameters needed to perform the test (settings and user inputs of the considered test)
- Define the export information
1.2 Test selection
In the current version of Altair® FluxMotor ® , one test can be selected:
- Characterization / Model / Motor / Maps
1.3 Test configuration
After selecting a test, the corresponding test inputs (settings and user inputs) must be defined. This allows to define the initial conditions for testing.
|
|
Motor Factory – EXPORT AREA – FORMAT – FMU / Test configuration for Characterization / Model / Motor / Maps | |
1 | Overview of the selected test is displayed |
2 | User inputs can be defined in the test area. |
1.4 Export information
The last step for building and exporting data in FMU format files is to define the export information.
Two inputs must be defined:
- The name of the directory in which the created files will be stored
- The destination folder in which the previous directory will be located
|
|
Motor Factory – EXPORT AREA – FORMAT – FMU / Export information | |
1 | Tab to be expanded to define export information. |
2 | Area in which the export information parameters to be defined are listed |
3 | Button to validate the previous choices |
4 | Button to finalize the export of the data files. One click opens the folder where the directory is located |
2. A C/C++ compiler is needed
2.1 C/C++ compiler / System requirements
FluxMotor requires a C/C++ compiler to perform some operation for creating FMU blocs.
Here is the list of the supported Visual Studio compilers supported:
Microsoft® Visual Studio 2019, Community, Professional, Enterprise
Microsoft® Visual Studio 2017, Community, Professional, Enterprise
Microsoft® Visual Studio 2019/2017/2015: Build Tools
the option for Windows 10 SDK must be selected
Microsoft® Visual Studio C++ 2015 (VC 14.0 Express, Community and Professional)
2.2 Access path of the C/C++ Compiler
Once the C/C++ Compiler is installed on the computer, its access path must be specified in the user’s preferences.
|
|
FluxMotor / Supervisor / User’s preferences / Location of the C/C++ Compiler | |
1 | The Preferences dialog box is opened from the FluxMotor® supervisor. |
2 | Second tab is Path Preferences. |
3 | Define the location of the C/C++ Compiler on the computer |
Here is below a list of files to select in the installation directory (path) according to the Visual Studio version that you installed:
Visual Studio 2019, Community | C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvarsall.bat |
Visual Studio 2019, Professional | C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\vcvarsall.bat |
Visual Studio 2019,Enterprise | C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Auxiliary\Build\vcvarsall.bat |
Visual Studio 2017, Community | C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvarsall.bat |
Visual Studio 2017, Professional | C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Auxiliary\Build\vcvarsall.bat |
Visual Studio 2017, Enterprise | C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvarsall.bat |
Microsoft® Visual Studio C++ 2015 Express | C:\Program Files (x86)\Microsoft Visual Studio\14.0\VC\Build\vcvarsall.bat |
Microsoft® Visual Studio C++ 2015 Community | C:\Program Files (x86)\Microsoft Visual Studio\14.0\VC\Build\vcvarsall.bat |
Microsoft® Visual Studio C++ 2015 Professional | C:\Program Files (x86)\Microsoft Visual Studio\14.0\VC\Build\vcvarsall.bat |
Microsoft® Visual Studio 2019, Build Tools | C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Auxiliary\Build\vcvarsall.bat |
Microsoft® Visual Studio 2017, Build Tools | C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Auxiliary\Build\vcvarsall.bat |