Facebook
Google
GitHub
Linkedin
I've worked with industrial HMI systems for many years, including larger platforms such as Wonderware, and one question I've kept coming back to is: how much of a large HMI/SCADA platform do we actually need for a typical machine or process application?
Over time, I developed my own Windows-based HMI around the functions I regularly needed. It has now become HMIMaker and HMIViewer.
The current system includes:
• Graphical HMI development and runtime
• Tag-based animation
• SQL database integration
• Real-time and historical trending
• OPC DA
• EtherNet/IP / CIP
• Allen-Bradley SLC legacy Ethernet
• Modbus IEC
• Modbus Generic
HMIMaker is the development environment, while HMIViewer is the runtime.
The objective isn't to duplicate every feature of a large SCADA system. The idea is to provide the functionality needed for many real industrial applications in a smaller PC-based HMI package.
I'm the developer of the software, and it has now reached public release. I'm interested in hearing from other automation engineers rather than simply assuming that the functions I use are the same ones everyone else considers important.
What functionality do you consider essential in a modern PC-based HMI before you would consider using it on a real machine or process?
I'm particularly interested in requirements beyond the obvious graphics, PLC communications, SQL and trending—things that become important only after you've actually commissioned and maintained an HMI in the field.
If there is interest, I'm happy to share more technical details about the architecture and the decisions behind it.
Over time, I developed my own Windows-based HMI around the functions I regularly needed. It has now become HMIMaker and HMIViewer.
The current system includes:
• Graphical HMI development and runtime
• Tag-based animation
• SQL database integration
• Real-time and historical trending
• OPC DA
• EtherNet/IP / CIP
• Allen-Bradley SLC legacy Ethernet
• Modbus IEC
• Modbus Generic
HMIMaker is the development environment, while HMIViewer is the runtime.
The objective isn't to duplicate every feature of a large SCADA system. The idea is to provide the functionality needed for many real industrial applications in a smaller PC-based HMI package.
I'm the developer of the software, and it has now reached public release. I'm interested in hearing from other automation engineers rather than simply assuming that the functions I use are the same ones everyone else considers important.
What functionality do you consider essential in a modern PC-based HMI before you would consider using it on a real machine or process?
I'm particularly interested in requirements beyond the obvious graphics, PLC communications, SQL and trending—things that become important only after you've actually commissioned and maintained an HMI in the field.
If there is interest, I'm happy to share more technical details about the architecture and the decisions behind it.
