This submission was created by Valery Tchkalov and Steve Miller to help engineers understand parameterization of hydraulic valves. The included white paper, simulation models, and MATLAB scripts cover the structure of a valve model, examples of how to use optimization algorithms to tune your valve parameters so that your simulations match characteristics on manufacturer’s data sheets, and how to use experimental data to determine realistic parameter values. The power stage and control device of valves are discussed, and the models include steady-state, transient response, and frequency domain examples.
Please read the README.txt file to get started.
For an explanation of valve modeling and several of the examples contained in this submission, please watch, “Hydraulic Valve Parameters From Data Sheets and Measured Data“
Three of the examples are shown in videos:
1. Tuning hydraulic valve parameters to match flow rate characteristics:
2. Tuning hydraulic valve parameters to match transient characteristics:
3. Tuning hydraulic valve parameters to match frequency characteristics:
To find other Simscape examples, search for posts with the keyword "physical modeling"
To learn more about MathWorks Simscape Products, go to:
I think that there is an error in obj_find_prop_valve_driver_param.m on line 28.
The name of the variable used is "time_const" and must be corrected to "time_constant".
Did someone have the same issue?
Example 8a is not match to video. Let me know this problem
Data_Sheets folder as well as the PDFs underneath do not exist, which prevents the hyperlink in the Demo Script HTML from working. It would be nice if it is corrected.
I always wanted to use the values from datasheets. Thanks for sharing information
Added R2016a version.
Fixed webinar link.
Updated links to videos in "Description" field. No changes to submission files.
Added link to webinar
Added links to videos
Added additional example models that use Simulink Design Optimization and Simulink Control Design.
Added link to white paper.
Create scripts with code, output, and formatted text in a single executable document.