Saturday, July 12, 2008

bridged between modern electronic and mechanical equipment.


Computer Architecture and Interfacing to Mechatronic Systems



Very few systems in modern engineering are either purely mechanical or purely electronic in nature. Most engineering devices, machines and systems are a combination of mechanical elements, computer controls and the electronic interfacing circuitry that binds these elements together. In the mid-1980s, these hybrid systems were recognized as being a rapidly growing part of the engineering world and were given the rather commercial, but nonetheless appropriate, title of "mechatronic"systems. It is somewhat ironic that the two fields of engineering (electronic and
mechanical) that were derived from the classical mechanical engineering streams of the early 19th century have now had to be brought back together as a result of the growing need for mechatronic systems.

A mechatronic system can have many forms. At a domestic level, it could be a compact-disk player or a video recorder. At an industrial level, a mechatronic system could be a robot, a computer controlled production machine or an entire production line. The extraordinary increase in low-cost processing power that has arisen as a result of the microprocessor now means that few mechanical devices in the modern world are born without some form of intelligence.

The problem that most engineers now face is that their undergraduate courses have simply not equipped them to undertake the task of designing mechatronic systems. Mechanical and manufacturing engineers seldom understand enough about electronic engineering and computing concepts to tackle the inter-disciplinary realities of system design. Electrical and electronics engineers similarly understand very little about the mechanical systems for which they design computer controls and interfaces.

It is surprising therefore, that in this day and age we still retain separate courses
for electronic and mechanical engineering - and yet the trend towards greater specialization is unfortunately continuing. The common university argument is that in order to be a good electronic or mechanical engineer, one needs to have a highly specialized undergraduate program. The reality is that in order to be a good engineer, one needs to have a good understanding of both mechanical and electronic engineering disciplines and a degree of specialization that is born of practical realities, rather than esoteric theories.

No comments: