How to add alarms in factory talk view studio

For a straightforward setup, I recommend one BOOL tag per alarm, with a Value trigger of 1 in the HMI.

1. Back up the existing applications

Before editing:

1. Save a copy of the Studio 5000 .ACD file.
2. Back up the FactoryTalk View ME application using Application Manager.
3. Keep the currently working .MER runtime file.
4. Record the PLC address, HMI address, communications shortcut, and terminal runtime version.

2. Decide how each alarm should behave

Write down these items before programming:

Acknowledging an alarm and resetting a machine fault are separate actions. Acknowledgment means the operator has seen the message. Reset changes the fault state through PLC logic.

3. Create the PLC alarm tags in Studio 5000

Under Controller Tags, create:

Use controller-scoped tags for this example.

Set External Access appropriately:

• ALM_Infeed_Jam: Read Only.
• HMI_Fault_Reset_PB: Read/Write.

Define the input meaning explicitly: Infeed_PE_Blocked = 1 must mean the beam is blocked, regardless of the physical sensor’s electrical polarity.

4. Program the alarm condition

Choose one of these approaches.

Option A: Alarm automatically clears when the condition disappears

When the photoeye clears, the timer resets and the alarm BOOL becomes false.

Option B: Alarm stays latched until a valid reset

For Option B, configure the HMI Reset button as Momentary. Keep machine-stop and restart behavior in the PLC logic.

Make sure the alarm routine is actually called by the executing program.

5. Verify PLC-to-HMI communications

In FactoryTalk View Studio ME:

1. Open the HMI application.
2. Expand FactoryTalk Linx—called RSLinx Enterprise in older versions.
3. Open Communication Setup.
4. Select the existing PLC shortcut, or create one such as PLC.
5. Under Design (Local), associate the shortcut with the correct controller.
6. Apply the association.
7. Check Runtime (Target) and verify the controller path the terminal will use.
8. Copy the Design configuration to Runtime only when that path is also correct for the terminal.

The Design configuration supports development testing; Runtime defines the terminal’s communications. A working desktop test does not prove the terminal path is correct. rockwellautomation.com

6. Add the alarm trigger

In the application tree:

1. Expand Alarms.
2. Double-click Alarm Setup.
3. Select the Triggers tab.
4. Click Add.
5. Use the Tag Browser to select ALM_Infeed_Jam through your PLC shortcut.
6. Set Trigger type to Value.
7. Give the trigger a descriptive label, such as Infeed_Jam.

For the initial setup, leave optional acknowledgment and handshake connections unassigned. Those connections require additional PLC/HMI coordination. Rockwell’s Alarm Setup editor separates trigger configuration, messages, and advanced display settings. rockwellautomation.com

7. Add the alarm message

On the Messages tab, add a row:

For an automatically clearing alarm, use a message such as:

Infeed photoeye blocked longer than 3 seconds. Check for an obstruction.

The Display checkbox requests the configured alarm popup. Messages can still be recorded and shown in alarm objects when this checkbox is unchecked. rockwellautomation.com

Repeat Steps 6–7 for each BOOL alarm tag.

8. Select the popup display and enable alarms at startup

1. Open the Advanced tab in Alarm Setup.
2. Select the alarm display to open, commonly the existing [ALARM] display.
3. Review the alarm update rate, notification hold time, and history capacity.
4. Save Alarm Setup.
5. Open the application’s Startup editor.
6. Verify that Alarms is selected.

Both the display selection and Startup setting matter. literature.rockwellautomation.com

9. Create an operator alarm screen

Create a display named something like Alarm_Screen.

Include:

Check the alarm objects’ trigger filters so your new alarms are included.

Alarm buttons are available under Objects → Advanced → Alarm. Rockwell provides separate objects for alarm lists, status lists, banners, and acknowledgment controls. rockwellautomation.com

Do not use an acknowledgment button as your PLC fault-reset command. Wire the separate Reset button to the reset tag and let the PLC enforce reset conditions.

10. Test the complete application

Use Test Application, then verify the following with a controlled test condition:

Use a dedicated test tag or an approved commissioning method. Avoid forcing a live machine output just to test an HMI message.

11. Build and transfer the runtime application

1. Save the HMI application.
2. Select Application → Create Runtime Application.
3. Choose a runtime version supported by the terminal.
4. Create the new .MER.
5. Transfer it with ME Transfer Utility or your established transfer method.
6. Load and run the application on the PanelView.
7. Verify the terminal’s PLC communications.
8. Repeat the alarm activation, acknowledgment, clearing, and reset tests on the actual terminal.

Also check the terminal’s date and time so alarm timestamps are useful.

12. Document the finished alarms

Record each alarm’s:

• PLC tag and activation logic.
• HMI trigger type and trigger value.
• Message and popup behavior.
• Clearing and reset conditions.
• Test result, tester, and date.

If you use a DINT alarm word instead

The trigger setup changes when multiple alarms occupy bits in one DINT.

For example, if the trigger is the whole tag HMI_Alarm_Word with trigger type Bit:

ME Bit trigger values are bit positions starting at 1. Use Bit to report simultaneous alarms. LSBit prioritizes the lowest active bit rather than reporting every active bit simultaneously. rockwellautomation.com

For your first implementation, the individual BOOL → Value trigger → Trigger Value 1 method will be easier to follow and troubleshoot.

#How-to-add-alarms-in-factory-talk-view-studio