FMU Definition File Editor
(Standard Interface) Simulate → FMI interface → Real Time FMU Export → FMU Definition File Editor
Exports an FMU of the active vehicle model with the selected FMU Property file definition.
For the option: | Do the following: |
|---|---|
FMU Definition File | Name of the FMU Definition Property File, can be selected from disk or a database, or a new file name can be entered. |
General Tab | Lists all general FMU parameters which can be modified. |
Signal Subsystem File(s) | Lists all subsystems that are used for the FMU input and output signals. Preferably all in- and output signals selected should be generated in these assemblies so the FMU Export is vehicle assembly independent. |
Event Set File / Driver Control File | Either an Event Set File or Driver Control File (applied in File Driven Event), previously created, can be selected. When a Driver Control File is select, the Road Property file needs to be selected in addition. |
Road Data File | The road property file to be used by the vehicle model in the FMU. Enter the name of a file that contains road data information. The tire subsystems use this information to calculate the tire/road interaction forces. Tips on Entering File Names in Text Boxes. You can also use a 3D road in this context. Make sure that the vehicle remains on the road, because 3D roads are not as wide as 2D flat roads. |
Event | Select an event within the Event Set File that you specified |
 | Import and visualize road graphics from file. |
 | Remove road or path graphics. |
 | View road / path file in info window. |
 | Edit road / path file in road builder or text editor. |
Input Signals | Enter names of state variables that you want to use as plant inputs. Select From Pinput to enter state variables from existing plant inputs. Only available for new/existing controls plant selection. These are automatically picked up from the control systems in case of mechatronics system. |
Output Signals | Enter names of state variables that you want to use as plant outputs. Select From Poutput to enter state variables from existing plant outputs. Only available for new/existing controls plant selection. These are automatically picked up from the control systems in case of mechatronics system. |
Solver Setting File(s) | Select one or more files (extension .ssf) defining the solver settings to be temporarily applied for this simulation (optional). Note: Solver settings files are applied in the order specified, so if multiple .ssf files contain the same solver settings, the last file in the list determines those settings. |
 | Opens the Solver Settings File (extension .ssf) editor dialog box. |
 | Clicking this button opens a dialog where model parameters can be selected for export. Parameter variables, hard points, mass properties, UDE design variables and property files are supported. Note: dSPACE does not support modification of string parameters in the FMU. |
Real Time Tab | Lists all specific Adams Car Real Time parameters which can be modified. |
FMI Parent | SIMWB, SCALEXIO or None can be selected. The FMU can be output for Simulation WorkBench(SIMWB), SCALEXIO or any generic FMI Parent. |
Communication Mode | DIRECT, PIPE and TCP/IP can be selected. For Simulation Workbench, the communication mode is fixed to DIRECT. For SCALEXIO, the communication mode is fixed to TCP/IP. PIPE/TCP/IP is used for an Adams parent-child simulation. |
Remove Sensors | When using the vehicle in open loop configuration (steering, brake, throttle are fmu inputs), the model sensor elements are not required in general. Removing those will increase solver performance. Note: If you define a simulation event with multiple mini-maneuvers, you need to set Remove Sensors to No, otherwise only the first mini-maneuver will be executed. |
Remove Requests | Requests are not used with the default real time mode setting, but for creating smaller FMU’s one can remove the requests from the model. |
Remove Switch Parts | Switch parts will be removed to increase solver speed. |
Remove Interface Parts | Interface parts will be removed to increase solver speed. |
Remove Dummy Parts | The Adams solver will remove the dummy parts from the internal model. |
Steering (Cut-Off Filtering Frequency Inputs) | When having a signal subsystem (like Controls_IO) having a build-in low-pass frequency filter specified by a pvs_cut_off_freq_steer parameter, this parameter will be adjusted with this input. |
Throttle (Cut-Off Filtering Frequency Inputs) | When having a signal subsystem (like Controls_IO) having a build-in low-pass frequency filter specified by a pvs_cut_off_freq_throttle parameter, this parameter will be adjusted with this input. |
Brake (Cut-Off Filtering Frequency Inputs) | When having a signal subsystem (like Controls_IO) having a build-in low-pass frequency filter specified by a pvs_cut_off_freq_brake parameter, this parameter will be adjusted with this input. |
Steering Parameter A (Exponential Smoothing Input) | Exponential smoothing can be applied to the steering angle input, parameter A is the first parameter, see Exponential Smoothing Steering Input. |
Steering Parameter G (Exponential Smoothing Input) | Exponential smoothing can be applied to the steering angle input, parameter G is the first parameter, see Exponential Smoothing Steering Input. |
Support for Repositioning Assembly | Check this box when repositioning of the assembly is desired. This option works with the definition of the environment variables VIDRIVESIM_VEHICLE_USER_LOCATION or ADAMS_VEHICLE_USER_LOCATION and VIDRIVESIM_VEHICLE_USER_ORIENTATION or ADAMS_VEHICLE_USER_ORIENTATION in the realtime environment. Defining the road property file through environment variable VIDRIVESIM_ROAD_PROPERTY_FILE or ADAMS_ROAD_PROPERTY FILE, the vertical position is automatically computed by evaluating the road. Using these environment variables allows you to change road property file without changing the Adams model files, also when not repositioning the assembly. If both environment variables are defined, VIDRIVESIM_* takes precedence. E.g.: ADAMS_VEHICLE_USER_LOCATION = 10;0 - means moving the vehicle by 10 meters with respect to the road in X direction and automatically computes the vertical position by evaluating the road. ADAMS_VEHICLE_USER_ORIENTATION = 3.14159;0;0 - means a yaw rotation of the road by 180 degrees. |
Tire Convergence Forces for Statics | Adds ghost tire forces to improve Adams Solver Statics convergence. These forces will not change simulation results in dynamics. |
Header Tab | Lists the comments in the header |
Header Text | The text in the comments section of the header of the fmd file |
Target | Location of the FMU property tile, ‘Directory’ or ‘Database’. |
Info | If ‘Target’ has been selected the Info button shows information about the available databases. |
Select | If ‘Directory’ has chosen, another directory location with the browser. |
Add to FMU | Use this field to select the files that will be copied/bundled into the FMU. When an FMU ‘consumer’ application loads the Adams FMU, these additional files will be present in the same working directory (‘resources’ folder inside the FMU) as the Adams model files. |
Encrypt Model | If selected, the Adams model will be encrypted and not readable for the user. Note that exposing parameters in combination with encryption is not possible. Solver will not allow a LIST argument on an object command in encrypted models. SCALEXIO FMUs can not be encrypted at the moment. |
Save | For saving the current editor inputs in the specified FMU property file |