Motion Control Integration and FPGAs

Sept. 18, 2013
Any motion control functionality achieved through the use of modular I/O and an FPGA can be integrated into an axis of motion that can then be integrated with other axes.

Following the release of a video I hosted on the topic of reconfigurable versus traditional motion control systems, featuring Nate Holmes of National Instruments, I wrote a blog post exploring the decisions behind choosing a fixed function controller or a real-time controller and another post looking at FPGAs for control algorithms and I/O and vision synchronization. But there remained one more issue from this video that deserves mention: How FPGAs aid the integration of various motion control aspects.

For lower level control applications, for example, in the drive firmware level, FPGAs can be used for a number of common motion control tasks such as control loops and commutation schemes, motion I/O like an encoder read, reading limit switches, and implementing filters.

“By targeting very specific portions of FPGA code for modification, you can achieve the flexibility you need and still get an application up and running very quickly,” says Holmes. With the “flexibility this approach provides, you can achieve coordinated motion with a FPGA controlled drive and an external smart drive from two different manufacturers. You could also coordinate many different types of motors—using a different type of feedback for each—all without changing the existing trajectory generation or move profile software."

Bottom line: Any functionality provided through the use of modular I/O and an FPGA can be integrated into an axis of motion, and that axis of motion can be integrated with other axes of wildly different configurations, Holmes says.

Despite the clear advantages FPGAs can bring to motion control applications, Holmes is quick to point out that FPGA technology is not always the best fit for every application. For example, if your application “falls within the use cases for which the manufacturer designed the fixed function controller and drive, then you can probably design the system at a lower cost and more quickly using traditional motion systems,” he says. “However, if you are reaching the limits of a high performance machine that needs to be better, faster, smarter, you will probably run into cases where you need advanced I/O, custom synchronization, specialized control algorithms or the need to integrate disparate and/or non-standard subsystems.”

It is at this point that Holmes says a reconfigurable architecture, enabled by FPGAs, become your most effective engineering tool.

For more information visit: www.automationworld.com/nipac

About the Author

David Greenfield, editor in chief | Editor in Chief

David Greenfield joined Automation World in June 2011. Bringing a wealth of industry knowledge and media experience to his position, David’s contributions can be found in AW’s print and online editions and custom projects. Earlier in his career, David was Editorial Director of Design News at UBM Electronics, and prior to joining UBM, he was Editorial Director of Control Engineering at Reed Business Information, where he also worked on Manufacturing Business Technology as Publisher. 

Companies in this Article

Sponsored Recommendations

Why Go Beyond Traditional HMI/SCADA

Traditional HMI/SCADAs are being reinvented with today's growing dependence on mobile technology. Discover how AVEVA is implementing this software into your everyday devices to...

4 Reasons to move to a subscription model for your HMI/SCADA

Software-as-a-service (SaaS) gives you the technical and financial ability to respond to the changing market and provides efficient control across your entire enterprise—not just...

Is your HMI stuck in the stone age?

What happens when you adopt modern HMI solutions? Learn more about the future of operations control with these six modern HMI must-haves to help you turbocharge operator efficiency...