HMI text for PINTLK instructions

Use the
HMI
tab on the
PINTLK Properties
 dialog box to enter text that appears on HMI devices for the instruction.
To enter HMI text for Process Interlocks (PINTLK) instructions
  1. On the instruction in the routine, perform one of these actions:
    • On the Ladder or FBD instruction, select .
    • In the Structured Text editor, right-click the tag name and select
      Configure <tag name>
      .
  2. Select the
    HMI
    tab.
  3. Configure these settings:
    • Library name
      . Associates instructions with a display library for faceplate call-up.
    • Instruction name
      . Associates the instruction name for faceplate call-up.
    • Display label
      . A label that appears on the graphic HMI symbol.
    • Area name for security
      . The area name for area-based security in the HMI.
    • Help button URL
      . URL for accessing help from the HMI.
    • Enable navigation to an object with more information
      . Select this checkbox to enable navigation to another source of information. In the box, enter the navigation path to the object, document, or website.
    • Operator command confirmation required
      . Configure operator commands and settings to require confirmation or to apply an e-signature from the HMI. Select:
      • None
        –command requests do not require confirmation by the operator.
      • Command confirmation
        –command requests require confirmation by the operator. This option displays a dialog asking the user to confirm the action.
      • Performer e-signature
        –command requests require an operator signature. This option enforces security from the HMI and disables commands and settings from the Logix Designer dialog.
      • Performer and approver e-signatures
        –command requests require both operator and supervisor signatures. This option enforces security from the HMI and disables commands and settings from the Logix Designer dialog.
  4. Select
    Apply
    .
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.