Week-3 Challenge: ADVISOR Tool
AIM: To simulate the given data and conditions for an EV using Advisor Tool in MATLAB.
THEORY:
What is ADVISOR TOOL and its benifits;
ADVISOR, NREL’s ADvanced VehIcle SimulatOR, is a set of model, data, and script text files for use with Matlab and Simulink. It is designed for rapid analysis of the performance and fuel economy of conventional, electric, and hybrid vehicles. ADVISOR also provides a backbone for the detailed simulation and analysis of user defined drivetrain components, a starting point of verified vehicle data and algorithms from which to take full advantage of the modeling flexibility of Simulink and analytic power of MATLAB.
You may benefit from using ADVISOR if you want to:
- estimate the fuel economy of vehicles that have not yet been built
- learn about how conventional, hybrid, or electric vehicles use (and lose) energy throughout their drivetrains
- compare relative tailpipe emissions produced on a number of cycles
- evaluate an energy management strategy for your hybrid vehicle’s fuel converter
- optimize the gear ratios in your transmission to minimize fuel use or maximize performance, etc.
The models in ADVISOR are:
- mostly empirical, relying on drivetrain component input/output relationships measured in the laboratory, and
- quasi-static, using data collected in steady state (for example, constant torque and speed) tests and correcting them for transient effects such as the rotational inertia of drivetrain components.
THEORY:-
What is ADVISOR & who might benefit from using it?
ADVISOR, NREL’s ADvanced VehIcle SimulatOR, is a set of model, data, and script text files for use with Matlab and Simulink. It is designed for rapid analysis of the performance and fuel economy of conventional, electric, and hybrid vehicles. ADVISOR also provides a backbone for the detailed simulation and analysis of user-defined drivetrain components, a starting point of verified vehicle data and algorithms from which to take full advantage of the modeling flexibility of Simulink and analytic power of MATLAB.
You may benefit from using ADVISOR if you want to:
- estimate the fuel economy of vehicles that have not yet been built
- learn about how conventional, hybrid or electric vehicles use (and lose) energy throughout their drivetrains
- compare relative tailpipe emissions produced on a number of cycles
- evaluate an energy management strategy for your hybrid vehicle’s fuel converter
- optimize the gear ratios in your transmission to minimize fuel use or maximize performance, etc.
The models in ADVISOR are:
- mostly empirical, relying on drivetrain component input/output relationships measured in the laboratory, and
- quasi-static, using data collected in steady-state (for example, constant torque and speed) tests and correcting them for transient effects such as the rotational inertia of drivetrain components.
ADVISOR was preliminarily written and used in November 1994. Since then, it has been modified as necessary to help manage the US DOE Hybrid Vehicle Propulsion System subcontracts. Only in January 1998 was a concerted development effort was undertaken to clean up and document ADVISOR.
Since then, over 4500 individuals have downloaded one or more versions of ADVISOR, including all of the OEMs and major suppliers. About 2/3 of the users are from industry and 1/3 from universities. A shortlist of major ADVISOR users includes:
- DaimlerChrysler
- Ford Motor Company
- General Motors Corp.
- Delphi Automotive Systems
- Visteon and hundreds of others
Capabilities and Intended use
ADVISOR uses basic physics and measured component performance to model existing or future vehicles. Its real power lies in the prediction of the performance of vehicles that have not yet been built. It answers the question “what if we build a car with certain characteristics?” ADVISOR usually predicts fuel use, tailpipe emissions, acceleration performance, and gradeability.In general, the user takes two steps
1.Define a vehicle using measured or estimated component and overall data.
2.Prescribe a speed versus time trace, along with road grade,that the vehicle must follow
ADVISOR then puts the vehicle through its paces, making sure it meets the cycle to the best of its ability and measuring (or offering the opportunity to measure) just about every torque, speed, voltage, current, and power passed from one component to another.
ADVISOR will allow the user to answer questions like:
- Was the vehicle able to follow the speed trace?
- How much fuel and/or electric energy were required in the attempt?
- How does the state-of-charge of the batteries fluctuate throughout a cycle?
- What were the peak powers delivered by the drivetrain components?
- What was the distribution of torques and speeds that the piston engine delivered?
- What was the average efficiency of the transmission?
By iteratively changing the vehicle definition and/or driving cycle, the user can go on to answer questions such as:
- At what road grade can the vehicle maintain 55 mph indefinitely?
- What’s the smallest engine I can put into this vehicle to accelerate from 0 to 60 mph in 12 s?
- What’s the final drive ratio that minimizes fuel use while keeping the 40 to 60 mph time below 3 s?
- What is the fuel economy sensitivity to mass, aerodynamic drag, or other vehicle or component variations?
ADVISOR’s GUI and other script files answer many of these questions automatically, while others require some custom programming on the user’s part.
Because ADVISOR is modular, its component models can be relatively easily extended and improved. For example, an electrochemical model of a battery, complete with diffusion, polarization, and thermal effects, can easily be put into a vehicle to cooperate with a motor model that uses a measured efficiency map. Of course, developing new, detailed models of drivetrain components (or anything else, for that matter) requires an intimate familiarity with the environment, MATLAB/Simulink.
LIMITATIONS:-
Primarily for analysis, not design
ADVISOR was developed as an analysis tool, and not originally intended as a detailed design tool. Its component models are quasi-static, and cannot be used to predict phenomena with a time scale of less than a tenth of a second or so. Physical vibrations, electric field oscillations, and other dynamics cannot be captured using ADVISOR, however recent linkages with other tools such as Saber, Simplorer, and Sinda/Fluent allow a detailed study of these transients in those tools with the vehicle level impacts linked back into ADVISOR.
System Requirements
ADVISOR has been developed and tested in Release 12.1 (MATLAB 6.1 and Simulink 4.1), available from The Mathworks. The Mathworks software runs on multiple platforms including Macintosh, UNIX, and PCs. Contact The Mathworks at www.mathworks.com for more information. ADVISOR files, however, have been tested using only the PC platform with Windows 2000 (it should still work with NT, and Win 98 as well). If you have success using other platforms (such as UNIX) we would love to hear about it, but in general, we do not support other platforms at this time.
Additional features for users with VisualDOC
Additional features for users with GCTool
-steps to execute the Advisor tool in Matlab
-download the advisor tool zip file from given sources, and extract the zip file (source:-https://sourceforge.net/projects/adv-vehicle-sim/)
-after that open Matlab and change the path to where the advisor tool is located.
-then open the advisor.m Matlab code file which is present in the working directory.
-after that advisor.m code file will open the type advisor in the command window and run the program this window will appear
1.For EV_defaults_in file, if cargo mass is 500 kg with all other default conditions, can the vehicle travel for 45 km with FTP drive cycle?
Answer:
LOAD FILE: EV_defaults_in ; CARGO MASS: 500KG
DRIVE CYCLE: CYC_FTP ; NO. OF CYCLES: 3
CONCLUSION: Thus we can see that for 3 number of cycles at the given conditions,the vehicle can travel for only 41.4km
If we increase the number of cycles,then the vehicle can travel above 45km.
2. In the above case, try changing the battery capacity and repeat the simulation.
Answer:
IN the above simulation we have changed the battery capacity from 25 to 50V.
-comparing the results for different battery mods for no of cycle
1) battery mods=26
| no of cycles | voltage(v) | distance traveled (km) | battery weight |
| 1 | 321 | 17.8 | 286 |
| 2 | 321 | 35.5 | 286 |
| 3 | 321 | 42.7 | 286 |
2) battery mods=28
| no of cycles | voltage(v) | distance traveled (km) | battery weight |
| 1 | 345 | 17.8 | 308 |
| 2 | 345 | 35.5 | 308 |
| 3 | 345 | 46.3 | 308 |
2) battery mods=30
| no of cycles | voltage(v) | distance traveled (km) | battery weight |
| 1 | 370 | 17.8 | 330 |
| 2 | 370 | 35.5 | 330 |
| 3 | 370 | 49.1 | 330 |
i)Battery modules 28 with 3 drive cycles we cover 46.3 km
ii)Battery modules 30 with 3 drive cycles we cover 49.1 km
conclusion:-
-while changing battery modules till the 2 drive cycle the distance traveled is the same.
-changing battery modules till 3 drive cycle we get a change in distance traveled.
-to cover 45 km we need 28 modules 345-volt battery and 30 modules 370-volt battery is needed
We can see that, by increasing the battery capacity,the vehicle can travel for more than 53kms in the same number of drive cycles.
similarly,when we decrease the battery capacity , the vehicle travels a lesser distance.
3. Perform gradeability test with PRIUS_Jpn_defaults_in file
Compare your results in table and conclude.
Answer:
SPEED: 50mph
fully electric;
hybrid;
IC Engine;
At 20mph,
Gradeability for fully electric,hybrid and IC engine vehicles are 19.8,19.8& nil% resp.
COMPARISSION TABLE:
-comparing the results
a) for 10 sec
| sr no | speed (mph) | speed(kmph) | gradeability |
| 1 | 25 | 40.2 | 16.5 |
| 2 | 35 | 56.3 | 13 |
| 3 | 45 | 72.4 | 10.7 |
| 4 | 55 | 88.5 | 8.9 |
-comparing the results
a) for 20 sec
| sr no | speed (mph) | speed(kmph) | gradeability |
| 1 | 20 | 32.2 | 22.9 |
| 2 | 30 | 48.3 | 17.7 |
| 3 | 40 | 64.4 | 14.6 |
| 4 | 50 | 80.5 | 12.4 |
-from the above tables we can conclude that as vehicle speed increases the gradeability decreases
RESULTS:-
1) Vehicle failed to travel 45k with ftp_drive_cycle at the end of 3rd cycle the maximum distance traveled by vehicle was 41.4 km and the battery was drained
2) To cover 45 km we need 28 modules 345-volt battery and 30 modules 370-volt battery is needed
3) Gradeability at different speed and duration is calculated above
CONCLUSION:-
1) As no of cycles increases with the distance traveled the state of charge decreases
2) By adding battery mods with increase voltage we can achieve the defined distance withing the cycles before the battery gets drains
3)we can conclude that as vehicle speed increases the gradeability decreases.
(Note:-All the related screenshots attached below)