Table of Contents

Advertisement

N e t w o r k 3 0 0 0
C o m m u n i c a t i o n s
C o n f i g u r a t i o n G u i d e
( A u s e r ' s g u i d e t o s o f t w a r e c o n f i g u r a t i o n
a n d t r o u b l e s h o o t i n g f o r t h e N e t w o r k 3 0 0 0
C o m m u n i c a t i o n s s y s t e m . )
Bristol Babcock
D5080 Issue:
April, 2001

Advertisement

Table of Contents
loading

Summary of Contents for Bristol Babcock Network 3000

  • Page 1 N e t w o r k 3 0 0 0 C o m m u n i c a t i o n s s y s t e m . ) Bristol Babcock D5080 Issue:...
  • Page 2 Billing for extra copies will be according to current pricing schedules. ACCOL is a trademark and Bristol is a registered trademark of Bristol Babcock. Other trademarks or copyrighted products mentioned in this document are for information only, and belong to their respective companies, or trademark holders.
  • Page 3 Workstation® products, call (860) 945-2286. For technical questions regarding TeleFlow products call (860) 945-8604. For technical questions regarding Network 3000 hardware products call (860) 945-2502. For technical questions about ControlWave call (860) 945-2244 or (860) 945-2286. You can e-mail the Application Support Group at: bsupport@bristolbabcock.com The Application Support Group maintains an area on our web site for software updates and other technical information.
  • Page 4 Please call the main Bristol Babcock number (860-945-2200) if you are unsure which office covers your particular area. Visit our Site on the World Wide Web For general information about Bristol Babcock and its products, please visit our site on the World Wide Web at: www.bristolbabcock.com Training Courses Bristol Babcock’s Training Department offers a wide variety of courses in Bristol hardware...
  • Page 5 This document assumes familiarity with the following subjects: • Users must have some level of knowledge regarding how their Network 3000 hardware is to be used. In particular, they should be familiar with the data update requirements for their particular process.
  • Page 6 BLAN...
  • Page 7: Table Of Contents

    Table of Contents Chapter 1 - Introduction .................... 1-1 BSAP Networks ..................1-1 IP Networks ....................1-4 Converting NETTOP Files For Use Below An NHP......... 1-8 Overview of Configuration ................. 1-9 Is this still unclear? ................ 1-10 Chapter 2 - Guidelines For Setting Up BSAP Networks.......... 2-1 A Quick Review of BSAP Network Terminology ........
  • Page 8 OpenEnterprise..................6-12 Enterprise Server ..................6-13 Intellution® FIX® ..................6-13 Iconics Genesis ..................6-14 Chapter 7 - Trouble-Shooting Network 3000 Communications ....... 7-1 Trouble-Shooting Techniques ..............7-2 Frequently Asked Questions Concerning Communication Problems..7-22 Checklist for Diagnosing Communication Problems ......7-30 Appendix A - Summary of Port Types ...............A-1...
  • Page 9: Chapter 1 - Introduction

    Currently the 386EX Protected Mode DPC 3330/DPC 3335 controllers with Ethernet hardware installed are the only Network 3000-series controllers which support the IP protocol. Bristol Babcock’s ControlWave controller also supports IP, however, ControlWave communications are not covered in this book.
  • Page 10 NetView must be used. If you want to use a mixture of older DOS-based ACCOL Tools with Open BSI 3.1 (or newer) you will need to use NetView, and then use the NETBCX utility to generate network files compatible with the DOS-based tools. Page 1-2 Network 3000 Communications Configuration Guide...
  • Page 11 RBE signals, and expanded memory is Collection signals which have a required. Compatible RBE Manager software must be value change exceeding a available for the particular Network Master specified deadband. HMI/SCADA software. Network 3000 Communications Configuration Guide Page 1-3...
  • Page 12: Ip Networks

    This manual will discuss certain aspects of IP as part of communications configuration for your Bristol Babcock controller. The details of how IP works are beyond the scope of this manual, however. One book on the subject we recommend is Internetworking with TCP/IP, Volume I: Principles, Protocols, and Architecture by Douglas E.
  • Page 13 (Other types of LANs may be supported in the future, however, Ethernet is currently the only choice available.) A Bristol Babcock network using only IP nodes does NOT follow a hierarchical structure. For certain applications, this is a significant advantage over BSAP, because all nodes in a given section of the network are essentially on the same level.
  • Page 14 The NHP performs the exact same function as the directory assistance operator; except instead of giving out phone numbers, it provides IP address information, on request, for connections to any node in its section of the network. Page 1-6 Network 3000 Communications Configuration Guide...
  • Page 15 Sending signal and/or Users must configure IP_Client and IP_Server Communication array data from one Modules in their ACCOL loads. controller, to another controller, so the other controller can perform some processing on it. Network 3000 Communications Configuration Guide Page 1-7...
  • Page 16: Converting Nettop Files For Use Below An Nhp

    Only the single BSAP node underneath the IP node would have to be manually defined in NetView; the other BSAP node definitions (under the NHP) would be extracted from the existing NETTOP file, and added to a new NETDEF file, using the NETCONV utility. Page 1-8 Network 3000 Communications Configuration Guide...
  • Page 17: Overview Of Configuration

    To obtain this performance goal, however, the user must have an understanding of how Network 3000 communications work. We can think of the Network 3000 architecture as being made up of three major parts. These parts are the data link, the network routing information, and the applications which use the data link.
  • Page 18: Is This Still Unclear

    (data request) was undeliverable. If this analogy didn’t clarify the distinction between the data link, application, and network routing information, don’t worry. We’ll talk more about these subjects in the next several chapters. Page 1-10 Network 3000 Communications Configuration Guide...
  • Page 19: Chapter 2 - Guidelines For Setting Up Bsap Networks

    What is BSAP? BSAP stands for Bristol Synchronous / Asynchronous Protocol. All ACCOL-based Network 3000-series controllers can communicate using BSAP. Each node (RTU) in a BSAP network is assigned a 7-bit local address (from 1 to 127) and a 15-bit global address, based on its location in the network. The local...
  • Page 20 If this BSAP network is a sub-network of an IP node, the Network Master would be the Network Host PC (NHP), and the IP node would be the only level 1 node. A node’s configured local address may be viewed on-line through the #NODEADR.. system signal. Page 2-2 Network 3000 Communications Configuration Guide...
  • Page 21: Things To Be Aware Of When Defining Your Network

    Defining Network Size in NETTOP off. Polling will be discussed in a later chapter. Note that program size in the master node of non- existent slaves will be affected because extra #NODE.nnn signals will be created. Network 3000 Communications Configuration Guide Page 2-3...
  • Page 22 HMI/SCADA packages, nor earlier versions of ACCOL and Open BSI tools support the longer node names, therefore, if your system includes a mixture of older and newer software, you should not exceed the 4 character limit. Page 2-4 Network 3000 Communications Configuration Guide...
  • Page 23 #13, #25 and #36, don’t set the addresses of your three nodes to 13, 25, 36. Local addresses should be sequential, and should always start with address 1. Assigning these values randomly, with gaps in Network 3000 Communications Configuration Guide Page 2-5...
  • Page 24 HMI/SCADA packages from functioning correctly. If your system includes redundant controllers, each redundant pair is considered to be a single node, since only 1 of the 2 can be the on-line unit at any one time. Page 2-6 Network 3000 Communications Configuration Guide...
  • Page 25 NETTOP. Pseudo Masters must, however, have current identical copies of the NETTOP files in order to perform global communication. • When you release a new network file using NETTOP, you actually generate three files, named . These NETFILE RTUXREF.DAT, GLADXREF.DAT Network 3000 Communications Configuration Guide Page 2-7...
  • Page 26 ‘SET ACCOL=\directory_spec\’ where directory_spec is the DOS directory containing the network files. This command can be entered directly at the DOS prompt, or may be included in the AUTOEXEC.BAT file of your PC. Page 2-8 Network 3000 Communications Configuration Guide...
  • Page 27 Network Host PC (NHP). (Otherwise, you would have to re-enter all of the NETTOP information within NetView.) Instructions for using NetView, NETCONV, and the NetDef to Database utility are included in the Open BSI Utilities Manual (document# D5081). Network 3000 Communications Configuration Guide Page 2-9...
  • Page 28 IP node, you take care not to define a large number, since that would reduce number bits available represent addresses for the BSAP nodes on level 2 through 6. Setting the Local Address For the IP node on Level 1 Page 2-10 Network 3000 Communications Configuration Guide...
  • Page 29: Chapter 3 - Guidelines For Setting Up Ip Networks

    This section will discuss certain aspects of IP as part of communications configuration for your Bristol Babcock controller (RTU). The details of how IP works are beyond the scope of this manual, however. One book on the subject we recommend is Internetworking with TCP/IP, Volume I: Principles, Protocols, and Architecture by Douglas E.
  • Page 30: What Is A Network Host Pc (Nhp)

    What is A Network Host PC (NHP)? A Network Host PC is any Open BSI 3.0 (or newer) workstation. Typically, this workstation has some Network 3000-series remote process controllers (RTUs) connected to it (it serves as the ’host’ for those RTUs). Those RTUs must be defined in a Network Definition (NETDEF) File at this NHP.
  • Page 31 In addition, following our same analogy, the directory assistance operator can generally do one of two things when you call for information. If you are unable to call someone, one thing the directory assistance operator can do is establish a Network 3000 Communications Configuration Guide Page 3-3...
  • Page 32 Open BSI Workstation needs to communicate with an RTU associated with another NHP, the other NHP can relay messages between its RTU and the inquiring workstation. This is called proxy access, and is depicted in the figure, below: Page 3-4 Network 3000 Communications Configuration Guide...
  • Page 33 Also, because you can have multiple NHPs, each of which is responsible for a portion of your network, your supervisory control is truly distributed among multiple sites. Through proxy access, any Open BSI 3.0 (or newer) workstation can Network 3000 Communications Configuration Guide Page 3-5...
  • Page 34: What Is The Format Of Ip Addresses

    For example, if this network has connections outside the plant (i.e. a connection to the real world- wide Internet), then the choice of this network number is assigned by an Internet governing body called the Network Information Center (NIC) or whatever Internet service provider you are using. Page 3-6 Network 3000 Communications Configuration Guide...
  • Page 35 ’01111000’ (120 in decimal) is the network portion of the address. The remaining parts of the IP address ’00000000.11010010.00000001’ have a corresponding sub-net mask of ’00000000.00000000.00000000’. These bits are used as part of the local communications addressing scheme. Network 3000 Communications Configuration Guide Page 3-7...
  • Page 36 Another 8 bits (remaining out of the 16 available) can be used to indicate a node number, allowing up to 256 IP controllers (RTUs) and Open BSI workstations, in a given section. Page 3-8 Network 3000 Communications Configuration Guide...
  • Page 37 The network shown has one Network Host PC (NHP) called NHP1, and 3 controllers (RTUs) named OAK_STREET, ELM_STREET, AND WALNUT_AVE. The table, on the next page, however, reveals a problem with the configured sub- net masks. Network 3000 Communications Configuration Guide Page 3-9...
  • Page 38 0 to 255. Based on their specified IP addresses and sub-net masks, OAK_STREET, ELM_STREET, and WALNUT_AVE can all communicate with each other. They can also send messages to NHP1. Page 3-10 Network 3000 Communications Configuration Guide...
  • Page 39: Things To Be Aware Of When Defining Your Network

    Internet. RFC 1918 - Rekhter, et al, Best Current Practice memo - Address Allocation for Private Internets, Internet Engineering Task Force, February, 1996. Please see http://www.ietf.org for complete text of this memo. Network 3000 Communications Configuration Guide Page 3-11...
  • Page 40 WARNING We are discussing the Internet Protocol (IP) for use in communication between Bristol Babcock controllers. The normal, intended application is for a ’closed circuit’ internet (LAN) of controllers and workstations in a company plant or industrial site. While, there is no built-in restriction against connecting an IP...
  • Page 41 Chapter 3 - Guidelines For Setting Up IP Networks The IP address of the Network Host PC (NHP) is initially defined in the System Wizard of NetView. Network 3000 Communications Configuration Guide Page 3-13...
  • Page 42 Chapter 3 - Guidelines For Setting Up IP Networks • Alarm and RBE (Report By Exception) data is sent to destination IP addresses defined in the Network Wizard of NetView. Page 3-14 Network 3000 Communications Configuration Guide...
  • Page 43 Chapter 3 - Guidelines For Setting Up IP Networks • The range of valid IP addresses, and the sub-net mask for the communication line are defined in the Comm Line Wizard of NetView. Network 3000 Communications Configuration Guide Page 3-15...
  • Page 44 Chapter 3 - Guidelines For Setting Up IP Networks • The IP address for an RTU’s IP port is defined in the RTU Wizard of NetView. Page 3-16 Network 3000 Communications Configuration Guide...
  • Page 45 (or downloaded with a new ACCOL load) for the new parameters to be activated. NOTE: For more information on IP address configuration, see ’Chapter 5 - Guidelines For Configuring the IP Data Link’. Network 3000 Communications Configuration Guide Page 3-17...
  • Page 46 BLANK PAGE...
  • Page 47: Chapter 4 - Guidelines For Configuring The Bsap Data Link

    If the slave node does not receive a poll message from its master within this period of time, it discards data messages for the master (except for alarms, which are saved in buffers), because the master is assumed to be ‘dead’. Network 3000 Communications Configuration Guide Page 4-1...
  • Page 48 A controller’s Master Port(s) are configured within the ACCOL source file. If you are using one or more Expanded Addressing Master Ports, the same instructions generally apply. Specific differences will be noted in footnotes. Page 4-2 Network 3000 Communications Configuration Guide...
  • Page 49 If Ports B, C, and G of this controller are to be configured Master Ports (see figure, above, and at right) then the “High Slave Addr” parameters for each port must configured properly. Network 3000 Communications Configuration Guide Page 4-3...
  • Page 50 That is, if the Master Port is set at 9,600 baud, the Slave Port in each slave node on that port must also be set at 9,600 baud. Bristol Babcock controllers do NOT ‘fall back’ to lower baud rates if they are unable to communicate at the specified rate.
  • Page 51 'Configuring Advanced Master Polling Parameters' on page 4-10 for details. For a technical description of the polling algorithm, and the handling of ‘dead nodes’ see the Network 3000 Communications Application Programmer’s Reference (document# D4052). Network 3000 Communications Configuration Guide Page 4-5...
  • Page 52 POLLPER.BAT program from the on-line bulletin board of Bristol Babcock’s Application Support Group. Bristol’s Application Support Group can be contacted using the phone numbers listed on page ii of this manual. Page 4-6 Network 3000 Communications Configuration Guide...
  • Page 53 Making the poll period too short will cause the system to go as fast as it can, but can reduce throughput by eliminating preferred polling and other aspects of the polling algorithm. Network 3000 Communications Configuration Guide Page 4-7...
  • Page 54 NOTE: Make sure the refresh rates for DataView are not set longer than the poll period or this technique will NOT work. Some dead time is always required. It is used for processing alarms, download messages, etc. Page 4-8 Network 3000 Communications Configuration Guide...
  • Page 55 If you enter a negative value for #NDARRAY.., the absolute value of the number you enter refers to a signal list, which allows advanced users to define the node array and set additional polling parameters, See ‘Configuring Advanced Master Polling Parameters’, later in this chapter, for details. Network 3000 Communications Configuration Guide Page 4-9...
  • Page 56 See the ‘EAStatus Module’ and ‘Expanded Node Addressing’ sections of the ACCOL II Reference Manual (document# D4044) for details. Page 4-10 Network 3000 Communications Configuration Guide...
  • Page 57 4-5 will be used instead. POLL MSG ATTEMPTS this analog signal specifies that number of times the Master Port will attempt to send a poll message to its Network 3000 Communications Configuration Guide Page 4-11...
  • Page 58 Page 4-12 Network 3000 Communications Configuration Guide...
  • Page 59 SET.SIZE. = 1 *LIST 7 NDARRAY.. SET.SIZE PORTA.RESP.TIMO PORTC.RESP.TIMO PORTD.RESP.TIMO RASCL stands for Redundant Automatic Switching Communication Link, and is available on certain ports and versions of the DPC 3330 and DPC 3335. Network 3000 Communications Configuration Guide Page 4-13...
  • Page 60 One Pseudo Slave with Alarms Port, and several Pseudo Slave Ports may be defined for use by Pseudo Master devices, but these ports do NOT serve the same function as the Slave Port. See Appendix A for summary information on port types. Page 4-14 Network 3000 Communications Configuration Guide...
  • Page 61 In this case, the Slave Port poll period would be set ‘tightly’ since the fresh acquisition of data is critical. Network 3000 Communications Configuration Guide Page 4-15...
  • Page 62: Using Advanced Poll Period Parameters

    Master Port will ignore it. The IMMEDIATE RESPONSE DELAY specifies a period of time (in seconds) that a Slave node will wait, before responding to a request for data from its Master. This delay can actually speed up Page 4-16 Network 3000 Communications Configuration Guide...
  • Page 63 ’Communication Ports’ section of the ACCOL II Reference Manual (document# D4044). For details on setting the poll period for an RIOR Port, see the discussion on poll periods in the ’System Signals’ section of the same manual. Network 3000 Communications Configuration Guide Page 4-17...
  • Page 64: Setting Up Data Link Parameters At The Network Master

    Ports apply. The Network Master has to perform polling, it has to do this at a certain baud rate, etc. This section will highlight certain aspects of the configuration of Network Master communications for the two Bristol Babcock supplied Network Master software packages - - Open BSI Utilities (either Version 2.x or 3.x and newer), and the Universal Operator Interface (UOI).
  • Page 65 Chapter 4 - Guidelines For Configuring the BSAP Data Link Network 3000 Communications Configuration Guide Page 4-19...
  • Page 66 Communication Line Parameters dialog box. All parameters within this dialog box are related to configuration of the data link. Many serve similar functions to the parameters used when defining a Master Port. (See the figure below.) Page 4-20 Network 3000 Communications Configuration Guide...
  • Page 67 In Open BSI Version 3.0 (or newer), the Network Host PC (NHP) serves as the Network Master of the BSAP network. Open BSI Version 3.0 (and newer) data link parameters are configured in the Comm Line Wizard of NetView: Network 3000 Communications Configuration Guide Page 4-21...
  • Page 68 Chapter 4 - Guidelines For Configuring the BSAP Data Link Adjustments to the link-level timeout period, and dialing parameters may be made via the [Advanced Parameters] push button. Page 4-22 Network 3000 Communications Configuration Guide...
  • Page 69 (as defined in NETTOP) needs to be entered. Once the decision concerning local or global communication has been made, the user must enter the actual data link parameters including the baud rate, timeout, etc. Network 3000 Communications Configuration Guide Page 4-23...
  • Page 70 POLL_RATE parameter value in the ATOOLS.INI file. Valid rates which may be entered are: 0.15, 0.2, 0.25, 0.3, 0.4, 0.5, or 1.0. For full details on the ATOOLS.INI file, see the ACCOL II Reference Manual (document# D4044). Page 4-24 Network 3000 Communications Configuration Guide...
  • Page 71: Bsap Local Line (Used For Special Applications Only)

    • Users running Open BSI on a laptop/notebook PC want to plug into the pseudo slave port of a Network 3000 controller which is at a lower level of the BSAP network (network level 2, 3, 4, 5, or 6) to view data from various network nodes.
  • Page 72: Configuration Issues For Modems

    A pair of modems is required for each setup; i.e. there must be one modem on each end of the telephone line. Depending upon the Network 3000 series controller(s) you are using, they may have an internal modem already installed. In other cases, external modems must be purchased.
  • Page 73 &H0 Disable data compression. &K0 Disable error control. NOTE: This setting is NOT &M0 required if you have an identically configured modem at the RTU end. Ignore RTS for receive data (RD). &R1 Network 3000 Communications Configuration Guide Page 4-27...
  • Page 74 Bristol Babcock controllers dynamically change their baud rates. If you are configuring a Network 3000-series controller to dial another Network 3000-series controller, or an Open BSI Workstation: The ‘Auto-dial’ feature must be configured. It allows controllers to dial out. "...
  • Page 75 A negative value for the #DIAL.nnn. signal specifies that the Enhanced Slave Dial Control Signal List will be used. Auto-dialing is described in the ‘Auto-Dial Modem Interface’ section of the " ACCOL II Reference Manual (document# D4044). Highlights from that section are presented below. Network 3000 Communications Configuration Guide Page 4-29...
  • Page 76 Possible values for this signal are shown in the table, below: Error/Status Code: Description Dialing or Special Command completed successfully Dialing or Special Command in progress Phone hung up Dialing complete but line was Busy Page 4-30 Network 3000 Communications Configuration Guide...
  • Page 77 If you are specifying a special command for a Hayes-compatible modem, you must precede it with an exclamation point ‘!’ in the first character position. The remainder of the string is sent, and automatically terminated with a carriage return (13 or 0DH, not shown below): Network 3000 Communications Configuration Guide Page 4-31...
  • Page 78 Enhanced Slave Dial Control Signal List. It is similar to the Dial Control Signal List except it has some additional signals which include the Empty Transmit Queue disconnect time signal, and the DIAL_UP_ACK enable signal. Page 4-32 Network 3000 Communications Configuration Guide...
  • Page 79 80 PHONENUM.CALL.RTU2 90 PHONENUM.CALL.RTU3 In this case, it should be set to 6 because there are two special purpose signals ( MAXEMPTY.QUEUE.TIME ) which pushes the PORTD.DIALUP.ACK PHONE#/COMMAND SELECT signal (PORTD.PHONE.SEL) to position 6. Network 3000 Communications Configuration Guide Page 4-33...
  • Page 80 Open BSI can be configured to send an initialization string to the modem. Any other modem configuration must be performed using any modem configuration software provided by the modem manufacturer, or if applicable, through switch settings on the modem. Page 4-34 Network 3000 Communications Configuration Guide...
  • Page 81 When configuring the dial string in the Open BSI Setup Tool’s RTU Dial Strings dialog box, include a ‘DT’ or ‘DP’ modem command in the string. Open BSI immediately precedes the dial string with the ‘AT’ modem command. Network 3000 Communications Configuration Guide Page 4-35...
  • Page 82 (accessible from the third page of the RTU Wizard in NetView), include a ‘DT’ or ‘DP’ modem command in the string. Open BSI immediately precedes the dial string with the ‘AT’ modem command. Page 4-36 Network 3000 Communications Configuration Guide...
  • Page 83: Configuration Issues For Radios

    Chapter 4 - Guidelines For Configuring the BSAP Data Link Configuration Issues For Radios Bristol Babcock Network 3000 equipment has been used successfully with several different brands and types of radios. The configuration of the radio interface varies depending upon the type of radio, particularly with respect to cabling and timing.
  • Page 84 Click on the plus sign ’+’ next to the ’Ports (COM & LPT)’ selection. A list of ports will appear. Click once on the port used for Open BSI communications (typically COM1 or COM2), then click on the [Properties] push button. Page 4-38 Network 3000 Communications Configuration Guide...
  • Page 85 Communication Port Properties dialog box, and in the Device Manager page, to exit the control panel and save the settings. Reboot your PC for the new settings to take effect. Network 3000 Communications Configuration Guide Page 4-39...
  • Page 86 BLANK PAGE...
  • Page 87: Chapter 5 - Guidelines For Configuring The Ip Data Link

    Specifying the characteristics of the IP port(s) in the RTU’s FLASH memory " using the "RTU Comm Config" feature of LocalView. The specific type of IP protocol Bristol Babcock uses is called the User Datagram Protocol (UDP). Network 3000 Communications Configuration Guide Page 5-1...
  • Page 88: Declaring An Ip Port In Accol Workbench

    PORT_I IP PORT_J IP ETHRNT IP No other configuration is necessary within the ACCOL source file. IP Port baud rate and other characteristics must be defined using the "RTU Comm Config" feature of LocalView. Page 5-2 Network 3000 Communications Configuration Guide...
  • Page 89: Specifying The Characteristics Of The Ip Port(S)

    LocalView always uses BSAP to communicate, even though you are configuring IP port parameters with it. A full description of the RTU Comm Config feature is included in the Open BSI Utilities Manual ( document# D5081). Network 3000 Communications Configuration Guide Page 5-3...
  • Page 90 Setting Up the Ethernet Interface Ethernet parameters are only configured if you are using the Ethernet Port as your IP Port; they do NOT apply if you are only using serial IP ports. Page 5-4 Network 3000 Communications Configuration Guide...
  • Page 91 Be sure to select an Internet Protocol (such as ’PPP_HDLC’ or ’User Mode’ if you have created your own Internet Protocol implementation) for the port; choosing either ’BSAP’ or ’EBSAP’ will disable the Internet parameters. Network 3000 Communications Configuration Guide Page 5-5...
  • Page 92: Defining The Ip System Parameters

    Chapter 5 - Guidelines For Configuring the IP Data Link Defining the IP System Parameters Once your IP ports have been defined (either Ethernet or Serial) you must also define certain IP System Parameters. Page 5-6 Network 3000 Communications Configuration Guide...
  • Page 93: Chapter 6 - Application Notes

    (BSAP Master/Slave Modules) Peer-to-peer communication is the transfer of signal list or data array data from one Network 3000 controller to another. This transfer is performed using Master Modules (or EMaster Modules) and Slave Modules. Peer-to-peer communication is typically used in situations where one controller must make some logical decision based on data from another controller.
  • Page 94 ‘alarm state’, the user will know that peer-to-peer To make this timeout modification, see instructions under the MODE terminal description in the ‘Master/EMaster’ section of ACCOL II Reference Manual (document# D4044). Page 6-2 Network 3000 Communications Configuration Guide...
  • Page 95 20 * WAIT FOR (MASTER1.COMM.DONE) 0.1 Level n+1 30 * MASTER REMOTE WAIT statement is used POINT to prevent another MASTER MODE Module from being started before the first one finishes its transaction. Network 3000 Communications Configuration Guide Page 6-3...
  • Page 96: Peer-To-Peer Communication (Ip_Client/Ip_Server Modules)

    IP_Client Module only at certain times or when certain data is ready. NOTE Currently, the only IP-capable Network 3000 RTU’s are 386EX Protected Mode versions of the DPC 3330 or DPC 3335, with PES03/PEX03 or newer firmware. To perform peer-to-peer communication in non-IP RTU’s you must use BSAP...
  • Page 97 RTU’s which will be granted access via IP_Client requests. In this case, we must identify the RTU with address 120.0.0.1. NOTE: Always check for successful completion via the STATUS terminal(s) before attempting to use peer-to-peer data. Network 3000 Communications Configuration Guide Page 6-5...
  • Page 98 Chapter 6 - Application Notes Page 6-6 Network 3000 Communications Configuration Guide...
  • Page 99: Setting Task Rates

    For more information on task rates, see ‘An Introduction to ACCOL’ (document# D4056) for details. For a list of system tasks priorities, see the ‘Task’ section of the ACCOL II Reference Manual (document# D4044). For more information on task priority see ‘An Introduction to ACCOL’ (document# D4056). Network 3000 Communications Configuration Guide Page 6-7...
  • Page 100: Accol Load Design Issues

    Buffers are pre-allocated blocks of memory which are used to hold data messages. The system automatically allocates a certain number of buffers in your Network 3000 controller; additional buffers should be added by the user, depending upon the requirements of your application. Page 6-8 Network 3000 Communications Configuration Guide...
  • Page 101: Report By Exception (Rbe)

    In order for RBE data to be viewed by the user, the central software (i.e. Network Master HMI/SCADA package) must include RBE Manager software. Not all HMI/SCADA packages support this. For more information on RBE, see the ‘RBE’ section of the ACCOL II Reference Manual (document# D4044). Network 3000 Communications Configuration Guide Page 6-9...
  • Page 102: Open Bsi Utilities (Version 2.3 Or Earlier)

    “RTU Message Timeout” represents the length of time (in seconds) that Open BSI will wait for a Network 3000 controller to respond to an application’s specific request for data. To determine a minimum value for this number, find the longest Master Port poll period for each level of the network (including the Network Master level.) The “RTU Message Timeout”...
  • Page 103: Open Bsi Utilities (Version 3.0 Or Newer)

    Click here A node must respond to a program (such as to go to page 2 DataView) within this time period. If no response is received, that node is said to have ‘timed out.’ Network 3000 Communications Configuration Guide Page 6-11...
  • Page 104: Open Bsi Scheduler And Open Bsi Data Collector Array/Archive Collection (All Versions)

    If you are using OpenEnterprise software, most communications configuration is performed within Open BSI itself, and not in OpenEnterprise. Certain items, however, such as RBE scan rates and data collection rates are defined within OpenEnterprise. Page 6-12 Network 3000 Communications Configuration Guide...
  • Page 105: Enterprise Server

    BSIMexBuff= m m this parameter defines the maximum number of buffers that are allocated from the pool of Open BSI buffers available for use by the Network 3000 Communications Configuration Guide Page 6-13...
  • Page 106: Iconics Genesis

    Genesis workstation is connected. Also, verify that the same NODE ID is used in NETTOP. NOT all versions of Genesis support peer-to-peer communication between top-level (level 1) Network 3000 controllers. Page 6-14 Network 3000 Communications Configuration Guide...
  • Page 107 • Use the hardware and software diagnostic tools provided with the product. Bristol Babcock hardware often includes failure LEDs which can help identify problems. Many ACCOL software modules report error and status data which may be viewed on-line.
  • Page 108: Trouble-Shooting Techniques

    #TIME.001. and #TIME.007. signals (which are in units of seconds). The rate at which these signals change will tell you how fast data is being updated at the PC. For help on using DataView, see the Open BSI Utilities Manual (document# D5076 or D5081). Page 7-2 Network 3000 Communications Configuration Guide...
  • Page 109 ACCOL II Reference Manual (document# D4044) for details. Check Both Ends of Your Communication Line Using the Open BSI Monitor (or Monitor Window in NetView) and the Open BSI Remote Communication Statistics Tool Network 3000 Communications Configuration Guide Page 7-3...
  • Page 110 Open BSI communications, and the top-level nodes in the network. Check the Buffer Usage Statistics dialog box to see if you have enough buffers at the PC. Page 7-4 Network 3000 Communications Configuration Guide...
  • Page 111 Chapter 7 - Trouble-shooting Communications Another thing to check in the Open BSI Monitor is the statistics that Open BSI has collected about its communication with the top-level Network 3000 controllers. These are displayed in the RTU Details Window. NOTE: The information displayed in the RTU Details window is collected at the workstation end of the communication line, it does NOT reflect statistics collected directly from the RTU.
  • Page 112 If you are using Open BSI Utilities Version 3.0 (or newer), the Monitor Window in NetView can provide you with information on the operation of Open BSI communications. Check the Buffer Usage Statistics dialog box to see if you have enough buffers at the PC. Page 7-6 Network 3000 Communications Configuration Guide...
  • Page 113 Chapter 7 - Trouble-shooting Communications If you have a BSAP network, the Monitor Window allows you to examine statistics about the top-level Network 3000 controllers. These statistics are displayed in the RTU Details Window: NOTE: The information displayed in the RTU Details window is collected at the workstation end of the communication line, it does NOT reflect statistics collected directly from the RTU.
  • Page 114 NOTE: The information displayed in the RTU Details window is collected at the workstation end of the communication line, it does NOT reflect statistics collected directly from the RTU. RTU statistics are available from the Remote Communication Statistics Tool, discussed later. Page 7-8 Network 3000 Communications Configuration Guide...
  • Page 115 Tool relates to buffers in the controller (not the PC). The EGM 3530 TeleFlow / RTU 3530 TeleRTU units do NOT store communication statistics, therefore, the Remote Communication Statistics Tools cannot collect and report communication statistics from these units. Network 3000 Communications Configuration Guide Page 7-9...
  • Page 116 Chapter 7 - Trouble-Shooting Communications The Port Detail Statistics Window displays statistics collected on the operation of the communication ports in the controller. Master Port details are shown at right: Page 7-10 Network 3000 Communications Configuration Guide...
  • Page 117 Chapter 7 - Trouble-shooting Communications Information on Slave Port details is shown below: Network 3000 Communications Configuration Guide Page 7-11...
  • Page 118 If you are using an IP Port, statistics are collected for the port itself, as well as the functioning of the protocol used for the port. Information on the port itself is shown in the window, below: Page 7-12 Network 3000 Communications Configuration Guide...
  • Page 119 Do NOT confuse ’Protocol’ with the custom protocols which can be configured in ACCOL for communication with foreign devices. ’Protocol’, in this case, refers to layered protocols which make up this Internet Protocol (IP) implementation - these layers are: IP, ICMP, UDP, and IBP. Network 3000 Communications Configuration Guide Page 7-13...
  • Page 120 Chapter 7 - Trouble-Shooting Communications ICMP Protocol Statistics: Page 7-14 Network 3000 Communications Configuration Guide...
  • Page 121 Chapter 7 - Trouble-shooting Communications UDP Protocol Statistics: Network 3000 Communications Configuration Guide Page 7-15...
  • Page 122 Protected Mode controllers or 3530 TeleFlow/TeleRTU units. See the Toolkit Manual (document# D4053) for details. In addition, Port statistics may also be viewed on-line using the Portstatus Module. See the ’Portstatus’ section of the ACCOL II Reference Manual (document# D4044) for details. Page 7-16 Network 3000 Communications Configuration Guide...
  • Page 123 NetView to see that IP Mask and IP addresses are correctly defined. Check to see that the IP mask you configured is identical to the IP mask defined during TCP/IP installation. Network 3000 Communications Configuration Guide Page 7-17...
  • Page 124 RTU Configure mode in LocalView) is incorrect or out-of-range. Once you have fixed any of these problems, communication using PING should be possible. If it is, but Open BSI still cannot communicate, start checking for Open BSI configuration problems. Page 7-18 Network 3000 Communications Configuration Guide...
  • Page 125 In addition, certain Open BSI driver parameters may be modified. For detailed descriptions of the BSBSAP.INI and BSIPDRV.INI files, please consult Appendix E of the Open BSI Utilities Manual (document# D5081). Network 3000 Communications Configuration Guide Page 7-19...
  • Page 126 IP line for an RTU which has only one IP line should NOT be considered a problem. IMPORTANT: You should also check to make sure that the RTU has not been marked "Off-Line". If it has been, de-select that flag. IP Internal Debug Info: Page 7-20 Network 3000 Communications Configuration Guide...
  • Page 127 Chapter 7 - Trouble-shooting Communications BSAP Internal Debug Info: IMPORTANT: You should also check to make sure that the RTU has not been marked "Off-Line". If it has been, de-select that flag. Network 3000 Communications Configuration Guide Page 7-21...
  • Page 128: Frequently Asked Questions Concerning Communication Problems

    #LINE.007.=Port H #LINE.008.=Port I #LINE.009.=Port J For a Slave, Pseudo Slave, or Pseudo Slave with Alarms Port, the #LINE.nnn logical alarm signal is turned ON if there are no poll messages on the Page 7-22 Network 3000 Communications Configuration Guide...
  • Page 129 The local address of the slave node is indicated by the nnn. This could be for many reasons, but is usually due to data link problems. Check cabling, baud rates, etc. Network 3000 Communications Configuration Guide Page 7-23...
  • Page 130 There could be a problem with the ACCOL Task. operating satisfactorily, Also, check to see that the signals affected are but certain signals are NOT control inhibited. NOT changing and they should be." Page 7-24 Network 3000 Communications Configuration Guide...
  • Page 131 The ’Node Currently Off-Line’ message will ‘Node Currently Off- appear in Open BSI if either 1) Open BSI cannot find the node you are looking for, or 2) it cannot Line’. If I look at the On Network 3000 Communications Configuration Guide Page 7-25...
  • Page 132 4) Node has been marked off-line. In the NetView tree, right-click on the icon for the RTU, and choose "Properties" then go to the 'Internal' tab. De-select the "Off-Line" RTU flag, if it is selected. Page 7-26 Network 3000 Communications Configuration Guide...
  • Page 133 FOR OPEN BSI 3.0 (or newer) ONLY: For Protected Mode RTUs with PES03/PEX03, PLS03/PLX03 or newer firmware, ONLY, you can "I set the local address set the Default Switch (SW1-3) to its OFF Network 3000 Communications Configuration Guide Page 7-27...
  • Page 134 3 times the "Timeout" value specified on the Define Local Link portion of the Communication Setup Menus. If you are in the process of establishing communications when this occurs, there is probably a data link or network routing Page 7-28 Network 3000 Communications Configuration Guide...
  • Page 135 ACCOL load running in the unit, and the Error’. What does this .ACO/ACL files on the hard disk of your PC. You mean?" may need to re-link and re-download the unit to clear up this problem. Network 3000 Communications Configuration Guide Page 7-29...
  • Page 136: Checklist For Diagnosing Communication Problems

    Chapter 7 - Trouble-Shooting Communications Checklist For Diagnosing Communication Problems This checklist is adapted from information provided by the Bristol Babcock Application Support Group. These represent the most common problems customers encounter when configuring communications. DID YOU ACCURATELY DEFINE YOUR NETWORK AND ARE THE NETWORK FILE(S) ACCESSIBLE TO ALL NODES? For DOS-based ACCOL Tools, and/or Open BSI 2.3 (or earlier):...
  • Page 137 For Open BSI 3.0 (or newer) Users: Establish communications using LocalView, then activate Downloader from within LocalView. This will ensure you are downloading to the correct node. Network 3000 Communications Configuration Guide Page 7-31...
  • Page 138 Are the Slaves really being polled at better than or equal to the assigned #POLLPER? If not, then the Slaves’ time-out may be insufficient. ARE ACCOL TASK PRIORITIES SET TOO HIGH? ACCOL task priorities should be set below 32 to avoid conflicts with communication task priorities. Page 7-32 Network 3000 Communications Configuration Guide...
  • Page 139 "Node Information" in the pull down menu, and "Debug Flags" in the second pull down menu. See the ACCOL Workbench User Manual (document# D4051) for more information. For Taskspy users, you can choose the ’Show Flags’ poke point from the Network 3000 Communications Configuration Guide Page 7-33...
  • Page 140 Task control statements in ACCOL (e.g. WAIT FOR or SUSPEND) can also halt task execution. [ ] 12. DOES THE NETWORK 3000 CONTROLLER HAVE ENOUGH COMMUNICATION I/O BUFFERS? At least 10 additional I/O Buffers should be assigned. As a general rule, it is better to have too many buffers than too few.
  • Page 141 IP address in the actual RTU using the "RTU Configure" option of LocalView, and then you need to reset or re-download the RTU for the IP address to become active. Network 3000 Communications Configuration Guide Page 7-35...
  • Page 142 ’Internal’ page of the RTU Properties. If this happens, no communication with that RTU will occur. To check if the off-line flag is set, right-click on the RTU in the Page 7-36 Network 3000 Communications Configuration Guide...
  • Page 143 Chapter 7 - Trouble-shooting Communications NetView tree, and choose "Properties". Then select the ’Internal’ tab, and de-select the "Off-Line" RTU flag, if it is selected. Network 3000 Communications Configuration Guide Page 7-37...
  • Page 144 BLANK PAGE...
  • Page 145: Appendix A - Summary Of Port Types

    VSAT Master software to support it. PC workstations with Open BSI Utilities (Version 2.1 and newer) can serve as VSAT Master devices, however, Network 3000-series controllers CANNOT serve as VSAT Masters. IP Port This type of port is ONLY supported in DPC 3330/DPC 3335...
  • Page 146 Appendix A - Summary of Port Types Port Type: When would I need to use this type of port? Logger Port This type of port allows ASCII information to be output to an attached printer or terminal device. Page A-2 Network 3000 Communications Configuration Guide...
  • Page 147: Appendix B - Message Traffic

    This appendix will briefly discuss (in greatly simplified terms) the underlying message traffic involved in three different polling methods, and the major advantages and disadvantages of each method. These methods are: • BSAP Transactions • Immediate Response Transactions • VSAT Transactions. Network 3000 Communications Configuration Guide...
  • Page 148 Appendix B - Message Traffic BSAP Transactions BSAP is a standard method of communication among Network 3000-series controllers. A Master node sends out messages on its Master Port, and the Slave node receives them, and sends out responses on its Slave Port.
  • Page 149 Appendix B - Message Traffic Master Node Slave Node Figure 1 BSAP Transaction Network 3000 Communications Configuration Guide Page B-3...
  • Page 150 Appendix B - Message Traffic Immediate Response Transactions The immediate response concept was initially limited to only certain Network 3000- series devices such as the EGM 3530-10A and EGM 3530-50A TeleFlow, the 3508 TeleTrans Transmitter, the SLC 3740, and the older model RTU 3320. These...
  • Page 151 Appendix B - Message Traffic Master Node Delay time Slave Node Figure 2 Immediate Response Transaction Network 3000 Communications Configuration Guide Page B-5...
  • Page 152 Appendix B - Message Traffic VSAT Transactions VSAT transactions differ from BSAP and immediate response transactions in that Network 3000 controllers CANNOT be configured as VSAT Masters. Open BSI Workstations, however, can communicate with top-level nodes configured as VSAT slaves.
  • Page 153 Appendix B - Message Traffic Open BSI Workstation Top Level Node Figure 3 VSAT Transaction Network 3000 Communications Configuration Guide Page B-7...
  • Page 154: Is This Still Unclear

    According to the VSAT Slave method, the transactions would go as follows: You: I’d like a dozen jelly doughnuts. (Data Request) (The cashier goes into the back room, without saying anything, and a few moments later, emerges with a box) Page B-8 Network 3000 Communications Configuration Guide...
  • Page 155 BSAP transactions are appropriate for most situations. If, however, the underlying message traffic of BSAP results in higher cost communication, one of the other methods (immediate response, or VSAT) may be a viable substitute. Network 3000 Communications Configuration Guide Page B-9...
  • Page 156 BLANK PAGE...
  • Page 157: Glossary

    Application is a program or function which makes use of the data link to transmit messages. Among the applications supported in Network 3000 are Open BSI utilities such as DataView, Intellution® FIX®, and ACCOL Master Modules. Baud Rate the character-by-character rate at which data flows on a communication line.
  • Page 158 Communication protocol this is the method by which a particular device communicates. The standard communication protocol used by Network 3000 controllers is BSAP, (there is also a separate version of BSAP used for large networks called EBSAP). Some Network 3000 controllers can also communicate using Internet Protocol (IP).
  • Page 159 First level slave same as Top Level Node. See ’Top Level Node’. Global a message between two Network 3000 nodes is considered ’global’ if it must pass between one or more additional nodes on its journey. For example, if a message between DPC2 and DPC7 goes directly, without passing through any other nodes, it is considered ’local’, and not ’global’.
  • Page 160 IP mask see Sub-net mask IP node refers, in this context, to a Network 3000 controller (RTU) which supports IP communication. Currently, the only Network 3000 IP nodes are 386EX Protected Mode versions of the DPC 3330 and DPC 3335 with Ethernet hardware and PES03/PEX03 or newer firmware.
  • Page 161 LocalView allows local communication (BSAP only) with any Network 3000 series controller. It is also used to configure cold download parameters and IP addresses for IP controllers. Master refers to a BSAP node containing a Master or EAMaster Port.
  • Page 162 Network Topology Program see NETTOP see Network Host PC Node a Network 3000 controller which is part of a network of Page G-6 Network 3000 Communications Configuration Guide...
  • Page 163 Bristol Babcock Network 3000-series controllers. Among the utilities in the standard Open BSI set are either the Open BSI Setup Tool (Open BSI 2.3 or earlier) or NetView (Open BSI 3.0 or newer), the DataView utility, the...
  • Page 164 DPC 3330s which need to have I/O cards; the I/O must be installed in RIO 3331(s). Report By Exception (RBE) is a method of data collection in which data is collected only when it changes. Page G-8 Network 3000 Communications Configuration Guide...
  • Page 165 Remote Terminal Unit. This refers to any Network 3000- series remote process controller such as the DPC 3330, DPC 3335, RTU 3310, RTU 3305, EGM 3530, RTU 3530, GFC 3308.
  • Page 166 Timeouts are used in configuring both the data link, and the applications which use it. Top Level Node(s) (used in BSAP networks ONLY): a Network 3000 controller which is on the network level immediately below the operator workstation running Open BSI. Also known as a ‘first level node’...
  • Page 167 It’s the only way we know we’re doing our job by giving you correct, complete, and useful documentation. DOCUMENT NUMBER: D5080 TITLE: Network 3000 Communications Configuration Guide ISSUE DATE: April, 2001 COMMENT/COMPLAINT: ______________________________________________________________________________...
  • Page 168 8†w‡ˆƒ€Â8ipqƒqy an FKI company 1100 Buckingham Street Watertown, CT 06795 Telephone: (860) 945-2200...

Table of Contents