{"searchBar":{"inputPlaceholder":"Search by keyword or ask a question","searchBtn":"Search","error":"Please enter a keyword to search"}}

Welcome to the Schneider Electric Website

Welcome to our website.

Select your location

Welcome the the Schneider Electric French website. It looks like you are located in the United States, would you like to change your location?

Traduisez en francais
{"support":{"yesButton":"Yes","noButton":"No","feedback":{"title":"What can we do to improve?"},"submitButton":"Submit","successMessage":"Thank you for your feedback","title":"Was this helpful?","feedbackPercentLabel":"of people found this helpful","captcha":{"error":"Please tick the box"}}}
Search FAQs

Event Notification Module 8.3 (ENM) Hotfix 47138 - ENM sends Measurement ID instead of Measurement Name and alarm active time shows UTC Timestamp

If ENM 8.3 is configured to alarm on events in which any of the Cause/Cause Value/Effect/Effect Value fields are measurement IDs, the ID is not converted to a localized measurement name string, but instead passes through as a raw number. This may cause confusion from a user perspective when a number is displayed instead of a measurement name.

Also Alarm Activetime shows UTC Timestamp.

Product Line
Event Notification Module (ENM) 8.3
Power Monitoring Expert (PME) 8.0

Event Notification Module - Event Notifications

These are known issues with ENM 8.3 and is addressed in hotfix 47138.  It is recommended to apply this hotfix to all ENM 8.3 installs.

*Warning: Take backups of any files prior to modifying them. Ensure the backups are in a location that will not be overwritten (i.e. the Desktop).

Apply hotfix 47138

1. Extract Alarms.EnmAlarms.dll from the attached zip.
2. Stop the ION Software Alarm Service if running
3. Copy and replace the extracted Alarms.EnmAlarms.dll into the System\Bin folder in the Power Monitoring Expert directory. (Default install location: C:\Program Files (x86)\Schneider Electric\Power Monitoring Expert\)
4. Start the ION Software Alarm Service if stopped in step 2.