Error handling is critical in any software development. When done correctly and with the user in mind, error handling makes it easier to operate a system correctly, lets users know when something has gone wrong (and ideally how to fix it), and makes your code easier to debug and maintain. In this blog, I’ll discuss the common error handling techniques for Ignition SCADA applications and key considerations to keep in mind to provide the best possible user experience.
Equipment manufacturers, engineering, procurement and construction (EPC) companies, and power and process plant owners and operators commonly face the challenge of keeping their fleet, machinery, and other assets working efficiently while reducing the cost of maintenance and time-sensitive repairs. Considering the aggressive time-to-market required for industrial products and services, it is crucial to identify the cause of potential faults or failures before they have an opportunity to occur.
UL-508A certification for industrial control panels is a requirement in most jurisdictions and a standard many OEMs voluntarily choose to follow. There is a common misconception that a UL-508A certified panel shop can certify any panel they build. However, panels must also be designed to UL-508A standards to be certified. Because of this, it’s important to make sure your design is compliant with the 508A standard before approaching a panel shop to build and certify it. Here are a few things to consider to ensure your design is UL-508A certification ready.
Edge computing is designed to enhance the Industrial Internet of Things (IIoT) and provides many potential advantages for users. Edge computing speeds up data flow and extends knowledge of what's happening on a network. It also improves data reliability by making device data the one source of truth. And there's less latency. If there are local human-machine interfaces (HMIs), there's still local access and control even if network connectivity is lost to help prevent against losing data. Edge devices are more powerful, easier to use, and less expensive, making it very affordable to put powerful computers at the edge of a network.
ICC 2019 is in full swing in Folsom, CA. The Ignition Community Conference brings together the entire Inductive Automation ecosystem of integrators, third-party suppliers, and the entire Inductive staff including executives, developers, sales, marketing, support and more. Ten Vertech team members representing all three of our offices are attending. Here are a few impressions and comments from the team.
Have you ever looked at your SCADA screen(s) and thought this screen could look a lot better? Or why isn’t there organization or functionality to this screen design? Maybe you haven’t, but we guarantee your operators have. The problem with some SCADA designs is programmers don’t take the time to think about the daily usage. The goal for any screen design should be to help the operator receive important information efficiently in order to make decisions.
In my last post, I gave tips on the various tools available for finding and logging issues both within your application and with Inductive Automation’s Ignition SCADA software. In this post, we’ll dive into three additional debugging and diagnostics tools in Ignition: Execution, Threads, and Gateway scripts.
Vertech prides it's self in creating an innovative work environment. FedEx day is a dedicated day for Vertech employees to be creative and come up with projects that can enhance the company. To see the different project and team watch the video below.
Inductive Automation’s Ignition platform is a powerful, flexible, and highly customizable SCADA platform enabling data-driven decision making for industrial enterprises. Before the final product hits the plant floor, however, developers must configure and program the platform. This post provides a few tips on the different tools available for troubleshooting issues both within your application and with the Ignition software.