Comments
Reading your comments, I was struck by the similarity to 'fit for purpose', the basic concept of quality. Couplings should be keyed if the provision of a key is less trouble than a coupling slipping at some time in the future. If rezeroing after power up is too time consuming, then you need absolute encoders and so on. This line of thought leads you back to the fundamental question, 'what is the mechanism for?' Who are the customers and stakeholders for the functionality provided by the mechanism and what are their requirements?
It was a US Army engineer in the 1800's who defined an engineer as someone who could do for $1 what any fool could do for $5. Since he was probably talking mainly about earthworks, brute force would probably succeed but never elegantly.
An elegant Mechatronic design applies the fit for purpose concept across the range of engineering disciplines - mechanical, electrical and software, using the best approach for each aspect of the machine rather than favouring a single discipline. Sounds a lot like systems engineering doesn't it. Unfortunately, a wide range of skills are needed by at least one individual or else very good colaboration between different disciplines. My own experience with packing machines over many years is that design faults often seem to occur at the boundaries between disciplines.
A final detail, looking at the US website for Yaskawa, it says that they thought up and registered 'Mechatronics' in 1967 and released it to general public use in 1987. Since they make servo drives, it can be considered as originally meaning 'mechanical and electronic' but I think the term has moved on to systems with mechanical, electrical/electronic and software elements.
Posted by: Leon Hooper on May 21, 2008
I am an electronic engineer in Medellin - Colombia. I am involved in the development of control systems for packaging machines.
For me mechatronics design is to make a mechanical movement simple, fast, flexible and precise.
Simple: minimal mechanical parts involved (shafts- servomotor-gears or belts (good mechanical design))
Fast: Very good mechanical and electrical response (system modelation, programming and mechanical designing)
Flexible: Could be changed basically, by use of a recipe (programming: Human Machine Interfase and Control Software)
Precise: The motion could be repeated with minimal errors during operations (mechanical and control design).
Like we see is the use of many knowledge areas ( mechanical, electrical-electronic and software) with only one purpose: A simple, fast, flexible and precise machine.
Posted by: David Perez on July 29, 2008
I agree that its hard to define. And I challenge the notion that there are mechatronic principles, although there is a great need for systematic methods. In part this is because the "mechatronic" term is over used and its application is very situational. THe key thing to understand is that in each project there are differing goals and differing priorities of what is important. Obviously, people who build machinery are concerned with throughput and cost. But the boundary conditions and number of variables are extremely complex and difficult to navigate.
I am currently on a kick about better tradeoff analysis as a key part of better mechatronic design, and I have some techniques that can be directly applied to the design process.
I would like to correspond with you longer term toward driving the discipline forward. I am currently blogging and writing for Design World magazine. You can review some of my recent rants at Projectmechatronics.com
Sincerely
Steve Meyer
Posted by: Steve Meyer on September 1, 2008
I was struck by the similarity to 'fit for purpose', the basic concept of quality. Couplings should be keyed if the provision of a key is less trouble than a coupling slipping at some time in the future.
Posted by: kieran23h on February 9, 2011
|