Control System Architecture
October 3, 2010 by Steve Meyer
Filed under Automation, Commentary, Design, Manufacturing Trends, Motion Control, Technology
The recent trend from control systems vendors is the use of the term “architecture”. This trend has become so pervasive that one major vendor changed the titles of it’s sales reps to “System Architects”. That shift says a lot about the importance of control system architecture.
Architecture is used when talking about the the design and construction of buildings. The term has been equally appropriated to refer to the internal design of computers and complex semiconductor processors. But just as a processor or a computer has an architecture, a control system has an architecture too.
The control system architecture can be the internal architecture of control product such as a PLC, and it can be a priced bill of materials for a complex list of parts. But how do we go about describing the control system adequately so that everyone understands and agrees that it will do what is expected. A panel layout can be created to put all the control systems in an enclosure. And you can write a functional specification for the control system, although these tend to be very difficult to interpret. And none of these things will provide the needed assurance of specific performance.
A control system architecture is an attempt to graphically represent how a bill of materials goes together to solve a customer’s required functionality. This is a little more subtle and may require some additional information, like a flowchart. But the architecture of a control system is an attempt to translate the functional requirement into hardware. And such a diagram will make more sense in terms of the actual application to anyone who looks at it.
And there are plenty of subtleties here. As vendors continue to integrate more capability into smaller, more integrated packages, it can be a little unclear how new hardware will reflect the application’s requirements. This is a little bit like the question of using a PC versus a PLC, only more complex.
An example might be the many new HMI products that are actually computers with the ability to partition the HMI application and control system application on a single processor platform. Which can be a very cost effective and processor efficient solution.
A system input-output map is only the beginning. Turning devices on and off, picking up analog sensors and controlling analog outputs are all the domain of the PLC. Software glues all of these components together. Based on the leap in processor capability over the last few years, the computing requirements for this type of control are certainly not taxing. And the architecture required is fairly flat, a central processor and an I/O buffer.
When the application requires motion control or the integration of pneumatic or hydraulic systems, there begins to be a system consideration. The pneumatic sub-system could be on a Device Net interface, where there will be a time latency between the central processor and the sub-system. And while this might present no discernable issue for the control system, the latency is very difficult to account for.
When integrating more complex sub-systems like external motion controllers, the time required to update position information can be significant. And as with other sub systems, the time latency cannot be accounted for or circumvented. Which puts a practical limit on the actual application.
This makes careful study of the system architecture an invaluable effort to not only evaluate the cost for a control system, but anticipate performance issues as well. With proper attention to issues like system timing, many pitfalls in implementation can be avoided and the architectural diagram can be an invaluable tool to instill confidence that an application is properly understood and will work as expected.
The Tools, They are a Changing’
December 14, 2008 by Steve Meyer
Filed under Commentary, Design, Simulation
(regarding the title, just think Bob Dylan’s “The Times They are a Changin”)
Just as Computer Aided Design, CAD, has revolutionized the design process, it is growing in capability and impacting many other arenas of engineering. The first major extensions to CAD were integration of Finite Element Analysis, the ability to analyze loads on the parts being created. And certainly, if the design software can model the complex aspects of loading, then animation of part motion can’t be a far reach. And that’s the case today. Read more
The Future of Mechatronic Design
September 1, 2008 by Steve Meyer
Filed under Automation, Commentary
I think mechatronics generally begins with mechanical design. That’s just my perspective, it may differ in your experience. If its a power window in a car, a hard disk drive platter machine, a blender, an amusement park ride or display, a surgical robot, whatever. They all start with mechanical design, performance goals and boundary conditions that are required for the mechanical system to be useful.
This is why there needs to be great emphasis on the design of software tools that are extensions to the 2D and 3D CAD products that are currently available. Obviously, if you are engaged in mechanical design, you are in a unique position to the final outcome of the design project. The mechanical design work sets the boundary conditions of what is possible. Read more
5 Design Challenges and Solutions for Machine Builders
Machine builders can virtually prototype their machine control systems with LabVIEW and the NI SoftMotion Development Module for motion profile generation as well as mechanically simulate and detect collisions with SolidWorks and COSMOSMotion.
Intense competition is putting pressure on machine builders to deliver machines with higher throughput, reduced operating cost, and increased safety.
By Nipun Mathur, National Instruments
Faster, better, cheaper, safer is the name of the game for machine builders. For this reason, today’s machine builders have switched from rigid, single-purpose machines – relying purely on mechanical gears and cams – to flexible multipurpose machines by adopting modern control systems and servomotors.
Although these improvements have made machines more adaptable, they also have introduced a significant amount of complexity to the machines and subsequently to the machine design process. Along with designing the mechanicals, machine builders now incorporate control logic, human machine interfaces (HMIs), networking, and machine condition monitoring systems into their designs. The added complexity has created inefficiencies in the machine design process that lengthen design time and increase design cost.
Solving this multidisciplinary engineering problem requires improvements in three key areas – development techniques, design tools, and embedded control technology. The term mechatronics is gaining popularity as a way to describe this evolution. It represents an industry-wide effort to improve the design process by integrating the best available development practices and technologies to streamline machine design, prototyping, and deployment. A mechatronics-based approach can lower the risks associated with machine design and meet the following five key challenges that machine designers face today. Read more
Mechatronics
October 8, 2007 by Steve Meyer
Filed under Commentary
Why should you care? Because whatever the term “mechatronics” might mean to you, it affects so many aspects of our daily life.
We’ve all seen commercials with a production floor full of welding robots making automobiles. Certainly automotive manufacturing would not be possible without numerically controlled machine tools, robots and much more. And the automotive manufacturers continue to advance the field of automated manufacturing resulting in higher quality products at lower costs. Read more


