TopView 6.17.0 Release Notes (6.17.2)

Version
Type
Description


 
General – Value Status


6.17.2
Change
New alarm processing suppression if tag/row status not good
Existing TopView versions support the alarm condition “status is good” which must be AND’d with the other alarm conditions of the point (e.g. value is > 100 and status is good)
If the row/tag alarm conditions are OR’d (e.g. value > 100 or value < 10) the user could not easily AND the “status is good” condition.
A new option for each tag’s alarm conditions, “Check for good status”, will suppress the processing of alarms if the status of the tag/row is not good.
For tags that have alarm processing suppressed due to this setting, TopView and the Remote Viewer will display “StatusBlock” in the alarm state column.
Descriptions of alarm limits for a tag/row will show (GOODSTATUS) if “check for good status” is enabled for a tag/row.


6.17.2
Change
Alarm logging: tag/row status
Both file and SQL Server alarm logging will store the tag/row status for alarm and RTN events (Good, Bad, Uncertain (uncertain for TopView OPC only))
Note: SQL Server logging users must perform [Connect and Verify Database] from Global Options to add the new status column to the SQL Server alarm log table.


6.17.2
Change
Display of tag/row Status

TopView monitors both tag/row value and status. This version of TopView greatly expands the display of status.
The status of a row value is “Good” or “Bad”. For TopView OPC, the status can also be “Uncertain”

Placeholders

  • %status% will return the tag/row status (Good, Bad, Uncertain)

  • %alarmstatus% will return the status at the time of the most recent alarm

Configurator

  • Value View columns: user can now select Status as a displayable column

  • Displayed limits for a tag/row will show (GOODSTATUS) if “check for good status” option is enabled

  • Scheduled alarm reports can now include status

TopView Engine

  • Values View will display Status if enabled in the configuration

  • State column will display “StatusBlock” if alarm processing suppressed due to “check for good status” option

  • Pop-up tool tip (when mouse hovers over a row) will show current state of Status Block

  • Alarm history details for selected alarm event will show status next to value

  • Export of alarm history list includes status

Remote Viewer

  • Values View can display Status

  • State column will display “StatusBlock” if alarm processing suppressed due to “check for good status” option

  • Pop-up tool tip (when mouse hovers over a row) will show current state of Status Block

  • Alarm history details for selected alarm event will show status next to value

  • Alarm history custom column list: user can add status column

  • Ad-hoc alarm reports: user can add status column

  • Export of alarm history list includes status


6.17.2
Change
AND Gate Block state text changed: “Blocked” now “GateBlock”
The alarm conditions for each monitored point in TopView may be blocked by an optional AND gate. For example, the AND gate can be used to block alarms related to a piece of equipment if the equipment is not running.

In previous versions, the text “Blocked” appeared in the State column for tags/rows with alarm suppression due to the AND gate. This text has been changed to “GateBlock”


6.17.2
Change
Logic Functions: set function return status (good, bad)
TopView Logic Functions allow the user to perform logic operations and calculations involving one or more inputs (e.g. tag values). The return value from a logic function (the function result) can be monitored just like any other tag in TopView, allowing the user to apply alarm conditions and notification to the function result.

Each Logic Function can now set a boolean value “FunctionFail” to return a function status with the function result. If FunctionFail is True, the tag/row that calls the function will have a status of Bad.

FunctionFail is set to False at the start of each function execution.

A new sample function that uses FunctionFail (named xReturnBadStatus ) is installed with TopView.


 
Fixes


6.17.2
Fix
Export of alarm log from TopView Engine and Remote Viewer
“Export Successful” message incorrectly appeared behind main application.


6.17.2
Fix
Output point error: Error outputting value () to …
For TopView OPC, if we could not determine the output tag data type, the conversion of the specified output point value to the tag datatype would fail resulting in no value to output ().
We will no longer attempt to convert the value before sending it if using the newer OPC layer.


Version
Type
Description


 
General


6.17
Change
Inheritance – Tag Alarm & Notification Setting
Each monitored TopView tag contains a group of settings related to the tag’s configured alarm conditions, notification, and escalation.

A common scenario is for related tags to share the same alarm limits and notification settings. In previous versions, the settings are stored for each tag, so changes to one tag must be duplicated for the related tags (bulk export/import allows the user to make these changes quickly).

Tag Inheritance allows a tag to inherit its alarm and notification settings from another tag. When the other tag (the template tag) is configured and/or edited, all tags that inherit these settings will automatically see the same settings.

The inherited settings can include Alarm Limits and Notification, Escalation, Return to normal, Acknowledge options, AND gate, Custom Response, and Event Output Points


6.17
Change


6.17
Change
POP Incoming email: process attachments
TopView supports incoming email for alarm acknowledge and information request. TopView processes the email subject and message body to find the request or acknowledgement information.

If the incoming email contains attachments, TopView will now convert each attachments to text and will process the attachment text to find request and acknowledgement information.

Reason: when the iPhone on Verizon replies to a text message which was generated via email (e.g. 5551112222@vtext.com for Verizon), the sending email address will receive the response via email, but the text message sent by the iPhone user appears as an attachment to the email. This prevented alarm acknowledge from some Verizon iPhones users since TopView did not previously process attachments.


6.17
Change
POP Incoming email: process HTML-only message
If the incoming email contains an HTML-only message body without a text-equivalent message body, TopView will now process the HTML body to find request and acknowledgement information.

Reason: when the iPhone on AT&T sends a text message to an email address, the received email message contains an HTML body but not a text-equivalent message body.


6.17
Change
New status tag & performance counter – PI EventPipe event count (TopView PI)
TopView PI uses a PISDK PointList EventPipe to receive new tag values from the PI Server. A new TopView status tag and TopView Performance Counter (pi_pe_count) contains the number of EventPipe values during the most recent refresh.

If an EventPipe fails (stops receiving new values from the PI Server), this value will go to zero and remain at zero. The new status tag can be used to create a TopView alarm condition and notification for a failed EventPipe (e.g. alarm if value = 0 for 120 seconds).


6.17
Change
Tag Groups: specify Escalation Template per group
In previous versions, Tag Groups could specify an optional notification recipient – tags that belong to the Tag Group would then inherit this notification setting (notification at the time of alarm).

Each Tag Group now contains an optional Escalation Template – tags that belong to the Tag Group will inherit this escalation (additional notification after the initial alarm).


6.17
Change
Escalation: notification message per escalation step
Notification Escalation in TopView is configured through Escalation Templates. Each Escalation Template consists of a set of steps that define the escalation condition (e.g. unacknowledged for 3 minutes) and escalation notification recipients. In previous versions, the escalation notification message was the same as the alarm notification message, although the user could add a description of the step (e.g. “alarm unacknowledged for 3 minutes”).

Each escalation step can now define a different notification message. The options are to (1) use the original alarm notification message or (2) use a specific notification message template.


6.17
Change
Text to speech (TTS): “rate” property added (speed of generated speech)
TopView TTS converts messages to spoken words for Audible Alarms and Voice Notification.

The configuration of TTS now includes a rate property to control the speed of the generated speech.


6.17
Change
Max refresh rate increased
The TopView Engine will now allow refresh rates up to 300 seconds. Previous maximum was 60 seconds


6.17
Change
Operations: Absolute value operation added (ABS)
Each monitored point/tag has an optional Operation field. Operations allow the user to perform calculations, logic, mathematical operations, and comparisons on a retrieved tag value.

A new operation for absolute value (of the retrieved tag value) has been added.


6.17
Change
Outgoing email “From” address: support for long form
The From email address for outgoing TopView email can now specify the name of the email address.

Example: “John Smith”<j.smith@company.com>

Notes:

(1) there should be no space between second ” and <

(2) your SMTP server may not support this syntax and may force the name to a known value for the email address