Model Settings
Description of the Model Settings dialog and its options.
| Option name | Description |
|---|---|
| Device | Specifies for which device the schematic is intended. Currently supported device settings include HIL402, HIL101, HIL404, HIL602+, HIL604, HIL506, HIL606, and VHIL+. |
| Configuration id | Specifies the configuration ID for the selected device. Available configurations are determined by the selected Device. |
| Device table | Shows a table with details for the selected device. For more information, see Device Configuration Table. |
| Autodetect settings | Choose device and configuration ID based on the connected device. |
| Limit device analog outputs to +/- 5 V | By checking this option, the analog outputs are limited to +/- 5 V. Otherwise, analog outputs are in range +/- 10 V. |
| Reset analog outputs on simulation stop | By checking this option, the analog outputs can be forced to reset to a pre-determined value when the simulation stops. Otherwise, outputs will maintain the last recorded value at simulation stop. |
| Reset analog outputs value | Specifies the reset values when Reset analog outputs on simulation stop is checked. Available values are Offset Value and Zero Volts. |
| Reset digital outputs on simulation stop | By checking this option, the digital outputs can be forced to reset to 0 when the simulation stops. Otherwise, outputs will maintain the last recorded value at simulation stop. |
| Enable VHIL analog/digital IO loopback | Enable use of analog and digital IO on Virtual HIL. The analog/digital IO is looped back to the appropriate input. |
| Enable DMA | Enables DMA transfers between CPU and FPGA. Can improve performance of models with high CPU utilization. This is an experimental feature, and can break some models. Available for HIL101, HIL404, HIL506, HIL606 |
| Option name | Description |
|---|---|
| Discretization method |
Choose the discretization method for state space equations of the model. |
| Simulation step |
If the simulation step is set to 'auto', the model will be simulated with the smallest acheivable simulation time step from the predefined list. |
| Simulation rate scaling |
The discretization step is calculated as simulation step/scaling. |
| Calculation method |
There are two available algorithms for state space matrix calculation of the model. By default, systematic elimination is used. In some extraordinary cases, constraint matrix algorithm is required. |
| Enhance stability |
Cancels out the positive poles of the system due to numerical calculation errors, which ensures the stability of long simulation runs. |
| Enable GDS oversampling |
Enables high resolution sampling of converter control inputs (gate drive signals). Recommended for switching frequencies exceeding 4 kHz. When enabled, it adds one additional simulation step of latency measured from digital inputs to analog outputs. |
| Enable coupling stability analysis | Enable core coupling stability analysis. |
| Set Ground component scope to core | If this option is checked, ground components from different cores will not be shorted. |
| Option name | Description |
|---|---|
| Place code section in |
Target memory selection for the code program sections. |
| Place data section in |
Target memory selection for the data program sections. |
| Compiler optimization level |
Choose the level of optimization for the user CPU. If you select to compile a SP (Signal Processing) model with a changed optimization level, it is highly recommended to manually restart the HIL before loading the model. |
| Real type mapping | Choose the real type precision for the user CPU. |
| CPU mapping option |
Defines the CPU partitioning algorithm mode of operation:
|
| Execution rate 1 | Define the fast execution rate for the system signal. |
| Execution rate 2 | Define the slow execution rate for the system signal. |
| Compiler optimization level | Choose the level of optimization for the system CPU. |
| Tunable parameters |
Global switch for the behavior of tunable parameters in supported components:
|
| Compiler type |
Choose what compiler to use when compiling the Signal Processing part of the model. Available options are:
|
| Dynamic Model Stimulation |
Choose whether to enable dynamic model stimulation feature:
|
| Option name | Description |
|---|---|
| PSIM install dir | Defines path to the PSIM installation that will be used for the Model Converter functionality. |
| Option name | Description |
|---|---|
| Solver type | Chooses the solver type. DAE solver converts model equations into differential-algebraic equations (DAEs). ODE solver converts model equations into ordinary differential equations (ODEs). |
| Integration method | Chooses the method for numerically solving differential equations of the model. |
| Maximum simulation step | Specifies the maximum step that an integration method is allowed to take during an integration. |
| Initial simulation step | Sets the value of the initial step that an integration method attempts. |
| Data sampling rate | Defines the rate at which the measurement data is logged in TyphoonSim Scope component. |
| Absolute tolerance | Specifies the largest acceptable absolute error around zero. |
| Relative tolerance | Determines the largest acceptable relative error that an integrator is allowed to make at each step. |
| Switches On resistance | Determines the resistance value when a switch is on. Applicable only to DAE solver. |
| Diode Von | Determines the diode turn-on threshold voltage. Applicable only to DAE solver. |
| Option name | Description |
|---|---|
| Export directory | Define the directory where C code will be exported. |
| int | Define type mapping for int Typhoon type. By default int is mapped to int C type. |
| uint | Define type mapping for uint Typhoon type. By default uint is mapped to unsigned int C type. |
| real | Define type mapping for real Typhoon type. By default real is mapped to double C type. |
| Option name | Description |
|---|---|
| Report inconsistent usage of terminal feedthrough as | You can select in which way errors related to terminals' feedthrough in C functions will be reported. When a warning is selected, compilation of the model will continue and even though there is a possibility that your model will work on a HIL device, it also may lead to incorrect results. When an error is selected, compilation will stop and you will have to make corrections to your code. |
More rules on how to write C code can be found in the Rules for writing C code section.