s
User Manual
Document: D5081
Part: D301414X012
November 2016
OpenBSI Utilities Manual
OpenBSI Version 5.9
Remote Automa ti on Solution
www.EmersonProcess.com/Remote
Application Safety Considerations
Protecting Operating Processes
A failure of this application – for whatever reason -- may leave an operating process without
appropriate protection and could result in possible damage to property or injury to persons. To protect
against this, you should review the need for additional backup equipment or provide alternate means
of protection (such as alarm devices, output limiting, fail-safe valves, relief valves, emergency shutoffs,
emergency switches, etc.)
CAUTION
When implementing control using this product, observe best industry practices as suggested by applicable
and appropriate environmental, health, and safety organizations. While this product can be used as a safety
component in a system, it is NOT intended or designed to be the ONLY safety mechanism in that system.
OpenBSI Utilities Manual
Changes added in OpenBSI 5.9 Service Pack 3
Support for newer Operating Systems
In addition to Windows 7 Professional, OpenBSI 5.9 Service Pack 3
now supports Windows 10 Professional, and Server 2012.
Support has been dropped for Windows XP. References to earlier
operating systems are for users with older OpenBSI versions.
See Chapter 2 for more information OpenBSI operating system
compatibility.
Changes added in OpenBSI 5.9 Service Pack 1
Support for Rosemount 4088B Transmitter
OpenBSI 5.9 Service Pack 1 includes several changes to support the
Rosemount 4088B transmitter in addition to the legacy Bristol 3808
transmitter:
The NetView toolbox has been modified to replace the 3808 icon with a
generic “MVT” icon that encompasses both the 4088B transmitter and
the legacy 3808 transmitter.
MVT icon covers
the 3808 and the
4088B
Various dialog boxes throughout the OpenBSI tools suite now include
4088B as a valid node choice.
Issued Nov-2016 What’s New In OpenBSI 5.9? iii
OpenBSI Utilities Manual
A set of web pages for the 4088B is available at:
Start > Programs > Web Page Access > 4088B MVT Pages
TechView has been updated to support the 4088B with a specific set of
configuration and calibration pages. See Chapter 10 of the TechView
User’s Guide for more information.
Signal Extractor change
The Signal Extractor now includes a new output option called Create
XML file for OpenEnterprise.
If you are using OpenEnterprise 3.1 (or newer) check Create XML file
for OpenEnterprise to allow Signal Extractor to generate an RTU
definition for this device in XML that can be incorporated into the OE
database.
iv What’s New in OpenBSI 5.9? Issued Nov-2016
OpenBSI Utilities Manual
Features Added in OpenBSI 5.9:
The following items were added in OpenBSI 5.9:
Support for 64-bit Windows Operating Systems
OpenBSI now runs on both 32-bit and 64-bit versions of the Windows 7
and Windows 2008 Server operating systems. Previously, only 32-bit
was supported.
See Chapter 2 for more information OpenBSI operating system
compatibility.
Issued Nov-2016 What’s New In OpenBSI 5.9? v
OpenBSI Utilities Manual
New Version of ControlWave Designer
OpenBSI 5.9 includes a new version of ControlWave Designer (Version
5.35). For information, see the online help within ControlWave
Designer.
Variable Extension Wizard Enhancement for Variable Descriptive Text
A Store All Descriptors option has been added to take all variable
descriptive text residing in the ControlWave project and add it to the
INI file so the user can view it. Previously, users had to do this
manually for each individual variable. See the ControlWave Designer
Programmer’s Handbook (D5125) for more information.
Number of OpenBSI Networks Increased
OpenBSI 5.9 now supports up to 1,000 BSAP networks (including subnetworks). Previously the maximum number of networks was 99.
Harvester allows Pushdown Array/Archive Collection at Designated Hour
Harvester can now start historical collections of pushdown arrays and
archives at a user-defined hour. Previously collections always began at
midnight on the specified day. See the OpenBSI Harvester Manual
(D5120) for more information.
.
vi What’s New in OpenBSI 5.9? Issued Nov-2016
OpenBSI Utilities Manual
Contents
Chapter 1 – Introduction – What is OpenBSI? 1-1
1.1 RTUs and NHPs ........................................................................................................................ 1-4
1.1.1 Remote Terminal Units (RTUs): .................................................................................... 1-4
1.1.2 Network Host PC (NHP) ................................................................................................ 1-4
1.2 Supported Network Configurations ........................................................................................... 1-5
1.3 BSAP Networks ......................................................................................................................... 1-5
1.3.1 Local and Global Addressing ........................................................................................ 1-5
1.3.2 Network Levels .............................................................................................................. 1-5
1.3.3 Supported Communication Methods in BSAP .............................................................. 1-6
1.3.4 Peer-to-Peer Communication ........................................................................................ 1-6
1.3.5 Variations on Standard BSAP – EBSAP ....................................................................... 1-7
1.3.6 Variations on Standard BSAP – BSAP Local Line ........................................................ 1-7
1.4 IP Networks ............................................................................................................................. 1-10
1.4.1 Applications Using IP .................................................................................................. 1-10
1.4.2 Differences between IP Nodes and Other RTUs ........................................................ 1-11
1.4.3 Controllers That Support IP ......................................................................................... 1-12
Format of IP Addresses .......................................................................................................... 1-13
Meaning of IP Address Components ...................................................................................... 1-13
Rules for Local Addressing Schemes .................................................................................... 1-14
Sub-net masks determine which nodes are reachable from a given node ............................ 1-15
1.4.4 Guidelines for Choosing Addresses in a Private Network .......................................... 1-17
1.4.5 IP Network Variations – Connecting Two Networks with a Single Router .................. 1-18
1.4.6 IP Network Variations - Using Multiple Routers (Gateways) and RIP for a Fault Tolerant
Connection .............................................................................................................................. 1-22
1.4.7 IP Network Variations - Using Multiple Routers (Gateways) without RIP ................... 1-22
1.5 IP Network Security Protocols (CHAP and PAP) Used on PPP Links .................................... 1-24
1.5.1 Challenge Handshaking Authentication Protocol (CHAP) .......................................... 1-24
1.5.2 Password Authentication Protocol (PAP) .................................................................... 1-27
1.6 Mixed Networks (Both BSAP and IP nodes) ........................................................................... 1-29
Chapter 2 – Installing OpenBSI 2-1
2.1 Hardware and Software Requirements ..................................................................................... 2-2
2.1.1 Controllers used with OpenBSI ..................................................................................... 2-2
2.1.2 Recommended Hardware/Software for the OpenBSI Workstation: .............................. 2-2
2.2 Installing the OpenBSI Utilities .................................................................................................. 2-3
2.3 Registering Your Software ...................................................................................................... 2-10
2.3.1 How do I Register My Software? ................................................................................ 2-10
2.4 How to Transfer a License from One PC to another PC ......................................................... 2-17
2.4.1 Using the software… ................................................................................................... 2-22
2.5 Using OpenBSI with Newer Microsoft® Windows Operating Systems ................................... 2-22
2.5.1 Which OpenBSI Features are affected? ..................................................................... 2-23
2.5.2 How do I make these applications work properly with Windows? .............................. 2-23
What is a Firewall? ................................................................................................................. 2-23
2.6 Using OpenBSI with Microsoft® Windows XP Service Pack 2 ............................................... 2-24
2.6.1 Reconfiguring the Windows XP Firewall ..................................................................... 2-24
2.6.2 Disabling the Windows XP Firewall ............................................................................ 2-24
2.6.3 Making Object Server an Exception to the Windows XP Firewall............................... 2-24
2.6.4 Add Ports for DCOM and RTRSERVC for the XP firewall .......................................... 2-26
2.6.5 Add Ports for the Bristol IP Driver (BSIPDRV) for the XP firewall .............................. 2-28
2.6.6 Reconfiguring the DCOM Software for the XP firewall ............................................... 2-29
2.7 Using OpenBSI with Microsoft® Windows 2008 Server ......................................................... 2-34
Issued Nov-2016 Contents vii
OpenBSI Utilities Manual
2.7.1 Reconfiguring the Windows 2008 Server Firewall ...................................................... 2-34
2.7.2 Disabling the Windows 2008 Server Firewall ............................................................. 2-34
2.7.3 Making Object Server an Exception to the Windows 2008 Server Firewall ................ 2-35
2.7.4 Add Ports for DCOM and RTRSERVC for the Windows 2008 Firewall ...................... 2-37
2.7.5 Add Ports for the Bristol IP Driver (BSIPDRV) for the Windows 2008 Server Firewall2-39
2.7.6 Reconfiguring the DCOM Software for the Windows 2008 Server Firewall ............... 2-41
2.8 Using OpenBSI with Microsoft® Windows 7 ........................................................................... 2-47
2.8.1 Reconfiguring the Windows 7 Firewall ........................................................................ 2-47
2.8.2 Disabling the Windows 7 Firewall ............................................................................... 2-47
2.8.3 Making Object Server an Exception to the Windows 7 Firewall ................................. 2-47
2.8.4 Add Ports for DCOM and RTRSERVC for the Windows 7 Firewall ............................ 2-56
2.8.5 Add Ports for the Bristol IP Driver (BSIPDRV) for the Windows 7 Firewall ................ 2-57
2.8.6 Reconfiguring the DCOM Software for the Windows 7 Firewall ................................. 2-59
2.9 Using OpenBSI with Microsoft® Windows 10 Professional .................................................... 2-59
2.9.1 Reconfiguring the Windows 10 Firewall ...................................................................... 2-59
2.9.2 Disabling the Windows 10 Firewall ............................................................................. 2-59
2.9.3 Making Object Server an Exception to the Windows 10 Firewall ............................... 2-60
2.9.4 Add Ports for DCOM and RTRSERVC for the Windows 10 Firewall .......................... 2-67
2.9.5 Add Ports for the Bristol IP Driver (BSIPDRV) for the Windows 10 Firewall .............. 2-68
2.9.6 Reconfiguring the DCOM Software for the Windows 10 Firewall ............................... 2-70
2.10 Using OpenBSI with Microsoft® Windows 2012 Server ......................................................... 2-70
2.10.1 Reconfiguring the Windows 2012 Server Firewall ...................................................... 2-70
2.10.2 Disabling the Windows 2012 Server Firewall ............................................................. 2-70
2.10.3 Making Object Server an Exception to the Windows 2012 Server Firewall ................ 2-71
2.10.4 Add Ports for DCOM and RTRSERVC for the Windows 2012 Server Firewall .......... 2-80
2.10.5 Add Ports for the Bristol IP Driver (BSIPDRV) for the Windows 2012 Server Firewall2-81
2.10.6 Reconfiguring the DCOM Software for the Windows 2012 Server Firewall ............... 2-83
2.11 Recommendations for Using OpenBSI ActiveX Controls ....................................................... 2-83
Chapter 3 – Quickstart (OpenBSI BSAP Communications) 3-1
3.1 Start NetView and Open a New Set of NETDEF Files ............................................................. 3-2
3.2 Use the System Wizard to Define Your Network Host PC (NHP)............................................. 3-4
3.2.1 System Wizard – Page 1 .............................................................................................. 3-4
3.2.2 System Wizard: Page 2 ................................................................................................ 3-5
3.2.3 System Wizard: Page 3 ................................................................................................ 3-6
3.3 Define Your BSAP Network Using the Network Wizard ........................................................... 3-8
3.3.1 Network Wizard: Page 1 ............................................................................................... 3-9
3.3.2 Network Wizard: Page 2 ............................................................................................. 3-10
3.4 Add Controllers to the BSAP Network Using the RTU Wizard ............................................... 3-11
3.4.1 RTU Wizard Page 1 .................................................................................................... 3-12
3.4.2 RTU Wizard Page 2 .................................................................................................... 3-13
3.4.3 RTU Wizard Page 3 .................................................................................................... 3-15
3.5 Define Your Communication Line using the Comm Line Wizard ............................................ 3-16
3.5.1 Comm Line Wizard Page 1 ......................................................................................... 3-17
3.5.2 Comm Line Wizard Page 2 ......................................................................................... 3-18
3.6 Verify Communications Are Active Using DataView ............................................................... 3-19
3.6.1 If NetView communicates…. ....................................................................................... 3-21
3.6.2 If NetView fails to communicate… .............................................................................. 3-22
Chapter 4 – Quickstart (OpenBSI IP Communications) 4-1
4.1 Using IP with ControlWave and Network 3000 RTUs ............................................................... 4-2
4.2 Start NetView and Open a New Set of NETDEF Files ............................................................. 4-3
4.3 Use the System Wizard to Define Your Network Host PC (NHP)............................................. 4-4
viii Contents Issued Nov-2016
OpenBSI Utilities Manual
4.3.1 Function of the NHP in an IP Network .......................................................................... 4-4
4.3.2 System Wizard – Page 1 ............................................................................................... 4-5
4.3.3 System Wizard: Page 2 ................................................................................................. 4-6
4.3.4 System Wizard: Page 3 ................................................................................................. 4-7
4.4 Define Your IP Network Using the Network Wizard .................................................................. 4-9
4.4.1 Network Wizard: Page 1 ............................................................................................. 4-10
4.4.2 Network Wizard: Page 2 ............................................................................................. 4-11
4.5 Add Controllers to the IP Network Using the RTU Wizard ...................................................... 4-11
4.5.1 RTU Wizard Page 1 .................................................................................................... 4-12
4.5.2 RTU Wizard Page 2 .................................................................................................... 4-14
4.5.3 RTU Wizard Page 3 .................................................................................................... 4-15
4.5.4 RTU Wizard Page 4 .................................................................................................... 4-17
4.6 Set RTU Configuration Parameters in Each RTU ................................................................... 4-18
4.7 Define Your Communication Line using the Comm Line Wizard ............................................ 4-18
4.7.1 Comm Line Wizard Page 1 ......................................................................................... 4-19
4.7.2 Comm Line Wizard Page 2 ......................................................................................... 4-20
4.8 Verify Communications Are Active Using DataView ............................................................... 4-21
4.8.1 If NetView communicates…. ....................................................................................... 4-23
4.8.2 If NetView fails to communicate… .............................................................................. 4-24
Chapter 5 – Using LocalView 5-1
5.1 LocalView Operational Restrictions .......................................................................................... 5-2
5.2 View Mode Files ........................................................................................................................ 5-2
5.3 System Firmware and RTU Configuration Parameters............................................................. 5-2
5.3.1 System Firmware .......................................................................................................... 5-2
5.3.2 RTU Configuration Parameters ..................................................................................... 5-3
5.3.3 OpenBSI Application Parameters ................................................................................. 5-3
5.4 Methods for Starting LocalView ................................................................................................ 5-3
5.5 Establishing Communications with an Attached RTU (Local Mode) ......................................... 5-4
5.5.1 Before You Begin .......................................................................................................... 5-4
5.5.2 Starting LocalView and the Setup Wizards ................................................................... 5-5
5.5.3 Communications Setup Wizard ..................................................................................... 5-6
5.5.4 RTU Setup Wizard ........................................................................................................ 5-8
5.5.5 Dial & Command Setup Wizard .................................................................................... 5-9
5.6 After You Have Finished With the Setup Wizards… ............................................................... 5-10
5.6.1 Starting Other Programs in Local Mode ...................................................................... 5-11
5.6.2 Reconfiguring the Active View Mode File ................................................................... 5-13
5.6.3 Saving the View Mode File .......................................................................................... 5-13
5.6.4 Restarting the View Mode File .................................................................................... 5-14
5.6.5 Viewing Current Configuration Parameters ................................................................ 5-14
5.7 Upgrading System Firmware in the Field (Flash Mode) ......................................................... 5-14
5.7.1 Before You Upgrade the System Firmware ................................................................ 5-15
5.7.2 Starting LocalView and the Setup Wizards ................................................................. 5-16
5.7.3 Communications Setup Wizard ................................................................................... 5-16
5.7.4 Flash RTU Setup Wizard ............................................................................................ 5-17
5.7.5 Flash Data Setup Wizard ............................................................................................ 5-19
5.7.6 Setting RTU Configuration Parameters in the 3305 (3305 ONLY) ............................. 5-21
5.8 Assigning IP Addresses and Cold Download Parameters for the Attach ed RTU (Configure Mode)
................................................................................................................................................ 5-23
5.8.1 Starting LocalView and the Setup Wizards ................................................................. 5-23
5.8.2 Communications Setup Wizard ................................................................................... 5-23
5.8.3 IP RTU Setup Wizard .................................................................................................. 5-24
5.9 Setting RTU Parameters in the Flash Configuration Utility ..................................................... 5-26
Issued Nov-2016 Contents ix
OpenBSI Utilities Manual
5.9.1 Flash Configuration Utility Buttons .............................................................................. 5-30
5.9.2 Forcing a Reboot of the ControlWave ......................................................................... 5-34
5.9.3 Flash Configuration Utility Tabs .................................................................................. 5-34
5.9.4 Soft Switches .............................................................................................................. 5-35
5.9.5 Ports ............................................................................................................................ 5-37
5.9.6 IP Parameters ............................................................................................................. 5-4 9
5.9.7 Application Parameters ............................................................................................... 5-54
5.9.8 Archive ........................................................................................................................ 5-57
5.9.9 Audit ............................................................................................................................ 5-62
5.9.10 IP Routes .................................................................................................................... 5-65
5.9.11 Security ....................................................................................................................... 5-67
5.10 Establishing Communications With an IP RTU (IP Comm Mode) .......................................... 5-72
5.10.1 Starting LocalView and the Setup Wizards ................................................................. 5-72
5.10.2 IP Communications Setup Wizard (Step 1 of 3) ......................................................... 5-73
5.10.3 IP Communications Setup Wizard (Step 2 of 3) ......................................................... 5-74
5.10.4 IP Communications Setup Wizard (Step 3 of 3) ......................................................... 5-75
Chapter 6 – Using NetView 6-1
6.1 Starting NetView ....................................................................................................................... 6-3
6.1.1 Network Definition (NETDEF) Files .............................................................................. 6-4
6.1.2 Starting OpenBSI Communications When Windows Starts.......................................... 6-4
6.1.3 Starting NETVIEW from the Command Line ................................................................ 6-7
6.2 Starting OpenBSI Communications .......................................................................................... 6-7
6.2.1 Restarting a Communication Line ................................................................................. 6-8
6.3 Stopping OpenBSI Communications ........................................................................................ 6-8
6.3.1 Method 1: Stop the Communication Line ...................................................................... 6-8
6.3.2 Method 2: Close the Current NETDEF files. ................................................................. 6-8
6.3.3 Method 3: Shut down NetView. ..................................................................................... 6-8
6.4 Opening an Existing Set of NETDEF Files ............................................................................... 6-9
6.5 Saving Changes to Your NETDEF Files ................................................................................. 6-10
6.6 Erasing the Last Change Made to Your NETDEF Files .......................................................... 6-10
6.7 Renaming the Currently Running NETDEF Files ................................................................... 6-10
6.8 Overview of Configuration ....................................................................................................... 6-10
6.9 Defining an NHP and Application Parameters ........................................................................ 6-11
6.9.1 What is A Network Host PC (NHP)? ........................................................................... 6-11
6.9.2 Activating the System Wizard ..................................................................................... 6-15
6.9.3 Navigating Between Pages of the System Wizard ..................................................... 6-15
6.9.4 System Wizard: Step 1 of 3 ........................................................................................ 6-15
6.9.5 System Wizard: Step 2 of 3 ........................................................................................ 6-20
6.9.6 System Wizard: Step 3 of 3 ........................................................................................ 6-25
6.9.7 Signing on to the System ............................................................................................ 6-27
6.9.8 Signing Off .................................................................................................................. 6-28
6.10 Configuring OpenBSI Security ................................................................................................ 6-29
6.10.1 Users, Usernames, and Passwords ............................................................................ 6-29
6.10.2 Default User (SYSTEM) .............................................................................................. 6-29
6.10.3 Assigning or Changing the Password of the Current User ......................................... 6-30
6.10.4 Adding a New User ..................................................................................................... 6-30
6.10.5 Modifying Passwords, Privileges for an Existing User ................................................ 6-32
6.10.6 Removing a User from the Security System ............................................................... 6-33
6.11 Viewing / Modifying Application Parameters ........................................................................... 6-33
6.12 Viewing Other Parameters You Have Already Defined .......................................................... 6-34
6.13 Viewing the OpenBSI Journal File .......................................................................................... 6-35
6.14 Defining a BSAP Network ....................................................................................................... 6-36
x Contents Issued Nov-2016
OpenBSI Utilities Manual
6.14.1 Activating the Network Wizard .................................................................................... 6-36
6.14.2 Navigating Between Pages of the Network Wizard .................................................... 6-37
6.14.3 Network Wizard: Step 1 of 2 ....................................................................................... 6-38
6.14.4 Network Wizard: Step 2 of 2 ....................................................................................... 6-39
6.14.5 Viewing BSAP Network Parameters ........................................................................... 6-39
6.15 Defining an IP Network ........................................................................................................... 6-41
6.15.1 Activating the Network Wizard .................................................................................... 6-41
6.15.2 Navigating Between Pages of the Network Wizard .................................................... 6-41
6.15.3 Network Wizard: Step 1 of 2 ....................................................................................... 6-42
6.15.4 Network Wizard: Step 2 of 2 ....................................................................................... 6-43
6.15.5 Viewing IP Network Parameters ................................................................................. 6-43
6.16 Defining RTUs (BSAP) ............................................................................................................ 6-44
6.16.1 Activating the RTU Wizard .......................................................................................... 6-45
6.16.2 Navigating Between Pages of the RTU Wizard .......................................................... 6-46
6.16.3 RTU Wizard: Step 1 of 3 ............................................................................................. 6-46
6.16.4 RTU Wizard: Step 2 of 3 ............................................................................................. 6-47
6.16.5 RTU Wizard: Step 3 of 3 ............................................................................................. 6-51
6.16.6 Modifying BSAP RTU Parameters .............................................................................. 6-52
6.17 Defining RTUs (IP) .................................................................................................................. 6-54
6.17.1 Activating the RTU Wizard .......................................................................................... 6-54
6.17.2 Navigating Between Pages of the RTU Wizard .......................................................... 6-55
6.17.3 RTU Wizard: Step 1 of 4 ............................................................................................. 6-55
6.17.4 RTU Wizard: Step 2 of 4 ............................................................................................. 6-57
6.17.5 RTU Wizard: Step 3 of 4 ............................................................................................. 6-59
6.17.6 RTU Wizard: Step 4 of 4 ............................................................................................. 6-61
6.17.7 Modifying IP RTU Parameters .................................................................................... 6-63
6.18 Defining a Communication Line for a BSAP Network ............................................................. 6-65
6.18.1 Activating the Comm Line Wizard ............................................................................... 6-65
6.18.2 Navigating Between Pages of the Comm Line Wizard ............................................... 6-66
6.18.3 Comm Line Wizard: Step 1 ......................................................................................... 6-66
6.18.4 Comm Line Wizard: Step 2 (BSAP and/or EBSAP Lines) ........................................ 6-67
6.18.5 Comm Line Wizard: Step 2 (Local BSAP Line) ........................................................... 6-70
6.18.6 Switching the Local Line to a Different RTU ............................................................... 6-72
6.18.7 Specifying Dial Parameters (NetView or LocalView) .................................................. 6-72
6.18.8 Forcing a Hang-up of the Dial-up Line ........................................................................ 6-74
6.18.9 Comm Line Wizard: Step 3 (Enable Port Poll Control - OPTIONAL) .......................... 6-74
6.18.10 Exiting the Comm Line Wizard ................................................................................. 6-76
6.18.11 Modifying the Characteristics of a BSAP Comm Line .............................................. 6-76
6.18.12 Modifying the Characteristics of a Local BSAP Line ................................................ 6-78
6.19 Defining a Communication Line for an IP Network ................................................................. 6-79
6.19.1 Activating the Comm Line Wizard ............................................................................... 6-79
6.19.2 Comm Line Wizard: Step 1 of 2 .................................................................................. 6-80
6.19.3 Comm Line Wizard: Step 2 of 2 .................................................................................. 6-81
6.19.4 Advanced Parameters ................................................................................................. 6-84
6.19.5 Navigating Between Pages of the Comm Line Wizard ............................................... 6-85
6.19.6 Exiting the Comm Line Wizard .................................................................................... 6-85
6.19.7 Modifying the Characteristics of an IP Comm Line ..................................................... 6-85
6.20 Deleting A Communication Line, RTU, or Network ................................................................. 6-88
6.21 Monitoring the Status of OpenBSI Communications ............................................................... 6-88
Issued Nov-2016 Contents xi
OpenBSI Utilities Manual
6.21.1 Accessing the Monitor Windows ................................................................................. 6-88
6.21.2 Using the RTU Summary Display ............................................................................... 6-89
6.21.3 Resetting the RTU Statistics: ...................................................................................... 6-90
6.21.4 Getting More Detailed Information about an RTU ...................................................... 6-90
6.21.5 Using the RTU Details Display .................................................................................... 6-91
6.21.6 Using the RTU Details Display for a BSAP/EBSAP RTU: .......................................... 6-91
6.21.7 Using the RTU Details Display for an IP RTU: ........................................................... 6-94
6.21.8 Using the Message Exchange Summary Display ....................................................... 6-96
6.21.9 Resetting the Message Exchange Statistics: .............................................................. 6-97
6.21.10 Getting More Detailed Information about a Message Exchange ............................. 6-97
6.21.11 Using the Message Exchange Details Display ........................................................ 6-97
6.21.12 Buffer Usage Summary Display ............................................................................... 6-99
6.21.13 Resetting the Buffer Statistics: ............................................................................... 6-100
6.21.14 Other Ways to View Communication Statistics ...................................................... 6-101
6.22 RTU Communication Status Checking ................................................................................. 6-102
6.22.1 Activating / De-activating RTU Communication Status Checking ............................ 6-102
6.23 Searching For A Particular RTU in A Large Network ............................................................ 6-103
6.24 Starting Other Programs From Within NetView .................................................................... 6-104
6.25 Documenting Your Network Configuration ............................................................................ 6-106
6.26 Setting up Proxy Access ....................................................................................................... 6-107
6.26.1 Steps for Setting up Proxy Access ............................................................................ 6-108
6.26.2 Steps for Setting up Proxy Direct Access (IP RTU's ONLY) .................................... 6-108
6.26.3 Creating and Exporting a Proxy File ......................................................................... 6-109
6.26.4 Importing a Proxy File ............................................................................................... 6-110
6.27 Sending a Time Synch/NRT (TS/NRT) Message ................................................................. 6-110
6.28 Deleting Archive Files and/or Audit Records ....................................................................... 6-111
6.28.1 Deleting Historical Data ............................................................................................ 6-111
Chapter 7 – Using the Downloaders 7-1
7.1 Starting the ACCOL Downloader .............................................................................................. 7-1
7.2 Downloading to a Single Network 3000 Node .......................................................................... 7-3
7.3 Downloading to a Group of Network 3000 Nodes .................................................................... 7-3
7.4 Downloading to a ControlWave-series Node: ........................................................................... 7-6
7.4.1 Before You Begin .......................................................................................................... 7-6
7.4.2 Starting the ControlWave Downloader.......................................................................... 7-9
7.4.3 Using the ControlWave Downloader ........................................................................... 7-10
7.4.4 Creating Download Scripts for Batch Downloading of ControlWave Controllers ....... 7-11
7.4.5 Running the ControlWave Downloader from the Command Line ............................... 7-13
Chapter 8 – Using DataView 8-1
8.1 Starting DataView ..................................................................................................................... 8-2
8.2 Using the Tool Bar within DataView .......................................................................................... 8-3
8.3 Using the Select New Node Dialog Box, Signing on to a Node ................................................ 8-3
Using the Select New Node Dialog Box .................................................................................. 8-4
Using the Sign On Dialog Box .................................................................................................. 8-4
Configuring Automatic DataView Sign-On ............................................................................... 8-5
8.4 Printing the Entries in the Current DataView Window .............................................................. 8-6
8.5 Exporting Data Entries to the Windows Clipboard ................................................................. 8-6
8.6 Conducting a Signal Search ..................................................................................................... 8-7
Starting the Signal Search ........................................................................................................ 8-7
Notes about STRING variables .............................................................................................. 8-12
Saving Search Criteria ............................................................................................................ 8-13
Retrieving Search Criteria ...................................................................................................... 8-13
Altering Search Criteria .......................................................................................................... 8-13
8.7 Viewing Entries in a Signal Window ........................................................................................ 8-14
xii Contents Issued Nov-2016
OpenBSI Utilities Manual
Changing Signal Values in the Signal Window ...................................................................... 8-15
Changing Signal Inhibit/Enable Bits in the Signal Window .................................................... 8-16
Changing the Floating Point Format of Data in the Signal Window ....................................... 8-16
8.8 Displaying a Remote Signal List ............................................................................................. 8-17
Selecting a Different Remote Signal List ................................................................................ 8-17
Changing Remote List Signal Values, Altering Inhibit/Enable Bits ......................................... 8-18
8.9 Creating and Using DataView Lists ........................................................................................ 8-18
Creating a DataView List ........................................................................................................ 8-18
Collecting Live Data into the DataView List ............................................................................ 8-19
Saving the DataView List ........................................................................................................ 8-19
Viewing a Previously Saved DataView List ............................................................................ 8-19
8.10 Creating and Using Recipes ................................................................................................... 8-19
Creating a Recipe ................................................................................................................... 8-20
To View/Modify an Existing Recipe File ................................................................................. 8-21
To Update Signals in the Controller with the Recipe Values .................................................. 8-21
To Read the Current Signal Values From the Controller Into the Recipe Window ................ 8-21
To Cancel Unsaved Modifications to the Recipe Values........................................................ 8-21
Changing the Floating Point Format of Data in the Recipe Window ...................................... 8-21
8.11 Viewing Data for a Single Signal ............................................................................................. 8-22
Acknowledging an Alarm ........................................................................................................ 8-23
8.12 Viewing Data Arrays ................................................................................................................ 8-23
Changing Values in the Data Array ........................................................................................ 8-24
Toggling the Time/Value Format ............................................................................................ 8-25
Keeping Column 1 Visible While Scrolling Through the Array ............................................... 8-25
Calling Up a Different Data Array ........................................................................................... 8-25
Changing the Floating Point Format ....................................................................................... 8-25
8.13 Viewing Audit Trail Records .................................................................................................... 8-26
8.14 Viewing Archive Data Files ..................................................................................................... 8-28
Keeping Column 1 Visible While Scrolling Through the Archive File ..................................... 8-29
Calling Up a Different Archive File .......................................................................................... 8-29
Changing the Floating Point Format ....................................................................................... 8-29
Restrictions on Archive File Size ............................................................................................ 8-29
Chapter 9 – Using the Communication Statistics Tool 9-1
9.1 Starting the Remote Communication Statistics Tool ................................................................. 9-2
9.2 Using the Select New Node Dialog Box, Signing On to a Node ............................................... 9-3
Using the Select New Node Dialog Box ................................................................................... 9-4
Using the Sign On Dialog Box .................................................................................................. 9-4
Configuring Automatic Sign-On ................................................................................................ 9-5
9.3 Buffer Usage Statistics Window (Network 3000 ONLY) ........................................................... 9-6
Indications of Buffer Shortages ................................................................................................ 9-7
Resetting the Min, Max Counts ................................................................................................ 9-7
Crash Block Statistics Window ................................................................................................. 9-7
9.4 Port Summary Statistics Window .............................................................................................. 9-8
Port Detail Statistics Window .................................................................................................... 9-9
Master/Expanded Addressing Master Port Statistics ............................................................. 9-10
Slave, Pseudo-Slave, Pseudo-Slave with Alarms, Serial CFE or VSAT Slave Port Statistics9-11
Custom Port Statistics (ControlWave-series Users ONLY) .................................................... 9-11
RIOR Master Port Statistics .................................................................................................... 9-12
RIOR Slave Port Statistics ...................................................................................................... 9-13
LIU Master Port Statistics ....................................................................................................... 9-14
LIU Slave Port Statistics ......................................................................................................... 9-15
Communications Front End (CFE) AUX Port Statistics .......................................................... 9-17
Internet Protocol (IP) Port Statistics ....................................................................................... 9-17
9.5 Custom PROM Information Window (Network 3000) ............................................................. 9-19
9.6 Version Information Window ................................................................................................... 9-21
9.7 Node Routing Table Window .................................................................................................. 9-23
9.8 Internet Protocol (IP) Statistics Window .................................................................................. 9-24
Issued Nov-2016 Contents xiii
OpenBSI Utilities Manual
IP Statistics Decription ............................................................................................................ 9-25
ICMP Statistics Description .................................................................................................... 9-26
UDP Statistics Description ...................................................................................................... 9-27
IBP Statistics Description ....................................................................................................... 9-28
9.9 Printing the Entries in the Current Window ............................................................................. 9-29
9.10 Exporting Data Entries to the Windows® Clipboard ................................................................ 9-29
Chapter 10 – Using Signal Writer 10-1
10.1 Starting Signal Writer .............................................................................................................. 10-1
10.2 Setting Up Signal Writer Configuration Parameters ............................................................... 10-2
10.3 Signal Writer File Formats ....................................................................................................... 10-3
10.3.1 Write Signal File .......................................................................................................... 10-3
10.3.2 Write List File .............................................................................................................. 10-3
Chapter 11 – Using Alarm Router 11-1
11.1 Starting Alarm Router .............................................................................................................. 11-2
11.2 How is the Alarm Router Configured? .................................................................................... 11-2
11.3 Specifying Initialization Parameters and Choosing DLLs ....................................................... 11-3
11.3.1 Parameter Configuration Page ................................................................................... 11-3
DLL Configuration Page ......................................................................................................... 11-5
11.3.2 Activating A DLL .......................................................................................................... 11-5
11.3.3 Removing A DLL From the Configured DLLs List Box ............................................... 11-5
11.3.4 Installing An All New DLL ............................................................................................ 11-6
11.3.5 Removing A DLL from the Available DLLs List Box .................................................... 11-6
11.4 Configuring Alarm Router DLLs .............................................................................................. 11-6
11.4.1 ALMTEXT DLL ............................................................................................................ 11-7
11.4.2 ALMWORX DLL .......................................................................................................... 11-8
11.5 Viewing Alarms in the Alarm Window ................................................................................... 11-10
11.5.1 Acknowledging Selected Alarms in the Alarm Window ............................................ 11-13
11.5.2 Changing the Font Used in the Alarm, Error, and Monitor Windows ........................ 11-14
11.6 Viewing Status Messages in the Monitor Window ................................................................ 11-15
11.6.1 List of Monitor Window Status Messages and Their Meanings ................................ 11-16
11.7 Viewing Error Messages in the Error Window ...................................................................... 11-17
11.7.1 Clearing Errors from the Error Window ..................................................................... 11-18
11.7.2 List of Error Messages and Their Meanings ............................................................. 11-18
11.8 Starting Alarm Processing..................................................................................................... 11-19
11.9 Stopping Alarm Processing ................................................................................................... 11-19
11.10Printing Entries in Alarm Router Windows ............................................................................ 11-19
11.11Shutting Down the Alarm Router .......................................................................................... 11-19
11.12Editing the Configuration Files .............................................................................................. 11-19
11.12.1 ALARMRTR.INI File ............................................................................................... 11-20
11.12.2 ALMTEXT.INI File .................................................................................................. 11-20
11.12.3 ALMWRX.INI File ................................................................................................... 11-20
11.13Program Messages ............................................................................................................... 11-21
Chapter 12 – Using the Signal Extractor 12-1
12.1 Starting the Signal Extractor ................................................................................................... 12-1
12.2 Signal Extract Options for Network 3000 Nodes .................................................................... 12-2
12.2.1 Standard File Format – Network 3000 Series Controllers .......................................... 12-3
12.2.2 Altered File Formats – Network 3000 / ControlWave ................................................. 12-5
12.3 Signal Extract Options for ControlWave ................................................................................. 12-7
12.4 Standard File Format – ControlWave Controllers ................................................................. 12-11
12.4.1 Example 1 - Standard Format ................................................................................... 12-12
12.5 Running Signal Extractor from the DOS Command Line ...................................................... 12-13
12.6 Troubleshooting Tips for Using Signal Extractor with ControlWave ..................................... 12-14
xiv Contents Issued Nov-2016
OpenBSI Utilities Manual
Chapter 13 – Using the Data Array Save / Restore Utility 13-1
13.1 Saving the Contents of a Single Array to Disk ........................................................................ 13-1
13.2 Restoring the Values in a Single Array from a Previously Saved File .................................... 13-3
13.3 Creating a Script File to Save Multiple Arrays from One or More RTUs................................. 13-3
13.3.1 Creating a Script File ................................................................................................... 13-3
13.3.2 Executing the Script File to Save Multiple Arrays to Disk Files .................................. 13-5
13.4 Executing a Script to Restore Multiple Arrays from Previously Saved Disk Files ................... 13-6
13.5 Running a Script from the Command Line .............................................................................. 13-6
Chapter 14– Using the Network Troubleshooting Wizard 14-1
14.1 Before you Begin ..................................................................................................................... 14-1
14.2 Starting the Network Troubleshooting Wizard ........................................................................ 14-2
14.3 Testing a BSAP Network or BSAP Sub-Network .................................................................... 14-3
14.3.1 Step 1. Select the BSAP Network (or BSAP Sub-network) ........................................ 14-3
14.3.2 Step 2. - Specify the Branch of the Network you want to test ..................................... 14-4
14.3.3 Step 3. - Choose Which Tests to Perform .................................................................. 14-5
14.3.4 Setting Test Options: ................................................................................................... 14-7
14.3.5 Step 4. – Run the Tests .............................................................................................. 14-8
14.3.6 Saving the Results of the Network Tests .................................................................. 14-10
14.4 Interpreting the Messages Appearing in the Results Window .............................................. 14-10
14.4.1 Status Messages ....................................................................................................... 14-10
14.4.2 Error Messages ......................................................................................................... 14-11
14.4.3 Warning Messages ................................................................................................... 14-13
14.5 Making Changes at the OpenBSI Workstation (NHP) .......................................................... 14-17
14.5.1 Changing the Number of Buffers allocated at the OpenBSI Workstation ................. 14-17
14.5.2 Changing the Number of Wait Packets allocated in the OpenBSI Workstation ........ 14-18
14.5.3 Changing the RTU Message Timeout Used by OpenBSI ......................................... 14-18
14.5.4 Changing OpenBSI’s baud rate, poll period, slave address range, and link level timeout14-
20
14.6 Making Changes in the Network 3000 series node .............................................................. 14-22
14.6.1 Changing the Number of Buffers in a Network 3000 series node ............................. 14-22
14.6.2 Changing the Baud Rate of a Port in a Network 3000 Node .................................... 14-23
14.6.3 Changing the Link Level Timeout, and range of Slave addresses for a Master Port in a
Network 3000 node .............................................................................................................. 14-25
14.6.4 Changing the Poll Period of a Port in a Network 3000 Node .................................... 14-26
14.7 Making Changes in the ControlWave series node ................................................................ 14-29
14.7.1 Specifying the Baud rate and (for Master Ports only) the range of Slave node Addresses
14-29
14.7.2 Changing Poll Periods and the Link Level Timeout in a ControlWave Node ............ 14-30
14.8 Some Notes about Setting Immediate Response Delays ..................................................... 14-32
Appendix A – Error and Status Messages A-1
Appendix B – NETDEF File Format B-1
Appendix C – Keyboard Shortcuts C-1
Appendix D – Modem and Radio Configuration Tips D-1
Appendix E – Initialization Files E-1
Appendix F – Signal View ActiveX Controls F-1
Appendix G – Redirecting BSAP Messages through TCP/IP G-1
Appendix H – Defining Backup Communication Lines H-1
Appendix I – Port Arbitrator I-1
Appendix J – Using the System Firmware Downloader J-1
J.2 Requirements for Using the System Firmware Downloader ............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................. J-1
J.3 Starting the System Firmware Downloader ..................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... J-2
to a Single Controller J-3
J-8
Appendix K – Interpreting AUDIT Messages K-1
Issued Nov-2016 Contents xv
OpenBSI Utilities Manual
Addendum to D5081, D5087: Starting Web Pages or Programs using LocalView
(*.LVG) Files ADD-1
Index IND-1
xvi Contents Issued Nov-2016
OpenBSI Utilities Manual
Chapter 1 – Introduction – What is OpenBSI?
The Open Bristol System Interface (OpenBSI) allows your PC to
communicate with a BSAP or IP network of ControlWave and/or
Network 3000-series controllers (RTUs). This chapter introduces some
of the concepts and terminology used in OpenBSI.
In This Chapter
1.1 RTUs and NHPs .............................................................................. 1-4
1.1.1 Remote Terminal Units (RTUs): ........................................... 1-4
1.1.2 Network Host PC (NHP) ....................................................... 1-4
1.2 Supported Network Configurations .................................................. 1-5
1.3 BSAP Networks ............................................................................... 1-5
1.3.1 Local and Global Addressing ............................................... 1-5
1.3.2 Network Levels ..................................................................... 1-5
1.3.3 Supported Communication Methods in BSAP ..................... 1-6
1.3.4 Peer-to-Peer Communication ............................................... 1-6
1.3.5 Variations on Standard BSAP – EBSAP .............................. 1-7
1.3.6 Variations on Standard BSAP – BSAP Local Line ............... 1-7
1.4 IP Networks .................................................................................... 1-10
1.4.1 Applications Using IP ......................................................... 1-10
1.4.2 Differences between IP Nodes and Other RTUs ............... 1-11
1.4.3 Controllers That Support IP ................................................ 1-12
Format of IP Addresses ................................................................. 1-13
Meaning of IP Address Components ............................................. 1-13
Rules for Local Addressing Schemes ............................................ 1-14
Sub-net masks determine which nodes are reachable from
a given node ..................................................................... 1-15
1.4.4 Guidelines for Choosing Addresses in a Private Network . 1-17
1.4.5 IP Network Variations – Connecting Two Networks with a Single
Router ............................................................................... 1-18
1.4.6 IP Network Variations - Using Multiple Routers (Gateways) and
RIP for a Fault Tolerant Connection ................................. 1-22
1.4.7 IP Network Variations - Using Multiple Routers (Gateways)
without RIP........................................................................ 1-22
1.5 IP Network Security Protocols (CHAP and PAP) on PPP Links .... 1-24
1.5.1 Challenge Handshaking Authentication Protocol (CHAP) . 1-24
1.5.2 Password Authentication Protocol (PAP) ........................... 1-27
1.6 Mixed Networks (Both BSAP and IP nodes) ................................. 1-29
OpenBSI also includes a suite of programs known as the OpenBSI
utilities that interact with the network to allow you to:
Download ControlWave Designer projects and web pages to
ControlWave series RTUs.
Download ACCOL load files to Network 3000-series RTUs.
Collect and display data from the RTUs.
Monitor and control OpenBSI communications.
SCADA applications, such as OpenEnterprise, use OpenBSI
communications, and data files generated by OpenBSI utilities, to
Issued Nov-2016 Introduction 1-1
OpenBSI Utilities Manual
access the network in order to display and report information from field
instrumentation about a running process. You can then use this
information to interact with the network and your process.
Figure 1-1. OpenBSI Architecture
You access the OpenBSI utilities from the Start Programs menu on the
PC. Table 1-1 provides a brief description of each utility.
Table 1-1. OpenBSI Utilities
Icon Utility Description
NetView starts OpenBSI communications and allows you to
define details about how OpenBSI should work. It includes a
series of software “wizards” to help you specify
characteristics of the communication network, as well as the
remote process controllers (RTUs) which make up the
network.
NetView allows you to communicate with controllers in
standard BSAP networks, in EBSAP networks, and in
Internet Protocol (IP) networks. It also lets you specify
system directory and file locations. NetView allows you to
make on-line changes to the system configuration, and also
helps you monitor the “health” of OpenBSI communications.
See Chapter 6 – Using NetView.
The ACCOL Downloader transfers a linked ACCOL load file
(*.ACL) from the PC to a running Network 3000-series RTU.
The 1131 Downloader transfers web pages (HTML) and
ControlWave Designer projects to ControlWave series RTUs.
See Chapter 7 - Using the Downloader .
1-2 Introduction Issued Nov-2016
Icon Utility Description
DataView collects and displays several types of process
data from a controller, including signal values, data array
values, signal lists, archive data, and audit trail information.
In addition, it lets you search for signals based on various
criteria.
See Chapter 8 - Using DataView.
Remote Communication Statistics Tool allows you to
monitor OpenBSI communication from the RTU end. It
provides details on buffer usage, communication ports, and
custom protocols.
See Chapter 9 - Using the Remote Communication Statistics
Tool .
LocalView communicates locally with an RTU, and, for
certain controllers, also allows field upgrades of system
firmware. LocalView also lets you configure cold download
parameters and Internet Protocol (IP) addresses for 386EX
Protected Mode RTUs and ControlWave RTUs.
See Chapter 5 – Using LocalView.
OpenBSI Utilities Manual
Alarm Router collects alarm data from the network and
displays it in a window for you to view. It also exports the
alarm data to OpenEnterprise or other SCADA packages
which provide alarm management capabilities.
See Chapter 11 – Using Alarm Router.
Signal Writer reads ASCII files containing signal values, and
writes those values to corresponding signals or signal lists in
the RTU. SigWrite scans for such files at a user-definable
interval.
See Chapter 10 - Using Signal Writer.
Signal Extractor reads an ACCOL Object (*.ACO) file or
ControlWave Designer MWT file and generates an ASCII text
file containing information about all global, alarm, and report
by exception (RBE) signals defined in the file. Other userspecific applications use this file to construct a database.
See Chapter 12 - Using the Signal Extractor.
Database Config Utility allows you to modify database
portions of the OpenBSI 3.1 (or newer) Network Definition
Files offline. This provides an alternative to using NetView to
make modifications. Note: You can only modify existing
components; you cannot add or delete items.
See Appendix B.
Issued Nov-2016 Introduction 1-3
OpenBSI Utilities Manual
1.1 RTUs and NHPs
Icon Utility Description
Data Array Save / Restore Utility allows you to collect data
arrays from an RTU and then store them in disk file(s) at the
OpenBSI workstation. You can retrieve the file for a particular
array, at a later time, to restore the original array values from
the file into the array at the RTU.
See Chapter 13- Using the Data Array Save / Restore Utility
for details.
In addition to the standard set of utilities, just described, there are other
utilities, available as separate kits which provide capabilities for
scheduled data collection and file export such as the Harvester. See the
OpenBSI Harvester Manual (document# D5120) for details.
For purposes of this discussion, a network refers to one or more RTUs
connected using communication line(s) to a Network Host PC (NHP)
running OpenBSI.
1.1.1 Remote Terminal Units (RTUs):
Controllers are generically referred to in OpenBSI software by the term
RTU (Remote Terminal Unit); we use the term controller and RTU
interchangeably in this manual.
OpenBSI supports the ControlWave series of RTUs, as well as the older
Network 3000 series (3305, 3308, 3310, 3330, 3335, 3530-xx).
Field instrumentation devices (pressure transmitters, temperature
transmitters, level transmitters, electrical contacts, etc.) provide data
input/output to the controller (RTU) through the controller's process I/O
boards. The control strategy/load program executing in the controller
accesses this data to perform measurement and control tasks, tailored
specifically for your application (e.g. pipeline monitoring, pump
control, industrial automation, etc.).
Each RTU serves as a node in the network, and communicates with
other RTUs and OpenBSI workstations through its communication
ports. You can also configure an RTU to communicate with certain
third-party devices (PLCs, etc.) or networks though the use of a custom
communication protocol.
1.1.2 Network Host PC (NHP)
The term Network Host PC (NHP) refers to any PC workstation
running OpenBSI Version 3.0 or newer software. Typically, you
connect RTUs to it (so it serves as the host for those RTUs). You use
NetView (described in Chapter 6) to define the RTUs in the NHP’s
Network Definition (NETDEF) files. Any other NHP can only gain
1-4 Introduction Issued Nov-2016
access to these RTUs if this NHP allows it. The other NHP does not
need the address of the RTU it wants to communicate with; it only
needs to know the address of the NHP which is hosting the RTU, and
the RTU's name.
An OpenBSI workstation without attached RTUs though still considered
an NHP, serves as a proxy workstation. A proxy workstation contacts
other NHP(s) which do have attached RTUs, and requests proxy access
to those RTUs. Depending upon the type of network configuration, you
configure the proxy access as either direct to the RTU or only through
the RTU’s NHP.
In addition to running OpenBSI, each NHP typically also runs some
form of supervisory control and data acquisition (SCADA) or human
machine interface (HMI) software to display data collected from RTUs
for an operator. OpenEnterprise is the most common SCADA/HMI
package used with OpenBSI.
1.2 Supported Network Configurations
OpenBSI supports the following basic network configurations:
OpenBSI Utilities Manual
1.3 BSAP Networks
1.3.1 Local and Global Addressing
1.3.2 Network Levels
BSAP Networks
IP Network(s)
Mixed Network (mixture of IP and BSAP)
OpenBSI and all of the RTUs listed previously can communicate using
the BSAP protocol. For advanced users who want to see a full
description of BSAP, see the Network 3000 Communications
Application Programmer’s Reference (document# D4052).
Based on its location in the network, you use NetView to assign a local
address to each RTU in a BSAP network. The local address is an
integer from 1 to 127 and NetView stores it as 7 bits. NetView also
generates a 15-bit global address based on the local address. The local
address you configure in NetView must match the local address
hardware switch setting (or configuration parameter) set at the RTU.
BSAP networks use a hierarchical structure of 1 to 6 levels. You define
this hierarchy in NetView. Figure 1-2 shows an example of a 3-level
network.
Each RTU (node) serves as a “master” to the nodes connected
immediately below it in the network, and as a “slave” to a single master
on the level immediately above it. No single master node can have more
than 127 slave nodes. Note: NetView may impose additional
restrictions on the network size based on limitations of the 15 bit global
Issued Nov-2016 Introduction 1-5
OpenBSI Utilities Manual
address.
A network master (which in OpenBSI is always the NHP) sits at the top
of the network, and polls top-level nodes (nodes on level 1) for data.
Each top-level node is a master to the nodes connected to it on level 2,
and the level 2 nodes are masters to the nodes connected to them on
level 3, and so on.
Figure 1-2. Network Levels
Data from the lowest level of the network passes from slave to master to
slave to master etc. until it reaches the network master (NHP). At the
NHP, you access the data using various OpenBSI utilities and SCADA
software.
The level on which a node resides indicates the number of
communication lines traversed to reach the network master. For
example, a node on level 2 must send/receive data through two separate
communication lines to reach the network master.
Note: Certain types of RTUs, for example, the 3308, can only serve as
terminal nodes, i.e. they cannot serve as a master to slave nodes
connected to them on a lower level.
1.3.3 Supported Communication Methods in BSAP
In BSAP, communication lines typically use direct cable connections,
however, if your application requires it, you can use dial-up modems,
radios, or even satellite links.
1.3.4 Peer-to-Peer Communication
1-6 Introduction Issued Nov-2016
From a given node, direct peer-to-peer communication using
Client/Server function blocks is only possible to its master node, any
connected slave nodes, and any siblings (nodes on the same level which
N
D
A
N
F
p
share the same master). If you require communication to any node not in
these categories, you must route messages up using Client/Server
function blocks at each individual level of the network, until they reach
either the network master, or a master which is a sibling to another
master which can route the message down, using more Client/Server
function blocks at each level, until it reaches the desired node. Note:
etwork 3000 RTUs use ACCOL Master/Slave modules instead of
Client/Server function blocks.
1.3.5 Variations on Standard BSAP – EBSAP
OpenBSI Utilities Manual
Expanded node addressing (also known as “Expanded BSAP” or just
EBSAP) operates identically to BSAP, except that it allows a single
master to reference more than 127 slave nodes. EBSAP requires that
network level 1 consist of “virtual nodes”, and that the actual slave
nodes reside on level 2. See more information on EBSAP in Chapter 6,
and in the Expanded Node Addressing sections of the ControlWave
esigner Programmer’s Handbook (document# D5125) and the
CCOL II Reference Manual (document# D4044).
1.3.6 Variations on Standard BSAP – BSAP Local Line
BSAP Local Line
(for connecting a
laptop at lower
levels of the
network)
ormally, in a BSAP network, the OpenBSI workstation resides at the
top of the network (level 0). In addition to that workstation, you can
optionally plug a laptop PC running OpenBSI directly into a lower level
RTU's pseudo-slave port, and still retain the capability to connect with
other RTUs in the same BSAP network. During system debugging and
checkout this helps isolate a portion of the network and allows you to
communicate only with nodes in that portion.
You may also find the BSAP local line useful if you visit a BSAP RTU
that resides in a geographically remote location, with respect to the
control room containing the NHP. By plugging a laptop running
OpenBSI with a BSAP local line defined, you can, if your configuration
allows it, view other portions of the network.
igure 1-3 shows a typical use of the BSAP local line plugged into the
seudo slave port of an RTU. By default, the BSAP local line allows
communication only with the locally attached RTU, and its slave RTUs
(shown in the oval). When configuring the BSAP local line, you can
enable communication with other RTUs as well.
Issued Nov-2016 Introduction 1-7
OpenBSI Utilities Manual
Figure 1-3. BSAP Local Line for Network Access at lower levels of the network
BSAP Local Line
(Alternate
Emergency
Communication
Line)
You can also use BSAP local lines to establish an alternate emergency
communication connection to an RTU for use during a failure of the
normal communication connection. You can use this to connect to any
RTU configured with a slave, VSAT slave, pseudo slave, or pseudo
slave with alarms port and an appropriate connection medium. (For this
alternate connection, typically you use a dedicated modem configured at
each end for dial-up operation; however, you could also use cables or
radios.)
You use the BSAP local line in various scenarios in which the regular
communication connection fails, and an operator can manually activate
the alternate connection. Here is a typical example:
In Figure 1-4 an OpenBSI workstation normally uses a serial cable
connection to communicate with a single RTU. That RTU serves as the
top-level node of a BSAP network (or BSAP sub-network). All of the
RTUs in the BSAP network have dial-up modems. Using the BSAP
auto-dial feature, and ACCOL logic, the top-level RTU periodically
establishes dial-up connections to collect data, one at a time, from each
of the lower-level RTUs; it then passes that data up to the OpenBSI
workstation.
1-8 Introduction Issued Nov-2016
OpenBSI Utilities Manual
p
Figure 1-4. Typical BSAP Network where top-level node dials lower
levels nodes
A mishap occurs (see Figure 1-5) disrupting communication with the
top-level RTU. Examples of mishaps include lightning strikes, cable
breakage, etc. Such a mishap not only prevents communication with the
top-level RTU, it also prevents the OpenBSI workstation from receiving
data from the lower level RTUs, since it normally achieves its
connection by receiving data that passes through the top-level RTU. An
operator, who notices the communication failure activates a BSAP local
line which bypasses the failed portion of the network, and one-at-a-time,
manually selects an RTU, initiates dialing, and collects data, just as the
failed RTU would have done. This allows communications to continue
until the disruption is tracked down and repaired.
Another possible application for BSAP local lines is to provide backup
communications with IP RTUs when an Ethernet communication line
fails. For Network 3000 RTUs the backup link must use a configured
seudo slave port or pseudo slave with alarms port in each RTU since
slave or VSAT slave ports cannot exist in the same ACCOL load as an
IP slave port.
Note: In any of these scenarios, communication traffic only proceeds
from one OpenBSI workstation to any particular RTU through one
communication line at any one time. For this reason, any RTU reachable
Issued Nov-2016 Introduction 1-9
OpenBSI Utilities Manual
p
p
by the configured BSAP local line continues to receive its
communication traffic via the BSAP local line, even after you repair
roblems affecting the regular communication line. Therefore, when the
regular communication line is ready to return to service, shut down the
BSAP local line to resume normal operation.
Figure 1-5. Using BSAP Local Line for Communication in an
Emergency where top-level node dials lower levels nodes
1.4 IP Networks
Internet Protocol (IP) is a standard communications protocol for data
transmission over a computer network. It also allows computers on
different networks to exchange information with one another.
Note: For a general reference on IP, see Internetworking with TCP/IP,
Volume I: Principles, Protocols, and Architecture by Douglas E.
Comer.
1.4.1 Applications Using IP
1-10 Introduction Issued Nov-2016
IP allows you to connect ControlWave/Network 3000 RTUs together
using Ethernet, a standard type of local area network (LAN)
originally developed by Xerox Corporation. IP nodes are RTUs which
support IP communication. IP nodes can also communicate using other
rotocols such as serial Point-to-Point Protocol (PPP).
OpenBSI Utilities Manual
Warning
communication between ControlWave or Network 3000 RTUs. The
normal, intended application is for a “closed circuit” internet (LAN)
of RTUs and workstations in a company plant or industrial site.
While, there is no built-in restriction against connecting an IP
network of these nodes to the world-wide Internet, remember that
any external IP connection (no matter what brand of RTUs and
software you use) poses potential risks.
Always change default passwords, as well as default UDP/TCP
socket numbers, to lessen the possibility that an unauthorized
person could access your internal company process control data.
While these security features help prevent accidental access by plant
personnel, do not consider them protection against intentional
malicious activity by a sophisticated intruder, i.e. professional
“hacker”. Consider purchasing commercially-available "firewall"
software to gain a further degree of protection against such
malicious intrusions.
1.4.2 Differences between IP Nodes and Other RTUs
We are discussing the Internet Protocol (IP) for use in
From the user's point of view, IP nodes differ primarily in the
configuration required for communications. In Network 3000 RTUs, for
example, you must configure an IP port inside the ACCOL load. You
configure characteristics of the port (baud rate, stop bits, etc.) using the
Flash Configuration Utility.
In LocalView you assign an IP address for each IP port on the IP node.
(We’ll discuss IP addresses in more detail, later.)
Networks using only IP nodes are somewhat different from standard
BSAP networks. There is no hierarchical structure enforced at the
network level. For certain applications, this has significant advantages
over BSAP, because all nodes in a given section of the network exist on
the same level; this simplifies peer-to-peer communication because you
don’t need more than a single pair of IP_Client / IP_Server modules to
get a message from one node to any other node because all nodes are
“siblings” on the same level (see Figure 1-6.)
Note: There is no concept of “polling” in IP networks.
Network Definition Files (NETDEF) at the Network Host PC (NHP)
hold Information on the IP addresses for a given section of the network.
You use NetView to create the NETDEF files.
Issued Nov-2016 Introduction 1-11
OpenBSI Utilities Manual
Figure 1-6. Typical IP Network Using Ethernet
If an IP node or an OpenBSI workstation needs to communicate with
another IP node or OpenBSI workstation, and it doesn't know the
address of the IP port for that node or workstation, it obtains the
necessary addresses and routing information from the NETDEF files at
the NHP.
1.4.3 Controllers That Support IP
The ControlWave series and two Network 3000-series RTUs (the
386EX Protected Mode DPC 3330 and DPC 3335 controllers with
PES03 / PEX03 or newer firmware and Ethernet hardware) support IP.
In addition to Ethernet, ControlWave controllers support serial IP
communications using the Point-to-Point Protocol (PPP).
1-12 Introduction Issued Nov-2016
OpenBSI Utilities Manual
p
f
F
Format of IP
Addresses
Each network connection from an IP node has a unique IP address
within the network. Remember that the system associates the IP address
with the network connection (IP port) on the node, not the node itself.
This potentially allows a single IP node more than one IP port, and
consequently, more than one IP address.
IP addresses consist of 32 bits (1's and 0's) divided up into 4 groups of 8
bits each. A period separates each group. You convert each group of 8
bits from binary to a decimal number from 0 to 255 (see ). The resulting
IP address is in dotted decimal notation.
Figure 1-7. IP Address Explanation
Meaning of IP
Address
Components
Each of the numbers in the address has a specific meaning. For our
urposes, the IP address consists of a common network portion for
each node in the network, and a unique local portion for each particular
node.
Assign addresses to be consistent with whatever conventions you
establish for your system. In addition, you must follow certain rules for
defining addresses – we discuss these later in this chapter.
You use the sub-net mask to define the specific meaning of each part o
the address. The sub-net mask consists of another set of 32 bits (which
you must convert to dotted decimal notation). Each bit in the sub-net
mask corresponds to a bit in the IP address. If you set a bit in the sub-net
mask to 1 (ON), then we assume the corresponding bit in the IP address
is part of the network portion of the IP address. The system ignores (or
“masks”) the network portion when it communicates to nodes within the
same network, because by definition, the network portions of the
addresses for all nodes in the same network are identical. We assume
any bit in the sub-net mask which is 0 (OFF) is part of the local
addressing scheme.
igure 1-8 shows the IP address and corresponding sub-net mask for an
IP address of 120.0.210.1 and a sub-net mask of 255.0.0.0.
Issued Nov-2016 Introduction 1-13
OpenBSI Utilities Manual
f
Rules for Local
Addressing
Schemes
Figure 1-8. Sub-net Mask Explanation
Once again, a “1” in the sub-net mask indicates that the corresponding
bit in the IP address bit belongs to the network portion of the address.
Because the first part of the IP address “01111000”. has a corresponding
sub-net mask of “11111111'”we know that “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 belong to the local portion of the address.
When you create your IP address, the network portion of the address
must appear first. For example, if the network portion is 200, you
cannot define an IP address as 0.200.14.1. The network portion must
appear first. This means that when you create the sub-net mask, the
masked portion (i.e. all 1's) must appear first.
The organization of the remaining bits follows any local
communications scheme you choose to devise, except that each group o
bits that represents something must be contiguous.
For example, let's say you “mask out” the first 16 bits to define the
network address, i.e. your sub-net mask is:
11111111 . 11111111 . 00000000 . 00000000
which in dotted decimal format is:
255 . 255 . 0 . 0
That leaves 16 bits (indicated by the 0's) for your local communications
scheme.
1-14 Introduction Issued Nov-2016
OpenBSI Utilities Manual
N
You might want to use the first eight bits to indicate a section or area
number for a section of your network. Eight bits allows you to define up
to 256 sections. You can use another 8 bits (remaining out of the 16
available) to indicate a node number, allowing up to 256 IP RTUs and
OpenBSI workstations in a given section (see Figure 1-9).
Figure 1-9. Sample IP Addressing Scheme
If you have a device (controller, or workstation) which will have
multiple IP ports, we recommend you exercise special care when
specifying the IP address and mask for each IP port to ensure that IP
communication functions according to your plan. For example, you
typically would want each IP port to sit on a unique IP network. This is
because having two or more IP ports of the same device on the same
network is not particularly useful, since only one of the ports will be
allowed to send messages out to the network; the other ports will only
be able to receive messages.
Sub-net masks
determine which
nodes are
reachable from a
given node
The previous sections cover the mechanics of creating IP addresses and
sub-net masks. Another aspect we must discuss is the importance of IP
addresses and subnet masks.
The IP address and sub-net mask defines the range of acceptable
addresses with which the node potentially communicates. For example,
if one node’s IP address is 4.3.2.1 and another node’s IP address is
100.100.0.1, there is no common network portion between the two
addresses. For that reason, these two nodes cannot communicate with
each other directly; they belong to different networks. Any messages
between these nodes must pass through one or more router computers.
For two nodes to communicate directly, the network portion of their
addresses (specified by the sub-net mask) must match exactly.
To illustrate this concept, look at Figure 1-10. The network shown has one
etwork Host PC (NHP) called NHP1, and three RTUs named
OAK_STREET, ELM_STREET, AND WALNUT_AVE.
Issued Nov-2016 Introduction 1-15
OpenBSI Utilities Manual
Figure 1-10. IP Network with Error in Sub-net Masks
Table 1-2, however, reveals a problem with the configured sub-net
masks.
Table 1-2. Explanations of IP Addresses and Masks
Node Name IP Address, Sub-net Mask
NHP1 IP ADR: 100.22.49.1
MASK: 255.255.255.0
WALNUT_AVE IP ADR: 100.22.49.178
MASK: 255.255.0.0
OAK_STREET IP ADR: 100.22.50.33
MASK: 255.255.0.0
ELM_STREET IP ADR: 100.22.51.14
MASK: 255.255.0.0
SW1-5 IP ADR: 100.22.49.1
MASK: 255.255.255.0
SW1-6 IP ADR: 100.22.49.178
MASK: 255.255.0.0
SW1-7 IP ADR: 100.22.50.33
MASK: 255.255.0.0
Mask Says This Node Can Send Messages
to All Nodes with These Addresses
100.22.49.yyy
where yyy is an integer from 0 to 255.
100.22.yyy.zzz
where yyy and zzz are integers from 0 to 255.
100.22.yyy.zzz
where yyy and zzz are integers from 0 to 255.
100.22.yyy.zzz
where yyy and zzz are integers from 0 to 255.
100.22.49.yyy
where yyy is an integer from 0 to 255.
100.22.yyy.zzz
where yyy and zzz are integers from 0 to 255.
100.22.yyy.zzz
where yyy and zzz are integers from 0 to 255.
SW1-8 IP ADR: 100.22.51.14
MASK: 255.255.0.0
SW1-9 IP ADR: 100.22.49.1
MASK: 255.255.255.0
1-16 Introduction Issued Nov-2016
100.22.yyy.zzz
where yyy and zzz are integers from 0 to 255.
100.22.49.yyy
where yyy is an integer from 0 to 255.
OpenBSI Utilities Manual
Node Name IP Address, Sub-net Mask
SW1-10 IP ADR: 100.22.49.178
MASK: 255.255.0.0
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.
There is a problem, however. NHP1’s sub-net mask specifies that it can
only send messages to nodes with addresses 100.22.49.nnn where nnn is
an integer from 0 to 255. Therefore, the only node it can send messages
to is WALNUT_AVE.
To remedy this situation, we need to change NHP1's sub-net mask to
255.255.0.0 so that it can also send messages to OAK_STREET and
ELM_STREET. See the corrected sub-net mask in Figure 1-11.
Mask Says This Node Can Send Messages
to All Nodes with These Addresses
100.22.yyy.zzz
where yyy and zzz are integers from 0 to 255.
Figure 1-11. IP Network with Corrected Sub-net Mask
1.4.4 Guidelines for Choosing Addresses in a Private Network
If you have a small network which you don’t plan to connect to the
world-wide Internet, your choice of IP addresses is largely unrestricted.
Even if you have no plans to connect your network to the global
Internet, however, the Internet Engineering Task Force recommends, as
per RFC 1918 (http://www.ietf.org/rfc/rfc1918.txt) that you assign IP
addresses for your private networks from the following ranges:
10.0.0.0 to 10.255.255.255
Issued Nov-2016 Introduction 1-17
OpenBSI Utilities Manual
172.16.0.0 to 172.31.255.255
192.168.0.0 to 192.168.255.255
Internet governing bodies set aside these particular ranges of Internet
addresses for private networks. Most Internet Service Providers (ISP)
recognize any messages coming from these addresses as messages from
private networks, and the ISPs filter them out. This helps avoid
addressing conflicts should an accidental connection occur between a
private network, and the global Internet.
Devices (e.g. RTUs, workstations) in our networks always use fixed IP
addresses. This causes certain complexities if you choose to use
Dynamic Host Configuration Protocol (DHCP) in your network.
Because DHCP assigns IP addresses dynamically, as needed, you must
examine your DHCP server to determine the addresses assigned for
each RTU or workstation, and then manually enter those addresses in
NetView. You should then specify the longest possible lease time for
the addresses, to help prevent the loss of a given address through a
device failure.
We also strongly recommend you configure the DHCP server to
permanently reserve the addresses for the RTUs. (To do this, associate
the addresses with RTU MAC addresses within the DHCP configuration
or use a totally different address range). Do the same when you
configure RAS servers or other machines designed to provide dynamic
addressing information. Otherwise, you might accidently use duplicate
IP addresses on your network.
1.4.5 IP Network Variations – Connecting Two Networks with a
Single Router
Figure 1-12 shows a typical OpenBSI network using IP. A Network
Host PC (NHP) and additional OpenBSI workstations sit on the same
network as the RTUs (IP nodes). They exist on the same sub-network,
and the addresses of all of the devices share the same range of IP
addresses.
1-18 Introduction Issued Nov-2016
OpenBSI Utilities Manual
Figure 1-12. Typical IP Network Using Ethernet
For small networks of up to a few hundred nodes this type of
configuration is fine. More complex network configurations are
possible, however. When you need many hundreds or even thousands of
nodes, or nodes in different geographical locations, the type of
configuration, shown above, may prove inadequate.
You may find yourself in a situation where, because of new system
requirements, devices on a self-contained existing network now need to
share data with devices from an entirely different network.
Imagine, for example, a natural gas field (Figure 1-13) with hundreds of
different RTUs and workstations that uses an address range beginning
with 10.87.1.x. which now, because of changing requirements, must
share data with another natural gas field full of controllers and
workstations. This other network, in a different location, uses an address
range beginning with 172.24.x.x. Because their current address ranges
are incompatible, you cannot easily combine these two networks into a
single network.
It might be impractical to try to assign new IP addresses to one group or
the other; - - there might not even be enough unused addresses available
for you to do that, or the man-hours required to physically re-program
the devices might be prohibitive.
Issued Nov-2016 Introduction 1-19
OpenBSI Utilities Manual
Figure 1-13. Two Separate IP Networks That Cannot Communicate with Each Other
You use a device called a router (also known as a gateway) in these
sorts of situations. See Figure 1-14.
1-20 Introduction Issued Nov-2016
OpenBSI Utilities Manual
Figure 1-14. Connecting Two Separate IP Networks with a Router
A router is a device which has multiple IP ports such that the router
belongs to more than one network. As part of each network, it takes
messages from devices in one network and routes them to devices in
another network. Typically, a router is a physical hardware device
specifically designed for message routing. Software implementations of
routers also exist.
Note: Because IP RTUs such as the DPC 3330, and ControlWave can
contain more than one IP port (and so can sit on more than one network)
the RTUs can actually serve as routers.
In our IP networks, one way you can specify a router is to designate it as
the default gateway. When you define a particular IP network, the
system automatically sends any message with a destination IP address
which lies outside the defined address range for that network to the
default gateway, i.e. the router. You define the default gateway from the
IP Parameters tab of the Flash Configuration utility.
Issued Nov-2016 Introduction 1-21
OpenBSI Utilities Manual
Figure 1-15 shows how to specify the default gateway address for
Network "A" and Network "B" controllers, respectively, in our example.
Both networks actually use the same device with two different IP ports
(one RTU sits on each of the two networks).
Default Gateway (G/W) is an address
where any message that cannot be
routed within the network will be sent.
All controllers in Network “A” have this
as their default gateway.
Figure 1-15. Defining an RTU as a Router
1.4.6 IP Network Variations - Using Multiple Routers (Gateways) and
RIP for a Fault Tolerant Connection
Beginning with ControlWave firmware CWP02.0, you can configure
multiple gateways (routers) to communicate using Routing Internet
Protocol (RIP). We discuss this subject in Chapter 5 in the description
of the IP Routes tab of the Flash Configuration Utility.
1.4.7 IP Network Variations - Using Multiple Routers (Gateways)
without RIP
The Routing Internet Protocol (RIP) we discuss in Chapter 5 only works
if the PC and all devices that serve as routers on the network can
send/receive RIP broadcasts. If they can’t, or, if you want to prevent the
network overhead of a protocol like RIP, you must find an alternative
method for using multiple routers.
All controllers in Network “B”
have this as their default gateway
One way you can configure this is through the ROUTE ADD command
from the DOS prompt of your PC.
In Figure 1-16, an OpenBSI workstation (PC) only accesses devices in
the 10.x.x.x network.
1-22 Introduction Issued Nov-2016
OpenBSI Utilities Manual
Figure 1-16. Separate Networks that Share a Router
Messages from the OpenBSI workstation cannot reach the other
172.16.x.x and 192.168.x.x networks. You can configure
communication using ROUTE ADD because those networks have a
connection (using routers) to the same network that the OpenBSI
workstation is on. The syntax for the command is:
ROUTE ADD aaa.bbb.ccc.ddd MASK eee.fff.ggg.hhh iii.jjj.kkk.lll
Where:
aaa.bbb.ccc.ddd is the destination address range you want to reach
eee.fff.ggg.hhh is the IP Mask for that address range
iii.jjj.kkk.lll is the address of the gateway or router which
provides a route to that destination.
For the figure, shown earlier, if you enter the following ROUTE ADD
commands at the DOS prompt, the PC allows messages traffic from the
OpenBSI workstation to the RTUs on the 172.16.x.x and 192.168.x.x
networks:
ROUTE ADD 172.16.0.0 MASK 255.255.0.0 10.0.1.200
ROUTE ADD 192.168.0.0 MASK 255.255.0.0 10.0.0.10
Issued Nov-2016 Introduction 1-23
OpenBSI Utilities Manual
1.5 IP Network Security Protocols (CHAP and PAP) Used on PPP Links
While not required, we strongly recommend you consider using one of
the two supported security protocols (PAP and CHAP) to help prevent
unauthorized access to your network by an intruder (hacker). Typically,
you should use CHAP since it is more secure.
The PAP and CHAP protocols operate in a client/server arrangement.
The ControlWave RTU operates as a CHAP (or PAP) server. Either a
ControlWave RTU or an OpenBSI workstation operates as a CHAP (or
PAP) client. Any client must always supply a valid username/password
combination to gain access to the server.
If the OpenBSI workstation is the client, you enter the username and
password directly in response to a login prompt. These must match one
of the username / password combinations stored in the ControlWave.
If a ControlWave RTU is the client, use the "Challenge Protocol
Default Username" field in the “Ports” page of the Flash Configuration
Utility to enter the username. The RTU automatically transmits the
username / password text string for that username in response to a login
prompt from the server.
Both of these security methods are similar at the user level. The
difference is in the underlying operation of the protocols.
1.5.1 Challenge Handshaking Authentication Protocol (CHAP)
The CHAP server (ControlWave) issues an encrypted challenge
message (which appears as a normal login prompt) to any CHAP client
(workstation or ControlWave) that requests access. CHAP encrypts the
supplied username and password according to a pre-defined secret
encryption key. The result is called the response message.
Even though the username / password combination for a particular user
does NOT change on each login attempt, the encrypted challenge and
response messages are different on each attempt. This helps prevent an
intruder from replicating the proper response message for a given
challenge message, either through trial and error or “brute force”
searches of all possible challenge messages.
Another characteristic of CHAP is that even after the client logs in,
subsequent challenge / response transactions occur to verify that the
connection is still with a valid user.
1-24 Introduction Issued Nov-2016
OpenBSI Utilities Manual
Example 1 - In this first CHAP example, the CHAP client is a PC
workstation, and the CHAP Server is a ControlWave RTU.
Figure 1-17. CHAP – Workstation to Controller
Issued Nov-2016 Introduction 1-25
OpenBSI Utilities Manual
Example 2 - The second CHAP example is very similar, except in this
case, the CHAP client is another ControlWave RTU. For this reason,
you configure a username/password combination (default IP user) and
store it in FLASH memory. You also configure a Challenge Protocol
Default Username on the IP parameters page of the Flash Configuration
Utility, to reference the default IP user.
Figure 1-18. CHAP – Controller to Controller
1-26 Introduction Issued Nov-2016
1.5.2 Password Authentication Protocol (PAP)
PAP requires a client requesting access to provide a username and
password, similar to CHAP. PAP is a simpler method of protection,
however, that has certain characteristics which make it less secure than
CHAP.
PAP allows clients to send passwords as clear “plain text” unencrypted
strings of characters. This could allow an unauthorized person to
intercept a password message, and then subsequently use the password
to gain access.
PAP also has no safeguards against repeated attempts to log in. For
example, an intruder using trial and error to “guess” a password, or
someone using software which performs a “brute force” search of all
possible passwords could gain access.
Example 1 - In the first PAP example, the PAP client is a PC
workstation, and the PAP Server is a ControlWave RTU.
OpenBSI Utilities Manual
Figure 1-19. PAP – Workstation to Controller
Issued Nov-2016 Introduction 1-27
OpenBSI Utilities Manual
Example 2 - The second PAP example is very similar, except in this
case, the PAP client is another ControlWave RTU. For this reason, you
configure a username/password combination (default IP user) and store
it in FLASH memory. You also configure a Challenge Protocol Default
Username, on the IP parameters page of the Flash Configuration Utility,
to reference the default IP user.
Figure 1-20. PAP – Controller to Controller
Further Information
For further information on PAP and CHAP, see these documents, both
of which are available at www.ietf.org.
PPP Authentication Protocols by Brian Lloyd and William
Simpson, Daydreamer Computer Systems Consulting Services, RFC
1334, October, 1992.
The MD5 Message-Digest Algorithm by Ronald Rivest, MIT
Laboratory for Computer Science, and RSA Data Security Inc., RFC
1321, April, 1992.
1-28 Introduction Issued Nov-2016
1.6 Mixed Networks (Both BSAP and IP nodes)
You can configure multiple IP networks for any Network Host PC
(NHP). In addition to IP network(s), you can also define multiple BSAP
networks, immediately below the NHP. The NHP serves as the BSAP
network master computer.
You can also create a BSAP sub-network underneath an IP node. In
this case, the IP node must be the only BSAP Level 1 node, and the
NHP is still the Network Master.
These configurations are useful, for example, if you want to add some
IP RTUs to an existing network of BSAP nodes.
Figure 1-21 shows a typical configuration which mixes both IP nodes
and BSAP network(s). The BSAP node shown on the left hand side,
under the IP node, is a small BSAP sub-network which includes only
one node. The large grouping of BSAP nodes on the right is a BSAP
network.
OpenBSI Utilities Manual
Figure 1-21. Mixed Network – IP and BSAP
Issued Nov-2016 Introduction 1-29
This page is intentionally left blank
OpenBSI Utilities Manual
Chapter 2 – Installing OpenBSI
This chapter discusses the hardware and software requirements for
OpenBSI installation, installation instructions, and software registration.
In This Chapter
2.1 Hardware and Software Requirements ..................................................... 2-2
2.1.1 Controllers used with OpenBSI ................................................. 2-2
2.1.2 Recommended Hardware/Software for the OpenBSI Workstation:
................................................................................................... 2-2
2.2 Installing the OpenBSI Utilities .................................................................. 2-3
2.3 Registering Your Software ....................................................................... 2-10
2.3.1 How do I Register My Software? ............................................. 2-10
2.4 How to Transfer a License from One PC to another PC ......................... 2-17
2.4.1 Using the software… ............................................................... 2-22
2.5 Using OpenBSI with Newer Microsoft® Windows Operating Systems ... 2-22
2.5.1 Which OpenBSI Features are affected? ................................. 2-23
2.5.2 How do I make these applications work properly with Windows?2-23
What is a Firewall? ............................................................................. 2-23
2.6 Using OpenBSI with Microsoft® Windows XP Service Pack 2 ............... 2-24
2.6.1 Reconfiguring the Windows XP Firewall ................................. 2-24
2.6.2 Disabling the Windows XP Firewall ......................................... 2-24
2.6.3 Making Object Server an Exception to the Windows XP Firewall2-24
2.6.4 Add Ports for DCOM and RTRSERVC for the XP firewall ...... 2-26
2.6.5 Add Ports for the Bristol IP Driver (BSIPDRV) for the XP firewall2-28
2.6.6 Reconfiguring the DCOM Software for the XP firewall ........... 2-29
2.7 Using OpenBSI with Microsoft® Windows 2008 Server .......................... 2-34
2.7.1 Reconfiguring the Windows 2008 Server Firewall .................. 2-34
2.7.2 Disabling the Windows 2008 Server Firewall .......................... 2-34
2.7.3 Making Object Server an Exception to the Windows 2008 Server
Firewall .................................................................................... 2-35
2.7.4 Add Ports for DCOM and RTRSERVC for the Windows 2008
Firewall .................................................................................... 2-37
2.7.5 Add Ports for the Bristol IP Driver (BSIPDRV) for the Windows 2008
Server Firewall ........................................................................ 2-39
2.7.6 Reconfiguring the DCOM Software for the Windows 2008 Server
Firewall .................................................................................... 2-41
2.8 Using OpenBSI with Microsoft® Windows 7 ........................................... 2-47
2.8.1 Reconfiguring the Windows 7 Firewall .................................... 2-47
2.8.2 Disabling the Windows 7 Firewall ........................................... 2-47
2.8.3 Making Object Server an Exception to the Windows 7 Firewall2-47
2.8.4 Add Ports for DCOM and RTRSERVC for the Windows 7 Firewall
................................................................................................. 2-56
2.8.5 Add Ports for the Bristol IP Driver (BSIPDRV) for the Windows 7
Firewall .................................................................................... 2-57
2.8.6 Reconfiguring the DCOM Software for the Windows 7 Firewall2-59
2.9 Using OpenBSI with Microsoft® Windows 10 Professional .................... 2-59
2.9.1 Reconfiguring the Windows 10 Firewall .................................. 2-59
2.9.2 Disabling the Windows 10 Firewall ......................................... 2-59
2.9.3 Making Object Server an Exception to the Windows 10 Firewall2-60
2.9.4 Add Ports for DCOM and RTRSERVC for the Windows 10 Firewall
................................................................................................. 2-67
2.9.5 Add Ports for the Bristol IP Driver (BSIPDRV) for the Windows 10
Firewall .................................................................................... 2-68
2.9.6 Reconfiguring the DCOM Software for the Windows 10 Firewall2-70
2.10 Using OpenBSI with Microsoft® Windows 2012 Server .......................... 2-70
Issued Nov-2016 Installation 2-1
OpenBSI Utilities Manual
2.10.1 Reconfiguring the Windows 2012 Server Firewall .................. 2-70
2.10.2 Disabling the Windows 2012 Server Firewall .......................... 2-70
2.10.3 Making Object Server an Exception to the Windows 2012 Server
Firewall .................................................................................... 2-71
2.10.4 Add Ports for DCOM and RTRSERVC for the Windows 2012 Server
Firewall .................................................................................... 2-80
2.10.5 Add Ports for the Bristol IP Driver (BSIPDRV) for the Windows 2012
Server Firewall ........................................................................ 2-81
2.10.6 Reconfiguring the DCOM Software for the Windows 2012 Server
Firewall .................................................................................... 2-83
2.11 Recommendations for Using OpenBSI ActiveX Controls ........................ 2-83
2.1 Hardware and Software Requirements
OpenBSI requires a suitable PC workstation, and collects data from
ControlWave and/or Network 3000 controllers.
2.1.1 Controllers used with OpenBSI
OpenBSI requires a network of ControlWave and/or Network 3000series controllers (RTUs). OpenBSI functions with any ControlWave
RTUs as well as any Network 3000 RTU with released firmware created
after 1994.
2.1.2 Recommended Hardware/Software for the OpenBSI
Workstation:
To run OpenBSI, your PC workstation must meet the following
minimum system requirements:
1 GHz processor
at least 200 MB free disk space for use by OpenBSI
512 MB RAM (more recommended)
CD-ROM drive
VGA Monitor (minimum 256 colors 800x600). Optimal screen
resolution for OpenBSI web pages is 1024 x 768.
Mouse
Communication cable(s) to connect the PC to the RTU network
Microsoft® Windows® 2008 Server, Windows® 7.0 Professional,
Windows® 10 Professional, or Windows® 2012 Server. OpenBSI
supports both 32-bit and 64-bit operating systems. We
recommend you install the latest available service pack for your
operating system.
Microsoft® Windows® 7.0 Enterprise is not supported.
Note: Emerson only tests OpenBSI on the following platforms:
Windows 7.0 Professional, Windows 10 Professional, and
Windows™ 2008 Server including both dual core, and dual-core
dual-processor computers.
Microsoft® Internet Explorer Version 5 or newer (Required for
ControlWave web pages).
2-2 Installation Issued Nov-2016
OpenBSI Utilities Manual
Note: For older OpenBSI versions, if you use Microsoft® Windows XP
Service Pack 2 (or newer), you must change default operating
system settings for certain OpenBSI features to work. Please see
the Using OpenBSI with Microsoft® Windows XP Service Pack 2
notes at the end of this chapter for details.
2.2 Installing the OpenBSI Utilities
We recommend you shut down all other programs before you begin to
install OpenBSI. OpenBSI includes several different packages – which
packages you choose to install depends on your application. You must
register some packages to continue using them after the 60-day trial
period expires.
Caution
If you install over an existi ng v ersi on of Open BSI, an d y ou pr evio usly
added other programs or data to the default OpenBSI installation folder
(\Program Files\Bristol\OpenBSI\) or its sub-folders (ControlWave projects,
Sixnet I/O definitions, etc.) you must back them up prior to the OpenBSI
installation.
If you install OpenBSI Network Edition over an existing version of
OpenBSI, data in the \OpenBSI folder is automatically copied to the user
files area. The original data is left untouched. The default user files area is
\ProgramData\Bristol\OpenBSI. Note: Windows normally hides this folder.
If you install BSI_Config over an existing version of BSI_Config, the
installation leaves existing data files in the \OpenBSI area untouched and
BSI_Config continues to use the existing \OpenBSI area for new data files.
You cannot install OpenBSI Network Edition or BSI_Config on the same
PC as Field Tools s oft ware v ersi ons p rio r to 2.0. Fiel d To ols v e rsion 2.0
(and newer) can coexist on the same PC with OpenBSI Network Edition or
BSI_Config. You also cannot install OpenBSI Network Edition or
BSI_Config on the same PC with OpenEnterprise Version 3.1 or newer.
Beginning with OpenBSI 5.8, th e older OPC Server is not supported; use
Object Server instead. Once you install OpenBSI 5.8, any older version of
OPC Server on your PC ceases to function.
If you install OpenBSI on a different driv e from a prev ious inst allation, y ou
must uninstall the prev ious ver sion and edit the Win do ws system path
statement to remove the prev ious Op enBSI pa th refere nce, befo re you
install the new version.
If you use OpenBSI utilities in conjunction with a third-party humanmachine interface (HMI) package, you must remove any version of the
file BSI32.DLL from the installation directory of the third-party package,
and replace it with the newer version from the OpenBSI installation
directory. If you don’t remove the older version, OpenBSI will function
improperly. Although not recommended, if you install OpenBSI and the
third-party package in the same installation directory, install OpenBSI
after the third-party package to solve the BSI32.DLL problem.
You cannot install ControlWave Designer on the same PC on which you
have installed other KW products (for example MULTIPROG or another
product which incorporates MULTIPROG) or else you may encounter
Issued Nov-2016 Installation 2-3
OpenBSI Utilities Manual
licensing issues or other problems.
Please review the release notes (README.DOC, README.TXT) for any
late changes not included in this manual.
1. Log into the workstation with administrative privileges.
2. Insert the OpenBSI CD-ROM in your CD-ROM drive.
3. If your CD-ROM drive has autorun enabled, skip to the next step.
Otherwise, open a DOS prompt with administrative privileges, then
set the folder to the CD root directory, and run the same “open”
command that is in the autorun.inf file on the CD, for example
“demo32.exe openbsi.dbd”. When the CD browser screen appears,
choose the Install OpenBSI option.
4. A screen reminds you to close all other programs, and warns you
that older OpenBSI versions will be removed. Click Next. (See
Figure 2-1.)
Click Next
Figure 2-1. OpenBSI Installer - Welcome Screen
5. A license agreement screen opens (Figure 2-2). Review the
agreement, using the scroll bar to bring it into view. Click I accept
the terms of the license agreement to proceed. Then click Next.
2-4 Installation Issued Nov-2016
OpenBSI Utilities Manual
Click here, then click Next
Figure 2-2. OpenBSI Installer - License Agreement
6. On the next screen (Figure 2-3), you can specify the user files
folder. The system stores user files such as ControlWave projects,
ACCOL files, recipes, and network files in sub-folders of this folder.
Note: If User Account Control (UAC) is enabled in Windows, you
must have modify access to this folder. The default is
C:\ProgramData\Bristol\Openbsi. Use the default or use Browse
to specify a different user files folder. When finished click Next.
Note: You can use the OpenBSI Folders tab of the Advanced
Configuration tool to view/change the names of sub-folders of
the OpenBSI user files folder. See Appendix E for details.
Click Next
Figure 2-3. OpenBSI Installer – User File Folders
Issued Nov-2016 Installation 2-5
OpenBSI Utilities Manual
/
r
I
r
r
r
A
7. On the next screen, use the check-boxes to select whichever
package(s) you want to install.
Figure 2-4. OpenBSI Installer - Choose Packages
Table 2-1. OpenBSI Packages
Software Component Description
Network Edition:
NetView You use NetView to configure the OpenBSI
Workstation and start OpenBSI communications. This
selection also installs several other tools including
LocalView, DataView, Alarm Router, BSAP to IP
Redirector, Remote Communication Statistics Tool,
Data Array Utility, ACCOL and 1131 Downloaders,
Off-Line Database Configuration utility, Signal
Extractor, Signal Writer, OpenBSI DDE Server,
ValScan, ActiveX Controls, Web_BSI web pages.
Harvester You use the programs in this package to collec t array
archive and audit trail data, and export it to data
files. This package includes the OpenBSI Harveste
and the Data File Conversion Utility. For information
on the Harvester software see the OpenBS
Harvester Manual (document# D5120). NOTE: In
order to use the Harvester, you must also install
NetView.
Programming Software:
ACCOL Workbench Lets you create, edit, and d ebug ACCOL files used in
ControlWave Designer
with ACCOL III
a Network 3000 series RTU. See the ACCOL
Workbench User’s Manual (document# D4051) fo
details. In addition, the ACCOL Downloader and
LocalView programs are included.
This software lets you create, edit, and debug IEC
61131 projects for the ControlWave RTU. Fo
information on using ControlWave Designer, see
Getting Started with ControlWave Designe
(document# D5085). This selection also includes the
CCOL III Function Block Library, ACCOL Translator,
and the IEC 61131 Downloader.
2-6 Installation Issued Nov-2016
OpenBSI Utilities Manual
t
y
f
f
f
Virtual ControlWave The Virtual ControlWave includes a set of tools that
allows you to take real-time signals from the
OpenEnterprise Database and bring them into a
ControlWave Designer project. Once in ControlWave
Designer, you can create calculations using those
signals. Then you compile and downloa d the projec
into the Virtual ControlWave, where it runs like an
other project. The Virtual ControlWave then stores
results of the calculations back in the OpenEnterpr ise
Database.
Security Vision The Security Vision application is a package of
hardware and software which allows a ControlWa ve
RTU to store images from a remote security camera,
and make them available to operators back at the
OpenBSI Workstation.
Setup and Configuration
Utilities:
BSIConfig This free package includes web pages n ecessary for
Remote I/O Tools This package installs I/O Tools for configuring
Communications
Interfaces for Non-OE
Users:
ObjectServer The ObjectServer suite works with OpenBSI to
ObjectServer Database This uses OpenBSI communications to collect real-
ObjectServer Client This transfers data between the ObjectServer
WebToolkit This consists of a set of tools th at allow you to create
calibration and configuration of the 3530-series o
TeleFlow flow computers, correctors and recorders,
as well as the 3808 MVT Transmitter and the 4088B.
It also includes LocalView, Diagnostics, WINUOI, and
the ControlView file viewer utility. IMPORTANT: You
cannot install the standalone version o
BSIConfig on a PC that already has OpenBSI
Network Edition installed.
ControlWave Ethernet I/O. See the on-line help in the
Remote I/O Toolkit for information on how to use the
Remote I/O Tools.
provide OPC clients (such as an HMI package) with
real-time access to a network o
ControlWave/Network 3000 RTUs.
time and alarm data from the RTU ne twork and store
it in a database.
database and a third-party HMI that serves as an
OPC client.
a simple HMI using web pages. This HMI retrieves
and displays data from ObjectServer.
8. Once you make your choices, click Next.
Issued Nov-2016 Installation 2-7
OpenBSI Utilities Manual
9. This is your last opportunity to make any changes prior to starting
the installation. If you want to make changes, you can click Back to
go back to earlier pages. If you want to read the printed release notes
for this version of OpenBSI, check the View the Release Notes box.
(See Figure 2-5.)
10. If you are ready to perform the installation, click Install, and the
installation process starts. Be patient, as it may take several minutes
to install all of the different utilities, depending upon which you
choose.
Click Install
Figure 2-5. OpenBSI Installer – Ready to Install
11. When the installation completes, re-boot your computer when
prompted (see Figure 2-6). This must be done in order for OpenBSI
to function properly. If you choose not to re-boot now, you must do
so before running OpenBSI. Click Finish, and the installation will
be complete, and re-boot will proceed, if you chose to do it now.
2-8 Installation Issued Nov-2016
OpenBSI Utilities Manual
Click Finish
Figure 2-6. OpenBSI Installer – Installation Finished
After re-boot, an “OpenBSI Tools” menu selection is added to your
Windows Start Programs menu through which you can access the
various OpenBSI utilities. If you prefer, you can create Windows™
shortcuts to the tools to provide access through icons on the desktop.
See your Windows™ documentation for information on how to do this.
Issued Nov-2016 Installation 2-9
OpenBSI Utilities Manual
2.3 Registering Your Software
Upon initial installation, the OpenBSI software packages operate for a
60 day evaluation period. Each time you start the software the system
displays a reminder message telling you that the software is not
registered (see Figure 2-7), and shows you a count of the number of
days remaining in the trial period. During this trial period, you can
continue to run the software without registering by clicking OK.
At the conclusion of the 60-day evaluation period, the OpenBSI software
Caution
packages cease to function. You MUST register the software packages
in order to use them after 60 days. Do NOT attempt to set back the da te
on your computer in order to extend the evaluation period; doing so
disables the software and terminates the evaluation period.
Figure 2-7. Software Not Registered Message
2.3.1 How do I Register My Software?
1. Install the desired software package(s) on your computer as
described in Section 2.2. The computer must have an active Internet
connection.
Note: If this computer does not have an active Internet
connection, you will need access to a computer which does,
and you will need a USB thumb drive (or other method) to
transfer the license file between the Internet-connected
computer, and the computer on which you have installed the
software.
2. Start the License Manager software, on the computer containing the
newly installed software packages, using the sequence: Start >
Programs > Bristol Babcock Licensing> License Manager.
3. The License Manager examines your PC, and identifies in a list,
which OpenBSI software packages are installed on this computer
(see Figure 2-8). Any package that is not registered shows as Trial
in the State field. Click Create LRF to generate a License Request
File (*.LRF) and save the file on your PC. Leave the License
Manager session running.
Note: Make note of where on this computer you save the LRF file,
because you will need it later.
2-10 Installation Issued Nov-2016
OpenBSI Utilities Manual
This lists the software
packages currently
installed on this
computer.
Click Create
LRF
Figure 2-8. License Manager
4. Click Get Key, and your Internet browser brings you to the
Software Registration area of the Emerson Remote Automation
Solutions website. Alternatively, in your browser, go to:
http://www2.emersonprocess.com/en-
US/brands/remote/systems_and_software/supportnet/Pages/license_re
gistration.aspx
Note: If this computer does not have internet access, transfer the *.LRF
file you just created to a computer which does have internet
access. You might need to copy it to a CD, use a USB thumb
drive, or transfer it by other means. Once you load it onto the
other internet-capable computer, use the URL in step 4 to
proceed with the registration.
Issued Nov-2016 Installation 2-11
OpenBSI Utilities Manual
Figure 2-9. Software Registration Page on Website – Initial Appearance
5. Click CLICK HERE TO REGISTER.
Figure 2-10. Software Registration Page on Website – Expanded Appearance
6. Click the Enter your License Id and Password and click Sign-On.
Note: You can find the License Id and Password on a label affixed
to the outside of your OpenBSI CD-ROM package.
7. Now you have two options. You can view which licenses have been
purchased and are available for you to register, or you can skip that
step and proceed to register your software. To view the available
licenses, go to step 8. To register the software, skip to step 9.
Note: The Park option shown in Figure 2-11 does not apply to any
OpenBSI related products; use the transfer license option instead.
2-12 Installation Issued Nov-2016
OpenBSI Utilities Manual
Figure 2-11. Register or View Licenses
8. To view which software packages have been purchased for this
particular License Id number, as well as how many of those licenses
are already in use, click the View link. The View Software Licenses
page (Figure 2-12) opens. You may need to use the scroll bar to
locate the product you want to view.
Figure 2-12. View Software Licenses Web Page
Issued Nov-2016 Installation 2-13
OpenBSI Utilities Manual
r
r
t
Field Description
Product Name This displays the name of the software packages fo
which licenses have been purchased using you
Customer Id number. In addition to OpenBSI
packages other software products such as
OpenEnterprise packages are displayed.
Available This displays the number of licenses out of the total
number purchased which have not been registered
for use. If the Available number is 0, you canno
register a new copy of this particular package.
Quantity Ordered This displays the total number of licenses purchased
using this Customer Id number.
Clients If the particular package includes restrictions on the
number of I/O clients, that appears here.
I/O Points If the particular package includes restrictions on the
number of I/O points, that appears here.
9. To register your software, click the Register link. The Registration
Information page opens.
2-14 Installation Issued Nov-2016
OpenBSI Utilities Manual
Figure 2-13. Enter Your Information Web Page
10. Enter your name in the Your Name field, and your e-mail address in
both the E-mail Address and Verify E-Mail fields. Enter your
mailing address in the Company Address fields then scroll down to
specify your Country and specify your preferences about receiving
notifications of product updates, service packs, contract renewals,
and marketing announcements by e-mail.
11. Then use the Browse button to locate the license request file you
generated previously in Step 3. Finally, click Next. The Unlock
Software Licenses page opens.
Note: The website will send yo u an e-mail with an attached unlock
key file to the e-mail address you specify here.
12.
Click the Unlock checkbox for the product(s) you want to register,
then click Submit License Request to send the license request to
the website.
Issued Nov-2016 Installation 2-15
OpenBSI Utilities Manual
Figure 2-14. Submit License Request Web Page
13. If the license request is successful, the website generates a key file
you can use to unlock your software. Click Key file to download a
copy of the key file (see Figure 2-15). (The website also e-mails you
a copy of the key file at the e-mail address you entered in step 9.)
Note: If the computer which contains the locked software does not
have internet access, you need to transfer the key file back to that
computer to complete the registration process.
Your unlock request has completed successfully.
Please download, save and apply the Key file using the License Manager.
Key file
A copy of the Key file has also been emailed to
(your e-mail address here)
View
Figure 2-15. Download Key File Web Page
14. In order to complete the registration process, the key file you
received must reside on the PC containing the newly installed
software packages. Go back to the License Manager session you
started in Step 3. (If you shut the License Manager down, restart it
by clicking Start > Programs > Bristol Babcock Licensing>
License Manager.
2-16 Installation Issued Nov-2016
OpenBSI Utilities Manual
15. To apply the key file, click the Include Key button and specify the
location of the key file.
16. If the registration completes successfully, you will see the message
box in Figure 2-16; just click OK and you’re done. Reboot your PC
for the new licenses to be activated.
Figure 2-16. License Successfully Updated message box
2.4 How to Transfer a License from One PC to another PC
Occasionally, it may be necessary for you to transfer an OpenBSI
software license from one computer, to another computer. This might be
necessary, for example, if you are upgrading to a newer computer, and
want to shift your OpenBSI license to the newer computer, and remove
it from the older computer.
In this explanation, the computer which is giving up its license will be
referred to as the source computer and the new computer which will
receive the transferred license will be referred to as the destination
computer.
Note: In order to transfer the license, the license on the source
computer must already be registered, and the software must have
already been installed on the destination computer.
1. Start the License Manager software, on the destination computer,
using the sequence: Start > Programs > Bristol Babcock
Licensing> License Manager.
2. Select the unlicensed package you want to change from a trial /
demo package, into a licensed package, and generate an empty
transfer request file.
Note: The transfer request file you create must be read-write. It
cannot be a read-only file.
Issued Nov-2016 Installation 2-17
OpenBSI Utilities Manual
First, select the
unlicensed
package for
which you want
to obtain a
license for from
another
computer.
Then click Create
Transfer
Figure 2-17. Generate a License Transfer Request File
3. Answer Yes to the prompt. (See Figure 2-18.)
Click Yes.
Figure 2-18. Confirm Transfer Request message box
4. Save the empty transfer (*.XFR) file. (See Figure 2-19.)
2-18 Installation Issued Nov-2016
OpenBSI Utilities Manual
Click Save
to create the
empty
transfer file.
Figure 2-19. Save Transfer Request File
5. Click OK when the file is created.
Click OK.
Figure 2-20. XFR File Created Successfully
6. Copy the XFR File you just saved onto the source (licensed)
computer. You can transfer it via a USB thumb drive, e-mail, etc.
7. Start the License Manager software, on the destination computer,
using the sequence: Start > Programs > Bristol Babcock
Licensing> License Manager.
8. Now, you must transfer the license of the software package, into the
transfer (*.XFR) file you created in Step 5. In the License Manager,
select the license you want to transfer and click Transfer License.
9. Now locate the XFR file you created earlier and click Open.
Issued Nov-2016 Installation 2-19
OpenBSI Utilities Manual
Open the XFR file you created earlier
Figure 2-21. Open XFR File on Source Machine
10. When the License Manager completes the update of the XFR file,
click OK. You now have successfully removed the license from the
source computer, and stored it in a file. Notice now that the State
field in the License Manager on the source computer no longer
shows “Licensed” for this software package.
Click on
[OK]
Figure 2-22. License Transferred Into File
11. You can now copy the XFR file onto the destination computer. (You
can transfer it via a USB thumb drive, e-mail, etc.)
12. Once you copy the XFR file to the destination computer, you can
install, and complete the transfer. To do this, select the package
which needs to be licensed, then click Install Transfer. (See Figure
2-23.)
2-20 Installation Issued Nov-2016
OpenBSI Utilities Manual
Select the package
you want to license,
then click Install
Transfer
Figure 2-23. Install Transferred License
13. The License Manager prompts you to confirm you want to install the
transferred license. Click Yes. (See Figure 2-24.)
Figure 2-24. Confirm Transferred License
Issued Nov-2016 Installation 2-21
OpenBSI Utilities Manual
14. Specify the location of the updated XFR file on the destination
computer and click Open. This completes the transfer.
2.4.1 Using the software…
Most users can begin with one of the “Quickstart” chapters, listed
below.
Chapter 3 - Quickstart (OpenBSI BSAP Communication)
Chapter 4 - Quickstart (OpenBSI IP Communication)'
Detailed information on each option in NetView is included in Chapter
6 - Using NetView.
Information on programming configuration parameters at the controller
using the Flash Configuration utility is included in Chapter 5 - Using
LocalView.
Once the configuration activities described in these chapters are
complete, you can proceed to use the other tools (Downloader,
DataView, Signal Writer, etc.) The remaining chapters of this manual
describe these tools.
As you are becoming familiar with a particular utility, you should also
consult the Help Windows integrated with it. These are accessed from
the Help menu bar selection in each individual utility, or by pressing the
[F1] key.
Some utilities also include context-sensitive help, in
which you point at the item for which you need help.
Context-sensitive help is accessible through the icon
shown at left.
2.5 Using OpenBSI with Newer Microsoft® Windows Operating Systems
Microsoft® Windows operating systems in recent years (XP and newer)
include security enhancements designed to prevent unauthorized
communication with other computers. If you have installed these
operating systems on your computer, any application which Windows is
unfamiliar with, and performs communications, may either be
automatically prevented from working, or its operation may be
restricted by the Windows operating system.
Like any other communications application, these security
enhancements affect OpenBSI. Certain default Windows settings will
disable some OpenBSI features. In order to remedy this situation, these
OpenBSI application programs need to be identified for Windows, as
authorized communicators. Once this is done, OpenBSI is recognized by
Windows, and can operate normally.
2-22 Installation Issued Nov-2016
OpenBSI Utilities Manual
a
y
2.5.1 Which OpenBSI Features are affected?
Proxy communication – If your system incorporates proxy
OpenBSI Workstations, that is, OpenBSI Workstations that are not
Network Host PCs, but that nonetheless communicate with RTUs
through other OpenBSI Workstations, they will no longer
communicate, either directly, or indirectly.
Bristol IP Driver – BSIPDRV - If your system communicates with
controllers using IP, both IP communications and time
synchronization messages will be blocked by the firewall.
Object Server - This application uses OPC (OLE for Process
Control), an industry-standard communication method which is
disabled by the operating system upgrade.
ActiveX Controls– The OpenBSI ActiveX controls (used in web
pages, for example) will still operate; however, users are required to
perform extra steps to access them following the operating system
upgrade. In addition, certain items, such as grid controls for signal
lists, etc. may require a particular OpenBSI Service Pack, or
Microsoft® Windows patch to work correctly.
2.5.2 How do I make these applications work properly with
Windows?
In order for these OpenBSI applications to work properly again, you
need to:
Re-configure the Windows Firewall software (if you’re using it).
Re-configure the DCOM and RTRSERVC software on your
computer.
A firewall is either a software program or a hardware device, which
What is a
Firewall?
What is
DCOM?
blocks unauthorized communications. It is used to block malicious
communications (spam e-mail, viruses, hacker intrusions, etc.) In order
for communications to be allowed through the firewall, they must be
authorized. Windows operating systems have a built-in firewall, which,
beginning with Windows XP Service Pack 2, is turned ON by default.
DCOM stands for Distributed Component Object Model. It’s just
communication protocol that allows different appli cations to talk to
each other over networks. The Object Server requires DCOM in
order to function.
What is
RTRSERVC?
Issued Nov-2016 Installation 2-23
RTRSERVC is a router service that allows OpenBSI prox
communication.
OpenBSI Utilities Manual
The next several sections details steps you need to take to allow
OpenBSI applications to work with various Windows operating
systems.
2.6 Using OpenBSI with Microsoft® Windows XP Service Pack 2
For OpenBSI to function with XP Service Pack 2, you need to reconfigure the Windows Firewall software, and re-configure DCOM
software.
2.6.1 Reconfiguring the Windows XP Firewall
Reconfiguring the Windows XP Firewall involves either disabling it
(not recommended in most cases) or making certain OpenBSI
applications exceptions to the firewall, to let them through.
Note: Portions of these sections reproduced, with permission, from the
OPC™ Foundation white paper Using OPC via DCOM with
Microsoft Windows XP Service Pack 2 by Karl-Heinz
Deiretsbacher, Jim Luth, and Rashesh Mody 2004.
Note: If Object Server is currently running, you must shut it down
during this configuration.
2.6.2 Disabling the Windows XP Firewall
If the Windows XP Firewall is the only firewall protection you have, we
recommend you leave it enabled, and skip to Section 2.6.3. If, however,
you have a corporate firewall, already installed, and it is operating
correctly, you may decide that the Windows XP Firewall is
unnecessary. If this is the case, you can disable the Windows XP
firewall.
Only perform these next three steps if you have a separate corporate
Caution
firewall which renders the XP firewall unnecessary.
1. From the Windows™ Control Panel, double-click on Windows
Firewall.
2. On the General page of the Windows Firewall dialog box, select the
Off (not recommended) button, then click on OK.
3. Skip the remaining steps in this sub-section, and continue with the
section “Reconfiguring the DCOM Software.”
2.6.3 Making Object Server an Exception to the Windows XP Firewall
If you install Object Server, you need to grant it as an exception to the
Windows XP Firewall.
2-24 Installation Issued Nov-2016
OpenBSI Utilities Manual
1. From the Windows™ Control Panel, double-click Windows
Firewall.
2. On the Exceptions tab of the Windows Firewall dialog box, click
Add Program (see Figure 2-25.)
Click Add Program
Figure 2-25. Windows Firewall Exception tab
3. To add Object Server to the list of authorized communicators
through the Windows XP Firewall, choose Object Server’s OPC
server (BristolOPCServer.exe) from the list, or use the Browse
button to locate it. Select it, and then click OK.
Issued Nov-2016 Installation 2-25
OpenBSI Utilities Manual
Figure 2-26. Windows Firewall Add Program dialog box
2.6.4 Add Ports for DCOM and RTRSERVC for the XP firewall
In the previous section, we specified programs that the Firewall needed
to know about. Now we have to identify which ports these programs
use.
Note: When we say ports, we’re not talking about physical
communication ports; we’re talking about software connections
into the system.
To add the ports, follow these steps:
1. From the Exceptions tab of the Windows Firewall dialog box, click
Add Port.
2-26 Installation Issued Nov-2016
OpenBSI Utilities Manual
Click Add Port
Figure 2-27. Windows Firewall Add Port
2. First, you need to add the port for DCOM. In the Add Port dialog
box, enter DCOM for the port’s Name, 135 for the Port Number
and choose TCP. Then click OK.
Figure 2-28. Windows Firewall Add a Port dialog box
Issued Nov-2016 Installation 2-27
OpenBSI Utilities Manual
2.6.5 Add Ports for the Bristol IP Driver (BSIPDRV) for the XP
firewall
3. Now add the port for RTRSERVC. Click Add Port again, and in
the Add Port dialog box, enter rtrservc for the port’s Name, 1236
for the Port number and choose TCP. Then click OK.
Note: The reason we say “1236” is that “1236” is the default port
number used by RTRSERVC. That number is initially set in the
TCP Port Number for Router Process field of the IP
Parameters dialog box in NetView’s System Wizard. If you
originally set it to something different than 1236, you should use
that number here, instead of 1236.
This section is almost identical to Section 2.6.4. We are adding two
additional ports for the Bristol IP Driver (BSIPDRV). One is for the
driver itself, and the other is for Time Synchronization messages. The
main difference from the previous step is the port numbers and the port
type, which is UDP, instead of TCP.
1. From the Exceptions tab of the Windows Firewall dialog box, click
Add Port.
Click Add Port
Figure 2-29. Windows Firewall – Add Port for BSIPDRV
2. Add the first port for BSIPDRV. In the Add Port dialog box, enter
BSIPDRV for the port’s Name, 1234 for the Port Number and
choose UDP. Then click OK.
2-28 Installation Issued Nov-2016
OpenBSI Utilities Manual
Figure 2-30. Windows Firewall Add Port for BSIPDRV
3. Repeat Step 2 to add the second port for BSIPDRV except enter
1235 for the Port Number.
Note: Again, we’re saying “1234” and “1235” because those are the
default port numbers used by BSIPDRV. Those numbers are
initially set in the UDP Port Number for IP Driver and UDP
Port Number for Time Synch fields of the IP Parameters dialog
box in NetView’s System Wizard. If you originally set them to
something different than 1234 and 1235, you should use those
numbers here, instead.
2.6.6 Reconfiguring the DCOM Software for the XP firewall
You must reconfigure the DCOM software for the Object Server to
function correctly.
1. Click Start > Run.
2. Type DCOMCnfg in the Run dialog box and click OK. This opens
the Component Services page.
Issued Nov-2016 Installation 2-29
OpenBSI Utilities Manual
.
Type ‘DCOMCnfig’ then click [OK]
Figure 2-31. Run dialog box
First, click on ‘Component Services’
Then -click on the ‘My Computer’ icon,
and choose from the pop-up
menu.
right
“Properties”
Figure 2-32. Component Services page
3. In the Component Services page, locate Console Root in the file
tree of the left window pane.
4. Under Console Root, click Component Services to expand the
folder.
5. In the right window pane, right-click the My Computer icon, and
select Properties from the pop-up window. This opens the My
Computer Properties dialog box.
6. In the My Computer Properties dialog box, click the COM Security
tab.
2-30 Installation Issued Nov-2016
OpenBSI Utilities Manual
Click Edit
Limits
Figure 2-33. Access Permissions
7. In the “Access Permissions” box (top part of the page) click Edit
Limits.
8. In the Group or user names box (top part of the Access
Permissions dialog box) click the ANONYMOUS LOGIN icon.
Issued Nov-2016 Installation 2-31
OpenBSI Utilities Manual
Figure 2-34. Access Permissions dialog box
9. In the bottom part of the dialog box, select the Allow Local Access
and Remote Access permission items. They must be checked for
OPC to function.
10. Repeat this process for the Everyone icon.
11. Click OK and the My Computer Properties dialog box re-opens.
Click Edit Limits in the Launch and Activation Parameters (bottom
part of the dialog box).
2-32 Installation Issued Nov-2016
OpenBSI Utilities Manual
Click Edit
Limits
Figure 2-35. Launch and Activation Permissions
12. In the Launch and Activations Permissions box (bottom part of the
My Computer Properties COM Security tab) click Edit Limits.
13. In the Launch Permissions dialog box, click the Everyone icon in
the Group or user names box (top part of the dialog box).
Figure 2-36. Launch Permissions dialog box
14. In the bottom part of the dialog box, select the Allow permission
items for all the options shown (Local Launch, Remote Launch,
Local Activation, and Remote Activation.). It must be checked for
OPC to function.
Issued Nov-2016 Installation 2-33
OpenBSI Utilities Manual
C
hoose ‘Allow’ for all the items
Figure 2-37. Grant Permissions for Everyone
15. Click OK.
Note: If you are concerned about granting “everyone” these
permissions, where “everyone” in this context refers to every
user account on this computer, you can create a special group
with these permissions. To restrict it to only some users, you
should create a group of users called, for example, “OPC Users”,
and then give launch permissions only to the “OPC Users”
group, instead of “everyone.” In this case, you would substitute
“OPC Users” for “everyone” in these instructions.
2.7 Using OpenBSI with Microsoft® Windows 2008 Server
For OpenBSI to function with Windows 2008 Server you need to reconfigure the Windows Firewall software, and re-configure DCOM
software.
2.7.1 Reconfiguring the Windows 2008 Server Firewall
Reconfiguring the firewall involves either disabling it (not
recommended in most cases) or making certain OpenBSI applications
exceptions to the firewall, to let them through.
Note: If Object Server is currently running, you must shut it down
during this configuration.
2.7.2 Disabling the Windows 2008 Server Firewall
If the Windows firewall is the only firewall protection you have, we
recommend you leave it enabled, and skip to Section 2.7.3. If, however,
you have a corporate firewall, already installed, and it is operating
correctly, you may decide that the Windows firewall is unnecessary. If
this is the case, you can disable the Windows firewall.
Only perform these next four steps if you have a separate corporate
Caution
firewall which renders the Windows firewall unnecessary.
1. From the Windows™ Control Panel, double-click on Windows
Firewall.
2. Click on the Turn Windows Firewall on or off link.
2-34 Installation Issued Nov-2016
OpenBSI Utilities Manual
3. On the General page of the Windows Firewall dialog box, select the
Off button, then click on OK.
4. Skip the remaining steps in this sub-section, and continue with the
section “Reconfiguring the DCOM Software.”
2.7.3 Making Object Server an Exception to the Windows 2008
Server Firewall
If you install Object Server, you need to grant it as an exception to the
Windows Firewall.
1. From the Windows™ Control Panel, double-click Windows
Firewall.
Click here
Figure 2-38. Allow a Program Through the Firewall
2. Click Allow a program through Windows Firewall.
3. On the Exceptions tab of the Windows Firewall dialog box, click
Add Program (see Figure 2-39.)
Issued Nov-2016 Installation 2-35
OpenBSI Utilities Manual
Click Add Program
Figure 2-39. Windows Firewall Exception tab
4. To add Object Server to the list of authorized communicators
through the Windows Firewall, choose Bristol OPC Alarm & Event
Server (BristolOPCServer.exe) from the list, or use the Browse
button to locate it. Select it, and then click OK. Repeat this process
for Bristol OPC Data Access Server.
2-36 Installation Issued Nov-2016
OpenBSI Utilities Manual
Figure 2-40. Windows Firewall Add Program dialog box
2.7.4 Add Ports for DCOM and RTRSERVC for the Windows 2008
Firewall
In the previous section, we specified programs that the firewall needed
to know about. Now we have to identify which ports these programs
use.
Note: When we say ports, we’re not talking about physical
communication ports; we’re talking about software connections
into the system.
To add the ports, follow these steps:
1. From the Exceptions tab of the Windows Firewall dialog box, click
Add Port.
Issued Nov-2016 Installation 2-37
OpenBSI Utilities Manual
Click Add Port
Figure 2-41. Windows Firewall Add Port
2. First, you need to add the port for DCOM. In the Add Port dialog
box, enter DCOM for the port’s Name, 135 for the Port Number
and choose TCP. Then click OK.
2-38 Installation Issued Nov-2016
OpenBSI Utilities Manual
Figure 2-42. Windows Firewall Add a Port dialog box
3. Now add the port for RTRSERVC. Click Add Port again, and in
the Add Port dialog box, enter rtrservc for the port’s Name, 1236
for the Port number and choose TCP. Then click OK.
Note: The reason we say “1236” is that “1236” is the default port
number used by RTRSERVC. That number is initially set in the
TCP Port Number for Router Process field of the IP
Parameters dialog box in NetView’s System Wizard. If you
originally set it to something different than 1236, you should use
that number here, instead of 1236.
2.7.5 Add Ports for the Bristol IP Driver (BSIPDRV) for the Windows
2008 Server Firewall
This section is almost identical to Section 2.7.4. We are adding two
additional ports for the Bristol IP Driver (BSIPDRV). One is for the
driver itself, and the other is for Time Synchronization messages. The
main difference from the previous step is the port numbers and the port
type, which is UDP, instead of TCP.
1. From the Exceptions tab of the Windows Firewall dialog box, click
Add Port.
Issued Nov-2016 Installation 2-39
OpenBSI Utilities Manual
Click Add Port
Figure 2-43. Windows Firewall – Add Port for BSIPDRV
2. Add the first port for BSIPDRV. In the Add Port dialog box, enter
BSIPDRV for the port’s Name, 1234 for the Port Number and
choose UDP. Then click OK.
Figure 2-44. Windows Firewall Add Port for BSIPDRV
3. Repeat Step 2 to add the second port for BSIPDRV except enter
1235 for the Port Number.
2-40 Installation Issued Nov-2016
OpenBSI Utilities Manual
Note: Again, we’re saying “1234” and “1235” because those are the
default port numbers used by BSIPDRV. Those numbers are
initially set in the UDP Port Number for IP Driver and UDP
Port Number for Time Synch fields of the IP Parameters dialog
box in NetView’s System Wizard. If you originally set them to
something different than 1234 and 1235, you should use those
numbers here, instead.
2.7.6 Reconfiguring the DCOM Software for the Windows 2008
Server Firewall
You must reconfigure the DCOM software for the Object Server to
function correctly.
Note: This same procedure applies for Windows 7.
1. Click Start > Run.
2. Type DCOMCnfg in the Run dialog box and click OK. This opens
the Component Services page.
Type “DCOMCnfig” then click OK.
Figure 2-45. Run dialog box
Issued Nov-2016 Installation 2-41
OpenBSI Utilities Manual
Then right-click on the
“My Computer” icon, and
choose “Properties” from
the pop-up menu.
First, click on “Component Services”
Figure 2-46. Component Services page
3. In the Component Services page, locate Console Root in the file
tree of the left window pane.
4. Under Console Root, click Component Services to expand the
folder.
5. In the right window pane, right-click the My Computer icon, and
select Properties from the pop-up window. This opens the My
Computer Properties dialog box.
6. In the My Computer Properties dialog box, click the COM Security
tab.
2-42 Installation Issued Nov-2016
OpenBSI Utilities Manual
Click Edit
Limits
Figure 2-47. Access Permissions
7. In the “Access Permissions” box (top part of the page) click Edit
Limits.
8. In the Group or user names box (top part of the Access
Permissions dialog box) click the ANONYMOUS LOGIN icon.
Issued Nov-2016 Installation 2-43
OpenBSI Utilities Manual
Figure 2-48. Access Permissions dialog box
9. In the bottom part of the dialog box, select the Allow Local Access
and Remote Access permission items. They must be checked for
OPC to function.
10. Repeat this process for the Everyone icon.
11. Click OK and the My Computer Properties dialog box re-opens.
Click Edit Limits in the Launch and Activation Parameters (bottom
part of the dialog box).
2-44 Installation Issued Nov-2016
OpenBSI Utilities Manual
Click Edit
Limits
Figure 2-49. Launch and Activation Permissions
12. In the Launch Permissions dialog box, click the Everyone icon in
the Group or user names box (top part of the dialog box).
Issued Nov-2016 Installation 2-45
OpenBSI Utilities Manual
Click
“Allow”
for all the
items.
Figure 2-50. Grant Permissions for Everyone
13. In the bottom part of the dialog box, select the Allow permission
items for all the options shown (Local Launch, Remote Launch,
Local Activation, and Remote Activation.). It must be checked for
OPC to function.
14. Click OK.
Note: If you are concerned about granting “everyone” these
permissions, where “everyone” in this context refers to every
user account on this computer, you can create a special group
with these permissions. To restrict it to only some users, you
should create a group of users called, for example, “OPC Users”,
and then give launch permissions only to the “OPC Users”
group, instead of “everyone.” In this case, you would substitute
“OPC Users” for “everyone” in these instructions.
2-46 Installation Issued Nov-2016
OpenBSI Utilities Manual
2.8 Using OpenBSI with Microsoft® Windows 7
For OpenBSI to function with Windows 7 you need to re-configure the
Windows Firewall software, and re-configure DCOM software.
2.8.1 Reconfiguring the Windows 7 Firewall
Reconfiguring the firewall involves either disabling it (not
recommended in most cases) or making certain OpenBSI applications
exceptions to the firewall, to let them through.
Note: If Object Server is currently running, you must shut it down
during this configuration.
2.8.2 Disabling the Windows 7 Firewall
If the Windows firewall is the only firewall protection you have, we
recommend you leave it enabled, and skip to Section 2.8.3. If, however,
you have a corporate firewall, already installed, and it is operating
correctly, you may decide that the Windows firewall is unnecessary. If
this is the case, you can disable the Windows firewall.
Only perform these next four steps if you have a separate corporate
Caution
firewall which renders the Windows firewall unnecessary.
1. From the Windows™ Control Panel, double-click on Windows
Firewall.
2. Click on the Turn Windows Firewall on or off link.
3. On the General page of the Windows Firewall dialog box, select the
Off button, then click on OK.
4. Skip the remaining steps in this sub-section, and continue with the
section “Reconfiguring the DCOM Software.”
2.8.3 Making Object Server an Exception to the Windows 7 Firewall
If you install Object Server, you need to grant it as an exception to the
Windows Firewall.
1. From the Windows™ Control Panel, double-click Windows
Firewall.
Issued Nov-2016 Installation 2-47
OpenBSI Utilities Manual
Click here
Figure 2-51. Allow a Program Through the Firewall
2. Click Allow a program or feature through Windows Firewall.
3. In the Windows Firewall with Advanced Security page, double-click
on Inbound Rules.
Double-click
on “Inbound
Rules”
Figure 2-52. Defining an Inbound Rule
4. On the Inbound Rules page click New Rule.
Click “New Rule”
Figure 2-53. Defining a New Inbound Rule
2-48 Installation Issued Nov-2016
OpenBSI Utilities Manual
5. In the Rule Type page of the New Inbound Rule Wizard, click
Program. Then click Next.
Click “Program.”
Then click “Next.”
Figure 2-54. New Inbound Rule Wizard – Rule Type page
6. On the Program page (see Figure 2-55), you can add Object Server
to the list of authorized communicators through the Windows
Firewall. Click the Browse button next to the This Program Path
field to locate the Bristol OPC Server (BristolOPCServer.exe).
Issued Nov-2016 Installation 2-49
OpenBSI Utilities Manual
Figure 2-55. New Inbound Rule Wizard – Program page
7. Select BristolOPCServer.exe, as shown in Figure 2-56 then click
Open.
2-50 Installation Issued Nov-2016
OpenBSI Utilities Manual
Figure 2-56. Selecting BristolOPCServer
8. The path for the item you just selected shows in the This program
path field on the Program page of the New Inbound Rule Wizard
(Figure 2-57). Click Next.
Issued Nov-2016 Installation 2-51
OpenBSI Utilities Manual
Figure 2-57. Program Path for the Exception
2-52 Installation Issued Nov-2016
OpenBSI Utilities Manual
9. On the Action page of the New Inbound Rule Wizard, click Allow
the Connection. Then click Next.
Figure 2-58. Allowing the Connection
10. On the Profile page of the New Inbound Rule wizard, specify the
cases where the ObjectServer inbound rule applies.
Issued Nov-2016 Installation 2-53
OpenBSI Utilities Manual
Figure 2-59. Choosing Where the Exception Applies
11. On the Name page of the New Inbound Rule Wizard, specify a
Name for the rule, and optionally enter a description. Then click
Finish.
2-54 Installation Issued Nov-2016
Loading...