ReadMe

# Wonderware SCADAlarm 6.0 SP2 ReadMe

Last revision: 4/10/2007

This document contains important information about the WonderwareÒ SCADAlarmÔ 6.0 SP2 software. Please carefully review this document for known issues in this version and changes to the SCADAlarm 6.0 SP2 software included on this CD.

System Requirements

Installation Information

Known Issues

Known Issues - Documentation

Resolved Issues

Release Summary

Documentation

# System Requirements

The following minimum system requirements are recommended:

· Any IBMÒ compatible computer with a Pentium 166 MHz processor (or the minimum required by the operating system)

· At least 100 MB of free hard disk space

· At least the minimum amount of RAM required by the operating system

· Any of the following MicrosoftÒ operating systems:

· Windows 2000 Professional with Service Pack 4

· Windows 2000 Server with Service Pack 4

· Windows Server 2003 Standard Edition with Service Pack 1

· WindowsÒ XP Professional with Service Pack 2

· Modem hardware:

· Internal or external voice modem that supports TAPI

or

· Internal or external data modem that supports TAPI and a sound device

· Receiver (for example, a pager, e-mail server, or phone)

· 800 x 600 video resolution or higher

### Licensing

You can install the SCADAlarm software without a license and run it in "demo" mode for up to two hours. At the end of the two hours, the SCADAlarm software will shut down.

In order to run the SCADAlarm software in "normal" mode, you will need a license. Licenses can be installed and updated using the License Utility. For more information, see the License Utility documentation.

The SCADAlarm software includes a "demo version." This is simply a pre-configured SCADAlarm application that includes a simulated pager/phone. You can select to install the demo version during the installation. If you have a valid SCADAlarm license installed, the demo version will run until the license expires; if not, the demo version will shut down after two hours. The demo version will not allow you to make calls to external devices.

### Supported Software Packages

The following software packages have been tested and are supported:

· Wonderware InTouchÒ 8.0 SP2 P04, 9.0, or 9.5 SP1 software

· Wonderware Industrial Application Server 2.1 Patch 2

· IntellutionÒ iFixÒ 3.5

· SiemensÒ SIMATICÒ WinCCÒ 6.0

· RockwellÒ RSViewÒ32Ô 6.3

· Ci Technologies CiTectÒ 5.40

< top of document >

# Installation Information

Detailed installation instructions are included in the Install-SCADAlarm.chm, which is available in the root of the installation CD. It is recommended that you read the information contained in this Help file prior to beginning the installation process.

< top of document >

# Known Issues

### No support for NetDDE on the Windows XP and Windows 2003 operating systems.

NetDDE is not supported on the Windows XP and Windows 2003 operating systems. If you are using InTouch HMI software as the data server, use SuiteLinkÔ instead of DDE as the communication protocol. If you are using Industrial Application Server as the data server, the use of the Galaxy (Message Exchange) protocol is required. If you are using these operating systems with an HMI other than InTouch HMI software or Industrial Application Server, you will need to run the SCADAlarm software and the HMI on the same node (computer).

### The "Hardware Failure" tag type has been removed from the SCADAlarm software.

TAPI does not provide a mechanism to determine a hardware failure; therefore, the "hardware failure" tag type has not been included in the SCADAlarm 6.0 SP2 software. If you are currently using this type of tag, you will need to delete or disable it. To determine whether the hardware is working, set up a phone line test. For more information on setting up a phone line test, see the SCADAlarm User's Guide or Help file.

### If the SCADAlarm software is running on the Windows XP SP2 or Windows Server 2003 SP1 operating system, you must add the SCADAlarm software to the list of Windows firewall exceptions in order to browse a remote Galaxy.

For the Windows XP SP2 and Windows Server 2003 SP1 operating systems, the Windows firewall will block the SCADAlarm program by default. The first time you attempt to browse a remote Galaxy, a Windows Security Alert dialog box appears, prompting you to unblock the SCADAlarm application. Select Unblock to add an exception to the firewall and allow the SCADAlarm software to browse the remote Galaxy.

### L00016022:

The SCADAlarm software is not able to send SMS messages to the pager becuase of a unique local UCP protocol.

The SCADAlarm software only supports operation input types of 01 and 30. To use an input type of 01, you must configure an advanced modem setting. This setting has been tested with the KPM service provider. Other service providers may require different settings.

To configure the modem to use type 01

1. Start Control Panel.
2. Double-click Phone and Modem Options. The Phone and Modem Options dialog box appears.
3. Click the Modems tab.
4. Select your modem and click Properties. The Modem Properties dialog box appears.
5. Click the Advanced tab.
6. In the Extra initialization commands box, type: AT\N0

The AT\N0 command enables normal speed buffered mode and forces the Q6 command. The AT &6 command enables asynchronous operation in normal mode (speed buffering). The value 110b is written to S27 bits 3, 1, and 0, respectively.

7. Click OK to close the Modem Properties dialog box.
8. Click OK to close the Phone and Modem Options dialog box.

### L00029227:

The InTouch Browse button is not available if the InTouch application that was previously selected has been moved or deleted.

When you open the tag browser using the InTouch browse button, the SCADAlarm software uses the application that was previously opened in the InTouch HMI software. If you delete or move that InTouch application, the InTouch Browse button on the Server tab of the Alarm / Tag Data Point Definition dialog box will not be available. To use a different InTouch application than you originally specified:

1. Open the new application in the InTouch HMI software so that it becomes the default application for the SCADAlarm software.
2. Restart the SCADAlarm software and use the InTouch browse button to browse the new application.

### L00033354:

Wave files (.WAV) can only be located in the \VoxFiles folder. If you attempt to use a .WAV file that is located in a different folder, the SCADAlarm software will prompt you to create a new file.

### L00033535:

The SCADAlarm software starts playing sound files before the operator has picked up the phone.

Some modems cannot detect if the line has been answered or if a hang-up has occurred. The modem TSP (Telephony Service Provider) or driver reports a CONNECTED state even before the phone rings at the destination. For these modems, the SCADAlarm software will show the status as "Connected" to the device, even though no one has picked up the phone yet. The SCADAlarm software will play the notification message as soon as it determines that the status is "Connected." When the operator picks up the phone, he or she may hear a fragment of the notification message. The notification message will repeat every six seconds until the message has been played a total of six times or until the operator logs in, whichever comes first.

### L00034612:

When importing tag definitions from the InTouch HMI software, you cannot select members of a SuperTag.

### L00034915:

If the modem is powered off and then powered on again, the SCADAlarm software must be restarted.

This is a TAPI issue that is currently under investigation by Microsoft. This issue only occurs if the SCADAlarm software is running on the Windows XP operating system. This issue does not occur on the Windows 2000 or Windows Server 2003 operating systems.

### L00037102:

An alarm for a Data Server Status tag to an Industrial Application Server Galaxy only triggers when the Platform for the SCADAlarm node is undeployed and the SCADAlarm software is restarted. A loss of the network connection to the Galaxy does not trigger the alarm.

To work around this issue, monitor a Platform's scan period to determine the status of the communication with the Platform. When the scan period goes to 0 (meaning that the Platform is unavailable), then an alarm is triggered.

For example, two SCADAlarm tags named GRNodeStatus and SAPlatformStatus can be created to monitor communication to two Galaxy Platforms: WinPlatform_001 (GR node) and WinPlatform_002 (SCADAlarm node). The SCADAlarm tags would be configured as follows:

- GRNodeStatus: with Value in Alarm=0; Type of Connection=Get data; Server Item=WinPlatform_001.Scheduler.ScanPeriod

- SAPlatformStatus: with Value in Alarm=0; Type of Connection=Get data; Server Item=WinPlatform_002.Scheduler.ScanPeriod

When the network connection is no longer present, then the GRNodeStatus alarm occurs.

When WinPlatform_002 is undeployed, then both the SAPlatformStatus alarm and the GRNodeStatus alarm occur.

### L00037354:

The Windows operating system crashes and displays a blue screen when you install the Zoom 3048C external serial modem.

This issue is noted for informational purposes; this issue is hardware-based and not related to the SCADAlarm software in any way.

### L00048499:

The user is inundated with repeated emails from the same alarm if the tag's "Acknowledgment" is configured for not "Ack when delivered" (unchecked) and "Wait to expect Ack Call (minutes) after eMail" is set to 0 (zero).

### L00051883:

Using Remote Desktop Connection to troubleshoot SCADAlarm can generate PHIO_PlaySoundFile() Failed errors. Reconfiguring the Remote Desktop Connection options resolve this problem. Under the Local Resources tab in the Remote Desktop Connection options window, select "Leave at remote computer" for Remote computer sound, select "In full screen mode only" for Keyboard, and select nothing (unchecked) for all three Local devices (Disk drives, Printers, and Serial ports).

< top of document >

# Known Issues - Documentation

The following table describes changes to the documentation.

### Item

### Location of Change

### Existing Documentation

### Change

1 | SCADAlarm.pdf: "Alarm Reporting and Acknowledgment" section, page 97 SCADAlarm.chm: "Alarm Reporting and Acknowledgment" topic | The following text is incorrect: "Without a tag report script, SCADAlarm will speak, in the configured text-to-speech voice, a default message that includes the tagname and alarm state." | The text should read as follows: "Without a tag report script, the SCADAlarm software will speak a default message that includes the tagname, description, and alarm state."
2 | SCADAlarm.pdf: "Changing the Alphanumeric Paging Baud Rate" section, page 40 SCADAlarm.chm: "Changing the Alphanumeric Paging Baud Rate" topic | The following paragraph is incorrect: "SCADAlarm only supports three baud rate entries: 300, 1200, or 33600. If any other baud rate is specified, SCADAlarm will revert to 33600." The Pager Service Comm .ini setting of 33600E7 is incorrect. | The paragraph should read as follows: "The SCADAlarm software only supports four baud rate entries: 300, 1200, 9600 and 2400. If any other baud rate is specified, the SCADAlarm software will revert to 2400." The Pager Service Comm .ini setting should be 2400E7.

3

SCADAlarm.pdf: "Telephone Driver Parameters" section, page 232

SCADAlarm.chm: "Telephone Driver Parameters" topic

The default Pager Service Comm .ini setting of 33600E7 is incorrect.

The following statements are incorrect:

"Currently, acceptable values are: 300, 1200, or 33600 bps."

"Therefore, the bps settings of 1200 and 300 actually select the appropriate modulation style, and the 33600 setting allows any negotiable bit rate that can use V.90 modulation."

The default Pager Service Comm .ini setting should be 2400E7.

The statements should read as follows:

"Currently, acceptable values are: 300, 1200, 9600, or 2400 bps."

"Therefore, the bps settings of 1200 and 300 actually select the appropriate modulation style, and the 2400 setting allows any negotiable bit rate that can use V.90 modulation."

The following statement should be added:

"You will need to change the default baud rate settings for the operating system to the settings recommended by your alpha-numeric pager service provider. Note that this applies only to alpha-numeric paging.

4 | SCADAlarm.pdf: "Assigning Hardware Devices to SCADAlarm Functions" section, page 145 SCADAlarm.chm: "Assigning Hardware Devices to SCADAlarm Functions" topic | The dialog box displays Control Panel Selected Device as the default device for local annunciation. | The dialog box should display None as the default device for local annunciation.
5 | SCADAlarm.chm | The copyright link at the bottom of the each topic page is incorrect. | The copyright link at the bottom of the each topic page should display: "2004 Invensys Systems, Inc. All Rights Reserved."
6 | DBDL.pdf: "Overview" section, page 7 DBDL.chm: "Overview" topic | The following note no longer applies: "Version 5.0.3 of this utility is to be used with SCADAlarm version 5.0.3 or later." | The note should be removed from the documentation.

7

Install-SCADAlarm.chm: "Required Modems and/or Devices" topic

In row two of the table, the following text is incorrect:

"All notification features."

In row three of the table, the following text is incorrect:

"All notification features."

In row two of the table, the following text should be:

"All notification features except for local annunciation."

In row three of the table, the following text should be:

"Alpha-numeric paging, e-mail notification, and local annunciation."

The following paragraph should be deleted:

"If the installation program detects a valid TAPI-compliant modem driver (voice/data/fax), but not a valid modem, the system will not be checked for sound devices. If the installation program detects a valid TAPI-compliant modem driver (data/fax only), but not a valid modem, the system will be checked for sound devices."

< top of document >

# Resolved Issues

### L00037655:

The Database Utility program does not export or import Text-to-speech information in the Tag Report Scripts.

### L00039421:

Restarting SCADAlarm multiple times with FS Gateway running can cause SCADAlarm to not connect to FS Gateway until FS Gateway is restarted.

### L00039549:

The Telephone Line Test fails on some telephone network systems due to the absence of a Busy Signal when a telephone line dials itself.

### L00047343:

The "Access violation at address 03401CD9 in module 'voxapi32.dll'. Read of address 000" message is shown in the debug window when there are no modems configured for SCADAlarm.

### L00048489:

I/O device for phone failed.

### L00048725:

Access violation can occur when paging in either alphanumeric or numeric mode.

### L00048727:

The Phone Line Test function interferes with the alphanumeric paging operation.

### L00050692:

Created two new parameters under the Telephone Driver Parameters section in SCADAlarm.INI file, Numeric Page Prefix Pause and Numeric Page Postfix Pause. The default values are 4000 and 1000, respectively. Modify these values only after consulting with Wonderware Technical Support. These values can also be changed from the Configuration | System Parameters | Paging window (HotFix 455).

### L00052997:

Modem hangs up with HotFix 455 (L00050692) to resolve "Busy Paging" signal issue.

### L00053808:

Access violation occurs when SCADAlarm run continuously for over 49.7 days (HotFix 533).

### L00055456:

Numeric paging can stop while SCADAlarm is configured to do both alphanumeric and numeric paging (HotFix 540).

### L00055467:

SCADAlarm only sends out e-mail for new alarms if there are no existing alarms; does not send out e-mail on new alarms if it already has an existing alarm; and new alarms are only sent after "Wait to expect Ack Call (minutes)" has expired.

### L00055997:

Alphanumeric paging randomly stops or is delayed and computer must be rebooted.

### L00060896:

SCADAlarm gets stuck on Busy On Hook (HotFix 610).

### L00061542:

Alphanumeric and numeric paging will stop functioning after receiving a "Busy Paging" signal.

< top of document >

# Release Summary

### New features included in the SCADAlarm 6.0 software:

· MSI-based installation

· Supports TAPI, making the SCADAlarm software device independent

· Support for standard RIFF (i.e., .WAV) files

· Local annunciation over multimedia hardware

· Support for multi-channel

· Independent device configuration

· Support for text-to-speech

· Direct on-site paging support (TAP/UCP)

· Support for Calling Party Identification (CPID)

· Automatic logins based on the caller's phone number

· Restricted logins based on the caller's phone number

· Hacker detection

· InTouch tag browser that supports batch import of InTouch tag definitions into the SCADAlarm software

· Support for Industrial Application Server as a data server

· Industrial Application Server Attribute Browser that supports importing attribute definitions (one at a time) into the SCADAlarm software

< top of document >

# SCADAlarm 6.0 SP2 Documentation

The SCADAlarm documentation includes the following:

· SCADAlarm Installation Help (Install-SCADAlarm.chm). This Help file contains information about installing the SCADAlarm software, including upgrading from previous versions. This Help file is available in the root of the installation CD, as well as from the SCADAlarm installation wizard.

· SCADAlarm User's Guide (SCADAlarm.pdf). This guide contains information about using the SCADAlarm software.

· SCADAlarm Help (SCADAlarm.chm). This Help file contains information about using the SCADAlarm software and can be accessed from the SCADAlarm Help menu.

· SCADAlarm Database Utility User's Guide (DBDL.pdf). This guide contains information about using the database utility to import and export alarm tags and report scripts to and from the SCADAlarm software.

· SCADAlarm Database Utility Help (DBDL.chm). This Help file contains information about using the Database Utility (Tag and Script Utility) to import and export alarm tags and report scripts to and from the SCADAlarm software. This file can be accessed from the Help menu of the Database Utility.

· SCADAlarm Demo ReadMe (ReadMeDemo.html). This ReadMe file provides information on the SCADAlarm demo version and the demo InTouch application.

· SCADAlarm Sound File Conversion Utility ReadMe (VConvert ReadMe.txt). This ReadMe file provides information on how to use the utility to convert sound files. This file can be accessed from the Help menu of the utility.

< top of document >

### © 2007 Invensys Systems, Inc. All Rights Reserved.