Essential Guide to Configuring Alarms in FactoryTalk View ME Edition

Question:

Hello everyone, I am in the process of upgrading from the PV550 to the PV700+ and designing all screens in FactoryTalk View ME Edition. However, I've encountered some challenges with the alarm setup. Most of my alarms are configured in the N7:1 register (16-bit) as an "alarm address array," while the N7:2 register is designated for the "reset alarm address array." In FactoryTalk View, I started by creating new tags as follows: - **Alarm1 Digital Data Source**: Device Address - `::[program]N7:0/1` Next, I proceeded to the alarm setup, where I selected "Alarm1" as the trigger and set the trigger type to "Value," with the label "some message." I have a couple of questions: 1. Do I need to utilize the acknowledge bit in N7:2 for resetting the alarm in the optional trigger connections? 2. Is using `::[program]N7:0/1` a valid address, or should I opt for `::[program]N7:0 [L1]`? I’ve noticed some discussions on forums advising the use of `[L1]`. I would greatly appreciate any assistance in properly configuring these alarms. Your help would mean a lot to me!

Top Replies

Your alarm activation will be represented as "::[program]N7:0]". To select the trigger type, opt for the bit trigger option, which allows the trigger to be determined by the specific bit position (for example, N7:0/0 corresponds to 1 and N7:0/15 corresponds to 16).

What version of FT are you currently using?

Chopin inquired: "Which version of FT are you currently utilizing?" Click to reveal more details... I'm presently on version 6.00 (CPR 9 SR 3).

User tarik1978 inquired: "How should I configure my alarm trigger? Is it sufficient to use the notation '::[program]N7:0]' for selecting the bit trigger type, which allows for triggering based on the bit position (ranging from N7:0/0 for 1 to N7:0/15 for 16)? Should I specify '::[program]N7:0[L1]' or simply '::[program]N7:0' along with the corresponding bit values for the trigger? Additionally, is it necessary to include an acknowledgment process to clear the alarm?"

You can use the commands {::[shortcut]N7,L3} or {::[shortcut]N7:0,L3} to optimize your alarm system. When you specify L3, you're designating N7:0, N7:1, and N7:2 as your alarm triggers. This setup allows for trigger values ranging from 1 to 15, and continuing from 16 to 33, and up to 48. With each N register comprising 16 bits and accommodating three registers, you essentially have a total of 48 available trigger values. To manage your alarms effectively, take advantage of the built-in acknowledge button and the alarm clear button. These features are ideal for basic applications. If your project requires advanced alarm management capabilities, you have the option to create custom logic for acknowledging and clearing alarms. However, rest assured that the built-in functionalities meet the needs of 99% of typical applications.

More Replies →

Streamline Your Asset Management
See How Oxmaint Works!!

✅   Work Order Management

✅   Asset Tracking

✅   Preventive Maintenance

✅   Inspection Report

We have received your information. We will share Schedule Demo details on your Mail Id.

You must be a registered user to add a comment. If you've already registered,
sign in. Otherwise, register and sign in.

Frequently Asked Questions (FAQ)

Ready to Simplify Maintenance?

Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.

Request Demo  →