In our Small Scale Lab, we have encountered issues with Operators mistakenly starting/stopping the wrong Vacuum Pumps. To prevent this, we have brainstormed solutions such as implementing Screen Control Logic to reset back to the Main Menu after a certain period. However, due to multiple Panels running the same PanelBuilder App, creating a separate app for just one Panel could lead to Configuration Management challenges. As an alternative, we are considering adding an extra Display layer with a confirmation message before initiating actions on the Vacuum Pumps. This will require strategically placing YES & NO buttons to avoid accidental inputs. Despite having multiple actions such as START, STOP, and Nitrogen Valve OPEN/CLOSE, we aim to streamline the process by having a single Confirmation Screen for each Dryer. To achieve this, we need to find a way to transfer information from the Upper Level Display to the new Confirmation Display for dynamic text display and Bit setting/clearing for the SLC 5/05 PLC. One approach could involve using the PLC Tag List as a temporary data storage area, including defining TEXT Tags like "D4510" or "D4511" to dynamically display relevant information on the Confirmation Screen. Although attempting to define these tags as "LOCAL" String Tags in PanelBuilder32 resulted in errors due to missing Controller information, we may need to explore other methods to make this functionality work seamlessly.
There are no local tags available in PV that I am aware of. In order to use placeholders, you will need to create a string or ASCII data file in the PLC.
Jimtech67 mentioned that there are no local tags in PV systems, so setting up a string or ASCII data file in the PLC will be necessary. It's important to create a simple screen with a prompt like "YOU ARE ABOUT TO MAKE CHANGES TO DRYER D4510 ... CONTINUE (Y/N)?" for confirmation. This screen can have a larger font for emphasis and even make the equipment tag blink. Pressing YES will go back to the previous screen, while NO will return to the main menu. This approach is efficient, as it can be applied to all panels without altering the PLC application. Additionally, confirmation screens can be added for every function if requested by Operations to prevent errors on other panels. While Operations suggested keeping motor outputs permanently on for easy wall switch use, this solution was deemed non-standard and unsustainable in the long run.
Unfortunately, the "epiphany" I had does not work as intended. To resolve this issue, I will need to initiate the START (Motor) or OPEN (valve) function on the second press of the button, after navigating back from the Confirmation Screen. If not, the system will be stuck in an endless loop between the "Main" and "Confirmation" screens. Additionally, the bits will also need to be cleared for the process to function correctly.
Attempting to outwit a skilled operator? Good luck with that task!
Oops, it seems I made a mistake! While driving home from work, I realized that my original plan won't work. I will need to make some adjustments so that the top-level Screen can communicate with an intermediate Tag instead of directly with the Motor Tag. Additionally, I need to ensure that the "Confirmation Screen" is displayed during this process. The YES button on the Confirmation Screen will then write to the Motor Tag and return to the top-level Screen. Can this be achieved with one of these Panels? I am looking for a solution that eliminates the need for Screen Control Logic and avoids breaking the app into separate entities.
I think your proposed solution of adding an extra confirmation display layer could indeed minimize operator errors. Using the PLC Tag List as temporary data storage seems like a viable option to transfer information between displays. Your errors in defining "LOCAL" String Tags suggest some incompatibility issues in your current setup. Have you considered trying "GLOBAL" String Tags instead? These are not linked to a particular PanelView, which might bypass the issues you faced. Additionally, while introducing such changes, remember to keep the operators informed and trained to adjust to new workflows, ensuring the introduction of new interface elements doesn't inadvertently increase confusion.
It sounds like you've really thought this through and are on the right track. Exploring the use of PLC Tag List as a temporary data storage would be an ingenious way to transfer the necessary information to the Confirmation Display. One thing you might also consider is using GLOBAL String Tags instead, as these don't require linking to a specific controller and may circumvent the issue you experienced. Remember to make your YES and NO buttons sufficiently large and clear to minimize chances of operator error.
I think implementing an extra layer of confirmation with a display message for controlling vacuum pump actions is an excellent idea. It will serve as a valuable double check for operators and could greatly reduce the occurrence of mistakes. As for the issue of transferring information from the Upper Level Display to the Confirmation Display, using the PLC Tag List sounds like a reasonable approach. Yet, if you're encountering errors with "LOCAL" String Tags in PanelBuilder32, you might need to dig deeper. Consider reaching out to the software vendor or checking dedicated forums for advice. Specialists might offer insight into alternative, efficient methods of achieving this.
Your idea of adding an extra display layer for confirmation is interesting and could potentially minimize the errors. As for transferring the information from the Upper level display to this new confirmation display, utilizing the PLC tag list seems to be a feasible method if executed correctly. Addressing the issue you faced regarding the 'LOCAL' String Tags in PanelBuilder32 could involve defining them as 'GLOBAL' string tags for a generic controller. Another approach could be to create an array in the PLC and use it as a dictionary to store your Strings. The key would be having a way to map the array indices to your dryer actions. Make sure to consider user-interface and workflow in your implementation, so operators find it user-friendly and efficient.
It sounds like you're dealing with a tricky balance between usability and complexity! I really like the idea of the extra display layer with confirmation prompts; it could significantly reduce those accidental starts and stops. For the data transfer from the Upper Level Display to the Confirmation Display, maybe consider using a combination of global tags and a list of pre-defined strings that can be referenced without needing to declare them as local. This might streamline your setup while avoiding those errors you've encountered. Ensuring that operators have a clear visual indication of their intended action could be a game-changer in preventing mistakes. Would love to hear how it progresses!
It sounds like you're tackling a tricky but crucial issue with the vacuum pumps! I really like the idea of adding a confirmation layer to enhance safety and reduce operator errors. Using the PLC Tag List for dynamic text display is smart, but you might want to look into utilizing the data logging features in your HMI software as a potential workaround for the tag issues you're facing. Setting up a dedicated "message" area to temporarily store input values could create a smoother user experience and help streamline the confirmation process. Balancing usability and safety is key, and your approach seems promising—good luck, and keep us posted on how it goes!
It sounds like you've thought through some solid strategies to tackle the confusion with the vacuum pumps! The idea of adding a confirmation layer is definitely a smart move—it not only enhances safety but also allows operators to double-check their actions. For transferring data to your confirmation display, consider using a combination of global tags and structured data types to simplify the process. That way, you can avoid the local tag issues you encountered. Also, maybe look into scripting or macros that could help automate some of the data handling between displays. It can be a little tricky, but once you get it set up, you'll probably find it significantly improves the workflow!
✅ 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: Answer: Implementing confirmation screens can help prevent operators from mistakenly starting/stopping the wrong equipment, such as Vacuum Pumps, by requiring a deliberate action before initiating any process.
Answer: Answer: One approach could involve adding an extra display layer with confirmation messages and strategically placed YES & NO buttons to avoid accidental inputs, ensuring a consistent user experience across all Panels.
Answer: Answer: Using the PLC Tag List as a temporary data storage area and defining TEXT Tags like "D4510" or "D4511" can enable dynamic information display on the Confirmation Screen. However, defining these tags as "LOCAL" String Tags in PanelBuilder32 may result in errors, prompting the need to explore alternative methods for seamless functionality.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.