Hello everyone, I am facing a situation with an old PV program that has over 2000 configured alarms, many of which are warnings and messages that continuously appear on the alarm page, causing inconvenience for operators. While the HMI will eventually be updated, the client is looking for a temporary solution by installing two PanelViews next to each other - one to display alarms and the other for regular operation. To streamline this process and avoid having to manage two separate HMI programs, I am exploring options to disable alarms on one HMI with the press of a button, such as using a macro or system tag, or having the program differentiate between which HMI it is running on to prevent the alarm display. This would allow me to use the same program on both PanelViews. Although I have doubts about the feasibility of this solution, I am hopeful that there may be a way to achieve it.
One way to address nuisance alarms in a PLC program is to deactivate unnecessary bits to avoid constant interruptions. Setting an excessive number of alarms can be counterproductive as operators may start to disregard important alerts if inundated with insignificant ones. The overload of alarms can also impact the speed of the HMI, particularly when utilizing serial communications. This is because the HMI constantly updates the alarm statuses along with the tags required to refresh the displayed page.
I fully concur with your perspective. Eliminating the problem at its source is indeed the most effective solution. However, I have not been tasked with that by the client, as it is something they will address in the future. At this moment, my focus is on finding a solution related to HMI.
The Alarm page keeps appearing constantly in FactoryTalk View ME. The software has three features that open pop-up Displays automatically: Alarms, Messages, and Diagnostics. These Displays are preset to launch when needed. Disabling the Alarm Display in the HMI project is simple - just uncheck the box. While it may be concerning that alarms won't be displayed, creating a separate runtime file without alarms is an easy solution. You can also take the time to filter out nuisance alarms or group them for easier management.
Thank you, Ken, for your suggestion. I have also considered the option of running two programs simultaneously, one with alarms enabled and the other with alarms disabled. I was looking for a way to have identical programs running on both HMIs. To address concerns, the preference is to have both programs running concurrently, allowing the operator to view alarms on a separate screen. This is a temporary solution until they upgrade to SE.
Hello, you are dealing with an interesting challenge! I'd suggest you to consider grouping the alarms based on their severity. This way, you can use one PanelView to display critical alerts that require operator intervention, while minor warnings can be managed in the other. Regarding turning off alarms with a button, although macros or system tags may offer a possible solution, remember to ensure that the operator won't accidentally disable important alarms, which could potentially lead to grave consequences. Regarding your program issue, it's not wholly unfeasible. You might want to consider the FactoryTalk View ME Station's multi-monitor feature as a possible solution, as you can run numerous screen displays on the same program. This could help distinguish between the two HMIs without having to manage separate programs. Just an idea, but it might be worth investigating. Good luck!
I totally understand your predicament. An archaic alarm system can turn fairly straightforward tasks into a nightmare. As a temporary solution, your idea of using the same program on both PanelViews could be effective. You might be able to create an alias tag that gets the PanelView ID via a system tag, then use that in your alarm display logic. When alarm is triggered, it checks the PanelView ID first before displaying. If the ID matches the alarm display PanelView, it shows the alarm; otherwise, it remains silent. This way, operators can keep monitoring their respective tasks without distractions. I am not entirely sure but I think it's doable with some tweaking. Certainly worth exploring in more detail!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - While it may not be a standard feature, there are ways to potentially achieve this by exploring options like using macros, system tags, or programming logic to differentiate between HMIs.
Answer: - Yes, it may be possible to configure the HMI program to prevent alarm display on one PanelView while showing them on the other by implementing specific logic or conditions.
Answer: - Disabling alarms on one PanelView should not impact the functionality of the alarms system itself, as it is more about controlling the display of alarms on the HMI interface.
Answer: - While a temporary solution like the one described can help alleviate the issue, it is advisable to eventually update the HMI program to handle alarms more efficiently, especially with a large number of configured alarms.
Answer: - Some challenges may include ensuring seamless integration between the two PanelViews, maintaining consistency in alarm handling, and testing thoroughly to confirm that the solution works as intended without affecting other aspects of the HMI program.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.