TwinCAT HMI helps engineers develop the kind of operator interface users expect with web-design tools and UX best practices in a fully integrated, extensible platform
HMIs are often an afterthought in the automation space. Many engineers and integrators treat them as a necessary evil rather than a strategic component of their systems. With TwinCAT HMI, however, engineers can harness a game-changing product that elevates the role of the HMI.
In my recent webinar, I explored how TwinCAT HMI accomplishes this goal. As part of the comprehensive software suite, TwinCAT HMI enables engineers to harness web design tools in the standard TwinCAT engineering environment. This doesn’t just deliver value to the machine builder OEM. It also provides a more intuitive, smartphone-like UX for the equipment end user, which simplifies operation, training, troubleshooting, etc., for greater efficiency.
Below you can read a recap of the webinar. On top of the main points of the presentation, we added a few of the key questions from our Q&A. If you couldn’t attend or want to watch again, you’re in luck. Just fill out this form to access the full on-demand video, along with some additional resources:
HMI development has some new tricks
The key to TwinCAT HMI's capabilities lies in its architecture. Rather than relying on proprietary hardware or software, it leverages standard web technologies like HTML, CSS, and JavaScript to create a cross-platform, scalable client-server model. This means your HMI can be accessed from any device with a web browser, without the need for custom installations or add-ons. You can also dive right into multi-touch functionality for immersive, user-friendly visualizations. And on the server side, the software can run on a standard PC, seamlessly integrating with your TwinCAT PLC and other Beckhoff products.
What really sets TwinCAT HMI apart is the balance it strikes between flexibility and accessibility. While the underlying technology is based on web development, the tool provides a familiar, low-barrier-to-entry experience for control engineers. The project generator and drag-and-drop designer make it easy to get started, with options for responsive layouts, localization, and theme customization. And for those with more web development experience, the extensibility of the platform is truly remarkable.
Take control with integration and extensibility
One of my favorite aspects of TwinCAT HMI is the way it integrates with the broader Beckhoff ecosystem. Features like the EtherCAT diagnostics control, MDP extension, and TwinCAT Vision control seamlessly bring in data and functionality from other Beckhoff products, streamlining the user experience, and reducing the need for custom development. These "ecosystem features" are included in the base product license, providing tremendous value without additional cost.
But the real power of TwinCAT HMI lies in its extensibility. Whether you're a seasoned web developer or a controls engineer new to these technologies, the platform offers endless opportunities for customization and expansion. The ability to create custom front-end controls and back-end server extensions means you can truly tailor the HMI to the unique needs of your application and your organization.
I've seen customers and internal teams at Beckhoff leverage these extensibility features to build some truly impressive solutions. From integrating third-party libraries to creating specialized visualizations and data processing workflows, the possibilities are nearly limitless. And with the growing repository of sample extensions on the Beckhoff GitHub and examples compiled at cmi.beckhoff-cloud.com, there's a wealth of resources to help get you started.
Peer into the future of HMI design
The latest version of TwinCAT HMI, 1.14, further solidifies its position as a cutting-edge HMI platform. The addition of 64-bit development support, improved performance, and new ecosystem features like the motion control and TwinSAFE diagnostics controls demonstrate Beckhoff's commitment to continuously enhancing the product.
In conclusion, TwinCAT HMI stands out in the automation landscape by combining the flexibility and power of web-based technologies with the accessibility and integration that control engineers expect. Whether you're looking to create a simple, responsive HMI or build a highly customized, multi-touch-enabled visualization platform that’s right up there with the best smartphone and tablet apps, this product has the tools and capabilities to make your vision a reality.
I'm excited to see how customers continue to push the boundaries of what's possible with TwinCAT HMI.
Follow up from our TwinCAT HMI Q&A
We received some great questions during the webinar. Here are a few that we wanted to address in writing for anyone to see.
Q: Is TwinCAT HMI only for Beckhoff PLCs?
A: No, you can use OPC UA to talk to any third-party system as well.
Q: How many clients does the tool support?
A: There is probably some programmatic limit, but it is important to note that this tool is not meant to displace full-on SCADA implementations. That being said, we have customers using tens of, or nearly 100 concurrent clients. There are a lot of performance optimizations going on in the server – for instance tag filtering and grouping, etc.
Q: How much does it cost to add the EtherCAT Diagnostics control in TwinCAT HMI?
A: Zero. Nada. Zilch. That is a free environmental feature that’s a bonus included in the Beckhoff platform. This became available with version 1.12.760.59 of the TwinCAT HMI Server.
Q: When will TwinCAT HMI version 1.14 be available – and on what version of TwinCAT?
A: It is already out! You simply need TwinCAT 4026, which works better with the package manager than 4024 did.
Q: Is the MQTT extension through the PLC?
A: MQTT functionality is available through TwinCAT PLC via software libraries. It is conceivable to build this out in HMI through extensibility options too, though.
Q: What’s the easiest way to set alarms in the HMI?
A: One option is to tie the event logger in the TwinCAT PLC to elements in your HMI. There is another option, the Alarm Extension, and you basically set up the PLC conditions that trigger that alarm. For example: “If XYZ Boolean goes high, then throw this alarm.”
Q: What will the auto-mapping feature include?
A: We have an InfoSys page for that!
Q: Is 1.14 only on 4026 for the 64-bit shell?
A: From the development environment perspective, yes. For runtimes, they can coexist and communicate.
Q: Can TwinCAT HMI talk directly to an MQTT broker?
A: Not natively but through our Server Extensions it would be possible to create an MQTT connection.
Q: Is there a way to create a nuget package from an HMI server extension?
A: Yes. The build output of a server extension is the same as that of a regular C# project, so that process of creating a nuget package would be similar/the same.
Q: What is the best browser for TwinCAT HMI?
A: We have had a good experience with Chromium as it is an open source, lightweight browser. We also have a new product, TF1200 UI Client that is a cross-platform, standalone browser.
Q: Is the TwinCAT HMI included with the base runtime or is it an additional module like the PLC HMI?
A: It is a standalone product.
Q: Can the HMI program be downloaded from the PLC to the engineering environment?
A: HMI runtime projects cannot be downloaded from the target like PLC projects. That being said, they are just files on the target system and can be exchanged via any file transfer means. Just not through the same development environment.
Q: To use TwinCAT HMI Server on an actual machine, do I need a license for TF2000?
A: Yes, the TF2000 license covers the server, 1 client and 1 target license.
Q: Is anything from today's webinar specific to TwinCAT 3 Build 4026? Or are all these features available on 4024 as well?
A: The “what’s new” features will not be backward compatible, but everything else discussed should be available on both.
Q: Is 14.2.13 the latest version? Will there be an updated version anytime soon?
A: That is the latest. 14.3 is coming soon (with updates like Python server extensions).
Q: Why is the package manager showing the TwinCATHMI version as 14.2.13 instead of 1.14?
A: That is simply a change to the naming convention of TwinCAT HMI releases.
Q: What version of the HMI server do I need to acquire it?
A: For EtherCAT Diagnostic control, it became available with 1.12.760.59
Q: Is the version alignment 1.12 and 1.10 for 4024, and 1.14 for 4026?
A: Components or extensions are largely shared, but not cross-compatible between major versions. For custom framework controls or extensions, they are usually able to be used with newer versions without much or any rework (but not able to go backward).
Want to brighten up your operator interface with powerful HMI development tools? Contact your local Beckhoff sales engineer today.
And check out our upcoming and on-demand webinars to stay current on the latest automation innovations from Beckhoff.
Brandon Stiffer is a Software Product Manager at Beckhoff Automation LLC
Comments