## Alarms for converted SuperVision® systems A WebCTRL® system can support alarms generated from SuperVision (Exec 6 and earlier) hardware. However, if your system includes any Exec 3 or Exec 4 controllers with older function blocks, you are limited to the older Exec 3-style trends and alarms. The WebCTRL® sequence for alarm generation and delivery is similar to the alarm sequence in a SuperVision system: A function block in a controller generates an alarm based on hardware inputs and user-defined conditions. The Alert microblock in the function block turns on, then sends alarm information to the router. The router transmits the alarm to the WebCTRL® application. The WebCTRL® application uses the Event ID contained in the alarm to associate it with the reference name of an alarm template. Or, if the single alarm template option was chosen during the InterOp® conversion, the template alert_auto is used and the text which includes the Event ID in the file cmnet_alert_text.properties is displayed. For Exec 3-style bit alarms, the Alarm Text number contained in the alarm is used to associate the alarm with the reference name of an alarm template (or the appropriate text in the file cmnet_alert_text.properties if using the single alarm template). See Exec 3 bit alarms. NOTE If you are using a CMnet/IP connection to receive alarms, you must type the CMnet Station Number when you configure the connection. See "Setting up CMnet connections for converted SuperVision systems" in the SuperVision Support Manual found at http://accounts.automatedlogic.com/download. Alarms from SuperVision hardware can be simulated in the WebCTRL® interface. See Setting up an alarm source in the WebCTRL® interface.
Click for details below Modifying Event IDs Including Alert alarm text in WebCTRL® alarm templates Exec 3 bit alarms
### Modifying Event IDs After the SuperVision® function blocks have been converted to a WebCTRL-compatible format, if an alarm template was created for each legacy alarm name, the Event ID contained in an Alert microblock-style alarm determines which alarm template is used. To change the Event ID of an Alert microblock in the WebCTRL® interface On the Geographic tree, select the piece of equipment. Click Properties. Verify that the Parameters tab is selected. Scroll to the portion of the screen that contains the parameters for the Alert microblock. Select the Event ID field, then type the desired ID. Click Accept. To change the default Event ID of an Alert microblock in Eikon CAUTION Make this change in Eikon, not the EIKON® application. Start Eikon. In the Edit Variables mode, click the Alert microblock. Type the new Event ID in the Alert MB pop-up. After the function block has been successfully compiled and saved, this ID will be used as the default Event ID for this alarm for all instances of this function block.
### Including Alert alarm text in WebCTRL® alarm templates The InterOp Conversion Wizard includes Alert alarm text in the .interop file. The Alert alarm text is automatically added to the short and long text fields in the new WebCTRL® alarm templates. The Off Normal Short Text field defaults to "$Field_Message$ is in alarm." The field code “$Field Message$” retrieves the address and Event ID from the equipment where the alarm was generated. NOTE Field codes automatically convert to their WebCTRL® equivalent, but their formatting does not. You will need to redo any formatting. See Formatting field codes. Optional - Single alarm template If the single alarm template option was chosen during the InterOp Conversion, a file was generated in the WebCTRLx.x\webroot\<system_name> folder called cmnet_alert_text.properties. For any alarms which use the Alert Auto template, the WebCTRL® application will look up the appropriate text in this file. NOTE If the system was originally created without using this option, the file can be created, alarm text added to it, and then any appropriate alarms can be assigned to the Alert Auto template and the cmnet_alert_text.properties will be used. To edit the text for any alarms using the Alert Auto template, edit cmnet_alert_text.properties. (Text prefixes and suffixes can still be added using the in the WebCTRL® interface). The following is the format for text in the cmnet_alert_text.properties file: EVENT_ID.alarmshort=Short alarm text. EVENT_ID.alarmlong=Long alarm text \r\n Long text line 2:\r\n Long text line 3 EVENT_ID.normalshort=Return to normal short text. EVENT_ID.normallong=Return to normal long text \r\n Long text line 2:\r\n Long text line 3 HI_ZONE.alarmshort=High Zone Temp HI_ZONE.alarmlong=High Zone Temp \r\n At the time of the alarm:\r\n Zone Temp = $latched_data_analog:1$ HI_ZONE.normalshort=Zone Temp is normal. HI_ZONE.normallong=Zone Temp is normal. NOTE “\r\n” is used to determine where a carriage return (CR or Enter) should be placed when the alarm is displayed in the WebCTRL® interface. The entire text string should be typed in with no CRs used on the keyboard until the end of the field.
### Exec 3 bit alarms The WebCTRL® application uses the Alarm Text number defined on the Parameters page to determine which alarm template to use. When a bit alarm or message is received, the WebCTRL® application uses the message text number preceded by an "a" or an "m" to display the alarm template. For example, if a particular bit alarm has the number "31" defined as its alarm text,t he WebCTRL® application uses the alarm template with a reference name of "a31". Bit alarms are automatically assigned to the General Alarm alarm category. Bit messages are assigned to the General Message alarm category. To modify the message text for a bit alarm On the Geographic tree, select the equipment. Click Properties. Verify that the Parameters tab is displayed. Change All Options to Y. Select the appropriate bit alarm message text field, then type the new number. Click Accept. See Including Alert alarm text in WebCTRL® alarm templates.