Trigger an action on a Touch Press or a Touch Release event
Configure an action to occur when pressing or releasing a graphic element or the screen on the HMI device. For example, create a
Touch Press
event so that a specific screen opens when touching a graphic element. To trigger an action on a Touch Press or a Touch Release event
- Select the item to have the event. The item can be a graphic element, a graphic element in the definition of an Add-On Graphic, an Add-On Graphic instance, a group of elements, a screen, a popup, or the System Banner.TIP:Select items on either theScreenarea,Project Explorer, orGraphic Explorer.
- In thePropertiespane, click theEventstab.
- SelectAdd Eventand select an event from the list.
- Touch Press.Occurs when pressing a screen or element on the HMI device.
- Touch Release.Occurs when releasing a screen or graphic element on the HMI device.
- If a Touch Release event requires that the event of the element trigger even if a finger slides off the element before releasing the element, the graphic element becomes disabled or invisible, or a screen navigation opens a different screen, select theAlways Trigger Release Eventcheck box. This setting is useful for having the element act like a momentary push button. For example, a Touch Press sets a tag to 1 to start a conveyor belt, and a Touch Release event sets the same tag to 0 to stop the conveyor belt.
- SelectAdd Command.
- Expand a command category to list the commands in that category:
- Select the command the event is to perform.
- Alarm History.
- Data Log.
- HMI Device Configuration.
- Language. Change the language that displays on the HMI device.TIP:Tips:
- Import the desired languages before changing the language that displays on the HMI device.
- If a translatable string is left blank,View Designerdefaults to the download language for runtime applications downloaded to the HMI device. If the string that is translated for the download language is also blank,View Designerdefaults to the language used for designing the project.
- Navigation.Navigate to screens on the HMI device.TIP:Multiple screen navigation commands can exist for an event. All other types of commands for the event are executed before the navigation command. Only one navigation command is executed for an event. This is generally the first navigation command. The remaining navigation commands are ignored on the HMI device. To ensure the navigation command is the navigation command executed,Rockwell Automationrecommends adding only one navigation command to an event.
- Language. Command that changes the language that displays on the HMI device.TIP:Tips:
- Import the desired languages before changing the language that displays on the HMI device.
- If a translatable string is left blank,View Designerdefaults to the download language for runtime applications downloaded to the HMI device. If the translated string for the download language is also blank,View Designerdefaults to the language used for designing the project.
- Notification. Send an email notification.
- PDF. Commands that zoom or navigate pages in a PDF file.
- Security. Log on or log off the HMI device.
- Value.Commands that increment, toggle, or write a value to the selected tag.
- Windows.Commands to open a program or file from the Emulator or a View 5000 Client for a project configured with a View 5000 Server HMI device or to open Logix Designer.
TIP:
Tips:
- Create multiple commands for each event. The order of execution may not correspond with the order of commands listed on theEventcard.
- Creating many tag write commands for an event may pause screen updates while the writes occur.
- When an event performs multiple commands that write to multiple tags, all of the write commands occur sequentially. Therefore, you may not see all of the tag values in the Logix controllers at the same time.
Provide Feedback