In reply to David-m.walker:

One thing to remember when deleting the device out of the AMS DM database. You will delete also the history of that device and calibration records. Using DelDev.exe only if you don't need that device information in AMS DM anymore and/or get rid of a test device tag to release a AMS license tag.
Mojola: What is that you are trying to accomplish?
Best Regards,
Tinh

In reply to Tinh Phan:

I am trying to delete the tag because the device doesn't exist anymore and its been decommissioned from the controller .Yet the controller is giving me a 'COMM_ALM' alarm.

In reply to David-m.walker:

How do you mean when you say terminate the AMS server? Do you mean Start menu >> AMS >> Terminate server? WIll that affect the other devices running on AMS and the controller, and how will you start the server back if you terminate the AMS server? Can you show a snip of that. Thanks.

In reply to Mojola:

Yes, use Start menu >> AMS >> Terminate server but you will need to do this for all AMS DM Stations you have. Once you done deleting the device out of the database, just launch AMS again and it will startup all the services.

In reply to Mojola:

Do you have a DeltaV system? If you do, you can disabled this alarm without deleting the device out of AMS database.

In reply to Tinh Phan:

Yes, I do have deltaV System. Thanks for the help. I was able to delete the tag from AMS DM Stations . But the COMM_ALM still exist on Alarm list on DeltaV.

In reply to Mojola:

Fieldbus device?

Check in Books Online:

Clearing COMM_ALM alarms when a fieldbus device is removed from the segment

In reply to John Rezabek:

For non-fieldbus devices and nodes you can use the procedure starting at step 3d and it will work to clear the alarm out of the alarm list.

In reply to John Rezabek:

I did exactly what you said. The alarm went off the moment I download the new control module I created.
But the alarm came back after I delete the new control module. That was why I felt, the alarm came back because the device tag still exist in AMS.
I was able to delete the tag in AMS, Thanks to Tinhand Dave but the alarm still exist,Iam getting a prompt from the PC anytime I tried launching any device on AMS saying " unable to connect to Live device, AMS server need to be restarted. I opened AMS on ProPlus but the prompt keeps coming up. Not sure if I haven't restarted the AMS server

In reply to Mojola:

I would expect that you will still get this alarm bc DeltaV still is looking for this alarm and the system don't see a response from the device when DeltaV ask for it.
Is this a Fieldbus or HART device?

In reply to Tinh Phan:

Hart Device

In reply to Mojola:

That is always the challenge in a forum like this is one asks for help on one task, and we all try to help you do it. But in reality the problem was unrelated to the specific ask.

In DeltaV Alarms are generated at the source (in the controller, or FF Device), and are sent to every workstation that subscribes to the assigned plant area of the alarm source. Once the alarm is in the Alarm System, it awaits a new alarm state message, such as alarm inactive, Acknowledged, etc. By deleting the module, the active COMM alarm can not be cleared.

By recreating an alarm in a temporary module, as John explained, the Alarm can report its current status and in the case of the device COMM alarm, it can go inactive and thus clear.

The issue is how to remove this alarm with out triggering it inadvertently. With FF, there is the added challenge that the COMM alarm is generated based on the device to controller communication status, which we can't recreate without the device. Hmm.

All this has nothing to do with the device in AMS DM. That data is now lost unless you have a back to restore from, but that would remove events since the deletion.

If you were able to remove the alarm with a simulated alarm in a module, then I'd suggest doing so again. Once the alarm is gone, and before you delete this module, create a new Plant Area and move the module to this area is not assigned to any workstation. Down load set up data to all workstations so that they are aware of this change in alarm reporting. This will make it such that no console will care when the module is deleted and that should prevent it from popping back up when you delete the module.

Comm alarms occur at the destination. When an alarm source is no longer communicating, it is the destination node that sets a loss of comm on the item. Makes sense since the source is no longer communicating, how can it tell anyone of that condition. If this is a device alert (COMM FAIL) alarm, and we are mimicking it with a module alarm (Process alarm, not Device alert), there is an added twist.

Andre Dicaire

In reply to Andre Dicaire:

My bad. Thought it was FF. Much easier to take any FF device and connect it to the same channel to recreate device alarms. Keep DST name the same, even if the device tag is left at something else. Don't rebuild hierarchy in AMS DM while temp device is connected. But moving module to new Area once alarm is inactive as mentioned above should prevent alarm from coming back.

Andre Dicaire

In reply to Tinh Phan:

You might need to go to that device and change the Comm_Alm priority to Log only. It will not show up in your DeltaV Operate Alarm page but it will get log into your ejournel. Here is a paper I wrote long time ago but it still apply to this situation.
emersonexchange365.com/.../3179