Contents

ii

iii

iv

About ???..........................................................................................................................................................5-99

v

vi

vii

viii

ix

x

xi

xii

xiii

Introduction

Scope of the Manual

This manual provides instructions for IP Gateway installation and operation, as well as detailed instructions for the setup of its configuration. In addition, this manual provides the user with an overview of the MOSCAD system including a few examples that show SCADA control centers and NFM Manager which are integrated into the MOSCAD system via the IP Gateway.

Additional applicable manuals are:

???MOSCAD Programming Toolbox, System Overview Manual, 68P02956C45

???MOSCAD Programming Toolbox, System Setup and Diagnostics Tools Manual, 68P02956C50

???MOSCAD Programming Toolbox, Application Programmer Manual, 68P02956C55

???MDLC Gateway for TCP/IP Application Programming Interface ??? User???s Manual, 68P02951C05

???MOSCAD NFM Manual, 68P02958C45

???MOSCAD RTU Service Manual, 68P02991G90

IP Gateway System and ToolBox Software Version Policy

The version numbers of the ToolBox and system software are updated according to additional features and improvements.

Compatibility (at source level) between the ToolBox and the IP Gateway is assured only if the version number of the ToolBox Software is later than the version number of the Gateway system software.

A version number is composed of two numbers, as in the following example: V1.61. The one- digit number to the left of the decimal point describes a major modification of the software, while the two-digit number to the right of the decimal point describes a minor modification.

In this manual, some headings of major subjects are marked by the following annotation:

??? Va.b.

For example, ??? V1.61 indicates that the marked subject is supported by a Gateway whose system software version number is at least 1.61.

1-1

Introduction

Introducing the IP Gateway

The IP Gateway for SCADA and NFM systems is a smart unit, based on the Motorola 68360 microprocessor and includes on-board memory, communication channels, indicator LEDs and other circuits. It provides the SCADA and NFM software with access to the MOSCAD system, based on the seven layers of the MDLC protocol, in order to exchange data with the RTUs. A typical example of the IP Gateway is shown in Figure 1-1; a SCADA control center is connected via the IP Gateway to a radio link of the MOSCAD system.

Your gateway into the

MOSCAD world

MDLC on Radio

MOSCAD

RTU

RTU

RTU

Figure 1-1: MOSCAD System with IP Gateway, General View

1-2

Introduction

A system with multiple vendors SCADA control center is shown in Figure 1-2. The MDLC communicates with any SCADA computer which supports the TCP/IP network (UNIX, VMS, Windows/NT, Windows/95, OS/2 etc.).

Ethernet

TCP/IP

RTU

RTU

RTU

Figure 1-2: IP Gateway with Multiple Vendors SCADA Control Center

The SCADA control center, which includes workstations and a SCADA computer, exchanges data with the MOSCAD system via the IP Gateway, which serves as a Gateway from the TCP/IP world to the MDLC world. There are many SCADA packages which already have the Gateway Interface driver implemented, some as direct access to the IP Gateway, and some as OPC server.

IP Gateway Applications

The IP Gateway uses the TCP/IP LAN Protocol for exchanging data application messages with the SCADA software. The IP Gateway API (Application Programming Interface) source library allows SCADA developers to quickly and easily connect to the MOSCAD world. The IP Gateway API, which is part of the IP Gateway product line, allows SCADA driver developers to quickly and easily build the IP Gateway Interface (driver), which serves as a communication interface with the MOSCAD world.

Data exchange between the SCADA (client) and the IP Gateway (server) is carried out using "peer -to-peer" communication over the LAN. The IP Gateway can support multiple connections that are initiated from multiple SCADA computers.

The implementation of the IP Gateway interface in the SCADA software allows the SCADA to perform the following:

???Poll a MOSCAD RTU in order to get data and COS (Change-of-State) events from the RTU tables.

1-3

Introduction

???Send commands to the MOSCAD RTU and download parameters to its local process.

???Send commands via broadcasts to any required group of RTUs.

???Download parameters (set-points) to the RTU local process.

???Receive spontaneous reports (by contention) from RTUs (both burst and event transmission).

???Receive time-tagged events logged in the RTUs (1 msec resolution).

???Adjust the RTU clocks (1 sec resolution).

???Synchronize the RTU clocks (1 msec resolution), using an external CPU with GPS.

???Support redundant IP Gateway configuration.

???Set the Gateway mode (Primary/Secondary).

???Retrieve Gateway status.

???Retrieve RTU links status.

MOSCAD NFM Overview

The MOSCAD NFM system provides communication providers with a solution for supervising and controlling the operation of conventional and trunked radio, analog and digital cellular, microwave radio and wireline telecommunication systems.

The MOSCAD NFM system provides the Network Management Center (NMC) with access to the communication and environmental devices and gives the operator and the system manager the tools needed to identify and fix faults within the communication system.

Figure 1-3 describes the general architecture of the MOSCAD NFM, which includes control center workstations and computers that exchange data with the IP Gateway, allowing the NMC to monitor and control non-SNMP devices at the communication sites.

1-4

Introduction

Ethernet

MOSCAD NFM RTU

Figure 1-3: General Architecture of the MOSCAD NFM System

The MOSCAD NFM via the IP Gateway allows the system to offer SNMP (Simple Network Management Protocol) connectivity, therefore providing a standard interface to a wide range of NMC platforms (such as HP/OpenView, SUN/Solstice, IBM/NetView etc.).

The MOSCAD Remote Terminal Unit (RTU) represents the Element Level of the network management model. It collects the various inputs, outputs and analog signals via a variety of input/output (I/O) modules. In addition, the MOSCAD RTU serially interfaces to communication devices (radio, cellular and telecommunication) and is able to emulate (speak) their ASCII based native protocol, allowing the MOSCAD to not only monitor alarms, but to configure and change parameters as well.

1-5

IP Gateway System Overview

SCADA System

The complete control system is comprised of the SCADA control center (or centers) communicating with MOSCAD RTUs over various communication links, such as:

The communication system is used for transmitting alarms, status and telemetry, calculated data diagnostics and error logging information from the MOSCAD RTUs to the central facility computer and vice versa. It is also used for downloading, monitoring and debugging the application program at the sites.

The system may be relatively simple, comprising several RTUs and a single control center, or a more complicated hierarchical system, where several sub-control-centers communicate with lower, parallel and higher hierarchies. The RTUs may also communicate with each other and/or with any other hierarchy in the system.

The MOSCAD system uses the MDLC protocol, based on the seven layers of the OSI model published by ISO, and adapted for SCADA communications. It provides network support, multiple logical channels per physical port, allowing each RTU to simultaneously run several communication sessions, such as data exchange, on-line monitoring, diagnostics, etc.

The MOSCAD system is supplied with a Toolbox, which is a software package that runs on an IBM PC (or compatible). All RTU functions such as configuration, database and process definition, downloading, monitoring, hardware and software diagnostics, etc. are defined by means of the MOSCAD Programming Toolbox.

Figure 2-1 describes a typical MOSCAD radio system. The IP Gateway includes one Ethernet port for connection to the SCADA computer and 3 serial ports for communicating via MDLC protocol to the MOSCAD devices. In this particular case, one MDLC port is connected to the MOSCAD Programming Toolbox and the second MDLC port is connected to a radio for communicating with the RTUs.

2-1

System Overview

Your gateway into the

MOSCAD world

MDLC on Radio

MOSCAD

RTU

RTU

RTU

Figure 2-1: SCADA Control Center with Radio-Based MOSCAD System

2-2

System Overview

The IP Gateway allows the SCADA center to conduct a large number of sessions via a large number of logical channels in spite of a single physical RS-232 port. The IP Gateway also serves as an MDLC router between the MOSCAD Programming Toolbox and RTUs.

The Toolbox may be connected either locally to an RTU or via the MDLC port of the IP Gateway to any RTU in the system. All programming and monitoring functions can be performed either locally or remotely.

Note: The MOSCAD Programming Toolbox that is connected locally to one of the RTUs in the system can service any other RTU in the system via the communication network.

Figure 2-2 describes multiple SCADA control centers which are connected to the IP Gateway via a 10 Mbps Ethernet LAN. In this case, multiple TCP/IP logical links are used for communicating with the IP Gateway, which is connected via multiple MOSCAD CPUs to multiple MDLC links (Radio link, Line link, Dial-up link etc.).

Multiple SCADA control centers can simultaneously perform multiple sessions with the IP Gateway in order to send commands and polling requests to the RTUs and to receive data and contention reports from the MOSCAD RTUs.

SCADA SCADA

Computer Computer

Work Stations

TCP/IP on Ethernet

Figure 2-2: SCADA Control Center with Multiple Links-Based MOSCAD System

2-3

System Overview

MDLC Over IP

MOSCAD RTUs and IP Gateways can use IP (Internet Protocol) technology to interface to advanced radio infrastructure (e.g. digital ASTRO IP conventional systems) and to standard private IP networks. Most benefits of the MDLC protocol are preserved. MDLC and IP networks can be integrated in the same system, as networking properties are preserved. MOSCAD MDLC applications need not be modified as the lower layers of the protocol support IP.

MDLC packets to be transmitted are enveloped inside IP datagrams and sent between remote RTUs or between an IP Gateway and an RTU.

An IP Gateway can act as a gateway between the field and the SCADA Central to extract the enveloped frames from the IP message. A ToolBox can be connected to one of the RTUs or to the IP Gateway, either locally or over IP network.

Each RTU/IP Gateway is assigned a Site ID. In addition, each RTU/IP Gateway with an IP interface is assigned an IP address. An IP conversion table which maps Site IDs to IP addresses is created in the ToolBox and downloaded to the RTUs and IP Gateway. This enables routing over the IP network to the proper destination.

Two variations of MDLC over IP exist, MDLC via Terminal Server and MDLC via Astro IP.

MDLC via Terminal Server

If the RTUs are on a Local Area Network (LAN), each can be connected to a Terminal Server attached to the Ethernet. The Terminal Server converts the RS232 to the Ethernet LAN and enables communication with an IP Gateway, or between RTUs.

In the diagram below, a typical configuration is shown, with RTUs attached via SLIP (Serial Line IP) port to a Terminal Server, which is in turn attached to Ethernet.

2-4

System Overview

SCADA Central

Ethernet

IP Network

Figure 2-3: Typical Configuration, MDLC via Terminal Server

MDLC via Astro IP

RTUs can be connected via SLIP connection to an ASTRO radio, which is part of an IP network.

In the diagram below, a typical configuration is shown, with RTUs attached via SLIP over RS232-E to ASTRO SPECTRA radios which support IP data capability. A ToolBox is connected to one of the RTUs through either Port 2 or Port 3. The IP Gateway on Ethernet acts as a gateway, translating between the IP and MDLC protocols.

2-5

RNC

MDLC Over Private DataTac

MOSCAD RTUs can communicate over Private DataTac systems (RDLAP) with SCADA centrals and with other RTUs. All MDLC features are preserved except for clock synchronization.

RTUs are connected to RDLAP (DataTac) radios (e.g. VRM 500, 600, 650, 660, and TRM 660) via RS232. An RTU sends a message (MDLC), through the radio to the Radio Network Controller (RNC). The RNC encapsulates the MDLC message and send it over IP to the IP Gateway. The IP Gateway then extracts the MDLC message from the IP envelope and transmits it to the appropriate destination. If the destination is another RTU over Private DataTac, the IP Gateway must support the reflector feature, which enables it to ???reflect??? the message back over RDLAP (DataTac).

2-6

RF System

Figure 2-5: Typical Configuration, MDLC via Private DataTac radios.

The picture above shows a typical system which supports MDLC communication over RDLAP (DataTac) radios. Note that the IP Gateway is configured as RDLAP (DataTac) reflector. A host computer attached to the Ethernet can receive TCP/IP applications from non-MOSCAD terminals on existing RDLAP (DataTac) systems, if required. A MOSCAD Programming ToolBox can be connected to one of the RTUs, and can access another RTU by using its Site ID and Link ID. ToolBox can also be attached to one of the serial ports of the IP Gateway.

SCADA Interface

Client-Server environment

The SCADA application for the IP Gateway is based on a client-server approach.

The IP Gateway application acts as a server while the SCADA Interface acts as a client. In such a relationship, the SCADA Interface must establish the connections with the IP Gateway needed for communicating with the MOSCAD RTUs.

After the connections have been established, the SCADA Interface can send data, commands, and polling requests to the field RTUs. It can also establish a special connection that enables

2-7

System Overview

receipt of data transmissions initiated by the field RTUs (so called burst/RTU event data, contention data or Change-Of-State [COS] messages).

A specialized routine, API CONNECT, allows the SCADA Interface to establish the most fitting mode of communication with the IP Gateway, based on the existing SCADA communication mode.

Channels and Channel types

The SCADA Interface must establish at least one connection toward the IP Gateway server. These connections are called channels and are used to transfer messages from the SCADA center toward both the Gateway and the RTUs in the field. The client application can open different types of channels to best serve its SCADA Interface process.

The two basic channel types are:

???Regular

???Spontaneous

A Regular channel enables asynchronous sending/receiving of data and requests. It uses amailbox mechanism for mapping the request messages to their replies.

A Spontaneous channel allows receiving burst data (Spontaneous COS messages) and RTU events - i.e. transmissions initiated by the field RTUs. This feature almost eliminates the need for the SCADA application to poll data since every change in one of the telemetry field variables can immediately be transmitted to the SCADA application.

MOSCAD System - RTU definitions

To make the MOSCAD field system definition transparent to the SCADA client application and to correctly parse the data received from the MOSCAD system, the API builds an internal data structure defining the types and numbers of the field RTUs. To do so, it uses two external system definition files (in ASCII format).

This automatic system definition done by the API routines hides the field system structure from the SCADA application and eliminates the need for any application modifications when working with different MOSCAD systems. Moreover, new RTUs can be added to the system at run time using the appropriate API routine.

Primary/Secondary Gateway Modes

The IP Gateway supports a redundant configuration. There are two modes of operation: Primary and Secondary. The initial mode of operation is defined by the startup process of the IP Gateway. At any other time, the SCADA can change the mode of operation flexibly by calling the appropriate API set mode routine. The API also supplies a routine for checking the current mode of operation. This functionality of the IP Gateway provides redundant gateway operation, which minimizes the risk of communication failure.

2-8

System Overview

Communicating with the IP Gateway

Once a channel has been established with the IP Gateway, the SCADA interface can issue requests to the IP Gateway. The request categories are Send routines, Receive routines, Data Analysis routines and Management routines.

Typical API sequence calls are the following:

Get_next_data_entity /* Get one data entity from the message buffer. */

Troubleshooting

The IP Gateway handles the communication with the SCADA in the REQMNG device. Diagnostics on this device can help when troubleshooting the SCADA connectivity.

For more information on the REQMNG device, see the Software Diagnostics Output section.

2-9

System Overview

MOSCAD NFM System

A typical network management system can be divided into three main levels:

???Network Management Level

???Element Manager Level

???Element Level

The following section provides a brief description of the MOSCAD NFM components that allow managing and supporting these network management levels.

Figure 2-6 shows a typical MOSCAD NFM configuration including all network management levels. It describes the MOSCAD NFM architecture that includes NMC computers and workstations that monitor and control - via the IP Gateway and the NFM RTUs - non-SNMP devices at the communication sites.

In this configuration, the end devices at the communication sites serve as a NE (Network Element) and the NFM RTU serves as an Element Manager that monitors and controls multi- communication and environmental devices at the site. The IP Gateway allows monitoring and controlling devices - via the NFM RTU - that are installed at multiple communication sites. The NMC allows monitoring and controlling of all devices in the network via multiple IP Gateways.

The NMC application can use the SNMP protocol and the IP Gateway MIB to Auto-discover the IP Gateway, the communication sites as well as the devices and their objects.

By using this MIB, the NMC application can poll the devices and their objects (NEs and their objects) in order to refresh its database and to display unsolicited events (Traps ) in the Alarm Manager application. By using the TELNET application in the host, the operator can access via the IP Gateway and the NM RTU any communication devices that have an RS-232 port with interactive interface.

The MOSCAD NFM product can be integrated either with the Motorola PRN (Private Radio Network) architecture or with a third party communication/telecommunication system via an IP Gateway that gives the NMC applications access to the equipment and environmental devices at the sites.

2-10

System Overview

Figure 2-6: MOSCAD NFM System Architecture with TELNET Application

2-11

System Overview

MOSCAD RTU

The MOSCAD RTU is a smart modular unit designed to operate as a stand-alone controller or as part of a system having any number of RTUs, control centers and sub-centers connected through a communication network with any number of links and nodes.

The MOSCAD RTU must be configured and loaded with the appropriate application using the MOSCAD Programming Toolbox.

The MOSCAD RTU is a microprocessor-based unit, which basically consists of a CPU module and various I/O and communication modules. A wide range of I/O and communication modules makes the MOSCAD system flexible to meet most application requirements.

For further details on the MOSCAD RTU, refer to the MOSCAD Owner???s Manual and the MOSCAD Service Manual.

MOSCAD Toolbox

The MOSCAD Programming Toolbox software package allows the system engineer to define and maintain the MOSCAD system according to user needs and requirements. The following main functions may be performed by means of the MOSCAD Programming Toolbox:

1.Editing the RTU user program including the following:

???Site Configuration according to hardware and port configuration

???Network Configuration according to network configuration

???Application database

???Application process

2.Preparing project documentation for the user

3.Automatically creating a central file to be used later during RTU database creation in the SCADA control center

4.Downloading Site Configuration to the MOSCAD RTU via the RS-232 port of the unit

5.Performing the following functions on any MOSCAD RTU either via local connection or via the communication network:

???Uploading Site Configuration and related data

???Downloading Application Program and Network Configuration

???Real-time symbolic (graphic) monitoring and debugging of the application (both database and process)

???Updating time and date at RTU sites

2-12

System Overview

???Testing all hardware modules, including software calibration of analog inputs and outputs

???Retrieving time-tagged events (of down to 1mSec resolution) logged in the RTUs

???Synchronizing the RTU real-time clock

???Retrieving errors logged in the RTUs (hardware or software malfunctions)

???Capturing the data packets on the communication links and analyzing the protocol seven layer

???System software diagnostics by object entity names

The definition of the RTU application program allows the system engineer to build the RTU???s database in a tabular form as a set of tables. The same tables used for the RTU database definition are the basis for process programming, I/O link definition, automatic central database definition, real-time monitoring of RTU operation, etc.

Once the database is built, the RTU programming process is carried out by using the symbolic Motorola Advanced Ladder Diagram Language.

IP Gateway for TCP/IP

The IP Gateway hardware is based on the 68360 Motorola microprocessor, which is a smart CPU with Ethernet and an I/O controller. It includes support for TCP/IP over an Ethernet port (10Base-T and AUI connectors) for communication with the SCADA, and three serial ports for communication with the Toolbox and with the MOSCAD RTUs.

The IP Gateway includes 22 LEDs, located on its front panel which indicate hardware status and communication port activity. In case of a malfunction, see the Indication LEDs section in the Hardware Installation section of this manual.

Two Ethernet connectors give support for connection to either a Twisted-Pair Ethernet cable (via 8-pin RJ45 connector) or a Thick-Wire Ethernet cable (via 15-pin AUI connector). To connect a Thin-Wire coaxial cable to the IP Gateway, a Thin-Wire to AUI connector unit which allows connecting the coaxial cable to the AUI port, should be used (not supplied).

The IP Gateway software provides MDLC services to the SCADA control center applications. The MDLC application layer is used for receiving events, status and telemetry calculated data from the MOSCAD RTUs to the SCADA central applications. It is also used to send controls and process parameters from the SCADA central to the MOSCAD RTUs. The IP Gateway software includes the TCP/IP driver for communicating with the SCADA computers and the MDLC driver for communicating with the MOSCAD RTUs as well as with the MOSCAD Programming Toolbox.

2-13

System Overview

IP Gateway Toolbox

The IP Gateway Toolbox is a software package, which runs on an IBM PC (or compatible), and allows the user to build the configuration for the MDLC and TCP/IP drivers. It also enables the user to download it to the IP Gateway hardware.

The IP Gateway Toolbox features the following:

???Microsoft Windows Man Machine Interface (MMI).

???Graphical User Interface (GUI). Each Toolbox module is represented by an icon, enabling friendly user access.

???Receiving errors logged in the system from the IP Gateway and the RTUs.

???Receiving communication diagnostics from the RTUs and operation diagnostics from the IP Gateway.

???Setting IP Gateway or RTU time and date.

???Downloading of user selected definitions/configurations to the IP Gateway.

???Erase Flash and System Download ??? enables the user to erase and download specific system partitions.

???Links Configurator ??? enables the user to change the number of links assigned to each medium.

The IP Gateway Toolbox allows the user to set, modify and download the following four basic groups of parameters:

IP Gateway Web Server

The IP Gateway, version 4.0 and higher, includes a built-in Web Server. The Web server enables users to perform certain Toolbox operations and to convey site information to and from the technicians, regardless of where they are located, over the World Wide Web.

The IP Gateway Toolbox utilities available through the Web Server enable the user to remotely perform the following operations:

???Provide reports on the status of each device in the current IP Interface or Gateway, as well as historical and statistical data on the device activities.

2-14

System Overview

???Remotely define SNMP and Motorola SSC parameters.

???Erase the IP Interface/Gateway Flash memory and downloads a new system.

IP Gateway Redundancy

To minimize the risk of a SCADA control center single point of failure and to ensure high availability for its applications, a redundant IP Gateway can be configured. When one

IP Gateway is not available, a second, redundant IP Gateway can be used. To increase the availability of the LAN network, dual Ethernet segments can be used, and each IP Gateway can be connected to a different segment.

In a redundant IP Gateway system configuration, one IP Gateway acts as the primary unit. The primary IP Gateway communicates properly over MDLC communication and over the SCADA channels. There is bi-directional transfer of both SCADA application messages and IP Gateway management messages. The secondary IP Gateway transfers IP Gateway management messages only. (It does not send or receive any MDLC messages, since it is logically disconnected from the link.)

HealthCheck Mechanism

The IP Gateway system includes a HealthCheck mechanism which manages the MDLC connectivity to the sites. Associated with each site are two links, through which the site can be reached. A background mechanism in both the IP Gateway and the MOSCAD units constantly verifies which links are available.

The HealthCheck mechanism uses the site table as the basis for its operations. As the

IP Gateway identifies which links are available, it can reduce communication overhead by routing frames destined to sites through their operational links.

2-15

Hardware Installation

Hardware description

The IP Gateway hardware is based on the 68360 Motorola processor, which is a dedicated smart CPU with Ethernet and I/O controller. In addition to the communication capabilities, the IP Gateway has powerful processing capabilities, using 32 Mbytes (8 Mbytes X 32 bit) of DRAM and 1 Mbyte (256 Kbyte X 32 bit) of FLASH memory.

A simplified block diagram of the IP Gateway hardware is provided in Figure 3-1.

Figure 3-1: IP Gateway, Simplified Block Diagram

3-1

Hardware Installation

Communication Ports

The IP Gateway includes support for TCP/IP over 10 Mbits/sec Ethernet LANs for communication with the SCADA, and three serial ports for MDLC over various links (radio, dialup and dedicated lines, multidrop wireline, serial RS-232 or RS-485) for communication with the MOSCAD RTUs.

The IP Gateway supports multiple logical channels running the TCP/IP protocol over Ethernet, thus allowing multiple processes running on the SCADA computer, to simultaneously access a number of functions in the IP Gateway.

The IP Gateway software supports four communication channels that can be configured to support the following links:

Ports 3 and 4 are available with one of the following options:

Note: The same plug-in boards that are used for the MOSCAD are used in the IP Gateway.

3-2

Hardware Installation

The third and fourth channels can be connected via plug-in board to various communication media:

Radio: VHF or UHF, conventional or trunked radio, that support the following characteristics:

???FSK up to 2.4 kbps

???DPSK @ 1.2 kbps

???DFM @ up to 4.8 kbps

???Leased 2 or 4 wire, up to 2.4 kbps, Sync and Async

???V.22, V.22 bis, Bell 212, Bell 102

???Multidrop 2-wire, up to 1.2 kbps, Sync

???Dial-up, up to 2.4 kbps, Async, V.22, V.22 bis, Bell 212

???RS-232 Async, up to 57.6 kbps

3-3

Hardware Installation

Mechanical Installation

The IP Gateway unit can be supplied with the following two configurations:

Gateway with communication interface

In this configuration, the Gateway is mounted in an NEMA4 housing, suitable for wall mounting and composed of the following:

???Stand-alone Gateway unit

???Radio unit applicable for the required frequency range and power, or alternatively, line unit applicable for interfacing to dedicated or dial-up lines.

???A 110V AC power supply + charger (produces +12V DC for the Gateway???s logic board and charges the battery); a 220V AC power supply is available as an option.

???12V DC battery rated for 5 Ah operation (10Ah battery is available as an option).

Figure 3-2: IP Gateway with Communication Interface

3-4

Hardware Installation

Stand-alone Gateway unit

The IP Gateway desk-top unit without radio, PS/Charger and box, to be placed on a desk or installed in the central facility by the user. The user must supply 12V DC.

Figure 3-3: Stand-alone IP Gateway

3-5

Hardware Installation

Connectors

Connector Locations

Eight connectors are located on the IP Gateway rear panel as shown in Figure 3-4 below:

Figure 3-4: IP Gateway Rear Panel

Connector Description

The following table lists the IP Gateway???s connectors and their connection points:

3-6

Hardware Installation

Power Supply

The IP Gateway with connection interface is powered by the MOSCAD 12V power supply (10.8 ??? 15.1V DC). Connect a four-wire power cable - FKN4411A - from this power supply to POWER on the rear panel.

The stand-alone Gateway is powered from an external +12V DC power supply.

3-9

Hardware Installation

Indication LEDs

There are 22 indication LEDs located on the IP Gateway???s front panel. These LEDs provide an indication of the board status and communication ports activity. Table 3-4 below describes each indication. The front panel and LEDs are shown in Figure 3-6 below.

Table 3-4: List of Indications

Note: When reverse polarity is detected on the reception lines (High and Low), the indication POL is lit, but the reception is not disabled.

3-10

Hardware Installation

???(2) RX LED of Port 4 is on: ROM test has failed.

???(3) CM and RX LEDs are on: FLASH memory test has failed.

???(4) TX4 LED is on: Create software module has failed.

???(5) CM4 and TX3 LEDs are on: Real time clock has failed.

???(6) RX3 and TX3 LEDs are on: Internal clock has failed.

???(7) CM3, RX3, and TX3 LEDs are on: Hardware breakpoint has failed.

???(8) MON LED is on: XTAL rate change has failed.

???(9) CM3 and MON LEDs are on: User request has failed.

???(10) RX3, CM3, and MON LEDs are on: The current site configuration was downloaded by a previous version of the Programming Toolbox.

???(11) TX and CM LEDs of Port 4 are on: Creating of Heap failed.

3-12

Software Installation

Introduction

The IP Gateway Toolbox software which is delivered with the IP Gateway unit, allows the system engineer to define and maintain the MDLC and TCP/IP parameters according to system requirements and user needs. It runs on a PC, under the Windows environment and provides the user with access to the following programs:

Each of these programs may be selected from the IP Gateway Toolbox Main Menu:

4-1

Software Installation

IP Gateway Toolbox - Functions and Features

a.The following configurations for the MDLC and TCP/IP can be edited:

???IP Gateway Site Configuration, according to hardware and port configuration

???MDLC Network Configuration, according to system-wide network configuration

???MDLC Sites Table (system-wide Site IDs and Link IDs)

???Host Table for manager registration

???Phone Book for dial-up modem support

???Data Tac (RNC) Modem ID Table

???IP Conversion Table

???SNMP Configuration

b.Downloading Site Configuration, Network Configuration, MDLC Site Tables, IP Gateway Configuration and TCP/IP Driver Configuration to the IP Gateway via the RS-232 port.

c.Retrieving errors logged in the IP Gateway (hardware or software malfunctions)

d.IP Gateway or MOSCAD RTU software diagnostics by object entity names

Prerequisites

Before installing the IP Gateway Toolbox application, make sure that your computer (IBM PC or compatible) has the following minimum configuration:

Hardware

???Pentium 100 or better

???CD-ROM drive

???Hard disk - the IP Gateway Toolbox requires at least 20 Mbytes on your disk

???32 Mbytes RAM

Software

???Microsoft Windows Operating System

4-2

Software Installation

Installation Procedures

This document outlines the instructions for installing the IP Gateway Toolbox Application software. An installation CD-ROM is supplied with the IP Gateway Toolbox.

Follow the instructions on the screen.

To install the IP Gateway Toolbox software, proceed as follows:

1.Insert the installation CD-ROM in the CD drive.

2.Select Install IP Gateway Toolbox V5.50.

3.The Install Wizard displays the product???s Splash Logo (see Figure 4-1) and the setup program prepares the InstallShield(r) for installation.

Figure 4-1: IP Gateway Toolbox Application Splash Logo

4.The Install Wizard starts with the Welcome Dialog screen (see Figure 4-2). Make sure to exit all Windows applications before continuing with the setup. If you have other Toolbox applications running, be sure to stop the communications driver after you quit all applications. After reviewing the instructions, click NEXT.

4-3

Software Installation

6.The Install Wizard displays the Choose Destination Location screen with the default directory path C:\Itbox550 (see Figure 4-4). If the default directory is acceptable, click NEXT. To install the software in a different directory, click BROWSE and then specify the pathname of a different folder.

Figure 4-4: Destination Drive and Directory Dialog screen

If you clicked the BROWSE button, the Installation Wizard displays the Choose Folder screen (see Figure 4-5). Click on the desired directory, then click OK.

4-5

Software Installation

Figure 4-5: Choose Folder screen

If you specified a non-existing destination directory, the Install Wizard inquires if you want to create this directory (see Figure 4-6). If you answer Yes, the Wizard creates a new directory. If you answer No, you are prompted to specify a new destination path.

Figure 4-6: Create New Destination Directory screen

7.The Select Program Folder screen suggests that you install the Toolbox icons in the

IP Gateway Toolbox folder (see Figure 4-7). If you wish to install the Toolbox icons in a different folder, select a program folder from the Folders list, or, if you wish to create a new folder, type a new program folder name. Click NEXT.

4-6

Software Installation

Figure 4-7: Select Program Folder screen

8.The Installation Wizard displays the Confirm Your Settings screen (see Figure 4-8). Verify that your settings are correct. If your settings are incorrect, click BACK to make the necessary changes. If your settings are correct, click NEXT to start the installation.

4-7

Software Installation

Figure 4-8: Confirm Your Settings screen

9.While the Setup program copies the IP Gateway Toolbox software files, a program indicator displays the progress of the file transfer progress (see Figure 4-9).

4-8

Software Installation

Figure 4-9: File Transfer Progress screen

10.When the last installation diskette is copied, setup displays a confirmation message indicating that the installation was successful (see Figure 4-10). After completion of the installation process, specify whether you want to view the Readme file, then click FINISH to complete the setup.

4-9

Software Installation

Figure 4-10: Setup Complete screen

Starting a Toolbox Application

In Windows, the IP Gateway Toolbox folder is located in the Start menu. To select the folder:

???Open the IP Gateway Toolbox 5.50 icon created automatically on the desktop during installation.

OR

???Press the Start button

???Select Programs

???Find the IP Gateway Toolbox 5.50 folder (or any other name you may have specified during installation).

???Select the desired tool from the Toolbox.

4-10

IP Gateway Toolbox

General Concept

The Windows-based IP Gateway Toolbox software which is delivered with the IP Gateway unit, allows the system engineer to define and maintain the IP Gateway parameters. For communication over the IP network, the IP Gateway requires that a unique Gateway IP address be set, as well as other optional TCP/IP parameters. For communication with the MOSCAD RTUs, the IP Gateway requires that the type of the communication links be selected, as well as the routing topology and other optional MDLC configuration parameters.

When you start the IP Gateway Toolbox, the main IP Gateway Toolbox screen appears with the following icons:

Each icon represents a program that allows you to define, modify and save the sub- configuration or to retrieve diagnostics reports from the Gateway.

5-1

Site Configuration

The IP Gateway system operates with a very wide range of communication boards which satisfy most application requirements. To make the system operation more efficient, the configuration of the IP Gateway unit should be defined. Site configuration involves the following:

???The ports of the IP Gateway and their parameters.

???Site ID (logical address) and system address.

???The IP Address of the IP Gateway

Once the configuration is downloaded to the site, it is ready to communicate with the devices connected to its ports (Computer, RTU, Terminal Server, etc.).

Note: CPU modules received from the factory are configured to the default configuration.

Site Configuration Window

The Site Configuration window allows you to define, modify, and save the IP Gateway ports and their parameters. To start the Site Configuration tool, double-click the Site Configuration

icon in the IP Gateway Toolbox folder. The following will appear:

5-2

Site Configuration

ToolBar

The Toolbar displays the icons described under Icons.

SiteIDBar

The SiteIDBar is used to specify the IP Gateway to which the site configuration will be downloaded and from which a site configuration can be uploaded. For SiteIDBar parameters, see the Download and Upload commands.

WorkSpaceBar

The WorkSpaceBar becomes available when you create a new site configuration file, open an existing file, or upload a configuration from the IP Gateway. The WorkSpaceBar provides an index into the various parameters of the site configuration and enables you to view or modify their values.

Port Tab

The WorkSpaceBar Port tab contains a treeview of the three IP Gateway ports. The items in this treeview provide access to screens and parameters which define how each of the ports is connected to the communication network and which devices are connected to each port.

5-3

Site Configuration

The highest level item in the treeview is the workspace name and below that is the project name. The third level contains the three ports ??? Port 2, Port 3, and Port 4.

A ???+??? sign before an item indicates that it contains other levels and can be expanded. Single- click the ???+??? (or double-click the item name) to expand it and access the next level. A ???-??? sign before an item indicates that it is fully expanded. Single-click the ???-??? (or double-click the item) to collapse it and hide its sublevels.

For each port, four screens can be opened: Type, User, Advanced Physical Layer, and Advanced Link Layer. Double-click on a screen name to open the screen in the client area. For more information about the port parameters and their settings, see Port Parameters below.

IP Port Tab

The IP Port tab contains a treeview of the Application Definition for the IP Port and the parameters for Port 1 and Terminal Server ports. As with the Port tab, the highest level item in the treeview is the workspace name and below that is the project name. The third level contains the definitions for DataTac, TCP/IP, and Terminal Server. By default, only the TCP/IP item can be defined. To define the DataTac and Terminal Server settings, right-click on the item and select Define from the right-click menu.

The IP Port tab treeview can be collapsed or expanded the same as the Port tab.

For more information, on configuring the IP Port, see IP Port below.

5-4

Site Configuration

Advanced Tab

The WorkSpaceBar Advanced tab contains a treeview of the port parameters and the advanced parameters of the site configuration. As with the other tabs, the highest level item in the treeview is the workspace name and below that is the project name. The next level in the treeview contains a variety of parameters.

The items under the project are displayed according to context.

Items preceded by a ???+??? or ???-??? sign can be collapsed, expanded and opened, as described under the Port tab. Items not preceded by a ???+??? or ???-??? sign can be opened by double-clicking on the item name.

For more information, see Advanced Parameters below.

5-5

Site Configuration

SCADA Tab

The WorkSpaceBar SCADA tab contains a treeview of the SCADA system parameters.

As with the other tabs, the highest level item in the treeview is the workspace name and below that is the project name. Items preceded by a ???+??? or ???-??? sign can be collapsed, expanded and opened, as described under the Port tab.

The next level in the treeview contains SCADA system parameters. Two screens of General and Gateway parameters can be opened. Double-click on a screen name to open the screen in the client area.

For more information about the SCADA system parameters and their settings, see System Parameters below.

OutPutBar

The OutPutBar displays information about the site configuration file and the download/upload process. The OutPutBar appears on the Site Configuration by default, but can be closed by clicking on the ???x??? in the upper left-hand corner. To redisplay, check OutPutBar on the View menu.

5-6

Site Configuration

File Menu, Preview Current File command

Help Menu, About Site Configuration command

File Menu

The commands in the File menu are mainly designed to handle configuration files.

New

The New command (Site Configuration, File menu) opens a new site configuration file. After this command is activated, the following dialog box is shown. Enter a project name and hit OK.

Dialog box parameters

Project Name

The name of the site configuration file.

Location

The folder in which the site configuration file will be created. By default, site configuration files are stored under C:\Itbox550\config.

5-8

Site Configuration

Open

The Open command (Site Configuration, File menu) opens an existing site configuration file. After the command is activated, the ToolBox displays the Open dialog box, as shown below.

Initially, the Open dialog box defaults to the config sub-directory of the ToolBox directory (e.g., C:\Itbox550\config), where the ToolBox stores configuration files by default. After the first execution of the Site Configuration utility, the Open dialog box defaults to the directory of the last opened configuration file.

Select the configuration file (see parameters below) and click OK to load it.

Dialog box parameters

Use the parameters in the order specified below.

Look in

If the currently displayed directory is not the correct one, open the Look in list and locate the directory. To access sub-directories, double-click parent directories.

File Name

Type the name of the configuration file. Site Configuration automatically adds the extension. Alternatively, locate the file name in the file list, and double-click the name.

Files of Type

This box shows the type (extension) of the files currently displayed in the File Name list. There are three file types in the drop-down list: Workspace (.ifw), Project (.ifp), and Config File (.cfg).

5-9

Site Configuration

The IP Gateway Toolbox recognizes and opens configuration files saved with previous ToolBox versions. If you open an older configuration file, a message box, like the one illustrated below, is displayed:

???To keep the older format, click the V3.50 button. In the Site Configuration menus, new features will appear dimmed, but the configuration can be changed using the enabled features (those are the features that exist in the older version of the ToolBox). After saving the updated file, you can still open and modify it using the older version of the ToolBox.

???To upgrade the configuration file to take advantage of the new ToolBox features, click the V5.50 button.

!IMPORTANT

If you click V5.50, you will not be able to load the file with an older version of

ToolBox.

Save WorkSpace

The Save WorkSpace command stores the current configuration.

Save as

The Save as command saves the current configuration under another name.

After activating this command, ToolBox displays the Save As dialog box, as shown below.

5-10

Site Configuration

Dialog box parameters

Use the parameters in the order specified below.

Save in

If the currently displayed directory is not the correct one, open the Look in list and locate the directory. To access sub-directories, double-click parent directories.

File Name

Type the name of the configuration file. Site Configuration automatically adds the extension. Alternatively, locate the file name in the file list.

Save as Type

This box shows the type (extension) of the files currently displayed in the File Name list. There is only one file type in the drop-down list. Config File (.cfg).

Close WorkSpace

The Close WorkSpace command clears the current configuration data from the screen and workspacebar.

Download

The Download command is used to download a site configuration file to the IP Gateway (to be stored in the FLASH memory). You can download to the IP Gateway directly connected to the ToolBox computer, or to a remote IP Gateway.

This command also enables you to change the Site ID and system address of the IP Gateway unit.

Before activating the Download command:

???Make sure that you have opened the correct configuration file - the one that contains

the configuration for the IP Gateway you are communicating with. Use the Open command to open a configuration file.

5-11

Site Configuration

???Ensure that the OutPutBar is displayed.

???Ensure that the SiteIDBar is displayed and the address is configured properly.

???Ensure that the ToolBox computer is ready to communicate.

Use the SiteIDBar to specify the IP Gateway to which the site configuration file is to be downloaded.

SiteIDBar parameters

Local

If the ToolBox computer is locally connected to the IP Gateway, make sure that this parameter is selected. Note: New site ID (default=1) will be used.

Remote

If you want to configure a remote site, click this parameter.

Site ID, Link ID

If you want to configure a remote site, specify its Site ID, open the Link ID drop-down list and select the appropriate link ID.

New Site ID

To specify a new site, change the site ID and the system address of the IP Gateway. Enter the appropriate values in the Site ID field. The default is 1.

The site ID defines the unit???s logical address, and it may range from 1 to 65,287.

System Address

To specify a new site, change the site ID and the system address of the IP Gateway. Enter the appropriate value in the System Address field. The default is 0.

The system address is the physical base address assigned to the whole system, and may range from 0 to 65,535. The base address is used in broadcast transmissions.

The physical address of each IP Gateway is automatically allocated by ToolBox and by the control center in the form of <system address> + k where k is the logical address (Site ID) of the unit. For example, if the system address is 100, then the IP Gateway addresses may be 101, 102, ???, 100+n. If two systems share the same communication radio (over one frequency) and the first system contains N sites, then the system address of the second system must be defined as N+50 (50 addresses reserved).

After specifying the IP Gateway in the SiteIDBar, click on the Download icon or select Download from the File menu. The ToolBox will ask you to specify the communication password. After the correct password is entered, ToolBox will begin downloading the configuration file. The download information and status will be displayed in the OutPutBar Download Tab. At the end of the download operation, the IP Gateway will perform a cold restart and build the software object entities according to the user???s definitions. Once a unit has been reconfigured and restarted, the port used for configuration may no longer be defined as RS232 Local Computer port. In this case, connect the ToolBox to another port, defined as Computer port, in order to proceed with your work. For a local connection to the ToolBox, there must be at least one port defined as RS232 Local Computer port.

5-12

Site Configuration

If none of the ports is defined as RS232 Local Computer, ToolBox access will be permitted through any port, provided it is defined as MDLC. If there is no such port, access will be denied. You may reset the configuration of the IP Gateway using the 'Erase Configuration' operation in the Downloader application.

Upload

The Upload command is used to read the site configuration from the IP Gateway into the ToolBox. You can upload from the IP Gateway directly connected to the ToolBox computer, or from a remote IP Gateway.

Before you activating the Upload command:

???Make sure that the OutPutBar is displayed.

???Make sure that the SiteIDBar is displayed and the address is configured properly.

???Make sure that the ToolBox computer is ready to communicate.

Use the SiteIDBar to specify the IP Gateway to which the site configuration file is to be uploaded.

SiteIDBar parameters

Local

If the ToolBox computer is locally connected to the IP Gateway, make sure that this parameter is selected.

Remote

If you want to upload the configuration of a remote site, click this parameter.

Site ID, Link ID

If you want to upload the configuration of a remote site, specify its Site ID, open the Link ID drop-down list and select the appropriate link ID. If a configuration created with an earlier version of ToolBox is uploaded, a message box appears which is similar to the one that displays when you activate the Open command for an older configuration. See details in Open, earlier in this chapter.

After specifying the IP Gateway in the SiteIDBar, click on the Upload icon or select Upload from the File menu. The ToolBox will ask you to specify the communication password. After the correct password is entered, ToolBox will begin uploading the configuration file. The upload information will be displayed in the OutPutBar Upload Tab. After the upload operation ends successfully, the ToolBox displays useful status information in the Upload Information dialog box, as illustrated below.

5-13

Site Configuration

The information includes details such as the number of times the FLASH memory of that specific IP Gateway has been burnt (the FLASH memory may be burnt 10,000 times). The version numbers of the IP Gateway and ToolBox are also displayed. Another important piece of information displayed in this window is about the configuration of the specific IP Gateway - the version number of ToolBox that was used when programming the configuration.

The version numbers of ToolBox and IP Gateway system software are updated when additional features and improvements are added.

Compatibility between ToolBox and the IP Gateway is assured only if the version number of ToolBox software is higher than the version number of the IP Gateway system software.

The version number is composed of two numbers, as follows: Va.b. Note that a is a one-digit number and b is a two-digit number (for example, V1.34).

The number to the left of the decimal point describes a major modification of the software, while the number to the right of the decimal point describes a minor modification.

Abort Upload/Download

The Abort Upload/Download command stops the upload or download process.

View Last Upload Information

The View Last Upload Information command displays information about the most recent upload. See Upload above.

5-14

Site Configuration

CPU Menu

The CPU menu displays the IP Gateway type. It cannot be modified by the user.

View Menu

The commands in the View menu are mainly designed to handle the display of the control bars. The following views are available to the user. Click on an entry to select it, and a check mark will appear on the menu. The associated view is then displayed.

ToolBar

When checked, this command displays the ToolBar of icons, usually at the top of the screen.

WorkSpaceBar

When checked, this command displays the WorkSpaceBar with its treeview and tabs, usually on the left side of the screen.

OutPutBar

When checked, this command displays the OutPutBar, usually towards the bottom of the screen.

StatusBar

When checked, this command displays the StatusBar, at the bottom of the screen.

SiteIDBar

When checked, this command displays the SiteIDBar, usually towards the top of the screen.

Tools Menu

The command in the Tools menu is designed to handle the settings of the program.

Options

This command is used to set the fonts and colors of the texts displayed in the program. After activating this command, the dialog box looks as shown below.

5-16

Site Configuration

Window Menu

The commands in the Window menu are designed to handle the display of the windows and the style of these windows.

Close

This command closes the current active window. If you have made changes in the currently active window and have not yet saved the workspace, Site Configuration asks if you want to save the changes. To save the changes, click on Yes. To close the window without applying the changes, click on No.

Close All

This command closes all the open windows. If you have made changes in any active windows and have not yet saved the workspace, Site Configuration asks for each window if you want to save the changes. To save the changes, click on Yes. To close the window without applying the changes, click on No.

Cascade

This command arranges the various screens in cascade style.

5-17

Site Configuration

Tile Vertically

This command arranges the various screens in vertically tiled style.

Tile Horizontally

This command arranges the various screens in horizontally tiled style.

Help Menu

The Help menu enables the user to view the version information and help files which relate to the Site Configuration tool.

Help Topics

This command opens the help files which describe the Site Configuration tool and other IP Gateway Toolbox utilities.

About Site Configuration

This command displays the version information for the Site Configuration tool.

Port Parameters

The Port parameters define the communications ports of the site, regarding their connection to the communication network and the devices connected to them. The ports parameters windows can be opened from the Port tab or Advanced Tab of the WorkSpaceBar. For information on opening the windows, see WorkSpaceBar.

Port 2

Port 2 can be configured as RS232 or RS485.

Port 2 parameters are grouped as follows:

???Port Type. The Port Type window displays the type of communication used by the port. The communication type is established by means of a set of parameters. Double-click the Type item in the WorkSpaceBar Port tab to display the Port Type parameters window.

???User parameters. Double-click the User item in the WorkSpaceBar Port tab to display the User parameters window.

???Advanced Physical Layer parameters. Double-click the Advanced Physical Layer item in the WorkSpaceBar Port tab to display the Advanced Physical Layer parameters window.

???Advanced Link Layer parameters. Double-click the Advanced Link Layer item in the WorkSpaceBar Port tab to display the Advanced Link Layer parameters window.

5-18

Site Configuration

Port Type for Port 2

The Port Type parameters window is displayed with the default setting. To change the Port Type, select an option in the first box. Other parameters become available as you select options in subsequent boxes. You have reached the last parameter when the message ???Port Type selection is completed??? is displayed, as shown below:

ToolBox requires you to select a value for each parameter. After selecting the required values,

click on the OK or Apply icon to save the selection. Until the changes are applied, the screen header will reflect the previous values, but will be marked as ???(Modified)???. Until the changes are applied, all other related screens will use the previous Port Type values. If you try to apply the changes or save the WorkSpace without selecting a value in a drop-down list, an appropriate message is displayed which tells you to complete the entries. To exit the screen

without applying the changes, click on the Cancel icon. To revert to the default values, click the on the Default icon.

When you finish setting the Port Type parameters, the parameters you have selected will appear beside Port 2 in the WorkSpaceBar Port tab.

!IMPORTANT

If you change the Port Type parameter setting, all parameter values that have been previously modified return to their default.

The following is a description of the different combinations.

Not Used

Means that the specific port is not used. This definition saves RAM memory (about 2Kb) that can be used by the application.

RS232, Async, Local Computer (MDLC)

For connection to ToolBox or central, using the MDLC protocol.

RS232, Async, RTU-to-RTU (MDLC)

For local connection to another RTU in asynchronous mode, via RS232, using the MDLC protocol (it can also be used for communicating with the ToolBox).

5-19

Site Configuration

RS232, Sync, RTU-to-RTU (MDLC)

For local connection to another RTU in synchronous mode, via RS232.

RS485, RTU Multi-drop (MDLC)

For local connection between two or more RTUs in asynchronous mode, via RS485.

User Parameters for Port 2

A description of the User parameters follows.

Link name

Contains the logical name of the link that the port is connected to. The link name is automatically selected according to the Port Type parameters. For example, if the connection type is Local Computer, then ToolBox automatically selects COMPUTER1 as link name. If relevant, you can open the drop down list and select another name.

Data speed

If data speed is applicable to the port type parameters selected earlier, this parameter defines the communication data speed of the selected media. The default is 9600. The IP Gateway supports baud rates of up to 57,600.

Description

Enter your own description of the communications link (up to 40 characters).

Default Routing

Ensures RTU ???mobility???. The Default Routing parameter allows you to define the IP Gateway as one that can be switched from one base station to the other by changing the radio frequency (RadioX) or switching physical lines (LineX), but without changing the Link ID and the MDLC network settings.

The choices are:

5-20

Site Configuration

Advanced Physical and Link Layer Parameters for Port 2

When one of the advanced parameters windows is displayed, you can use the following functions:

???After changing a parameter, you can restore all changes to their default, by clicking the Default icon.

???Modified parameters appear against red background the next time you access the parameter list.

For more details, see Advanced Parameters in this chapter.

Port 3

Port 3 is a plug-in port designed for various radio or line communications, for example:

For details on the selection method and options, see Port 2.

Port Type for Port 3

For details on the selection method, options, and possible combinations, see Port 2. The following is a description of the additional combinations that apply to Port 3 and Port 4 only.

Radio, Conventional, radio type, max. number of repeaters, modem

Direct FM modulation for conventional radio. For all parameters that appear italicized above, open the drop-down list and select the corresponding value. If you cannot find the requested value on the list (like a radio type), select the ???General??? parameter (for example, General Radio).

Radio, Trunking, radio type, trunk system, modem

Trunked radio. For all parameters that appear italicized above, open the drop-down list and select the corresponding value. If you cannot find the requested value on the list (like a radio type or trunk system), select the ???General??? parameter (for example, General Radio).

Line, Multi-Drop Half-Duplex

For multi-drop half-duplex wire line communication, using the Line Modem board.

Line, Full Duplex (2w/4w), Sync

For full-duplex (2w/4w), synchronous wire line communication, using the Line Modem board.

Line, Full Duplex (2w/4w), Async

For full-duplex (2w/4w), asynchronous wire line communication, using the Line Modem board.

Line, Dial-up, Async

For asynchronous wire line communication using the dial-up Line Modem board.

5-21

Site Configuration

Microwave, Full-Duplex, Sync

For full-duplex, synchronous microwave communication, using the Line Modem board.

Microwave, Full-Duplex, Async

For full-duplex, asynchronous microwave communication, using the Line Modem board.

Microwave, Half-Duplex

For half-duplex microwave communication, using the Line Modem board.

5-22

Site Configuration

User Parameters for Port 3

A description of the User parameters follows.

Link name

Contains the logical name of the link that the port is connected to. The link name is automatically selected according to the Port Type parameters. For example, if the medium is Radio, then ToolBox automatically selects RADIO1 as link name. If relevant, you can open the drop down list and select another name.

Data Speed

If data speed is applicable to the port type parameters selected earlier, this parameter defines the communication data speed of the selected media. The default is 9600. The IP Gateway supports baud rates of up to 57,600.

Modulation

Defines the type of modulation, the data speed, and the communication standard. The various available options for the three types of line interfaces are detailed in the following table.

5-23

Default Routing

Ensures IP Gateway ???mobility???. The Default Routing parameter allows you to define the IP Gateway as one that can be switched from one base station to the other by changing the radio frequency (RadioX) or switching physical lines (LineX), but without changing the Link ID and the MDLC network settings.

The choices are:

Description

Enter your own description of the communications link (up to 40 characters).

Advanced Physical and Link Layer Parameters for Port 3

After clicking one of the advanced parameters tabs, you can use the following functions:

???After changing a parameter, you can restore all changes to their default, by clicking the Default icon.

???Modified parameters appear against red background the next time you access the parameter list.

Parameters are reviewed in Advanced Parameters in this chapter.

Zones in Port 3

For details about zones, see the MOSCAD Programming ToolBox System Overview manual. 5-24

Site Configuration

The Zones button appears in the Definition of Port 3 Parameters dialog box when the selected port type parameters involve zone definitions. Click the Zones button to open the Define Zones dialog box, shown below.

Dialog box parameters

Unused zones

Click the zone(s) on the left list that you want to select.

Selected zones

Click the zone(s) you want to remove from the current definition.

Add

Click this button to select the zone marked on the left list. The zone name moves to the right list.

To mark zones non-sequentially, hold CTRL down and click the zones you want. To mark successive zones, click the first, hold down SHIFT and click the last.

Remove

Click this button to remove a zone from the selected zones (right list).

For details about the marking method, see Add.

5-25

Site Configuration

Port 4

Port 4 is also a plug-in port like Port 3, designed for various radio or line communications, for example:

For details on the selection method and options, see Port 3.

Port Type for Port 4

For details on the selection method, options, and possible combinations, see Port 3. The following is a description of the additional combinations that apply to Port 3 and Port 4 only.

Radio, Conventional, radio type, max. number of repeaters, modem

Direct FM modulation for conventional radio. For all parameters that appear italicized above, open the drop-down list and select the corresponding value. If you cannot find the requested value on the list (like a radio type), select the ???General??? parameter (for example, General Radio).

Radio, Trunking, radio type, trunk system, modem

Trunked radio. For all parameters that appear italicized above, open the drop-down list and select the corresponding value. If you cannot find the requested value on the list (like a radio type or trunk system), select the ???General??? parameter (for example, General Radio).

Line, Multi-Drop Half-Duplex

For multi-drop half-duplex wire line communication, using the Line Modem board.

Line, Full Duplex (2w/4w), Sync

For full-duplex (2w/4w), synchronous wire line communication, using the Line Modem board.

Line, Full Duplex (2w/4w), Async

For full-duplex (2w/4w), asynchronous wire line communication, using the Line Modem board.

Line, Dial-up, Async

For asynchronous wire line communication using the dial-up Line Modem board.

Microwave, Full-Duplex, Sync

For full-duplex, synchronous microwave communication, using the Line Modem board.

Microwave, Full-Duplex, Async

For full-duplex, asynchronous microwave communication, using the Line Modem board.

Microwave, Half-Duplex

For half-duplex microwave communication, using the Line Modem board.

User Parameters for Port 4

See User Parameters for Port 3.

5-26

Site Configuration

Advanced Physical and Link Layer Parameters for Port 4

After clicking one of the advanced parameters tabs, you can use the following functions:

???After changing a parameter, you can restore all changes to their default, by clicking the Default icon.

???Modified parameters appear against red background the next time you access the parameter list.

Parameters are reviewed in Advanced Parameters in this chapter.

Zones in Port 4

For details about zones, see the Zones in Port 3 section above.

IP Port

The IP Port (Port 1) supports the following applications:

One or more applications can be defined. By default, only TCP/IP is selected, as shown below. To define either DataTac or Terminal Server, right click on the item in the treeview and select Define from the right-click menu.

Note: The TCP/IP option cannot be removed from the Selected applications. However, the Media in the TCP/IP Port Type can be set to Not Used.

Port Type for TCP/IP Port 1

Currently the only option for TCP/IP Port 1 besides NOT USED is:

Ethernet, TCP/IP, MDLC Over IP

User Parameters for TCP/IP Port 1

A description of the User parameters follows.

IP Gateway IP Address

IP address of the IP Gateway. For information on this and other IP Addresses in the configuration, see your network administrator.

Default Router IP Address

Range: 000.000.000.001-255.255.255.254

Net Mask Address

Range: 000.000.000.001-255.255.255.255

5-27

Site Configuration

5-29

Site Configuration

Length of buffer for debug sprint (C++ function)

Port Type for DataTAC Port 1

Currently the only option for DataTAC Port 1 is:

DataTAC

User Parameters for DataTAC Port 1

A description of the User parameters follows.

Link name

The logical name of the link that the port is connected to. The link name is automatically selected according to the port type parameters. If relevant, you can open the drop-down list and select another name.

RNC IP address

IP Address of the RNC box. Default: 000.000.000.001-255.255.255.254

Default routing

See Default Routing under User Parameters for Port 2 for the choices.

Physical Parameters for DataTAC Port 1

Idle interval between RX frames and end reception <200-3000> [200]

The interval of time after RX frames have been received to wait for an end frame.

The interval of time to wait for a frame.

Link Layer Parameters for DataTAC Port 1

This section reviews the parameters through which you can control the functioning of the Link Layer.

Not supported yet. Select the Standard link type to establish a link that requires ACKs. Otherwise select Fast Link (no ACK).

5-30

Site Configuration

This is the maximum number of MDLC frames that can be placed in the transmission queue before a transmission process starts.

The reception process of the Data Link layer prepares an ACK for each received data frame, and is capable of issuing, in a single ACK message, up to 57 ACKs for data frames that arrived in uninterrupted sequence. This parameter determines the number of ACK buffers in which ACKs are prepared and moved to transmission before the ???Cannot get ACK buffers??? message is issued to the Error Logger. This message means that the acknowledging side is unable to move to ACK transmission because of heavy reception traffic, or because it cannot access a channel for transmission.

The number of times the Data Link layer retransmits a data frame for which ACK was not received.

The number of times the Data Link layer retransmits a data frame for which BUSY ACK was received (BUSY ACK is issued when all Data Link layer boxes of the switching node on are full).

The interval of time that should elapse before a data frame for which BUSY ACK was received, is retransmitted.

The number of retries for broadcast frames. Since broadcast frames are not acknowledged, specify a value greater than 0 to increase the chances of the frames reaching their destination.

A broadcast that activates a momentary operation (not latch!) is likely to reactivate the operation if the number of TX broadcasts is greater than 0.

The period of time that should elapse between retries of broadcast frames (if the previous parameter is not 0).

It is possible to conduct a session based on Site ID/Link ID using Local if the port is of Computer/Rslink type. Normally the port is defined for Local Response if the medium is not ???multidrop???. In any case, ???local response??? can be forced on a port if it is not ???multidrop???. The default value is based on the port type. It is recommended to leave the default as is.

The delay (applied to the channel) between the end of a transmission and the beginning of reception, for clock synchronization purposes. The default depends on the selected medium. However, the user can change it.

5-31

Site Configuration

Maximum number of units the Data Link layer is capable of addressing in a single transmission. For ???private conversation???, specify 1.

A period of time after which a failed link will be considered as being back in order, provided the value of the next parameter (???Periodic check...???) is Disable. Or, the period of time after which the Network layer issues a control frame to check the link, if the value of the next parameter is Enable.

The period of time that should elapse before a retry takes place in Full Duplex. New data frames cannot be sent to the retried unit.

Terminal Server

The Ports Overview displays the total number of ports defined in the system and allows you to add new ports, and to modify or delete existing ports.

By default, the Terminal Server item in the workspace treeview has no items beneath it. To open the Ports Overview screen, first select Define from the right-click menu on the Terminal Server item. The Ports Overview item will appear under Terminal Server.

Double-click on the Ports Overview item. The Ports Overview screen will appear.

New terminal server ports can be added. See Insert One Port and Insert Group of Ports below. Once the ports have been added, click on OK or Apply. New Terminal Server Port items will appear in the workspace under the Terminal Server item. User, advanced physical layer and advanced link layer parameters can be set for the new ports.

To delete items defined under the Terminal Server node, select Delete from the right-click menu on the Terminal Server. All servers will be deleted.

Ports Overview

To modify the parameters of a particular Terminal Server Port in the Ports Overview screen, click in the field and enter the changes.

5-32

Site Configuration

Terminal Server IP address

This column displays the 32-bit IP address parameter of the Terminal Server connected to the current port.

Range: 000.000.000.001-255.255.255.254

TCP Port ID

This column displays the TCP Port ID of the current port.

Link ID

This column displays the Link Name (ID) of the current port.

Description

This column is used to enter free format text in user application terminology.

Five icons appear at the top of the Ports Overview screen in addition to the standard icons.

Insert One Port

Use the Insert One Port button to define a new port which will be connected to a Terminal Server. Click Insert One Port. Toolbox adds a blank row below the insertion point, with default values for:

After the port is inserted, the default value for the Terminal Server IP Address must be modified.

The TCP PORT ID must be modified only if the Terminal Server IP Address to which it will be defined already has a TCP PORT ID with the same value.

To save the changes, click on OK or Apply. A new Terminal Server Port item will appear in the workspace under the Terminal Server item. User, advanced physical layer and advanced link layer parameters can be set for the new port.

Terminal Server IP address

Double-click this cell to change the default address to the IP address of the Terminal Server that the specific port is connected to.

5-33

Site Configuration

Range: 000.000.000.001-255.255.255.254

If you accidentally type an IP address which has already been assigned to an existing Port, the following message appears when you try to Save or enter Advanced parameters:

If you accidentally type an invalid address or don???t change the default address, the following message appears:

TCP Port ID

Double-click this cell to change the default value to the corresponding four-digit TCP Port ID. The TCP Port IDs must be unique in the same Terminal Server IP address. Default value is 2001.

Link ID

This column is used to assign a communications link to the port. Select the appropriate Link ID from the drop-down list box. Possible values are RSlink(x) and LINE(x), where (x) is a specific RSlink number or a LINE number.

The total number of items listed, reflects the configuration in the MDLC Links Configurator utility.

This field defaults to the first available (unused) Link ID in the drop-down list box.

Description

Double-click this column to enter a description of the port (up to 40 characters).

Insert Group of Ports

Use the Insert Group of Ports button to insert a group of ports linked to the same IP address group. The following screen is displayed:

5-34

Site Configuration

For Terminal with Server IP address

Range: 000.000.000.001-255.255.255.254

User Free Link-IDs starting from

This field defaults to the first available Link ID and generates consecutive, unique Link IDs.

Use Free Port-IDs starting from

This field defaults to Port ID 2001 and generates a Port ID for each inserted port in sequential order.

Number of Ports to insert (up to xx)

where xx = total number of available ports

Click to enter the number of ports you want to insert. Minimum: 1

Maximum: total number of available ports

Default: 5

Click OK to accept the values and to return to the Terminal Server Ports screen.

Toolbox inserts the newly created ports after the insertion point with specified values for the TCP Port ID and the Link ID.

To save the changes, click on OK or Apply. A new Terminal Server Port item will appear in the workspace under the Terminal Server item for each port. User, advanced physical layer and advanced link layer parameters can be set for the new ports.

Terminal Server IP address

As defined in the Insert group of Terminal Server Ports screen.

TCP Port ID

The TCP Port ID defaults to the next available TCP Port ID.

5-35

Site Configuration

Link ID

The Link ID defaults to the next available Link ID.

Description

Defaults to a blank field. You may enter an up to 40-character port description.

Copy One Port

Use the Copy One Port button to create a new Terminal Server Port with the same properties to belong to the same group of Terminal Server IP addresses as the existing Port and to retain the same Advanced Parameters as the existing Terminal Server Port.

From the Terminal Server Ports screen, select an existing port with properties similar to the one you want to create. Click Copy One Port.

Toolbox copies the new port after the insertion point. The copied Port is identical to the source Port, except for the TCP Port ID and Link ID. To save the changes, click on OK or Apply. A new Terminal Server Port item will appear in the workspace under the Terminal Server item. User, advanced physical layer and advanced link layer parameters can be set for the new port.

Terminal Server IP address

Same as the source port.

TCP Port ID

The TCP Port ID is not copied since Toolbox automatically assigns the next available TCP Port ID.

Link ID

The Link ID is not copied since Toolbox automatically assigns the next available Link ID.

Description

Same as the source port. Can be modified.

Copy Group of Ports

Use the Copy Group of Ports button to create a new Terminal Server Port with the same properties (belong to the same group of IP addresses (Terminal Server) as the existing Port and to retain the same Advanced Parameters) as the existing Terminal Server Port. From the Terminal Server Ports screen select an existing port with properties similar to the one you want to create. Click Copy Group of Ports. The following screen appears:

5-36

Site Configuration

Description

Same as the source port. Can be modified.

Toolbox copies the new ports after the insertion point. The copied ports are identical to the source port, except for the TCP Port ID and Link ID.

Delete Ports

Use the Delete Ports button to delete one or more of the Terminal Server Ports.

Select the Terminal Server Port to be deleted from the Terminal Server Ports screen and click the Delete Ports button.

To select successive Terminal Server Ports, click the first Terminal Server Port address and press the SHIFT key while you click the last Terminal Server Port address, or click-hold-and- drag.

To delete all ports, defined under the Terminal Server node, select Delete from the right-click menu on the Terminal Server. All servers will be deleted.

User Parameters for Terminal Server Port 1

A description of the User parameters follows.

Terminal Server IP address

This column displays the 32-bit IP address parameter of the Terminal Server connected to the current port.

Range: 000.000.000.001-255.255.255.254

TCP ID of Port

This column displays the TCP Port ID of the current port.

Link Name

This column displays the Link Name (ID) of the current port.

Description

This column is used to enter free format text in user application terminology.

Advanced Physical Parameters for Terminal Server Port 1

For a description of the Advanced Physical parameters, see Physical Parameters for DataTAC Port 1 above.

Advanced Link Parameters for Terminal Server Port 1

For a description of the Advanced Link parameters, see Link Layer Parameters for DataTAC Port 1 above.

5-38

Site Configuration

The period of time the system will wait for channel access, from the time it requests a channel.

The maximum time during which data can be transmitted. After this period of time transmission stops even if it has not yet ended.

The period of time during which the PTT should be held pressed at the end of data transmission or between frames. Enter 0 to ignore this feature.

The maximum waiting time for a channel. After this time-out, the system accesses a channel whether or not it is free.

The period of time during which the PTT should be held pressed before a predetermined preamble is transmitted and before data transmission begins.

In a trunked system, the period of time that should elapse between releasing the PTT and until the radio is ready for reception.

In a trunked system, the maximum period of time during which the PTT should be held pressed in order to access a channel.

In a trunked system, the PTT pressing time cycle until a channel is accessed.

The size of a time slot in the slotted channel access mechanism of MDLC.

This is the minimum period of time during which a channel must be free before transmission can resume. If another unit transmitted during this time, the current unit does not have to hold transmission.

The minimum period of time that should elapse between the end of a transmission and its first retry, and between retries.

In pulse dialing, the ON (???make???) and OFF (???break???) times should be defined. This parameter defines the OFF time.

61 US standard

5-40

Site Configuration

will start transmitting only after a delay that is equal to this parameter multiplied by the RTU's priority level. If in the meantime the channel has been taken by a higher-priority RTU, the whole process is repeated when the channel is free again.

For example, let's assign the time resolution T. When the RTU accesses the channel, it starts transmitting only after a delay that is a factor of T. When the RTU accesses the channel for the first time, the delay is (n+4)??? T, where n represents the 4 less significant bits in the address. When an RTU sends an acknowledgment to another RTU, it will start transmitting only after a delay of 0 to 3T. If a collision occurs because two RTUs have been addressed with the same 4 less significant bits, then the address bits are shifted automatically, and the RTU starts transmitting after a different delay.

Defines the delay after which the RTU will transmit its message even if the communications channel is busy. The default value of 0 means that this feature is disabled (i.e., the RTU will not transmit if the channel is busy).

Not used.

For future use. To implement the store and forward feature by hardware. It is applicable in case the piggyback modem is DFM, FSK, or COS.

The minimum time (in msec) that the RTU will wait before retransmitting an unacknowledged message.

Link Layer

This section reviews the parameters through which you can control the functioning of the Link Layer.

Not supported yet. Select the Standard link type to establish a link that requires ACKs. Otherwise select Fast Link (no ACK).

This is the maximum number of MDLC frames that can be placed in the transmission queue before a transmission process starts.

The reception process of the Data Link layer prepares an ACK for each received data frame, and is capable of issuing, in a single ACK message, up to 57 ACKs for data frames that arrived in uninterrupted sequence. This parameter determines the number of ACK buffers in which ACKs are prepared and moved to transmission before the ???Cannot get ACK buffers??? message is issued to the Error Logger. This message means that the acknowledging side is unable to move to ACK transmission because of heavy reception traffic, or because it cannot access a channel for transmission.

5-43

Site Configuration

The number of times the Data Link layer retransmits a data frame for which ACK was not received.

The number of times the Data Link layer retransmits a data frame for which BUSY ACK was received (BUSY ACK is issued when all Data Link layer boxes of the switching node on are full).

The interval of time that should elapse before a data frame for which BUSY ACK was received, is retransmitted.

The number of retries for broadcast frames. Since broadcast frames are not acknowledged, specify a value greater than 0 to increase the chances of the frames reaching their destination.

A broadcast that activates a momentary operation (not latch!) is likely to reactivate the operation if the number of TX broadcasts is greater than 0.

The period of time that should elapse between retries of broadcast frames (if the previous parameter is not 0).

It is possible to conduct a session based on Site ID/Link ID using Local if the port is of Computer/Rslink type. Normally the port is defined for Local Response if the medium is not ???multidrop???. In any case, ???local response??? can be forced on a port if it is not ???multidrop???. The default value is based on the port type. It is recommended to leave the default as is.

The delay (applied to the channel) between the end of a transmission and the beginning of reception, for clock synchronization purposes. The default depends on the selected medium. However, the user can change it.

Maximum number of units the Data Link layer is capable of addressing in a single transmission. For ???private conversation???, specify 1.

A period of time after which a failed link will be considered as being back in order, provided the value of the next parameter (???Periodic check...???) is Disable. Or, the period of time after which the Network layer issues a control frame to check the link, if the value of the next parameter is Enable.

The valid values are:

5-44

Interval between FULL DUPLEX TX retries <10-100> *100mSec [50]:

The period of time that should elapse before a retry takes place in Full Duplex. New data frames cannot be sent to the retried unit.

Transport Multiplex Layer

Number of logical channels in the MDLC protocol capable of initiating communication via a session oriented channel. Do not change this value.

Number of MDLC logical channels that can be accessed through one or more masters simultaneously.

Message-Oriented Service (Frame Sequence)

The period of time during which a Reset ACK should be transmitted to a unit that is expected to return a void frame at Transport Multiplex level for each Reset ACK. After the period of time specified here, the unit stops sending Reset ACKs in order to identify another reset situation, should it occur.

A frame that is received again during this period of time is considered a duplicate, and discarded. If it arrives after this time, it is considered to be a new frame.

The period of time during which frames that failed to arrive as part of a chain are allowed to be retried at Data Link level. This timeout is calculated as a function of the number of retries and the data speed.

The gap that will cause the unit to move to synchronization at Transport Multiplex level. For example if the value is 16 and frame x+16 arrives while x was expected, synchronization will take place.

The allowed interval between retried frames. For example, if the value is 16 and x-16 arrived while x is expected, the unit moves to perform synchronization as in the previous parameter.

5-45

Site Configuration

Specify YES to broadcast to all units defined after Reset Load in order to synchronize at Transport Multiplex level.

Time interval between two Restart control frames at Transport Multiplex level.

The period of time after which an ???urge??? frame will be issued if a gap formed at Transport Multiplex level. A response to the urge frame means that the gap will never be filled since all Data Link layer retries have already been exhausted.

Since Transport Multiplex consumes buffers for transmission, the number of buffers is limited via this parameter in order to prevent HP-Tx from being emptied completely.

The number of times an urge frame will be retransmitted.

Support for terminal emulation within the application. The valid values are Yes/No.

Support for health check within the application. The valid values are Yes/No.

MDLC Network Layer

Network Layer

Number of paths the Network layer is allowed to learn. This parameter is for future use. In the current version, Network can learn only one path even if a different value is specified.

General Communication

Addr. range response for 'All RTU simulation' <Site ID +- Range> [0]:

Assigning alternate addresses to an RTU. If the basic address is X and the range is Y, then the unit responds to all calls in the range of {X,X+1,...,X+Y}. If the range is -Y, the unit responds to all calls in the range of {X-Y, X-Y+1, ..., X}.

This parameter is for field simulation in laboratory conditions and for the Dual CPU mechanism.

5-46

Site Configuration

MDLC Session Logical Channels

Application layer

The workspace allocated to MDLC applications (for the transmission and reception of data frames). The end-user is not expected to modify this parameter as it is reserved for the software engineer???s development needs. It enables the engineer to accurately determine the memory requirements of the MDLC applications.

The size of the stack to be allocated for the MDLC application manager task.

Presentation Layer

For future use.

Transport Layer

Number of retries at session oriented logical channel level after which the Transport Layer declares that transmission to destination site has failed.

When the source site sends frames to a destination site and receives a ???logical channel busy??? signal (because the channels are busy transmitting data from other applications that already accessed them), it retries as many times as determined in this parameter. After this pre-defined number of retries, the source site declares the channel as being ???busy???.

Number of MDLC frames that are sent in a single burst after which the Transport Layer waits for ACK from the destination site before it sends the next burst.

Number of MDLC frames the Transport Layer is capable of receiving from upper layers (Application, Presentation and Session) for transmission. When this number is reached, the Transport Layer signals to the application to stop sending frames until it makes room for more frames. This number should be equivalent to twice the size of a burst or more.

The number of MDLC frames the receiving site is capable of handling on their way to the upper layers. This number should be equivalent to twice the size of a burst or more.

The number of MDLC frames the receiving site is capable of handling on their way from the lower layers (Data Link Reception, Network, Transmission Multiplex).

5-47

Site Configuration

Data frames are the information stored in Txbuf in case of transmission, and in Rxbuf in case of reception.

The number of retries that should take place at source/destination level if an answer was not received for a transmission via SndFrm (and not via TxFrm).

The interval of time that should elapse between retries. This period of time starts after the Data Link layer of the MDLC protocol finalizes the transmission of a frame (that is, after it received an appropriate ACK or exhausted all retries at From/To level).

Enables the user to add a communication password to data frames. The value of this parameter must be identical in both the transmitting and receiving side.

For future use.

Event and Burst

The number of boxes allocated at any given time for transmitting data frames via the Burst and TxEvnt functions.

Number of retries to be performed by the RTU towards the central unit, if it does not receive ???Application Data-Ack from central??? to Burst or TxEvnt calls. If the value of the ???Application Data-Ack from central??? is NO, this parameter is irrelevant (because the system relies on ACK at Data Link level, that is, at From/To level, and does not need any further acknowledgments at RTU/Central Unit level).

The interval of time that should elapse between two retries from the RTU towards the central unit. (Retries may be requested if the RTU does not receive ???Application Data-Ack from central??? to Burst or TxEvnt calls. See previous parameter.)

This period of time starts after the Data Link layer of the MDLC protocol finalizes the transmission of a frame (that is, after it has received an appropriate ACK or exhausted all retries at From/To level).

If the value of the ???Application Data-Ack from central??? is NO, this parameter is irrelevant (because the system relies on ACK at Data Link level, that is, at From/To level, and does not need any further acknowledgments at RTU/Central Unit level).

The valid values are:

5-49

Site Configuration

Timers Hookups

The 10 msec task enables different modules to perform specific activities with a resolution of 10 msec. This is achieved by letting each module link itself to the 10 msec task. The number of service users (modules) depends on the configuration and sometimes it may be necessary to increase the value of this parameter (if the configuration includes more modules than the default number specified here).

Number of '10 mSec' ticks passed before declaring error <3-10> [4]:

The operating system is supposed to activate the 10 msec task every 10 msec. If it fails to activate the task as many times as the number specified in this parameter (for example, 4 means if the system fails to activate the task during 40 msec), an error message is sent to the Error Logger.

This is not a fatal error. If the system fails to activate the task this means that it is experiencing an unusual burden (in which case it is advisable to locate the origin of the problem).

Same as the ???Number of connected service-users with '10 mSec' device??? parameter for the 100 msec task. Not applicable for IP Gateway.

Number of '100 mSec' ticks passed before declaring error <3-10> [4]:

Same as the ???Number of '10 mSec' ticks passed before declaring error??? parameter for the 100 msec task.

Number of connected service-users with '1 Sec' device <10-100> [20]:

Same as the ???Number of connected service-users with '10 mSec' device??? parameter for the 1 sec task. Not applicable for IP Gateway.

Same as the ???Number of '10 mSec' ticks passed before declaring error??? parameter for the 1 sec task.

Number of connected service-users with '1 Min' device <10-100> [16]:

Same as the ???Number of connected service-users with '10 mSec' device??? parameter for the 1 min task. Not applicable for IP Gateway.

Same as the ???Number of '10 mSec' ticks passed before declaring error??? parameter for the 1 min task.

The number of ???C??? block 10 msec. timers that can be used. For details on how 10 msec. timers in ???C?????? block can be used, see ???C??? Toolkit manual. Not applicable for IP Gateway.

5-52

Site Configuration

The number of ???C??? block 100 msec. timers that can be used. For details on how 100 msec. timers in ???C?????? block can be used, see ???C??? Toolkit manual. Not applicable for IP Gateway.

Buffer and Queue Size

The size of the buffer that is used to store error messages.

Error messages are generated by modules to inform the user of unusual events that have taken place in the system. It is advisable to increase the buffer size if a large number of errors is expected.

The transmission queue of a user port is used for SEND purposes. This parameter determines the size of the queue. Increase the value if the number of bytes to be transmitted by SEND is expected to be greater than 200 during one SCAN of the ladder diagram.

Ladder Process Tasks

System Flags

5-53

Site Configuration

System Values

The ratio between the time allocated to the main process of the application (including higher priority tasks such as MDLC reception), and tasks of lower priority.

The objective of this parameter is to enable lower priority tasks to perform even when the application is busy.

At the end of the main process and after the timeout specified in this parameter, the system checks for bursts awaiting transmission. If the period of time between bursts has not yet elapsed, the possibility exists to add new bursts to the buffer during the next scan.

This parameter defined the maximum time that the ???event timer??? can be activated (in units of 10 msec).

The event timers can be activated via the SetTmr function in relation to events that have been received via GtEvnt. The timers and the events are accurate to 10 msec. The timers are activated when the event actually takes place (and not when GetEvent was performed).

Increasing the maximum time consumes about 4 bytes per time unit.

Together with the previous parameter, this parameter defines the number of events and event timers that can be received simultaneously.

Increasing the number of events consumes ~35 bytes per event.

The maximum number of frames that can be stored in the frame sequence device. If more frames arrive, an error is issued to the Error Logger.

The number of frames for which a burst can be created during the same scan.

The amount of memory reserved for dynamic allocations at runtime.

C programs require dynamic allocations. Therefore, the value of this parameter should be determined according to the amount of memory required by the C programs, or according to the number of C program blocks.

You can expand the regular site table (a Database Builder system table) using the dynamic site-table which is accessible via ???C??? Toolkit.

5-54

Site Configuration

'C??? application parameters

In addition to the 5 tasks defined by the system (main process, Task priority A...Task priority D), up to 10 additional tasks can be defined. These tasks can be activated via a user-defined C function which can be called with ucall. The tasks can be activated or suspended using a C routine. Each task allocates ??? 2KB of stack. For details consult the C Toolkit.

It is possible to execute MOSCAD_malloc from a ???C??? block, to hold the allocated buffer in named pointers between downloads (access function from ???C??? Toolkit), and to get it back after the download ends. This feature enables you to keep data between different downloads.

Number of slave ???C??? functions for session based protocol <0-255> [0]:

Number of ???C??? language functions to be supplied by the ???C??? application for session based protocol.

Number of ???C??? language functions to be supplied by the ???C??? application to the 10 millisecond task.

Number of ???C??? language functions to be supplied by the ???C??? application to the 100 millisecond task.

Number of ???C??? language functions to be supplied by the ???C??? application to the 1 second task.

Number of ???C??? language functions to be supplied by the ???C??? application to the 1 minute task.

Number of ???C??? language functions to be supplied by the ???C??? application to the Software Diagnostic utility.

Maximum buffer size in the heap used by the ???C??? application.

Maximum number of buffers in the heap used by the ???C??? application.

Number of ???C??? language functions to be supplied by the ???C??? application to the DB map.

Number of callback functions to be supplied by the ???C??? application for logging flash operations. The first entry in the table will always contain the Program callback function, the

5-55

Site Configuration

Allows the definition of the maximum size of the communication buffers (in bytes).

If you entered an incorrect range, Toolbox displays a dialog box with the valid parameter range. Click OK to dismiss the dialog box and enter the correct value.

Task Allocation

Allows the definition of overall concurrent application tasks.

Allows the definition of concurrent Command tasks (dedicated for sending commands).

Allows the definition of concurrent Data tasks (dedicated for polling RTUs and for downloading parameters).

Allows the definition of concurrent Service tasks (dedicated for sending/reading RTUs time).

If you entered an incorrect range, the Toolbox displays a dialog box with the valid parameter range. Click OK to dismiss the dialog box and enter the correct value.

Request Allocation

Allows the definition of overall pending requests, (must equal the combined sum of Pending CMD, Data and Service Requests).

Allows the definition of minimum pending command requests from the SCADA).

Allows the definition of minimum pending data requests from the SCADA).

Allows the definition of minimum pending service requests from the SCADA).

5-57

Network Configuration

mechanism is disabled, the failed link is considered to be restored after a specified period of time.

Routing over Alternative Direct Link

The Routing of Data Frames section above describes automatic routing between sites which are not directly connected. The system will also perform automatic alternative routing between nodes that are directly connected by more than one direct link (if one of them is failed). In previous versions, finding alternative communication routes across such systems was performed by the user application.

All relevant links in the example below were defined in the Network Configuration and downloaded to the units. RTU100 will choose a link which is not failed for communication with RTUs 1-99 (as will be done in communication between RTU4 and RTU 88.) Thus if RTU100 is unable to initiate communications with RTU2 over the radio link, due to a radio failure, it will automatically attempt to communicate using the dial link. If no alternative links exist, or if all fail, then the transmission will fail. In the case of a failed direct link, the recovery mechanism described above in Routing of Data Frames is performed, according to the parameter settings in the site configuration.

.

.

RTU 99

Routing over Direct Link is only possible with new versions of both the ToolBox and system. Note that if you have existing applications which try to transmit over alternate links, these should be modified to prevent redundancy.

When RTU101 tries to transmit to one of the RTUs (1-99), the routing is actually performed by RTU100. The behavior of the routing in the system, when one of the links to the designated RTU is failed, is exactly as described in Routing over Alternative Direct Link above.

5-59

Network Configuration

Network Configuration Window

To start Network Configuration, double-click the Network Configuration icon in the

IP Gateway ToolBox folder. Click on the New icon or select New from the File menu. The following is displayed.

The network configuration is defined in this window.

In the displayed table, you define the accessible (logical) links for every site that serves as a node. A site that uses two or more communication ports and does not serve as a node should not be defined in Network Configuration. If, for example, Site 1 is directly connected to Link 1 and to Link 2, both links are added to the Site entry in the table.

For each site, you may define up to six links (minimum two links to define a site as a communication node). Just click the Site ID box, type the Site ID, and then for each Link ID, open the drop-down list and select the appropriate value.

In the example below, Sites 1, 2, and 3 serve as nodes, each connected to two links. Data packets can be relayed from Site 1 to Site 2 over RSlink2. The DIAL link enables connection via dialup modem from Site 1 to any other site attached to a modem. From Site 3 to Site 2, LINE1 is used. To display a more detailed version of the configuration, with all possible communication through the site, see View As Text below.

5-60

Network Configuration

Icons

The following is the list of the available command icons.

5-61

Network Configuration

File Menu

The commands in the File menu are mainly designed to handle configuration files.

New

The New command (Network Configuration File menu) opens a new network configuration file. If more than one network configuration file is opened, they can be rearranged using commands in the Window menu or resized using the standard window operations.

Open

The Open command (Network Configuration, File menu) opens an existing network configuration file. After activating this command, the ToolBox displays the Open dialog box, as shown below.

The Open dialog box defaults to the Config sub-directory of the IP Gateway ToolBox (Itbox550) directory. The Config sub-directory is where the ToolBox stores configuration files by default.

The Open command allows you to open applications that have been developed under earlier ToolBox versions. You do not have to upgrade your applications in order to continue development under the new version.

Select the configuration file (see parameters below) and click OK to load it.

Dialog box parameters

Use the parameters in the order specified below. Normally you???ll only use the File Name parameter.

5-62

Network Configuration

Look in

If the currently displayed directory is not the correct one, double-click the drive letter at the right of the Look in list and locate the directory. To access sub-directories, double-click parent directories.

File Name

Type the name of the configuration file. the ToolBox automatically adds the .scf extension. Alternatively, locate the file name in the file list, and double-click the name.

Files of Type

This box shows the type (extension) of the files currently displayed in the File Name list. If the displayed file type ???filter??? is not .scf, open the drop-down list and select the .scf type.

Close

The Close command (Network Configuration, File menu) closes the current network configuration file.

Save

The Save command (Network Configuration, File menu) stores the current configuration.

If the file has not been saved at least once, the ToolBox opens the Save As dialog box where you assign a name to the configuration file.

If the file has been saved at least once, the ToolBox just saves the file.

Save As

The Save As command (Network Configuration, File menu) saves the current configuration under a different file name. Generally, you???ll use this command when you want to create a configuration file that is slightly different from an existing one (load the existing file, save it under a new name, and make the changes).

The command opens the dialog box shown below. This dialog appears also when you request to save a configuration file for the first time.

5-63

Network Configuration

Dialog box parameters

Use the parameters in the order specified below. Normally you???ll only use the File Name parameter.

Save in

If the currently displayed directory is not the correct one, double-click the drive letter at the right of the Save in Directories list and locate the directory. To access sub-directories, double- click parent directories.

File Name

Type the name of the configuration file you want to create, and click OK. The ToolBox automatically adds the .scf extension. If you specify the name of a configuration file that appears on the list, the ToolBox issues a message asking you whether you want to overwrite the existing file. Select Yes only if you want to replace the existing file with the new one.

Save as Type

This box shows the type (extension) of the files currently displayed in the File Name list. If the displayed file type ???filter??? is not .scf, open the drop-down list and select the .scf type.

Print

The Print command (Network Configuration, File menu) prints the contents of the displayed table to a printer, as defined in Print Setup.

Page Setup

The PageSetup command (Network Configuration, File menu) enables the user to define the page setup and printer to be used.

Exit

The Exit command (Network Configuration, File menu) exits the network configuration utility.

5-64

Network Configuration

Edit Menu

The Edit menu contains commands the affect the network configuration table in the main window.

Delete Rows

Deletes the selected row(s).

Sort Rows

Sorts the table in Site ID order.

Insert Rows

Opens a specified number of rows above the row specified in the dialog box.

Define Up To

From a specified Site ID, automatically defines a specified number of consecutive sites, each with the same configuration. The links associated with all of the sites are selected from a list by first selecting the link name (e.g. LINE 1) and then clicking on the right arrow. Links can be deselected by clicking on the left arrow.

Note: if you single-click with the right mouse button, you get the associated menu, i.e. the commands associated with the current state.

Authenticate Links

Authentication enables MOSCAD RTUs/IP Gateways to rely on the integrity of information sent on the MDLC network. An RTU/Gateway can be certain that received data was transmitted by the original sender and not by some other, unauthorized source. For background information on authentication, see the Advanced Features section of the MOSCAD Programming ToolBox Application Programmer manual.

When the Authenticate Links command is selected, a table of all links in the network is displayed, as shown in the Links Authentication Information window below.

5-65

Network Configuration

Note: If the Server ID or authentication keys are not defined for any link in the table, the authentication information will not be downloaded to the network.

It is possible to authenticate a link from the main Network Configuration screen by clicking the right mouse button and selecting Authenticate Link when the cursor is in a Link ID cell. The next time you open the Links Authentication Information window, the box to the right of that Link ID will be already checked. You will still have to define the server for the link, if one exists.

Authentication Keys

The Authentication Keys are defined for a given link within a given network. This enables the user to determine which subnetworks within the system will understand each other. When either the Has Keys or Has Aliases button is selected, the screen below is displayed.

Three keys of eight bytes each should be defined. Each byte can be entered as either a numeric value or as a string. To switch from numeric to string format, click the appropriate field. If the chosen number cannot be displayed in ASCII format, an asterisk will be displayed instead.

To use the same authentication keys for all links in the network, click the Force All Links button. In this situation, all data transmitted around the network will be understood by all authenticated RTUs.

5-67

Network Configuration

In case of an unreachable server (due to some communication problem), communication overhead will be higher as this parameter is lower (more frequent request transmissions). On the other hand, a client may be left with an invalid clock for at least the period of time defined in this parameter, if the server is unreachable.

This parameter defines the interval between two consecutive retries to transmit an ???After Restart??? message to the entire network (on the authenticated Links only). This parameter is relevant only to Server and Client/Server operation modes. Note that the number of retries is not set since a Server will try endlessly to transmit an After Restart message until it succeeds.

This parameter defines the maximum drift allowed between the timestamp contained in an authenticated received frame and the local clock or the receiving RTU. Hence this parameter defines the maximum drift between any two CPUs??? clocks. If Max Drift is set to x, then for a given time t0 (local receiver clock), a received frame must carry a timestamp in the range of t0 +/- x in order that it NOT be discarded. Recall that a received timestamp is added to the value of Maximum Network Delay and only then it is checked against the local receiver clock. The authentication mechanism of a received frame is stricter as Max Drift is set lower.

Note that the maximum drift may actually be smaller than the Max Drift parameter, because the incoming timestamp is compared to an internal generated timestamp and not to an actual clock. The internal timestamp is generated every TX Stamp Interval. Consider a situation where the Max Drift is set to 300 seconds and the TX Stamp Interval is set to 150 seconds. An RTU whose clock has drifted by 200 seconds may reject the received frame as invalid if its internal timestamp was generated 140 seconds previously.

This parameter defines the maximum of all delays of the authenticated links in the network. It is relevant to received frames only. If a frame carrying a timestamp with a value of t1 is received, the receiving RTU will add the value of Maximum Network Delay to t1 for the purpose of authenticating the frame. In most cases, this parameter should be set to zero.

Once the parameters have been set, click OK.

Edit Links Costs

This command is for future use.

Tools Menu

View As Text

The View As Text command (Network Configuration, Tools menu) opens the network configuration parameter values in textual form, as shown below. All standard Windows text file operations are available.

5-69

Network Configuration

The text file pictured above describes each link connected to NODE 1. From LINE 1 (known internally as LINK-21) communication is possible through that node to LINE 2 (LINK-22), LINE 3 (LINK-23), and LINE 4 (LINK-24). The file contains a similar entry for LINE 2, LINE 3, and LINE 4 respectively. Thus any other nodes connected to LINES 1,2, 3, or 4 can be reached from NODE 1.

Download

The Download command (Network Configuration, File menu) is used to download the currently open configuration file to an RTU.

After selecting the command, the ToolBox requires the password. Then it opens the following dialog box:

5-70

Network Configuration

Dialog box parameters

Site ID

Enter the Site ID of the unit to which the network configuration is to be downloaded.

Link ID

Enter the Link ID of the unit to which the network configuration is to be downloaded.

OK

Click this button to start the download process. While the Network Configuration tool is

communicating with the RTU, the icon at the top right hand corner of the Network Configuration window will be animated.

Font

The Font command (Network Configuration, Tools menu) is used to change the current settings for font name, style, size, etc.

View Menu

The View menu enables you to view or hide various screens from the utility window. Pull down the menu and click on an entry to toggle the viewing. The following views are available to the user.

Toolbar

The Toolbar displays the icons described under Icons.

Status bar

The Status bar displays the status messages at the bottom of the Network Configuration window.

Download window

The Download window displays a window with the progress and status of the download at the bottom of the Network Configuration window. This window can be dragged to a different area of the screen and can be closed by clicking on the X in the upper left-hand corner of the window. This window is read-only.

Window Menu

The Window menu enables the user to arrange the various screens within the Network Configuration window. The screens can also be moved, resized or closed as standard Windows. In addition to the commands below, the Window menu lists the currently open windows. The checked name is the active screen. By clicking on another filename, the user can change the active screen.

5-71

Network Configuration

Cascade

The Cascade command arranges the various screens in cascade style.

Tile

The Tile command arranges the various screens in tiled style.

Arrange Icons

The Arrange Icons command arranges any minimized screens on the bottom of the window.

Help Menu

The Help menu enables the user to view the version information and help files which relate to the Network Configuration tool.

Contents

The Contents opens the help files which describe the Network Configuration tool and other IP Gateway ToolBox utilities.

How to Use Help

The How to Use Help explains to the user how the IP Gateway ToolBox help is used.

About

The About displays the version information for the Network Configuration tool.

5-72

MDLC Links Configurator

The MDLC Links Configurator allows you to change the number of links assigned to each medium, such as lines, Rslinks, Radio links and zones.

Note: It is recommended that users not change the default values set by the manufacturer unless absolutely necessary. Be aware that the Links Configurator may change the physical value of each link. This may cause different treatment of links in certain configurations, such as Rslink as Radio or vice versa.

After activating the Links Configurator, close all ToolBox tools, stop the Communication Driver and then double-click the icon of the tool you want to reactivate.

The MDLC Links Configurator Window

To activate the MDLC Links Configurator, double-click the icon in the IP Gateway ToolBox folder. A dialog box like the one shown below is displayed:

5-73

MDLC Links Configurator

The first time you open the tool, two tabs will be available, Default and port.txt. The Default screen contains the values set by the manufacturer and cannot be modified. The port.txt screen above displays the (active) current configuration. This configuration file is initially the same as the Default, but both the content and the tab name can be modified.

At this point, you can choose to view either the Default dialog box or another existing dialog box (e.g. port.txt above), by clicking on the appropriate tab at the top of the screen.

To access another configuration (e.g. n1.txt above), simply click on the appropriate tab. You can open another configuration file or several files, using the Open option of the File menu.

Dialog box parameters- Communications Link Number

This section is used to change the number of links assigned to each medium.

5-74

MDLC Links Configurator

Number of free Links

Displays the number of free links in the current configuration. This is a protected field, and the displayed value cannot be changed.

Line

Displays the number of lines used in the current configuration. This is an unprotected field, and the displayed value may be changed. The minimum is two lines.

RSlink

Displays the number of Rslinks used in the current configuration. This is an unprotected field, and the displayed value may be changed. The minimum is one Rslink.

Radio

Displays the number of Radio links used in the current configuration. This is an unprotected field, and the displayed value may be changed. The minimum is one radio.

X.25

Displays the number of X.25 links used in the current configuration. This is a protected field, and the displayed value cannot be changed.

Dialog box parameters - Radio Zones Number

This section is used only to define the number of zones for each Radio link.

Number of free Radio Zones

Displays the number of free radio zones links in the current configuration. This field is updated automatically when the Number of Zones field changes.

Link Name

Use this field to select the particular radio link. Click the down arrow key to display the list of radio links defined, according to the Radio field. Select the desired radio link from the drop- down list box.

Zones Number

Displays the zone number corresponding to the radio link in the Link Name field. To change the value, click the down arrow key to display the drop-down list box and select the preferred zone number.

In the bottom section of the window, all zones defined in the current configuration are displayed with their corresponding radio links.

Icons

The following is a list of the available command icons.

5-75

MDLC Links Configurator

When you save a configuration file for the first time, the ToolBox displays the Save dialog box.

Type the name of the link configuration file you want to create, and click OK. The ToolBox automatically adds the .txt extension. If you specify the name of a link configuration file that appears on the list, the ToolBox issues a message asking you whether you want to overwrite the existing file. Select Yes only if you want to replace the existing file with the new one.

Save As

Saves the current link configuration information under a different file name. Use this command when you want to create a new link configuration file that is slightly different from an existing one. To do so, open an existing file, and click Save As in the File menu. The command opens the Save As dialog box as shown below.

To save the file under a different name, highlight the existing file name, type the new name and click OK. The ToolBox automatically adds the .txt extension. The Links Configurator program stores the current file under the new name on disk.

If you specify the name of a link configuration file that appears on the list, the ToolBox issues a message asking you whether you want to overwrite the existing file. Select Yes only if you want to replace the existing file with the new one.

Save All

Saves all open link configuration files. If a file has not been saved before, the ToolBox displays the Save Configuration dialog box. Enter the new link configuration file name in the File Name box and click OK.

Print

The Print command (MDLC Links Configurator, File menu) prints the contents of the link configuration file to a printer.

5-77

MDLC Links Configurator

Activate

Activates a different link configuration.

To activate another link configuration, use the Open command to display an existing link configuration file, then:

1.Click the tab of the desired configuration file at the top of the Links Configurator screen.

2.Open the File menu.

3.Choose the Activate command.

The ToolBox asks you to confirm that you want to activate another link configuration. Click Yes to activate the new configuration.

Activate Default

Activates the default link configuration. If you want to revert to the default link configuration:

1.Open the File menu.

2.Choose the Activate Default command.

The ToolBox asks you to confirm that you want to activate another link configuration. Click Yes to activate the default configuration.

Exit

Closes any open files and quits the MDLC Links Configurator. If a file has unsaved changes, an alert appears, asking whether to save the changes before exiting.

Help Menu

The Help menu enables the user to view the version information and help files which relate to MDLC Links Configurator tool.

Contents

The Contents opens the help files which describe the MDLC Links Configurator tool and other IP Gateway ToolBox utilities.

About

The About displays the version information for the MDLC Links Configurator tool.

5-78

Site Table

The Site Table utility enables the user to define the sites in the system with which the IP Gateway wishes to communicate. Unlike the network configuration which defines only those sites which are nodes, the Site table contains all the sites.

For each destination site, the user defines a logical address (Site ID), and the links (Link ID) through which it is connected. When sending data to another site, the user refers to the destination using the site index of the table.

Site Table Window

The Site Table Window allows you to define all sites in the system. To start the Site Table tool, double-click the Site Table icon in the IP Gateway Toolbox folder.

Click on the New icon or select New from the File menu to open a new Site table. The following is displayed. An existing Site table can also be opened and edited.

5-79

Site Table

For each site in the system, enter the Site ID, the number of retries to be performed and the number of seconds to wait between retries. For each site, enter the primary link ID, secondary link ID and the length of time to wait before an unresponsive link is considered invalid. Next, click on the Save icon or select Save/Save As from the File menu. Double-click in any cell to return to the default value.

Once the file is saved, it can be downloaded to the site.

Communication parameters

Local

When this box is checked, the Site table is downloaded to the locally connected site. The default setting for communication is Local. When this box is not checked, the Site table is downloaded to the remotely connected site, and the appropriate Site ID and Link ID must be specified.

Site ID:

When the Local box is not checked, the Site table is downloaded to a remote site at the specified Site ID connected to the PC via the specified Link ID.

Link ID:

When the Local box is not checked, the Site table is downloaded to a remote site connected to the PC via the specified Link ID.

5-80

Site Table

Dialog box parameters and functions

Site ID

Click in the cell to enter the Site ID for the site being added. (Note: The Site ID was defined for the site in its site configuration.)

Retries

Click in the cell to enter the number of attempts to be made to communicate with a non- responding site. The valid range of retries is 1-255. The default is 1.

Timeout

Double-click to define the time (in seconds) to wait between communication retries. The minimum value is 1 second; the maximum value is 255 seconds. The default is 30.

Primary Link ID

Click on the down arrow (or double-click in the cell) and select from the list box the link through which the site is connected to the network.

Primary Link Validity

The Gateway tests communication with the sites on a regular basis. If a site has not responded for a specific time interval, the link is considered unreachable.

Secondary Link ID

Click on the down arrow and select the proper link (other than the Primary) through which the RTU is connected to the network from the list box.

5-81

Site Table

Secondary Link Validity

The Gateway tests communication with the sites on a regular basis. If a site has not responded for a specific time interval, the link is considered unreachable.

Icons

The following is the list of the available command icons.

5-82

Site Table

Most of the icons are dimmed unless there is an open Site table file.

File Menu

The commands in the File menu are designed mainly for manipulating tables and exiting the application.

New

The New command clears the currently loaded file from the screen and opens a new file.

Open

The Open command opens an existing Site table file. After activating this command, the Toolbox displays the dialog box shown below. The Open dialog box defaults to the config sub-directory of the Toolbox directory. The config sub-directory is where the Toolbox stores the Site table files by default.

If the desired table is listed, double-click it. Otherwise, type the path and file name in the File Name box and click OK.

The Toolbox automatically adds the .stb extension.

Close

The Close command closes the current open Site table file. If the file has unsaved changes, an alert appears, asking whether to save the changes before closing.

5-83

Site Table

Abort

This command aborts the download of the Site table data to the specified site.

Exit

The Exit command closes any open files and quits the Site table program. If a file has unsaved changes, an alert appears, asking whether to save the changes before exiting.

Click the appropriate button.

Edit Menu

The Edit menu contains commands that affect the Site table list.

Cut

Cuts selected row(s) from the current Site Table file to the system clipboard.

Copy

Copies selected row(s)/column(s) from the current Site Table file to the system clipboard.

Paste

Pastes selected row(s)/column(s) from the current Site Table file to the system clipboard.

Insert Site

Opens a new row above an existing row to insert a new site.

Insert Group of Sites

Inserts a single site or several sites at once. When activated, the following screen is displayed:

5-85

Site Table

Dialog box parameters and functions

Number of Sites

Double-click and enter the number of sites you want to add to the Site table.

First Site ID

Double-click and enter the first Site ID in the current group.

Retries

Double-click to enter the number of attempts to be made to communicate with a non- responding site. The default value is 1. The valid range of retries is 1-255.

Time-out

Double-click to define the time (in seconds) to wait between communication retries. The minimum value is 1 second, the maximum value is 255 seconds. The default value is 30 seconds.

Primary Link ID

Click on the down arrow and select the proper Link ID from the list box. The default Link ID is Radio 1.

Primary Link Validity

Double-click to define the time to wait for a response from a RTU. The format is HHH:MM:SS. If there is no response within the specified time, the link is marked as unreachable.

Secondary link ID

Click on the down arrow and select the proper Link ID (other than the Primary) from the list box. The default Link ID is Radio 1.

5-86

Site Table

Secondary Link Validity

Double-click to define the time to wait for a response from a RTU. The format is HHH:MM:SS. If there is no response within the specified time, the link is marked as unreachable.

Delete Site

Deletes the selected site.

Delete Group of Sites

You may use this command to delete either an individual site, or several sites at once. .

To delete a single site:

???Click the desired site.

???Select the Delete Group of Selected Sites command or click on the icon.

To delete two or more sites at the same time:

???Select the sites you wish to delete by holding the left mouse button while dragging the mouse until all sites are highlighted.

???Select the Delete Group of Selected Sites command or click on the icon.

Change Retries Value

Changes the number of retries of the selected site(s).

???Double-click in the retries cell of the desired Site ID and enter the new retries value;

???Or select several retries cells at once by dragging with the left mouse button until all sites to be changed are highlighted. Select the Change Retries Value command or click on the icon.

???Enter the desired number of retries in the dialog as shown below and click OK.

5-87

Site Table

Change Timeout Value

Changes the timeout value of the selected site(s).

???Double-click in the timeout cell of the desired Site ID and enter the new timeout value;

???Or select several timeout cells at once by dragging with the left mouse button until all sites to be changed are highlighted. Select the Change Timeout Value command or click on the icon.

???Enter the new timeout value in the dialog box as shown below and click OK.

Change Primary Link ID Value

Changes the Primary Link ID of the selected site(s).

To change the Primary Link ID of a single site:

???Double-click in the Primary Link ID cell of the desired Site ID or click on the down arrow to the right of the cell.

???Select the proper Link ID from the displayed list box and click OK.

To change the Primary Link ID of several sites at once:

???Select several Primary Link ID cells at once by dragging with the left mouse button until all sites to be changed are highlighted.

???Select the Change Primary Link ID Value command or click on the icon.

???Click on the down arrow and select the proper Link ID from the displayed list box as shown below and click OK.

5-88

Site Table

Change Primary Link Validity Value

Changes the primary link validity value of the selected site.

???Double-click in the desired Primary Link Validity cell and enter the new value;

???Or select several Primary Link Validity cells at once by dragging with the left mouse button until all sites to be changed are highlighted. Select the Change Primary Link Validity Value command or click on the icon.

???Enter the new link validity value in the dialog box as shown below and click OK.

Change Secondary Link ID Value

Changes the Secondary Link ID of the selected site(s).

To change the Secondary Link ID of a single site:

???Double-click in the Secondary Link ID cell of the desired Site ID or click on the down arrow to the right of the cell.

???Select the proper Link ID from the displayed list box and click OK.

To change the Secondary Link ID of several sites at once:

???Select several Secondary Link ID cells at once by dragging with the left mouse button until all sites to be changed are highlighted.

???Select the Change Secondary Link ID Value command or click on the icon.

???Click on the down arrow and select the proper Link ID from the displayed list box as shown below and click OK.

5-89

Site Table

Change Secondary Link Validity Value

Changes the secondary link validity value of the selected site.

???Double-click in the desired Secondary Link Validity cell and enter the new value;

???Or select several Secondary Link Validity cells at once by dragging with the left mouse button until all sites to be changed are highlighted. Select the Change Secondary Link Validity Value command or click on the icon.

???Enter the new link validity value in the dialog box as shown below and click OK.

Sort By Site ID

Arranges the cells in the Site Table by site order.

Default Center

The Default Center command enables the user to set up the Site table entry for the default central for burst to central. This screen is read-only.

5-90

Site Table

Dialog box parameters and functions

Reserved Line

The row in the Site table where the default center will be defined.

Site ID

The Site ID for the site being defined as the default center. (Note: The Site ID was defined for the site in its site configuration.)

Retries

The number of attempts to be made to communicate with a non-responding site.

Time-out

The time (in seconds) to wait between communication retries.

Primary Link ID

The link through which the site is connected to the network.

Primary Link Validity

The Gateway tests communication with the sites on a regular basis. If a site has not responded for a specific time interval, the link is considered unreachable.

Secondary Link ID

The link (other than the Primary) through which the RTU is connected to the network from the list box.

Secondary Link Validity

The Gateway tests communication with the sites on a regular basis. If a site has not responded for a specific time interval, the link is considered unreachable.

View Menu

The following views are available to the user. Click on an entry to select it, and a check mark will appear on the menu. The associated view is then displayed on the Site Table window.

Toolbar

The Toolbar displays the icons described under Icons.

Table bar

The Table bar displays, at the top of the Site Table window, the commands used to manipulate the Site Table cells.

Site bar

The Site bar displays the Site ID/Link ID at the top of the Site Table window and enables the user to define the site (local/remote) to which it will download the Site table.

Status bar

The Status bar displays the status messages at the bottom of the Site Table window.

5-91

Site Table

Window Menu

The Window menu enables the user to arrange the various screens within the Site Table window. The screens can also be moved, resized or closed as standard Windows. In addition to the commands below, the Window menu lists the currently open windows. The checked name is the active screen. By clicking on another filename, the user can change the active screen.

Cascade

The Cascade command arranges the various screens in cascade style.

Tile

The Tile command arranges the various screens in tiled style.

Arrange Icons

The Arrange Icons command arranges any minimized screens on the bottom of the window.

Help Menu

The Help menu enables the user to view the version information and help files which relate to the Site Table tool.

Contents

The Contents command opens the help files which describe the Site Table tool and other IP Gateway Toolbox utilities.

How to Use Help

The How to Use Help explains to the user how the IP Gateway Toolbox help is used.

About

The About command displays the version information for the Site Table tool.

5-92

SNMP Configurator

Manager host IP

The IP Gateway sends, without the need for registration, SNMP Trap_PDUs to the SSC manager with ???Manager host IP??? address.

Manager Port ID

The IP Gateway sends SNMP Trap_PDUs to the SSC manager with non-standard SNMP Port ID.

MIB II

The following four fields are part of MIB II parameters that define the contact person???s name and the location of the Gateway, as well as the Community Strings that serve as passwords for accessing the Gateway.

Contact

The name of the contact person responsible for setting, configuring and maintaining the IP Gateway and all NFM RTUs and devices installed at the communication sites.

Location

For maintenance purposes, the address of the location of the IP Gateway device should be provided. The NMC application or the MIB Browser can retrieve this address by using the IP Gateway MIB.

Community Read

The definition of the Community String Read provides a READ security password to the IP Gateway. The NMC should supply the same Community String (case sensitive) in order to read information from the IP Gateway: (Get_PDU/Get_Next_PDU Requests PDUs) and for sending Traps.

Community Write

The definition of the Community String Write provides a WRITE security password to the IP Gateway. The NMC should supply the same Community String (case sensitive) in order to write information to the IP Gateway: Set_PDU Request.

DB refresh interval[s]

The database refresh interval specifies the refresh (validity) interval in seconds of the data received from the sites in the internal IP Gateway cache. The data is discarded after this interval expires.

Icons

File menu, New command

File menu, Open command

File menu, Save command

File menu, Download command

File menu, Upload command

5-94

SNMP Configurator

File Menu

The commands in the File menu are designed mainly for managing SNMP Configuration files and exiting the application. File menu commands are:

New

The New command clears the current settings from the main window. If you made changes to the current settings without saving them, the SNMP Configurator program displays a confirmation screen, asking if you want to save the data. Click the appropriate button.

Open

The Open command opens an existing SNMP Configuration file. After activating this command, Toolbox displays the Open dialog box. The Open dialog box defaults to the config sub-directory of the Toolbox (itbox550) directory and to the .snm type files. The config sub- directory is where Toolbox stores SNMP Configuration files by default. Locate the file name in the file list, and double-click the name.

Save

The Save command stores the current SNMP Configuration parameters that appear on the main screen. If the file has not been saved at least once, Toolbox opens the Save As dialog box where you assign a name to the SNMP Configuration file. If the file has been saved at least once, Toolbox just saves the file.

Save As

The Save As command saves the current download settings under a different file name. Generally, you'll use this command when you want to create a SNMP Configuration file that is slightly different from an existing one (load the existing file, save it under a new name, and make the changes).

The command opens the Save As dialog box. This dialog appears also when you request to save a configuration file for the first time.

Type the name of the SNMP Configuration file you want to create, and click OK. Toolbox automatically adds the .snm extension. If you specify the name of a SNMP Configuration file that appears on the list, Toolbox issues a message asking you whether you want to overwrite the existing file. Select Yes only if you want to replace the existing file with the new one.

Download

The Download command is used to download a SNMP Configuration file to the IP Gateway unit (to be stored in the FLASH memory in the CPU module). You can download to an IP Gateway unit directly connected to the Toolbox computer, or to a remote IP Gateway unit.

This command also enables you to change the Site ID and system address of the IP Gateway unit. Before activating the Download command:

5-95

SNMP Configurator

???Make sure that you have loaded the correct configuration file - the one that contains the

configuration for the IP Gateway unit you are communicating with. Use the Open command to open a configuration file.

???Ensure that the Toolbox computer is ready to communicate.

After you select Download, Toolbox asks you to specify the communication password, if this is the first time that the Communication Driver is used. If the Communication Driver was activated before, no password is required. Following the entry of the correct password, the Download SNMP Configuration dialog is displayed.

Local

Select this parameter if the Toolbox computer is locally connected to the IP Gateway.

Remote

Select this parameter if the Toolbox computer is connected to a remote IP Gateway. This selection enables the Site ID and Link ID parameters.

Site ID, Link ID

To configure a remote site, specify the Site ID, then open the Link ID drop-down list and select the appropriate Link ID.

Download button

After entering the parameters, click this button to download the configuration file. Toolbox displays the download progress, as shown below.

5-96

SNMP Configurator

This screen records the ongoing activity of the SNMP Configuration downloading process from the Toolbox computer to the IP Gateway unit. Click Abort to abort the download.

If the Download ended successfully, the "Download finished successfully" message will display in the output screen. Click OK to return to the Download SNMP Configuration screen.

In case of a malfunction, the corresponding error message will be displayed.

At the end of this operation, the IP Gateway builds the software object entities according to the users definitions.

Close button

Click this button to stop the download process.

5-97

SNMP Configurator

Upload

The Upload command is used to read the SNMP configuration of a site into Toolbox. You can upload from the IP Gateway directly connected to the Toolbox computer, or from a remote IP Gateway unit.

Before you activate the Upload command, ensure that the Toolbox computer is ready to communicate. After you select Upload, Toolbox asks you to specify the communication password, if this is the first time that the Communication Driver is used. If the Communication Driver was activated before, no password is required. Following the entry of the correct password, the Upload SNMP Configuration dialog is displayed.

Local

If the Toolbox computer is locally connected to the IP Gateway, select this parameter.

Remote

If you want to upload the configuration of a remote site, click this parameter.

Site ID, Link ID

To upload the configuration of a remote site, specify its Site ID, then open the Link ID drop- down list and select the appropriate Link ID. The Toolbox displays the following screen.

5-98

SNMP Configurator

This screen records the ongoing activity of the SNMP Configuration uploading process from the IP Gateway unit to theToolbox computer.

Click OK to return to the Upload SNMP Configuration screen.

Exit

The Exit command closes any open files and quits SNMP Configurator.

If a file has unsaved changes, an alert appears, asking whether to save the changes before exiting.

Click the appropriate button.

Help Menu

This menu enables you to view the version information and help files which relate to the SNMP Configurator utility.

Contents

The Contents command opens the help files which describe the SNMP Configurator tool and other IP Gateway utilities.

Using Help

The Using Help command explains to the user how the IP Gateway help is used.

About

The About command displays the version information for the SNMP Configurator tool.

5-99

Downloader

The Downloader utility enables you to download multiple blocks or files needed to configure the IP Gateway. You can specify the names of files to download and save the list of names in a file (.ini) which can be reused.

The Downloader is also used to upgrade the system software of the IP Gateway. An alternative method of upgrading the system software is described in the IP Gateway Web Operation chapter below.

Downloading Files

After activating the utility from the ToolBox folder, the following dialog box is displayed.

To define a session, click on the Add Session icon or select Add New Session from the Edit menu. The initial/default download settings file will be named download.ini. To open an existing download settings file, click on the Open icon or select Open from the File menu. An example of a session is shown below:

5-100

Downloader

Required unit type

Specify the unit type to which the files are to be downloaded. The only possible value is:

IP Gateway

Flash Erase type

The IP Gateway hardware does not include EPROMs. Instead, its software is stored on Flash memory chips. In order to load and burn the Gateway software and the Gateway configuration, a small kernel software file was developed, and is factory-installed in the IP Gateway. This kernel includes a unique Ethernet address and resides on a read-only Kernel partition of the Flash memory.

Other partitions of the IP Gateway Flash memory are:

CODE (system) partition

CONFIGURATION (parameters) partition.

Loading a new version of the Gateway software is done using the Downloader utility, which downloads the Gateway programs into the Code partition. Before loading the new software, the old version should be erased from the Flash memory, using the Erase flash and preserve siteConf option.

Occasionally, it is necessary to erase the Gateway configuration in order to restore the default configuration. In such cases, the old configuration should be erased from the Configuration partition, by using the Erase all flash before download option.

The erasing and loading of the Gateway software requires communication between Port-2B in the IP Gateway and Port COM1 in the PC, as shown in the IP Gateway Toolbox Connection figure below:

Specify whether the flash memory should be erased before downloading and whether the site configuration should be preserved. The possible values are:

Don???t erase flash before download (default)

Erase all flash before download

Erase flash and preserve siteConf

5-103

Downloader

Don???t Erase Flash Before Download

The download operation does not erase the contents of the flash memory.

Erase All Flash Before Download

Causes the utility to erase the contents of the flash memory before the download.

Erase Flash and Preserve SiteConf

Causes the utility to erase the contents of the flash memory, except for the site configuration data, before the download.

Unit Reset

Specify whether the IP Gateway should be reset after downloading or under what circumstances the IP Gateway should be reset. The only possible values is:

Reset after total download

If you have changed the site ID, you must first download the site configuration alone, with the modified ID. If you want to download more data, repeat the Download operation for the additional blocks (do not download the site configuration together with the other blocks).

Log File

Specifies the name of the file where the download session is logged.

New Site ID

Enables the user to change the Site ID of the IP Gateway. The Site ID defines the unit???s logical address, and it may range from 1 to 65,287. By default, this value is 1. This parameter is only visible when adding a site configuration file to the session. If the site configuration file is deleted from the session, this parameter will also be deleted.

System Address

The system address is the physical base address assigned to the whole system, and may range from 1 to 65,287. The base address is used in broadcast transmissions. By default, this value is 0. This parameter is only visible when downloading the site configuration. If the site configuration file is deleted from the session, this parameter will also be deleted.

Files

Specify the files to be downloaded to the IP Gateway. The files can include Site Configuration (.cfg), Network Configuration (.scf), Phone Book (.tel), Sites Table (.stb), SNMP Configuration (.snm), Host Table (.hst), IP Conversion Table (.ipc), DataTac (RNC) Modem ID Table (.rnc), NTP Configuration (.ntp). A new version of the system software (.krl) can also be downloaded in a separate System Download session.

Specifying files to be downloaded:

First choose a file type for the file to be downloaded from the File Type choice list at the bottom of the Directory bar.

Find the desired file name on the computer, using the Drive parameters described below. Drag the file name to the session text area or right-click on the file and select Add to the

5-104

Downloader

File Name

Enter the name of the download settings file. The ToolBox automatically adds the .ini extension. Alternatively, locate the file name in the file list, and double-click the name.

Files of Type

This box shows the type (extension) of the files currently displayed in the File Name list. If the displayed file type ???filter??? is not .ini, open the drop-down list and select the .ini type.

Open

The Open command (Downloader, File menu) opens an existing download settings file. After activating this command, Downloader displays the Open dialog box, as shown below.

The Open dialog box defaults to the config sub-directory of the ToolBox (Itbox550) directory, and to the .ini type files (download settings files). The config sub-directory is where the ToolBox stores download settings files by default.

Select the download settings file (see parameters below) and click OK to load it. If another file is open, it will be closed and replaced by the selected file. If changes were made to the open file, you will first be prompted to save the changes.

Dialog box parameters

Use the parameters in the order specified below. Normally you???ll only use the File Name parameter.

Look in

If the currently displayed directory is not the correct one, double-click the arrow to the right of the Look in parameter and locate the drive/directory. To access sub-directories, double-click parent directories.

File Name

Enter the name of the download settings file. The ToolBox automatically adds the .ini extension. Alternatively, locate the file name in the file list, and double-click the name.

5-109

Downloader

Files of Type

This box shows the type (extension) of the files currently displayed in the File Name list. If the displayed file type ???filter??? is not .ini, open the drop-down list and select the .ini type.

Save

The Save command (Downloader, File menu) saves the current download file. The initial/default download file is called download.ini.

If an existing download file is opened or a new file is created, the changes must be saved before performing the download. If no save is done, you will be prompted to save the file.

Save As

The Save As command (Downloader, File menu) saves the current download settings under a different file name. Generally, you???ll use this command when you want to create a download settings file that is slightly different from an existing one (load the existing file, save it under a new name, and make the changes).

For a standard download settings file, the command opens the dialog box shown below. An open system file can also be saved under a different name using the Save As command, but the default directory and file type in the dialog box will be different.

Dialog box parameters

Use the parameters in the order specified below. Normally you???ll only use the File Name parameter.

Save in

If the currently displayed directory is not the correct one, double-click the arrow to the right of the Look in parameter and locate the drive/directory. To access sub-directories, double-click parent directories. The default directory for .ini files is the Config subdirectory. The default directory for .krl files is the System subdirectory.

5-110

Downloader

File Name

Type the name of the download settings file you want to create, and click OK. The ToolBox automatically adds the .ini extension to download setting files and .krl to system files. If you specify the name of a download settings file that appears on the list, the ToolBox issues a message asking you whether you want to overwrite the existing file. Select Yes only if you want to replace the existing file with the new one.

Save as type

This box shows the type (extension) of the files currently displayed in the File Name list. The default type for download setting files is .ini. The default type for system files is .krl. If the displayed file type ???filter??? is not correct, open the drop-down list and select the correct type.

Close

The Close command (Downloader, File menu) closes the current open download/system file.

Open System File

The Open System File command (Downloader, File menu) opens an existing a system file (.krl). After activating this command, Downloader displays the dialog box below.

The dialog box defaults to the system sub-directory of the ToolBox (Itbox550) directory, and to the .krl type files (system files). The system sub-directory is where the ToolBox stores system files by default.

Select the system file (see parameters below) and click OK to load it.

5-111

Downloader

the Downloader window have been rearranged/resized by the user, they will appear in those places/sizes the next time the Downloader is started.

Edit Menu

The Edit menu contains the following commands which are applicable for download settings files only. In System sessions, only the Communication Port and Data Speed parameters can be edited, and this is done using choice lists, not the Edit menu.

Download This session

Downloads the current session to the IP Gateway. While the Downloader tool is

communicating with the IP Gateway, the icon at the top right hand corner of the Downloader window will be animated.

Rename Session

Renames the current session.

Add Session

Adds a new session to the current active download file.

Copy Session

Copies selected session from the current download settings file to the system clipboard.

Paste Session

Pastes session from the system clipboard to the selected cells in the current download settings file.

Cut Session

Cuts selected session from the current download settings file to the system clipboard.

Delete

Deletes session from the current download settings file.

View Menu

The following views are available to the user. Click on an entry to select it, and a check mark will appear on the menu. The associated view is then displayed on the Downloader window.

5-113

Downloader

Toolbar

The Toolbar displays the icons described under Icons.

Status bar

The Status bar displays the status messages at the bottom edge of the Downloader window. This message area is read-only.

Directory bar

The Directory bar displays a window with the list of directories, by default, to the left of the Downloader window. The user can select files to download, using the Drive and Files Type boxes. This window can be dragged to a different area of the screen and can be closed by clicking on the X in the upper right hand corner of the window.

Download bar

The Download bar displays a window with the progress and status of the download at the bottom of the Downloader window. This window can be dragged to a different area of the screen and can be closed by clicking on the X in the upper left-hand corner of the window. This window is read-only.

Help Menu

This menu enables you to view the version information and help files which relate to the Downloader utility.

Contents

The Contents command opens the help files which describe the Downloader utility and other IP Gateway ToolBox utilities.

How to Use Help

The How to Use Help explains to the user how the IP Gateway ToolBox help is used.

About

The About command displays the version information for the Downloader utility.

5-114

Dial Up

In order for the changes to the Dial Up Utility to take effect, close all Toolbox tools and Stop Communication Driver.

Dial Up Window

To start the program, double-click the Dial Up icon in the IP Gateway Toolbox folder. After the correct password is entered, the Dial Up screen is opened. A new or existing Dial Up file can be opened (using the New or Open commands or icons), and entries can be input as shown below. Several Dial Up files can be opened at the same time.

Icons

The following is the list of the available command icons.

5-117

Dial Up

Edit menu, Copy command

Edit menu, Paste command

File menu, Print command

Help menu, About command

Phone menu, Dial Up command

Phone menu, Hang Up command

Edit menu, Insert Row command

Edit menu, Delete Row command

Edit menu, Sort command

Dialog box parameters and functions

Name

A logical name of the addressed site.

Phone Number

The phone number at the addressed site. If a pulse phone is to be used, you should enter ???p??? before the phone number. Refer to the modem manual for information about codes (such as wait, pause, etc.) to be added to the phone number.

Description

A free-format field for describing the addressed site.

File Menu

The File menu commands enable you to save phone numbers to a file and to carry out file operations.

New

The New command opens a new dial up file. If an existing file is currently displayed, the new dial up file will be opened in front of it. To view the previous file, simply minimize, close or resize the new file. Multiple windows can be displayed simultaneously.

Open

The Open command opens an existing file. After activating this command, Toolbox displays the Open dialog box, as shown below.

5-118

Dial Up

The Open dialog box defaults to the config sub-directory of the Toolbox (itbox550) directory. The config sub-directory is where Toolbox stores dial-up files by default.

Select the configuration file (see parameters below) and click Open to load it.

Dialog box parameters

Use the parameters in the order specified below. Normally you???ll only use the File Name parameter.

Look in

If the currently displayed directory is not the correct one, double-click the arrow to the right of the Look in parameter and locate the drive/directory. To access sub-directories, double-click parent directories.

File Name

Type the name of the dial up file. ToolBox automatically adds the .dlp extension. Alternatively, locate the file name in the file list, and double-click the name.

Files of Type

This box shows the type (extension) of the files currently displayed in the File Name list. If the displayed file type ???filter??? is not .dlp, open the drop-down list and select the .dlp type.

Close

The Close command closes an existing file.

Save

The Save command stores the current dial-up file.

If the file has not been saved at least once, Toolbox opens the Save As dialog box where you assign a name to the file. (See below.)

If the file has been saved at least once, Toolbox just saves the file.

5-119

Dial Up

Save As

The Save As command saves the current dial-up information under a different file name. Generally, you???ll use this command when you want to create a dial-up file that is slightly different from an existing one (load the existing file, save it under a new name, and make the changes).

The command opens the dialog box shown below. This dialog also appears when you request to save a file for the first time.

Dialog box parameters

Use the parameters in the order specified below. Normally you???ll only use the File Name parameter.

Look in

If the currently displayed directory is not the correct one, double-click the arrow to the right of the Look in parameter and locate the drive/directory. To access sub-directories, double-click parent directories.

File Name

Type the name of the dial up file you want to create, and click OK. ToolBox automatically adds the .dlp extension. If you specify the name of an existing dial up file, ToolBox asks you if you want to overwrite the existing file. Select Yes only if you want to replace the existing file with the new one.

Files of Type

This box shows the type (extension) of the files currently displayed in the File Name list. If the displayed file type ???filter??? is not .dlp, open the drop-down list and select the .dlp type.

Print

This command prints the current dial up file to your standard system printer. If no printer is set up, see Windows Help or your system administrator.

5-120

Dial Up

Merge

The Merge command combines two dial-up files. Follow these steps:

1.Open one of the files.

2.Open the File menu and select the Merge command. The following is displayed.

3. In the Merge dialog box, double-click the name of the other dial-up file.

Note that Dial Up adds the contents of the second file to the first. The current file is the first file. You can Save or Save As.

Exit

The Exit command exits the Dial Up utility.

5-121

Dial Up

Edit Menu

The edit menu contains commands that affect the dial-up list in the main window.

Cut

Cuts selected block of cells from the current dial up file to the system clipboard.

Copy

Copies selected block of cells from the current dial up file to the system clipboard.

Paste

Pastes block of cells from the system clipboard to the selected cells in the current dial up file.

Insert Row

Opens a new row above an existing row.

Delete Current Row

Deletes the current row from the file.

Sort

Sorts the file entries in Name order.

View Menu

The View menu enables you to view or hide the Toolbar or Status Bar from the utility window. Pull down and select the entry to toggle the viewing.

Toolbar

The Toolbar displays the icons described under Icons.

Status bar

The Status bar displays the status messages at the bottom of the Dial Up window.

Phone Menu

This menu includes commands for dialing and hanging up.

5-122

Dial Up

Dial Up

Select a row and then this command to dial the corresponding phone number. If a channel is currently open, the dial up utility asks you to close it first.

Hang Up

Use this command to disconnect the telephone line. The line is not automatically disconnected when you close the Dial Up window.

Window Menu

This menu enables you to arrange and view the open files as desired, using standard Windows commands.

Cascade

The Cascade command arranges the various screens in cascade style.

Tile

The Tile command arranges the various screens in tiled style.

Arrange Icons

The Arrange Icons command arranges any minimized screens on the bottom of the window.

Help Menu

This menu enables you to view the version information and help files which relate to the Dial Up utility.

Contents

The Contents command opens the help files which describe the Dial Up tool and other IP Gateway utilities.

How to Use Help

The How to Use Help explains to the user how the IP Gateway help is used.

About Dial Up

The About command displays the version information for the Dial Up tool.

5-123

Site Date & Time

Site Menu

The Site menu enables the user to perform commands on the Site Date & Time screens.

New

The New command opens a new Site Date & Time screen. If an existing file is currently displayed, the new Site Date & Time screen will be opened in front of it. Screens open in a cascade, but can be moved around the Site Date & Time window. (See Window Menu.)

To view the previous file, move, minimize, close or resize the new file. Multiple windows can be displayed simultaneously. Each new screen is numbered sequentially (i.e. Site Date & Time[1], Site Date & Time[2], etc.)

Close

The Close closes the current Site Date & Time screen.

Exit

The Exit command exits the Site Date & Time utility.

Actions Menu

The following actions are available to the user.

Get

The Get command retrieves the current Date & Time from the IP Gateway. During the retrieval, the string ????? ?? ????? will be displayed in the Site Date & Time Field. If the get is successful, the IP Gateway Date & Time will be displayed in the Site Date & Time Field. If the get fails, a message ???No Communication??? will be displayed.

Set

The Set command writes the current Date & Time of the host PC to the IP Gateway. During the write process, the string ????? ?? ????? will be displayed in the Site Date & Time Field. If the set is successful, the updated Date & Time will be displayed in the Site Date & Time field. If the set fails, a message ???No Communication??? will be displayed.

Sync

The Sync command sends a message to synchronize all sites in the Network with the Date & Time of the host PC. During the sync process, the string ????? ?? ????? will be displayed in the Site Date & Time Field. If the sync is successful, the updated Date & Time will be displayed in the Site Date & Time Field.

5-126

Site Date & Time

View Menu

The following views are available to the user. Click on an entry to select it, and a check mark will appear on the menu. The associated view is then displayed on the Date & Time window.

Toolbar

The Toolbar displays the icons described under Icons.

Status bar

The Status bar displays the status messages at the bottom of the Site Date & Time window.

Window Menu

The Window menu enables the user to arrange the various screens within the Date & Time window. The screens can also be moved, resized or closed as standard Windows. In addition to the commands below, the Window menu lists the currently open windows. The checked name is the active screen. By clicking on another filename, the user can change the active screen.

New Window

The New Window command creates a new screen within the Date & Time window and displays it on top of any existing windows. This window is another instance of an existing window and will be numbered sequentially (i.e. Site Date & Time[1]:2)

Cascade

The Cascade command arranges the various screens in cascade style.

Tile

The Tile command arranges the various screens in tiled style.

Arrange Icons

The Arrange Icons command arranges any minimized screens on the bottom of the window.

Help Menu

The Help menu enables the user to view the version information and help files which relate to the Date & Time tool.

Contents

The Contents command opens the help files which describe the Date & Time tool and other IP Gateway utilities.

5-127

Site Date & Time

How to Use Help

The How to Use Help explains to the user how the IP Gateway help is used.

About Site Date

The About command displays the version information for the Date & Time tool.

5-128

Phone Book

The Phone Book utility allows you to conduct a session with another unit via a telephone line. The utility connects to the unit as any other unit or link in the system (using Site ID and Link ID). After you activate Phone Book from the Program Manager, the following is displayed.

The utility opens with an empty phone book. You can create a new phone book or load an existing one and type in changes or additions.

Icons

The following is the list of the available command icons.

5-129

Phone Book

File menu, Print command

Help menu, About command

Help menu, Help command

Edit menu, Insert Row command

Edit menu, Delete Row command

Edit menu, Sort command

File menu, Download command

Edit menu, Abort command

Dialog box parameters and functions

Site Id

Type or edit the site ID of the unit.

Phone Number 1, 2, 3

You can enter up to three telephone numbers for each site. The phone number can hold up to 50 characters.

The valid characters are: 1234567890*#ABCDabcdPTWptw and the comma (,) which is used for pausing. Note P or p are used form pulse dialing and T or t for tone dialing.

File Menu

You can perform all the basic file operations using the commands of the File menu. After opening the menu, the following commands are displayed:

New

The New command opens a new phone book file.

5-130

Phone Book

Look in

If the currently displayed directory is not the correct one, double-click the arrow to the right of the Look in parameter and locate the drive/directory. To access sub-directories, double-click parent directories.

File Name

Type the name of the dial up file. ToolBox automatically adds the .tel extension. Alternatively, locate the file name in the file list, and double-click the name.

Files of Type

This box shows the type (extension) of the files currently displayed in the File Name list. If the displayed file type ???filter??? is not .tel, open the drop-down list and select the .tel type.

After loading the file, you can edit existing data by direct typing or using the Edit menu command, or add new telephone numbers.

Close

The Close command closes an existing file.

Save

The Save command stores the current phone book.

If the file has not been saved at least once, ToolBox opens the Save As dialog box where you assign a name to the phone book file.

If the file has been saved at least once, ToolBox just saves the file.

Save As

The Save As command saves the current phone book under a different file name. Generally, you???ll use this command when you want to create a phone book file that is slightly different from an existing one (load the existing file, save it under a new name, and make the changes).

The command opens the dialog box shown below. This dialog appears also when you request to save a phone book file for the first time.

5-132

Phone Book

Dialog box parameters

Use the parameters in the order specified below. Normally you???ll only use the File Name parameter.

Save in

If the currently displayed directory is not the correct one, double-click the arrow to the right of the Look in parameter and locate the drive/directory. To access sub-directories, double-click parent directories.

File Name

Type the name of the phone book file you want to create, and click OK. ToolBox automatically adds the .tel extension. If you specify the name of a phone book file that appears on the list, ToolBox issues a message asking you whether you want to overwrite the existing file. Select Yes only if you want to replace the existing file with the new one.

If you want to Save As an older version of the phone book, ToolBox allows you to select a format. See Save command for explanation.

Save as Type

This box shows the type (extension) of the files currently displayed in the File Name list. If the displayed file type ???filter??? is not .tel, open the drop-down list and select the .tel type.

Print

This command prints the current phone book file to your standard system printer. If no printer is set up, see Windows Help or your system administrator.

Merge

The Merge command combines two phone books. Follow these steps:

1.Open one of the phone books.

2.Open the File menu and select the Merge command. The following is displayed.

3. In the Merge dialog box double-click the name of the other phone book.

Note that Phone Book adds the contents of the second file to the first. The current file is the first file. You can Save or Save As.

5-133

Phone Book

Status bar

The Status bar displays the status messages at the bottom of the Dial Up window.

Window Menu

This menu enables you to arrange and view the open files as desired, using standard Windows commands.

Cascade

The Cascade command arranges the various screens in cascade style.

Tile

The Tile command arranges the various screens in tiled style.

Arrange Icons

The Arrange Icons command arranges any minimized screens on the bottom of the window.

Help Menu

This menu enables you to view the version information and help files which relate to the Phone book utility.

Contents

The Contents command opens the help files which describe the Phone Book tool and other IP Gateway utilities.

How to Use Help

The How to Use Help explains to the user how the IP Gateway help is used.

About

The About command displays the version information for the Phone Book tool.

5-135

Communication Setup

Dialog box parameters

Serial Port

Select this option if the communication will go over the serial port and specify the port and data speed below.

Communication Port

Specify the serial port over which the ToolBox will communicate with the RTU.

Data Speed

Specify the data speed at which the ToolBox will communicate with the RTU.

Protect Third Party Protocol over MDLC port

The ???Protect Third Party Protocol over MDLC port??? checkbox (??? V7.50) is relevant only when a ToolBox MDLC port is also used for some Third Party protocol. If this Third Party protocol is not sophisticated enough to ignore messages from other protocols sharing the port, the Communication Setup utility allows you to block all messages not intended for that protocol for the length of the session.

Before each MDLC session, MDLC sends a ???start protection??? message, after which the remote prevents MDLC messages from being sent to Third Party protocol. At the end of the session, an ???end protection??? is sent which opens the port to all MDLC messages. If communication fails and the ???end protection??? transmission is lost, protection will end after a few minutes, as determined by an internal timer.

Third Party protocol protection adds overhead of approximately 20 bytes/session (start/end protection bytes) and therefore should not be selected if the port is only used for MDLC. Mature protocols such as MDLC and DNP do not require this protection and can recognize and reject messages which are irrelevant to them.

Ethernet Port

Select this option if the communication will go over an Ethernet connection and specify the IP address below. A MOSCAD/MOSCAD-L RTU or IP Gateway with connectivity to Ethernet must act as a bridge to the Ethernet for other RTUs in the field with no such connectivity.

Local Site IP Address

If the communication is over an Ethernet connection, specify the IP Address of the IP Gateway. Range: 000.000.000.001-255.255.255.254

If the communication is over an Ethernet connection, specify the IP Port Number of the IP Gateway. This number is common to all RTUs and IP Gateways connected to the link.

Cancel

If you press the Cancel button, the Communication Setup window will close.

OK

The OK button saves changes made to the Communication Setup. A message will appear reminding you to close any ToolBox applications and Stop the Communication Driver in order for the changes to take place. Once all other ToolBox applications are closed and the driver has been stopped, click the Apply button to apply changes. If you press the OK button, the Communication Setup window will close.

5-137

Communication Setup

Apply

The Apply button saves changes made to the Communication Setup. A message will appear reminding you to close any ToolBox utilities and Stop the Communication Driver in order for the changes to take place. Press OK to close the window.

More

If you press the More button, the Communication Setup window will expand as follows:

Dialog box parameters

Less

If you press the Less button, the Communication Setup window will shrink back to its original size.

Number of MASTER logical channels

Specify the number of logical channels in the MDLC protocol capable of initiating communication via a session oriented channel.

Number of retries to declare TX FAIL

Specify the number of retries at session oriented logical channel level after which the Transport Layer declares that transmission to destination site has failed.

Interval between Tx retries

Specify the interval of time that should elapse between two retries at Source/Destination level.

Formatted buffer size

Specify the size of the formatted buffer that serves as asynchronous port.

Restore Default

If you press the Restore Default button, the default values for the four parameters on the right side of the Communication Setup window will return to their original values.

5-138

Stop Communication Driver

The Stop Communication Driver is used when a session password is changed. This utility allows you to sever the connection to the current unit and connect to another IP Gateway, or work off-line. Before stopping communications, close all Toolbox tools and then double-click the Stop Communication Driver icon in the Toolbox program folder (shown below).

If you try to stop the communication driver while a communication session is in progress, a message warns you that a logical channel is currently open.

If you chose to continue (stop the driver), the results of the current communication cannot be predicted. It is, therefore, advisable to finish the current task and then to stop the driver.

If all applications were closed before activating the utility, the following dialog box is displayed.

If no drivers were active before stopping the communication driver, the following message is displayed.

5-139

Host Table

General

The Host Table enables users to define all the SCADA/NFM manager host computers in the system which are connected to a particular IP Gateway. When the hosts have been defined, they can be downloaded to the IP Gateway. After downloading the Host Table, the IP Gateway will send SNMP Traps to all the SNMP Type hosts in the Host Table for all the spontaneous events that occur.

The Host Table Window

To start the Host Table utility, double-click the Host Table icon in the IP Gateway Toolbox folder. The Host Table Window, as shown below, enables the user to define each host with IP Address, Host Name, and Host Type. The same window is used to define the hosts for the NTP Configuration.

5-140

Host Table

Dialog box parameters

IP Address

The IP address of the host computer.

Range: 000.000.000.001-255.255.255.254

Host Name

Alphanumeric name assigned by user. Up to 10 characters.

Host Type

There are four host type options for the standard Host Table:

???Generic SNMP ??? for SNMP for a Network Manager which uses generic MIB (SNMP Database). (See MOSCAD NFM Manual.)

???FullVision ??? for interface with the Motorola Network Fault Manager.

???TCP/IP ??? for a Host which is only a SCADA manager. (See MDLC Gateway for TCP/IP Application Programming Interface User???s Manual.)

???(not applicable)

There is one host type option for the NTP Configuration File:

???NTP Server ??? for a Host which provides time related services, using the Network Time Protocol.

Icons

The following is the list of the available command icons.

File menu, New command

File menu, Open command

File menu, Save command

File menu, Print command

File menu, Download command

File menu, Upload command

5-141

Host Table

File Menu

The commands in the File menu are designed to handle host/NTP Configuration files.

New

The New command opens a submenu and enables the user to create either a new host or NTP Configuration file. If there is an open host/NTP file on the screen, it will be closed. (The user will be prompted to save the file if changes were made.)

Open

The Open command opens an existing host/NTP file. When the Open command is executed, the Toolbox displays the Open dialog box, as shown below.

The Open dialog box defaults to the config sub-directory of the Toolbox directory (e.g., c:\itbox550\config).

Select the host table/NTP file (see parameters below) and click OK to load it.

Dialog box parameters

Use the parameters in the order specified below. For host files, you will probably only use the File Name parameter. For NTP files, you may have to change the Files of Type parameter.

Look In

If the currently displayed directory is not the correct one, double-click the drive letter at the beginning of the Directories list and locate the directory. To access sub-directories, double- click parent directories.

File Name

Type the name of the host/NTP file. Toolbox automatically adds the .hst extension. If the desired file is an NTP file, select .hst under Files of Type. Alternatively, locate the file name in the file list, and double-click the name.

5-142

Host Table

Action Menu

Upload

Uploads the Host Table or NTP Configuration file from a specified IP Gateway as shown in the figure below. The type of file to be uploaded is selected from the Upload submenu. The IP Gateway can be local or remote.

Download

Downloads the currently open Host Table/NTP Configuration file to a specified IP Gateway as shown in the figure below. The IP Gateway can be local or remote.

Help Menu

This menu enables you to view the version information and help files which relate to the Host Table utility.

Help Topics

The Contents command opens the help files which describe the Host Table tool and other IP Gateway utilities.

About

The About command displays the version information for the Host Table tool.

5-145

DataTac Modem ID Table

General

Two sites (MOSCAD RTUs) can communicate with one another through the IP Gateway (with Reflector capability), if both are connected to Private DataTac radios. The MDLC message is encapsulated and sent over IP to the Gateway. The user ports on the RTUs must be configured properly and the IP Gateway must have the Modem IDs for both sites. The figure below depicts such a system.

SCADA

Central

Ethernet

Host Computer

IP Gateway

w/Reflector

RS-232

RNC

Programming

ToolBox

RF

SYSTEM

The DataTac Modem ID Table enables users to define all the DataTac Modems in the system which are connected to a particular MOSCAD RTU. When the Modem IDs have been defined, they can be downloaded to the IP Gateway. MDLC communication from one RTU to another can then be routed through the IP Gateway.

For more information, see the MDLC over Private DataTac chapter in the MOSCAD Programming Toolbox Application Programmer manual (Advanced Features).

5-146

DataTac Modem ID Table

The DataTac Modem ID Table Window

To start the DataTac Modem ID Table utility, double-click the DataTac Modem ID Table icon in the IP Gateway Toolbox folder. The DataTac Modem ID Table Window, as shown below, enables the user to define the Modem ID for each site.

Dialog box parameters

Site ID

The Site ID whose modems are being defined.

Modem ID

Number assigned by the system (80000001, 80000002, etc.)

Icons

The following is the list of the available command icons.

File menu, New command

File menu, Open command

File menu, Save command

File menu, Print command

File menu, Download command

File menu, Upload command

5-147

DataTac Modem ID Table

File Menu

The commands in the File menu are mainly designed to handle Modem ID table files.

New

The New command clears the current Modem ID data from the screen, and opens a new Modem ID file.

Open

The Open command opens an existing Modem ID file. When the Open command is executed, the Toolbox displays the Open dialog box, as shown below.

The Open dialog box defaults to the config sub-directory of the Toolbox directory (e.g., c:\itbox550\config).

Select the Modem ID table file (see parameters below) and click OK to load it.

Dialog box parameters

Use the parameters in the order specified below. Normally you???ll only use the File Name parameter.

Look In

If the currently displayed directory is not the correct one, double-click the drive letter at the beginning of the Directories list and locate the directory. To access sub-directories, double- click parent directories.

File Name

Type the name of the Modem ID file. Toolbox automatically adds the .rnc extension. Alternatively, locate the file name in the file list, and double-click the name.

5-148

DataTac Modem ID Table

Files of Type

This box shows the type (extension) of the files currently displayed in the File Name list. If the displayed file type ???filter??? is not .rnc, open the drop-down list and select the .rnc type.

Save

The Save command stores the current Modem ID table.

If the file has not been saved at least once, Toolbox opens the Save As dialog box where you assign a name to the Modem ID file. The name may contain up to 6 characters to ensure backward compatibility.

If the file has been saved at least once, Toolbox just saves the file.

Save As

The Save As command saves the current Modem ID table under a different file name. Generally, you???ll use this command when you want to create a Modem ID table file that is slightly different from an existing one (load the existing file, save it under a new name, and make the changes).

The command opens the dialog box shown below. This dialog also appears when you request to save a Modem ID table file for the first time.

Dialog box parameters

Use the parameters in the order specified below. Normally you???ll only use the File Name parameter.

Save In

If the currently displayed directory is not the correct one, double-click the drive letter at the beginning of the Save In list and locate the drive/directory. To access sub-directories, double- click parent directories.

5-149

DataTac Modem ID Table

File Name

Type the name of the Modem ID file. Toolbox automatically adds the .rnc extension. Alternatively, locate the file name in the file list, and double-click the name.

Save as Type

This box shows the type (extension) of the files currently displayed in the File Name list. If the displayed file type ???filter??? is not .rnc, open the drop-down list and select the .rnc type.

Close

The Close command closes the current Modem ID table file. If changes have been made to the file, the tool will ask if you want to save those changes. If you specify yes, the Save As dialog box will appear and enable the current Modem ID file to be saved under a different file name. If no changes have been made, the dialog box reverts to an empty screen.

Print

The Print command prints the current Modem ID table file to a local printer.

Exit

The Exit command exits the DataTac Modem ID Table utility. If changes have been made to the current file, the tool will ask if you want to save those changes. If you specify yes, the Save As dialog box will appear and enable the current Modem ID file to be saved under a different file name. If no changes have been made, the DataTac Modem ID Table screen will disappear.

Edit Menu

The Edit menu contains commands that affect the entries in the Modem ID table.

New

Creates a new entry in the DataTac Modem ID Table. Note that once an empty entry has been created, a valid IP Address must be entered, or an error message will appear.

Delete

Deletes the current entry in the DataTac Modem ID Table.

5-150

DataTac Modem ID Table

Action Menu

Upload

Uploads the DataTac Modem ID Table from a specified IP Gateway as shown in the figure below. The IP Gateway can be local or remote.

Download

Downloads the DataTac Modem ID Table to a specified IP Gateway as shown in the figure below. The IP Gateway can be local or remote.

Help Menu

This menu enables you to view the version information and help files which relate to the DataTac Modem ID Table utility.

Help Topics

The Contents command opens the help files which describe the DataTac Modem ID Table tool and other IP Gateway utilities.

About

The About command displays the version information for the DataTac Modem ID Table tool.

5-151

IP Conversion Table

General

IP (Internet Protocol) technology can be used to interface between MOSCAD RTUs and IP Gateways over advanced radio infrastructure (e.g. digital ASTRO IP conventional systems) and standard private IP networks. MDLC packets to be transmitted are enveloped inside IP datagrams and sent between remote RTUs or between an IP Gateway and an RTU.

An IP Gateway can act as a gateway between the field and the SCADA Central to extract the enveloped frames from the IP message. A Toolbox can be connected to one of the RTUs or to one of the serial ports of the IP Gateway.

Each RTU/IP Gateway is assigned a Site ID. In addition, each RTU/IP Gateway with an IP interface is assigned an IP address. An IP conversion table which maps Site IDs to IP addresses is created in the Toolbox and downloaded to the RTUs and IP Gateway. This enables routing over the IP network to the proper destination.

For more details on the possible network configurations and RTU setup, see the MDLC over IP section of the MOSCAD Programming ToolBox Application Programmer Manual (Advanced Features).

IP Gateway Site Configuration

Configure an IP Port as TCP/IP, as follows:

(Note that this is one of the virtual ports over Port 1, rather than physical port.)

Link ID:

(e.g. LINE 1) Same as for all RTUs.

Port number:

(e.g. 2002) Same as for all RTUs.

The rest of the parameters are set up according to normal IP Gateway procedures. Any exceptions or known problems are described in the release notes.

5-152

IP Conversion Table

IP Conversion Table Preparation

Click on the IP Conversion Table icon in the IP Gateway Toolbox folder to start the tool. Add entries for each Site ID, as shown below.

Download the IP Conversion Table to the IP Gateway and to all RTUs in the network, along with the site configuration and network configuration, if necessary.

Icons

The following is the list of the available command icons.

5-153

IP Conversion Table

Help menu, About command

File menu, Download command

File menu, Upload command

Edit menu, Abort command

Insert New Line command

Delete Current Site command

Delete Group of Sites command

Sort by ID command

Dialog box parameters and functions

Site ID

Type or edit the Site ID of the unit.

IP Address

The IP address of the host computer.

Range: 000.000.000.001-255.255.255.254

File Menu

You can perform all the basic file operations using the commands of the File menu. After opening the menu, the following commands are displayed:

New

The New command opens a new, empty IP conversion table.

5-154

IP Conversion Table

Open

The Open command opens an existing IP conversion table file. When the Open command is executed, the Toolbox displays the Open dialog box.

The Open dialog box defaults to the config sub-directory of the Toolbox directory (e.g., c:\itbox550\config).

Select the IP conversion table file (see parameters below) and click OK to load it.

Dialog box parameters

Use the parameters in the order specified below. Normally you???ll only use the File Name parameter.

Save in

If the currently displayed directory is not the correct one, double-click the drive letter at the beginning of the Directories list and locate the directory. To access sub-directories, double- click parent directories.

File name

Type the name of the host file. Toolbox automatically adds the .ipc extension. Alternatively, locate the file name in the file list, and double-click the name.

Save as type

This box shows the type (extension) of the files currently displayed in the File Name list. If the displayed file type ???filter??? is not .ipc, open the drop-down list and select the .ipc type.

Close

The Close command closes the current IP conversion table.

Save

The Save command stores the current IP conversion table.

If the file has not been saved at least once, Toolbox opens the Save As dialog box where you assign a name to the IP conversion file. The name may contain up to 6 characters to ensure backward compatibility.

If the file has been saved at least once, Toolbox just saves the file.

Save As

The Save As command saves the current IP conversion table under a different file name. Generally, you???ll use this command when you want to create an IP conversion table file that is slightly different from an existing one (load the existing file, save it under a new name, and make the changes).

The Save As dialog also appears when you request to save an IP conversion table file for the first time.

5-155

IP Conversion Table

Print

The Print command prints the current IP conversion file to your standard system printer. If no printer is set up, see Windows Help or your system administrator.

Download

Downloads the IP Conversion Table to a specified IP Gateway. The IP Gateway can be local

or remote. While the IP Conversion table tool is communicating with the RTU, the icon at the top right hand corner of the window will be animated.

Upload

Uploads the IP Conversion Table from a specified IP Gateway. The IP Gateway can be local

or remote. While the IP Conversion table tool is communicating with the RTU, the icon at the top right hand corner of the window will be animated.

Abort

The Abort command terminates the download or upload operation currently in progress with the IP Gateway.

Exit

The Exit command exits the IP Conversion Table utility. If changes have been made to the current file, the tool will ask if you want to save those changes. If you specify yes, the Save As dialog box will appear and enable the current IP conversion file to be saved under a different file name. If no changes have been made, the IP Conversion Table screen will disappear.

Edit Menu

The Edit menu contains commands that affect the list of sites in the main window.

Cut

Cuts selected block of cells from the current IP Conversion file to the system clipboard.

Copy

Copies selected block of cells from the current IP Conversion file to the system clipboard.

Paste

Pastes block of cells from the system clipboard to the selected cells in the current IP Conversion file.

5-156

IP Conversion Table

View Menu

The following views are available to the user. Click on an entry to select it, and a check mark will appear on the menu. The associated view is then displayed on the window.

Toolbar

The Toolbar displays the basic icons, described under Icons, used for handling files and editing text.

Tablebar

The Tablebar displays the icons, described under Icons, used for manipulating rows in the IP Conversion Table.

Sitebar

When checked, this command displays the Sitebar, usually towards the top of the screen. Use the SiteIDBar to specify the RTU to which the IP Conversion file is to be downloaded. If the ToolBox computer is locally connected to the RTU, make sure that Local is selected (default). If you want to configure a remote site, unclick Local and specify the Site ID and the appropriate link ID.

Statusbar

The Status bar displays the status messages at the bottom of the IP Conversion Table window.

Window Menu

The Window menu enables the user to arrange the various screens within the IP Conversion Table window. The screens can also be moved, resized or closed as standard Windows. In addition to the commands below, the Window menu lists the currently open windows. The checked name is the active screen. By clicking on another filename, the user can change the active screen.

Cascade

The Cascade command arranges the various screens in cascade style.

Tile

The Tile command arranges the various screens in tiled style.

Arrange Icons

The Arrange Icons command arranges any minimized screens on the bottom of the window.

5-157

IP Conversion Table

Help Menu

The Help menu enables the user to view the version information and help files which relate to the IP Conversion Table tool.

About IP Conv. Table

The About command displays the version information for the IP Conversion Table tool.

5-158

SW Diagnostics & Loggers

The SW Diagnostics & Loggers utility enables the user to run several instances of three different diagnostics tools simultaneously. The user can interface with one of three tools at any one time, jumping from one window to another as necessary.

The diagnostics applications are:

???Error Logger

???Software Diagnostics

The Error Logger retrieves error information (hardware or software malfunctions) from the IP Gateway. The Software Diagnostics program allows access to each of the modules (or ???devices???) that handle the various tasks of the IP Gateway according to their logical names. The tools can communicate with any IP Gateway in the system, local or remote, based on the setup of the communication links.

SW Diagnostics and Loggers Window

To activate the tool, double-click the SW Diagnostics and Loggers Tool icon in the IP Gateway ToolBox folder. The following window is displayed.

5-159

SW Diagnostics & Loggers

Select one or more applications by clicking on the appropriate logger icon or by selecting from the Loggers menu. New logger windows open in a cascade, but can be moved around the Logger window. (See Window Menu.) Before the logging is begun, the files are empty, with only one screen active at a time. The header of each screen includes the application name, file name and Site ID (e.g. Error Logger Errlog102.30.01_15.25.32.log Site: Local). The log file name incorporates the window instance (Errlog1) and the date/time.

For each window, identify the IP Gateway from which the information is to be retrieved. In the Site Toolbar, make sure that Local is selected if you are connected locally to the

IP Gateway. If you are connecting to a remote IP Gateway, specify the Site ID and Link ID. If the Site Toolbar is not shown, select it from the View menu.

If you are running the Error Logger, press the Start icon or select Start from the Loggers menu, to begin communication with the IP Gateway and retrieve Error Log data. For more details on the Error Logger, see the Error Logger Tool section.

If you are running the SW Diagnostics tool, the device and level must be defined in the Device toolbar. If the Device toolbar is not shown, select it from the View menu. Type in the device name to be tested or select it from the pull-down menu. If the name does not appear on the list, run the Get Device List command from the Loggers menu or click on the icon. This retrieves the full list of devices from the IP Gateway. Next enter the level at which the diagnostics will be performed. All devices in the system have a level of request, starting from Level 0. Level 10 gets the data and resets all counters. Level 11 gets the data without resetting the counters. For details on the devices and levels, refer to the Software Diagnostics Output section. Press the Start icon or select Start from the Loggers menu, to begin communication with the IP Gateway and retrieve the diagnostics data. For more details on the Software Diagnostics tool, see the Software Diagnostics Tool section.

While the SW Diagnostics & Loggers utility is communicating with the IP Gateway, the

icon at the top right hand corner of the SW Diagnostics & Loggers window will be animated.

Error Logger Tool

The Error Logger retrieves error information (hardware or software malfunctions) from any gateway or site in your system. Several logger windows can be opened simultaneously, each one numbered sequentially Errlog1, Errlog2, etc. The information is stored in the c:\Itbox550\log\ErrLog directory. Log files will be named Errorlog<#>_Date_Time.log by default, where # is the sequential number (1, 2, etc.) of the error logger window opened. The default log file name can be changed. For a review of error messages, see the Error Messages section. For an example of an Error Log, see Error Log example.

When the Error Logger is activated from the ToolBox, the contents of the site???s error log are appended to the log file and the site???s log file is then cleared. (This is important, as the size of the site???s error log is limited.) The error log in the ToolBox, however, is not cleared, and it is recommended that the file be cleaned out manually from time to time.

5-160

SW Diagnostics & Loggers

Software Diagnostics Tool

The IP Gateway software is based on an ???Object Oriented Multi-Tasking??? operating system. The software is comprised of modules, named ???devices??? (objects, entities), that handle the various tasks of the MOSCAD RTU.

Some of the devices handle the operation of physical elements such as communication ports or I/O modules, and other devices are simply software modules such as communication applications, time handling etc.

One of the many advantages of such an operating system is that it creates the devices according to the user configuration requirements as defined by the Site Configuration program.

For example, devices are created to handle the I/O modules (one device for each module according to the type of module) and each of the physical ports according to the required protocol and parameters defined by the user.

Another advantage of this operating system is the Software Diagnostics program that allows access through the communication (local or remote) to each of the devices according to their logical names (the devices are created with a logical name).

The Software Diagnostics program provides reports on the status of each device at different levels of breakdown. It also provides historical and statistical data on the device activities. The Software Diagnostics data is useful for system maintenance, problem identification for remote services and statistics data on the communication system performance.

The Software Diagnostics tool allows access to each of the modules (or ???devices???) that handle the various tasks of the IP Gateway according to their logical names. The tool retrieves information from any site in your system. For more background on communication, diagnostics and devices, see Diagnostics below.

Several logger windows can be opened simultaneously, each one numbered sequentially Diaglog1, Diaglog2, etc. The information is stored in the c:\Itbox550\log\DiagLog directory. Log files will be named Diaglog<#>_Date_Time.log, where # is the sequential number (1, 2, etc.) of the Software Diagnostics window opened. (The default name of the log file can be changed.) For a review of the possible devices and their levels, refer to the Software Diagnostics Output section.

The device and level must be defined in the Device toolbar. If the Device toolbar is not shown, select it from the View menu. Select the device name to be tested from the pull-down menu or type it into the Device Name field. If the name does not appear on the list, run the Get Device List command from the Loggers menu or click on the icon. This retrieves the full list of devices from the IP Gateway. Next enter the level at which the diagnostics will be performed. All devices in the system have a level of request, starting from Level 0. Level 10 gets the data and resets all counters. Level 11 gets the data without resetting the counters. Select the appropriate level. For details on the devices and levels, refer to the Software Diagnostics Output section.

Press the Start icon or select Start from the Loggers menu, to begin communication with the IP Gateway and retrieve the diagnostics data.

5-161

SW Diagnostics & Loggers

When the Software Diagnostics tool is activated from the ToolBox, the diagnostics information is appended to the log file, and the site???s log file is then cleared. (This is important as the size of the site???s log is limited.) The log file in the ToolBox, however, is not cleared, and it is recommended that the file be cleaned out manually from time to time.

Icons

The following command icons are available in the toolbar. Those icons which are specific to a given logger, are marked accordingly below. Note that during execution, the icons displayed in the toolbars relate to the active tool.

File Menu

The File menu commands enable you to save logger information to a file and to carry out file operations. Those commands which are specific to a given logger, are marked accordingly below.

5-162

SW Diagnostics & Loggers

Save As

The Save As.. command saves the current logger information under a different file name. The Save As dialog box defaults to the appropriate logger sub-directory of the ToolBox log directory (c:\Itbox550\log), based on the active logger (Errlog, Diaglog). If, for example, the Error Logger is active, the default log file name incorporates the window instance (Errlog1) and the date and time: Errlog102.30.01_15.25.32.log. Both the default name and directory of the log file can be changed in the dialog.

The command opens the dialog box shown below.

Dialog box parameters

Use the parameters in the order specified below. Normally you???ll only use the File Name parameter.

Save in

If the currently displayed directory is not the correct one, double-click the drive letter at the right of the Save in list and locate the directory. To access sub-directories, double-click parent directories.

List Files of Type

This box shows the type (extension) of the files currently displayed in the File Name list. If the displayed file type ???filter??? is not .log, open the drop-down list and select the .log type.

File Name

The file name (e.g. Errlog102.30.01_15.25.32.log) represents the current log file of the active utility and incorporates the window instance (Errlog1) and the date/time. The tool automatically adds the .log extension to the file.

5-164

SW Diagnostics & Loggers

Edit Menu

The Edit menu contains commands that affect the logger file or logger view in the current window. The Edit menu displays certain commands when a view is open for editing and others when a logger tool is open.

Undo

Undoes the last edit action performed in the current logger file.

Cut

Cuts selected text from the current logger file to the system clipboard.

Copy

Copies selected text from the current logger file/view to the system clipboard.

Paste

Pastes text from the system clipboard to the selected cells in the current logger file.

Delete

Deletes selected text from the current logger file to the system clipboard.

Find

Finds a specified text string in the current logger file/view.

Replace

Replaces text with a specified text string in the current logger file.

Clear View

Clears the screen of the active logger view. Note that the file still contains the log information, although the view is blank.

Loggers Menu

The Loggers menu contains commands that start the logger tools.

Error Logger

The Error Logger command starts an instance of the Error Logger.

5-166

SW Diagnostics & Loggers

Error Log example

The error logger window header is as follows: Error Logger <filename> <site id><link id>

The format of the error message itself is as follows:

???The first row displays the date and time in the PC.

???The second row displays the date and time in the IP Gateway, and the error number.

???The third row displays the error message.

Thu May 31 11:12:51 2001 SITE: Local 01/01/80 05:21 ERROR #: 141

Cannot find link id in network configuration, network layer: NETWRK dest site: 17 , dest link: 23 , dest port: 0

Diagnostics

The Diagnostics command starts an instance of the Software Diagnostics.

Communication System Statistics

The IP Gateway and MOSCAD communication systems implement the seven layers of OSI (Open Systems Interconnection) model. In each layer, one or more devices are created to handle that specific layer. Each of the devices (in addition to its functions) performs statistical follow-up that may be used to analyze the status of the communication system. The following figure describes the devices (objects) of the communication system:

5-167

SW Diagnostics & Loggers

The names of the devices of the Link and Physical layers are taken from the logical names of the links, as defined by the user in the Site Configuration program. There is no connection between the number that is part of the device name and the port number.

For example, the device of the link of port 3 is named RAD1L, since the link name is RADIO1 and L indicates a link device.

The IP Gateway communication supports two modes of transmission:

???Synchronous mode (may be used in ports 3 and 4 of the CPU module)

???Asynchronous mode, UART (all ports of the CPU module)

Port 3 is used in the Synchronous mode of transmission, when:

1)A radio of any type is connected.

2)A modem is connected and synchronous communication is defined in the Site Configuration program (except dial-up mode that allows only asynchronous mode of operation).

3)An RS232 Synchronous piggyback is connected to ports 3 and 4.

When the communication is synchronous (bit oriented), the physical channel consists of the Link device and Physical device. The transmitted frame is composed of a stream of bits that starts and ends with flags that indicate the frame limits.

When the communication is asynchronous (byte oriented), the frame is broken down and encoded into a series of bytes, transmitted and received by a UART. This type of communication is handled by the Adapter device.

To get the statistics of a specific device, define the device name, the Site ID, and also the Level of request. All devices in the system have a level of request, starting from Level 0.

Level 10 and Level 11 should be used to get communication statistics.

The following table provides the device names that respond to Level 10 and Level 11.

5-169

SW Diagnostics & Loggers

5-170

Reading Diagnostics Information

The structure of the statistical data is described below for each device name.

COMxA (Adapter device of Computer X)

The # of Received Frames includes only correct frames (including acknowledgment frames).

The # of Re-transmitted Frames represents only frames rejected by the physical layer (do not use this number; use the # of Re-transmitted Frames in the Link device).

RADxL (Link device of Radio X)

5-171

SW Diagnostics & Loggers

The # of Transmitted Frames does not include retransmission and acknowledgment frames. The # of Received Frames includes only correct frames.

COMxL (Link device of Computer X)

The # of Transmitted Frames does not include retransmission and acknowledgment frames. The # of Received Frames includes only correct frames.

NETWRK (Network device)

STCL

Jun 30 15:09:25 Site: LOCAL Device: STCL Level: 11

#of transmitted frames as ORIGINATE: 0

#of transmitted frames as GROUPCALL: 0

TRANSx, MTRNSx

5-172

SW Diagnostics & Loggers

REQMNG Requirements Manager device

The meaningful levels are 0, 1. Diagnostic levels of 2, 3, 4 are for internal use only.

Example of Level 0 Diagnostics:

Oct 31 09:45:36 Site: 10000 Link: Rslink1 Device: REQMNG Level: 0

Interesting fields:

Static Data

Dynamic Data

5-173

Interesting fields:

The name column indicates the names of the connected clients, (if a row starts with 1, the first - name field is empty).

LNKHNDL

HELTHCH Health Check Device

5-174

5-175

SW Diagnostics & Loggers

STBLA Sites Table Device

Start

The Start command begins retrieval of error logger or diagnostics information from the IP Gateway. The information is displayed in the appropriate logger window. When the ToolBox is communicating with the IP Gateway, the Start icon and command will be dimmed. While

the SW Diagnostics & Loggers utility is communicating with the IP Gateway, the

icon at the top right hand corner of the SW Diagnostics & Loggers window will be animated.

Device List

(SW Diagnostics only) A basic device list is available when you open the SW Diagnostics tool. The Device List command updates the device list with all the devices actually residing in the IP Gateway.

5-176

SW Diagnostics & Loggers

Abort

The Abort command terminates retrieval of error logger or diagnostics information from the IP Gateway.

View Menu

The following views are available to the user. Click on an entry to select it, and a check mark will appear on the menu. The associated view will be displayed on the SW Diagnostics & Loggers window. Those views which are specific to a given logger, are marked accordingly below. Note that during execution, the icons displayed in the toolbars relate to the active tool.

Toolbar

The Toolbar displays the icons described under.

Status bar

The Status bar displays the status messages at the bottom edge of the SW Diagnostics & Loggers window. This message area is read-only.

Site bar

The Site bar dialog enables the user to specify the location of the IP Gateway with which the current logger tool communicates. The logger tool runs can be connected locally to an IP Gateway or over a network to a remote IP Gateway in order to retrieve error or diagnostics information. If you are connected locally to the IP Gateway, make sure that Local is selected. If you are connected remotely, unselect Local and specify the Site ID and Link ID.

By default, the Site bar is displayed at the top of the SW Diagnostics & Loggers window. To remove the bar, unselect it in the View menu.

Dialog box parameters

Local

When this box is checked, the logging is done for the locally connected IP Gateway. The default setting for communication is Local.

Link ID

When the Local box is not checked, the logging is done for a remote IP Gateway connected to the PC via the specified Link ID.

Site ID

When the Local box is not checked, the logging is done for the remote IP Gateway at the specified Site ID connected to the PC via the above Link ID.

Loggers Bar

The Loggers Bar enables the user to launch a new logger tool and set it as the active tool.

5-177

SW Diagnostics & Loggers

Device Bar

(Available for the SW Diagnostics tool only). The Device Bar enables the user to select the name and level of breakdown for whose data is to be reported.

Window Menu

The Window menu enables the user to arrange the various logger screens within the Logger window. The logger screens can also be moved, resized or closed as standard Windows. In addition to the commands below, the Window menu lists the currently open screens. The checked name is the active logger. By clicking on another name, the user can change the active logger.

Cascade

The Cascade command arranges the various screens in cascade style.

Tile

The Tile command arranges the various screens in tiled style.

Arrange Icons

The Arrange Icons command arranges any minimized screens on the bottom of the window.

Fonts

The Fonts command enables the user to change the font name, font style, size and script used in the screens.

Help Menu

The Help menu enables the user to view the version information and help files which relate to the SW Diagnostics & Loggers utility.

Contents

The Contents opens the help files which describe the SW Diagnostics & Loggers utility and other IP Gateway ToolBox utilities.

How to Use Help

The How to Use Help explains to the user how the IP Gateway ToolBox help is used.

About

The About displays the version information for the SW Diagnostics & Loggers utility.

5-178

Advanced Features

The IP Gateway system includes several advanced features which are described below. These often require special setup and configuration procedures.

6-1

HealthCheck Mechanism

IP Gateway through the same link the Ping arrived. Unless being pinged, the RTU HealthCheck mechanism will not initiate any communication.

Disabled HealthCheck

When HealthCheck is disabled in the IP Gateway, the IP Gateway will assume that all sites registered in the site table are reachable. However ??? since SNMP proxy operation relies on HealthCheck, disabling this mechanism will disable any SNMP proxy operation (MCPS).

When HealthCheck is disabled in the RTU, the RTU MDLC stack will not allow the incoming of any HealthCheck messages. Instead, an automatic response indicating that HealthCheck application is blocked will be communicated back to the originator of an incoming ping frame. The IP Gateway HealthCheck, though, is capable of handling such cases by assuming the link is OK if such a response is received. However, the indications received from the HealthCheck mechanism may not be accurate, as the path the response traveled through cannot be determined.

HealthCheck Setup

Setting up the Site Table

The IP Gateway site-table should contain all the sites upon which the HealthCheck is requested to operate. Each site is associated with two links, one primary and one secondary. Additionally, each link is given a time parameter ??? Link validity interval. For each link, the HealthCheck mechanism uses the Link validity interval for calculating the time basis for the Ping-Pong mechanism to operate. Further ??? this parameter also determines the maximum time to wait for a Pong to arrive back at the IP Gateway before declaring a link to be in a failure condition. . .

When defining primary and secondary links, one should pay attention to the following:

???Primary and secondary links may be identical. In this case, the HealthCheck mechanism will assume the site possesses only one link and thus will not ping the same site twice.

???Primary and secondary links may not be identical. However in this case ??? the two paths to the site (one through each link) should not overlap any part of the route. If two different paths to the same RTU do indeed overlap part of the route, the indications received from the HealthCheck mechanism may not be accurate.

For more information, see the description of the IP Gateway Toolbox Site Table utility above.

Site Configuration

The IP Gateway HealthCheck mechanism is activated through IP Gateway Toolbox Site Configuration utility. In order to activate it,

1.Run the Site Configuration utility from the IP Gateway Toolbox.

2.Click on the Advanced tab in the workspace bar.

3.Open the Message Oriented Service advanced parameters screen.

6-3

HealthCheck Mechanism

4. Set the ???Health-check application support??? parameter to Yes.

By default, the HealthCheck mechanism is enabled. For more details refer to the Health-check (application) support parameter under Advanced Parameters in the Site Configuration chapter above.

The RTU HealthCheck mechanism is activated through MOSCAD Programming ToolBox Site Configuration utility. In order to activate it,

1.Run the Site Configuration utility from the MOSCAD Programming ToolBox.

2.Click on the Advanced tab in the workspace bar.

3.Open the Message Oriented Service advanced parameters screen.

4.Set the ???Health-check application support??? parameter to Yes.

By default, the HealthCheck mechanism is enabled. For more details, refer to the Site Configuration chapter in the MOSCAD Programming ToolBox manual.

HealthCheck Diagnostics

Two sets of diagnostics are relevant to the HealthCheck mechanism, the IP Gateway site table and the HealthCheck device.

To retrieve the downloaded IP Gateway site table,

1.Run the SW Diagnostics & Loggers utility from the IP Gateway Toolbox.

2.Select device STBLA from the pull-down menu into the Device Name field in the Device toolbar or type in STBLA. If the Device toolbar is not shown, select it from the View menu.

3.Enter 2 in the Level field.

4.Click on the Start Communications button in the icon bar or select Start from the Loggers menu. The site table will be displayed in the output window.

The same diagnostics can be retrieved via the Web Server (See below.)

To retrieve the current HealthCheck status of each of the links for a site,

1.Run the SW Diagnostics & Loggers utility from the IP Gateway Toolbox.

2.Select device HELTHCH from the pull-down menu into the Device Name field in the Device toolbar or type in HELTHCH. If the Device toolbar is not shown, select it from the View menu.

3.Enter 1 in the Level field.

6-4

HealthCheck Mechanism

4.Click on the Start Communications button in the icon bar or select Start from the Loggers menu. The current HealthCheck status will be displayed in the output window.

The same diagnostics can be retrieved via the Web Server (See below.)

6-5

Adding Terminal Server Ports

General

The IP Gateway supports on board 4 ports for MDLC communication. In case more ports are required for MDLC communications external hardware is needed. The Standard hardware for Ports extensions is a Terminal Server.

The Terminal Server has an Ethernet port and many RS232 ports. It conveys communication traffic from IP to the RS232 ports and the other way around.

The IP Gateway establishes a connection to the Terminal Server over the LAN and establishes IP sessions for each RS232 port that???s utilized for MDLC communication. The connection remains opened even if there is no data to transmit/receive. Every connection is associated with an IP address (of the Terminal Server) and a TCP port id (associated with the specific RS232 port in that specific Terminal Server).

IP Gateway is designed to support up to 32 ports connected to one or more Terminal Servers.

IP Gateway is designed to be able to communicate with any TCP\IP Terminal Server that is implemented over TELNET. The IP Gateway was tested with several Terminal Servers. In this book we will elaborate the use of Equinox Terminal Servers.

IP Gateway Site Configuration and Terminal Server configuration must be defined in order to support external Terminal Server ports.

???The maximum number of ports connecting to RTUs in the network is 32.

???The IP Gateway can work with up to 32 Terminal Server IP addresses.

6-6

Adding Terminal Server Ports

???Two RS232 ports can have the same TCP port ID only if they reside in different Terminal Servers.

Site Configuration for Terminal Server

In order for the IP Gateway to be able to work with Terminal Server the following configuration should be applied:

1. Click on the IP port tab in the IP Gateway Site Configuration.

2.Right click on the Terminal Server and select ???Define???. The Ports Overview item will be displayed.

3.Double-click on the Ports Overview item. The Terminal Server Definition window will be displayed, as shown below.

6-7

Adding Terminal Server Ports

4.Define the Terminal Server ports. Every definition includes the Terminal Server IP address, the specific TCP port assignment for every physical port, and the MDLC link ID for that port.

5.Click on the ???Ok??? button to save the Terminal Server ports.

Configuring Terminal Server to work with IP Gateway

Configuration

Configure the Terminal Server to meet the needs of TELNET TCP\IP based connection.

Assign an IP address to the Terminal Server, and define each port allocated to MDLC as a TELNET listener, or in some cases as a SERVICE with a unique TCP port ID.

Activate TELNET in a binary profile, and disable all control characters, TELNET commands and options.

Disable flow control, and do not log out of the port under any condition.

Applying the configuration will allow the IP gateway to establish connection with all of its Terminal Server ports right after power up, even if there are no RTUs attached to them.

6-8

Adding Terminal Server Ports

The following sections contain a configuration example for the Equinox Terminal Server. However, following the guidelines described in this section should enable configuring every Terminal Server.

Wiring

The 8-pin connector used by the Terminal Server contains all necessary RS232 signals, but in a non standard format, Each user might output them in different pins. In most cases there is a need for an adapter, so that signals coming from the Terminal Server will be in the pins they are expected to be in.

The wiring description for the Equinox Terminal Server is described below.

Example: EQUINOX ELS16 Terminal Server Wiring and Configuration

General

The EQUINOX ELS16 is a 16 port Terminal Server.

1.Plug the machine to a 220v AC. The machine will perform a Self Boot Process, which takes about 15 seconds. While booting up, the LEDs in the front panel will blink. When Self Boot Process finishes, the READY led should be the only one lit.

The default console port is 1.

2.Attach a terminal (or a terminal emulator) to port 1, with a cable wired as described in the next section. The terminal should be configured as follows:

Wiring

Wiring PC to Terminal Server

For a PC HyperTerminal connection, use the Standard Connector and cable to connect the PC ???COM1??? to the Serial port of the Terminal Server. No other adapters are needed.

Wiring a MOSCAD to EQUINOX ELS-16 Using a Cable

The pins in the ELS16 ports are numbered from the right to the left. The rightmost pin is the first one, and the left most is the eighth.)

The numbering of the 8 pin connectors follows the MOSCAD convention.

6-9

Adding Terminal Server Ports

DEFINE SERVICE LOCAL PORT15 3015 PORT 15 ENABLED CONNECTIONS

ENABLED TELNET ENABLED

DEFINE SERVICE LOCAL PORT16 3016 PORT 16 ENABLED CONNECTIONS

ENABLED TELNET ENABLED

DEFINE SERVER IP 155.155.155.155

DEFINE SERVER SUBNET 255.255.0.0

DEFINE SERVER GATEWAY NONE

DEFINE SERVER TCPIP KEEPALIVE TIMER 120

INIT

6-14

Adding Terminal Server Ports

IP Gateway definition

The Site Configuration for this setting is shown below:

6-15

IP Gateway Redundancy

A redundant IP Gateway can be configured to minimize the risk of a SCADA control center losing contact with sites, and to ensure high availability for its applications. Two IP Gateways are set up with similar configurations, except that one is designated as the primary and the other is designated as the secondary. When the primary IP Gateway becomes unavailable, the secondary (similarly configured) IP Gateway takes over. To increase the availability of the LAN network, dual Ethernet segments can be used, and each IP Gateway can be connected to a different segment.

When the IP Gateway is configured for redundancy, the NFM application will not operate.

Initially, the IP Gateway Redundancy Mode is set to ???Secondary???. In this state:

???The IP Gateway does not ack any frame received by the MDLC communication (except local connection).

???The requests queued in the IP Gateway will return errors once activated. (In most cases this will be immediately. However, in some cases it could take as long as the longest MDLC session timeout defined.)

???The IP Gateway disconnects from all the Terminal Server ports defined in the Site Configuration.

The SCADA driver is responsible for changing the IP Gateway Redundancy Mode to ???Primary???. In this state, the IP Gateway communicates properly over MDLC communication and over the SCADA channels.

When the IP Gateway is configured for redundancy, it checks each of the channels to the unit. If all the channels to the unit are disconnected or unavailable, the unit automatically switches to ???Secondary??? mode.

When the SCADA establishes connections to the IP Gateway, it should change the redundancy mode of the IP Gateway to ???Primary???. Only one IP Gateway should be in ???Primary??? mode at any time. ???Primary??? mode of the IP Gateway allows bi-directional transfer of both SCADA application messages and IP Gateway management messages. ???Secondary??? mode allows transferring of IP Gateway management messages only. (It does not send or receive any MDLC messages, since it is logically disconnected from the link.)

Redundant IP Gateway Configurations

There are several possible options for Redundant IP Gateway system configuration:

1.Both IP Gateways are connected to the MOSCAD system over the same many-to-many media (i.e. RS485/Radio). In this configuration, when the secondary IP Gateway becomes primary, the IP Gateway???s mode changes take effect immediately.

2.Both IP Gateways are connected to the MOSCAD system over the same Terminal Sessions. In this configuration, the ???old primary??? IP Gateway must close all of the Terminal Server connections, the terminal server must end its sessions with the ???old primary??? IP Gateway and

6-16

IP Gateway Redundancy

then the ???new primary??? IP Gateway must establish connection with the Terminal server. In this configuration, several minutes may elapse before the IP Gateway???s mode changes take effect.

3. Both IP Gateways are connected to the MOSCAD system over an IP network. Using this configuration, the IP Gateway???s mode change takes effect immediately for requests going from the IP Gateway to the RTUs. The SCADA should initiate a communication to the RTU through the ???new??? primary IP Gateway in order for the RTU being able to send Bursts to it.

Site Configuration

The IP Gateway is configured for redundancy through the IP Gateway Toolbox Site Configuration utility.

To set up the site configuration,

1.Run the Site Configuration utility from the IP Gateway Toolbox.

2.Click on the SCADA tab in the workspace bar.

3.Under General System settings, set the ???Startup mode??? parameter for the primary IP Gateway to ???Redundant GW1???.

4.Save the site configuration file and download it to the primary IP Gateway.

5.Under General System settings, set the ???Startup mode??? parameter for the secondary IP Gateway to ???Redundant GW2???.

6.Make sure that the Site ID of the secondary IP Gateway is identical to the Site ID of the primary IP Gateway.

7.Save the site configuration file and download it to the secondary IP Gateway.

6-17

IP Gateway Web Operation

The TIPS box provides useful, context-sensitive tips for using the Web Server.

The LEGEND box explains the object types and fault severity levels.

The Search function enables the user to search for items within the current view level.

The Sort function enables the user to sort all items within the current view level according to Severity or ID (name). Sites can also be sorted according to MOSCAD State.

An Event Log lists all NFM RTU events, regardless of your location in the site map. Events appear in chronological order with the most recent alarm at the bottom of the list. Events include all bursts sent out from the site, such as equipment and environmental alarms, status changes, link up or down etc.

Security

The Web Server is password-protected to restrict access to the system to authorized personnel.

For each IP address there are three security levels, each with a different password: Read-Only, Read&Configure or Read&Permits.

Typically, equipment technicians have Read-Only rights, MOSCAD technicians have Read&Configure rights, and the Web Server Administrator has Read&Permits rights.

All security levels enable viewing the site maps, properties, the Event Log, and the MOSCAD Tools: Error Logger and Software Diagnostics.

6-19

IP Gateway Web Operation

Accessing the Web Server

1.Connect the host computer to the IP network with IP route to the IP Gateway.

2.Open a web browser (Internet Explorer or Netscape Navigator) and enter the IP Gateway URL address. An Entry Page similar to the one pictured below will be displayed.

6-20

IP Gateway Web Operation

3. Click on the picture and the user logon dialog will be displayed, as shown below.

4.Log in to the system, with the default username ???User??? and the password ???moscad???. Note that the default authentications can be changed. See the Web Server Administrator Tools section of the MOSCAD NFM Web Server 4.0 User Guide for details. A graphic desktop similar to the one pictured below will be displayed.

Note that the main screen can differ from system to system.

5.To run a Toolbox utility, click on the MOSCAD Tools link. Links to several MOSCAD tools will be displayed. Choose the desired link.

6-21

IP Gateway Web Operation

In case of firmware mismatch an error screen will be displayed.

Retrieving Errors using the Web Server

The Web server enables the user to retrieve error information (hardware or software malfunctions) from any IP Gateway remotely, over the web.

To read errors from the IP Gateway, do the following:

1.Follow the instructions under the Accessing the Web Server section above.

2.Click on the Error Logger link from the list of MOSCAD Tools. The following screen will be displayed.

3.To retrieve the errors from the site, click on the Read Errors button. To retrieve the errors from the site and clear the logger messages, click on the Read & Clear button. The errors will be displayed in the message area of the window.

6-23

IP Gateway Web Operation

4.To send the Error Logger messages from the screen via email, click on the Send Error Log by Email icon in the bottom left-hand corner of the screen. A new mail message will be opened in the PC's mail program and all errors retrieved from the site in the last session will be copied to the body of the message. Type in the destination address and send the message.

For a full description of the IP Gateway Toolbox Error Logger, see the SW Diagnostics & Loggers section above. For a full list of the Error Logger messages, see the Error Messages section below.

Retrieving Software Diagnostics using the Web Server

The Software Diagnostics program allows access to each of the modules (or ???devices???) that handle the various tasks of the MOSCAD RTU according to their logical names. The Software Diagnostics program provides reports on the status of each device at different levels of breakdown. It also provides historical and statistical data on the device activities. The Software Diagnostics data is useful for system maintenance, problem identification for remote services and statistics data on the communication system performance. The Web server enables the user to retrieve software diagnostics from the IP Gateway remotely, over the web.

To read software diagnostics from the IP Gateway, do the following:

1.Follow the instructions under the Accessing the Web Server section above.

2.Click on the Software Diagnostics link from the list of MOSCAD Tools. The following screen will be displayed.

3.Select the device name from the Device pull-down menu. If the device name does not appear on the list, click on the Open Device List button. This retrieves the full list of devices from the site.

4.Next enter the Level at which the diagnostics will be performed. All devices in the system have a level of request, starting from Level 0. Level 10 gets the data and resets all

6-24

IP Gateway Web Operation

counters. Level 11 gets the data without resetting the counters. For details on the devices and levels, see the Software Diagnostics Output section below.

5.To retrieve the diagnostics from the site, click on the GO button. The diagnostic messages will be displayed in the message area of the window.

6.To send the software diagnostics from the screen via email, click on the Send Diagnostics by Email icon in the bottom left-hand corner of the screen. A new mail message will be opened in the PC's mail program and all diagnostics retrieved from the site in the last session will be copied to the body of the message. Type in the destination address and send the message.

For more information on the IP Gateway ToolBox Software Diagnostics, see the SW Diagnostics & Loggers section above. For a detailed list of software diagnostic messages, see the Software Diagnostics Output section below.

Setting SNMP Configuration using the Web Server

The Web server enables the user to define SNMP and Motorola SSC parameters for the IP Gateway remotely, over the web.

To set the SNMP Configuration for the IP Gateway, do the following:

1.Follow the instructions under the Accessing the Web Server section above.

2.Click on the SNMP Configuration link from the list of MOSCAD Tools. The following screen will be displayed.

3.Enter values for each field, as described in the SNMP Configurator section above.

4.To download the SNMP configuration to the site, click on the Set Configuration button.

5.To refresh the data received from the sites in the internal IP Gateway cache, click on the Reload button.

6-25

IP Gateway Web Operation

For more information on the IP Gateway ToolBox SNMP Configurator, see the SNMP Configurator section above.

Sending Email to the Web Server Administrator

To send an email message to the Web Server system administrator, click on the Admin icon in the upper right-hand corner of the screen. A new mail message will be opened in the PC's mail program. Type in the message and send.

6-26

IP Gateway Telnet Application

General

The Telnet protocol is a standard protocol that provides virtual terminal communication, passing data from a remote Telnet host to the IP Gateway Telnet application.

In NFM systems, the IP Gateway Telnet application allows authorized users to access any communication devices that support an interactive interface.

Authorized users can establish connections with the IP Gateway from a Telnet window from any workstation (PC, UNIX, etc.) by using the IP Gateway Telnet Shell (user interface), to establish interactive session(s) with end devices.

The following figure shows the data passing from the Telnet hosts to the end devices.

Telnet User Interface

The IP Gateway Telnet Shell provides the following functionality:

???Telnet application administration - including password handling, adding and deleting new users, displaying a list of users and active sessions, etc.

???Listing the sites and network elements in the system.

???Performing terminal emulation to a network element device.

The IP Gateway Telnet interface supports multiple window sessions simultaneously, thus allowing parallel connection to the IP Gateway from different computers by different users.

The IP Gateway Telnet Shell is case sensitive.

The IP Gateway is organized hierarchically; zones contains sites which contain devices.

Connecting to the IP Gateway

To connect to the IP Gateway, perform the following steps on your host computer:

Type: telnet <IP Gateway IP Address>

At the Login prompt, enter your <login name>.

At the Password prompt, enter your <password>.

At the first startup, the only valid login name is root (generally the name of the superuser or system administrator.) The password for the superuser for the first startup is the existing MDLC password of the IP Gateway.

Upon entering the IP Gateway shell, the prompt becomes Gateway_Name> .

6-27

IP Gateway Telnet Operation

Telnet Command Summary

6-28

IP Gateway Telnet Operation

6-29

6-30

IP Gateway Telnet Operation

Example Output

The chart below depicts a list of users and sessions which might be displayed by the who command.

The chart below depicts a list of devices in a site which might be displayed by the dir command.

6-31

APPENDIX A:

RS232 Adapter Cables

This appendix provides the information required for connecting an RTU RS232 port to various units, as detailed below:

???Connection to a computer/terminal (MDLC protocol or User Port)

???Connection to a modem (MDLC protocol or User Port)

???Connection to a radio (MDLC protocol)

???RTU-to-RTU connection using MDLC protocol through RS232 ports (RS-Link)

Connection to a Computer or Terminal

To connect one of the RTU RS232 Ports to a computer/terminal, you should use the FLN6457 adapter, which ends with the female 25-pin or 9-pin, D-type connector. The port may be defined either as a MDLC protocol port or as a User Port.

The signals that appear on the female 25-pin or 9-pin D-type connector are according to the RS232 standard ??? see the following table. In this case, the RTU serves as DCE (Data Communication Equipment).

To extend the cable, you may use any extension cable with male and female D-type connectors (connected pin-to-pin, not crossed).

Note: When a User Port is defined as Computer/Terminal with DTR support:

1)The RTU will not transmit unless it receives DTR=ON from the computer/terminal.

2)The RTU will not receive unless it receives RTS=ON from the computer/terminal.

A-1

APPENDIX A:

RS232 Adapter Cables

Connection to a Modem

To connect one of the RTU RS232 Ports to a Modem, you should use the FLN6458 adapter, which ends with the male 25-pin or 9-pin D-type connector. The port may be defined either as a MDLC protocol port or as a User Port.

The signals that appear on the male 25-pin, or 9-pin D-type connector are according to the RS232 standard ??? see the following table. In this case, the RTU serves as DTE (Data Terminal Equipment).

To extend the cable, you may use any extension cable with male and female D-type connectors (connected pin-to-pin, not crossed).

Before transmitting, the RTU sends RTS=ON to the modem, and waits for CTS=ON from the modem as a condition for transmitting.

The RTU will receive data from the modem only when DCD=ON.

When using a modem in auto-answer mode (connected to a Computer port) for remote service, the RTU does not support RTS/CTS protocol since the port is designated to operate with a local computer as well as with a modem.

Connection to a Radio

Note: On all of the Motorola RJ45 connector heads, the numbering of the pins is different than the standard, as shown in the figure below. Pin 1-8 are left to right rather than right to left, as shown below. Therefore, only original Motorola cables should be used.

A-2

APPENDIX A:

RS232 Adapter Cables

Connection to VRM650/VRM660 radio

To connect the RTU (via Port 2 or Port 3) to a VRM650/VRM660 radio, you should use the FKN4895A adapter, which ends with the male 9-pin, D-type connector. The port should be defined as RS232, Async, External Modem, RD-LAP, RTU (LineX).

Connection to Conventional Astro radio

To connect the RTU (via Port 2 or Port 3) to a Conventional Astro radio, you should use the FKN4905A adapter, which ends with the male 15-pin, D-type connector. The port should be defined as RS-232, Async, SLIP, ASTRO SPECTRA, MDLC over IP.

A-3

APPENDIX A:

RS232 Adapter Cables

RTU-to-RTU Connection Using MDLC Protocol through RS232

To establish a link between two RTUs using MDLC protocol, the ports of both RTUs should be defined as RS232 RTU-to-RTU (RS-Link). The ports of the two RTUs should be connected by the FLN6457 and FLN6458 adapters, when the adapters are connected.

!IMPORTANT

Do not connect between RTUs without the adapter cables. A direct connection will cause a short circuit between the pins that have the same function.

A-4

APPENDIX A:

RS232 Adapter Cables

RTU-to-RTU Synchronous Communication

Using Port 3, 4

The pin assignment of the cable to be used for RTU-to-RTU synchronous communication (using Port 3, 4) is given below.

A-5

APPENDIX B:

Remote ToolBox Modem Setup

Hayes ACCURA 144 + FAX 144

Configuration (9600 Baud)

at&v

ACTIVE PROFILE:

B0 E1 L1 M1 N0 Q0 T V1 W0 X4 Y0 &C1 &D0 &G0 &J0 &K0 &Q6 &R1 &S0 &T5 &X0 &Y0 S00:001 S01:000 S02:043 S03:013 S04:010 S05:008 S06:002 S07:050 S08:002 S09:006 S10:014 S11:095 S12:050 S18:000 S25:005 S26:001 S36:007 S37:009 S38:020 S44:020 S46:136 S48:007 S95:000

STORED PROFILE 0:

B0 E1 L1 M1 N0 Q0 T V1 W0 X4 Y0 &C1 &D0 &G0 &J0 &K0 &Q6 &R1 &S0 &T5 &X0 S00:001 S02:043 S06:002 S07:050 S08:002 S09:006 S10:014 S11:095 S12:050 S18:000 S36:007 S37:009 S40:104 S41:192 S46:136 S95:000

STORED PROFILE 1:

B1 E1 L1 M1 N1 Q0 T V1 W0 X4 Y0 &C1 &D2 &G0 &J0 &K3 &Q5 &R1 &S0 &T5 &X0 S00:000 S02:043 S06:002 S07:050 S08:002 S09:006 S10:014 S11:095 S12:050 S18:000 S36:007 S37:000 S40:104 S41:195 S46:138 S95:000

TELEPHONE NUMBERS:

Modem Settings

AT&F0

ATB0

ATN0

AT&D0

AT&K0

ATS0=1

ATS37=9

AT&W0

AT&Y0

B-1

APPENDIX B:

Remote ToolBox Modem Setup

Command Summary

(* indicates a change from the default)

*B0 ITU-T answer sequence

*E1 Enable local echo

(Must be set to E0 when modem is connected directly to the RTU as opposed to the PC.)

L1 Low volume

M1 Speaker ON until CONNECT

*N0 Automode is disabled. The handshake will occur based on the value of

B-2

APPENDIX B:

Remote ToolBox Modem Setup

S-Registers

(* indicates a change from default)

*S00=001 sets the number of rings before modem answers

*S037=009 Desired DCE Line Speed

(This information is according to the standard Hayes Command Set. This was not in this modem???s documentation. Use with caution.)

0Use Last AT Speed

1Reserved (75)

2Reserved (110)

3300

4Reserved (600)

51200

62400

74800

87200

99600

1012000

1114400

B-3

APPENDIX B:

Remote ToolBox Modem Setup

Motorola OnlineSURFR 28.8

Configuration (9600 Baud)

at&v

ACTIVE PROFILE:

B0 E1 L2 M1 Q0 V1 W0 X4 &B1 &C1 &D0 &G0 &L0 &P0 &Q0 &R1 &S0 &X0 &Y0 %A013 %C0 %G0 \A3 \C0 \G0 \J0 \K5 \N0 \Q0 \T000 \V1 \X0 -J0 "H0 "O032

S00:001 S01:000 S02:043 S03:013 S04:010 S05:008 S06:002 S07:060 S08:002 S09:006 S10:014 S11:095 S12:050 S18:000 S25:005 S26:001 S37:009 S72:000

STORED PROFILE 0:

B0 E1 L2 M1 Q0 V1 W0 X4 &B1 &C1 &D0 &G0 &L0 &P0 &Q0 &R1 &S0 &X0 %A013 %C0 %G0 \A3 \C0 \G0 \J0 \K5 \N0 \Q0 \T000 \V1 \X0 -J0 "H0 "O032 S00:001 S02:043 S03:013 S04:010 S05:008 S06:002 S07:060 S08:002

S09:006 S10:014 S11:095 S12:050 S18:000 S25:005 S26:001 S37:009 S72:000

TELEPHONE NUMBERS: &Z0=

&Z1=

&Z2=

&Z3=

Modem Settings

AT&F0

ATB0

AT&D0

AT&R1

AT%C0

AT%G0

AT\N0

AT\Q0

AT\V1

AT-J0

AT???H0

ATS0=1

ATS37=9

AT&W0

AT&Y0

B-4

APPENDIX B:

Remote ToolBox Modem Setup

Command Summary

(* indicates a change from the default)

*B0 ITU-T answer sequence

*E1 Enable local echo

*-J0 Disable detection of type of V.42 error correction

B-5

APPENDIX B:

Remote ToolBox Modem Setup

S-Registers

(* indicates a change from default)

*S00=001 sets the number of rings before modem answers

B-6

APPENDIX B:

Remote ToolBox Modem Setup

Motorola OnlineSURFR 33.6

Configuration (9600 Baud)

at&v

ACTIVE PROFILE:

B0 E1 L2 M1 Q0 V1 W0 X4 &B1 &C1 &D0 &G0 &L0 &P0 &Q0 &R1 &S0 &X0 &Y0 %A013 %C0 %G0 \A3 \C0 \G0 \J0 \K5 \N0 \Q0 \T000 \V1 \X0 -J0 "H0 "O032

S00:001 S01:000 S02:043 S03:013 S04:010 S05:008 S06:002 S07:060 S08:002 S09:006 S10:014 S11:095 S12:050 S18:000 S25:005 S26:001 S37:009 S72:000

STORED PROFILE 0:

B0 E1 L2 M1 Q0 V1 W0 X4 &B1 &C1 &D0 &G0 &L0 &P0 &Q0 &R1 &S0 &X0 %A013 %C0 %G0 \A3 \C0 \G0 \J0 \K5 \N0 \Q0 \T000 \V1 \X0 -J0 "H0 "O032 S00:001 S02:043 S03:013 S04:010 S05:008 S06:002 S07:060 S08:002

S09:006 S10:014 S11:095 S12:050 S18:000 S25:005 S26:001 S37:009 S72:000

TELEPHONE NUMBERS: &Z0=

&Z1=

&Z2=

&Z3=

Modem Settings

AT&F0

ATB0

AT&D0

AT&R1

AT%C0

AT%G0

AT\N0

AT\Q0

AT\V1

AT-J0

AT???H0

ATS0=1

ATS37=9

AT&W0

AT&Y0

B-7

APPENDIX B:

Remote ToolBox Modem Setup

Motorola OnlineSURFR 56K

Configuration (9600 Baud)

at&v

ACTIVE PROFILE:

B0 E1 L2 M1 Q0 V1 W0 X4 &B1 &C1 &D0 &G0 &L0 &P0 &Q0 &R1 &S0 &X0 &Y0 %A013 %C0 %G0 \A3 \C0 \G0 \J0 \K5 \N0 \Q0 \T000 \V1 \X0 -J0 "H0 "O032

S00:001 S01:000 S02:043 S03:013 S04:010 S05:008 S06:002 S07:060 S08:002 S09:006 S10:014 S11:095 S12:050 S18:000 S25:005 S26:001 S37:009 S72:000

STORED PROFILE 0:

B0 E1 L2 M1 Q0 V1 W0 X4 &B1 &C1 &D0 &G0 &L0 &P0 &Q0 &R1 &S0 &X0 %A013 %C0 %G0 \A3 \C0 \G0 \J0 \K5 \N0 \Q0 \T000 \V1 \X0 -J0 "H0 "O032 S00:001 S02:043 S03:013 S04:010 S05:008 S06:002 S07:060 S08:002

S09:006 S10:014 S11:095 S12:050 S18:000 S25:005 S26:001 S37:009 S72:000

TELEPHONE NUMBERS: &Z0=

&Z1=

&Z2=

&Z3=

Modem Settings

AT&F0 Restore factory configuration 0

AT+MS=9,0,9600,9600 Modulation mode (9=V.32, 9600 or 4800), 0=forced, min speed=9600, max speed=9600

AT&D0 Modem ignores DTR ATE0 Turn off command echo AT&R1 CTS is always active

AT&K0 Disable computer/modem flow control

AT\N1 Normal speed buffered mode (no error correction) AT%C0 Disable data compression

ATS0=1 Rings to autoanswer = 1

AT\V1 Connect messages displayed in single line format ATW2 Report modem-to-modem speed in error correction mode AT&W0 Store active profile in NVRAM profile 0

AT&Y0 Recall stored profile 0 upon power up

B-8

APPENDIX B:

Remote ToolBox Modem Setup

UDS V.3225

Configuration (9600 Baud)

at&v

ACTIVE PROFILE

S00:001 S01:000 S02:043 S03:013 S04:010 S05:008 S06:002 S07:030 S08:002 S09:006 S10:014 S12:050 S14:8AH S16:00H S18:000 S21:84H S22:46H S23:00H S25:005 S26:000 S27:08H S28:015 S29:000 S32:06H S34:00H S52:000 S53:00H S54:01H S57:00H S58:000 S59:005 S60:41H S61:1EH S62:000 S63:255 S67:005 S69:005 S70:001 S71:00H S72:00H S78:030 S79:035

OK

Modem Settings

Instructions to load Factory Option Set #2 (Asynchronous Dial-up without MNP) (Settings are made from front panel of modem.)

???(Brief message will be displayed)

B-9

APPENDIX B:

Remote ToolBox Modem Setup

Factory Option Set #2 (Asynchronous Dial-up without MNP)

???MODEM PARAMETERS

DCE RATE = DTE RATE

NORMAL ORIGINATE

FAST TRAIN DISABLED

AUTO RETRAIN ENABLED

TRANSMIT CLOCK INTERNAL

DIAL LINE

JACK TYPE RJ11 (PERMISSIVE)

LINE CURRENT DISCONNECT LONG ENABLED

LONG SPACE DISCONNECT ENABLED

V.22 GUARD TONE DISABLED

???MNP PARAMETERS

MNP PROTOCOL DISABLED *

DTE SPEED = DCE SPEED *

FLOW CONTROL DISABLED *

XON/XOFF PASS THROUGH DISABLED

DATA COM PRESSION ENABLED *

MNP ACTIVITY TIMER OFF

MNP BREAK CONTROL 0 *

???DTE PARAMETERS

ASYNC DATA DTE RATE = 9600 8 BIT

NO PARITY

AT COMMAND SET ENABLED

IGNORES DTR

DSR FORCED HIGH

DCD FORCED HIGH

CTS FORCED HIGH

DTE FALLBACK DISABLED

OPTIONS RETAINED AT DISCONNECT

???TEST PARAMETERS

BILATERAL ANALOG LOOP DISABLED

BILATERAL DIGITAL LOOP DISABLED

DTE LOCAL TEST DISABLED

DTE REMOTE TEST DISABLED

REMOTE COMMANDED TEST ENABLED

TEST TIMEOUT OFF

???DIAL/DBU PARAMETERS

TONE DIAL AUTO DIAL #1

WAIT FOR DIAL TONE

WAIT DELAY 2 SECONDS

PAUSE DELAY 2 SECONDS

CALL TIMEOUT 30 SECONDS

ANSWER ON 1 RING

B-10

APPENDIX B:

Remote ToolBox Modem Setup

???SPEAKER OPTION

VOLUME MEDIUM

ON UNTIL CARRIER DETECT

* Indicates variation from factory option set #1 (Information taken directly from manual)

B-11

APPENDIX B:

Remote ToolBox Modem Setup

USRobotics Sportster 14400 Fax

Configuration (9600 Baud)

ati4

USRobotics Sportster 14400 Fax Settings...

B0 E1 F1 M1 Q0 V1 X4 Y0

BAUD=9600 PARITY=N WORDLEN=8

DIAL=HUNT ON HOOK

&A1 &B1 &C1 &D0 &G0 &H0 &I0 &K0 &M0 &N6 &P0 &R1 &S0 &T5 &Y1

S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002

S07=060 S08=002 S09=006 S10=007 S11=070 S12=050 S13=000

S14=000 S15=000 S16=000 S17=000 S18=000 S19=000 S20=000

S21=010 S22=017 S23=019 S24=000 S25=005 S26=000 S27=000

S28=008 S29=020 S30=000 S31=000 S32=000 S33=000 S34=006

S35=000 S36=014 S37=009 S38=000 S44=015 S51=000

LAST DIALED #:

Modem Settings

AT&F0

AT&A1

AT&D0

AT&H0

AT&K0

AT&N6

AT&R1

ATS0=1

ATS37=9

AT&W0

ATY0

B-12

APPENDIX B:

Remote ToolBox Modem Setup

Command Summary

(* indicates a change from the default)

B0 ITU-T answer sequence

*E1 Enable local echo

B-13

APPENDIX B:

Remote ToolBox Modem Setup

S-Registers

(* indicates a change from default)

*S00=001 sets the number of rings before modem answers

*S037=009 Desired DCE Line Speed

(This information is according to the standard Hayes Command Set. This was not in this modem???s documentation. Use with caution.)

0Use Last AT Speed

1Reserved (75)

2Reserved (110)

3300

4Reserved (600)

51200

62400

74800

87200

99600

1012000

1114400

B-14

APPENDIX B:

Remote ToolBox Modem Setup

USRobotics Sportster 28800 Fax

Configuration (9600 Baud)

Use the following dip switch settings on the back of the modem:

1.Down (Ignore DTR)

2.Up (Verbal result codes)

3.Down (display result codes)

4.Up (echo off line commands)

5.Up (auto ans first ring)

6.Up (CD normal)

7.Up (upload at powerup)

8.Down (smart mode)

Modem Settings

AT&F0

AT&A1 (Enables ARQ codes)

AT&D0 (DTR ignored)

AT&H0 (Flow control disabled)

AT&K0 (Data compression disabled)

AT&N6 (Forces connection at 9600 baud or modem hangs up)

AT&R1 (Modem ignores RTS)

ATS0=1 (Answer on first ring)

ATS37=9 (no effect)

AT&W0 (store to NVRAM 0)

ATY0 (defaults to profile 0 at power up)

B-15

APPENDIX B:

Remote ToolBox Modem Setup

Command Summary

(* indicates a change from the default)

B0 ITU-T answer sequence

*E1 Enable local echo

B-16

APPENDIX B:

Remote ToolBox Modem Setup

S-Registers

(* indicates a change from default)

*S00=001 sets the number of rings before modem answers

*S037=009 Desired DCE Line Speed

(This information is according to the standard Hayes Command Set. This was not in this modem???s documentation. Use with caution.)

0Use Last AT Speed

1Reserved (75)

2Reserved (110)

3300

4Reserved (600)

51200

62400

74800

87200

99600

1012000

1114400

B-17

APPENDIX B:

Remote ToolBox Modem Setup

USRobotics Sportster 56K Fax

Configuration (9600 Baud)

Use the following dip switch settings on the back of the modem:

9.Down (Ignore DTR)

10.Up (Verbal result codes)

11.Down (display result codes)

12.Up (echo off line commands)

13.Up (auto ans first ring)

14.Up (CD normal)

15.Up (upload at powerup)

16.Down (smart mode)

Modem Settings

AT&F0

AT&A1 (Enables ARQ codes)

AT&D0 (DTR ignored)

AT&H0 (Flow control disabled)

AT&K0 (Data compression disabled)

AT&N6 (Forces connection at 9600 baud or modem hangs up)

AT&R1 (Modem ignores RTS)

ATS0=1 (Answer on first ring)

ATS37=9 (no effect)

AT&W0 (store to NVRAM 0)

ATY0 (defaults to profile 0 at power up)

B-18

APPENDIX B:

Remote ToolBox Modem Setup

Intel SatisFAXtion Modem/400e

ACTIVE PROFILE:

B0 E1 L0 M1 T Q0 V1 X4 Y0 &C1 &D0 &G0 &L0 &P0 &Q0 &R0 &S0 &X0 &Y0 \A3 %A013 \C0 %C1 %E1 \G0 \J0 \K5 \N3 \Q0 \T00 \V2 \X0 -J1 "H3 "S0 "O250 S00:001 S01:000 S02:043 S03:013 S04:010 S05:008 S06:002 S07:060

S08:002 S09:006 S10:014 S11:070 S12:050 S18:000 S25:005 S26:001 S31:000

STORED PROFILE 0:

B0 E1 L0 M1 T Q0 V1 X4 Y0 &C1 &D0 &G0 &L0 &P0 &Q0 &R0 &S0 &X0 \A3 %A013 \C0 %C1 %E1 \G0 \J0 \K5 \N3 \Q0 \T00 \V2 \X0 -J1 "H3 "S0 S00:001 S07:060 S11:070 S18:000 S23:027 S25:005 S26:001 S27:000 S31:000

STORED PROFILE 1:

B1 E1 L2 M1 T Q0 V1 X4 Y0 &C1 &D2 &G0 &L0 &P0 &Q0 &R0 &S0 &X0 \A3 %A013 \C0 %C1 %E1 \G0 \J0 \K5 \N3 \Q3 \T00 \V2 \X0 -J1 "H3 "S0 S00:000 S07:060 S11:070 S18:000 S23:011 S25:005 S26:001 S27:064 S31:000

TELEPHONE NUMBERS: &Z0

&Z1

&Z2

&Z3

OK

Modem Settings

AT&F

ATB0

ATT

AT&C1

AT&D0

AT&K0

ATS0=1

AT&W0

AT&Y0

B-19

APPENDIX B:

Remote ToolBox Modem Setup

Command Summary

(* indicates a change from the default)

*B0 ITU-T answer sequence

*E1 Enable local echo

(Must be set to E0 when modem is connected directly to the RTU as opposed to the PC.)

L1 Low volume

M1 Speaker ON until CONNECT

*N0 Automode is disabled. The handshake will occur based on the value of

B-20

APPENDIX B:

Remote ToolBox Modem Setup

S-Registers

(* indicates a change from default)

*S00=001 sets the number of rings before modem answers

*S037=009 Desired DCE Line Speed

(This information is according to the standard Hayes Command Set. This was not in this modem???s documentation. Use with caution.)

0Use Last AT Speed

1Reserved (75)

2Reserved (110)

3300

4Reserved (600)

51200

62400

74800

87200

99600

1012000

1114400

B-21

Software Diagnostics Output

This section lists the diagnostics which are available for the various MOSCAD RTU devices. The messages are listed as they appear on the screen, with %% signs in the text to represent the device???s current alphanumeric values.

The description which follows the diagnostics messages, provides an explanation for the variables.

Terms that are used frequently in diagnostics are described below:

1.Number of logical mini-sessions that serve the RTU applications. A mini-session is an API layer that serves the RTU-to-RTU communications, event bursts, and setcall.

2.The number of logical channels above the Presentation layer from which the RTU can initiate communications. In an RTU there are no such logical channels as there is no application that can initiate a call. Control centers (e.g. MCP-M) do have such applications such as schedulers and command dispatchers.

3.The number of logical channels above the Presentation layer through which the RTU reacts to calls simultaneously (such as error logger, diagnostics, D.B. monitor, process monitor, date and time, download). The RTU does not need more than 2-4 channels for regular and orderly activity.

C-1

Software Diagnostics Output

## 17 LEVEL = 1

Minisession Channels

--------------------

This is the applications table that uses the mini-session API for communication purposes. For each application this table records the key for the instance of the mini-session, and the application ID.

## 18 LEVEL = 2

This table defines the logical channels located above the Presentation layer, and capable of initiating communications. For each channel the table records the call destination. The destination address consists of the site ID, the port ID, and the link ID.

## 19 LEVEL = 3

This table defines the active logical channels that can react to communications from ToolBox, the control center, MCP-M, or MCP-T. For each logical channel, the table records information about the SRC that initiated the call, namely, the site ID, link ID, Port ID and the identification number of the logical channel that was used for the call.

## 20 LEVEL = 4

Frame Sequence Channels

-----------------------

Frame Seq Key Application Id

------------- --------------

The Frame Seq Key field holds the key of the application that should receive the frames originating from the corresponding application on the transmitting side, specified in the Application ID field.

## 21 LEVEL = 5

C-2

Software Diagnostics Output

T_reset The amount of time a unit waits after having acknowledged repeated reset requests, before sending its own reset frame.

T_dup The amount of time a unit, which has received frames with identical numbers, considers them as duplicates instead of new transmissions.

T_hole The amount of time a unit, which has received frames with holes in the sequence numbers, still expects to receiving the missing frames.

B_reset 1 means that the frame contains a reset bit.

B_ack 1 means that the frame contains a reset ACK bit.

## 23

Current Waiting Buffers Number of frames held in Waiting Queue.

HEAP DEVICE = HP_F_TX, HP_F_RX, HP_UF_A, HP_UF_U

C-3

Software Diagnostics Output

## 32 LEVEL = 0

1.Number of buffers in heap instance

2.Number of free buffers in heap.

3.Minimum number of free buffers left in heap since the last diagnostic. This information reflects the extent to which the heap is capable of meeting RTU needs under heavy traffic.

4.The number of times, since the last diagnostic, the RTU software detected an empty heap. A large number of times points to incorrect allocation of memory resources.

5.Size of buffer including the overhead for managing a single buffer.

6.The flag that indicates that the RTU is in startup stage.

7.The flag that points to memory overwrite in the memory area allocated to the heap.

8.Unit of time to be measure how long a buffer is out of the heap (used by other parts of the system).

9.10. and 11. The heap consists of a chain of joined buffers. For chain management purposes, a key holds pointers to the beginning of the chain, the end of the chain, and to the next buffer that will be taken from the chain. The P_current_chain value must be (numerically) between the start and end values.

## 32 LEVEL = 1

Buf Key Next Cntr #FF

--------------------------------------

Buf Address of the buffer in the memory.

Key Handle (identifier) of the heap. (If =0, buffer is in heap. Otherwise buffer is in use by system.)

Next Next buffer in heap to be allocated. (Meaningful only if key=0.)

Cntr Counts intervals of time that the buffer is out of the heap. (Meaningful only if key ??? 0)

#FF Forced free. (Meaningful only if key ??? 0.) Indicates the total number of units that the buffer was in use out of the heap. Set back to zero when heap is returned to heap. If this value is greater than 3, there may be a memory leak problem. Please consult product group.

C-4

Software Diagnostics Output

ADAPTER DEVICE = COM1A,RTU1A, LIN1A,???

## 48 LEVEL = 0

General - The adapter is the layer which coordinates the transmission / reception of the MDLC frame above Asynchronous Port.

1.The physical asynchronous key.

2.PIN Table - A pointer which allows ???cabling??? during run time to the physical asynchronous layer selected in Site Configuration.

3.The Rx Heap key - This is the key to the formatted buffer Heap HP_F_RX to be used to collect the stream of bytes which is received in the Asynchronous Port in the MDLC Frame.

4.The Tx Heap key - This is the key to the unformatted buffer Heap HP_UF_A to be used to convert the MDLC frame into a stream of bytes for transmitting through the Asynchronous Port.

5.0XFFFF - means receiving every MDLC frame regardless of its address. (used for the Protocol Analyzer)

6.The System address - In the local port (not above radio) the value is zero , even if the user chooses a different value.

7.The Site ID.

8.Used for transmissions in the local address (-2).

9.Used as a default router address

10.Whether or not to allow reception of SYNC frames.

11.TimeAuth device key in Hexadecimal form.

12.TimeAuth identifier.

13.Offset of Authentication stamp within the buffer for authenticated SYNC frames only.

C-5

Software Diagnostics Output

## 49 LEVEL = 10,11

1.The number of unformatted frames that have been transmitted.

2.The number of unformatted frames that have been transmitted and for which the physical layer returned a fail signal.

3.The number of received frames includes only correct frames (including acknowledgment frames).

4.The number of unformatted frames that have been received with some error.

5.The following figure illustrates the mask:

6.Number of synchronization frames which were not properly authenticated.

C-6

1.The logical channel number.

2.The number of seconds between transmission attempts when ACK is not received at the Transport layer.

3.The number of seconds between transmission attempts when a Busy ACK is received. (not enough logical channels on the answering site).

4.The preset time that the site will wait until it issues its ACK to a partial reception.

5.The preset time that the site will wait for the first time until it asks the other site ???is session on????

6.The current number of seconds between transmission attempts.

7.The current number of seconds between transmission attempts in case of Busy ACK.

8.The actual time that the site waits until it issues its ACK to a partial reception.

9.The actual time that the site will wait for the first time until it asks the other site ???is session on????

10.Number of transmission attempts.

11.Number of transmission attempts in case of Busy ACK.

12.The current number of transmission attempts.

13.The current number of transmission attempts in case of Busy ACK.

14.The sequence number of the master session at the initiator???s site.

15.The current number of frames in a single transmission while waiting for ACK on the receiving site.

C-7

Software Diagnostics Output

16.The total number of frames in a single transmission while waiting for ACK on the receiving site.

17.The size of the Tx queue until the Transport layer suspends the application.

18.The index of the next buffer to be transmitted. (beginning of queue).

19.The index of the next buffer to be added to the queue. (end of queue).

20.The sequence number of the first frame and last frame in the queue.

21.The size of the Rx queue.

22.The next frame to be received by the Rx queue.

23.The sequence number of the frame to be received.

24.The expected sequence number of the next frame to be received.

25.The location of the next frame to be received in the Rx queue.

26.A temporary queue in case of holes in reception (the receiving sequence number is different from expected). The data is similar to the Rx queue

27.Does Transport expect start session in the next frame to be received?

28.Is Sync ACK required?

29.Has Sync ACK arrived?

30.Was Sync ACK transmitted? Have new frames been received?

31.Is this Instance master or slave?

32.Is this Instance in Tx state?

33.Has a Reset been sent from the Master?

34.Has the current session been aborted?

35.Send ACK in next transmission?

36.Is this the first burst in the current transmission for sending Start Session?

37.Is the Transport layer retrying?

## 65 LEVEL = 1

The number of MDLC frames in each queue in this instance of the Transport layer.

C-8

1.The # of Transmitted Frames (does not include retransmission and acknowledgment frames.)

2.The # of Received Frames (includes only correct frames.)

3.The # of Re-transmitted Frames represents only frames rejected by the physical layer (do not use this number; use the # of Re-transmitted Frames in the Link device).

MTE

## 80 LEVEL = 0

1.The amount of unused memory in bytes.

2.The amount of memory that the MTE (the operating system) received at startup and distributed among all of the instances that were created in the system.

3.The number of tasks (infinite threads) that were created according to the site configuration.

4.The total number of instances created by the MTE according to the site configuration.

5.The number of extra bytes for each stack. These bytes are designed to detect memory corruption.

6.The length in bytes of the supervisor stack.

7.The amount of unused bytes in the supervisor stack.

8.The length in bytes in the MTE structures ??? TCB (Task Control Block) and DCB (Device Control Block).

C-9

Software Diagnostics Output

9.Data on the current task (the task ID and the task priority).

10.The RTU tasks are wrapped by two inner tasks (high, low) which are to be reached by the CPU every so and so ticks (the numbers are defined).

11.These two numbers are the maximum reached by the two tasks above.

## 81 LEVEL = 1

The list of all of the instances created, the key of each one of them and its address in memory.

## 82 LEVEL = 2

The list of all of the tasks created in the system, the stack address of each one of them, and the current number of unused bytes.

LINK

## 112 LEVEL = 0

1.The number of MDLC frames that the Link layer can handle simultaneously.

2.The number of ACK frames that are available to the instance Link for transmitting ACK for the receiving MDLC frames.

3.The number of bits reserved for the sequence number in the Link layer protocol of the MDLC Frame.

C-10

Software Diagnostics Output

4.The number of times the MDLC frame was retried without receiving ACK.

5.The number of MDLC frame retries that received Busy ACK. (The receiving site does not have enough room to handle it because of overload).

6.The number of seconds between transmission attempts in case of Busy ACK.

7.The number of times the broadcast frame was retried.

8.The number of different addresses the Link will transmit to simultaneously.

9.The RTU Site ID.

10.The RTU System address.

11.The time that the Link layer waits when the Physical layer returns Busy to the transmission attempts of the Link layer in ???private conversation???, until it retries.

12.The number of times the Link layer will try to transmit to the Physical layer, if the latter returns Busy in ???private conversation???.

13.The Link layer is capable of answering a range of addresses. This number is the upper bound that the RTU reacts to, whereas the lower bound is the Site ID.

14.Flag which indicates AUTH TX state (1=YES, 0=NO)

15.Flag which indicates AUTH RX state (1=YES, 0=NO)

16.Flag which indicates Stop obeying AUTH TX (1=YES, 0=NO)

17.Flag which indicates Start obeying AUTH TX (1=YES, 0=NO)

18.Flag which indicates Stop obeying AUTH RX (1=YES, 0=NO)

19.Flag which indicates Start obeying AUTH RX (1=YES, 0=NO)

20.Flag which indicates that AUTH is active for TX (1=YES, 0=NO)

21.Flag which indicates that AUTH is active for RX (1=YES, 0=NO)

22.Flag which indicates Obeying AUTH TX (1=YES, 0=NO)

23.Flag which indicates Obeying AUTH RX (1=YES, 0=NO)

24.TimeAuth identifier

25.TimeAuth device key (HEX)