Wonderware Bristol Babcock OpenBSI I/O Server User's Guide

Wonderware® Bristol BabcockOpenBSI® I/O Server

User’s GuideRevision DNovember 1999

Wonderware Corporation

All rights reserved. No part of this documentation shall be reproduced, stored in a retrievalsystem, or transmitted by any means, electronic, mechanical, photocopying, recording, orotherwise, without the prior written permission of the Wonderware Corporation. No copyrightor patent liability is assumed with respect to the use of the information contained herein.Although every precaution has been taken in the preparation of this documentation, thepublisher and author assume no responsibility for errors or omissions. Neither is any liabilityassumed for damages resulting from the use of the information contained herein.

The information in this documentation is subject to change without notice and does notrepresent a commitment on the part of Wonderware Corporation. The software described inthis documentation is furnished under a license or nondisclosure agreement. This softwaremay be used or copied only in accordance with the terms of these agreements.

Wonderware Bristol Babcock OpenBSI I/O Server User’s Guide

© 1999 Wonderware Corporation. All Rights Reserved.

100 Technology DriveIrvine, CA 92618U.S.A.(949) 727-3200http://www.wonderware.com

TrademarksAll terms mentioned in this book that are known to be trademarks or service marks have beenappropriately capitalized. Wonderware Corporation cannot attest to the accuracy of thisinformation. Use of a term in this book should not be regarded as affecting the validity of anytrademark or service mark.

Wonderware and InTouch are registered trademarks of Wonderware Corporation.

FactorySuite, WindowMaker, WindowViewer, SQL Access Manager, Recipe Manager, SPCPro, DBDump, DBLoad, HDMerge, HistData, Wonderware Logger, InControl, InTrack,InBatch, IndustrialSQL, FactoryOffice, Scout, SuiteLink and NetDDE are trademarks ofWonderware Corporation.

i

Contents

Introduction ......................................................................................................................1Communication Protocols .........................................................................................1Accessing Remote Items via the I/O Server ..............................................................3

Report by Exception (RBE) Signals .................................................................................4

Alarm Signals ...................................................................................................................5

Ethernet.............................................................................................................................5

Configuring the I/O Server ...............................................................................................6

Saving the I/O Server’s Configuration File.......................................................................7Save Configuration ....................................................................................................7Saving Multiple Configuration Files..........................................................................7

Configuring a Topic Definition ........................................................................................8Topic Definition ........................................................................................................8BSAP Topic Definition .............................................................................................9

Configuring the I/O Server Settings................................................................................10Server Settings.........................................................................................................10

Accessing I/O Server Help .............................................................................................12Contents...................................................................................................................12How to Use Help .....................................................................................................12About BSAP ............................................................................................................12

Item Names.....................................................................................................................13Bristol Babcock Inhibit Bits ....................................................................................13Force Control Bit.....................................................................................................13Specifying Discrete Data Type ................................................................................14Server Specific Predefined Diagnostic and Control Items.......................................14

Monitoring the Status of Communications with a PLC...................................................17Using the Status Item in Excel.................................................................................17

Monitoring the Status of Communications with InTouch ...............................................17Using DDEStatus and IOStatus in Excel .................................................................17

Reading Values from the I/O Server into Excel..............................................................18

Writing Values to the I/O Server from Excel..................................................................19

Troubleshooting I/O Server Communication Problems..................................................20Debugging Communication Between InTouch and an I/O Server...........................20Debugging Communication Between SuiteLink and an I/O Server.........................22Debugging Communication Between an I/O Server and a PLC ..............................23

ii Table of Contents

Wonderware Bristol BabcockOpenBSI I/O Server

IntroductionThe Wonderware® Bristol Babcock OpenBSI® I/O Server (referred to as the serverthrough the remainder of this user’s guide) is a Microsoft® Windows applicationprogram that acts as a communication protocol server. It allows other Windowsapplication programs to access data within Bristol Babcock Network 3000 Controllers.This server supports both serial and Ethernet communications with Bristol Babcocknetwork of controllers and RTUs. The Wonderware Bristol Babcock OpenBSI I/OServer is not a standalone server. It requires the use of Bristol Babcock’s “Open BristolSystem Interface” software utilities (OpenBSI Utilities Version 3.1 and later). Prior toexecuting and configuring this server, the OpenBSI driver must be properly configuredand started. Please contact Bristol Babcock for further instructions on installing andconfiguring any of the OpenBSI utilities. Bristol Babcock OpenBSI Utilities manageboth the serial and the Ethernet communications lines as well as the network ofcontrollers connected to those lines. It allows sharing of these resources among severalapplication programs running concurrently under Microsoft Windows. All applicationscan use the standard interface that is provided. The NetView tool of Bristol BabcockOpenBSI Utilities must be running at the time the server is started. Otherwise, theserver will run but not connect to Bristol Babcock’s OpenBSI driver.It just prints a message in Wonderware Logger and waits for Bristol Babcock’s NetViewto start.

Through the use of global messages, the Wonderware Bristol Babcock OpenBSI I/OServer is able to access data from the direct attached Controller as well as from otherControllers in the same network.

While the server is primarily intended for use with Wonderware InTouch® (version 3.01and later), it may be used by any Microsoft Windows program capable of acting as aDDE, FastDDE, or SuiteLink™ client.

Communication ProtocolsDynamic Data Exchange (DDE) is a communication protocol developed by Microsoft toallow applications in the Windows environment to send/receive data and instructionsto/from each other. It implements a client-server relationship between two concurrentlyrunning applications. The server application provides the data and accepts requestsfrom any other application interested in its data. Requesting applications are calledclients. Some applications such as InTouch and Microsoft Excel can simultaneously beboth a client and a server.

FastDDE provides a means of packing many proprietary Wonderware DDE messagesinto a single Microsoft DDE message. This packing improves efficiency andperformance by reducing the total number of DDE transactions required between aclient and a server. Although Wonderware's FastDDE has extended the usefulness ofDDE for our industry, this extension is being pushed to its performance constraints indistributed environments.

2 Wonderware Bristol Babcock OpenBSI I/O Server

NetDDE™ extends the standard Windows DDE functionality to include communicationover local area networks and through serial ports. Network extensions are available toallow DDE links between applications running on different computers connected vianetworks or modems. For example, NetDDE supports DDE between applicationsrunning on IBM® compatible computers connected via LAN or modem and DDE-awareapplications running on non-PC based platforms under operating environments such asVMS™ and UNIX®.

SuiteLink uses a TCP/IP based protocol and is designed specifically to meet industrialneeds such as data integrity, high-throughput, and easier diagnostics. This protocolstandard is only supported on Microsoft Windows NT 4.0 or higher.

SuiteLink is not a replacement for DDE, FastDDE, or NetDDE. The protocol usedbetween a client and a server depends on your network connections and configurations.SuiteLink was designed to be the industrial data network distribution standard andprovides the following features:

l Value Time Quality (VTQ) places a time stamp and quality indicator on all datavalues delivered to VTQ-aware clients.

l Extensive diagnostics of the data throughput, server loading, computer resourceconsumption, and network transport are made accessible through the MicrosoftWindows NT operating system Performance Monitor. This feature is critical for thescheme and maintenance of distributed industrial networks.

l Consistent high data volumes can be maintained between applications regardless ifthe applications are on a single node or distributed over a large node count.

l The network transport protocol is TCP/IP using Microsoft’s standard WinSockinterface.

Introduction 3

Accessing Remote Items via the I/O Server The communication protocol addresses an element of data in a conversation that uses athree-part naming convention that includes the application name, topic name and itemname. The following briefly describes each portion of this naming convention:

application name The name of the Windows program (server) that will be accessingthe data element. In the case of data coming from or going toBristol equipment via this server, the application portion of theaddress is BSAP.

topic name Is an application-specific sub-group of data elements. TheWonderware Bristol Babcock OpenBSI I/O Server considers eachcontroller to be at least one separate topic. The operator createsmeaningful names for the controllers and uses these names as thetopic names as references, for example, GasFlowController. Ifdesired, a single controller can be divided into several differenttopics, each with its own unique name. This might be done inorder to logically organize multiple functions within a singlecontroller.

For example, a controller could be configured with one topiccalled TempControl and a second topic called GasFlowControl.Multiple topics per controller are also useful when one group ofdata items within a controller is desired to be polled frequentlywith a second group to be updated less frequently. Thiscontrolled polling rate technique can be useful to efficientlyutilize a Bristol Babcock OpenBSI network's finitecommunications bandwidth.

Note: You can define multiple topic names for the same device(PLC) to poll different points at different rates.

item name A specific data element within the specified topic. For example,when using this server, an item can be a relay, timer, counter,register, etc., in the PLC.

Note: The item/point names are predefined by the server. Theterm "point" is used interchangeably with the term "item" in thisuser's guide.

$ For more information on item/point names, see the "ItemNames" section later in this user's guide.


Report by Exception (RBE) SignalsThe server supports RBE signals (see Bristol Babcock documentation). If the user hasconfigured some of the items (signals) in the controller as RBE items and has enabledthe RBE task, then the server will accept and process the unsolicited RBE messages.The process of defining an item (signal) as RBE in the controller is done by using theBristol Babcock programming software and not by the server.

When configuring the RBE module, the recommended terminal settings are as follows:MODE = 01STOPXMIT = 00FORMAT = 01

In this way, the RBE system will use parameter settings defined in the ACCOL filewhich become active immediately at the RTU initialization time. However, if the RBEsystem parameters are to be specified by users at initialization, the terminal settingsMODE = 00 should be used. In this way, the RBE task enters the wait state atinitialization until it receives a valid initialization request from the host workstation atstartup of the server. The following is a sample showing default RBE system parametersadded by the users to the WIN.INI file for the initialization of the RBE system.

[BSAP]Scanrate = 36000Scanslice = 1Format = 1Stopxmit = 1Timeout = 36000

Users can modify these settings for their own particular needs.

Note: For details on RBE Mode settings, see Bristol Babcock’s Network 3000Communications Application Programmer’s Reference, D4052, Appendix D, RBE,Section 3.2.

The RBE messages will be received by the server as unsolicited messages. In order forthis to be meaningful, the user of the server must generate a client application (usuallyInTouch) that requests data for these RBE items (just as for any other item). If an RBEmessage is received by the server and there is no client that has requested the data (putitem on advise), then the data is discarded.

If you are using a controller that has both RBE items and non-RBE items defined, then itis suggested that you define two different topics for the same controller. One of thetopics, say Topic1, could process all of the RBE signals and has a 0 poll period (or avery long poll period), and the other topic, say Topic2, could process the non-RBEitems and has some standard poll period defined. In this case, you would set up yourInTouch application to use Topic1 to advise the RBE items, and you would use Topic2to advise the non-RBE items.

Note: The unsolicited RBE messages are ONLY sent out from the slave port of a toplevel controller to the Network Host PC. If multiple types of communication ports areconfigured on the same unit, the Ethernet port is the slave port by default. Therefore,the topic associated with the Ethernet port of the top level controller or any topic of alower level RTU defined under this Ethernet network branch must be connected to theserver for collecting the unsolicited RBE reports from the particular RTU in the clientapplication.

Alarm Signals 5

Alarm SignalsThe server supports Alarm signals (see Bristol Babcock documentation). If the user hasconfigured some of the items (signals) in the controller as Alarm items and has enabledthe Alarm task, then the server will receive and process the unsolicited alarm messages.The process of defining an item (signal) as an Alarm in the controller is done by usingthe Bristol Babcock programming software and not the server.

The Alarm messages will be received by the server as unsolicited messages. In order forthis to be meaningful, the user of the server must generate a client application thatrequests data for these Alarm items (just as for any other item). This client applicationis usually an InTouch application. If an Alarm message is received by the server andthere is no client that has requested the data (put the item on advise), then the data isdiscarded.

If you are using a controller that has Alarm items defined, then you should set up yourInTouch (or other client) application to advise these items. The Alarm data will be sentto your application and will be logged to the Wonderware Logger as well.

If you do not want alarms messages logged to the logger, then add the following settingto you WIN.INI file:

[BSAP]LogBSAPAlarms=0

Note: The unsolicited Alarm messages are ONLY sent out from the slave port of a top-level controller to the Network Host PC. If multiple types of communication ports areconfigured on the same unit, the Ethernet port is the slave port by default. Therefore,the topic associated with the Ethernet port of the top-level controller or any topic of alower level RTU defined under this Ethernet network branch must be connected on theserver for collecting unsolicited Alarm messages from the particular RTU in theWonderware Logger.

EthernetThe server supports Ethernet and long (16 characters) RTU names. Once you haveconfigured the network of RTUs, you don’t need to know IP addresses or RTU localaddresses. You access the RTUs connected to Ethernet exactly like the RTUs connectedto the serial (COM) ports. All that is needed is the name of the RTU. Bristol Babcock’sNetView driver takes care of all the details.

Follow these four steps to get your server up and running:1. Use Bristol Babcock’s LocalView utility to configure the IP address inside the

RTU’s flash memory. See Bristol Babcock’s Open Bristol System InterfaceUtilities Manual, D5081, Chapter 5, Using LocalView.

2. Use Bristol Babcock’s NetView utility to configure the network topology. SeeChapter 6, Using NetView in Open Bristol System Interfact Utilities Manual,D5081.

3. Use Bristol Babcock’s ACCOL Workbench Tools to configure an IP network in theload file for each RTU that is connected to the Ethernet lines. See Chapter 8, page8-21 of Bristol Babcock’s ACCOL Workbench for Windows Manual, D4051.

4. Use Bristol Babcock’s DataView utility to test the network configuration. SeeChapter 8, Using DataView in Open Bristol System Interface Utilities Manual,D5081. If you get data using DataView, then you can start the server and useInTouch or some other client to get data from the Bristol Babcock network ofRTUs.


Configuring the I/O ServerOnce the server has been installed, some configuration is required. Configuring theserver automatically saves the data in a configuration file. If no configuration file isselected, the user is prompted to select a filename.

To

ac

To access the options used for the various configurations, open the Configure menu:

Note: Before configuring the server, a Network Definition file should exist. This file isprepared with the Bristol Babcock OpenBSI Utilities for your network of controllers andRTUs. Please refer to the appropriate Bristol Babcock’s manual for complete details onconfiguring your BSAP network.

To perform the required configurations, start up the server bydouble-clicking on its icon. If the server starts up as an icon,double-click on the icon to open the server's window.

Saving the I/O Server’s Configuration File 7

Saving the I/O Server’s Configuration FileIf a configuration file does not currently exist in the configuration file directory, theserver will automatically display the Save Configuration dialog box:

Save Configuration

This field displays the drive\directory into which the server will save the currentconfiguration file. To save the configuration file to a different directory, enter the pathfor that directory in this field.

This option is selected and disabled on initial entry to the Save Configuration dialogbox. This field becomes active if the Configuration File Directory is changed. Onceenabled, selecting this option will record a new Configuration File path in the WIN.INIfile. This option allows the server to find its configuration file automatically each time itis started.

Note: When the server initially starts up, it attempts to locate its default configurationfile by first checking the WIN.INI file for a previously specified path. If a path is notpresent in the WIN.INI file, the server will assume that the current working directory isto be used.

Click Defaults to reset the settings to their default values without saving changes.

Click OK to save the configuration file to the specified directory.

Saving Multiple Configuration FilesThere is no limit to the number of configuration files that you can create as long as theyare saved in separate directories. This allows you to have multiple configuration filesthat can be accessed by using a special switch (/d:). For example, to start the serverusing a configuration file located in a different directory, click the Start button on thetaskbar, then choose Run and enter the following in the Open combo box:

BSAP /d:c:\directoryname


Configuring a Topic DefinitionUse the Topic Definition option from the Configure menu to create new, modify, ordelete topic definitions. One or more topic definitions must exist for each PLC that theserver will communicate with. Each topic definition must contain a unique name for thePLC associated with it. When this option is selected, the Topic Definition dialog boxwill appear:

Topic DefinitionNote: Once topics have been defined, their names will be listed in the Topics section ofthis dialog box.

Click this button to close the dialog box and accept any new definitions, modificationsor deletions made.

To modify or view an existing topic definition, select its name in the list and click onthis button. The BSAP Topic Definition dialog box described below will appeardisplaying the selected topic definition.

To delete an existing topic definition, select its name in the list and click on this button.A message box will appear prompting you to confirm the deletion.

To add a new topic definition, click on this button. The BSAP Topic Definition dialogbox will appear:

Configuring a Topic Definition 9

BSAP Topic Definition

Enter a unique name (up to 32-characters long) for the PLC in this field, for example,AA14.

Note: When communicating with InTouch, this exact name is used as the topic name inthe Access Name definition.

Select a Controller Name from the drop down list box. This is the Node Name (up to16 characters long) that was assigned to this controller when the Network Definition filewas configured with Bristol Babcock’s NetView tool.

Enter the frequency in seconds with which the items (signals) in the Topic will bepolled. If all the items on this topic are RBE items, set the poll period to 0. This willcause the server to go out and poll all the RBE items (Bristol Babcock calls these items“signals”) for initial values. The item is updated only when an unsolicited RBE messagecontaining new data for this item is received from the RTU. Another option is to use avery long poll period. This method assures that the items on advise are updated at leastevery poll period.

Note: For more information on Slave Types, see the "Item Names" section later in thisuser's guide.

Click Cancel to close the dialog box without saving changes.

Click OK to accept the topic definition and return to the Topic Definition dialog box.

Click Done to close this dialog box.


Configuring the I/O Server SettingsUse the Server Settings option from the Configure menu to change the protocol timer,to enable the network using Wonderware NetDDE, to specify the default configurationfile path, or to enable the server to start automatically as a Windows NT service.

Note: When configuring the server on Windows NT, the user must be logged on withsystem administrator privileges. This will ensure that updates to the system registry maybe performed.

When the Server Settings option is selected, the Server Settings dialog box willappear:

Server Settings

Enter the frequency (in milliseconds) that the server is to check for data to process. Thisshould be approximately two to four times faster than the fastest rate desired to updatedata from the equipment.

Select this option if you are networking using Wonderware NetDDE.

To create a new default configuration file, enter the complete path for the directory inwhich the file is to be saved in this field. This new path will automatically be written tothe WIN.INI file and the server will use this path to load its configuration file the nexttime it is started.

Configuring the I/O Server Settings 11

To create a new default configuration file, enter the complete path for the directory inwhich the file is to be saved in this field. This new path will automatically be written tothe WIN.INI file and the server will use this path to load its configuration file the nexttime it is started.

Note: There is no limit to the number of configuration files created. However, eachmust be saved in a different directory. When using the server with InTouch, werecommend that you save the configuration file in your application directory. For moreinformation on the Configuration File, see "Saving the I/O Server’s Configuration File"in this user's guide.

Enabling this option will cause the server to start as a Windows NT service.

Windows NT offers the capability of running applications even when a user is notlogged on to the system. This is valuable when systems must operate in an unattendedmode. Enabling this option and rebooting the system will cause the server to run as aWindows NT service. However, to view configuration information or to reconfigure theserver, the user must log on to the system. Any server related problems that may arisesuch as missing adapter cards, licensing failures or device drivers not loading will not bevisible to the user until a log on is performed. Disabling this option and rebooting thesystem will cause the server to run as a Windows NT application program once again.

Note: For this server to run as a Windows NT service successful, Bristol BabcockOpenBSI driver must be started as a Windows NT service first. For information onsetting up Bristol Babcock OpenBSI driver as a Windows NT service, see Chapter 6,Using NetView in Open Bristol Systems Interface Utilities Manual, D5081 for details.

Click Cancel to close the dialog box without saving changes.

Click OK to accept the server settings. The following message box will appear:

Click OK to close the dialog box.

Note: You must restart the server for the changes to take effect.


Accessing I/O Server HelpThe Help menu contains three options that are used to access help for the server.

The following briefly describes the Help menu options.

ContentsThis option is used to display the table of contents for the Help file.

How to Use HelpThis option is used to access a list of basic instructions for using the Help file.

About BSAPThis option is used to access miscellaneous information regarding the server, such as thesoftware version, the copyright information, license information, etc.

Your FactorySuite system license information can be viewed through the licenseviewing utility that is launched from the About dialog box.

$ For more information on the license viewing utility, see your FactorySuite SystemAdministrator’s Guide.

Item Names 13

Item Names Valid item names conform to standard Bristol Babcock’s ACCOL II conventions withitems composed of a base, extension and attribute. Please refer to the Babcock BristolACCOL II Reference Manual for further details on valid item names. The following isan example of a valid Name: TANK5.TEMP.001 Array Elements can be accessed using the item name format #ADATx.y.z. for analogarrays or #LDATx.y.z. For logical arrays, where x is the array number (1-255), y is thecolumn and z is the row. The following is an example of a valid Array Element ItemName: #ADAT1.1.1

Bristol Babcock Inhibit Bits The Bristol Babcock family of controllers supports a concept of access controls whenmodifying data items. The controller maintains Inhibit bits for each data point. If thecontrol Inhibit bit for a point is set (TRUE), then control tasks, such as PID modules,running within the controller are prevented from modifying the point's value. If theManual Inhibit bit is set, external operator interfaces, including InTouch and otherClients are prevented from changing the point's value. Bristol Babcock’s controllersalso allow alarm monitoring for a point to be disabled by setting the point's AlarmInhibit bit. An '&' character followed by a single letter is used to access (read and writeaccess is supported) the Inhibit bits associated with a point. '&C' is used for ControlInhibit, '&M' for Manual Inhibit and '&X' for Alarm Inhibit. The following areexamples of valid item names for the Inhibits Bits:

TANK5.TEMP.001&C TANK5.TEMP.001&M TANK5.TEMP.001&X

Force Control Bit The Wonderware Bristol Babcock OpenBSI I/O Server provides a mechanism to "force"a point to return a fixed, operator specified value overriding the value actually held inthe controller and taking the point "off scan" by the server. The use of this mechanismis called "forcing" the point. The characters '&F' are appended to a point's name toaccess the point's Force Control Bit. If a point's Force Control Bit is set (TRUE), theWonderware Bristol Babcock OpenBSI I/O Server will cease to request updates to thepoint's value from the controller containing the point. If the Force Control is set and aClient attempts to write a new value to the point, the value will not be written to thecontroller, but the new value will be returned to all Clients which have the point onadvise. The Force Control Bit is maintained only in the server and setting it has noeffect in the controller that contains the associated data point. The following is anexample of a valid item name for the Force Control Bit: TANK5.TEMP.001&F


Specifying Discrete Data Type The Microsoft specifications require that the server immediately return the data type(Integer, Logical or Real) of a data item placed "on advise". This server is not aware ofthe native type of a data item until a controller in response to the data request returns itsvalue (along with a type indicator). This data return may take a considerable amount oftime and the application placing the point on advise is suspended until the data type isreturned.

In order to prevent suspensions of Client application programs, this server informs itsclient that all points are Real values by default. If the response from the controller laterindicates that the point is a Discrete, the value is converted to a Real before it is passedto the application. This treatment allows all data accesses to work but causes a slightamount of inefficiency when discrete (Bristol Babcock’s 'logical') data points arecommunicated to the Client application. The overhead associated with theseconversions is minimal and transparent to the application and should be ignored.

However, this server supports a mechanism to force a point to be returned as a discreteby appending the characters '&L' to the standard ACCOL point name, for example,TANK5.TEMP.001&L. If a point's type has been forced to Discrete and the point islater determined to be a Real, the value will be converted to a Discrete with 0.0 = Falsebefore it is passed to the Client application.

Server Specific Predefined Diagnostic and ControlItems The following predefined items are built into this server. All the integer items are 32-bit. Whenever the total number meets or exceeds 4,294,967,295 the value of the integeritem rolls over to 0:

?1 Returns the total number of signal read and signal write requests that havebeen directed to a Topic since the server started running. The value isupdated approximately every 10 seconds.

?2 Returns the total number of replies in response to signal read and signal writerequests that have been directed to a Topic since the server started running.The value is updated approximately every 10 seconds.

?3 Returns the total number of response timeouts while waiting for a response tosignal read and signal write requests that have been directed to a Topic sincethe server started running. The value is updated approximately every 10seconds.

?4 Returns the total number of alarm messages that have been received for aTopic since the server started running. An alarm message can pertain tomultiple signals. The value is updated approximately every 10 seconds.

?5 Returns the poll period in milliseconds for a Topic. The value may bealtered. If the value is set to 0, the controller will not be polled althoughalarm messages might still cause values of items for the Topic to be updated.Values less than zero should not be entered.

Item Names 15

?6 Returns the response timeout in milliseconds for the Topic. The value maybe altered. Values less than or equal to zero should not be entered.

?7 May be written with a value of 1 to cause the item defined for the Topic to bepolled, even if the nominal poll period has not yet expired.

?8 Returns the total number of RBE messages that have been received for aTopic since the Wonderware Bristol Babcock OpenBSI server startedrunning. An RBE message can pertain to multiple signals. The value isupdated approximately every 10 seconds. It can be polled more frequently.This value can be altered. Values less than zero should not be entered.

?16 Returns the total number of RBE messages that have been received from allTopics since the Wonderware Bristol Babcock OpenBSI I/O Server startedrunning. An RBE message can pertain to multiple signals. The value isupdated approximately every 10 seconds. It can be polled more frequently.This value can be altered. Values less than zero should not be entered.

?17 Returns the total number of responses that have been ignored for all Topicson the same COM port. Ignored responses can be caused when an item ispolled but taken off advise before the value is returned. Not implemented forthis server version 5.6 or later.

?18 Returns the total number of CRC errors on responses from all Topics on thesame COM port. Ignored responses can be caused when an item is polledbut taken off advise before the value is returned. Not implemented for thisserver version 5.6 or later.

?19 Returns the total number of NAKs that have been received on the COM port.Not implemented for this server version 5.6 or later.

?20 Returns the total number of timeouts awaiting a response that have occurredfor the COM port. Not implemented for this server version 5.6 or later.

?21 Returns the number of consecutive NAKs that have been received on theCOM port. If a response is received other than a NAK, this item is zeroed.Not implemented for this server version 5.6 or later.

?22 Returns the number of consecutive timeouts awaiting a response that haveoccurred for the COM port. If a response is received without a timeout, thisitem is zeroed. Not implemented for this server version 5.6 or later.

?23 Returns the total number of responses received by the COM port. Notimplemented for this server version 5.6 or later.

?24 Returns the total number of sends (reads, writes and polls, including retries)by the COM port. Not implemented for this server version 5.6 or later.

?25 Returns the total number of polls sent out the COM port. Not implementedfor this server version 5.6 or later.

?26 Returns the total number of overruns suffered by the Windows COM portdriver. Not implemented for this server version 5.6 or later.

?27 Returns the total number of times the Windows COM port driver "fellasleep" during transmit and had to be restarted. Not implemented for thisserver version 5.6 or later.


?28 Returns the total number times the PC's UART detected an error on the COMport. Not implemented for this server version 5.6 or later.

?29 Is incremented by one every time an Alarm is directed to the WonderwareLogger. This value reset by writing a value of zero to it.

?30 May be written with a value of 1 to prevent Momentary Alarms from beinglogged to the Wonderware Logger.

?31 Returns the response timeout in milliseconds for the COM port. This valuecan be altered. Values less than or equal to zero should not be entered.

Monitoring the Status of Communications with a PLC 17

Monitoring the Status of Communications with a PLC For each topic name (PLC), there is a built-in discrete item that can be used to monitorthe status of communications with the PLC. The discrete item, Status, is set to 0 whencommunication with the PLC fails and is set to 1 when communication is successful.

Using the Status Item in Excel The status of the PLC communications can be read into Excel by entering the followingreference formula in a cell on a spreadsheet:

= BSAP|TempControl!Status

where:BSAP Is the name (without extension) of the server application.

TempControl Is the exact topic name defined in the server for the PLC.

Status Built-in discrete item used to monitor the status ofcommunications with the PLC.

Monitoring the Status of Communications with InTouch InTouch supports built-in topic names called DDEStatus and IOStatus that are used tomonitor the status of communications between the server and InTouch. For moreinformation on the built-in topic names DDEStatus and IOStatus, see your online”InTouch User’s Guide”.

Using DDEStatus and IOStatus in Excel The status of communication between the server and InTouch can be read into Excel byentering the following reference formula in a cell on a spreadsheet:

=view|DDEStatus!TempControl

or

=view|IOStatus!TempControl

where:

view Is the name of the InTouch application.

[DDE][IO]Status Built-in topic name used to monitor the status of communications between the server and InTouch.

TempControl The exact topic name defined in the server for the PLC.


Reading Values from the I/O Server into Excel Values may be read directly into Excel spreadsheets from the server by entering aformula into a cell using the following format:

=applicationname|topicname!itemname

Example formula:

=BSAP|TempControl!?1

where:

BSAP Is the name of the server application name.

TempControl Is the exact topic name defined in the server for the PLC.

?1 Is the actual location in the PLC that contains the data value. This is the item name.

In this example, each time the value of ?1 changes in the PLC, the server willautomatically send the new value to the cell containing the formula in Excel.

Note: Refer to the Microsoft Excel manual for complete details on entering RemoteReference formulas for cells.

Writing Values to the I/O Server from Excel 19

Writing Values to the I/O Server from Excel Values may be written to the server from Microsoft Excel by creating an Excel macrothat uses the POKE command. The proper command is entered in Excel as follows:

channel=INITIATE("applicationname","topicname")

=POKE(channel,"itemname", Data_Reference)

=TERMINATE (channel)

=RETURN()

The following describes each of the above POKE macro statements:

channel=INITIATE("applicationname","topicname")

Opens a channel to a specific topic name (defined in the server) in a particularapplication name (the executable name less the .EXE) and assigns the number of thatopened channel to channel.

Note: By using the channel=INITIATE statement the word channel must be used inthe =POKE statement instead of the actual cell reference. The "application name" and"topic name" portions of the formula must be enclosed in quotation marks.

=POKE(channel,"itemname", Data_Reference)

POKEs the value contained in the Data_Reference to the specified item name (actuallocation in the PLC) via the channel number returned by the previously executedINITIATE function. Data_Reference is the row/column ID of the cell containing thedata value.

=TERMINATE(channel)

Closes the channel at the end of the macro. Some applications have a limited number ofchannels therefore, they should be closed when finished. Channel is the channelnumber returned by the previously executed INITIATE function.

=RETURN()

Marks the end of the macro.

Note: Refer to the .XLM sample Excel poke macro provided on the server programdisk. Also refer to the Microsoft Excel manual for complete details on entering RemoteReference formulas for cells.


Troubleshooting I/O Server Communication Problems This section provides you with some simple steps that can be taken to ascertain andcorrect communication problems. The problems described here represent the mostprobable causes of communication failure.

Note: This is a general troubleshooting guide and for the sake of brevity we cannotcover every possible source of communication problems.

Debugging Communication Between InTouch andan I/O Server This section explains the most common error situations that can occur when attemptingto establish communication between InTouch and a server.

Servers are Window applications that communicate with I/O, PLCs, and/or other datasources. If a server supports either the Microsoft Dynamic Data Exchange (DDE) or theWonderware SuiteLink protocol, it is capable of communicating with the WonderwareInTouch program.

Note: All Wonderware version 7.0 or later servers support both DDE and SuiteLink.However, the SuiteLink protocol is only supported on the Windows NT (version 4.0 orlater) operating system.

Servers respond to data requests made by other applications. Requesting applicationsare called clients. When WindowViewer acts as a client and requires the value of anitem, it contacts the server and requests the item’s value. The server will report thevalue and update WindowViewer only if a change occurs. All WindowViewer datarequests provide information relating an item to a register, coil number, or I/O data pointunderstood by the server. The server uses the information to automatically handle allmessages to and from I/O, hardware devices (PLC), and/or other data sources.

Note: We highly recommend starting all the servers required by the InTouch applicationbefore starting WindowViewer. InTouch (versions prior to 7.0) will display theInitiating DDE Conversation message box for each uninitiated conversation.

For example:

If you start up WindowViewer and cannot successfully establish a conversation witha server, the following Initiating DDE Conversation dialog box will appear:

Troubleshooting I/O Server Communication Problems 21

The information in the second line indicates that you have at least one I/O typetagname defined in your Tagname Dictionary that is associated with an AccessName that defines OMRONFO as the Application Name, and HLPLC as the TopicName. Make note of exactly how the application and topic names are spelled.

8 This example only applies when using a version of InTouch prior to InTouch7.0.

To troubleshoot communication problems between WindowViewer and the server,perform the following steps as listed below.

Ø Verify the I/O Server is running.

1. Start the server program.

2. Verify the server is running by checking to see if it is in the Windows Task List.

On Windows NT, click the right mouse button on the Windows taskbar and selectTask Manager from the menu. Click the Applications tab to view all currentlyrunning applications. Or press the CTRL+SHIFT+ESC keys.

On Windows 95, press the ALT+TAB keys while holding down the ALT key.

On Windows 3.1 or Windows for Workgroups, press the CTRL+ESC keys.

Ø If the I/O Server is running, verify the I/O Server's program name is correct in allWindowMaker Access Name definitions.

1. Switch to (or start) WindowMaker. Select Access Names from the Special Menu,the Access Name Definitions dialog box appears listing all Access Names definedin the WindowMaker.

2. In the Access Names list, select the Access Name referencing the server and clickModify. The Modify Access Name dialog box will appear.

3. Verify the server's program name in the Application Name box is correct. If it iswrong then correct it and click OK , else click Cancel.

8 The server's exact "executable name" must be typed in the Application Namebox in all Access Name definitions. The ".exe" extension is not used.

8 If you are debugging a remote tagname reference, also verify that the nodename for the remote computer in the Node Name box is correct.

4. Repeat steps 2 & 3 and verify the server program name is correct in all AccessNames that use it.

Ø If you still cannot establish a conversation, verify the exact topic name used in theWindowMaker Access Name definitions are defined in the I/O Server program.

1. Close WindowViewer if it is running. The server cannot be configured ifWindowViewer is running.

2. Start the server program.

3. From the server’s Configure menu select Topic Definition. The Topic Definitiondialog box appears listing all topic names defined in the server.

4. Verify that the topic name exists and is spelled exactly the same (including spaces)as the topic name referenced in the WindowMaker Access Name definition.


8 Blank spaces cannot follow the topic name in either the server's TopicDefinition or the Access Name definition.

5. If the topic name is different, either correct it in the server or switch toWindowMaker and correct it in the Access Name definition.

6. Once you performed the above procedure, restart WindowViewer and switch to theserver program. Data should now appear in the server’s program window toindicate that WindowViewer and the server are communicating.

8 The data in the server’s program window indicates the read and write messagesthe server is sending to and receiving from the PLC. These are not errormessages; only status messages are written to the server’s program window.

7. If no data appears in the server’s program window, switch to the WonderwareLogger to check for error messages. For example, a common error message is:

"Error for DDE: OMRONFO|HLPLC!<null>("item") Advise failed"

This message appears when the item defined in one or more tagnames is invalid forthe server.

8 InTouch tagnames use specific naming conventions when accessing data from aserver. The valid item names for all Wonderware servers are documented intheir respective user's guides. Typically, the item naming conventions used byeach server are consistent with the names used by the equipment manufacturer.

$ For more information on the Wonderware Logger, see your onlineFactorySuite System Administrator's Guide.

If you are still experiencing problems, continue with the following troubleshootingsection.

Debugging Communication Between SuiteLinkand an I/O Server If you have successfully applied the debug techniques listed in the previous section andare still experiencing communication problems to a server that is attempting tocommunicate using the SuiteLink protocol, perform the following steps as listed below:

Ø Verify the I/O Server supports the Wonderware SuiteLink protocol, that is, the I/OServer is version 7.0 or above.

Ø Try communicating to the I/O Server using the DDE protocol. If this is notpossible, then proceed to the next troubleshooting section otherwise continue withthe following steps:

1. Verify Microsoft's TCP/IP stack is installed and configured properly.

8 SuiteLink uses the Microsoft TCP/IP stack for its communications even if theclient application and the server reside on the same node.

2. If you do not have an Ethernet card to bind to the TCP/IP stack, install theMicrosoft Loop Back Adapter.

3. Install the Microsoft TCP/IP stack.


Debugging Communication Between an I/O Serverand a PLCThis section provides you with simple steps to diagnose and correct server to PLCcommunication problems. The debug techniques listed below address both serial andboard servers. Disregard any information that is not applicable to the server type thatyou are using.

When attempting to establish communication between a server and a PLC, if no dataappears in the server's program window and the data items are not updating inWindowViewer, switch to the Wonderware Logger and check for error messages.

$ For more information on the Wonderware Logger, see your online “FactorySuiteSystem Administrator's Guide.”

For example, some of the most common errors that may appear in the WonderwareLogger for serial servers are:

Response TimeoutWCRET = -2WakeUp = -2Receive OverrunFraming Errors

Note: Unless specified otherwise, most serial communication based servers are fullduplex. If you require a server for half duplex (one that monitors the CTS and RTSlines) or if you are not sure whether the PLC's protocol is full or half duplex, call yourPLC supplier.

Also, during in-house server testing, we have found that the communication cards thatuse the National 16450 and 16550 UARTs seem to be less susceptible to level andtiming problems. Cards based on other chips may work, but we recommend using theNational cards. Some of the highly integrated UART chips (most notably, Winbond andUMC) have a tendency for their transmitters to hang, requiring re-initialization of theUART. If this occurs, you may have to restart the server or execute the Reinitialize I/Ocommand from the Special menu in WindowViewer.

Ø Check your cabling to the PLC.

Is it wired correctly? Check for shorts, loose wires, broken wires, crossed wires, and soon.

8 A continuity tester can be helpful here.

Ø Verify the I/O Server’s serial configuration settings (Parity, Stop Bits, Baud Rate,Handshaking and so on) against the settings in the hardware device.

Ø Verify the communication port is working properly in Windows.

1. Close the server program.

8 If you are using a server that requires a TSR, you will not be able to verify thatthe port is functioning properly while the TSR is running. Stop all TSRs thencontinue with this procedure. If you confirm that the port functions properlywithout the TSR running, change your software interrupt (IRQ) to anothernumber, for example, change 60 to 62.


8 Also, if you are using an AT type computer, two devices cannot shareinterrupts. Verify that the communication port you are using has a uniqueinterrupt setting.

2. On Windows 3.1 or Windows for Workgroups, start the Terminal program. OnWindows 95 or Windows NT, start the HyperTerminal program.

3. Configure the Terminal (or HyperTerminal) program to use the samecommunication port with the same settings (baud rate, parity, stop bits and so on) asthe hardware device.

4. Connect a null modem cable to a second computer's port.

5. On the second computer, start and configure the Terminal (or HyperTerminal)program with the same settings as the first computer.

6. Verify that you can send data between the two computers.

8 If you do not have two computers and the computer you are using has anotherport, start two instances of the Terminal (or HyperTerminal) program with eachconfigured to their own port. Then try communicating between them.

8 If you have an external modem, connect the modem to the communication portthat you are testing to see if you can dial out.

7. If the communication port does not appear to be functioning properly, check yourenvironment files (AUTOEXE.BAT, CONFIG.SYS, SYSTEM.INI, andWIN.INI). Look for suspicious programs or drivers that might be taking control ofthe port or its interrupt before the server is loaded. Always keep your environmentfiles as clean as possible. If you are in doubt about an entry, comment it out.

8. If the previous step was unsuccessful, try another communication port or anothercomputer.

Note: A common misconception of connecting to a PLC with a DOS program and thesame communication port will work in Windows is not the case! Windows is an entirelydifferent environment than DOS.

Ø What type of UART is on the COM port?

If it’s not a 16550, then you must lower your baud rate to 9600 or slower. Only the16550 UART can sustain continuous, error free communications at speeds higher than9600 baud. Other UARTs may work at speeds faster than 9600 baud, but errors may bewritten to the Wonderware Logger. For example, "Receive Overruns." To determinewhich UART you have, enter MSD at a DOS prompt, then choose COM Ports from theMSD menu.

Ø If you are running Windows for Workgroups, verify the following:

1. Add these lines to the [386Enh] section of your SYSTEM.INI file which is locatedin your \Windows directory:

EMMEXCLUDE=A000-EFFFCOMxFIFO=0

where x specifies the COM port number. You need to add a separate COMxFIFOline for each serial port using a 16550 UART chip.


2. If you are running Windows for Workgroups (version 3.1 or later), downloadSERIAL.386 (this fixes a Microsoft bug) from the Wonderware Bulletin Boardsystem (949-727-0726) or from the Wonderware WEB site at:http://wondertech.wonderware.com.

8 The size of this file is 10620 bytes, has a date of 2/17/94, and is a self-extracting zip file called wg1001.exe. It’s located in the "PatchFix Library" onthe Wonderware BBS in the File Transfers / Patchfix area.

8 You must be registered to access the Wonderware Web site.

3. If the above numbers, 1. and 2., do not work, verify the value of the ComBoostTimeparameter in your SYSTEM.INI file. This parameter represents the number ofmilliseconds a virtual machine processes a COM interrupt. (The default value is 2.)It is not recommended that you change this setting. However, if you are receivingerrors such as "Receive Overruns" or "WCRE=-2", try increasing the value to 20.

Ø Verify the parameters for WWCOMTSR.

Do not specify a receive and/or transmit buffer size of 8!

For example:

Correct:COM1:0 COM2:1,2048,2048COM1:0 COM2:1

Incorrect:COM1:0 COM2:1,8,8

Ø Does your computer crash when trying to communicate through the COM port?

If so, verify that each TSR has a unique software interrupt.

8 A utility, ShowSoft, is available on the Knowledge Base CD that can assist indetermining the available software interrupts.

Ø Does your computer lock up?

Verify the COM port's IRQ’s do not conflict with each other or with othercommunication boards in the computer.

Ø If the PLC or field device has more than one COM port, verify the connection tothe correct port.

The COM port on your computer uses the RS-232 hardware communication standardand connects the cable from the COM port to an RS-232 compliant device.

Note: To connect to an RS-422 or RS-485 port on the PLC, you need an RS-232 to RS-422/485 conversion device.

If possible, use an external converter instead of a board-based converter that plugs into aslot in the computer. A board-based converter is difficult to get working forinexperienced users. If a board-based converter is not set up properly, it can conflictwith other communication boards in the computer such as, internal modems.


Ø If you are using the Windows 95 operating system, verify the following:

1. Click Start on the Windows taskbar. Point to Settings, then click Control Panel inthe menu. The Control Panel dialog box will appear.

2. Double-click the System icon. The System Properties dialog box will appear.Click the Device Manager tab and select the COM port that you are using for theserver. For example:

3. Click Properties. The Properties dialog box will appear. Click the Port Settingstab.


4. Click Advanced. The Advanced Port Settings dialog box appears:

5. Lowering the default Receive Buffer and Transmit Buffer settings to their minimummay solve I/O communication problems for portable computers (notebook orlaptops) and framing errors for standard computers.

6. If using a 16550 UART chip, select the Use FIFO buffers (requires 16550compatible UART) option. If you are not using a UART chip, make sure thisoption is not selected.

Ø If you are using the Windows NT operating system, verify the following:

1. Click Start on the Windows taskbar. Point to Settings, then click Control Panel inthe menu. The Control Panel dialog box will appear.

2. Double-click the Ports icon, the Ports dialog box will appear.

3. Select a port and click the Settings button. The Settings for COMx dialog boxappears:

4. Click Advanced. The Advanced Settings for COMx dialog box appears:

5. Lowering the setting for the Interrupt Request Line (IRQ) value to the minimummay solve I/O communication problems for portable computers (notebook orlaptops) and framing errors for standard computers.

6. If you are using a 16550 UART chip, select the FIFO Enabled option. If you arenot using a UART chip, make sure this option is not selected.


Ø How long is your RS-232 cable?

Fifteen meters (fifty feet) is the maximum practical length for the RS-232 standard.

Ø Try using a different COM port for the I/O Server.

Ø If you are installing an I/O Server or configuring a board-based I/O Server on acomputer running on the Windows NT operating system, log on withAdministrator privileges.

8 Without Administrator privileges, the server and Server Install program cannotmake the necessary edits to the Windows NT Registry during installation or boardconfiguration of the server.

1. Click Start on the Windows taskbar. Point to Programs, then to AdministrativeTools (Common), and click User Manager in the menu. The User Manager dialogbox will appear:

2. Double-click the Username you typed in during log on.

3. If the User Properties dialog box does not appear, you do not have Administratorprivileges.

4. If the User Properties dialog box does appear, click on the Groups button and verify“Administrators” is in the “Member of” list.

Ø If you experience occasional or random communication errors in the WonderwareLogger, such as "Response Timeouts," check for noise.

Do the physical cables run past any known noise sources such as photocopiers,fluorescent lamps, fans, pumps, motors or generators? Are the cables properly shieldedfrom its environment? With radio modems and satellite link ups, occasionalcommunications errors in the Wonderware Logger are normal and to be expected aslong as they do not adversely impact the flow of data.


Ø Increase the Reply Timeout setting in the I/O Server to a value between 5 and 10seconds.

Not allowing the PLC or field device enough time to respond to the server’s request fordata may result in communication errors.

Ø Verify the PLC is properly configured and the cable is good by using theprogramming software for the PLC.

1. Connect to the PLC with the programming software. The connection must bethrough the same port and cable. Go into the programming software configurationand write down what the communications parameters are (baud rates, routes, nodenumber, error checking, etc.).

2. Close the programming software. Open the I/O Server and verify thecommunications settings are the same.

3. Poke data into the PLC with InTouch or WWClient.

4. Shut down the server and use the programming software to verify that the valueswere correctly poked.

8 Performance of this test depends upon the type of PLC you are using.

Ø Reinstall the I/O Server and verify that you are using the latest version.

Wonderware is continually improving our servers and using the latest version willguarantee the best results.

8 New versions of the Wonderware I/O Servers are released regularly on theKnowledge Base CD. These are available to Comprehensive Support customers onthe Wonderware Bulletin Board System (949-727-0726) or from the WonderwareWEB site at: http://wondertech.wonderware.com.

Ø Move the I/O Server’s configuration file to another location on the computer’shard drive. This will clear all configuration for the I/O Server, then reconfigurethe I/O Server.

8 Wonderware server configuration files are typically the exact same name as theserver’s executable name with the .CFG extension. For example,OMRONFO.CFG. Refer to the Configuration File section of the specific serveruser’s guide for the exact name of the configuration file.

Ø If possible, reinstall the Windows operating system.

Files installed earlier on your computer or the NT registry may have been corrupted oraccidentally modified.

Ø If these troubleshooting suggestions do not solve your problem, there may be aproblem with your computer. There are many subtle differences between thevarious computer hardware brands. Using a computer that is a different brandand meets the following criteria:

1. Select a different PC manufacturer and if this is not possible, try a different PCmodel from the same manufacturer.


2. The computer can not use an OEM (Original Equipment Manufacturer) version ofMicrosoft Windows. We highly recommend using only a Microsoft Windowsproduct. Contact your vendor to determine if installing an off-the-shelf copy ofMicrosoft Windows will cause any problems.

Ø If you feel you have tested all possible situations that may be causing your failedI/O communications, contact your local Wonderware distributor for technicalsupport.

$ For more information on obtaining technical support, see your online FactorySuiteSystem Administrator’s Guide.

Documents

Wonderware Bristol Babcock OpenBSI I/O Server User's Guide