Week 1 : Exploring the GUI of GT-POWER

Assignment 1: Exploring the GUI of GT-Suite

Question 1:

The answer of this question has been divided into 4 subsections as follows;

Introduction
Main page GUI description
Brief explanation of the modules available
Workspace GUI description

A] Introduction:

GT-Suite is a simulation software that is extensively used in the automotive industry, and is commonly known for its automobile powertrain simulation module GT-Power. Upon installation (v2021 used) the following tools are installed:

GT-ISE
COOL3D
GEM3D
VTDESIGN
GT-POST
We will focus on the GT-ISE tool form now onwards. This tool, also known as the main model builder is the place where all the simulation models will be built and tested. It is the main tool in the above list mentioned. The tools like COOL3D, GEM3D are used to render HVAC related and other 3D CAD models into 1D. VTDESIGN is specially reserved for valvetrain design.

GT-POST is a post processing tool that is provided by GT. To understand better, we have to understand that any simulation activity is divided into 3 stages, i.e., Pre-processing, solver, and post-processing. GT-ISE handles the first two stages, while GT-POST is a dedicated tool for the latter. It allows the user to dive deeper into the obtained results and conduct his/her analysis work even better.

So, to conclude, consider the analogy a cabinet team of the government. Any such cabinet consists of ministers who advice and guide the Prime Minister/ President, work with him, have their own individual tasks and thus ensure a smooth overall functioning of the government. Similarly, here GT-ISE is the Prime Minister/ President, and the other mentioned tools aid in its main operations like ministers.

Now we will explore the main page GUI.

B] Main Page GUI:

When one opens the GT-ISE tool freshly, a window shown in Fig 1. will appear. The window can be divided into 3 subsections:

Feed: this section covers the much of the page and is very helpful to keep in touch with current happenings related to this software. One can find upcoming events, conferences, etc that might be sponsored by GT. Sort of a news feed in any social media app.
Quick Buttons: This section contains quick buttons for starting up any project, subassembly, etc. We mostly use these buttons to quickly setup a project.
Basic panel: This layout is much like that of any other application like MS Word, PowerPoint that we use often, and thus does not deserve much attention. Although, one needs to be know about the great learning resources one can find in this section. Awesome tutorials, ready-to-use models, proper guides, and in-detail documentation about each model, the theory behind it, description of the models used can be found in the ‘Examples’, ‘Tutorials’, and ‘Manuals’ sections on the centre-left side.

To create a new project, one needs to click on the ‘Model’ button present in the ‘Quick Buttons’ section. This opens up a dialog box where ‘GT Model’ is generally preselected. After we say ‘Next’ a licenses section opens up where all the available modules can be seen.

C] Brief Description of the Available Modules

Fig 2. Shows the list of modules available under the GT-Suite license. This selection itself covers all the modules that are present in the GT-Suite software. Other license selections like GT-Power, GT-PowerLab just select some of the modules available in the GT-Suite license. Such a flexible selection allows for cost saving in case of specific requirements.

The brief description of the modules available is as follows:

Engine Performance and Acoustics: Useful to analyse engine power, efficiency, emissions, and noise by performing simulations
Exhaust Aftertreatment: Used to model aftertreatment systems and analyse their performance
Electrical: Covers a broad simulation role right from electrical connections, electronic components right up to battery storage and electrical motors for EVs
Cooling Systems and Thermal Management: Models the behaviour of engine/ motor cooling systems
Air Conditioning/ Waste Heat Recovery: Useful to model vehicle AC systems and devices used to recover waste heat from the respective sources in the vehicle.
Fuel Injection: Covers modelling aspects like fuel flow, resistance to flow, injector actuation and controls and much more
Hydraulics and Pneumatics: Simulates the respective components in the vehicle.
Lubrication Circuits: Models various lubrication aspects of engines, pumps, and also useful in evaluating bearings and oil properties.
Vehicle and HEV Fuel Economy and Performance: Helps capture vehicle dynamics, model controls and simulate HEVs.
Transmission and Shift quality: Models the transmission performance and its dynamics
Cranktrain and Crankshaft Dynamics: Models the structural aspects of the crankshaft and cranktrain
Valvetrain Kinematics and Dynamics: Helps model the performance of the valvetrain. Has to be combined with VTDESIGN
Timing and Front End Drive Systems: Used to model the gear, chain, belt based systems in the vehicle.
Engine Real Time: Modelling of the engine
Aerospace Systems: Used to model aerospace related components.

Finally, we will explore the Workspace GUI

D] Workspace GUI Description:

Figure 3 shows the main workspace in GT-ISE where all the models are built. This GUI can be divided into 3 sections as:

Main Workspace
Tree section
Header
The main workspace is the space where the representations of the required models will be built. Components have to be assembled in the space to build the model. The functioning of this is very similar to that of SIMULINK

The tree section is a place where the components, references used in the main workspace are displayed in a detailed, tree like manner. The main parents of each tree are templates which cover broad areas such as Flow, Mechanical mentioned in the figure.

Under each template there are again 3 sections: Components, References, and Connections. They represent the references, connections, and the component template used. Now, from each of these templates, objects are created and from these objects, the components are created which are placed in the main Workspace.

Finally, the header section again contains generic options like save, etc. Some notable mentions though are:

Template library: Used to browse through different templates available
Model Setup: Used to complete the pre-processing stage
Optimisation: Used in performing optimization activities
Run: From here the model is run and also helps in loading the post processing tool GT-POST.

Question 2:

For Time Control Flag (Fig_4):

Path: GT-ISE Main Workspace> Model Setup> Run Setup> Time Control> Option 1

For Time Step and Solution Control (Fig_5):

Path: GT-ISE Main Workspace> Model Setup> Run Setup> Flow Control> Option 2

For Integrator/ Solver Type (Fig_6):

Path: GT-ISE Main Workspace> Model Setup> Run Setup> ODEControl> Option 2

Question 3:

The intercooler tutorial explored is a part of the 6-cylinder turbocharged DI engine. Intercoolers are generally used after the turbocharged to cool down the compressed air, which gets heated during the compression process in the turbocharger before being sent to the engine.

Such cooling has a straight and simple advantage: It cools down the air mass before it enters the cylinder. Cooling of the air mass leads to increase in its density, which in turn will result in more air being supplied to the engine. This supply finally will increase the engine’s capacity to produce power by burning more fuel in the increased air mass.

Heading off to the Intercooler tutorial (ref Fig_7), we see that the whole model is built in the workspace using the following blocks:

Inlet-1: Modelled using the BoundaryFlow template to signify that compressed air is being sent from the turbocharger.
cooler-in-1/2: Modelled using the PipeRound template as representative of the path the compressed air would take.
cooler-fsplit-1/2: Modelled using the FlowSplitGeneral template to account for the expansion of the compressed air that can occur in the pipes.
nocond-1/2: Modelled using the OrificeConn connection template in order to measure the mass flow rate into and out of the intercooler.
cooler-1: Modelled using the PipeRound template and acts as the intercooler.
Outlet-1: Modelled using the BoundaryPressure template to set the output state of the compressed gas.
Now we will explore the settings used in the pre-processing steps:

Run setup: Refer Fig_8. Apart from the setting that were used in the video, only 2 settings very here. Once is the time flag, which is set to be continuous instead of periodic, given the fact that cooling is considered here to be a continuous process, ignoring the pulsating behaviour of the exhaust gases. Secondly, instead of number of simulation cycles, simulation time has been used.
Advanced setup: Refer Fig_9. All the default settings have been used.
Plot setup: Refer Fig_10. All default settings have been used.
Output setup: Refer Fig_11. All default settings have been used.

Question 4:

Given:

Diameter of cooler inlet, outlet pipe: 50mm
Length of charge air cooler (CAC): 1000mm
Inlet mass flow rate: 1200 kg/h at 100 degC
Outler pressure: 2 bar at 30degC
Find:

Average heat transfer at CAC
Pressure drop across CAC
Solution:

The main model is as presented in Fig_7. We will first set the given conditions in the model.

For the diameter settings for inlet and outlet pipe and length of CAC, refer Fig_12:

For the inlet mass flow rate settings, refer Fig_13:

For the outlet pressure settings, refer Fig_14

After doing these settings, rest of the default settings have been kept as is. As visible in Fig_15, the average heat flux to walls has been found out to be 0.381 kW/m^2

For the pressure drop, refer Fig_16, which is found out to be 3.83e-6 bar.

Thus the problem has been solved.