In the programming of a G308A210 device using Crimson 3.0 build 579.003, there is a display page configured as a master slide. Along with the standard alarm banner at the bottom, I aim to incorporate a menu overlay accessible by pressing the "MENU" button. This overlay would display a rectangle with labels for each hardware key, possibly including touch cells. While adjusting visibility is straightforward, I seek to ensure that the menu pops up and covers all other elements on the screen, rather than appearing behind them. Although currently I can achieve this by duplicating the group on each display, I prefer the convenience of having it on the master slide for easier updates. Are there any solutions or newer features in updated software versions that address this issue? Despite operating an older software version for consistency among multiple HMIs in use, I welcome any suggestions for improving this functionality.
In Crimson 3.0 build 579.003, when programming a G308A210, setting up a display page as a master slide can be enhanced by adding a menu overlay for easier navigation. By utilizing the "MENU" button, operators can access a menu with prompts for each hardware key, potentially including touch cells. Ensuring the visibility of the menu overlay is essential, with the goal of having it pop up and cover the content on each screen instead of appearing behind it. If encountering issues with the display, consider configuring a "Popup Menu" page with the desired layout and functionality. This approach allows for convenient access to various programs by pressing hardware buttons or invisible touch buttons. Additionally, leveraging the popup menu eliminates the need to make changes to the Master Slide. Despite using an older software version, optimizing the functionality of HMIs is crucial for efficiency and consistency in maintenance and operation. Explore the possibilities offered by menu key configurations to enhance user interaction and streamline navigation on HMIs.
This current setup is not functioning properly. Despite having visible buttons, the activation of touch buttons for each hardware button is not consistent. It seemed to work for some buttons but not all, indicating a possible alignment issue between Crimson and the HMI. To address this, I adjusted the layout by creating 6 touch buttons, each 80 pixels tall for the 6 hardware buttons on the G308, which is 480 pixels tall. This new configuration improved the functionality, although the bottom 2 hardware buttons trigger the touch buttons above them. This can be seen in the attached "Menu1.jpg" and "Menu2_Smaller.jpg" images. Additionally, I discovered that the "MENU" button for the popup menu must be set as local rather than global for each display to work correctly, as setting it globally resulted in it not working at all. This unusual behavior warrants further investigation.
Joseph_e2 is experiencing issues with the alignment of touch buttons on the HMI display. Despite appearing aligned in Crimson, the touch buttons do not activate correctly when associated with hardware buttons. In an attempt to resolve this issue, Joseph_e2 resized the touch buttons to match the height of the hardware buttons, resulting in proper functionality. However, some hardware buttons trigger the touch button above them instead of the intended one. Upon further investigation, Joseph_e2 discovered that the "MENU" button must be set to local instead of global to work effectively as a popup menu. It is crucial to ensure that no buttons are set to global or local but rather use Open Page as Popup Menu for proper operation. To optimize functionality, it is recommended to use the IsPressed variable to enhance button appearance. By adjusting the size and positioning of the buttons to prevent overlapping, users can improve the overall usability of the HMI display. Additionally, creating program calls for the buttons can enhance navigation and functionality, allowing for multi-page menus and additional features. For further assistance, it is suggested to share the configuration for a detailed review. Remember to utilize popup menus instead of keeping buttons always visible for seamless operation.
1) All hardware buttons, with the exception of "MENU", are currently unconfigured and have a global/local setting on all screens. 2) The "MENU" button is set to a local configuration on all displays, directing users to a specific page as a popup menu. However, on the Menu display itself, it is set to "User Defined" and programmed to "HidePopup()". Despite my initial attempt to set the "MENU" button as global, it failed to function properly. It did not display a popup menu. After changing the configuration to local and ensuring uniform settings across all displays, the button now works correctly. I suspect there may be an alignment issue, as the buttons appear perfectly aligned in the software (Crimson) but slightly off in reality. To address this discrepancy, I adjusted the height of the buttons while maintaining their alignment. While they appear aligned in Crimson (Menu3.jpg), there is a noticeable difference in real life (Menu4_Smaller.jpg). I have included the project files for reference. During testing, I found that the hardware buttons for "Manual" and "Auto" function as expected, but those near "Data Entry", "Indicators", and "Drive Diagnostics" are unresponsive. Additionally, the button next to "Alarm History" triggers the "Drive Diagnostics" touch button. I will continue to make adjustments to improve alignment and functionality.
I successfully configured all hardware buttons to function properly after making some adjustments, however, this caused the touch buttons to become unresponsive. For a visual reference, please refer to Menu5.png for a screenshot of Crimson and Menu6_Smaller.jpg for a photo of the HMI. It is worth noting that relocating the "Manual" button to align with the other buttons resulted in its corresponding hardware button malfunctioning. I believe contacting Red Lion tech support may be necessary to resolve this issue.
In Crimson 3.1, it introduced the 'Layer Priority' property for display elements. This is perfect for your scenario. It allows you to set the Z-order of the elements on your screen. You might want to consider upgrading to this version and giving this feature a go. However, please remember that any upgrade needs to be executed carefully to ensure compatibility with your existing projects. Make sure to back up all files and test thoroughly after the upgrade to avoid any discrepancies.
One solution that might work is creating a pop-up page that has the overlay you're looking for, and then calling this pop-up page when the MENU button is pressed. This should ensure your menu appears on top of all other elements. Also, do consider upgrading to a newer version of the software as it may come with updated features that make tasks like this easier. However, remember to first test the new version in a controlled environment before deploying it, especially if there are several HMIs that need to remain operational.
That sounds like a tricky situation with the G308A210 and Crimson 3.0! It's great that you're trying to streamline the menu overlay using the master slide. Have you considered adjusting the Z-order or layer properties for the menu overlay? Some versions of Crimson allow you to set visibility and layering priorities, so if your overlay is set to a higher layer than other elements, it should appear on top when activated. Additionally, while you mentioned sticking with the older version for consistency, it's definitely worth looking into whether there are updates or patches that address layering or pop-up functionality without going through a full upgrade. It might save you a lot of hassle down the line!
It sounds like you're navigating a classic challenge with UI on master slides. While sticking to Crimson 3.0 limits your options, one workaround could be leveraged visibility layers or using the display hierarchy to prioritize your menu overlay. Instead of duplicating elements, consider grouping the menu overlay in a way that allows you to manage z-index or layering within the master slide - this might help keep everything consolidated and more manageable across updates. If you do eventually consider upgrading to a newer version, they often introduce features like advanced layering or modal pop-ups that would simplify this process greatly. Meanwhile, the workaround you mentioned with duplicating may just be the most reliable approach within your current constraints. Good luck!
✅ 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: - To configure a menu overlay, you can create a display page as a master slide and incorporate a menu accessible by pressing the "MENU" button. Adjust the visibility settings to ensure the menu covers all other elements on the screen.
Answer: - One solution is to duplicate the group on each display, but for convenience, you can aim to have it on the master slide for easier updates. Check for any newer features or updates in the software that may address this issue.
Answer: - While operating an older software version for consistency, you can explore options like duplicating groups on each display or updating to newer software versions that may offer improved functionality for menu overlays.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.