4.Mechatronics Workshop KCC Day1 Session4.pdf

Mechatronics for the 21st Century

K. Craig 1

Mechatronics Master Class Schedule

Day 1

Day 2

Day 3

Session 1

Mechatronics and Innovation

Modeling & Analysis of Dynamic Physical Systems

High-Performance Mechatronic Motion Systems

Session 2

Human-Centered Design

Session 3

Model-Based Design

Session 4

Mechatronic System Design

Automotive Mechatronics

Control System Design: Feedback, Feedforward, & Observers

Web-Handling Mechatronic Applications Fluid Power Mechatronic Applications K. Craig 2

Mechatronic System Design • What makes a system a mechatronic system? • How can an engineer mechatronify a traditional system? • How are mechatronic systems designed? What are the essential elements in the design process? • Who comprises a mechatronic system design team? Who is the leader? • What is the why of mechatronics, the how of mechatronics, and the challenges of mechatronics for a company?

K. Craig

3

K. Craig

4

K. Craig

5

Balance: The Key To Success

K. Craig

6

K. Craig

7

K. Craig

8

K. Craig

9

K. Craig

10

The WHY of Mechatronics • Companies must: • have the ability to increase the competitiveness of their products through the use of technology. • be able to respond rapidly and effectively to changes in the market place. • Mechatronic strategies: • support and enable the development of new products and markets. • enhance existing products. • respond to the introduction of new product lines by a competitor. K. Craig

11

The HOW of Mechatronics • The achievement of a successful multidisciplinary design environment essentially depends on the ability of the design team to innovate, communicate, collaborate, and integrate. • Indeed, a major role of the multidisciplinary systems engineer is often that of acting to bridge the communications gaps that can exist between more specialized colleagues in order to ensure that the objectives of collaboration and integration are achieved. • This is important during the design phases of product development and particularly so in relation to requirements definition where errors in interpretation of customer requirements can result in significant cost and time penalties. K. Craig

12

The CHALLENGE of Mechatronics • Master the future increase of system complexity • Innovative Excellence • Yielding new products with distinctive functionality, better quality and/or a cost advantage • Operational Excellence • Effective and highly efficient processes for product design, manufacturing, and calibration K. Craig

13

K. Craig

14

K. Craig

15

K. Craig

16

Trade-Offs & Performance Limitations

K. Craig

17

K. Craig

18

K. Craig

19

K. Craig

20

K. Craig

21

Best-In-Class Companies • Mechatronic systems significantly outperform legacy systems, but they are much more complex. • Close cooperation among multiple design disciplines is required and design processes must evolve. • Combining the right design process and tools is essential. • Best-in-Class Companies can be identified by examining five key product development performance criteria: • • • • •

Revenue Product Cost Product Launch Dates Quality Development Costs K. Craig

22

• Best-in-Class Companies not only perform better, but perform 2 to 3 times better on every criterion. Why? • Best-in-Class companies are able to achieve these superior results by doing a much better job: • Communicating design changes across disciplines (3 times better) • Partitioning the multiple technologies present and allocating design requirements to specific systems, subsystems, and components (3 times better) • Validating system behavior with modeling and simulation (virtual prototyping) of integrated mechanical, electrical, and software components (7 times better) K. Craig

23

• Regarding Simulation and Virtual Prototyping • A system can be tested as it is being designed and access to the innermost workings is available at every phase of the design process. • When employed early in the design process, modeling and simulation provides an environment in which a system, with its subsystems and components, can be tuned and optimized, and critical insights gained, even before hardware can be built. • After the basic system is locked down, simulation can be employed to verify intended system operation, varying parameters in ways that would otherwise be impossible with physical prototypes. • System integration can begin before physical hardware is available, including embedded software. K. Craig

24

• It is rare to find electromechanical devices without some kind of embedded system. The intelligence from an embedded system delivers enhanced performance, reduced energy consumption, better reliability, and safer operation, which are key differentiators and value drivers. • However, the benefits of an embedded system come at a price. The interaction between hardware and software becomes more complex and managing this complexity can prove challenging. • In most traditional design approaches, engineers test software on hardware prototypes, addressing software validation very late in the development process. Errors found at this late stage create costly delays. Errors relating to incomplete, incorrect, or conflicting requirements may even necessitate a fundamental redesign. K. Craig

25

• Model-Based System Design simplifies the development of multidisciplinary engineering systems by providing a common environment for design and communication across different engineering disciplines. • Model-Based System Design extends the computeraided engineering world with an additional perspective on system-level design. It incorporates the dynamics and performance requirements needed to properly describe the system. It is software driven! Engineers can continually test the design as it evolves. It automates code generation for the embedded system by eliminating the need to hand code open-loop and closedloop control algorithms.

K. Craig

26

• The Benefits of Model-Based System Design then are: • The capability to inexpensively design and test multiple approaches without costly commitment to prototype hardware early in the development process. • A collaborative design environment using common executable specifications that connect to requirement documents and lets all multiple engineering disciplines communicate in a common language. • The ability to reduce development costs by easily finding and correcting errors during an early simulation stage. • The capability to develop complex embedded systems that provide customer value, product quality, and sophistication in multidisciplinary systems. K. Craig

27