User’s Manual ToolBox for MOSCAD™ IP Gateway Version 5.50 68P02958C00-B MOTOROLA and the Stylized M Logo are registered in the U.S. Patent and Trademark Office. All other product or service names are the property of their respective owners.
COMMERCIAL WARRANTY (STANDARD) Motorola radio communications products are warranted to be free from defects in material and workmanship for a period of ONE (1) YEAR, (except for crystals and channel elements which are warranted for a period of ten (10) years), from the date of shipment.
Contents Introduction .......................................................................................................................................... 1-1 Scope of the Manual .............................................................................................................................................. 1-1 Introducing the IP Gateway ...................................................................................................................................
Contents Uninstalling the IP Gateway Toolbox Application .............................................................................................. 4-11 IP Gateway Toolbox ............................................................................................................................. 5-1 General Concept .................................................................................................................................................... 5-1 Site Configuration ...............
Contents Terminal Server............................................................................................................................................... 5-32 Advanced Parameters .......................................................................................................................................... 5-39 Physical layer ..................................................................................................................................................
Contents About............................................................................................................................................................... 5-72 MDLC Links Configurator................................................................................................................ 5-73 The MDLC Links Configurator Window............................................................................................................. 5-73 Icons ...................................
Contents View Menu .......................................................................................................................................................... 5-91 Toolbar ............................................................................................................................................................ 5-91 Table bar ........................................................................................................................................................
Contents Edit Menu .......................................................................................................................................................... 5-113 Download This session.................................................................................................................................. 5-113 Rename Session.............................................................................................................................................
Contents Contents......................................................................................................................................................... 5-123 How to Use Help ........................................................................................................................................... 5-123 About Dial Up ...............................................................................................................................................
Contents Window Menu ................................................................................................................................................... 5-135 Cascade ......................................................................................................................................................... 5-135 Tile ................................................................................................................................................................
Contents Edit Menu .......................................................................................................................................................... 5-150 New ............................................................................................................................................................... 5-150 Delete ..........................................................................................................................................................
Contents Save As.......................................................................................................................................................... 5-164 Select Central File ......................................................................................................................................... 5-165 Close Central File.......................................................................................................................................... 5-165 Print..
Contents Adding Terminal Server Ports ............................................................................................................ 6-6 General .................................................................................................................................................................. 6-6 Site Configuration for Terminal Server .................................................................................................................
Contents USRobotics Sportster 14400 Fax........................................................................................................................ B-12 USRobotics Sportster 28800 Fax........................................................................................................................ B-15 USRobotics Sportster 56K Fax........................................................................................................................... B-18 Intel SatisFAXtion Modem/400e....
Contents LNKHNDL....................................................................................................................................................... C-131 DOCTOR.......................................................................................................................................................... C-132 Error Messages ................................................................................................................................
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.
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.
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.).
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).
Introduction NFM Central MOSCAD ToolBox (over IP) Ethernet SNMP TCP/IP IP Gateway (Proxy MIB) IP Network Ethernet Ethernet MOSCAD NFM RTU MOSCAD NFM RTU SNMP Network Elements Network Elements MDLC Network MOSCAD NFM RTU MOSCAD NFM RTU Network Elements Network Elements MOSCAD RTU MOSCAD RTU Network Elements Network Elements 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) conne
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: • • • • • • conventional radio trunked radio data radio, dial-up lines leased lines, microwave, fiber optic links combined networks 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
System Overview SCADA Computer Work Stations TCP/IP on Ethernet MOSCAD ToolBox IP Gateway RS232 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.
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.
System Overview SCADA Central Ethernet LINE 1 IP Gateway ToolBox (over IP) IP Gateway (Proxy MIB) RS232 IP Network Ethernet MDLC Network Terminal Server MOSCAD Programming ToolBox (over IP) LINE 1 LINE 1 Terminal Server LINE 1 LINE 1 RS232 MOSCAD RTU IP1 MOSCAD RTU IP2 MOSCAD RTU IP3 MOSCAD RTU IP4 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.
System Overview SCADA Central Ethernet IP Cloud LINE 1 IP Gateway ToolBox (over IP) RS232 IP Gateway RNC ASTRO RF System MOSCAD Programming ToolBox (over IP) IP Network ASTRO Spectra Radio ASTRO Spectra Radio LINE 1 SLIP Connection LINE 1 SLIP Connection RS232 MOSCAD RTU MOSCAD-L RTU Figure 2-4: Typical Configuration, MDLC via Astro IP MDLC Over Private DataTac MOSCAD RTUs can communicate over Private DataTac systems (RDLAP) with SCADA centrals and with other RTUs.
System Overview SCADA Central Host Computer Ethernet IP Cloud LINE 1 RS232 IP Gateway with Reflector IP Gateway ToolBox (over IP) RNC RF System Private DataTAC Radio Private DataTAC Radio MOSCAD Programming ToolBox (over IP) RS232 RS232 RS232 MOSCAD RTU MOSCAD-L RTU 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.
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.
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: Connect /* Establish Connection to Gateway. */ Poll /* Send a polling request. */ Receive /* Receive MDLC communication (answer) buffer.
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.
System Overview Network Management Center System Support Center Telnet Work Station TCP/IP on Ethernet MOSCAD ToolBox Terminal Server RS232 1 ... 32 Communication Site MDLC SC RS485 EMU ... EMU EMU MDLC Network ENVIRONMENTAL SENSORS DEVICE DEVICE W X LEGEND Device Application Site Concentrator SC EMU Element Management Unit Communication Site MDLC SC Communication Site MDLC SC RS485 RS485 EMU ... ENVIRONMENTAL SENSORS EMU EMU DEVICE DEVICE Y Z EMU ...
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.
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 al
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.
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.
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.
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.
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 Wireline: Supports the following modem and their characteristics: • 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.
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.
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.
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: Connector Type/Usage Pin No. Power 4 pin Male Connector/ AC Power 1 Relay 2 Vin 3 P.GND 4 GND 1 TXD 2 RXD 3 CTS 4 P.GND 5 CD 6 RTS 7 CNTRL 8 DTR 1 +12V 2 DO_/rI_ 3 DO / RI 4 P.
Hardware Installation Port 1B Port 1A AUI / Ethernet RJ45 / Ethernet 5 CD 6 RTS 7 CNTRL 8 DTR 1 GND 2 COL+ 3 DO+ 4 GND 5 DI+ 6 GND 7 N.C 8 GND 9 COL- 10 DO- 11 GND 12 DI- 13 +12V 14 GND 15 N.C 1 TD+ 2 TD- 3 RD+ 4 N.C 5 N.C 6 RD- 7 N.C 8 N.C For connection of Port 3 and 4, refer to the J4 connector in the MOSCAD CPU Module in the MOSCAD RTU Service Manual.
Hardware Installation Use the “Thin-Wire to AUI” unit for connecting the IP Gateway to “Thin-Wire LAN” (coaxial media. A unique Ethernet port address is assigned by Motorola at the factory. This address is on a sticker, placed on the Gateway main board (but you don’t need to know it to run the Gateway). The IP address for the IP Gateway should be assigned by the network administrator and has to be set via the IP Gateway Toolbox. Like the Ethernet address, the IP address should be a unique number.
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.
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. Indication Port Description PWR The IP Gateway is DC powered. RST A hardware or software reset is being executed. DIAG An ERROR Message is pending in the Error-Logger.
Hardware Installation Figure 3-6: IP Gateway Indication Panel LEDs Combinations A combination of lighted LEDs indicates a malfunction in the CPU. The nature of the malfunction is indicated by the LEDs which light simultaneously with the DIAG LED, as detailed below: (DIAG LED is on): • (1) CM LED is on: RAM test has failed.
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.
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.
Software Installation IP Gateway Toolbox - Functions and Features a. The following configurations for the MDLC and TCP/IP can be edited: • • • • • • • • b.
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.
Software Installation Figure 4-2: Welcome Dialog screen 5. The Install Wizard displays the Software License Agreement (see Figure 4-3). Please read the text in this screen carefully, then click YES if you want to accept the license agreement and continue with the installation.
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).
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).
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.
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).
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.
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.
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.
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.
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.
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. Singleclick 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.
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.
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.
Site Configuration Information Tab This tab lists the version of the IP Gateway Toolbox version under which the configuration was created (e.g. V5.50), and the corresponding unit type (IP Gateway). Download Tab This tab is used to display information about the download of the site configuration to the IP Gateway. For more information, see the Download command below. (File menu) Upload Tab This tab is used to display information about the upload of the site configuration from the IP Gateway.
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.
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.
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).
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.
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.
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.
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.
Site Configuration Preview Current File The Preview Current File command displays the main settings of the current configuration file. The current file information is displayed in the OutPutBar Preview tab. Print The Print command prints the contents of the current configuration file to your standard system printer, as defined in Print Setup. To print the contents of the current configuration file to a postscript (.prn) or text file, check the Print to File box in the Print dialog.
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.
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.
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.
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.
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.
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.
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.
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.
Site Configuration Type of Modem → ↓ Modulation Full- Multi-Drop Duplex Half-Duplex Dial-Up Microwave Microwave Full-Duplex Half-Duplex 2W/4W QAM 2400 bps, V.22 bis, SYNC √ - - √ - Default Routing Ensures IP Gateway “mobility”.
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.
Site Configuration Port 4 Port 4 is also a plug-in port like Port 3, designed for various radio or line communications, for example: • • • • • Radio Line RS-232 Microwave Not used 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.
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.
Site Configuration Link Layer Parameters for TCP/IP Port 1 The following parameters relate to the MDLC Over IP technology. The range of possible is specified in < > symbols. The default is specified in square brackets (for example: [80]). You can change this default. Link name [LINE 1] All RTUs and IP Gateways use the same line. IP port number <1-65535> [2002] This number is common to all RTUs and IP Gateways connected to the link. This number identifies the MDLC.
Site Configuration TCP connect retries <5-20> [6] Maximum number of retries to create TCP connection Max waiting connections on socket <1-100> [5] Maximum number of waiting connections TCP RX window size <2-16> [2] Initial size in MSS for TCP receive window Max packets for row sockets <5-20> [10] Maximum number of incoming Ethernet packets ARP cache entries <8-200> [8] The number of ARP cache entries ARP cache lifetime (Min) <5-200> [15] The ARP cache time to live value in minutes ARP ask timeo
Site Configuration Printout format buffer size (Bytes) <256-1024> [524] 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.
Site Configuration TX queue size <2^3-2^9> [2^6]: This is the maximum number of MDLC frames that can be placed in the transmission queue before a transmission process starts. Number of ACK buffers <5-50> [40]: 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.
Site Configuration Max. number of addressable sites in a transmission <1-4> [4]: Maximum number of units the Data Link layer is capable of addressing in a single transmission. For “private conversation”, specify 1. TX to failed RTU <0:DISABLE 0-30> Min [5]: 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.
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.
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.
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.
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.
Site Configuration For Terminal with Server IP address Uses the IP address of the Terminal Server Port selected in the Terminal Server Ports screen. 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.
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.
Site Configuration Advanced Parameters This section reviews all of the ToolBox advanced configuration parameters. Throughout the ToolBox, advanced parameters are displayed according to context. For example, when you click the Advanced tab in the WorkSpaceBar in Site Configuration, ToolBox shows only those parameters that are applicable to the selected configuration. For details on opening the Advanced parameters windows, see WorkSpaceBar Advanced Tab.
Site Configuration Max. time waiting for TX-grant <100-900000> mSec [900000]: The period of time the system will wait for channel access, from the time it requests a channel. Max. TX-data duration <1000-60000> mSec [30000]: The maximum time during which data can be transmitted. After this period of time transmission stops even if it has not yet ended.
Site Configuration 67 European standard Hanging up an unused line by INITIATOR after <1-60> Sec [20]: A period of quiet time at the end of which the initiator of the conversation hangs up the phone. Hanging up an unused line by RESPONDER after <1-120> Sec [120]: A period of quiet time at the end of which the responder hangs up the phone.
Site Configuration ON RTS is always ON. This parameter is for old boards that do not react fast enough to RTS. Minimum number of flags between HDLC frames <0-15> [0]: Number of HDLC flags between frame transmissions. For old OEM equipment, specify a large value. Minimum TX time <0-2000> mSec [1000)]: Minimum transmission time. If the actual data transmission takes less than the specified value, the unit will continue to transmit until this time elapses.
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.
Site Configuration Number of TX retries <0-9> [2]: The number of times the Data Link layer retransmits a data frame for which ACK was not received. Number of TX retries upon BUSY ACK <0-9> [2]: 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). Interval between TX retries upon BUSY ACK <10-100> *100mSec...
Site Configuration Enable Network will send a control frame in order to check whether the link is still in “failed” status. The frame is issued if the link has been in “failed” status for the period of time specified in the previous parameter. Disable The link is considered to be back in order after the period of time specified in the previous parameter. 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.
Site Configuration Send broadcast reset after restart [YES]: Specify YES to broadcast to all units defined after Reset Load in order to synchronize at Transport Multiplex level. Restart declaration time out <5-200> Sec [30]: Time interval between two Restart control frames at Transport Multiplex level. Time out for URGE transmission after hole detection <0-3000> Sec. [15]: The period of time after which an “urge” frame will be issued if a gap formed at Transport Multiplex level.
Site Configuration MDLC Session Logical Channels Application layer Application manager work space <2000-6000> [4100]: 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.
Site Configuration Task suspension between transmitted frames <0-1000> mSec [50]: A delay that can be inserted between transmissions of frames in order to optimize CPU allocation to other processes (especially to processes that have a priority level which is lower than that of the application). Interval between TX retries <1-1000> Sec [15]: The interval of time that should elapse between two retries at Source/Destination level.
Site Configuration Data frames are the information stored in Txbuf in case of transmission, and in Rxbuf in case of reception. RTU-to-RTU Number of TX retries <0-20> [1]: 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). RTU-to-RTU Interval between TX retries <1-1000> Sec [60]: The interval of time that should elapse between retries.
Site Configuration NO There is no need for ACK from the central unit at RTU/Central Unit level. The system relies on Data Link ACK (at From/To level). YES The system requires that the central unit issues ACK to the RTU (RTU/Central Unit level), in addition to Data Link ACK. Event and Burst Password [Enable]: Enables the user to transmit events of bursts with a communication password. The value of this parameter must be identical for all RTUs and the central unit.
Site Configuration Diagnostics, Error Logger, Processes/Tables Monitor, Site Configuration and Downloader. If DEVICE=HP_F_TX is emptied frequently, increase the value of this parameter. ! WARNING Each buffer consumes about 250 bytes of RAM. Unformatted (Adapter) buffer size <10-1000> byte [50]: The size of the unformatted buffer that serves as asynchronous port. The overhead is ≈15 bytes, that is, the user can use only 35 bytes.
Site Configuration Timers Hookups Number of connected service-users with '10 mSec' device <10-100> [70]: 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).
Site Configuration Number of ’100 msec’ timers for ‘C’ applications <0-1000> [10] 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 Error logger buffer size <100-2000> byte [300]: 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.
Site Configuration System Values Main process duty cycle <0-100> [40]: 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.
Site Configuration 'C’ application parameters Number of user tasks for ‘C’ blocks <0-10> [0]: 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.
Site Configuration second entry will always contain the Erase callback function, and the third entry will always contain the Disable callback function. System Parameters The System parameters can be viewed and modified from the SCADA tab in the WorkspaceBar. General Gateway ID <1-255> [189]: The Gateway ID and the Startup Mode fields are essential to enable the SCADA computers to support redundant Gateway configurations. The Gateway ID should be a unique number in the range 1-255.
Site Configuration Communication Buffer Size <500-8192> [8192] 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 Overall Tasks <1-20> [6] Allows the definition of overall concurrent application tasks.
Network Configuration The Network Configuration program is used for defining the communication nodes (interconnection points between two or more links) in the network. The program defines the network’s structure; there is no need to define all RTUs, only the nodes in the network. The communication protocol uses these definitions for automatic routing of the packets through the network.
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).
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.
Network Configuration Icons The following is the list of the available command icons.
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.
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.
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, doubleclick 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.
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.
Network Configuration To specify that the link is authenticated, check the Authenticated box to the right of the Link ID. Next, specify the Site ID of the server which will perform synchronization for all the RTUs on the link. If the RTU is a server, you will specify its Site ID for all the authenticated links connected to it. If an RTU is a client, its Site ID cannot be entered into the Server ID field.
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.
Network Configuration Note: Force All Links can be used to define keys for all the links and then certain links can be modified in order to vary the authentication and limit the motility of the data. The authentication keys are not saved on the disk. When the Network Configuration utility is exited, the authentication keys are erased from the ToolBox. Yet it may be difficult to remember which authentication keys were downloaded to the Flash memory of the RTU.
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.
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.
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 Configuration window will be animated.
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.
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.
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.
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.
MDLC Links Configurator File Menu The commands in the File menu are designed mainly for manipulating files and exiting the application. File menu commands are: New Creates a new configuration, based on the default settings. The ToolBox gives the new configuration a temporary name (NEW1, NEW2, etc.), until you save it under a different name. Open Opens an existing link configuration file. After activating this command, the ToolBox displays the Open dialog box as shown below.
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.
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.
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 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.
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 nonresponding 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.
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.
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.
Site Table Click the appropriate button. Save The Save command stores the current Site table file on disk for future use. 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. If the file has been saved before, Toolbox just saves the file. Save As The Save As... command saves the current Site table information under a different file name.
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.
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 nonresponding 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.
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.
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.
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.
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.
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.
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.
SNMP Configurator General The SNMP Configurator program allows the definition of the SNMP and the Motorola SSC (System Support Center) parameters. Selecting the SSC option sets the Gateway MIB to support Motorola specific OmniLink and SmartZone systems. The SNMP Configurator Window The SNMP Gateway Configurator Window is used to set the SNMP configuration for the IP Gateway.
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.
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.
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.
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.
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.
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.
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.
Downloader Identify the IP Gateway to which the download will be performed, by default, the local RTU. To define a remote IP Gateway, specify the Site ID and Link ID. Next specify the various download parameters. The values for the parameters are changed by clicking in the cell and either typing or selecting from a choice list. Finally, select the files to be downloaded to the IP Gateway. Pick the desired file type and locate the desired file.
Downloader If for any reason you need to abort the download, press the Abort icon in the toolbar at the top of the window. After successful completion of the download, the following message appears: Download finished successfully. If a new system is to be downloaded, follow the process Downloading system software described below. Dialog box parameters and functions Download button Starts the process of downloading files.
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.
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.
Downloader desired session(s). A new entry of the appropriate type will be created (e.g. Site Configuration). Once a file type entry has been created for the session, the filename listed (e.g. C:\Itbox550\Config\conf1.cfg) can be edited or erased. If you decide not to download a file of that type, you can delete the file type entry, by right-clicking on the entry and selecting Delete or by single-clicking on the entry and pressing the Delete button on the keyboard.
Downloader stop the driver.) To change the Communication Port or Data Speed, select the parameter (left click) and select the value from the choice list. To specify a system software kernel file to be downloaded, select Open System File from the File menu. The utility will default to the C:\Itbox550\system directory. You can also select another directory. Select the desired .krl file and click on the Open button. The downloader session will automatically be renamed System Downloader Session.
Downloader user part of the Flash memory (Site/Network Configuration, phone book, etc.) must be erased and the contents downloaded again. Erasing Configuration Occasionally, it is necessary to erase the IP Gateway configuration and the contents of the user Flash memory, in order to restore the default configuration. To erase the existing configuration and the user part of the Flash , select Open System File from the File menu. The utility will default to the C:\Itbox550\system directory.
Downloader Erase Configuration command Edit menu, Download command Edit menu, Abort command File menu, Print command Help menu, About command File Menu The commands in the File menu are mainly designed to handle download settings files. New The New command (Downloader, File menu) opens a new download settings file (.ini). After activating this command, Downloader displays the New dialog box, as shown below.
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.
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.
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.
Downloader 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 system file. The ToolBox automatically adds the .krl extension.
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.
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.
Dial Up One of the most important features of the IP Gateway Toolbox is the capability to call a modem connected to any unit (RTU or FEP) in the system by means of a dialup modem (HAYES or compatible), and perform all the functions of the IP Gateway Toolbox remotely (from your office, home, or any other place).
Dial Up The FEP communication port baud rate should be equal to the modem baud rate. When connecting the IP Gateway Toolbox instead of the modem, the Toolbox baud rate should also be set up to be equal. The unit to which the modem is connected may be referred to as Local or by Site ID and Link ID. All other sites in the system should be referred to by their Site ID and Link ID. The modem connected to the site must be in Auto-Answer mode.
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.
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.
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.
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.
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.
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.
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.
Site Date & Time The Site Date & Time utility enables the user to update the date and time of any site and IP Gateway in the system and retrieve the date and time from any site or IP Gateway. The utility can communicate with more than one site in any given session, with multiple screens opened simultaneously. All the RTUs in the network can be synchronized to the same time as the host computer.
Site Date & Time Site Date & Time This parameter displays the current date and time at the site, and cannot be edited. While the tool is sending a command to the IP Gateway, the string “?? ?? ??” will be displayed in the Site Date & Time Field. Site The information below identifies the IP Gateway with which the Site Date & Time tool will communicate. Local When this box is checked, the Date & Time functions are performed on the locally connected IP Gateway.
Site Date & Time Icon Corresponding menu command Site Date & Time Help menu, About command 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.
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.
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.
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.
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.
Phone Book Open The Open command opens an existing phone book. After activating this command, Phone Book 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 .tel type files (phone book files). The config sub-directory is where ToolBox stores phone book files by default. Select the phone book file (see parameters below) and click OK to load it.
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.
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.
Phone Book Download The Download command sends the current phone book to any IP Gateway in the network. Before selecting this command, select Local if you are locally connected to the IP Gateway, or Remote (including Site ID and Link ID) if you are communicating with a remote unit. Internal modems support phone numbers up to 20 characters. If you download to an older version of the IP Gateway and the phone number is longer than 20 characters (the maximum for earlier versions), the number is truncated.
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.
Communication Setup This utility is designed to set the parameters to be used by the communication driver. If you want to change the communication setup, close all Toolbox tools, stop the communication driver using the Stop Communication Driver tool, and then make the modifications you want. The Ethernet port checkbox enables communication between an IP Gateway Toolbox and an IP Gateway unit over a TCP/IP interface.
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.
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.
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).
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.
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.
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.
Host Table Files of Type This box shows the type (extension) of the files currently displayed in the File Name list. The default should be .hst. If the desired file type “filter” is .hst, but it is not shown, open the dropdown list and select the .hst type. If the desired file type “filter” is .ntp, open the drop-down list and select the .ntp type. Alternatively, select All Files (*.*) to see all types. Save The Save command stores the current host/NTP file.
Host Table File Name Type the name of the host/NTP file. Toolbox automatically adds the .hst/.ntp 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 .hst/.ntp, open the drop-down list and select the .hst/.ntp type. Close The Close command closes the current host table/NTP file.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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).
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.
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.
SW Diagnostics & Loggers New The New command opens a new log file and prompts user to save it in the logger directory. The default name and directory of the log file in the dialog box can be changed in the dialog. You can also enter an existing log file name. The old logger information (from an earlier session) will be displayed and the new logger information will be appended to it. The New command and the corresponding icon are only available when a logger tool has been opened.
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.
SW Diagnostics & Loggers Select Central File This command allows you to select the central file by opening the following dialog box: If you do not select a central file, the variables are displayed by their Z, Y, and X coordinates. If you select the central file, their logical names are displayed. Close Central File Closes the currently open central file. Print The Print command prints the contents of the current log file to your standard system printer, as defined in Print Setup.
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.
SW Diagnostics & Loggers Error Log example The error logger window header is as follows: Error Logger 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.
SW Diagnostics & Loggers It shows a typical IP Gateway with two physical ports: Local Computer and Radio. The physical ports are supported by the Link and Physical layers. It also shows n Session Logical Channels used by various applications. In addition, three Minisession Logical Channels support event & burst transmission and broadcast reception.
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.
SW Diagnostics & Loggers Layer Name Device Name UART-Physical (Adapter) DILxA Notes For DIAL link COMxA for COMPUTER link RTUxA for RSlink link RADxA for RADIO link LINxA for LINE link via ext. modem TSxA for adapter over Terminal Server x – logical number Physical For DIAL link DILxP COMxP for COMPUTER link RTUxP for RSlink link RADxP for RADIO link LINxP for LINE link via ext.
SW Diagnostics & Loggers Link ID Link Adapter Physical Layer Rslink 12 RTUL RTU>A RTU>P Rslink 15 RTU?L RTU?A RTU?P Rslink 16 RTU@L RTU@A RTU@P Rslink 17-Rslink 19 RTUAL-RTUCL RTUAA-RTUCA RTUAP-RTUCP Rslink 20-Rslink 99 S020L-S099L S020A-S099A S020P-S099P Rslink 100-Rslink 200 S100L-S200L S100A-S200A S100P-S200P Radio 1-Radio 9 RAD1L-RAD9L RAD1A-RAD9A RAD1P-RAD9P Radio 10-Radio 99 R010L-R099L R010A-R099A R01
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) Jun 30 14:55:26 Site: LOCAL Device: COM1L # of Transmitted Frames : 17 # of Re-transmitted Frames : 0 # of Received Frames : 35 # of Received Frames (With Error): 0 Level: 11 The # of Transmitted Frames does not include retransmission and acknowledgment frames.
SW Diagnostics & Loggers REQMNG Requirements Manager device The meaningful levels are 0, 1. Diagnostic levels of 2, 3, 4 are for internal use only.
SW Diagnostics & Loggers Example of Level 1 Diagnostics: Oct 31 09:45:36 name myclnt another Site: 10000 free 0 0 1 1 id 1 2 255 255 Link: Rslink1 tx 2 3 255 255 burst 2 3 255 255 Device: REQMNG Level: 1 error 0 0 0 0 Interesting fields: The name column indicates the names of the connected clients, (if a row starts with 1, the first - name field is empty).
SW Diagnostics & Loggers Time to wait after ping: Tue Dec 21 09:01:43 1999 1000 SITE: Local Health Check Diagnostics - Rtus ------------------------------SiteId LinkId Status ------ ------ -----100 101 102 103 104 105 106 107 108 109 51 51 51 51 51 51 51 51 51 51 alive alive alive alive alive alive alive alive alive alive 100 101 102 103 104 105 106 107 108 109 alive alive alive alive alive alive alive alive alive alive 1 1 1 1 1 1 0 1 1 1 Tue Dec 21 09:02:01 1999 100 101 102 103 104 105 106 107
SW Diagnostics & Loggers STBLA Sites Table Device Tue Dec 21 09:02:44 1999 SITE: Local DEVICE: STBLA Version of Site-Table Downloader : The Target Unit (1-VRM-100, 2-Gateway): Size of Downloaded Site Table : Size of Learning Site Table : Tue Dec 21 09:03:19 1999 LEVEL: 0 400 4 101 100 SITE: Local DEVICE: STBLA LEVEL: 1 SITE: Local DEVICE: STBLA LEVEL: 2 Learning Site-Table: Site-ID ======== 0 0 0 0 Link-ID ======= 0 0 0 0 Tue Dec 21 09:03:25 1999 Downloaded Site-Table: Site-ID ======== 65533
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.
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.
Advanced Features The IP Gateway system includes several advanced features which are described below. These often require special setup and configuration procedures.
HealthCheck Mechanism General 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 Ping Pong 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.
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).
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.
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.
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.
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.
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.
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.
Adding Terminal Server Ports MOSCAD 8 Pin Connector RJ 45 Connector EQUINOX 8 Pin Connector RJ 45 connector 1 (TXD) 6 (RxD) 2 (RXD) 4 (TxD) 3 (CTS) 7 (DTR) 4 (GND) 3 (GND) 5 (CD) 8 (RTS) 6 (RTS) 2 (DCD) (*) 7 (12V) N.C 8 (DTR) 1 (CTS) Configuration General notes: • The commands to be entered were given under the assumption that the ELS16 is performing a ‘self boot’. In case of a boot server, please refer to EQUINOX documentation.
Adding Terminal Server Ports CHANGE SERVER SUBNET MASK m.m.m.m CHANGE SERVER IP a.a.a.a CHANGE SERVER GATEWAY IP a.a.a.a NETWORK a.a.
Adding Terminal Server Ports CHANGE PORT N TELNET OCRLF ENABLED CHANGE PORT N TELNET VERBOSE DIS CHANGE PORT N TELNET BINARY WILL BINARY DO CHANGE PORT N TELNET ECHO WONT ECHO DONT CHANGE PORT N TELNET SUPPRESS WILL SUPPRESS DO INIT At this point, the ELS16 will reboot itself. The ‘self boot’ process will take about 15 seconds.
Adding Terminal Server Ports DEFINE PORT 3-16 TELNET EL NONE DEFINE PORT 3-16 TELNET GA NONE DEFINE PORT 3-16 TELNET IP NONE DEFINE PORT 3-16 TELNET SYN NONE DEFINE PORT 3-16 TELNET ICRLF ENABLED DEFINE PORT 3-16 TELNET OCRLF ENABLED DEFINE PORT 3-16 TELNET VERBOSE DIS DEFINE PORT 3-16 TELNET BINARY WILL BINARY DO DEFINE PORT 3-16 TELNET ECHO WONT ECHO DONT DEFINE PORT 3-16 TELNET SUPPRESS WILL SUPPRESS DO DEFINE SERVICE LOCAL PORT3 3003 PORT 3 ENABLED CONNECTIONS ENABLED TELNET ENABLED DEFINE SERVICE LOCA
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.
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.
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.
IP Gateway Web Operation General 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. Equipment technicians can verify functionality of their equipment and to receive information about the status of similar or related equipment in other sites.
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.
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.
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.
IP Gateway Web Operation The Tools Downloading System Software using the Web Server The Web server enables the user to upgrade system firmware remotely, over the web. Before upgrading the IP Gateway firmware, verify that the new firmware version is not higher than the IP Gateway Site Configuration version. (If the configuration version is unknown, upload it using the IP Gateway Site Configuration utility.
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.
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.
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.
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.
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.
IP Gateway Telnet Operation Telnet Command Summary Command Format adduser Description Adds a user to the list of valid IP Gateway users. Enter the superuser password at the prompt. If the password is valid, the IP Gateway prompts for the initial password for the new user. At the prompt, confirm the initial password for the new user. The new user name and password are saved in the IP Gateway.
IP Gateway Telnet Operation Command Format Description Site ID of EMU = n1 Link ID of EMU = n2 Port ID of EMU = n3 Port mux # = n3 | N/A where n1, n2, n3, n4 are numbers. whoami Displays the login name used in the current telnet session. users Displays the list of valid IP Gateway users. passwd Changes the password of the current telnet user. 1. At the prompt, enter the current password. 2. Enter the new password. 3. Confirm the new password.
IP Gateway Telnet Operation Command Format parms all Description Displays or changes the IP Gateway Telnet application configurable parameters. parms Lists the Telnet and terminal emulation configuration parameters one by one. CR on input shows the next parameter. Any other input resets (changes) the parameter.
IP Gateway Telnet Operation Example Output The chart below depicts a list of users and sessions which might be displayed by the who command.
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 FLN
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).
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).
APPENDIX A: RS232 Adapter Cables Optional Function Description 15-pin Male SPKR+ SPKR+ 6 SPKR- SPKR- 7 SWB+ Shrink Tube (Ext. +12V DC) 4 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.
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.
APPENDIX B: Remote ToolBox Modem Setup Hayes ACCURA 144 + FAX 144 Modem Type Model Version Hayes ACCURA 144 + FAX 144 External 5611US 2.
APPENDIX B: Remote ToolBox Modem Setup Command Summary (* indicates a change from the default) * * B0 E1 * L1 M1 N0 * Q0 T V1 W0 X4 Y0 &C1 &D0 * &G0 &J0 &K0 &Q# &R1 &S0 &T5 &X0 &Y0 ITU-T answer sequence Enable local echo (Must be set to E0 when modem is connected directly to the RTU as opposed to the PC.) Low volume Speaker ON until CONNECT Automode is disabled. The handshake will occur based on the value of S37.
APPENDIX B: Remote ToolBox Modem Setup S-Registers (* indicates a change from default) * * S00=001 S037=009 sets the number of rings before modem answers 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.
APPENDIX B: Remote ToolBox Modem Setup Motorola OnlineSURFR 28.8 Modem Type Model Date Code: Motorola OnlineSURFR External MODEMSURFR 28.
APPENDIX B: Remote ToolBox Modem Setup Command Summary (* indicates a change from the default) * * 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 ITU-T answer sequence Enable local echo (Must be set to E0 when modem is connected directly to the RTU as opposed to the PC.
APPENDIX B: Remote ToolBox Modem Setup S-Registers (* indicates a change from default) * * S00=001 S037=009 sets the number of rings before modem answers 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.
APPENDIX B: Remote ToolBox Modem Setup Motorola OnlineSURFR 33.6 Modem Type Model Date Code: Motorola OnlineSURFR External MODEMSURFR 33.
APPENDIX B: Remote ToolBox Modem Setup Motorola OnlineSURFR 56K Modem Type Model Date Code: Serial No.
APPENDIX B: Remote ToolBox Modem Setup UDS V.3225 Modem Type Model Version UDS V.3225 External V.
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.
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 Modem Type Model Version USRobotics Sportster 14400 Fax External Configuration (9600 Baud) ati4 USRobotics Sportster 14400 Fax Settings...
APPENDIX B: Remote ToolBox Modem Setup Command Summary (* indicates a change from the default) * * * * * * * B0 E1 F1 M1 Q0 V1 X4 Y0 &A1 &B1 &C1 &D0 &G0 &H0 &I0 &K0 &M0 &N6 &P0 &R1 &S0 &T5 &Y1 ITU-T answer sequence Enable local echo (Must be set to E0 when modem is connected directly to the RTU as opposed to the PC.
APPENDIX B: Remote ToolBox Modem Setup S-Registers (* indicates a change from default) * * S00=001 S037=009 sets the number of rings before modem answers 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.
APPENDIX B: Remote ToolBox Modem Setup USRobotics Sportster 28800 Fax Modem Type Model Version USRobotics Sportster 28800 Fax External 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.
APPENDIX B: Remote ToolBox Modem Setup Command Summary (* indicates a change from the default) * * * * * * * B0 E1 F1 M1 Q0 V1 X4 Y0 &A1 &B1 &C1 &D0 &G0 &H0 &I0 &K0 &M0 &N6 &P0 &R1 &S0 &T5 &Y1 ITU-T answer sequence Enable local echo (Must be set to E0 when modem is connected directly to the RTU as opposed to the PC.
APPENDIX B: Remote ToolBox Modem Setup S-Registers (* indicates a change from default) * * S00=001 S037=009 sets the number of rings before modem answers 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.
APPENDIX B: Remote ToolBox Modem Setup USRobotics Sportster 56K Fax Modem Type Model Version USRobotics Sportster 56K Fax External 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.
APPENDIX B: Remote ToolBox Modem Setup Intel SatisFAXtion Modem/400e Modem Type Model Version Intel SatisFAXtion Modem/400e External PCFM6501 UNKNOWN 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
APPENDIX B: Remote ToolBox Modem Setup Command Summary (* indicates a change from the default) * * B0 E1 * L1 M1 N0 * Q0 T V1 W0 X4 Y0 &C1 &D0 * &G0 &J0 &K0 &Q# &R1 &S0 &T5 &X0 &Y0 ITU-T answer sequence Enable local echo (Must be set to E0 when modem is connected directly to the RTU as opposed to the PC.) Low volume Speaker ON until CONNECT Automode is disabled. The handshake will occur based on the value of S37.
APPENDIX B: Remote ToolBox Modem Setup S-Registers (* indicates a change from default) * * S00=001 S037=009 sets the number of rings before modem answers 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.
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: Term Explanation Device A MOSCAD/MOSCAD-L software module.
Software Diagnostics Output ## 17 LEVEL = 1 Minisession Channels -------------------Minisession Key Application ID ------------------------------- 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.
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.
Software Diagnostics Output ## 32 LEVEL = 0 # of buffers in heap # of buffers left in heap The minimum # of buffers left in heap from last diagnostic # of times the heap was empty since last diagnostic Size of one buffer in bytes During init flag Bad heap flag Unit time for freeing by force Pointer to start chain Pointer to current chain Pointer to end chain : %% 1 : %% 2 : %% 3 : : : : : : : : %% %% %% %% %% %% %% %% 4 5 6 7 8 9 10 11 1. Number of buffers in heap instance 2.
Software Diagnostics Output ADAPTER ## 48 DEVICE = COM1A,RTU1A, LIN1A,… LEVEL = 0 Physical device key Physical PIN’s table Heap key, to be used by the receive function Heap key, to be used by the transmit function Mask address (ignore addresses or not) System address Specific logical address (site id) Extra address 1 Extra address 2 Mode of operation TimeAuth device key (HEX) TimeAuth handle Authentication stamp offset : : : : : : : : : : : : : %% %% %% %% %% %% %% %% %% %% %% %% %% 1 2 3 4 5 6 7 8 9
Software Diagnostics Output ## 49 LEVEL = 10,11 # of transmitted frames # of transmission fails # of received frames # of received frames (with error) Mask of errors (receive) Number of non-properly authenticated SYNC frames : : : : : : %% %% %% %% %% %% 1 2 3 4 5 6 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.
Software Diagnostics Output Current no. of channel busy retries Sequence of master session No. of frames in burst No.
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.
Software Diagnostics Output ## 66 # # # # # # # # of of of of of of of of LEVEL = 10/11 transmitted frames received frames re-transmitted frames received frames (with error) frames in Tx queue frames in Rx queue frames in Tx queue (held by link layer) frames in Tx queue (held by physical layer) : : : : : : : : %% 1 %% 2 %% 3 %% %% %% %% %% 1. The # of Transmitted Frames (does not include retransmission and acknowledgment frames.) 2. The # of Received Frames (includes only correct frames.) 3.
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.
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.
Software Diagnostics Output ## 113 LEVEL = 1 Address 0 to transmit in same snapshot Address 1 to transmit in same snapshot Address 2 to transmit in same snapshot Address 3 to transmit in same snapshot Network device key Physical device key Physical pin’s table Last reported station in fail Port fail flag ‘one to one’ flag Full duplex flag # of frames in Tx queue # of frames in ‘wait for ack’ queue # of frames in ‘busy & setcall’ queue # of frames in ‘busy & finish’ queue ‘private conversation’ flag : :
Software Diagnostics Output 2. 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). 3. The # of Received Frames includes only correct frames.
Software Diagnostics Output NETWORK (NETWRK) ## 180 LEVEL = 0 # of links actually connected to network layer Transport interface key Formatted buffers heap key 1 Formatted buffers heap key 2 Network stock key Default central link key Default central via link-id Default central thru site-id The unit site-id The default central flag The network transparent flag : : : : : : : : : : : %% %% %% %% %% %% %% %% %% %% %% 1 2 3 3 4 5 6 7 8 9 10 1.
Software Diagnostics Output MINISESSION ## 200 (EVNT , STCL) EVNT Event & Burst device STCL Broadcast reception device LEVEL = 0 Application id No. of boxes in device No.
Software Diagnostics Output 17. The next index of answer frames to be issued. ## 201 Boxes_nr Boxes in Boxes in Boxes in Boxes in Boxes in Boxes in Boxes in Boxes in LEVEL = 1 : : : : : : : : : free queue wait_for_outside_answr queue outside_answrs queue requests_from_applic queue wait_for_applic_answr queue originate queue setcall queue answer queue %% %% %% %% %% %% %% %% %% 1 2 3 4 5 6 7 8 9 1. Total number of boxes to be handled by this instance. Each box handles one MDLC frame. 2.
Software Diagnostics Output 9. Next box index. 10. The internal queue ID. ## 203 LEVEL = 3 “outside answers queue” ------------------------------buf site port link retries ret_time indx p_indx _indx q_nr --------------------------------------------------------------------%% %% %% %% %% %% %% %% %% %% 1 2 3 4 5 6 7 8 9 10 See #202 above.
Software Diagnostics Output ## 208 LEVEL = 8 “answers queue” -------------------buf site port link retries ret_time indx p_indx _indx q_nr --------------------------------------------------------------------%% %% %% %% %% %% %% %% %% %% 1 2 3 4 5 6 7 8 9 10 See #202 above.
Software Diagnostics Output HDLC (RAD1P, RAD2P,...
Software Diagnostics Output 18. The number of empty frames ready to be received. 19. The number of frames received. 20. The number of frames transmitted. 21. The number of empty frames directed to transmission. ## 261 LEVEL = 1 HDLC hardware control and status :Internal software data (key) (DATA) Internal hardware registers (IREG) Internal hardware parameters (IRAM) Scc configuration register (SCON) Scc mode register (SCM) Scc data sync.
Software Diagnostics Output ## 262 LEVEL = 2 HDLC hardware data buffers status :Internal software data (key) (DATA) : Internal hardware registers (IREG) : Internal hardware parameters (IRAM) : Receive buffer descriptor 0 (RXBD0) : Receive buffer descriptor 1 (RXBD1) : Receive buffer descriptor 2 (RXBD2) : Receive buffer descriptor 3 (RXBD3) : Receive buffer descriptor 4 (RXBD4) : Receive buffer descriptor 5 (RXBD5) : Receive buffer descriptor 6 (RXBD6) : Receive buffer descriptor 7 (RXBD7) : Transmit buf
Software Diagnostics Output 14. Address of frame for transmission in descriptor 2. 15. Address of frame for transmission in descriptor 3. 16. Address of frame for transmission in descriptor 4. 17. Address of frame for transmission in descriptor 5. 18. Address of frame for transmission in descriptor 6. 19. Address of frame for transmission in descriptor 7. 20. Rx and Tx function code. 21. Maximum received frame length. 22. The reception status of the last received frame. 23.
Software Diagnostics Output ## 263 LEVEL = 3 HDLC software control and status :Internal software data (key) (DATA) Internal hardware registers (IREG) Internal hardware parameters (IRAM) Current mode parameters (MODE_BACKUP) Current rate parameters (RATE_BACKUP) Current sync parameters (SYNC_BACKUP) Address mask parameters (MASK_BACKUP) Address data parameters (ADRS_BACKUP) Current channel name (CHAN_BACKUP) Current channel data (CHAN_DATA) Current channel code (CHAN_CODE) Current heap name (HEAP_BACKUP)
Software Diagnostics Output 14. The heap pin table. 15. The Port number. 16. Semaphore of the reception function. 17. Semaphore of the transmission function. 18. Offset in Rx descriptors to the next free descriptor. 19. Offset in Tx descriptors to the next free descriptor. 20. Offset for Rx descriptors for receiving frame. 21. Offset for Tx descriptors for transmitting frame. 22. MTE signal of conditions that were met. 23. Whether the frame is formatted or unformatted. 24. Device semaphore. 25. Not in use.
Software Diagnostics Output ## 270 LEVEL = 10/11 HDLC hardware/software last status :Discard frame counter CRC error counter Abort sequence counter Non matching address counter Frame retransmit counter (DISFC) (CRCEC) (ABTSC) (NMARK) (RETRC) : : : : : %% %% %% %% %% 1 2 3 4 5 1. The number of discarded frames. 2. The number of CRC-error frames. 3. The number of abort-sequence frames. 4. The number of nonmatching address frames. 5. The number of retransmitted frames.
Software Diagnostics Output UART ## 280 UART hardware/software last status :Internal software data (key) Internal hardware registers Internal hardware parameters Current channel port Reception data lock Transmission data lock Reception data header Reception data tail Transmission data header Transmission data tail Communication signals Communication buffers Idle characters counter Parity error counter Framing error counter Noise error counter Break error counter Current reception empty buffer Current recep
Software Diagnostics Output 16. The number of times the noise error occurred during the reception of a single byte. 17. The number of times a break signal (end of reception) was received at the port. 18. The number of empty frames ready to be received. 19. The number of frames received. 20. The number of frames transmitted. 21. The number of empty frames directed to transmission.
Software Diagnostics Output 12. Break register. 13. The number of times the parity error occurred during the reception of a single byte. 14. The number of times the framing error occurred during the reception of a single byte. 15. The number of times the noise error occurred during the reception of a single byte. 16. The number of times a break signal (end of reception) was received at the port. 17. Not in use. 18. Control character register. 19. The characters that are used to close a frame.
Software Diagnostics Output 5. Address of frame in descriptor RX 1. 6. Address of frame in descriptor RX 2. 7. Address of frame in descriptor RX 3. 8. Address of frame in descriptor RX 4. 9. Address of frame in descriptor RX 5. 10. Address of frame in descriptor RX 6. 11. Address of frame in descriptor RX 7. 12. Address of frame for transmission in descriptor 0. 13. Address of frame for transmission in descriptor 1. 14. Address of frame for transmission in descriptor 2. 15.
Software Diagnostics Output ## 283 UART software control and status :Internal software data (key) Internal hardware registers Internal hardware parameters Current mode parameters Current rate parameters Current sync parameters Address mask parameters Address data parameters Current channel name Current channel data Current channel code Current heap name Current heap name Current heap data Current channel port Reception data lock Transmission data lock Reception next free Transmission next free Reception da
Software Diagnostics Output 14. The heap pin table. 15. The Port number. 16. Semaphore of the reception function. 17. Semaphore of the transmission function. 18. Offset in Rx descriptors to the next free descriptor. 19. Offset in Tx descriptors to the next free descriptor. 20. Offset for Rx descriptors for receiving frame. 21. Offset for Tx descriptors for transmitting frame. 22. MTE signal of conditions that were met. 23. Whether the frame is formatted or unformatted. 24. Device semaphore. 25. Not in use.
Software Diagnostics Output ## 285 UART hardware/software last status :Internal software data (key) (DATA) : Internal hardware registers (IREG) : Internal hardware parameters (IRAM) : Current channel port (UART_PORT) : Reception data lock (RXBD_LOCK) : Transmission data lock (TXBD_LOCK) : Reception data header (RXBD_HEAD) : Reception data tail (RXBD_TAIL) : Transmission data header (TXBD_HEAD) : Transmission data tail (TXBD_TAIL) : Communication signals (UART_SIGNAL): Communication buffers (UART_TYPE) : Id
Software Diagnostics Output 18. The number of empty frames ready to be received. 19. The number of frames received. 20. The number of frames transmitted. 21. The number of empty frames directed to transmission. ## 286 UART hardware control and status :Internal software data (key) (DATA) Internal hardware registers (IREG) Internal hardware parameters (IRAM) Scc configuration register (SCON) Scc mode register (SCM) Scc data sync.
Software Diagnostics Output 13. The actual counter that counts the number of idles since the last character was received. For example, the time that a character takes to arrive (corresponds to idle) at 9600 baud is 1 msec. 14. Break register. 15. The number of times the parity error occurred during the reception of a single byte. 16. The number of times the framing error occurred during the reception of a single byte. 17. The number of times the noise error occurred during the reception of a single byte.
Software Diagnostics Output 3. H-W parameters address. 4. Address of frame in descriptor RX 0. 5. Address of frame in descriptor RX 1. 6. Address of frame in descriptor RX 2. 7. Address of frame in descriptor RX 3. 8. Address of frame in descriptor RX 4. 9. Address of frame in descriptor RX 5. 10. Address of frame in descriptor RX 6. 11. Address of frame in descriptor RX 7. 12. Address of frame for transmission in descriptor 0. 13. Address of frame for transmission in descriptor 1. 14.
Software Diagnostics Output ## 288 UART software control and status :Internal software data (key) (DATA) : Internal hardware registers (IREG) : Internal hardware parameters (IRAM) : Current mode parameters (MODE_BACKUP): Current rate parameters (RATE_BACKUP): Current sync parameters (SYNC_BACKUP): Address mask parameters (MASK_BACKUP): Address data parameters (ADRS_BACKUP): Current heap name (HEAP_KEY) : Current channel port (DART_PORT) : Reception data lock (RXBD_LOCK) : Transmission data lock (TXBD_LOCK)
Software Diagnostics Output 15. Offset for Rx descriptors for receiving frame. 16. Offset for Tx descriptors for transmitting frame. 17. MTE signal of conditions that were met. 18. Whether the frame is formatted or unformatted. 19. Internal variable that represents the device status. 20. Not in use. 21. Coded time stamp of last received frame (in ticks). 22. Current counter of noise. 23. Current counter of quiet. 24.
Software Diagnostics Output 4. The number of times a break signal (end of reception) was received at the port.
Software Diagnostics Output ## 301 Radio hardware control and status :Internal software data (key) Internal hardware registers Internal hardware parameters Scc configuration register Scc mode register Scc data sync.
Software Diagnostics Output Transmit buffer descriptor 5 Transmit buffer descriptor 6 Transmit buffer descriptor 7 Rxd/Txd function code Maximum receive buffer length Current receive buffer status Current receive buffer offset Current receive data pointer Current receive byte counter Current receive temp memory Current transmit buffer status Current transmit buffer offset Current transmit data pointer Current transmit byte counter Current transmit temp memory (TXBD5) : (TXBD6) : (TXBD7) : (R/TFCR): (MRBLR
Software Diagnostics Output 22. The reception status of the last received frame. 23. The offset value in the descriptors of the last received frame. 24. Internal variable of 68302. 25. The status of the last transmitted frame. 26. The offset value in the descriptors of the last transmitted frame. 27. Internal variable of 68302.
Software Diagnostics Output 11. Whether FSK, DPSK or FSK. 12. The address to which this site will respond through this port. 13. Actual channel access timers. 14. Preset timers for fields defined in the advanced parameters of Port 3.
Software Diagnostics Output 14. Number of busy Tx descriptors. 15. Number of empty Tx descriptors. ## 321 Trunk radio hardware control and status :Internal software data (key) Internal hardware registers Internal hardware parameters Scc configuration register Scc mode register Scc data sync.
Software Diagnostics Output Transmit buffer descriptor 0 Transmit buffer descriptor 1 Transmit buffer descriptor 2 Transmit buffer descriptor 3 Transmit buffer descriptor 4 Transmit buffer descriptor 5 Transmit buffer descriptor 6 Transmit buffer descriptor 7 Rxd/Txd function code Maximum receive buffer length Current receive buffer status Current receive buffer offset Current receive data pointer Current receive byte counter Current receive temp memory Current transmit buffer status Current transmit buffe
Software Diagnostics Output 23. The offset value in the descriptors of the last received frame. 24. Internal variable of 68302. 25. The status of the last transmitted frame. 26. The offset value in the descriptors of the last transmitted frame. 27. Internal variable of 68302.
Software Diagnostics Output 6. Not relevant. 7. Port number. 8. Configuration mode. 9. Channel access semaphore. 10. MTE signal on events that took place. 11. Whether FSK, DPSK or FSK. 12. The address to which this site will respond through this port. 13. The ACK transmission slot. 14. Random value to obtain a channel during a retry. 15. Actual channel access timers. 16. Preset timers for fields defined in the advanced parameters of Port 3.
Software Diagnostics Output 7. MTE signal on events that took place. 8. Whether FSK, DPSK or FSK. 9. Defines the functionality of port B in 68. 10. Determines whether the pin is for input or output. 11. Defines the value of the pin (previous parameter). 12. Number of empty Rx descriptors. 13. Number of busy Rx descriptors. 14. Number of busy Tx descriptors. 15. Number of empty Tx descriptors.
Software Diagnostics Output ## 342 Rs232 hardware data buffers status :Internal software data (key) Internal hardware registers Internal hardware parameters Receive buffer descriptor 0 Receive buffer descriptor 1 Receive buffer descriptor 2 Receive buffer descriptor 3 Receive buffer descriptor 4 Receive buffer descriptor 5 Receive buffer descriptor 6 Receive buffer descriptor 7 Transmit buffer descriptor 0 Transmit buffer descriptor 1 Transmit buffer descriptor 2 Transmit buffer descriptor 3 Transmit buffe
Software Diagnostics Output 14. Address of frame for transmission in descriptor 2. 15. Address of frame for transmission in descriptor 3. 16. Address of frame for transmission in descriptor 4. 17. Address of frame for transmission in descriptor 5. 18. Address of frame for transmission in descriptor 6. 19. Address of frame for transmission in descriptor 7. 20. Rx and Tx function code. 21. Maximum received frame length. 22. The reception status of the last received frame. 23.
Software Diagnostics Output 3. H-W parameters address. 4. Working mode of the channel (synchronous, asynchronous, DTE, DCE). 5. Communication baud rate. 6. Not relevant. 7. Port number. 8. Configuration mode. 9. Channel access semaphore. 10. MTE signal on events that took place. 11. Whether FSK, DPSK or FSK. 12. The address to which this site will respond through this port. 13. Actual channel access timers. 14. Preset timers for fields defined in the advanced parameters of Port 3.
Software Diagnostics Output 6. Channel access semaphore. 7. MTE signal on events that took place. 8. Whether FSK, DPSK or FSK. 9. Defines the functionality of port B in 68. 10. Determines whether the pin is for input or output. 11. Defines the value of the pin (previous parameter). 12. Number of empty Rx descriptors. 13. Number of busy Rx descriptors. 14. Number of busy Tx descriptors. 15. Number of empty Tx descriptors.
Software Diagnostics Output 10. Defines the functionality of port B in 68. 11. Determines whether the pin is for input or output. 12. Defines the value of the pin (previous parameter).
Software Diagnostics Output 10. Address of frame in descriptor RX 6. 11. Address of frame in descriptor RX 7. 12. Address of frame for transmission in descriptor 0. 13. Address of frame for transmission in descriptor 1. 14. Address of frame for transmission in descriptor 2. 15. Address of frame for transmission in descriptor 3. 16. Address of frame for transmission in descriptor 4. 17. Address of frame for transmission in descriptor 5. 18. Address of frame for transmission in descriptor 6. 19.
Software Diagnostics Output ## 363 Modem software control and status :Internal software data (key) (DATA) Internal hardware registers (IREG) Internal hardware parameters (IRAM) Current mode parameters (MODE_BACKUP) Current Current Current Channel Channel Channel Channel Channel Channel Channel rate parameters sync parameters channel port status mode driver lock signals access type driver type addresses status Channel preset/timers : : : : : (RATE_BACKUP) : (SYNC_BACKUP) : (CHAN_PORT) : (CHAN_MODE) : (CH
Software Diagnostics Output TIMERS (10__MS , 100_MS , 1__SEC , 1__MIN) ## 380 LEVEL = 0 # of entries in the service table (actual) Maximum # of entries in the service table # of time units passed from last task running The limit # of time units passed without activating task : : : : %% %% %% %% 1 2 3 4 1. The number of timer services (in the specific Instance) currently in use. 2. The maximum number of timer services that can be used. 3.
Software Diagnostics Output 8. Whether FSK, DPSK or FSK. 9. Defines the functionality of port B in 68. 10. Determines whether the pin is for input or output. 11. Defines the value of the pin (previous parameter). 12. Number of empty Rx descriptors. 13. Number of busy Rx descriptors. 14. Number of busy Tx descriptors. 15. Number of empty Tx descriptors.
Software Diagnostics Output ## 522 Rs485 hardware data buffers status :Internal software data (key) Internal hardware registers Internal hardware parameters Receive buffer descriptor 0 Receive buffer descriptor 1 Receive buffer descriptor 2 Receive buffer descriptor 3 Receive buffer descriptor 4 Receive buffer descriptor 5 Receive buffer descriptor 6 Receive buffer descriptor 7 Transmit buffer descriptor 0 Transmit buffer descriptor 1 Transmit buffer descriptor 2 Transmit buffer descriptor 3 Transmit buffe
Software Diagnostics Output 14. Address of frame for transmission in descriptor 2. 15. Address of frame for transmission in descriptor 3. 16. Address of frame for transmission in descriptor 4. 17. Address of frame for transmission in descriptor 5. 18. Address of frame for transmission in descriptor 6. 19. Address of frame for transmission in descriptor 7. 20. Rx and Tx function code. 21. Maximum received frame length. 22. The reception status of the last received frame. 23.
Software Diagnostics Output 2. H-W registers address. 3. H-W parameters address. 4. Working mode of the channel (synchronous, asynchronous, DTE, DCE). 5. Communication baud rate. 6. Not relevant. 7. Port number. 8. Configuration mode. 9. Channel access semaphore. 10. MTE signal on events that took place. 11. Whether FSK, DPSK or FSK. 12. The address to which this site will respond through this port. 13. Actual channel access timers. 14. Preset timers for fields defined in the advanced parameters of Port 3.
Software Diagnostics Output LEVEL = 2 Disabled blocks for type- %%1 Block- 0 : %%2 Block- 1 : %%2 1. The block type (block id). For the FLASHDB device (application flash), there can be up to 50 blocks . For FLSEXT1 (logging flash), the user can define up to five blocks (0-4). 2. The status of the blocks in the application or logging flash can be one of: 0 (block enabled) or 1 (block disabled). ## 601 LEVEL = 1, 20 , 21 , ...
Software Diagnostics Output ## 620 Low byte Message ‘send message’ ‘comm established’ flag ‘message exist’ flag Warmup not done Dial number Physical key Mini - session key Unformatted heap key : : : : : : : : : : %% %% %% %% %% %% %% %% %% %% : : : : : : %% %% %% %% %% %% LDIALER (DIL2D , DIL 3D) ## 640 LEVEL = 0 Physical device key Physical pin’s table Async dial physical device key Async dial physical pin’s table Interval between phone call retries (sec) # of phone call retries # of times to call
Software Diagnostics Output 2. Time counter until disconnection. 3. Last or current dialed number. 4. Previous number dialed. 5. Last site ID connected. 6. Whether initiator or responder. (ML_DL) ## 645 LEVEL = 0 # of dial links (preset) Network key Pointer to links table : %% 1 : %% 2 : %% 3 1. Number of dialing channels. 2. Network layer device key. 3.
Software Diagnostics Output ## 646 LEVEL = 1 # of dial links (current) Last failed link used Port status partner link_key ldialer_key -----------------------------------------------------3 4 5 6 7 : %% 1 : %% 2 1. Number of dialing channels. 2. The last failed channel used. 3. The dialing line. 4. The call status. 5. The initiator site ID. 6. The Link layer device key. 7. The Ldialer layer device key. TOPLC (PLC1L, PLC2L, PLC3L) ## 660 LEVEL = 0 Port name Connection to Appl. code area Appl.
Software Diagnostics Output 9. Maximum amount of time to announce no response. 10. Number of idles to announce end of RX. 11. Number of errors. 12. Downloadable module version. 13. Downloadable module revision. 14. Name of the downloadable module. 15. Diagnostic string given by the downloadable module.
Software Diagnostics Output BURST - SEQ ## 710 application identity maximum buffers in ready queue Number of buffers in list : %% 1 : %% 2 : %% 3 1. Application ID number. 2. Maximum number of frames allowed to be accumulated. 3. Number of frames currently waiting in the queue. PHONE BOOK LEVEL = 0 PHNBK ## 940 Start at flash Number of entries : %% 1 : %% 2 1. The phone book address in the flash. 2. The number of entries in the phone book.
Software Diagnostics Output TIMER EVENT ## 960 Timers max. value (in 10msc units) Max. number of events / timers in buffer Current number of events / timers in buffer # of heap_aloc_buf failed : : : : %% %% %% %% 1 2 3 4 1. The maximum number of timers that can be set by SetTmr to a specific event. 2. The maximum number of events and timers that can be managed simultaneously by the timer event device. (They are managed by the heap.) 3. The number of events and timers currently in the heap. 4.
Software Diagnostics Output STBLA (SITE TABLE) ## 1022 LEVEL = 2 Downloaded Site-Table: Site-ID Link-ID Retries ======== ======= ======= %1 %2 %3 Timeout ======= %4 %5 %6 %7 1. The Site ID. 2. The number of attempts to be made to communicate with a non-responding site. (1-255) 3. The time (in seconds) to wait between communication retries. (1-255) 4. The Link ID of the link through which the site is connected to the network. (Primary) 5.
Software Diagnostics Output ## 1131 Chunk address ------------1 Chunk size ---------2 Is free? -------3 • A table of all of the chunks that were allocated in the pool (some were freed and therefore marked free). 1. The chunk address. 2. The chunk size. 3. Whether the chunk is occupied or free.
Software Diagnostics Output OCOMM LEVEL = 0 ## 1400 ocomm key variables -------------------------Heap device key : Physical device key : Rtu to RTU station address : Rtu to RTU system address : Rtu to RTU Rxlo : Rtu to RTU Rxhi : INTRAC Rxlo : INTRAC Rxhi : Maximum time units for a frame to be in reception queue [sec]: Repeater mode (Yes / No): Control opcode to execute by transmit thread : Answer of execution from receive thread : Pointer to plug-in diagnostic buffer : %% %% %% %% %% %% %% %% %% %% %%
Software Diagnostics Output ## 1401 LEVEL = 1 ocomm key variables (continue) --------------------------------------Radio transmit queue pointer : Radio transmit queue size [frames] : Line transmit queue pointer : Line transmit queue size [frames] : Rtu to RTU reception queue pointer : Rtu to RTU reception queue size [frames] : INTRAC reception queue pointer : INTRAC reception queue size [frames] : Was RTU to RTU reception queue pulled ? (Yes / No): Was INTRAC reception queue pulled ? (Yes / No): Transmis
Software Diagnostics Output ## 1410 The number of times the following operations were executed LEVEL : 10 (zeros the counters after diagnostics) LEVEL : 11 (does not zero the counters) How How How How How How How How How How How How How many many many many many many many many many many many many many ocomm key error counters -------------------------------times did getting buffer fail ? times was a frame transmitted ? times did transmission fail ? times did warmup fail ? times was control frame received
Software Diagnostics Output ## 1420 LEVEL = 20 plug - in modem config. parameters Pre - emphasize enable De - emphasize enable Radio channel monitor or txen polarity Radio indication or Rxen polarity Radio reception condition Radio gain level Line gain level Maximum received frame size A.g.c enable : : : : : : : : : %% %% %% %% %% %% %% %% %% 1 2 3 4 5 6 7 8 9 • FSK INTRAC Piggyback parameters : 1. Yes - Execute pre-emphasis in transmission. 2. Yes - Execute de-emphasis in reception. 3. Comm.
Software Diagnostics Output ## 1440 plug-in modem statistical information Number of spikes received at last reception Total number of spikes received Number of illegal received frames (till 225) : %% 1 : %% 2 : %% 3 • Piggyback hardware statistics LEVEL : 40 - Execute statistics and zero counters. LEVEL : 41 - Execute statistics but do not zero counters. 1. The number of spikes received the last time reception was operated. 2. The total number of spikes received. 3. From piggyback version 1.
Software Diagnostics Output 5. The maximum time frame (in seconds) for data transmission. Transmission over this time will be terminated, and a failure will be declared. The transmission always ends (normally or forced) with a constant tone for holdup time. 6. During this period (in msec), the system allows the plug-in modem to transmit the contents of its internal buffer, after the MOSCAD RTU has finished data transmission. It is not recommended to change this parameter. 7.
Software Diagnostics Output 8. The minimum waiting time (in msec) between one frame transmission and the next. It is measured from the end of the constant tone of the last transmission. 9. To detect a busy channel: Channel Monitor - The channel is busy when C.M. is active. Tone Detect - The channel is busy when there is tone on the channel. 10. The amount of quiet time on the radio (msec). 11. The amount of busy time on the radio, meaning Radio Tone Detect is active.
Software Diagnostics Output 7. Transmits a constant tone during this period (in msec), before data transmission starts. 8. The maximum time frame (in seconds) for data transmission. Transmission over this time will be terminated, and a failure will be declared. The transmission always ends (normally or forced) with a constant tone for holdup time. 9.
Software Diagnostics Output ## 1503 LEVEL = 3 Control channel Configuration parameters: Wait for control - channel - access timeout Sec Warmup control - channel time mS Transmission timeout Sec Wait for holdup timeout Sec Holdup control - channel time mS Shutup control - channel time mS Current status of control channel : 2 Is transmission enabled : %% : : : : : : %% %% %% %% %% %% 1 1 1 1 1 1 : %% 2 1. The piggyback control channel access parameters used for its diagnostics and configuration.
Software Diagnostics Output 7. Yes: OCOMM module is waiting for end of current piggyback transmission. (UART of CPU has finished transmitting). 8. Transmission state: Init, Grant (executing Channel Access), Warmup (transmitting Tone) and so on. 9. The amount of timeout left for current state. 10. The name of the channel that is currently being transmitted to. 11. Current channel access priority. 12. The amount of time the current channel was quiet before transmission or channel access. 13.
Software Diagnostics Output GPS ## 1600 GPS module parameters Heap key UART key Update System flags function pointer Read Ladder time offset function pointer Period to Get time from GPS [sec] Local offset to UTS time Local offset time at Reserved Values Table Last PPS occurred at Last PPS (before GPS - frame) occurred at Time sent from GPS Date sent from GPS Elapsed time from last PPS when saving it Time that GPS frame was encoded Current calculated local time Current calculated local date Is GPS connected
Software Diagnostics Output 13. When the GPS frame was encoded and calculated in local time. Because it is correct for 9, 10 is to be added. 14. The time calculated via GPS + offset. 15. The date calculated via GPS + offset. 16. Yes : GPS is connected to MOSCAD(always defaults to no). 17. Whether the time from GPS is valid. 18. Yes : Execute Warm Restart , meaning reconfigure GPS.
Software Diagnostics Output ## 1610 GPS statistical information How many 2 seconds timeout occurred during reception ? : How many valid frames were received : Number of invalid frames received (total) : Number of received frames that got timeout in the middle : Number of received frames with size less than 4 chars : Number of received frames that got invalid 2 prefix bytes : Number of received frames that got invalid 2 opcode bytes : Number of received frames with length more than required : Number of rece
Software Diagnostics Output TCP/IP ## 1700 LEVEL = 0 Ethernet address IP address Default router address IP network mask IP broadcast address Time in ms between clock service calls Boot time in seconds Max num of packets on UDP sending queue Max num of packets on UDP receive queue Max num of packets on sending queue of TCP socket Max num of packets on receiving queue of TCP socket Maximum retries to create TCP connection Maximum sockets Maximum # of waiting connection for listening socket Initial size in
Software Diagnostics Output 9. The maximum number of packets on the UDP receive queue. 10. The maximum number of packets on the sending queue of the TCP socket. 11. The maximum number of packets on the receiving queue of the TCP socket. 12. The maximum number of retries to create a TCP connection. 13. The maximum number of sockets. 14. The maximum number of waiting connections for the listening socket. 15. The initial size in MSS for the TCP dynamic receive window. 16.
Software Diagnostics Output GAUART ## 2020 DEVICE = COMxA, RTUxA, LINxA LEVEL = 0 GAUart 's Hardware Internal Registers :-----------------------------------------Internal software data (key) (DATA) : General Status Register (GSR) : General reset Register (GRR) : Events Register (ER) : Events Mask Register (EMR) : Max idles Register (MX_IDL) : Close Character : baud rate read register low (BRR_L) : baud rate read regiaster high (BRR_H) : Mode register (MR) : control 1 register (CC1) : control 2 register
Software Diagnostics Output 17. Receive Ready control Register (2nd buffer). 18. Receive Status control Register (2nd buffer). 19. Transmit control bits (2nd buffer).
Software Diagnostics Output ## 2022 LEVEL = 2 GAUART's Internal RAM data-Device Key :-----------------------------------------Current mode parameters (MODE_BACKUP): %% 1 Current rate parameters (RATE_BACKUP): %% 2 Current sync parameters (SYNC_BACKUP): %% 3 Address mask parameters (MASK_BACKUP): %% 4 Address data parameters (ADRS_BACKUP): %% %% %% %% 5 Current channel's name (CHAN_BACKUP): %% 6 Current channel's data (CHAN_DATA) : %% 7 Current channel's code (CHAN_CODE) : %% 8 Current heap's name (HEAP_B
Software Diagnostics Output 16. Offset for Tx descriptors for transmitting frame . 17. MTE signal of conditions that were met. 18. Whether the frame is formatted or unformatted. 19. Device semaphore. 20. Not in use. 21. Coded time stamp of last received frame (in ticks) 22. Current counter of noise. 23. Current counter of quiet. 24. GRANT-TIME for channel access: The time the site will wait to obtain a transmission channel until it decides that a channel is not available. 25.
Software Diagnostics Output IPLINK ## 2200 LINxL LEVEL = 0 Iplink device key -------------------Heap key : %% 1 Network key : %% 2 Network pin table : %% 3 Site ID : %% 4 Link ID : %% 5 IP port number : %% 6 IP address : %% 7 Enable RCP : %% 8 Port is in Fail : %% 9 Group IP address : %% 10 All RTU Simulation: %% 11 Enable IPModem : %% 12 Learn IP Address : %% 13 Check failed sites : %%14 Max echoes to send : %%15 Max sec between echoes: %%16 Max sec to check alive: %%17 When Port is defined as MDLC Ove
Software Diagnostics Output transmission to it results in an ICMP:Dest Unreach error message, or when the ‘check alive’ test fails. Use of this parameter makes MLDC over IP more reliable when transmitting to failed sites. 15. If ‘Check failed sites’ is YES, this specifies the number of retries of the ‘check alive’ test to the failed site, before the message is routed to an alternative path (if such exists) and asserting that it is still failed. 16.
Software Diagnostics Output 8. Last Site ID from which the RTU received transmission. 9. Last IP address from which the RTU received transmission. ## 2203 LEVEL = 3 Iplink conversion table -----------------------Maximum entries allowed Number of actual entries Next entry for setcall Site ---- IP-address ---------- Status ------ : %%1 : %%2 : %%3 Number Failed ------ Echo Reply Average Failed Echo Sent Received Delay Time[sec] Hint Left ---- -------- ------ --------- ---- ---- 1.
Software Diagnostics Output ## 2210 LEVEL = 10, 11 Iplink statistics -----------------Number of times re-opened socket : Number of times transmitted successfully : Number of times failed transmission : Number of times failed get IP address before transmitting : Number of times failed set IP address after receiving : Number of times failed get buffer from heap : Number of times received a frame successfully : Number of times failed reception : Number of times received irrelevant frame : Number of times fa
Software Diagnostics Output 13. Number of times the port recovered from failed mode. 14. Reason for failure to push received radio data frame to network (as in 11 above.) 15. Number of times transmission was attempted to a destination site with the same IP address as the RTU. As a result, transmission failed. 16. Number of times an ICMP:Host Unreachable message was received after transmission. As a result, destination site has become failed. 17.
Software Diagnostics Output SLIP ## 2300 LINxSlp LEVEL = 0 Slip port parameters --------------------formater key : %%1 port mode : %%2 port rate : %%3 port from : %%4 port flow control : %%5 Is device down : %%6 Is char being received : %%7 Is driver wait during transmission: %%8 Char that is being received : %%9 Has device went up ? : %% 10 Is driver being stopped ? : %% 11 Is reception from port being held? : %% 12 Is driver PPP ? : Maximal no reception time to declare disconnect [sec]: Time elapsed si
Software Diagnostics Output 14. Timeout in seconds in which no data was received and disconnecting/reactivating SLIP/PPP. 15. Time elapsed in seconds since the last received SLIP/PPP data from port. 16. Is PPP/SLIP driver in the process of being disconnected? 17. Is PPP/SLIP driver in the process of being connected? 18. Not relevant. 19. Not relevant. 20. Was an AT response noted when receiving data in SLIP/PPP mode? An AT response can be ERROR, +CME ERROR, AT, ATH, etc.
Software Diagnostics Output 2. Status of IPCP layer (up or down). 3. Status of PAP layer (up or down). 4. Status of CHAP layer (up or down). 5. Not relevant. 6. Not relevant. 7. Not relevant. 8. Not relevant. 9. Number of retries to terminate or configure the LCP layer. 10. Number of retries to terminate or configure the IPCP layer. 11. Number of retries to terminate or configure the PAP layer. 12. Number of retries to terminate or configure the CHAP layer. 13.
Software Diagnostics Output ## 2302 LEVEL = 2 PPP log information ------------------Last protocol received LCP protocol received LCP code received LCP id received LCP message length LCP message received Time received last LCP Number of Nak received Number of Rej received : : : : : : : : : IPCP protocol received : IPCP protocol received : IPCP code received : IPCP id received : IPCP message length : IPCP message received : Time received last IPCP: Number of Nak received : PAP protocol received : PAP cod
Software Diagnostics Output PAP message length : %%52 PAP message transmitted : %%53 Time transmitted last PAP: %%54 CHAP protocol transmitted : CHAP code transmitted : CHAP id transmitted : CHAP message length : CHAP message transmitted : Time transmitted last CHAP: Number of 'Success' codes : Number of 'Fail' codes : %%55 %%56 %%57 %%58 %%59 %%60 %%61 %%62 1. Last protocol received. 2. Not relevant. 3. Last LCP code received. 4. Last LCP id received. 5. Last LCP/IP message received. 6.
Software Diagnostics Output 24. Not relevant. 25. CHAP code received. 26. CHAP id received. 27. Length of CHAP message received in bytes. 28. CHAP message received. 29. Time the CHAP message was received. 30. Number of ‘Success’ CHAP messages received. 31. Number of ‘Fail’ CHAP messages received. 32. Not relevant. 33. Not relevant. 34. Last LCP code transmitted. 35. Last LCP id transmitted. 36. Last LCP/IP message length in bytes. 37. Last LCP/IP message transmitted. 38.
Software Diagnostics Output 53. Last PAP message transmitted. 54. The last time an PAP message was transmitted. 55. Not relevant. 56. CHAP code transmitted. 57. CHAP id transmitted. 58. Length in bytes of the last CHAP message transmitted. 59. Last CHAP message transmitted. 60. The last time an CHAP message was transmitted. 61. Number of ‘Success’ CHAP messages transmitted. 62. Number of ‘Fail’ CHAP messages transmitted.
Software Diagnostics Output 3. Number of bytes received. 4. Number of bytes received by the RTU which could not be processed. 5. Not relevant. 6. Size in bytes of the last transmitted datagram. 7. Number of rejected transmissions of datagrams when the driver was paused. The driver is paused when initializing modem (e.g. iDEN) using AT commands. 8. Number of times the driver was paused. 9. Number of times failed to pause the driver. 10.
Software Diagnostics Output ## 2398 PPP is not created on this port User has tried issue level 1 or 2 for SLIP port (## 2301 or ## 2302). Port is not PPP. ## 2399 PPP was not initialized yet try again later User has tried issue level 1 or 2 for PPP port (## 2301 or ## 2302). Port is still initializing and cannot provide data. Try again later.
Software Diagnostics Output 4. Sequential number of configuration message last sent to radio. 5. Indicates last type of operation. 6. Indicates whether radio succeeded in registering in the infrastructure. 7. Whether data service is unavailable (This might be the reason for failure to register in infrastructure.) 8. Whether network is unreachable (This might be the reason for failure to register in infrastructure.) 9. Not relevant. 10. The string which the radio returns (RF ACK). 11.
Software Diagnostics Output ## 2505 LEVEL = 105 Encryption failue info: ----------------------%% RTU sets radio in encrypted mode: %% Encryption mode of radio : %% Indicates if there is a contradiction between the radio’s actual encryption mode and the encryption mode according to the RTU.
Software Diagnostics Output 15. Last Destination IP Address for which an acknowledgement was received.
Software Diagnostics Output 13. Optional AT command string to send to modem before dialing. Used by the RTU to override default settings in the modem. Refer to technical support if needed. 14. Radio sampling time in milliseconds that RALP will poll the radio registration status. Relevant only if RALP is enabled. 15. Device to which the RTU is connected (iDEN,Tetra, Standard Modem, or Null Modem). 16. YES, if the RTU should disconnect Slip/PPP when getting an ICMP:Destination Unreach message. 17.
Software Diagnostics Output 6. If last modem configuration failed, display the reason for the failure. 7. The last AT command which was sent to the modem when configuring it. 8. If modem configuration has failed, display the last response from the modem that caused this failure (No Response if there was none). 9. Time in milliseconds that it took to configure the modem last time. Relevant only if modem configuration has succeeded.
Software Diagnostics Output ## 2523 LEVEL = 103 iDEN Radio Status: -----------------Radio status : %% Radio substatus : %% Radio services : %% Radio mobile IP : %% 1 2 3 4 1. Modem status. 2. Modem substatus (Packet data registered). 3. Modem supported services (e.g. packet data). 4. Accept if modem is mobile IP capable.
Software Diagnostics Output ## 2525 LEVEL = 105 LAPi related statistics in iDEN modem: -------------------------------------Number of PRAP message expirations : Number of Inbound I PDUs sent (not including retries) : Number of Inbound All Block Retry I PDUs sent : Number of Inbound Retry I PDUs sent : Number of Outbound I PDUs received (not including retries) : Number of Outbound Retry I PDUs received : Number of PDUs lost when the LLC receives a Local Release : Number of PDUs lost due to an error or con
Software Diagnostics Output ## 2526 LEVEL = 106 IP Related Statistics in iDEN modem: -----------------------------------Total number of IP Datagrams received from DTE : Total number of Total IP Datagrams received from FNE : Number of Valid IP Datagrams received from DTE : Number of Valid IP Datagrams received from FNE : Number of IP Datagrams sent to DTE : Largest IP Datagram sent to DTE (bytes) : Largest IP Datagram sent to FNE (bytes) : Number of ICMP Error Messages Sent : Number of Valid UDP Datagrams
Software Diagnostics Output ## 2527 LEVEL = 107 iDEN modem server description ----------------------------Normalized battery level : %% Color code : %% Carrier : %% Carrier RSSI (dbm) : %% Carrier SQE (db) : %% Battery level : %% Signal strength : %% 1 2 3 4 5 of %% 6 of %% 7 Obtained via RALP from modem. 1. Battery level 0 to 60. 2. Color code. 3. Carrier code. 4. RSSI, received signal strength, should be more than –100 dbm. 5. SQE, received signal strength in db. 6.
Software Diagnostics Output Configuration Advanced Link Layer. If data was transmitted while the modem was being configured, that data may have been lost. 5. Number of times that configuration succeeded. 6. Number of times that configuration failed. When failed, the RTU keeps reconfiguring the modem in cycles until it succeeds. This number denote how many configuration cycles have failed. 7. Number of times the RTU failed to register the modem because it is not data packet capable.
Software Diagnostics Output ## 2540 LEVEL = 210,211 RALP statistics: ---------------Number of times failed lock RALP Number of times posted a request Number of times aborted request Number of times got response for requests Number of times got unsolicited alarms Group of last response received from radio Opcode of last response received from radio Last alarm received from radio Number of software alarms received from radio Last software alarm error Last software alarm task name Number of registration ala
Software Diagnostics Output ## 2542 LEVEL = 102 IPMODM File variables --------------------Variable Value ------------ When a Standard Modem is used, this level shows obtained variables as set in the downloadable IP Modem file. The Variable column shows the variable name, and the Value column shows its contents. ## 2598 Failed communicate with radio Indication that communication with radio has failed. (Occurs when response from the radio times out.
Software Diagnostics Output ## 2710 LEVEL = 10,11 Dmap27 counter information : Number ok txframes :%%1 Number bad txframes :%%2 Number reject txframes :%%3 Number returned txframes :%%4 Number ok rxframes :%%5 Number bad rxframes :%%6 Last netpush err :%%7 1. Number of MDLC frames transmitted successfully by the LINK. 2. Number of MDLC frames not transmitted successfully by the LINK. 3. Number of MDLC frames rejected by the LINK. 4. Number of MDLC frames returned back from the LINK. 5.
Software Diagnostics Output MPT1327 (PHYSICAL MODULE) DEVICE = RADxP ## 2750 LEVEL = 0 ********************** * MPT1327 DEVICE KEY * ********************** pointer to device key : %%0 --------------------------sync part of the data table --------------------------sync_mode (hdlc mode) : %%1 sync_rate (data rate) : %%2 sync_chan_backup_ptr (pointer to channel device name): %%3 sync_chan_data_ptr (pointer to channel device data): %%4 sync_signal (sync communication signal) : %%5 sync_time_lock (sync SYNCRO
Software Diagnostics Output 5. Signal parameter, contains the status of the system (HDLC mode). 6. Sync SYNCRONIZATION latch lock. 7. Sync SYNCRONIZATION latch data. 8. Sync holdup time. Replaces the holdup parameter in the radio model. Its purpose is to set holdup time in the transmit mechanism. 9. Maximum time to wait until TXD_EMPTY occurs. 10. Sync RTS mode automatic "0" or on "1". 11. Sync Channel’s Delay in Msec units. 12. CONTROL RATE, MAP27 baud rate (9600 default). 13.
Software Diagnostics Output ## 2751 LEVEL = 1 ****************************** * MPT1327 hardware registers * ****************************** CURRENT MODE (from device key) : %%1 ASYNC_MODE=0 , SYNC_MODE=1 SCON1 (Config register) ASYNC_MODE = 00D6 h SYNC_MODE = 30D6 h : %%2 SCM1 (Mode register) ASYNC_MODE = 013D h SYNC_MODE = 093C h : %%3 DSR1 (Data sync register) ASYNC_MODE = 7E7E h SYNC_MODE = 7E7E h : %%4 SCCE1 (Event register) : %%5 ASYN (CTS,CD,IDL,BRK,CCR,BSY,TX,RX) SYNC (CTS,CD,IDL,TXE,RXF,BS
Software Diagnostics Output 4. DSR1 register parameters (See MC68302 Manual Page 4-119) 5. SCCM1 register parameters (See MC68302 Manual Page 4-44) 6. SCCE1 register parameters (See MC68302 Manual Page 4-44) 7. SCCS1 register parameters (See MC68302 Manual Page 4-44) 8. PACNT (PORT A Control register parameters) (See MC68302 Manual Page 3-33) 9. PADDR (PORT A Direction register parameters) (See MC68302 Manual Page 3-35) 10.
Software Diagnostics Output 9. UART ADDRESS Character 2 (UART mode) 10. Receive Control Character Register (UART mode) 11. CONTROL Character 1 (UART mode) 12. CONTROL Character 2 (UART mode) 13. CONTROL Character 3 (UART mode) 14. CONTROL Character 4 (UART mode) 15. CONTROL Character 5 (UART mode) 16. CONTROL Character 6 (UART mode) 17. CONTROL Character 7 (UART mode) 18.
Software Diagnostics Output 5. Discard Frame Counter (HDLC mode) 6. CRC Error counter (HDLC mode) 7. Abort Sequence Counter (HDLC mode) 8. Nonmatching Address Received Counter (HDLC mode) 9. Frame Retransmission Counter (HDLC mode) 10. Max Frame Length Register (HDLC mode) 11. Max Length Counter (HDLC mode) 12. User-Defined Frame Address MASK (HDLC mode) 13. User-Defined Frame Address (HDLC mode) 14. User-Defined Frame Address (HDLC mode) 15. User-Defined Frame Address (HDLC mode) 16.
Software Diagnostics Output ## 2754 LEVEL = 3 ******************************* * MPT1327 DESCRIPTORS STATUS * ******************************* RECEIVE INDEX (RECEPTION INDEX) : %%1 TRANSMIT INDEX (TRASMITION INDEX) : %%2 ----------------------------------------------RECEIVE ! STATUS ! LENGTH ! BUFFER ----------------------------------------------(RXBD0) : %% ! %% ! %%3 (RXBD1) : %% ! %% ! %%4 (RXBD2) : %% ! %% ! %%5 (RXBD3) : %% ! %% ! %%6 (RXBD4) : %% ! %% ! %%7 (RXBD5) : %% ! %% ! %%8 (RXBD6) : %% ! %% !
Software Diagnostics Output 3. Number of Abort sequences. 4. Number of frames with non-matching addresses. 5. Number of frames which had to be retransmitted. 6. Counter which measures if the Async receive descriptors are full. This number should be zero. If not, there might be a problem with the values of the radio’s timers. This should be checked using the RSS of the radio) 7. Counter which measures if the Async transmit descriptors are full. This number should be zero.
Software Diagnostics Output 2. Map27 mode: One of : “CONTROL", "DATA". 3. Indication that Initialization was done. (1 = yes, 0 = no) 4. Indication that this site is the initiator of the call. (1 = yes, 0 = no) 5. Indication that the IMAP27 warmup process was done (dialing). (1 = yes, 0 = no) 6. Indication that a new MAP27 (to Site ID) conversion table exists. 7. Indication that a MAP27 link to the local radio is exists. 8. Indication that the attempt to transmit a frame in MAP27 protocol has failed.
Software Diagnostics Output ## 2810 LEVEL = 10,11 Imap27 counter information : Number ok txmapframes :%%1 Number bad txmapframes :%%2 Number rxmapbytes :%%3 Number ok txmdlcframes :%%4 Number bad txmdlcframes :%%5 Number ok rxmdlcframes :%%6 Number bad rxmdlcframes :%%7 Number failedcalls :%%8 Number outcalls :%%9 Number accepted incalls :%%10 Number ignored incalls :%%11 Number line was cleared :%%12 Number protocol info :%%13 Number radiobusy :%%14 Last protocol info reason :%%15 Failed get buf :%%16
Software Diagnostics Output DESx ## 2900 %%#1 LEVEL = 0 %%#2 Encryption device information. Two strings will appear: 1. Denotes whether or not a certain DES instance is active. 2. DES serial number ## 2901 LEVEL = 1 Size of an encryption key alias: %%1 Number of encryption keys possessed: %%2 Currently active encryption key set: %%3 Number of encryption keys in each set:%%4 1. Encryption key alias size. 2. Number of encryption keys. 3. Encryption key set which is currently active. 4.
Software Diagnostics Output AUSYNC ## 3000 LEVEL = 0 Operation mode: Is synchronized (1=YES, 0=NO): SYNC interval (seconds): Number of links (includes zones): Number of authenticated links: Server SiteID: Server LinkID: Server link index: Maximum drift (seconds): RX SYNC interval (seconds): TX SYNC REQUEST interval (seconds): TX AFTER RESTART retry (seconds): Maximum network delay (MSEC): RX SYNC timer (seconds): TX AFTER RESTART timer (seconds): TX SYNC REQUEST timer (seconds): Requested signals (HEX):
Software Diagnostics Output ## 3001 LEVEL = 1 Device keys: MiniSession device key (HEX): Stock device key (HEX): Heap device key (HEX): TimeAuth device key (HEX) : %%1 %%2 %%3 %%4 1. The MiniSession device key in Hexadecimal form. 2. The Stock device key in Hexadecimal form. 3. The heap device key in Hexadecimal form. 4. The TimeAuth device key in Hexadecimal form.
Software Diagnostics Output ## 3011 LEVEL = 11 Counters: Number of Number of Number of Number of Number of Number of Number of requests arrived: requests handled: requests sent: responses arrived: invalid response: SYNC arrived: invalid messages: %%1 %%2 %%3 %%4 %%5 %%6 %%7 1. Count of the number of requests which have arrived. 2. Count of the number of requests which have been handled. 3. Count of the number of requests which have been sent. 4. Count of the number of responses which have arrived. 5.
Software Diagnostics Output REQMNG ## 5000 LEVEL = 0 Reqmng data: -----------max clients max channels max buffers comm buffer length clients offset channels offset buffers offset read list offset next client next channel n read channels cur buffer gateway id gateway status client error mng thread channel tx global rx global mng global site id startup mode left : : : : : : : : : : : : : : : : : : : : : : %%1 %%2 %%3 %%4 %%5 %%6 %%7 %%8 %%9 %%10 %%11 %%12 %%13 %%14 %%15 %%16 %%17 %%18 %%19 %%20 %%21 %%22
Software Diagnostics Output ## 5001 name %%1 LEVEL = 1 free %%2 id %%3 tx %%4 burst %%5 error %%6 1. The name of the connected clients. (If a row starts with 1, the name field is empty.) 2. Is the client free? 3. The channel ID of the channel used for receiving. (255 means no such channel) 4. The channel ID of the channel used for transmitting. (255 means no such channel) 5. The channel ID of the channel used for burst. (255 means no such channel) 6.
Software Diagnostics Output HELTHCH (HEALTH CHECK) ## 5121 LEVEL = 1 Health Check Diagnostics - Rtus ------------------------------SiteId LinkId Status PingTime ------ ------ ------------%%1 %%2 %%3 %%4 (times are in seconds) ResponseTime -----------%%5 PingsSent -------%%6 1. The Site ID. 2. The Link ID of the link through which the site is connected to the network. 3. The status of the site (alive /dead / disabled) 4. The time that the last ping was sent. 5. The time of the last response to a ping.
Software Diagnostics Output DOCTOR ## 5211 LEVEL = 1 %%1 Doctor Version: %%2 System Version: %%3 MTE ERROR SR:%%4 PC:%%5 ErrCode:%%6 CurrTask:%%7 CandidTask:%%8 DevKey:%%9 DevName:%%10 %%11 In the first line, general information about the crash history is presented. 1. The time and date of the restart event. 2. The version and revision of the Doctor feature. 3. The version and revision of the firmware. 4. The contents of the SR register at the time of restart. 5.
Error Messages Error Logger Messages This section lists the errors and warnings which may be generated by the Error Logger. The messages are listed as they appear on the screen, with %% signs in the text to represent alphanumeric values provided by the Error Logger. The description which follows the error messages, provides one or more possible causes for the error and possible solutions.
Error Messages Error #41: Low Byte Error When Using Flash Memory This message appears during configuration download, while downloading the flash. There is a problem in the flash. Error #42: High Byte Error When Using Flash Memory This message appears during configuration download, while downloading the flash. There is a problem in the flash. Error #43: Given address is not start address of flash memory This message appears during configuration download, while downloading the flash.
Error Messages Error #81: No Fixed transactions Table Was Assigned To Slave A fixed transaction was received but the fixed transaction table was not downloaded into the slave. Error #82: Bad transaction Format Illegal transaction. For example: 'Z' (table number) does not exist. Error #85: Trying To Comm. After Session Was Ended Illegal communication. The transaction ended but data still arriving. This may occur due to differences in the data structure of master and slave.
Error Messages Error #111: From Site : %%Link : %% can not communicate with current unit Communication was initiated by a site which is not defined in the Site table. Error #112: Trouble in queue: %% Illegal management of linked buffers. Error #113: Illegal control byte : %% Memory overwrite in a buffer that passed a CRC check. The buffer is dumped into the heap. Error #114: Illegal buffer : %% The Transport Multiplex layer can not understand a buffer that passed a CRC check.
Error Messages Error #141: Can not find Link ID in network configuration, network layer: %% Dest Site: %%, Dest Link: %%, Dest Port: %% The network layer in a RTU is asked to transfer a communication buffer to the Dest Site, Dest Link & Dest port but there is no route defined in the network configuration, which the communication can be transferred through.
Error Messages Error #181: Getting illegal date & time: Seconds: %% Minutes: %% Day : %% Date : %% Hours: %% Month: %% Year: %% May indicate either system software error or incorrect real-time clock component in the RTU. Consult product group. Error #190: Corrupted heap data base: device pointer to start chain pointer to current chain pointer to end chain # of buffers left in heap : %% : %% : %% : %% : %% May indicate system software problem. Consult product group.
Error Messages Error #230: Bad table coordinate :%% The 'Z' coordinate (table number) belongs to a table that does not exist in the application, probably because of differences in the data structure between master and slave. Error #231: Bad row coordinate :%% in table #%% The 'Y' coordinate (row number) does not exist in the table, probably because of differences in the data structure between master and slave.
Error Messages Error #241: Txintrc or Rxintrc was called with invalid type %% Invalid parameter type. See Intrac Protocols chapter in Advanced Features in the Application Programmer manual. Error #242: Intrac/Meic port not created The appropriate port must be defined in Site Configuration. Error #243: One of the following calls: Txintrc, Txwidth, Rxintrc, Rxwidth, Rxiupd failed getting pointer to value at intrac system table May indicate system software problem. Consult product group.
Error Messages Error #257: Some Failure In Module %%. Faulty FIFO communication in the specified module. Error #258: CLOCK fail flag in module %% is on. The clock in the specified module is faulty. Error #259: I/O module: %% EE memory problem. All the channels are calibrated, but the inner EE is problematic. Error #260: Analog input module: %% FIFO time-out. The Analog Input module does not respond to the RTU CPU.
Error Messages Error #270: Incompatible Communication PROTOCOL on: PORT #%% CONTROL=%% STATUS=%% May indicate system software/hardware problem. Consult product group. Error #271: Uncontrollable Communication PHYSICAL on: PORT #%% CONTROL=%% STATUS=%% May indicate system software/hardware problem. Consult product group. Error #272: Unoperational Communication PHYSICAL on: PORT #%% CONTROL=%% STATUS=%% May indicate system software/hardware problem. Consult product group.
Error Messages Error #282: Unoperational Communication CHANNEL on: PORT #%% CONTROL=%% STATUS=%% The port is transferred to software mode. This message is displayed if CD is not active. Error #283: Unoperational CHANNEL Internal LOOP on: PORT #%% CONTROL=%% STATUS=%% Incompatibility between the frame that was sent and received by the internal loop.
Error Messages Error #290: A fault has occurred in the spread spectrum (aironet) radio. The system has checked the radio registers and found that their values are different from the expected ones. The system tried to correct the problem by reinitializing the radio unsuccessfully. A power restart of the CPU and the radio may resolve the problem. Try to do a restart.
Error Messages Error #304: MTE: The CONTROL procedure of devices was not started, because the type of control parameter is out of range !! Type of requested control was : %% The last valid control entry is : %% Internal error. May indicate system software problem. Consult product group. Error #305: MTE: The MTE CONTROL procedure of devices failed !!! Device Name : %% Control Type : %% Number of successive fails : %% The control procedure of one of the devices has failed.
Error Messages Error #400: Presentation layer: in function %% remove slice failed. Remove slice failed. May indicate system software problem. Consult product group. Error #401: Presentation layer: in function %% get slice failed. Get slice failed. May indicate system software problem. Consult product group. Error #402: Presentation layer: in function %% push byte in fbuf failed. Push byte failed. May indicate system software problem. Consult product group.
Error Messages Error #413: Presentation layer: in function %% format error, encryption not supported. Encryption and compression are not supported. May indicate system software problem. Consult product group. Error #414: Presentation layer: in function %% format error, control number out of range. Protocol format error. May indicate system software problem. Consult product group. Error #415: Presentation layer: in function %% general synchronization error. May indicate system software problem.
Error Messages Error #560: The MC68882 Coprocessor is connected, but is not OK. All floating point and double precision calculations are emulated by software. Error #561: The MC68882 device data is corrupted. Software problem. May indicate system software problem. Consult product group. Error #562: The check validity or test of MC68882 device failed due to MTE_TSTNSET locking. Software problem. May indicate system software problem. Consult product group.
Error Messages Error #606: Fatal !!! Division by 0 in rungs while performing the divide operation. The result is undefined !! Dividing by 0 in user application. Error #620: Ticks disabled exceed allowed limit : SR=%% IPR/IMR=%% WRR/WCN=%% May indicate system software problem. Consult product group. Error #640: Fatal !!! Not enough work space for Monitor application !! Available space transferred for the Monitor – %% bytes. Minimum space required for Monitor – %% bytes.
Error Messages Error #735: Device TOPLC,Function %%, Port Name %% : Unable To Alloc Uf Buffer. Allocation problem. May indicate system software problem. Consult product group. Error #736: Device TOPLC,Function %%, Port Name %% : Unable To Unpack Uf Buffer. Unpack Uf Buffer failed. May indicate system software problem. Consult product group. Error #737: Device TOPLC,Function %%, Port Name %% : Unable To Alloc Buffer. Allocation problem. Empty heap. Consult product group.
Error Messages Error #746: Device TOPLC, Function %%, Port Name %% Received a control from the SWITCHER while there is no software loaded for the PLC port. The received f_buf (control) has been freed. The RTU has to switch frames while the protocol is not loaded in the FLASH memory. Error #760: Device TOSCADA, Function %% Port Name %% : Illegal Request from application. May indicate system software problem. Consult product group.
Error Messages Error #770: Device TOSCADA, Function %% Port Name %% : Cannot find site index and port. There is a problem in PLC table or site table definition. Error #771: Device TOSCADA, Function %% Port Name %% : Not enough memory for the application. Memory problem. Consult product group. Error #772: Device TOSCADA, Function %% Port Name %% : flashapp_get_block() has failed !! May indicate system software problem. Consult product group.
Error Messages Error #823: Userrom Plc module, Function %% Get_coldef_tab Failed ! May indicate system software problem. Consult product group. Error #824: Userrom Plc module, Function %% Data Type Format Error In Protocol ! Communication format error. Consult product group. Error #825: Userrom Plc module, Function %% Data Type Mismatch ! Data type error when accessing a column via PLC communication. Data type mismatch.
Error Messages Error #833: Userrom Plc module, Function %% Cannot Find PLCStt ! May indicate system software problem. Consult product group. Error #834: Userrom Plc module, Function %% Iolink definition problem of PLC column ! May indicate system software problem. Consult product group. Error #835: Userrom Plc module, Function %% Some PLC address in not defined in PLC Table ! Define all PLC addresses in the PLC Table.
Error Messages Error #844: Userrom Plc module, Function %% Cannot Find PLC address %% in download process or userrom not OK. Can not perform PLC communication while application not loaded or during application download. Error #845: Userrom Plc module, Function %% Failed to find PLC address %% in PLC Table. Define all PLC addresses in PLC Table.
Error Messages Error #876: The TX thread did not hang up the phone line as the RX thread asked. For system software developers. Consult product group. Error #877: Can not find Site Id – %% in phone book. Can not dial a Site ID without it being defined in the phone book. Error #878: Modem refuses to dial this phone number (too long, invalid command, or answer mode only): Invalid command (internal problem).
Error Messages Error #908: PLC Switcher module, Function %% Cannot get the PIN Table ! May indicate system software problem. Consult product group. Error #909: PLC Switcher module, Function %% Cannot find the key of a PLC port software from logical port i.d.! May indicate system software problem. Consult product group. Error #910: PLC Switcher module, Function %% Cannot find in switcher port table the key of PLC%% connected to %% PLC table,site table or third party protocol port definition problem.
Error Messages Error #934: MODBUSTM module, Function %% The MODBUS reply frame CRC is not correct CRC error in MODBUS reply frame. Error #935: MODBUSTM module, Function %% The size of RTU PLC format reply is too large or too small The master should not send frames or poll for frames longer than 140 bytes. Error #936: MODBUSTM module, Function %% No support for broadcast. Frame ignored The MODBUS module does not support broadcasts.
Error Messages Error #944: MODBUSTM module, Function %% The box number of the reply is not as expected!! Timeout problems. Consult product group. Error #945: MODBUSTM module, Function %% The length of pure data in frame is not as expected!! Timeout problems or system software problem. Consult product group. Error #946: MODBUSTM module, Function %% Can not pack in 1 byte the N_BYTES field in 1 byte. The value of N_BYTES > 0xff. May indicate system software problem. Consult product group.
Error Messages Error #972: MODBUSTS module, Function %% The FLUSH function failed, but continuing May indicate system software problem. Consult product group. Error #973: MODBUSTS module, Function %% The Set Parameters function failed, but continuing May indicate system software problem. Consult product group. Error #974: MODBUSTS module, Function %% The size of MODBUS format reply is too large or too small The master should not send frames or poll for frames longer than 140 bytes.
Error Messages Error #982: MODBUSTS module, Function %% The N_ELM field in poll control is zero ! It must be GE from 1. May indicate system software problem. Consult product group. Error #983: MODBUSTS module, Function %% Could not translate the RTU PLC to MODBUS because the MODBUS buffer is too short The master should not send frames or poll for frames longer than 140 bytes.
Error Messages Error #991: MODBUSTS module, Function %% The length of exception reply is not as expected Timeout problems or system software problem. Consult product group. Error #992: MODBUSTS module, Function %% The reply header contents is not as expected Timeout problems or system software problem. Consult product group. Error #993: MODBUSTS module, Function %% The reply frame length is not as expected Timeout problems or system software problem. Consult product group.
Error Messages Error #1006: ABTS module, Function %% Failed to build the reply or command in Allen Bradley format ! May indicate system software problem. Consult product group. Error #1007: ABTS module, Function %% Pure data in Poll control. No data must appear in this control !! May indicate system software problem. Consult product group. Error #1008: ABTS module, Function %% The N_ELM field in send control is EQ 0 ! It must be GE from 1 May indicate system software problem. Consult product group.
Error Messages Error #1016: ABTS module, Function %% The FLUSH function failed, but continuing May indicate system software problem. Consult product group. Error #1017: ABTS module, Function %% Not enough RAM memory for Allen-Bradley load module connected to PLC !! May indicate system software problem. Consult product group. Error #1018: ABTS module, Function %% Allen-Bradley to RTU PLC format translation of reply failed !! Internal communication protocol format error. Consult product group.
Error Messages Error #1109: Attempt To Use Slave With No Entry in Site table – %% RTU defined as Master can not operate without Site table. Error #1110: Self Site ID is not defined in X.25 Addresses Table. Please add it to your Addresses Table. Modify X.25 Addresses Table. Error #1111: Call Request Aborted - UnKnown Site ID: %% Check X.25 Addresses Table. Error #1112: Call Request Aborted - UnKnown X.25 address: %% Check X.25 Addresses Table. Error #1113: Invalid Convert table X.
Error Messages Error #1152: Channel Not Init – Msg Id: %% Msg Type: %% Uninitialized X25/LAPB channel. May indicate system software problem. Consult product group. Error #1153: Intr_ID: %% Code: %% Len: %% Params: %% X25 internal errors. CODE : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Error #1154: Rx frame discarded no header Rx frame discarded inactive Intr. Rx frame discarded Intr.
Error Messages 25 Error #1230: FRMR retry limit Chnltest -RX task got err Frame When Called From Trnsintr. buf_f_get() Returned: %% May indicate system software problem. Consult product group. Error #1231: Chnltest -Received tested frame too small. Length of frame is %% Frame lacks its header. May indicate system software problem. Consult product group. Error #1232: Chnltest -Tx Task Could not get a new buffer from heap. Ret: %% No buffer for transmission.
Error Messages Error #1260: Tmrevent: Events/Timers Buffer is Full. No more buffers for DI events and their related timers. Number of buffers can be increased in expert screen in configuration. Error #1261: Tmrevent: Events/Timers were Ignored – NO 'Get Event' for %% msec DI events and/or related timers were not checked (by GtEvnt function in rungs) during a time interval longer than the maximum time that was defined in the expert screens, and therefore were ignored.
Error Messages Error #1504: ‘TxIntrc’ was called with invalid subgroup ‘ITxSub’ %% This error occurs when you call the TxIntrc function with the wrong ITxSub variable. See Intrac Protocols chapter in Advanced Features in the Application Programmer manual. Possible range: Error #1505: 0-3 ‘TxIntrc’ or ‘ TxWdth’ was called with invalid link ‘Tx_Lnk’ %% This error occurs when you call the TxIntrc or TxWdth functions with the wrong Tx_Lnk variable.
Error Messages 173 174 175 Error #1553: Piggyback got from 68302 frame error Piggyback got from 68302 noise error Piggyback Config register not programmed properly Failed configuring or diagnosing INTRAC modem (ID = %%) The error message ID (%%) may be one of the following: ID 100 101 102 103 Error #1555: Description RTU received irrelevant config/diagnostics ACK from piggyback RTU received irrelevant config/diagnostics ACK from piggyback Piggyback failed to write parameters to its internal eeprom RTU
Error Messages Error #1602: Failed testing INTRAC modem piggyback (CTS signal) Hardware problem in modem. Error #1638: INTRAC system table: invalid radio warmup time (R_Ptt) %% Invalid R_Ptt value in the INTRAC system tables (database builder). Possible range: 10-60000 msec. Error #1639: INTRAC system table: invalid radio override time (ROvrid) %% Invalid ROvrid value in the INTRAC system tables (database builder). Possible range: 10-60000 msec.
Error Messages Error #1751: Invalid block Invalid “C” block loaded to the RTU. Its calculated CRC does not match that of the loaded block. Reload the “C” block. Error #1752: User Application Error: Occurs as a result of MOSCAD_error function usage in one of the “C” blocks loaded to the RTU. Error #1763: 'C' Block version is higher than system 'C' application version. Consult product group. Error #1764: 'C' block no. %% contain invalid name %% in the user_jumptable.
Error Messages Error #1906: Invalid conversion table in Flash Error in MDLC over IP. IP Conversion Table which was downloaded could not be read or is invalid. There may be a problem with the Flash or with the IP Conversion Tool. Consult product group. Error #1907: IP address in conversion table for this CPU is %% instead of the configured %% Error in MDLC over IP. Mismatch in IP Conversion Table between the IP address of this RTU and the one configured in the table.
Error Messages Error #1915: Unsupported 'connect to' %% device in MDLC over IP port ‘Connect to’ parameter is not supported by this system. This is provided for future configuration having new drivers that will be downloaded to older systems that does not support them. Error #1916: MDLC Compression not supported in Slip/PPP port This error is set when future configurations that support MDLC compression on Slip/PPP will be downloaded to older systems that do not support it.
Error Messages Error #1952: The reception queue of the dowloaded protocol driver is full Driver of second protocol is not emptying frames from queue fast enough. Error #2000: No SYNC server list was found in flash. Authentication was not activated. An Authentication information table should be defined in the Network Configuration tool. Error #2001: An invalid SYNC server list was found in flash. Authentication was not activated.
Error Messages Errors #5000-6999 are used for MCP-T. Errors #7000-9999 are used for C Applications. Errors #10000-12999 are used for MCP-M/T. Error: 15001 Reqmng - Buffer size problem : %% %% %% Error: 15002 Reqmng - Buffer2 Size problem : %% %% %% Error: 15003 Reqmng - Suspend failed : %% , ret code %% Error: 15006 Reqmng - Problem mapping devices : %% %% %% Error: 15007 Reqmng - No Comm buffers to fill.
Error Messages Error: 15050 Gtcpip - create socket error %% (%%) Error: 15051 Gtcpip - Bind socket error %% (%%) Error: 15054 Gtcpip - Problem reading from socket %%. Error: 15055 Gtcpip - Select error %%. Error: 15056 Gtcpip - Problem reading from socket %% (%%) Error: 15060 Gtcpip - Create Device error %% Error: 15061 Gtcpip - Problem writing to socket %% (%%) Error: 15062 Gtcpip - Channel already occupied %% (%%).
Error Messages Error: 15236 Trdpool- Get thread failed %% %% Error: 15237 Trdpool- Issue thread, get thread error %% %% Error: 15238 Trdpool- Issue thread, get box error %% %% Error: 15239 Trdpool- Block2Box, get box error %% %% Error: 15241 Trdpool- Block2Box, request length too big %% %% Error: 15242 Trdpool- Block2Box, copy failed %% %% Error: 15243 Trdpool- Get from Free Q error %% %% Error: 15244 Trdpool- Get from Other Q error %% %% Error: 15245 Trdpool- Get from Other Lower Q error
Error Messages Error: 15353 Gtappl - Nstart, setfunctab failed %% %% Error: 15354 Gtappl - Nstart, trdpool get block failed %% %% Error: 15355 Gtappl - Nstart, unknown application type %% %% Error: 15357 Gtappl - Nstart, reqmng push block failed %% %% Error: 15358 Gtappl - Nstart, threadpool release box failed %% %% Error: 15359 Gtappl - Burst, map failed %% %% Error: 15360 Gtappl - Burst, reqmng push block failed %% %% Error: 15365 Gtappl - Mismatch in block data length %% %% Error: 15366
Error Messages Error: 15502 newdel – pure virtual called Error: 15503 mcpsbld – create device error Error: 15510 contalib – forbidden delete: class %% ptr %% Error: 15511 contalib – forbidden resize: class %% ptr %% Error: 15530 HelthChk – Create failed Error: 15531 HelthChk – NULL parameter Error: 15532 HelthChk failed Error: 15533 Send ping failed for site id %% link id %% . Trnsintr_tx_frame_seg_2id() failed. Error = %% Tried %% times.
Error Messages Error: 15611 HASH-DB Failed to Update Heltch-Check\Link-Handler. Error: 15612 HASH-DB Failed to read Site Table. Error: 15630 POOL-MANAGER Failed to create Device. error = %%. Error: 15632 POOL-MANAGER Pool Manager size was Trancate from: %% To: %% error = %%. site = %% Error #16002: Doctor - Burn a new flash section failed. Error code - %% block size - %% block id - %%. Attempt to burn a new section of the flash has failed.
Software Installation Entering the Password When you activate a Toolbox application at the beginning of a work session, Toolbox displays the Password window, shown below, where you must enter the password. Type your password and click OK. This operation activates the communication driver, and the password remains in force throughout the session. If you want to access an RTU that requires a different password, you must stop the communication driver first. See Changing the Session Password below.
