Galaxy Gateway v3 Web-Based Remote Monitoring and Control
Product Manual Select Code 193-104-106 Comcode 108728163 Issue 9 January 2008
Notice: The information, specifications, and procedures in this manual are subject to change without notice. Lineage Power assumes no responsibility for any errors that may appear in this document.
© 2008 Lineage Power All International Rights Reserved Printed in U.S.A.
Galaxy Gateway v3
Table of Contents 1 Introduction.................................................................................................................... 6 The Product..................................................................................................................... 6 This Product Manual....................................................................................................... 8 Customer Service Contacts ............................................................................................. 9 2 Product Description ..................................................................................................... 10 Product Features............................................................................................................ 11 Galaxy Gateway Circuit Pack....................................................................................... 12 User Interfaces .............................................................................................................. 12 Galaxy Gateway Local Port .......................................................................................... 13 Alarm Reporting ........................................................................................................... 14 3 Installation in a Galaxy SC Controller System ......................................................... 15 Introduction................................................................................................................... 15 Preparation .................................................................................................................... 15 Precautions.................................................................................................................... 15 Tools/Equipment Required ........................................................................................... 16 Unpacking the Galaxy Gateway ................................................................................... 16 Galaxy Controller Configuration .................................................................................. 17 Galaxy Gateway Installation......................................................................................... 17 Precautions.................................................................................................................... 17 Procedure ...................................................................................................................... 18 Cable Connections ........................................................................................................ 18 10Base-T Network ........................................................................................................ 20 Configuring Network Communications........................................................................ 20 Logging In to the Galaxy Gateway............................................................................... 21 Configuring Static Network Parameters ....................................................................... 21 Logging Out of the Galaxy Gateway ............................................................................ 22 Post Installation Procedures.......................................................................................... 23 Troubleshooting ............................................................................................................ 23 4 Installation in a Galaxy SCF Controller System....................................................... 26 Introduction................................................................................................................... 26 Preparation .................................................................................................................... 26 Precautions.................................................................................................................... 26 Tools/Equipment Required ........................................................................................... 27 Unpacking the Galaxy Gateway ................................................................................... 27 Galaxy Controller Configuration .................................................................................. 28 Galaxy Gateway Installation......................................................................................... 28 Precautions.................................................................................................................... 28 Procedure ...................................................................................................................... 29 Cable Connections ........................................................................................................ 29 10Base-T Network ........................................................................................................ 30 Configuring Network Communications........................................................................ 31 Logging In to the Galaxy Gateway............................................................................... 31 Configuring Static Network Parameters ....................................................................... 32
Issue 9 January 2008
3
Galaxy Gateway v3
Logging Out of the Galaxy Gateway ............................................................................ 33 Post Installation Procedures.......................................................................................... 34 Troubleshooting ............................................................................................................ 34 5 Installation in a GPS with a Millennium Controller ................................................ 37 Introduction................................................................................................................... 37 Preparation .................................................................................................................... 38 Precautions.................................................................................................................... 38 Tools/Equipment Required ........................................................................................... 39 Unpacking the Galaxy Gateway ................................................................................... 40 Millennium Controller Configuration........................................................................... 40 Galaxy Gateway Installation......................................................................................... 41 Installing Gateway on a GPS Metal Door..................................................................... 42 Installing Gateway on a GPS Plastic Door ................................................................... 43 Galaxy Gateway Cable Connections ............................................................................ 44 10Base-T Network ........................................................................................................ 45 Configuring Network Communications........................................................................ 47 Logging In to the Galaxy Gateway............................................................................... 47 Configuring Static Network Parameters ....................................................................... 48 Logging Out of the Galaxy Gateway ............................................................................ 49 Post Installation Procedures.......................................................................................... 49 Troubleshooting ............................................................................................................ 50 6 Installation in a GPS with a Vector Controller......................................................... 52 Introduction................................................................................................................... 52 Preparation .................................................................................................................... 53 Precautions.................................................................................................................... 53 Tools/Equipment Required ........................................................................................... 54 Unpacking the Galaxy Gateway ................................................................................... 54 Vector Controller Configuration................................................................................... 55 Gateway Installation for Vector Controller .................................................................. 55 Galaxy Gateway Cable Connections ............................................................................ 56 10Base-T Network ........................................................................................................ 57 Configuring Network Communications........................................................................ 57 Logging In to the Galaxy Gateway............................................................................... 57 Configuring Static Network Parameters ....................................................................... 58 Logging Out of the Galaxy Gateway ............................................................................ 59 Post Installation Procedures.......................................................................................... 59 Troubleshooting ............................................................................................................ 60 7 Operation ...................................................................................................................... 62 Introduction................................................................................................................... 62 Web Browser Access (HTTP) ...................................................................................... 62 Using Web Pages .......................................................................................................... 63 Screens .......................................................................................................................... 65 Telnet ............................................................................................................................ 81 Alarm Reporting ........................................................................................................... 84 Galaxy Gateway Upgrade ............................................................................................. 88 TL1 Interface ................................................................................................................ 99
Issue 9 January 2008
4
Galaxy Gateway v3
Appendix A: Technical Specifications ........................................................................ 102 Appendix B: Troubleshooting...................................................................................... 104 Appendix C: FTP Supported Commands................................................................... 105 Appendix D: Telnet Supported Commands ............................................................... 108 Appendix E: Local Port Command Interface ............................................................ 110 T1.317 Command Language....................................................................................... 110 Network Administrator Commands............................................................................ 112 T1.317 Error Messages ............................................................................................... 115 Appendix F: TL1 (Transaction Language 1) ............................................................. 116 Galaxy TL1 Configuration.......................................................................................... 116 Telcordia Reference Documents................................................................................. 117 Appendix G: Safety....................................................................................................... 118 Safety Statements........................................................................................................ 118 Warning and Safety Symbols...................................................................................... 119 Precautions.................................................................................................................. 120 Appendix H: Product Warranty.................................................................................. 121 Revision History ............................................................................................................ 123
Issue 9 January 2008
5
Galaxy Gateway v3
1 Introduction The Product The Galaxy Gateway is a TCP/IP-based data access and networking product designed to meet power plant engineering, operation, and maintenance needs when installed in a Lineage Power Galaxy power system utilizing a Galaxy SC, Galaxy SCF, Galaxy Millennium, or Galaxy Vector controller. It provides remote access to this plant controller to display the power plant’s information via the world wide web (internet) or a user’s enterprise network (intranet). Gateway provides access to most major controller functions including all voltage and temperature readings, current alarms, and alarm history. The following is a list of typical functions available through the Gateway: • • • • • • • • •
Plant configuration Auto rectifier restart Selective high/low voltage shutdown Slope thermal compensation Float/boost mode control Recharge current limit Battery discharge testing Remote alarms test Battery management including reserve time prediction
• Energy management (efficiency algorithm) • Multiple level password security • Remote peripheral monitoring and control for 2-way signaling and monitoring • Controller alarms • Fuse alarms • Battery on discharge (low voltage) • AC fail • Rectifier fail • High voltage shutdown
For a complete listing of controller functions, refer to the specific controller’s documentation. This manual describes version G.3.18 application code and version G.3.14 web pages of the Gateway software. A unique feature of Galaxy Gateway is that older software versions may be upgraded to the latest version using the TCP/IP network connection. Go to http://www.lineagepower.com/ and choose the Design Tolls / Downloads link to download and update to the latest version free of charge. The Galaxy Gateway supports a web-based user interface using standard browsers such as Microsoft Internet Explorer® or Netscape® Navigator. It can provide plant alarm and control information to a distributed or centralized Network Operation Center (NOC) using the Simple Network Management Protocol (SNMP) or the Transaction Machine Language (TL1), which allow Galaxy Gateway to provide alarm information to the NOC for integrated network management.
Issue 9 January 2008
6
Galaxy Gateway v3
The enhanced surveillance capability at the user’s PC includes power plant health assessment, performance measurement, and configuration management through an HTML-based Graphical User Interface (GUI). The Galaxy Gateway provides multi-level secured access to each device, including rectifiers, controllers, batteries, AC/DC distribution, generators, secondary distributions, and peripherals in the site. The Galaxy Gateway, as shown in Figure 1-1, provides network communication with the controller using TCP/IP, commonly known as the Internet Protocol (IP). The Gateway software application includes a web server supporting HTTP, a command line interface supporting Telnet connections to the power system, a file server supporting FTP for remote software upgrades, and network management clients supporting SNMP, TL1, and SMTP. A 10Base-T (RJ-45) physical connector is used to connect the Gateway card to the LAN/WAN network.
Figure 1-1: Gateway Networking Diagram
Issue 9 January 2008
7
Galaxy Gateway v3
This Product Manual This product manual describes the features and operation of the Galaxy Gateway (BJD) when installed in a Galaxy SC or SCF controller, and the Galaxy Gateway (EBW) when installed in a Galaxy Millennium or Vector controller in a Lineage Power system. The emphasis throughout is to provide an introduction to the Gateway. Some familiarity with power systems, power system terminology, controllers, and web pages is assumed. This section also includes a list of contacts for technical support, repair and return, and other services available to customers. Section 2 provides product information on the Galaxy Gateway, outlining its technical highlights, features and applications. Sections 3 through 6 cover installation in the various models of the Galaxy Controller systems. Information found here includes installing the Galaxy Gateway card, cabling, initial configuration, and troubleshooting. Section 7 covers the operation of the Galaxy Gateway, and the use of Telnet, FTP, HTTP web pages, and SNMP protocols to communicate with the Galaxy Controller and/or the Galaxy Gateway. Appendices provide technical specifications troubleshooting, Telnet supported commands, FTP supported commands, TL1 commands, and a glossary.
Issue 9 January 2008
8
Galaxy Gateway v3
Customer Service Contacts Customer Service, Technical Support, Product Repair and Return, and Warranty Service For customers in the United States, Canada, Puerto Rico, and the US Virgin Islands, call 1-800-THE-1PWR (1-800-843-1797). This number is staffed from 7:00 am to 5:00 pm Central Time (zone 6), Monday through Friday, on normal business days. At other times this number is still available, but for emergencies only. Services provided through this contact include initiating the spare parts procurement process, ordering documents, product warranty administration, and providing other product and service information. For other customers worldwide the 800 number may be accessed after first dialing the AT&T Direct country code for the country where the call is originating, or you may contact your local field support center or your sales representative to discuss your specific needs.
Customer Training Lineage Power offers customer training on many Power Systems products. For information call 1-972-284-2163. This number is answered from 8:00 a.m. until 4:30 p.m., Central Time Zone (Zone 6), Monday through Friday.
Downloads and Software Power Systems on-line product manuals are available at http://www.lineagepower.com/ by choosing the applicable links. Galaxy Gateway and EasyView software is available on-line at http://lineagepower.com/ under the Design tools link.
Issue 9 January 2008
9
Galaxy Gateway v3
2 Product Description The Galaxy Gateway provides network access and control capability for users under the HTTP, Telnet, FTP, SMTP, SNMP, and TL1 protocols. The typical protocol functions are as follows:
HTTP HTTP (hypertext transfer protocol) is the foundation protocol of the world wide web (www) and can be used in any client-server application involving hypertext. HTTP makes use of TCP (transmission control protocol) for client to server connection and IP (internet protocol) for internetworking. Gateway’s standard HTTP protocol web pages present integrated site information with an enhanced graphical user interface. In addition, these web pages provide monitoring and full configuration capability for other site devices such as generators, BDFBs, ac monitoring, and other devices connected through the optional remote peripheral module options of the Galaxy SC, SCF, and Millennium controllers. Custom HTTP web pages may also be developed by the user and loaded into the Gateway for display of specific power plant or connected equipment attributes immediately upon a successful network login to the controller.
TELNET Telnet provides remote log-on capability to a computer or server. The terminal to terminal connection with Telnet is based on a TCP connection for traffic between user and server. All controller and Gateway commands that are available via the HTTP web pages can also be issued with the appropriate Telnet-based T1.317 command, identified in either the controller product manual or in Appendix D & E of this Gateway product manual.
SNMP SNMP (simple network management protocol) is the most dominant network management standard. It allows communication and control via open standards host systems for centralized management of multiple plants. A number of vendors such as HP OpenView, IBM NetView, Lucent OneVision, and Sun Micro’s NetManager have adopted the standard for telecommunication and computer equipment network management.
SMTP SMTP (simple mail transfer protocol) provides a basic electronic email facility. It provides a mechanism for transferring messages among separate hosts and browser applications. The protocol is used in Gateway for sending alarm messages and alerts through email.
Issue 9 January 2008
10
Galaxy Gateway v3
FTP FTP (file transfer protocol) is used to send files from one system to another under user commands. The protocol is used with Gateway for downloading files and upgrades through a TCP connection to the user.
TL1 TL1 is the transaction language command interface defined by Telcordia for various equipment that allows direct communication with a central monitoring system. It allows communication and control via open standards host systems for centralized management of multiple plants. The protocol is typically used over a X.25 network for alarm reporting.
Product Features • Real time plant status and alarms • Remote configuration and control capability • Global access using Netscape or Microsoft Explorer • Centralized monitoring and control via SNMP • Centralized monitoring via TL1 • Access on demand - no dedicated lines required • Multi-user access to the site • Custom web pages • Alarm e-mail capability • Security and flexibility of TCP/IP • Maximum security with multiple-level passwords • Remote software upgrade of Galaxy Gateway and controller • Alarm paging service with SMTP • Free software updates from our web site
Issue 9 January 2008
11
Galaxy Gateway v3
Galaxy Gateway Circuit Pack The Galaxy Gateway is an optional circuit pack for the Galaxy SC, SCF, Vector, and Millennium controllers. This card provides the necessary interface for a 10Base-T Ethernet connection to the system controller.
Software Components The Galaxy Gateway has four software components: • Boot software – support for power on self test, factory test, local and remote upgrade of the other software components. • Application software – including an HTTP web server and Telnet daemon. • Default web pages – web pages supplied by Lineage Power. • Custom web pages – customer specific web pages developed by Lineage Power or an external supplier.
User Interfaces Web Pages (HTTP) It is assumed that the user has a web browser, such as Netscape Navigator or Internet Explorer, and is familiar with it. The user may access the Galaxy Gateway by its IP address, or host name (if supported) through the browser. The HTTP web pages server has the following main features: • Password protection for read/write privilege for Galaxy Gateway and Galaxy Controller access. Note: Further access restrictions can be implemented using the hardware security features of the Galaxy Controllers. Consult the appropriate controller manual. • Support for two sets of web pages: default and customized web pages, which may be upgraded through the network • An extension to the HTML language to support transparent monitoring/control of the Galaxy Controller • Timeout for connections that remain idle more than a user-programmed time period
Issue 9 January 2008
12
Galaxy Gateway v3
Default Web Pages are loaded into the system at the time of manufacture. They consist of the following pages: • Security checking (logging in) • Logging off • Error messages • Galaxy Gateway administration • Galaxy controller data access/configuration pages -View alarms and warnings -Power plant data including batteries, rectifiers, and converters -Remote peripheral monitoring channels -Automatic equipment inventory information -Configuration of passwords, alarm thresholds, etc. Custom Web Pages can be uploaded to the Galaxy Gateway using FTP. These customerspecific web pages provide a flexible solution for viewing and configuring the many attributes provided by the Galaxy Controller and Galaxy Gateway. Customers may update these web pages at any time.
Galaxy Gateway Local Port Using the RS-232 local port (J2), the user may log into the Galaxy Gateway, view/change network properties, and upgrade application software or web pages.
Telnet Telnet access provides the user with access into the Galaxy Gateway or the Galaxy Controller. Once login is established; the Galaxy Gateway will support this session until the “exit” command is received or the idle timeout limit is reached. A command line interface is used to view and configure the Galaxy Gateway’s internal configuration and to access the Galaxy Controller’s T1.317 command set. Backup, restore, and upgrade procedures may also be performed on the connected Galaxy Controller as well as Galaxy Gateway configuration changes.
FTP FTP is used only for upgrading Galaxy Gateway software. Application software and default and/or custom web pages can be uploaded to the Galaxy Gateway using FTP. Users can also retrieve (get) existing custom web pages from the Galaxy Gateway, make modifications, and copy (put) them back into the Galaxy Gateway.
Issue 9 January 2008
13
Galaxy Gateway v3
SNMP SNMP is used to provide centralized monitoring and control of the power system. Users can monitor system performance, receive alarm notifications, and configure the system via the SNMP interface.
TL1 TL1 is used to provide centralized monitoring and autonomous messaging.
Alarm Reporting Alarm reporting for the Galaxy Gateway consists of three main features: • PAGER – The user may specify up to three e-mail pager numbers where the alarm report can be sent. • E-MAIL – The user may specify up to three e-mail addresses where the alarm report can be sent. • PUSH – The user may specify up to three IP address alarm receiving hosts for automatic alarm capture. The host must have a capture application running at all times. Alarms may be reported based upon levels of severity. The user may elect to report no alarms, all alarms, major and critical only, or critical only. Alarm reports are generated when alarms occur and when they retire.
Issue 9 January 2008
14
Galaxy Gateway v3
3 Installation in a Galaxy SC Controller System Introduction This section describes the Galaxy Gateway installation and cabling procedures required for the BJD Gateway card installed into a Galaxy SC (J85501F1 L-1, 3, or 4) controller. Galaxy SC is a rear-access controller commonly mounted into a relay rack style power board bay per J85500A. Galaxy SC circuit packs, including the BJD Gateway, insert into specific slots of the controller cage from the front, and interface into a common controller backplane. Additional backplane interface connections are then completed onto backplane module assemblies, which attach to the controller cage rear. Refer to Figure 31 for a front view of the controller circuit pack slots with the front keypad / display open.
Preparation The following Network Configuration Parameters for Galaxy Gateway must be obtained from your Network Administrator before starting: • IP address • Subnet mask • Gateway (Router) IP address (Optional, but necessary if network access from outside of the router’s subnet is to be provided.) • Host name (Optional. Requires a DNS assignment by the Network Administrator.)
Precautions Note: Before starting, make sure proper ESD precautions are observed. The ESD grounding termination point located on the front portion of the controller’s hinged door can be used for providing a chassis ground potential. 1. On the LCD display panel, verify that no controller related (CTLR LED) alarms are active. If controller alarms are active, consult the SC controller product manual. 2. Open the controller’s front door and confirm that only the green status indicators are illuminated on the Basic and Intelligent circuit packs. Otherwise, consult the Galaxy SC Controller J85501F-1 Product Manual (Select Code 167-790-060) for troubleshooting help. 3. Verify that the intelligent controller optional side packs designated BJH and BJJ are present with green status indicators active. If missing, the intelligent controller
Issue 9 January 2008
15
Galaxy Gateway v3
option must be added to the Galaxy SC before proceeding with the Gateway installation. Verify that the Auxiliary Port Cable Interface module backplane connector is installed in the AUX PORT position on the rear of the Galaxy SC. If missing, it may be reordered as comcode 847370996 cable interface module.
Tools/Equipment Required Before installing and configuring the Galaxy Gateway, the following tools/equipment are required: • Flat jeweler’s screwdriver (Galaxy controller DIP switch setting) • PC with terminal emulation program (example: HyperTerminal) • 9 pin male serial interface cable (DB-9 male) to connect to Galaxy Gateway • Network interface cable (CAT 5 UTP)
Unpacking the Galaxy Gateway The 848520383 Galaxy Gateway Kit has been inspected, tested and carefully packed. Examine the shipping carton and all components for any sign of shipping damage. 1. Check for external damage to the shipping cartons. 2. Remove all parts from shipping cartons. 3. Verify that all components are present: Item 1 2
3
Quantity Description 1 BJD1 Galaxy Gateway circuit pack (107243826) 1 Network Communication Card Cable Interface Assembly Backplane Module (848441960) 1 Galaxy Controller interface cable (848520367)
If damage is found and/or components are missing, file a claim with the carrier if applicable, and notify Lineage Power Customer Service (See Section 1).
Issue 9 January 2008
16
Galaxy Gateway v3
Galaxy Controller Configuration Since the physical interface for the Galaxy controller to the Galaxy Gateway is through the auxiliary port on the controller, this port must be configured so that it will communicate with the Galaxy Gateway. This port may already be configured correctly. 1. On the BJH (Intelligent controller) board: a. Verify that SW203-1 (Position 1 on switch 203) is ENABLED. b. Verify that SW203-5 (Position 5 on switch 203) is ENABLED. 2. From the Front Panel Display, use the Path: Menu /Configuration/ Port. a. Verify that the AUX port is ENABLED for RD_WR (read/ write). This completes the configuration (or verification) required for the Galaxy controller.
Galaxy Gateway Installation Note: Remove power to the Intelligent controller side during the Galaxy Gateway installation. • Disengage the BJJ intelligent controller power board, but do not remove the board completely from the guides. Use the following procedures to install a new or replacement Galaxy Gateway.
Precautions • Always consider personal safety before beginning any procedure. • Be aware of the presence of battery potential in the vicinity of the controller. • Use only insulated tools. • Wear grounded antistatic wrist straps when handling all circuit packs. The wrist strap must be in contact with the skin and is not to be worn over clothing. • Never hand a circuit pack from a grounded to a non-grounded person or vice-versa.
Issue 9 January 2008
17
Galaxy Gateway v3
Figure 3-1: Galaxy Gateway Installation
Procedure 1. Locate the area on left side of the Galaxy Controller that is designated for Intelligent Option boards (see Figure 3-1). The front door is labeled OPT.2 BJ** - OPT.6 BJ**. Choose any available option slot and carefully slide the Galaxy Gateway into the slot using the top and bottom guides. Once the board is seated, lock into place by lifting the circuit pack locking lever to the full upright position. Then press on the front edge of the pack to insure that it is fully seated into its backplane slot. 2. On the rear of the Galaxy, locate the Intelligent Option port associated with the slot occupied by the Galaxy Gateway board, and connect the Network Communication Card Cable Interface Assembly (Backplane) Module.
Cable Connections Galaxy Gateway The Galaxy Gateway maintains RS232 communications with the AUX Port of the BJH Intelligent controller. To connect the Galaxy Gateway to the BJH Intelligent controller, follow this procedure (see Figure 3-2): 1. Locate the controller interface cable assembly (4 position connector on one end and a black/red pair of wires on the other end) that is provided in the kit (Comcode 848520367) 2. Identify the black, 4-position connector and connect this end to P1 of the Network Communications Card Cable Interface Assembly.
Issue 9 January 2008
18
Galaxy Gateway v3
3. Connect the red wire of the interface cable assembly to TB5-1 (Terminal Block 5, position 1) on the AUX. Port Cable Interface Assembly located on the back of the Galaxy controller. 4. Connect the black wire of the interface cable assembly to TB5-2 (Terminal Block 5, position 2) on the AUX. Port Cable Interface Assembly located on the back of the Galaxy controller.
Figure 3-2: Galaxy SC Backplane Connections Gateway/Aux Port Interface
Issue 9 January 2008
19
Galaxy Gateway v3
10Base-T Network The Galaxy Gateway has an IEEE 802.3 compliant 10Base-T network interface. Since the cable length required to connect the Galaxy Gateway to the network is variable, this cable must be supplied by the user. To connect the Galaxy Gateway to your network, follow this procedure: 1. Connect one end of the network interface cable to J2 (RJ-45 Network Interface Connector) located on the Gateway Network Communication Card Cable Interface. This is the backplane connector, located on the rear of the Galaxy controller. 2. Connect the other end to an IEEE 802.3 compatible network. Carefully slide the BJJ power board into the slot using the top and bottom guides. Once the board is seated, lock into place by lifting the circuit pack locking lever to the full upright position. Then press on the front edge of the pack to insure that it is fully seated into its backplane slot. EXCEPT FOR THE GATEWAY CARD, verify that after 30-45 seconds, all Green status LEDs on the controller circuit packs are lit, and that no Amber status LEDs are lit. The Gateway Card LEDs will be checked and verified after configuration is complete.
Configuring Network Communications The Galaxy Gateway uses Transmission Control Protocol/Internet Protocol (TCP/IP) to communicate with the host computer on a local area network. Each device or host on a TCP/IP network has its own IP address. The IP address is a 32-bit number, usually written in dot notation (e.g., 127.9.235.48). Another 32-bit number, called subnet mask (or address mask, netmask, e.g., 255.255.0.0) is used to identify the network portion and subnet portion of the IP address. A third 32-bit address, identified as the Default Gateway (router) IP address, is optional, but necessary if network access from outside of the router’s subnet is to be provided. Typically, this router address will be similar to the IP address assigned to the Gateway card, but will end with an octet of 1. A Host name is up to 15 text characters that may optionally be assigned to this specific IP and subnet within the network’s DNS server. Using the built-in configuration utility of Galaxy Gateway, program the required network configuration information. This information may have to be provided by the network administrator. The following equipment is required: •
PC with terminal emulation communications program
•
Serial interface cable (DB-9 Male) for connection to the Galaxy Gateway Serial interface cable, DB-9 Male for connection to the Galaxy Gateway, and typically DB-9 Female for connection to a PC serial port
Issue 9 January 2008
20
Galaxy Gateway v3
Logging In to the Galaxy Gateway To login to the Galaxy Gateway, follow these steps: 1. Start-up the PC communications terminal program (Windows HyperTerminal, ProComm, etc.) using the following communication parameters: Baud : 9600 Data : 8 Parity : none Stop : 1 Handshaking: none Flow Control: none 2. Connect the PC to the Galaxy Gateway card’s local port (RS-232) connector J2. 3. Press reset (SW1 – microprocessor reset) switch on the Galaxy Gateway card. 4. Wait for any diagnostic messages to pass and for the “ENTER PASSWORD:” command line prompt. 5.
Input the Network Administrator password (default: networkadm).
6.
Wait for the “$” prompt.
Configuring Static Network Parameters After a valid password entry, a login header with the following format will be displayed: Board Code Serial Number
BJD1 1:2 02DJ09112345
Boot Block Application Code Default Web Pages Custom Web Pages
version G.1.0 version G.3.18 version G.3.14 not found
Ethernet Address IP Address Subnet Mask Default Gateway Host Name
00-60-1D-00-5C-07 not configured not configured not configured not configured
For assistance type help $
Typing HELP at the “$” will show all available network administration commands and command line formats.
Issue 9 January 2008
21
Galaxy Gateway v3
*note: 1) commands are not case sensitive 2) for the commands that follow, ddd is a number from 0 – 255 • To set the IP Address, type: CHA NET1,IP=ddd.ddd.ddd.ddd Verify by typing: STA NET1,IP • To set the Subnet mask, type: CHA NET1,SUB=ddd.ddd.ddd.ddd Verify by typing: STA NET1,SUB • Optional: To set the Default Gateway Address, type: CHA NET1,GTWY=ddd.ddd.ddd.ddd Verify by typing: STA NET1,GTWY • Optional: To set the Host Name, type: CHA NET1,HOST=“hostname” Verify by typing: STA NET1,HOST
Logging Out of the Galaxy Gateway To terminate the configuration session, enter the “bye” command. The Galaxy Gateway will notify the user if configuration is not complete. This message will have the following format: NOTICE: Default gateway may be required for network access. Host Name may be required for network access. Logging off... Messages referencing the Gateway and Host Name are acceptable, since these parameters are optional. Note: If the IP address or Subnet mask messages appear, for example: IP Address is required for network access. Subnet mask is required for network access. then the configuration procedure must be repeated.
Issue 9 January 2008
22
Galaxy Gateway v3
Post Installation Procedures Once configuration has been completed 1. Disconnect the PC from the Galaxy Gateway card’s local port (RS-232) connector J2. 2. Press SW1 (microprocessor reset) on the Galaxy Gateway card. 3. After approximately one minute, observe the LEDs on the Galaxy Gateway: • • •
Yellow STATUS LED: Green STATUS LED: Link / Active LED:
OFF ON May be blinking
The Galaxy Gateway should be communicating over the network. 4. Secure the cables and close and secure the hinged door.
Troubleshooting Status and communication LEDs on the Gateway provide operation information as follows: •
With everything powered up, the green status LED should be active after boot-up. The amber status LED should be retired. The Link LED should be active or blinking.
•
If just the amber status LED is active, the BJD Gateway board is bad.
•
If the green status LED is active and the amber status LED is blinking, Gateway thinks the PC is still connected to the serial RS232 port of the Gateway or the network parameters have not been programmed correctly. Insure that a Gateway microprocessor reset has been completed after disconnecting the PC RS232 communication cable.
•
If both the green and amber status LEDs are active, the unit is still in the process of powering up, the Gateway cannot communicate with the controller, or the Gateway is not communicating with the network over the TCP/IP connection. The Link LED will be green, solid or blinking, whenever network communication is active. ─ If the Link LED is not active, verify the physical connections and the configured addresses used for the Gateway card and its router connection. A Network Administrator may have to “ping” the Gateway card’s address and otherwise assist with troubleshooting the network side of the Ethernet connection.
Issue 9 January 2008
23
Galaxy Gateway v3
─ If both the green and amber status LEDs are active, and the Link LED is green, solid or blinking, then the Gateway is unable to login to the Aux port of the controller. This could be due to a physical connection trouble or a password or Aux port configuration trouble. Physical – Verify the connection on the backplane between the Aux port module, TB5 and Network interface card, P1, shown in Figure 3-2. Verify that both interface cards are fully inserted onto their backplane jacks. Verify that the Network interface card is in the same option slot used by the BJD Gateway card. Verify that both the BJD Gateway and BJH Intelligent processor cards are fully seated into their appropriate controller slots. (Do NOT count on the circuit board latches to accomplish this.) Password – If all three controller passwords (user, super user, and administrator) have been changed from their default values (lineage, super-user, and administrator respectively) before Gateway is installed, Gateway will not be able to initially login following its microprocessor reset, and the amber status LED will remain active. When this happens, a web page access request may result in an error message referring to a missing “status.html” page. The easiest solution to this is to use the BJH Intelligent processor card Password Reset switch to restore just its administrator password back to its default value. Once this initial Gateway login is completed successfully, the Gateway’s amber status LED will retire, and a user can login to the controller over any of its ports and change the administrator password back to whatever value is desired. Once this is successful, it is advisable to have a user login to the controller over the Ethernet, using the lowest user security level password, so that Gateway has the opportunity to “learn” it. Regardless of any user’s login level, Gateway will always try to drop its security level to user status on the controller’s Aux port during idle periods, so that super-user or administrator security level rejections over the local or modem ports are minimized. When this does occur, the use of a “!” prefix onto the super-user or administrator password entry will permit access into the local or modem ports. This “!” password prefix can also be used for telnet sessions through Gateway, but is not accepted for HTTP web page access. Aux port Configuration – The Aux port of the controller must be set to its default parameters of Terminal mode (CHA AU1,APP="TERMINAL"), Auto baud (CHA AU1,BDR="AUTO"), 8 data bits (CHA AU1,DBT=8), no parity (CHA AU1,PRY="N"), 1 stop bit (CHA AU1,SBT=1), no handshaking (CHA AU1,HSH="NO"), and no timeout (CHA AU1,TMO=0). These T1.317 commands may be entered manually via terminal mode over the local or modem ports or through the following EasyView path:
Issue 9 January 2008
24
Galaxy Gateway v3
Configure Æ Ports Communications Æ Aux.
If a parameter is changed, follow this with a microprocessor reset on the Gateway card to establish communication with the intelligent controller card.
Issue 9 January 2008
25
Galaxy Gateway v3
4 Installation in a Galaxy SCF Controller System Introduction This section describes the Galaxy Gateway installation and cabling procedures required for the BJD Gateway card installed into a Galaxy SCF (J85501F1 L-2 or 5) controller. Galaxy SCF is a front-access controller previously used in GPS 4848 cabinets per H569434. Galaxy SCF circuit packs, including the BJD Gateway, insert into specific slots of the controller cage from the front, and interface into a common BLG controller front access card located directly above the main controller cage. Refer to Figure 4-1 for a front view of the controller circuit pack slots with the front keypad / display open.
Preparation The following Network Configuration Parameters for Galaxy Gateway must be obtained from your Network Administrator before starting: •
IP address
•
Subnet mask
•
Gateway (Router) IP address (Optional, but necessary if network access from outside of the router’s subnet is to be provided.)
•
Host name (Optional. Requires a DNS assignment by the Network Administrator.)
Precautions Note: Before starting, make sure proper ESD precautions are observed. The ESD grounding termination point located on the front portion of the controller’s hinged door can be used for providing a chassis ground potential. 1. On the LCD display panel, verify that no controller related (CTLR LED) alarms are active. If controller alarms are active, consult the controller product manual. 2. Open the controller’s front door and confirm that only the green status indicators are illuminated on the Basic and Intelligent circuit packs. Otherwise, consult the Galaxy SCF Controller J85501F-1 Product Manual (Select Code 167-792-110) for troubleshooting help.
Issue 9 January 2008
26
Galaxy Gateway v3
3. Verify that the intelligent controller optional side packs designated BJH and BJJ are present with green status indicators active. If missing, the intelligent controller option must be added to the Galaxy SCF before proceeding with the Gateway installation.
Tools/Equipment Required Before installing and configuring the Galaxy Gateway, the following tools/equipment are required: •
Flat jeweler’s screwdriver (Galaxy controller DIP switch setting)
•
Small Phillips head screwdriver (controller service panel removal)
•
PC with terminal emulation program (example: HyperTerminal)
•
9 pin male serial interface cable (DB-9 male) to connect to Galaxy Gateway
•
Network interface cable (CAT 5 UTP)
Unpacking the Galaxy Gateway The 848520391 Galaxy Gateway has been inspected, tested and carefully packed. Examine the shipping carton and all components for any sign of shipping damage. 1. Check for external damage to the shipping cartons. 2. Remove all parts from shipping cartons. 3. Verify that all components are present: Item 1
Quantity 1
2
1
Description BJD1 Galaxy Gateway circuit pack (107243826) Network Interface Cable Adapter (848520375 – RJ45/4-wire)
Note: Two 20-22 AWG wires (10") must be supplied by the user. These wires will connect the auxiliary port of the intelligent controller to the Galaxy Gateway. If damage is found and/or components are missing, file a claim with the carrier if applicable, and notify Lineage Power Customer Service (See Section 1).
Issue 9 January 2008
27
Galaxy Gateway v3
Galaxy Controller Configuration Since the serial interface for the Galaxy Intelligent controller to the Galaxy Gateway is through the auxiliary port on the controller, this port must be configured so that it will communicate with the Galaxy Gateway. This port may already be configured correctly. 1. On the BJH (Intelligent controller) board: a. Verify that SW203-1 (Position 1 on switch 203) is ENABLED. b. Verify that SW203-5 (Position 5 on switch 203) is ENABLED. 2. From the Front Panel Display, use the Path: Menu /Configuration/ Port. a. Verify that the AUX port is ENABLED for RD_WR (read/ write). This completes the configuration (or verification) required for the Galaxy controller.
Galaxy Gateway Installation Note: Remove power to the Intelligent controller side during the Galaxy Gateway installation. •
Disengage the BJJ intelligent controller Power board, but do not remove the board completely from the guides.
Use the following procedures to install a new or replacement Galaxy Gateway.
Precautions •
Always consider personal safety before beginning any procedure.
•
Be aware of the presence of battery potential in the vicinity of the controller.
•
Use only insulated tools.
•
Wear grounded antistatic wrist straps when handling all circuit packs. The wrist strap must be in contact with the skin and is not to be worn over clothing.
•
Never hand a circuit pack from a grounded to a non-grounded person or viceversa.
Issue 9 January 2008
28
Galaxy Gateway v3
Figure 4-1: Galaxy Gateway Installation
Procedure 1. Locate the area on left side of the Galaxy Controller that is designated for Intelligent Option boards (see Figure 4-1). The front door is labeled OPT.2 BJ** OPT.6 BJ**. Important! The Galaxy Gateway MUST be inserted into Options Slot 5. 2. Carefully slide the Galaxy Gateway into Options Slot 5, using the top and bottom guides. Once the board is seated, lock into place by lifting the circuit pack locking lever to the full upright position. Then press on the front edge of the pack to insure that it is fully seated into its backplane slot.
Cable Connections Galaxy Gateway The Galaxy Gateway maintains RS232 communications with the AUX Port of the BJH Intelligent controller. To connect the Galaxy Gateway to the BJH Intelligent controller, follow this procedure (see Figure 4-2): These connections are on the BLG board. 1. Using the two 20-22 AWG wires (provided by the user), strip both ends of each wire (0.25") and connect 1 wire from TB11-1 (Terminal Block 11, position 1). This is the leftmost position of the terminal block when facing controller from the
Issue 9 January 2008
29
Galaxy Gateway v3
front) to TB5-2 (Terminal block 5, position 2 on the AUX port connector, also labeled RXD). 2. Connect the other wire from TB11-2 (Terminal Block 11, position 2). This is the second position from the left of the terminal block when facing controller from the front) to TB5-1 ( Terminal block 5, position 1 on the AUX port connector, also labeled TXD). Note: When dressing the wires, route them so that they do not touch the Termination Resistors, used for Remote Monitoring Bus 2 and 3.
Figure 4-2: Galaxy SCF Connections Gateway/Aux Port Interface
10Base-T Network The Galaxy Gateway has an IEEE 802.3 compliant 10Base-T network interface. Since the cable length required to connect the Galaxy Gateway to the network is variable, this cable must be supplied by the user. To connect the Galaxy Gateway to your network, see Figure 4-2 and follow this procedure: 1. Using the supplied Network cable assembly, connect the following wires to TB12 on the Galaxy SCF’s BLG board:
Issue 9 January 2008
30
Galaxy Gateway v3
Wire Color
Orange Orange/White Green Green/White
TB12 Position (1 is leftmost position, facing the BLG board from the front) 1 2 3 4
2. Connect the other end to a 10Base-T compatible network. Carefully slide the BJJ power board into the slot using the top and bottom guides. Once the board is seated, lock into place by lifting the circuit pack locking lever to the full upright position. Then press on the front edge of the pack to insure that it is fully seated into its backplane slot. EXCEPT FOR THE GATEWAY CARD, verify that after 30-45 seconds, all Green status LEDs on the controller circuit packs are lit, and that no Amber status LEDs are lit. The Gateway Card LEDs will be checked and verified after configuration is complete.
Configuring Network Communications The Galaxy Gateway uses Transmission Control Protocol/Internet Protocol (TCP/IP) to communicate with the host computer on a local area network. TCP/IP is a widely used protocol that provides communication across networks of diverse computers and devices. This protocol forms the basis for the Internet. Each device or host on a TCP/IP network has its own IP address. The IP address is a 32-bit number, usually written in dot notation (e.g., 127.9.235.48). Another 32-bit number, called subnet mask (or address mask, netmask, e.g., 255.255.0.0) is used to identify the network portion and subnet portion of the IP address. A third 32-bit address, identified as the Default Gateway (router) IP address, is optional, but necessary if network access from outside of the router’s subnet is to be provided. Typically, this router address will be similar to the IP address assigned to the Gateway card, but will end with an octet of 1. A Host name is up to 15 text characters that may optionally be assigned to this specific IP and subnet within the network’s DNS server.
Logging In to the Galaxy Gateway Using the built-in configuration utility of Galaxy Gateway, program the required network configuration information. This information may have to be provided by the network administrator. The following equipment is required: •
PC with terminal emulation communications program
Issue 9 January 2008
31
Galaxy Gateway v3
•
Serial interface cable, DB-9 Male for connection to the Galaxy Gateway, and typically DB-9 Female for connection to a PC serial port (DB-9 Male) for connection to the Galaxy Gateway
To login to the Galaxy Gateway, follow these steps: 1. Start-up the PC terminal program (Windows Terminal, ProComm, etc.) using the following communication parameters: Baud Data Parity Stop Handshaking Flow Control
: 9600 :8 : none :1 : none : none
2. Connect the PC to the Galaxy Gateway card’s local port (RS-232) connector J2. 3. Press reset (SW1 – microprocessor reset) switch on the Galaxy Gateway card. 4. Wait for any diagnostic messages to pass and for the “ENTER PASSWORD:” command line prompt. 5. Input the Network Administrator password (default: networkadm). 6. Wait for the “$” prompt.
Configuring Static Network Parameters After a valid password entry, a login header with the following format will be displayed: Board Code Serial Number
BJD1 1:2 02DJ09112345
Boot Block Application Code Default Web Pages Custom Web Pages
version G.1.0 version G.3.18 version G.3.14 not found
Ethernet Address IP Address Subnet Mask Default Gateway Host Name
00-60-1D-00-5C-07 not configured not configured not configured not configured
For assistance type help $
Issue 9 January 2008
32
Galaxy Gateway v3
Typing HELP at the “$” will show all available network administration commands and command line formats. *note: 1) commands are not case sensitive 2) for the commands that follow, ddd is a number from 0 – 255 •
To set the IP Address, type: CHA NET1,IP=ddd.ddd.ddd.ddd Verify by typing: STA NET1,IP
•
To set the Subnet mask, type: CHA NET1,SUB=ddd.ddd.ddd.ddd Verify by typing: STA NET1,SUB
•
Optional: To set the Default Gateway Address, type: CHA NET1,GTWY=ddd.ddd.ddd.ddd Verify by typing: STA NET1,GTWY
•
Optional: To set the Host Name, type: CHA NET1,HOST=”host name” Verify by typing: STA NET1,HOST
Logging Out of the Galaxy Gateway To terminate the configuration session, enter the “bye” command. The Galaxy Gateway will notify the user if configuration is not complete. This message will have the following format: NOTICE: Default gateway may be required for network access. Host Name may be required for network access. Logging off... Messages referencing the Gateway and Host Name are acceptable, since these parameters are optional. Note: If the IP address or Subnet mask messages appear, for example: IP Address is required for network access. Subnet mask is required for network access.
Issue 9 January 2008
33
Galaxy Gateway v3
then the configuration procedure must be repeated.
Post Installation Procedures Once configuration has been completed 1. Disconnect the PC from the Galaxy Gateway card’s local port (RS-232) connector J2. 2. Press SW1 (microprocessor reset) on the Galaxy Gateway card. 3. After approximately one minute, observe the LEDs on the Galaxy Gateway: Yellow STATUS LED: Green STATUS LED: Link / Active LED:
OFF ON May be blinking
The Galaxy Gateway should be communicating over the network. 4. Secure the cables and close and secure the hinged door.
Troubleshooting Status and communication LEDs on the Gateway provide operation information as follows: •
With everything powered up, the green status LED should be active after boot-up. The amber status LED should be retired. The Link LED should be active or blinking.
•
If just the amber status LED is active, the BJD Gateway board is bad.
•
If the green status LED is active and the amber status LED is blinking, Gateway thinks the PC is still connected to the serial RS232 port of the Gateway or the network parameters have not been programmed correctly. Insure that a Gateway microprocessor reset has been completed after disconnecting the PC RS232 communication cable.
•
If both the green and amber status LEDs are active, the unit is still in the process of powering up, the Gateway cannot communicate with the controller, or the Gateway is not communicating with the network over the TCP/IP connection. The Link LED will be green, solid or blinking, whenever network communication is active. ─ If the Link LED is not active, verify the physical connections at the BLG front access card, TB12 and the configured addresses used for the Gateway card and its
Issue 9 January 2008
34
Galaxy Gateway v3
router connection. A Network Administrator may have to “ping” the Gateway card’s address and otherwise assist with troubleshooting the network side of the Ethernet connection. ─ If both the green and amber status LEDs are active, and the Link LED is green, solid or blinking, then the Gateway is unable to login to the Aux port of the controller. This could be due to a physical connection trouble or a password or Aux port configuration trouble. Physical – Verify the connections on the BLG front access board between the Aux port, TB5 and Network interface, TB11, shown in Figure 4-2. Verify that the BJD Gateway card is installed only in option slot 5. Verify that both the BJD Gateway and BJH Intelligent processor cards are fully seated into their appropriate controller slots. (Do NOT count on the circuit board latches to accomplish this.) Password – If all three controller passwords (user, super user, and administrator) have been changed from their default values (lineage, super-user, and administrator respectively) before Gateway is installed, Gateway will not be able to initially login following its microprocessor reset, and the amber status LED will remain active. When this happens, a web page access request may result in an error message referring to a missing “status.html” page. The easiest solution to this is to use the BJH Intelligent processor card Password Reset switch to restore just its administrator password back to its default value. Once this initial Gateway login is completed successfully, the Gateway’s amber status LED will retire, and a user can login to the controller over any of its ports and change the administrator password back to whatever value is desired. Once this is successful, it is advisable to have a user login to the controller over the Ethernet, using the lowest user security level password, so that Gateway has the opportunity to “learn” it. Regardless of any user’s login level, Gateway will always try to drop its security level to user status on the controller’s Aux port during idle periods, so that super-user or administrator security level rejections over the local or modem ports are minimized. When this does occur, the use of a “!” prefix onto the super-user or administrator password entry will permit access into the local or modem ports. This “!” password prefix can also be used for telnet sessions through Gateway, but is not accepted for HTTP web page access. Aux port Configuration – The Aux port of the controller must be set to its default parameters of Terminal mode (CHA AU1,APP="TERMINAL"), Auto baud (CHA AU1,BDR="AUTO"), 8 data bits (CHA AU1,DBT=8), no parity (CHA AU1,PRY="N"), 1 stop bit (CHA AU1,SBT=1), no handshaking (CHA AU1,HSH="NO"), and no timeout (CHA AU1,TMO=0). These T1.317 commands may be entered manually via terminal mode over the local or modem ports or through the following EasyView path:
Issue 9 January 2008
35
Galaxy Gateway v3
Configure Æ Ports Communications Æ Aux.
If a parameter is changed, follow this with a microprocessor reset on the Gateway card to establish communication with the intelligent controller card.
Issue 9 January 2008
36
Galaxy Gateway v3
5 Installation in a GPS with a Millennium Controller Introduction This section describes the Galaxy Gateway installation and cabling procedures required for the EBW Gateway card installed into a Galaxy Power System (GPS) cabinet equipped with a Galaxy Millennium (J85501K1 L-1, 2, 3, or 4) controller. The Millennium controller mounts on the door of the initial GPS cabinet in these systems and the EBW Gateway card is installed on the inside of the same cabinet door along with it. The EBW Gateway mounts in one of three positions with the Millennium controller, depending on the door type and whether a BSM modem is also equipped: •
Figure 5-2 shows the Gateway in its most common configuration, mounted on the inside of the J85501K1 L-1 or 2 Millennium chassis door, used in a GPS cabinet with a metal door.
•
Figure 5-1A shows the Gateway mounted just above the J85501K1 L-1 or 2 Millennium chassis in a GPS cabinet with a metal door. This location is used whenever a BSM modem card occupies the space shown for the Gateway inside the Millennium chassis door in Figure 5-2.
•
Figure 5-1B and Figure 5-3 show the Gateway mounting under the cover, just above the J85501K1 L-3 or 4 Millennium, on the inside of a GPS cabinet with a plastic door.
Figure 5-1A: GPS with Metal Door and J85501K-1 List 1 or 2 Controller
Issue 9 January 2008
37
Galaxy Gateway v3
Figure 5-1B: GPS with Plastic Door and J85501K-1 List 3 or 4 Controller
Preparation The following Network Configuration Parameters for Galaxy Gateway must be obtained from your Network Administrator before starting: • IP address • Subnet mask • Gateway (Router) IP address (Optional, but necessary if network access from outside of the router’s subnet is to be provided.)Gateway IP address • Host name (Optional. Requires a DNS assignment by the Network Administrator.)
Precautions Note: Before starting, make sure proper ESD precautions are observed. The ESD grounding termination point is located on either the door latch bracket of the GPS cabinet or on the hinged door of the controller's metal chassis.
Issue 9 January 2008
38
Galaxy Gateway v3
• Wear grounded antistatic wrist straps when handling all circuit packs. The wrist strap must be in contact with the skin and is not to be worn over clothing. • Always consider personal safety. Be aware of the presence of battery potential in the vicinity of the controller. • Use only insulated tools. • Verify that no controller related alarms are active on the LCD display panel (CTLR LED). If alarm is active, consult the controller product manual for troubleshooting help. •
For controller in a metal chassis as in Figure 5-1A, open the hinged door and remove the service cover (two Phillips head screws on the bottom). For controller mounted on a plastic door as in Figure 5-1B, remove the plastic access cover. Confirm that only the green status indicators are illuminated on the Basic (BSH) and Intelligent (BSJ) circuit packs. Otherwise, consult the controller product manual for troubleshooting help.
•
Verify that the BSJ intelligent controller pack (outer of two circuit packs) is present with only its green status indicator active. If missing, the intelligent controller option must be added to the Galaxy Millennium before proceeding with the Gateway installation.
Tools/Equipment Required Before installing and configuring the Galaxy Gateway, the following tools/equipment are required: •
Flat jeweler’s screwdriver (controller DIP switch setting)
•
Small Phillips head screwdriver
•
Nut driver for 6-32 nut
•
PC with terminal emulation program (example: HyperTerminal)
•
9 pin male serial interface cable (DB-9 male) to connect to the Galaxy Gateway
•
Network interface cable (CAT 5 UTP)
Issue 9 January 2008
39
Galaxy Gateway v3
Unpacking the Galaxy Gateway The 108876400 Galaxy Gateway Kit has been inspected, tested and carefully packed. Examine the shipping carton and all components for any sign of shipping damage. 1. Check for external damage to the shipping cartons. 2. Remove all parts from shipping cartons. 3. Verify that all the following components are present. Item
Qty
Comcode
Description
1
1
108340100 Galaxy Gateway circuit pack
2
1
848281945 Black insulator
3
1
848364865 Millennium Controller interface cable
4
2
408456465 Nylon mounting posts (HMSP-TM-10)
5
1
402244081 Cable tie
6
2
407882141 Metal standoff (9740-SS-0632)
7
2
845143866 Screw, PPHM 6-32 x 5/16"
8
1
848589859 Black insulator
9
1
848575841 Vector Controller interface cable (not used)
10
4
408450955 Metal standoff (AL-5171-16)
11
8
901377366 Screw, PPHM M3 x 6mm
12
4
901351239 Nut, hex 6-32
13
1
848649943 Mounting bracket
If damage is found and/or components are missing, file a claim with the carrier if applicable, and notify Lineage Power Customer Service (See Section 1).
Millennium Controller Configuration Since the physical interface for the Millennium Controller to the Galaxy Gateway is through the auxiliary port (P203) on the controller, this port must be configured so that it will communicate with the Galaxy Gateway. This port may already be configured correctly. 1. On the BSJ (Intelligent controller) board: a. Verify that SW203-1 (Position 1 on switch 203) is ENABLED. b. Verify that SW203-5 (Position 5 on switch 203) is ENABLED.
Issue 9 January 2008
40
Galaxy Gateway v3
2. From the front panel display, use the Path: Menu /Configuration/Port. Verify that the AUX port is ENABLED for RD_WR (read/write). Note: It is not necessary to remove power to the controller during the Galaxy Gateway installation. However, if there is some uncertainty during this operation and added precaution is desired, power may be removed from the Intelligent controller board. This can be accomplished in one of two ways: • Disconnect the power cable at P202 on the BSJ intelligent controller board. OR • Remove fuses 1 and 2 (Option and Intelligent board power fuses, respectively), the two left-most fuses in the fuse block located at the top left corner of the BSH Basic controller board.
Galaxy Gateway Installation Installing Gateway in Millennium Chassis Use the following procedure and Figure 5-2 to install the EBW Galaxy Gateway onto a J85501K-1 List 1 or 2 Millennium chassis door, mounted on a GPS metal door, when there is no BSM modem in this location.
Figure 5-2: Galaxy Gateway on J85501K-1 List 1 or 2 Millennium Controller
Issue 9 January 2008
41
Galaxy Gateway v3
1. Remove the fuse puller located at the top of the hinged door on the controller. 2. Locate the four mounting standoffs on the hinged door of the controller. 3. Position the Galaxy Gateway over the mounting standoffs so that J1 (RJ-45 network interface connector) and J2 (DB-9 serial port connector) are located at the top of the hinged door. The component side of the circuit pack should be facing outward. 4. Install two 408456465 nylon mounting posts to the lower mounting standoffs (torque to 3 in·lbs). 5. Install two 407882141 metal standoffs to the upper mounting standoffs (torque to 10 in-lbs). 6. Align holes of 848281945 black insulator with nylon posts and snap onto the nylon posts. Using two 845143866 screws, secure top of insulator to metal standoffs (torque to 10 in·lbs). Note: Exercise caution when placing the insulator onto the board so that contact between components and hands are minimal.
Installing Gateway on a GPS Metal Door When a modem card is already mounted on the hinged door of the controller, the Galaxy Gateway can be attached directly to the metal door of the GPS cabinet as shown in Figure 5-1A. 1. Install 848649943 bracket onto four studs on metal door and secure with 901351239 hex nuts (6-32). 2. Place 848589859 black insulator under the Galaxy Gateway and position over the mounting standoffs so that J1 (RJ-45 network interface connector) and J2 (DB-9 serial port connector) are facing down. The component side of the circuit pack should be facing outward. 3. Install two 408456465 nylon mounting posts to the lower mounting standoffs (torque to 3 in·lbs). 4. Install two 407882141 metal standoffs to the upper mounting standoffs (torque to 10 in·lbs). 5. Wrap insulator around the Gateway board and snap onto nylon posts. Using two 845143866 screws, secure top of insulator to metal standoffs (torque to 10 in·lbs).
Issue 9 January 2008
42
Galaxy Gateway v3
Installing Gateway on a GPS Plastic Door Use the following procedure and Figure 5-3 to install the EBW Galaxy Gateway onto a GPS plastic door with a J85501K-1 List 3 or 4 Millennium as in Figure 5-1B.
Figure 5-3: Galaxy Gateway on GPS Plastic Door 1. Place 848589859 black insulator under the Galaxy Gateway and position over the mounting standoffs on plastic door so that J1 (RJ-45 network interface connector) and J2 (DB-9 serial port connector) are facing down. The component side of the circuit pack should be facing outward. 2. Install four 408450955 metal standoffs (AL-5171-16) (torque to 10 in·lbs). 3. Wrap insulator around the Gateway board and secure to metal standoffs using four 901377366 screws, PPHM M3 x 6mm (torque to 10 in·lbs).
Issue 9 January 2008
43
Galaxy Gateway v3
Galaxy Gateway Cable Connections Gateway to Controller The Galaxy Gateway receives power and communications from the BSJ Intelligent control board. Use the following procedure and Figure 5-4A or Figure 5-4B to connect the Galaxy Gateway to the Millennium Controller. 1. Locate 848364865 controller interface cable provided in the kit. 2. Identify the end with a black, 12 position connector. Connect this end to P203 auxiliary port connector on the BSJ Intelligent control board. 3. Connect the black 4-position connector of the cable to the P1 power connector on the Galaxy Gateway. Power will be applied to the Galaxy Gateway when this cable is plugged into P1. The DB-9 male (9 pin) connector will not be connected until after the Gateway is configured. 4. After the connection to P1, wait approximately 45 seconds. The Yellow status LED should blink, indicating that the Gateway is ready to be configured.
Figure 5-4A: Connection to BSJ Intelligent Controller in Millennium Chassis
Issue 9 January 2008
44
Galaxy Gateway v3
Figure 5-4B: Connection to BSJ Intelligent Controller on GPS Plastic Door
10Base-T Network The Galaxy Gateway has an IEEE 802.3 compliant 10Base-T network interface. Since the cable length required to connect the Galaxy Gateway to the network is variable, this cable must be supplied by the user. Connect the network interface cable from the IEEE 802.3 compatible network to J1 (RJ-45) connector on the Galaxy Gateway as shown in Figure 5-5A or Figure 5-5B. 1. Connect one end of the network interface cable to J1 (RJ-45 Network Interface Connector) located at the top left on the Galaxy Gateway. 2. Route the network interface cable through the hole above the P6 connector on the controller housing. 3. Connect the other end to an IEEE 802.3 compatible network.
Issue 9 January 2008
45
Galaxy Gateway v3
Figure 5-5A: Network Connection to Gateway in Millennium Chassis
Figure 5-5B: Network Connection to Gateway on GPS Plastic Door
Issue 9 January 2008
46
Galaxy Gateway v3
Configuring Network Communications The Galaxy Gateway uses Transmission Control Protocol/Internet Protocol (TCP/IP) to communicate with the host computer on a local area network. TCP/IP is a widely used protocol that provides communication across networks of diverse computers and devices. This protocol forms the basis for the Internet. Each device or host on a TCP/IP network has its own IP address. The IP address is a 32-bit number, usually written in dot notation (e.g., 127.9.235.48). Another 32-bit number, called subnet mask (or address mask, netmask, e.g., 255.255.0.0) is used to identify the network portion and subnet portion of the IP address. A third 32-bit address, identified as the Default Gateway (router) IP address, is optional, but necessary if network access from outside of the router’s subnet is to be provided. Typically, this router address will be similar to the IP address assigned to the Gateway card, but will end with an octet of 1. A Host name is up to 15 text characters that may optionally be assigned to this specific IP and subnet within the network’s DNS server.
Logging In to the Galaxy Gateway Using the built-in configuration utility of Galaxy Gateway, program the required network configuration information. This information may have to be provided by the network administrator. The following equipment is required: •
PC with terminal emulation communications program
•
Serial interface cable, DB-9 Male for connection to the Galaxy Gateway, and typically DB-9 Female for connection to a PC serial port
To login to the Galaxy Gateway, follow these steps: 1. Start-up the PC communications terminal program (Windows HyperTerminal, ProComm, etc.) using the following communication parameters: Baud : 9600 Data : 8 Parity : none Stop : 1 Handshaking: none Flow Control: none 2. Connect the PC to the Galaxy Gateway card’s local port (RS-232) connector J2. 3. Press reset (SW1 – microprocessor reset) switch on the Galaxy Gateway card. 4. Wait for any diagnostic messages to pass and for the “ENTER PASSWORD:” command line prompt.
Issue 9 January 2008
47
Galaxy Gateway v3
5. Input the Network Administrator password (default: networkadm). 6.
Wait for the “$” prompt.
Configuring Static Network Parameters After a valid password entry, a login header with the following format will be displayed: Board Code Serial Number
EBW1 1:3 02DJ09112345
Boot Block Application Code Default Web Pages Custom Web Pages
version G.1.0 version G.3.18 version G.3.14 not found
Ethernet Address IP Address Subnet Mask Default Gateway Host Name
00-60-1D-00-5C-07 not configured not configured not configured not configured
For assistance type help $
Typing HELP at the “$” will show all available network administration commands and command line formats. *note: 1) commands are not case sensitive 2) for the commands that follow, ddd is a number from 0 – 255 •
To set the IP Address, type: CHA NET1,IP=ddd.ddd.ddd.ddd Verify by typing: STA NET1,IP
•
To set the Subnet mask, type: CHA NET1,SUB=ddd.ddd.ddd.ddd Verify by typing: STA NET1,SUB
•
Optional: To set the Default Gateway Address, type: CHA NET1,GTWY=ddd.ddd.ddd.ddd Verify by typing: STA NET1,GTWY
•
Optional:
Issue 9 January 2008
48
Galaxy Gateway v3
To set the Host Name, type: CHA NET1,HOST=”host name” Verify by typing: STA NET1,HOST
Logging Out of the Galaxy Gateway To terminate the configuration session, enter the “bye” command. The Galaxy Gateway will notify the user if configuration is not complete. This message will have the following format: NOTICE: Default gateway may be required for network access. Host Name may be required for network access. Logging off... Messages referencing the Gateway and Host Name are acceptable, since these parameters are optional. Note: If the IP address or Subnet mask messages shown below appear, the configuration procedure must be repeated. IP Address is required for network access. Subnet mask is required for network access.
Post Installation Procedures Once configuration has been completed 1. Disconnect the serial cable from the Galaxy Gateway (J2 connector). 2. Connect the 9-pin male end of the auxiliary port cable assembly to the J2 connector on the Galaxy Gateway. 3. Press SW1 (microprocessor reset) on the Galaxy Gateway. 4. After approximately one minute, observe the LEDs on the Galaxy Gateway. • • • •
Yellow STATUS LED: Green STATUS LED: Link LED: XMIT/RCV:
OFF ON ON May be blinking
The Galaxy Gateway should be communicating over the network.
Issue 9 January 2008
49
Galaxy Gateway v3
5. Secure the cable using the cable tie provided. For controller in a metal chassis as in Figure 5-1A, replace fuse puller, reinstall service cover (two Phillips head screws on the bottom), and close hinged door. For controller mounted on a plastic door as in Figure 5-1B, reinstall the plastic access cover.
Troubleshooting Status and communication LEDs on the Gateway provide operation information as follows: •
With everything powered up, the green status LED should be active after boot-up. The amber status LED should be retired. The Link, TX, and RX LEDs should be active or blinking.
•
If just the amber status LED is active, the EBW Gateway board is bad.
•
If the green status LED is active and the amber status LED is blinking, Gateway thinks the PC is still connected to the serial RS232 port of the Gateway or the network parameters have not been programmed correctly. Insure that a Gateway microprocessor reset has been completed after disconnecting the PC RS232 communication cable and plugging back in the 9-pin connector of the Aux port cable set.
•
If both the green and amber status LEDs are active, the unit is still in the process of powering up, the Gateway cannot communicate with the controller, or the Gateway is not communicating with the network over the TCP/IP connection. The Link, TX, and RX LEDs will be green, solid or blinking, whenever network communication is active. ─ If the Link LED is not active, verify the physical connections and the configured addresses used for the Gateway card and its router connection. A Network Administrator may have to “ping” the Gateway card’s address and otherwise assist with troubleshooting the network side of the Ethernet connection. ─ If both the green and amber status LEDs are active, and the Link LED is green, solid or blinking, then the Gateway is unable to login to the Aux port of the controller. This could be due to a physical connection trouble or a password or Aux port configuration trouble.
Physical – Verify the connections for the 9-pin connector of the Aux port cable set at both the EBW Gateway end and the BSJ intelligent controller card P203 end. Verify that the BSJ intelligent card is powered up and functional. Time and Date should be displayed on the top row of the main screen of the Millennium if this card is functional.
Issue 9 January 2008
50
Galaxy Gateway v3
Password – If all three controller passwords (user, super user, and administrator) have been changed from their default values (lineage, super-user, and administrator respectively) before Gateway is installed, Gateway will not be able to initially login following its microprocessor reset, and the amber status LED will remain active. When this happens, a web page access request may result in an error message referring to a missing “status.html” page. The easiest solution to this is to use the BSJ Intelligent processor card Password Reset switch to restore just its administrator password back to its default value. Once this initial Gateway login is completed successfully, the Gateway’s amber status LED will retire, and a user can login to the controller over any of its ports and change the administrator password back to whatever value is desired. Once this is successful, it is advisable to have a user login to the controller over the Ethernet, using the lowest user security level password, so that Gateway has the opportunity to “learn” it. Regardless of any user’s login level, Gateway will always try to drop its security level to user status on the controller’s Aux port during idle periods, so that super-user or administrator security level rejections over the local or modem ports are minimized. When this does occur, the use of a “!” prefix onto the super-user or administrator password entry will permit access into the local or modem ports. This “!” password prefix can also be used for telnet sessions through Gateway, but is not accepted for HTTP web page access. Aux port Configuration – The Aux port of the controller must be set to its default parameters of Terminal mode (CHA AU1,APP="TERMINAL"), Auto baud (CHA AU1,BDR="AUTO"), 8 data bits (CHA AU1,DBT=8), no parity (CHA AU1,PRY="N"), 1 stop bit (CHA AU1,SBT=1), no handshaking (CHA AU1,HSH="NO"), and no timeout (CHA AU1,TMO=0). These T1.317 commands may be entered manually via terminal mode over the local or modem ports or through the following EasyView path: Configure Æ Ports Communications Æ Aux.
If a parameter is changed, follow this with a microprocessor Reset on the Gateway card to establish communication with the intelligent controller card.
Issue 9 January 2008
51
Galaxy Gateway v3
6 Installation in a GPS with a Vector Controller Introduction This section describes the Galaxy Gateway installation and cabling procedures required for the EBW Gateway card installed into a Galaxy Power System (GPS) cabinet equipped with a Galaxy Vector (BIC2, BIC3, GCM2, or GCM3) controller. The Vector controller mounts on the door of the initial GPS cabinet in these systems and the EBW Gateway card is installed on the inside of the same cabinet door along with it. Figures 6-1A and 61B show the Galaxy Gateway installation for use on metal and plastic GPC cabinet doors respectively. .
Figure 6-1A: GPS with Metal Door and Vector Controller
Issue 9 January 2008
52
Galaxy Gateway v3
Figure 6-1B: GPS with Plastic Door and Vector Controller
Preparation The following Network Configuration Parameters must be obtained from your Network Administrator before starting: •
IP address
•
Subnet mask
•
Host name
•
Gateway IP address
Note: Host and Gateway are optional.
Precautions Note: Before starting, make sure proper ESD precautions are observed. The ESD grounding termination point is located on the door latch bracket of the GPS cabinet. •
Wear grounded antistatic wrist straps when handling all circuit packs. The wrist strap must be in contact with the skin and is not to be worn over clothing.
Issue 9 January 2008
53
Galaxy Gateway v3
•
Always consider personal safety. Be aware of the presence of battery potential in the vicinity of the controller.
•
Use only insulated tools.
Verify that no controller related alarms are active on the LCD display panel. If controller alarm is active, consult the “Galaxy Vector Controller ACP-BIC2, BIC3” or the “Galaxy Vector Controller GCM2, GCM3” product manual for troubleshooting help.
Tools/Equipment Required Before installing and configuring the Galaxy Gateway, the following tools/equipment are required: •
Flat jeweler’s screwdriver (controller DIP switch setting)
•
Small Phillips head screwdriver
•
Nut driver for 6-32 nut
•
PC with terminal emulation program (example: HyperTerminal)
•
9 pin male serial interface cable (DB-9 male) to connect to Galaxy Gateway
•
Network interface cable (CAT 5 UTP)
Unpacking the Galaxy Gateway The 108876400 Galaxy Gateway Kit has been inspected, tested and carefully packed. Examine the shipping carton and all components for any sign of shipping damage. 1. Check for external damage to the shipping cartons. 2. Remove all parts from shipping cartons. 3. Verify that all components are present. Item
Qty
Comcode
1
1
108340100
Galaxy Gateway circuit pack
2
1
848281945
Black insulator (not used)
3
1
848364865
Millennium Controller interface cable (not used)
4
2
408456465
Nylon mounting posts (HMSP-TM-10)
5
1
402244081
Cable tie
6
2
407882141
Metal standoff (9740-SS-0632)
Issue 9 January 2008
Description
54
Galaxy Gateway v3
Item
Qty
Comcode
Description
7
2
845143866
Screw, PPHM 6-32 x 5/16"
8
1
848589859
Black insulator
9
1
848575841
Vector Controller interface cable
10
4
408450955
Metal standoff (AL-5171-16)
11
8
901377366
Screw, PPHM M3 x 6mm
12
4
901351239
Nut, hex 6-32
13
1
848649943
Mounting bracket
If damage is found and/or components are missing, file a claim with the carrier if applicable, and notify Lineage Power Customer Service (See Section 1).
Vector Controller Configuration The physical interface for the Vector controller to the Galaxy Gateway is through P4 connector on the BLJ terminal connection board, close DIP switch S1.3 (set to 1) to allow communication between Gateway and the Vector Controller.
Gateway Installation for Vector Controller Use the following procedure and Figures 6-1A and 6-1B to install a new or replacement Galaxy Gateway on a GPS metal or plastic door. 1. Install 848649943 bracket to metal door and secure with two 901351239 hex nuts (6-32) per Figure 6-1A or install to plastic door and secure with three 901377366 screws per Figure 6-1B. 2. Place 848589859 black insulator under the Galaxy Gateway and position over the mounting standoffs so that J1 (RJ-45 network interface connector) and J2 (DB-9 serial port connector) are facing down. The component side of the circuit pack should be facing outward. 3. Install two 408456465 nylon mounting posts to the lower mounting standoffs (torque to 3 in·lbs). 4. Install two 407882141 metal standoffs to the upper mounting standoffs (torque to 10 in·lbs). 5. Wrap insulator around the Gateway board and snap onto nylon posts. Using two 845143866 screws, secure top of insulator to metal standoffs (torque to 10 in·lbs).
Issue 9 January 2008
55
Galaxy Gateway v3
Galaxy Gateway Cable Connections Gateway to Controller The Galaxy Gateway receives power and communications from the controller. Use the following procedure and Figure 6-2 to connect the Galaxy Gateway to the Vector controller. 1. Locate 848575841 controller interface cable provided in the kit. 2. Identify the end with a black, 14 position connector. Connect this end to P4 on the BLJ3 terminal connector board. 3. The red and black leads should be connected to posts marked ABS and DG of the BLJ3. The ABS connection is protected by a 2 ampere fuse F1 (top fuse) on the BLJ3 terminal board. F3 holds a spare 2 amp fuse if needed. The maximum current required by the Gateway is 600mA. Verify that the current required by all equipment connected to these ABS connections does not exceed the capacity of the fuse. Connect the black 4-position connector of the cable to the P1 power connector on the Galaxy Gateway. Power will be applied to the Galaxy Gateway when this cable is plugged into P1. The DB-9 male (9 pin) connector will not be connected until after the Gateway is configured. 4. After the connection to P1, wait approximately 45 seconds. The Yellow status LED should blink, indicating that the Gateway is ready to be configured.
Figure 6-2: Gateway Connection to BLJ3 Terminal Board
Issue 9 January 2008
56
Galaxy Gateway v3
10Base-T Network The Galaxy Gateway has an IEEE 802.3 compliant 10Base-T network interface. Since the cable length required to connect the Galaxy Gateway to the network is variable, this cable must be supplied by the user. Connect the network interface cable from the IEEE 802.3 compatible network to J1 (RJ-45) connector on the Galaxy Gateway as shown in Figure 6-2. 1. Connect one end of the network interface cable to J1 (RJ-45 Network Interface Connector), usually located at the bottom right on the Galaxy Gateway. (Other configurations are possible with the hardware shown in Figure 6-2.) 2. Connect the other end to an IEEE 802.3 compatible network.
Configuring Network Communications The Galaxy Gateway uses Transmission Control Protocol/Internet Protocol (TCP/IP) to communicate with the host computer on a local area network. TCP/IP is a widely used protocol that provides communication across networks of diverse computers and devices. This protocol forms the basis for the Internet. Each device or host on a TCP/IP network has its own IP address. The IP address is a 32-bit number, usually written in dot notation (e.g., 127.9.235.48). Another 32-bit number, called subnet mask (or address mask, netmask, e.g., 255.255.0.0) is used to identify the network portion and subnet portion of the IP address. A third 32-bit address, identified as the Default Gateway (router) IP address, is optional, but necessary if network access from outside of the router’s subnet is to be provided. Typically, this router address will be similar to the IP address assigned to the Gateway card, but will end with an octet of 1. A Host name is up to 15 text characters that may optionally be assigned to this specific IP and subnet within the network’s DNS server.
Logging In to the Galaxy Gateway Using the built-in configuration utility of Galaxy Gateway, program the required network configuration information. This information may have to be provided by the network administrator. The following equipment is required: •
PC with terminal emulation communications program
•
Serial interface cable, DB-9 Male for connection to the Galaxy Gateway, and typically DB-9 Female for connection to a PC serial port
To login to the Galaxy Gateway, follow these steps: 1. Start-up the PC communications terminal program (Windows HyperTerminal, ProComm, etc.) using the following communication parameters:
Issue 9 January 2008
57
Galaxy Gateway v3
Baud : 9600 Data : 8 Parity : none Stop : 1 Handshaking: none Flow Control: none 2. Connect the PC to the Galaxy Gateway card’s local port (RS-232) connector J2. 3. Press reset (SW1 – microprocessor reset) switch on the Galaxy Gateway card. 4. Wait for any diagnostic messages to pass and for the “ENTER PASSWORD:” command line prompt. 5. Input the Network Administrator password (default: networkadm). 6.
Wait for the “$” prompt.
Configuring Static Network Parameters After a valid password entry, a login header with the following format will be displayed: Board Code Serial Number
EBW1 1:3 02DJ09112345
Boot Block Application Code Default Web Pages Custom Web Pages
version G.1.0 version G.3.18 version G.3.14 not found
Ethernet Address IP Address Subnet Mask Default Gateway Host Name
00-60-1D-00-5C-07 not configured not configured not configured not configured
For assistance type help $
Typing HELP at the “$” will show all available network administration commands and command line formats. *note: 1) commands are not case sensitive 2) for the commands that follow, ddd is a number from 0 – 255 •
To set the IP Address, type:
Issue 9 January 2008
58
Galaxy Gateway v3
CHA NET1,IP=ddd.ddd.ddd.ddd Verify by typing: STA NET1,IP •
To set the Subnet mask, type: CHA NET1,SUB=ddd.ddd.ddd.ddd Verify by typing: STA NET1,SUB
•
Optional: To set the Default Gateway Address, type: CHA NET1,GTWY=ddd.ddd.ddd.ddd Verify by typing: STA NET1,GTWY
•
Optional: To set the Host Name, type: CHA NET1,HOST=”host name” Verify by typing: STA NET1,HOST
Logging Out of the Galaxy Gateway To terminate the configuration session, enter the “bye” command. The Galaxy Gateway will notify the user if configuration is not complete. This message will have the following format: NOTICE: Default gateway may be required for network access. Host Name may be required for network access. Logging off... Messages referencing the Gateway and Host Name are acceptable, since these parameters are optional. Note: If the IP address or Subnet mask messages below appear, then the configuration procedure must be repeated. IP Address is required for network access. Subnet mask is required for network access.
Post Installation Procedures Once configuration has been completed
Issue 9 January 2008
59
Galaxy Gateway v3
1. Disconnect the serial cable from the Galaxy Gateway (J2 connector). 2. Connect the 9-pin male end of the auxiliary port cable assembly to the J2 connector on the Galaxy Gateway. 3. Press SW1 (microprocessor reset) on the Galaxy Gateway. 4. After approximately one minute, observe the LEDs on the Galaxy Gateway. • • • •
Yellow STATUS LED: Green STATUS LED: Link LED: XMIT/RCV:
OFF ON ON May be blinking
The Galaxy Gateway should be communicating over the network. 5. Secure the cable to the lance on the mounting bracket using the cable tie provided.
Troubleshooting Status and communication LEDs on the Gateway provide operation information as follows: •
With everything powered up, the green status LED should be active after boot-up. The amber status LED should be retired. The Link, TX, and RX LEDs should be active or blinking.
•
If just the amber status LED is active, the EBW Gateway board is bad.
•
If the green status LED is active and the amber status LED is blinking, Gateway thinks the PC is still connected to the serial RS232 port of the Gateway or the network parameters have not been programmed correctly. Insure that a Gateway microprocessor reset has been completed after disconnecting the PC RS232 communication cable and plugging back in the 9-pin connector of the BLJ3 P4 cable set.
•
If both the green and amber status LEDs are active, the unit is still in the process of powering up, the Gateway cannot communicate with the controller, or the Gateway is not communicating with the network over the TCP/IP connection. The Link, TX, and RX LEDs will be green, solid or blinking, whenever network communication is active. ─ If the Link LED is not active, verify the physical connections and the configured addresses used for the Gateway card and its router connection. A Network Administrator may have to “ping” the Gateway card’s address and otherwise assist with troubleshooting the network side of the Ethernet connection.
Issue 9 January 2008
60
Galaxy Gateway v3
─ If both the green and amber status LEDs are active, and the Link LED is green, solid or blinking, then the Gateway is unable to login to the communications port of the controller. This could be due to a physical connection trouble or a password or communications port configuration trouble. Physical – Verify the connections for the 9-pin connector of the Aux port cable set at both the EBW Gateway end and the BLJ3 Vector controller card P4 end. Verify that the Vector is powered up and functional. Password – If both the user and super-user controller passwords (lineage and super-user respectively) have been changed from their default values before Gateway is installed, Gateway will not be able to initially login following its microprocessor reset, and the amber status LED will remain active. When this happens, a web page access request may result in an error message referring to a missing “status.html” page. The easiest solution to this is to first login successfully with both of these passwords over a telnet session, rather than a HTTP web browser session. This will provide Gateway the opportunity to “learn” the passwords, after which, Gateway’s amber status LED will retire, and successful HTTP web browser access will follow. Communications Port – Verify that S1.3 of the Vector BLJ3 is set to “closed” or “1” for Gateway communication over the P4 communications port. Verify that the default settings for Vector for the Local Communications Port for Baud Rate and Handshaking are Auto and None respectively. Front display path: Configure Æ Comm Ports Æ Local Æ Baud Rate (Auto) Configure Æ Comm Ports Æ Local Æ Handshake (None)
Issue 9 January 2008
61
Galaxy Gateway v3
7 Operation Introduction This section provides an introduction to the Gateway’s basic features. Note that the Gateway features that are available will be based on and limited by individual Galaxy Controller feature sets. For example, Galaxy Vector controller features that may be accessed will differ from those available for the more sophisticated Galaxy Millennium controller. Also note that the web pages depicted here are based on the version G.3.18 application code and version G.3.14 web pages of the Gateway software, and may change over the product life span. To proficiently use the Gateway, some experience with power systems, power system terminology, controllers, and web pages is required.
Web Browser Access (HTTP) Using a standard web browser, such as Netscape or Internet Explorer, enter the IP address (or host name) of the Galaxy Gateway. A login screen will appear prompting the user to choose either the Galaxy Controller or the Galaxy Gateway Network Card. See Figure 71. Selecting the GALAXY destination allows you to access and configure the Galaxy Controller. Selecting Network Card allows you to access and configure the network card. Select a destination, enter the correct password, and click on the Submit button. (Default passwords for the Galaxy Controller are: lineage, super-user, administrator for the User, Super-User and Administrator logins respectively. For the Gateway (Network card), the default password is networkadm.
Figure 7-1: Login screen. Click “Submit” to continue
Issue 9 January 2008
62
Galaxy Gateway v3
Using Web Pages The figures that follow illustrate the types of web pages you will encounter. If GALAXY is chosen on the Login screen, inputting a valid controller password and clicking Submit or pressing your Enter or Return key brings up the Active Alarms screen (Figure 7-2).
Figure 7-2: Active Alarms Screen The Alarms screen displays the currently active alarms, the dates and times of occurrence, their severity, and a description of each event. Notice the links that allow users to view alarm history and to clear latched alarms. The left side of each screen displays the current readings of plant voltage, current, and state (float, boost, or battery thermal protection). It also contains a tree structure of folders which, when expanded, show the main links for navigating through the web pages. The folders available are: Present Status, System, Rectifier/Converter, Battery, Distribution, Alarms & Events, Controller Communications, Network Communications, Monitoring, and Administration. A Logout link is at the top of this tree structure and should be used to exit the web page access when completed.
Issue 9 January 2008
63
Galaxy Gateway v3
Figure 7-3 is a block diagram of the logical arrangement of the web page screens. These screens are accessed by clicking on the various links on each page. The illustrations in this section give examples of how to use these links to check the status of the plant and perform various functions. Login Page
Galaxy Controller
Galaxy Gateway
Present Status
Active Alarms Alarm History Settings Equipment Inventory
System
DC Plant Controller Alarm Test Trend Busy Hour Statistic User Defined Object
Rectifier / Converter
Rectifier Manager Rectifier Rectifier Bay Converter Plant Converter
Battery
Boost Slope Thermal Comp Battery Type Definition Battery Management Battery Bay Battery Section
Gateway Serial No Ethernet Address IP Address Subnet Mask Default Gateway Domain Name Host Name Submit Network Settings Download New Software Shutdown for Upgrade Change Network Password Logoff
Controller Communications
Call Out Manager Call Out Phone Number Periodic Call Out Call-Back Security Modem Local RS-232 Port Auxiliary Port Notepad Data Switch
Network Communications
Network Card Network Administration Network Alarm Network Security SNMP TL1 Manager TL1 Managed Objects Derived Channels Bay Current Monitor Bay Voltage Monitor Bay Temperature Monitor Remote Peripheral Monitor Voltage Channel Shunt Channel Temperature Channel Control Relay Binary Channel
Distribution
DC Distribution AC Distribution Contactor Bay Interface Card
Alarms & Events
Alarm Cut-off Alarm Settings Alarm Thresholds User Defined Events Timer Event Maintenance Reminder Connected Eqpt Alarm TL1 Links
Monitoring
Administration
Change Passwords
Logout
Figure 7-3: Block Diagram of Gateway Web Pages
Issue 9 January 2008
64
Galaxy Gateway v3
Screens A user may exit the system at any time by clicking on the Logoff link. See Figure 7-4. Note the reminder to exit the web browser at the end of each session, so that unauthorized users cannot access the system.
Figure 7-4: Logoff Screen
Examples of Screen Interactions To view data or programming, expand the appropriate folder in the tree structure at the bottom left quadrant of the active screen and select the desired web page link. The Figures shown in this section are examples of some of the web pages available.
Issue 9 January 2008
65
Galaxy Gateway v3
Figure 7-5 is the Present Status Æ Alarm History web page. Note the time line graphical representation of events at the top of this page. Links at the top provide easy access to the table listings of particular types of History listings, typical of what is found in EasyView access to the controller. The “Clear History” command buttons require super-user or administrator security to function. History event links are also available off many other web pages, specific to the type of data associated with those pages.
Figure 7-5: Present Status AlarmÆHistory Screen
Issue 9 January 2008
66
Galaxy Gateway v3
Figure 7-6 is the Present Status Æ Settings web page. This is a view-only page, providing once again, a quick graphical representation of some of the more important configurable settings and measured values. Changes to the configured settings are made from other, more detailed web pages. Clicking on DC Plant under the System heading brings up the screen shown in Figure 7-6. Note the variety of information displayed about this object. This is an example of a View page.
Figure 7-6: Present Status Æ Settings
Issue 9 January 2008
67
Galaxy Gateway v3
Figure 7-7 is the Present Status Æ Equipment Inventory web page. Once again, this is a view-only page, providing a quick table reference of the devices that make up the power system. Also note the controller and Gateway card software versions listed at the bottom of this web page.
Figure 7-7: Present Status Æ Equipment Inventory
Issue 9 January 2008
68
Galaxy Gateway v3
Figure 7-8 is the System Æ DC Plant web page. These are the DC1 objects and attributes shown on Table B-5 of the associated Galaxy SC or Galaxy Millennium product manual. Like most of the initial web page links, this is a view-only page, but has “Configure” and “Operate” links at the top that can be used by a super-user or administrator to make changes to configurable parameters or perform actions (such as Rectifier Restart) to objects that have those attributes. History and Statistic links are available for all users.
Figure 7-8: System Æ DC Plant
Issue 9 January 2008
69
Galaxy Gateway v3
Figure 7-9 is the System Æ Controller web page. These are the PS1 objects and attributes shown on Table B-1 of the associated Galaxy SC or Galaxy Millennium product manual. “Configure” and “History” links are available at the top.
Figure 7-9: SystemÆ Controllers
Issue 9 January 2008
70
Galaxy Gateway v3
Figure 7-10 is the Rectifier / Converter Æ Rectifier Manager web page. These are the GM1 objects and attributes shown on Table B-7 of the associated Galaxy SC or Galaxy Millennium product manual. All of these are configurable attributes and set the control of all serial type rectifiers in the power system.
Figure 7-10: Rectifier / Converter Æ Rectifier Manager Figure 7-11 is the Rectifier / Converter Æ Rectifier web page. Here the status of and change any configurable attributes for any of the up to 64 rectifiers that may be equipped in the power system may be seen. Note the green “LED” against each of the rectifiers on this page that will change color to indicate an alarm condition.
Figure 7-11: Rectifier / Converter Æ Rectifier
Issue 9 January 2008
71
Galaxy Gateway v3
Each of the Rectifier Descriptions in Figure 7-11 is a link to present all of the data available for that rectifier and to permit super-users to make configuration or operation changes to individual rectifiers. An example of this page is shown in Figure 7-12. Figure 7-13 is the Operate link page from Figure 7-12. The “Vacant” radio button and “Submit” command in Figure 7-13 are used to remove a serial type rectifier from the controller configuration to retire a Communications Fail alarm when one of these serial rectifiers is disconnected from a power system.
Figure 7-12: Rectifier / Converter Æ Rectifier Æ Rectifier G03
Figure 7-13: Rectifier / Converter Æ Rectifier Æ Rectifier G03 Æ Operate
Issue 9 January 2008
72
Galaxy Gateway v3
Figure 7-14 is the Battery Æ Slope Thermal Compensation web page. These are the SC1 objects and attributes shown on Table B-9 of the associated Galaxy SC or Galaxy Millennium product manual. All of these are configurable attributes associated with the Slope Thermal Compensation feature that is available on plants using all serial type rectifiers and measuring at least one battery temperature of “sealed” type batteries used in the power system.
Figure 7-14: Battery Æ Slope Thermal Compensation Figure 7-15 is the Battery Æ Battery Management web page. These are the BR1 objects and attributes shown on Table B-9 of the associated Galaxy SC or Galaxy Millennium product manual. Here configurable attributes associated with the Recharge Current Limit and Battery Test features available on plants using all serial type rectifiers and the Enhanced Reserve Time Prediction feature available on plants measuring at least one battery temperature in the power system are found.
Figure 7-15: Battery Æ Battery Management
Issue 9 January 2008
73
Galaxy Gateway v3
Figure 7-16 is the Distribution Æ Contactor web page. Here the status of and change any configurable attributes for any of the 3 Low Voltage Disconnect contactor control circuits that are available in the power system can be seen. Note that in GPS cabinets, Contactor 1 is wired as a Battery Disconnect (regardless of the number of battery contactors in the system) and Contactors 2 & 3 are reserved for Load Disconnects (assigned via jumper pins on the associated EBV contactor control card(s)). Each of the Contactor Descriptions in Figure 7-16 is a link to present all of the data available for that contactor and to permit super-users to make configuration or operation changes to them.
Figure 7-16: Distribution Æ Contactor
Figures 7-17 and 7-18 are the Alarms & Events Æ Alarm Settings and Alarms & Events Æ Alarm Thresholds web pages. Figure 7-17 shows the Severity, LED, and Contact Closure (supplemental alarm relay) configurable attributes for all of these standard alarm events in the power system. Figure 7-18 shows the assigned thresholds for each of the standard threshold alarm events. Note the green or red “LED” against each of the events on these pages that change color to indicate the status of each alarm event. Each of the Alarm Descriptions in Figure 7-17 & 7-18 is a link to present all of the data available for that alarm event and to permit super-users to make configuration changes to them. An example of this configuration page is shown in Figure 7-19, for the Alarms & Events Æ Alarm Thresholds Æ Battery on Discharge Æ Configure web page.
Issue 9 January 2008
74
Galaxy Gateway v3
Figure 7-17: Alarms & Events Æ Alarm Settings
Figure 7-18: Alarms & Events Æ Alarm Thresholds
Issue 9 January 2008
75
Galaxy Gateway v3
Figure 7-19:Alarms & EventsÆAlarm ThresholdsÆBattery on DischargeÆ Configure Figure 7-20, Alarms & Events Æ User Defined Events, is similar to Figures 7-18 & 7-19 but also provides the Program Line that controls the status of each event in addition to the Description, Severity, LED, and Contact Closure (supplemental alarm relay) configurable attributes for each of the User Defined Events programmed in the power system. Note the green or red “LED” against each of the events on these pages that change color to indicate the status of each alarm event. Each of the Alarm Descriptions is a link to present all of the data available for that alarm event and to permit super-users to make configuration changes to them.
Figure 7-20: Alarms & Events Æ User Defined Events
Issue 9 January 2008
76
Galaxy Gateway v3
Likewise, Figure 7-21, Monitoring Æ Derived Channel, is similar to Figure 7-20 in that it shows the Program Line that controls the calculated value, in addition to the Description, Value, and Unit attributes for each of the up to 32 Derived Channels in the power system. Each of the channel Descriptions is a link to present all of the data available for that alarm event and to permit super-users to make configuration changes to them.
Figure 7-21: Monitoring ÆDerived Channel Figure 7-22, Monitoring Æ Remote Peripheral Monitor, shows the Description, Status, and Module Type assigned to each of the RPMs recognized in the power system. Note the green or red “LED” against each of these modules just indicates that the RPM function is normal or not. Green here indicates simply that there is no active MDF (Module Fail) or MOR (Measurement Out of Range) alarm against them. Only when the values for the measured channels on RPMs are used in program lines of User Defined Events and/or Derived Channels can the controller perform any logical uses for them.
Issue 9 January 2008
77
Galaxy Gateway v3
Figure 7-22: Monitoring Æ Remote Peripheral Each of the RPM Descriptions is a link to present all of the data available for it and to allow super-users to make configuration changes to them. Figure 7-23 is the data provided for a Shunt Module E4 in our power system. Before a module can be removed in software for a system by using the “Delete” button on this page, several additional steps are necessary: 1. Disconnect the Module physically from the RPM bus. 2. Delete any channels of the module from all UDE or Derived channel program lines. 3. Use the Configure link on Figure 7-23 to “unlock” the module in the page shown in Figure 7-24. 4. Use the “Delete” button in Figure 7-23 to remove the module from programming.
Figure 7-23: Monitoring Æ Remote Peripheral Monitor Æ Myy
Issue 9 January 2008
78
Galaxy Gateway v3
Figure 7-24: Monitoring Æ Remote Peripheral Monitor Æ Myy Æ Configure Figure 7-25, Monitoring Æ Binary Channel, is an example of an RPM Channel web page, this one for Binary Channels. Those for Voltage, Shunt, Temperature, and Control Relay channels are similar. Displayed are the Description, Status, and Value for each of the channel type recognized in the power system. Once again, the green or red “LED” against each of these channels just indicates that reading on that channel is within a normal range or not. A user does not know from this page whether the “CLOSED” value against the Inverter Fail binary channel is an alarm state or a normal state. Only when the values for the measured channels on RPMs are used in program lines of User Defined Events and/or Derived Channels can the controller determine this.
Figure 7-25: Monitoring Æ Binary Channel
Issue 9 January 2008
79
Galaxy Gateway v3
Password administration is accessed by clicking on the Change Passwords link under the Administration folder. The Password Administration screen, shown in Figure 7-26, allows the administrator login security level to change passwords for all user types, elected from the drop-down box. After changing any desired password, click on the Submit button. Note that Galaxy controllers may also have hardware settings that provide additional security restrictions. Refer to the appropriate Galaxy Controller manual for your system.
Figure 7-26: Administration Æ Change Passwords Figure 7-27 shows the screen used to configure network security parameters. Network configuration is accessed by clicking on the Network Security link under the Network Communications folder, and then selecting the Configure link.
Figure 7-27: Network Communications Æ Network Security The last screen in this selection of examples is the Network Card Configuration screen shown in Figure 7-28. This screen is accessed by selecting Network Card on the login page. The network administrator password must be used. The default network administrator password is networkadm. These Network Settings configured here are
Issue 9 January 2008
80
Galaxy Gateway v3
typically provided by the IT department or administrator. Power specific configurations are not included in this section. The “Shutdown System for Upgrade” link is used prior to beginning a FTP session, as described later in this section, when upgrading the Gateway card software or web pages or making additions or changes to any custom web pages.
Figure 7-28: Gateway Network Card Configuration
Telnet Telnet Into Galaxy Telnet is an application layer on top of the TCP/IP protocol. From any networked computer, the user can initiate a Telnet session and connect to either a Galaxy Controller or a Galaxy Gateway on the network. A Telnet session can be initiated using the DOS command line Telnet command (Type Telnet ddd.ddd.ddd.ddd at the MS-DOS command line prompt or from the RUN menu screen of Windows) or from many communication programs, including Windows HyperTerminal. Initiate a Telnet session and connect to the target Galaxy Controller / Galaxy Gateway. The Galaxy Gateway will respond with the following message: Please select a destination: 1. Power Plant Administration, need Galaxy Controller passwords. 2. Network Administration, requires network administration password.
Issue 9 January 2008
81
Galaxy Gateway v3
Select 1 for Galaxy Controller access or 2 for viewing or changing settings of the Gateway card itself. If 2 (Gateway) is selected, the commands supported are ONLY the listed commands in Appendix D (upgrade, idle, reboot, network configuration, etc.) When prompted, enter the correct Network Administrator password. Type HELP and press ENTER for a list of supported commands. The screen should be similar to Figure 7-29:
Figure 7-29: Gateway Network Card Help Menu If 1 (Galaxy) is selected, the commands supported are all of the T1.317 commands used by the Galaxy Controller. For a listing of these commands, consult a Galaxy Controller product manual and refer to the T1.317 command appendix. Typing help provides a small subset of the T1.317 commands. At the prompt, enter the proper Galaxy password. The screen should be similar to Figure 7-30 below: (This example uses the Super-User Password (note the ** command line prompts), and the commands entered are for Plant Voltage, Plant Load and System Warnings.)
Issue 9 January 2008
82
Galaxy Gateway v3
Figure 7-30: Galaxy Controller Telnet Session Galaxy Controller Backup: Note: A Telnet application that will allow an ASCII file transfer, such as Windows HyperTerminal found in newer Microsoft operating systems, is required. The details that follow are specific to HyperTerminal. Once logged in as a super-user or administrator: Type backup and select option A for an ASCII backup. The following message will be returned: Start ASCII download process. Then hit any key to start backup. Use the HyperTerminal dropdown menu path Transfer Æ Capture Text and select a path and filename for the backup to be saved in and select the Start button. Then hit any key to begin the backup. The backup data will be displayed as the file is received from the controller. A message will be displayed when the backup is complete. Use the Transfer Æ Capture Text Æ Stop menu path to close the backup file. Open the file using any test editor (such as Windows Notepad) and remove any lines of information that might be there before the first REM command line at the top or after the last CHA or ALI command line at the bottom and save.
Issue 9 January 2008
83
Galaxy Gateway v3
Galaxy Controller Restore: Note: A Telnet application that will allow an ASCII file transfer, such as Windows HyperTerminal found in newer Microsoft operating systems, is required. The details that follow are specific to HyperTerminal. Once logged in a super-user or administrator: Type Restore and a select “A” for ASCII transfer. The following message will be returned: Start ASCII upload process. Multiple control-X characters will abort restore. Begin the restore by using the HyperTerminal dropdown menu path Transfer Æ Send Text File and select the backup’s path and filename and select the Start button. (The controller Restore command will timeout if a file is not selected within 2 minutes.) Nothing will be displayed during the file transfer, but activity over your Ethernet connection should be noticeable. A “Restore Complete” message will be displayed after a successful file transfer.
Alarm Reporting Alarm Alert Criteria, PUSH, pager and phone numbers, and e-mail configuration can be programmed using the Gateway web pages or a Telnet connection when logged in as a super-user or administrator.
Alarm Alert Criteria Alarm notification can be determined based on severity. All alarms, no alarms, or degrees of severity of the alarms may be reported. There are four degrees of severity as follows: • None
– no alarms are reported over the network
• CRIT
– Only Critical alarms are reported over the network
• MAJ+
– Only Major or Critical alarms are reported over the network
• MIN+
– Minor, Major and Critical alarms are reported over the network
Web Browser Configuration: Alarm Alert Criteria features are accessed by clicking the Network Alarm page link under the Network Communications folder, and changes are made using the Configure link. Telnet Configuration: The T1.317 commands for a Telnet session are as follows: cha nam1,sev=text – This command assigns the level(s) of alarm severities that are sent to pagers, PUSH stations, or e-mail addresses. Valid values for text are: NONE, CRIT, MAJ+, and MIN+
Issue 9 January 2008
84
Galaxy Gateway v3
sta nam1,sev – This command displays the level(s) of alarm severities that are sent to pagers, PUSH stations, or e-mail addresses.
Alarm Push Feature Alarm Push is a Gateway feature developed for a unique customer group and requires the use of specialized hardware and software at the receiving end to support it. Up to three IP addresses can be configured for automatic alarm capture with the Push feature. Web Browser Configuration: The Alarm push features are accessed by clicking the Network Alarm page link under the Network Communications folder, and changes are made using the Configure link. Choose the Alarm Push IP address to be configured and enter the IP address and port number. (To erase this field, enter an IP address of 0.0.0.0:1.) Press Submit to confirm changes. Telnet Configuration: Using a Telnet session with T1.317 commands, the commands are as follows: cha nam1,pshx = IP Address - This command configures Push Address x to be the IP Address entered. (x = 1, 2, or 3) sta nam1,pshx – This command displays the configured IP address for Push Address x. (x = 1, 2, or 3)
E-mail or Text Pager Up to three e-mail addresses (example:
[email protected]) and three text or numeric pager addresses (example:
[email protected]) may be configured for alarm reporting. The message sent to numeric pagers will just be the IP Address of the Gateway card, while the message sent to email addresses and text pagers will be similar to the following sample:
Notice the Gateway address link, which may be used with a browser to take the recipient directly into the Gateway card to obtain additional information as needed.
Issue 9 January 2008
85
Galaxy Gateway v3
In addition to the configuration information which follows, if the Gateway card is on a different subnet than a mail server being accessed, it is likely that the Default Gateway (router) IP address and/or a Domain Name for the Gateway card will need to be configured. Both may be accessed by selecting Gateway on the login page. Web Browser Configuration: The E-mail, pager, and mail server addresses are accessed by clicking the Network Alarm page link under the Network Communications folder, and changes are made using the Configure link. Choose the address to be configured and enter the address. Select an email address field for a text pager. E-mail and pager addresses may be no more than 35 characters. The Mail Server IP Address must be entered as an IP address. To erase this field, enter 0.0.0.0.1 for the IP address. Press Submit to confirm changes. Telnet Configuration: Using a Telnet session with T1.317 commands, the commands are as follows: Email or Text Pager Addresses cha nam1,emx = E-Mail Address - This command configures e-mail or text pager address x to be the e-mail Address entered. This address must be 35 characters or less. (x = 1, 2, or 3) sta nam1,emx – This command displays the configured e-mail address for e-mail address x. (x = 1, 2, or 3) Numeric Pager Addresses cha nam1,pgx = Pager Address - This command configures Pager address x. This address, an e-mail address, must be 35 characters or less. (x = 1, 2, or 3) sta nam1,pgx – This command displays the configured Pager address x. (x = 1, 2, or 3) Mail Server IP Address (The system mail host that relays messages) cha nam1,msrv = Mail Server Address - This command configures the Mail Server Address for paging/e-mail. This address is an IP address. sta nam1,msrv – This command displays the configured Mail Server Address for paging/e-mail.
Security The Galaxy Gateway has been designed with multiple security features to prevent unauthorized access to both, the Galaxy Gateway and the Galaxy Controller. A password
Issue 9 January 2008
86
Galaxy Gateway v3
is required to configure Galaxy Gateway Network Administration tasks and to log in to the Galaxy Controller. Three levels of login, each having a unique password, are provided for logging in to the Galaxy Controller through the Galaxy Gateway. An optional security feature permits only specific IP addresses to access the Galaxy Gateway or Galaxy Controller. If multiple super-users and administrators are logged in at the same time, the Galaxy Gateway will alert each super-user/administrator and inform them that other users are logged in with read/write privileges. Connections to the Galaxy Gateway that have been idle for more than a specific time (programmable) will be terminated.
Idle Connection Timeout Web Browser Configuration Using a standard web browser, login in to the Galaxy Controller through the Galaxy Gateway as a super-user or administrator, and configure the Network parameters that support the Idle Timeout feature. These are accessed by clicking the Network Security link under the Network Communications folder. Enter the timeout period. (To erase a field, clear the field and enter a space character.) Press Submit to confirm changes. Telnet Configuration Using a Telnet session with T1.317 commands, the commands are as follows: cha nsm1,idle=xx - This command sets the Galaxy Gateway’s idle timeout to a number xx from 0 to 60 minutes, 0 meaning no timeout. If no requests from an IP address are received for this specified time period, the login session is terminated. sta nsm1,idle - This command displays the timeout period
Restricting IP Address Access Web Browser Configuration Using a standard web browser, login in to the Galaxy Controller through the Galaxy Gateway as a super-user or administrator, and configure the Network parameters that support the super-user source feature. These are accessed by clicking the Network Security link under the Network Communications folder. Choose a super-user source and enter the IP address associated with it. (To erase a field, clear the field and enter a space character.) Press Submit to confirm changes. Telnet Configuration Using a Telnet session with T1.317 commands, the commands are as follows:
Issue 9 January 2008
87
Galaxy Gateway v3
cha nsm1,suse=x - This command enables or disables the Galaxy Gateway’s ability to communicate with only specific IP addresses (maximum of 5). If x=0, then any valid IP addresses may access the Galaxy Gateway. If x=1, only IP addresses configured under super-user sources 1-5 may access the Galaxy Gateway. sta nsm1,suse - This command displays the present state of the restricted IP address feature. cha nsm1,susx=ddd.ddd.ddd.ddd - This feature defines super-user source x as restricted IP address ddd.ddd.ddd.ddd. (x = 1-5) sta nsm1,susx - This command displays the present IP address assigned to super-user source x.
Galaxy Gateway Upgrade Gateway card software updates are available free of charge and can be downloaded at http://www.lineagepower.com. The Galaxy Gateway has four software components: •
The boot software – responsible for power on test, factory test, local and remote upgrade of the other software components.
•
The application software – including an HTTP server and Telnet daemon.
•
Default web pages – canned web pages supplied by Lineage Power.
•
Custom web pages – customer specific web pages developed by Lineage Power or someone else. The limits for files placed into the Custom directory of the HTTP server are 1000 files maximum and 500K of total file space. One file must be named index.html and a link to the standard web pages at index2.html should be provided.
FTP FTP (File Transfer Protocol) is used only for upgrading Galaxy Gateway software. Application software, default web pages, and/or custom web pages can be uploaded to the Galaxy Gateway using FTP. Users may also retrieve (get) existing custom web pages from the Galaxy Gateway, make modifications, and copy (put) them back into the Galaxy Gateway. Essentially any FTP client may be used with Gateway. The DOS FTP client available with Windows will be depicted in these instructions. It is only capable of transferring files that reside in the present, working directory when the FTP session was started. It is important to change to the directory holding the files to be transferred before issuing the FTP ddd.ddd.ddd.ddd command.
Issue 9 January 2008
88
Galaxy Gateway v3
To use FTP, the user must first initiate a webpage or Telnet session and select the Network Administration option. Enter the correct Network Administrator password (default is networkadm) and, on the web page or at the prompt, select the Shutdown System For Upgrade link or type the Upgrade command. This will place the Gateway card in the proper mode of operation and return a prompt to initiate the FTP command. The Galaxy Gateway will now wait up to 2 minutes for the FTP session to be established. The Galaxy Gateway has a file/directory structure as shown below:
Where “/” is the root directory. Each subdirectory contains files that are necessary for the Application Software, default web pages, and custom web pages. Using an FTP client on a PC, files may be transferred to/from these Galaxy Gateway directories. Common FTP commands used when performing file operations are: ftp - Initiate the ftp session. cd - Change directories on the Galaxy Gateway. put - Copy files from the PC running FTP to the Galaxy Gateway (The present working directory of the PC will be the source directory for the file being copied.) mput - Copy multiple files from the PC running FTP to the Galaxy Gateway (The present working directory of the PC will be the source directory for the files being copied.) get - Copy a file from the Galaxy Gateway to the PC running FTP (The present working directory of the PC will be the destination directory for the file being copied.) mget - Copy multiple files from the Galaxy Gateway to the PC running FTP (The present working directory of the PC will be the destination directory for the files being copied.) bye - Exit the FTP session and reboot the Galaxy Gateway pwd - Display the path of the current directory (in Gateway) del - Remove a file from a directory ls -
List all files in a directory
Issue 9 January 2008
89
Galaxy Gateway v3
Application Software Upgrade The following steps may be followed to use the DOS FTP client that comes with a Windows PC for loading a new Application Software file. Any other FTP client may also be used, modifying this procedure accordingly as necessary. 1. Access the Lineage Power Systems Galaxy Gateway web site at www.lineagepower.com and follow the page links to locate the Gateway software. Select the Download App Code link. Save this file as app.bin in a directory where you can locate it later, perhaps C:\temp\ . 2. Establish a Telnet or web browser session into the Gateway card and initiate an Upgrade command as described in the FTP section. 3. In Windows, use the path Start Æ Programs Æ Accessories Æ Command Prompt (or some variation of this depending on the Windows version) to activate the DOS Command Prompt screen. Change to the directory within your PC where the new Application Code file was saved when it was downloaded (C:\>cd \temp). 4. Issue the command, C:\Temp>FTP xxx.xxx.xxx.xxx where xxx.xxx.xxx.xxx = the Gateway IP Address or host name. 5. Login to the FTP session as “guest” (without the “”), using the Network Administrator password (default networkadm). 6. Change directory (cd) within the Gateway to the \code subdirectory (cd code). 7. Use the “put” command to copy the application software file into the Gateway (put app.bin). 8. Wait until the message indicating a successful file transfer is displayed. This may take several minutes, depending on the network speed. A message may also be displayed following a successful file transfer, “Connection closed by remote host” like that shown in Figure 7-31. 9. Type bye to exit the FTP session. This command also reboots the Gateway and begins running the new application program.
Issue 9 January 2008
90
Galaxy Gateway v3
Figure 7-31: FTP Session of Gateway Application Software Upgrade
Standard Web Pages Upgrade The following steps may be followed to use the DOS FTP client that comes with a Windows PC for loading new standard web pages. Any other FTP client may also be used, modifying this procedure accordingly as necessary. 1. Access the Lineage Power Galaxy Gateway web site at www.lineagepower.com and follow the page links to locate the Gateway software. Select the Download Gateway Webpages link. Save this file as pages.web in a directory where you can locate it later, perhaps C:\temp\ . 2. Establish a Telnet or web browser session into the Gateway card and initiate an Upgrade command as described in the FTP section. 3. In Windows, use the path Start Æ Programs Æ Accessories Æ Command Prompt (or some variation of this depending on the Windows version) to activate the DOS Command Prompt screen. Change to the directory within your PC where the new pages.web file was saved when it was downloaded (C:\>cd \temp). 4. Issue the command, C:\Temp>FTP xxx.xxx.xxx.xxx where xxx.xxx.xxx.xxx = the Gateway IP Address or host name. 5. Login to the FTP session as “guest” (without the “”), using the Network Administrator password (default networkadm). 6. Change directory (cd) within the Gateway to the \default subdirectory (cd default). 7. Use the “put” command to copy the pages.web file into Gateway (put pages.web).
Issue 9 January 2008
91
Galaxy Gateway v3
8. Wait until the message indicating a successful file transfer is displayed. This may take several minutes, depending on the network speed. A message may also be displayed following a successful file transfer, “Connection closed by remote host”. 9. Type bye to exit the FTP session. This command also reboots the Gateway and begins running the new web pages when accessed again via web browser.
Figure 7-32: FTP Session of Gateway Standard Web Pages Upgrade
Custom Web Pages Galaxy Gateway includes a password-protected web server capable of serving web pages with standard HTML, graphics, client-side JavaScript, and Java Applets. Using a standard web browser, it is possible to not only access power plant data, but to also maintain on-line documentation, tools, floor plans etc., that may be useful to users accessing the system remotely. Typically, custom web pages include dynamic data loaded from the controller. This is done by embedding references to controller data (using T1.317 syntax) in the web page source. These files might be used to view some of the commonly accessed controller data (plant voltage, load, capacity, reserve time, etc.) on a single web page immediately upon accessing the controller through its Gateway web server. Links from this page can then be used to access other custom web pages or to switch to the standard web pages (index2.html) or logoff. The following is an example of this HTML programming to present a Custom Web Page. This programming provides a web page with the site description, date, and time followed
Issue 9 January 2008
92
Galaxy Gateway v3
by a table with columns for the channel number, description, and value for all of the shunt type RPM channels of the power system. Following the table are links to the main custom web page, the standard web pages, and to logoff. Figure 7-33 is a sample output of this custom web page. Custom Gateway Data Site Description: %!Dsta ps1,sde%!
Date: %!Dsta ps1,dat%!
Time: %!Dsta ps1,tim%!
function channels(data) { if (data.length == 0 || data.indexOf("!-310") >= 0) { document.write("None Present"); } else if (data.indexOf("!-") >= 0) { document.write("ERROR: " + data); } else { // start the table document.write(""); document.write("Channel"); document.write("Description"); document.write("Value"); // display the channels var lines = data.split("
"); var ln = ""; for (var i = 0; i < lines.length-1; ) { ln = lines[i++]; document.write("" + ln.substring(1)); for (j = 0; j < 2; j++) { ln = lines[i++]; var w = ln.split("="); document.write("" + w[1]); } document.write(""); } // end the table document.write(""); } } Shunt Channels channels("%!Lsta shm,des,val%!");
Issue 9 January 2008
93
Galaxy Gateway v3 Back to Main Custom Page
Go to Standard Web Pages
Logoff
Figure 7-33: Shunt Channel Custom Web Page Example The following steps may be followed to use the DOS FTP client that comes with a Windows PC for loading new custom web pages. Any other FTP client may also be used, modifying this procedure accordingly as necessary. 1. Develop the custom web page or pages to be used. It is suggested that Lineage Power Technical Field Support should be contacted for assistance in this development work. Save the file(s) developed as file type .html in a directory that can be located later, perhaps C:\temp\ . One of the custom web page files must have the filename index.html . Note that the \custom subdirectory of Gateway is limited to 1000 files and/or 500K total file size maximum. A link to the standard web pages (index2.html) must also be provided. A logoff link might also be convenient for those sessions where access to the standard web pages is not otherwise necessary. 2. Establish a Telnet or web browser session into the Gateway card and initiate an Upgrade command as described in the FTP section.
Issue 9 January 2008
94
Galaxy Gateway v3
3. In Windows, use the path Start Æ Programs Æ Accessories Æ Command Prompt (or some variation of this depending on the Windows version) to activate the DOS Command Prompt screen. Change to the directory within your PC where the new custom web page file(s) is/are saved (C:\>cd \temp). 4. Issue the command, C:\Temp>FTP xxx.xxx.xxx.xxx where xxx.xxx.xxx.xxx = the Gateway IP Address or host name. 5. Login to the FTP session as “guest” (without the “”), using the Network Administrator password (default networkadm). 6. Change directory (cd) in the Gateway to the \custom subdirectory (cd custom). 7. Use the “put” command to copy the index.html file into the Gateway (put index.html) or the “mput” FTP command to copy multiple .html files into the Gateway \custom subdirectory (mput *.html). With the mput command, it will be necessary to affirm (with a y) the transfer of each .html type file located by the FTP application in the resident PC directory. 8. Wait until the message indicating a successful file transfer (or transfers) is displayed. This may take several minutes, depending on the network speed. A message may also be displayed following a successful file transfer, “Connection closed by remote host”. 9. Type bye to exit the FTP session. This command also reboots the Gateway and begins running the new custom web pages the next time the controller is accessed via web browser through the Gateway. C:\>cd \temp C:\Temp>ftp 160.240.240.10 Connected to 160.240.240.10. 220 SNX FTP server ready. User (160.240.240.10:(none)): guest 331 User name OK, need password. Password: 230 User guest logged in ftp> cd custom 250 Current directory is now “custom”. ftp> put index.html 200 Port Command OK. 150 Opening ACSII node data connection for ‘STOR’. 226 Transfer complete. ftp: 4222 bytes sent in 0.01 Seconds 422.20 Kbytes/sec. ftp> bye 221 Bye. C:\Temp> Figure 7-34: FTP Session of Gateway Custom Web Pages Upgrade
Issue 9 January 2008
95
Galaxy Gateway v3
SNMP Interface The Gateway Card also allows users to interface with the power system via the Simple Network Management Protocol (SNMP). This protocol permits control and monitoring of many power systems from a single operation center. Each of the individual power systems is controlled by a Galaxy Controller and connected to the Gateway network card. All of the Galaxy Controllers are accessible from the central location. In a typical application, the operator uses a browser-style interface to interact with the system. At the highest level, the screen may display a map showing the locations of all the installations controlled by the user. This map would show locations that currently have alarms. Clicking on a location’s icon would progressively zooms to more specific locations: for instance, a city, then a central office, then an individual power system, and so on through the components of each system. The structure of the items in the system (the Management Information Base, or MIB) may be displayed graphically as a “tree” in the browser interface. See Figure 7-21. Another screen may display current warnings and alarms. See Figure 7-22. Similar screens may display each aspect of the system.
Figure 7-35: SNMP Browser Display of MIB Contents
Issue 9 January 2008
96
Galaxy Gateway v3
Figure 7-36: SNMP Browser Display of Current Warnings and Alarms The SNMP protocol is transparent to the user. It uses a custom Management Information Base (MIB) that includes all the objects controlled or monitored by the Galaxy Controllers: rectifiers, converters, bay interface cards (BICs), alarms, etc. These items are the T1.317 objects and attributes listed in Appendix B of each of the Galaxy Controller Product Manuals. When an alarm occurs or retires the Gateway sends Galaxy Controller alarms as “traps,” which are automatically transmitted to the user’s network managing system. An alarm is “trapped” and included in one of three kinds of lookup table managed by the SNMP.
SNMP Configuration Two types of configurable data are used in this SNMP system: community strings and trap parameters. They are used to regulate access to the system, to direct information within the system, or for system updates. Users may configure SNMP from a telnet command line interface using these commands. The browser interface also supports SNMP configuration. Community Strings: These function like user IDs or passwords. The Gateway supports three different community strings. Each community string may be configured with either read-only or read-write access. An IP address may be associated with a community string to further restrict access. These fields, as well as other SNMP items, can be configured by clicking SNMP link under the Network Communications folder. Use the Configure link to modify these parameters. Figure 7-37 shows the SNMP screen.
Issue 9 January 2008
97
Galaxy Gateway v3
Figure 7-37: SNMP Screen These parameters may also be configured using a Telnet session into the Galaxy controller and the following T1.317 commands: CHA SNMP1,CSNx=text CHA SNMP1,CSIx=ddd.ddd.ddd.ddd CHA SNMP1,CSWx=1/0
change SNMP Community string name x=1-3 change SNMP Community IP address x=1-3. An IP address of 0.0.0.0 allows access from all IP addresses. change SNMP Community write enable x=1-3
Trap Parameters: A trap is a spontaneous message generated by the Gateway and sent to the monitoring system to provide notification of an alarm condition. The gateway supports five different destinations for SNMP messages. Each destination is configured
Issue 9 January 2008
98
Galaxy Gateway v3
with a community string and IP address. These parameters can be configured using the SNMP screen (Figure 7-37) or by using the following T1.317 commands: CHA SNMP1,TDNx=text
change SNMP Trap destination community name x=1-5
CHA SNMP1,TDIx=ddd.ddd.ddd.ddd
change SNMP Trap destination IP address x=1-5 Where ddd is a number between 0 and 255.
The SNMP agent in the Gateway supports different versions of alarm reporting. It understands and generates both SNMP V1 and V2C packets. The normal mode for the agent is to generate traps using V2C packets. For older management systems, it is possible to configure the Gateway to generate only V1 trap packets. These parameters can be configured using the SNMP screen (Figure 7-37) or by using the following T1.317 command: CHA SNMP1,V1T=x
x=1 enable sending V1 traps x=0 disable sending V1 traps
SNMP Operations Command to update information about Galaxy objects: This is used to update the Gateway’s database of MIB objects available in the connected Galaxy Controller. The Gateway polls the Galaxy for added/removed objects when this command is issued. The SNMP MIB can be updated by clicking the Operate link on the SNMP screen (Figure 737), or by the following T1.317 command. This command should be issued whenever objects (rectifiers, remote peripheral monitors, UDEs, etc.) are added to or removed from the Galaxy. OPE SNMP1,UPD=1
update MIB with added/removed objects
TL1 Interface The Galaxy Gateway card is also equipped with the Transaction Language (TL1) protocol used by Galaxy Controllers equipped with BSJ or BJH intelligent options. This protocol enables direct network-based communications with a central computerized monitoring system that uses the TL1 language as specified by Telcordia. In TL1 terminology, the Galaxy SC is commonly called a Network Element (NE) and the central computerized monitoring system is called the Operations System (OS). Appendix F includes the relevant TL1 parameter descriptions. Additional information can be found in the Galaxy Controller product manuals. To enable the TL1 protocol to work with TCP/IP, click the TL1 Manager link under the Network Communications folder. TL1 objects (alarms and events) are added or
Issue 9 January 2008
99
Galaxy Gateway v3
configured on the TL1 Monitoring screen (see Figure 7-38). To access this screen, click the TL1 Links link under the Alarms & Events folder
Figure 7-38: Alarms & Events Æ TL1 Links
To add a new TL1 object: Click the Add button for the object on the TL1 Monitoring screen (Figure 7-38). 2. Click the Link button to link the assigned TL1 ID to the selected object. Then click the Back button on the verification screen. 3. Click the Configure button to edit the TL1 parameters. Clicking the Disable button on this screen will cancel the TL1 assignment. Click the Submit button when finished. Clicking the back button on the verification screen will return you to the configuration screen if you need to re-edit any of your entries. 4. Use the links on the left side of the web pages to exit the configuration screens.
Issue 9 January 2008
100
Galaxy Gateway v3
5. When all configuration work is complete, click the TL1 Manager link under the Network Communications folder. On the TL1 Manager page, click the Operate link to update the TL1 database.
To configure or delete an existing object: 1. Click the Configure button for the object on the TL1 Monitoring screen. 2. To edit the object’s TL1 parameters, click the Configure button. Click the Submit button when finished. To delete the TL1 object, click the Disable button. 3. Use the links on the left side of the web pages to exit the configuration screens. 4. When all configuration work is complete, click the TL1 Manager link under the Network Communications folder. On the TL1 Manager page, click the Operate link to update the TL1 database. All assigned TL1 objects can be viewed by clicking the TL1 Managed Objects link under the Network Communications folder.
Issue 9 January 2008
101
Galaxy Gateway v3
Appendix A: Technical Specifications Table A-1: Technical Specifications Application Level Protocols Supported
TCP, HTTP, FTP, TELNET, SMTP (standard version), SNMP, TL1
Compatibility
Ethernet: IEEE 802.3 TCP/IP Intranet/Internet Networks
Web Browsers
Netscape Navigator 4.0 or later Microsoft Internet Explorer 4.0 or later
Network Interface
RJ-45 (10BASE-T) Twisted Pair Ethernet
RS-232 Serial Interface
DATA RATES 9600bps - 115.2Kbps
Serial Communication Formats
Data bits: 8 Stop bits: 1 Parity: none Flow control: none
System Software
Flash ROM: software upgrades are downloaded and installed over the network connection or Galaxy Gateway serial port
Ethernet Diagnostic LEDs
Transmit Data Receive Data Link Up
Circuit Pack Diagnostic LEDs
Green Amber
Power Requirements
EBW1 or BJD1 18V to 72V 125mA (nominal) @ 48V
Environmental
Operating Temperature: 0 to 50°C (32 to 122°F) Storage Temperature: -40 to 85°C (-40 to 185°F)
Physical Dimensions EBW1
9.0 cm (3.54 in) x 15.2 cm (6.00 in) x 2.0 cm (.78 in)
Physical Dimensions BJD1
26.5 cm (10.44 in) x 20.6 cm (8.1 in) x 1.3 cm (.5 in)
Issue 9 January 2008
102
Galaxy Gateway v3
Table A-2: Pin Assignments for Ethernet Ethernet (J1) Pin Function 1 TX+ 2 TX3 RX+ 4 NC 5 NC 6 RX7 NC 8 NC
Table A-3: Pin Assignments for RS-232 Serial Port RS-232 Serial Port (J2) Pin Function 1 NC 2 RXD 3 TXD 4 DTR 5 GND 6 DSR 7 RTS 8 CTS 9 GND
Table A-4: Pin Assignments for Power (EBW1 only) Power (P1) Pin Function 1 PWR+ 2 PWR3 NC 4 NC
Issue 9 January 2008
103
Galaxy Gateway v3
Appendix B: Troubleshooting The green and yellow status LEDs are controlled by software. Table B-1:
Table B-1: LEDs Normal Internet operation The following issues are fatal errors and the Galaxy Gateway must be replaced: • DRAM test failure • Boot block test failure • EEPROM test failure • Ethernet test failure • Ethernet address was not configured at factory • Serial number was not configured at factory • Board code was not configured at factory Green on, Yellow blinking • PC connected to Galaxy Gateway local RS-232 port Green only Yellow only
Green on, Yellow on
Issue 9 January 2008
The following issues may be resolved in the field: • Application software is not found • Default web pages not found • IP address not configured • Subnet mask not configured One or more following issues: • Power on self-test (temporary) • Controller interface cable disconnected • Galaxy Gateway cannot communicate with controller ─ Galaxy intelligent controller auxiliary port not configured correctly ─ Controller passwords all unknown ─ Circuit pack / interface module not fully inserted, located, or wired properly • 10Base-T network interface cable is disconnected or network problem exists (if LINK LED is illuminated, this is not the problem)
104
Galaxy Gateway v3
Appendix C: FTP Supported Commands ftp
File Transfer Protocol
Syntax ftp xxx
Initiates the ftp session with target IP address.
Description FTP Session is established
cd
Change Directory
Syntax cd dir
change directory to dir
Description Once FTP has started running, cd is used to change directories on the Galaxy Gateway.
put
FTP File Copy Command
Syntax put fn
copy fn from pc working directory to target directory
Description Used to copy a file from the PC running FTP to the Galaxy Gateway.
mput Syntax mput *.ext
FTP Multiple File Copy Command copy all .ext files from PC working directory to Galaxy Gateway directory
Description Used to copy multiple files from the PC running FTP to the Galaxy Gateway. The user must be in the directory containing the files to be copied. get
Issue 9 January 2008
FTP File Retrieve Command
105
Galaxy Gateway v3
Syntax get fn
copy fn from Galaxy Gateway to PC working directory
Description Used to copy a file from the Galaxy Gateway to a PC. The user must be in the directory containing the file to be copied.
mget Syntax mget *.ext
FTP Multiple File Retrieval Command copy all .ext files from the Galaxy Gateway to PC working directory
Description Used to copy multiple files from the Galaxy Gateway to a PC running FTP. The user must be in the directory containing the files to be copied.
bye
FTP logoff
Syntax bye Description Used to Exit the FTP session and reboot the Galaxy Gateway.
pwd
Present Working Directory
Syntax pwd Description Used to display the path of the current directory. del
Remove a File
Syntax del filename Description Used to remove a file from a directory. ls List all Files
Issue 9 January 2008
106
Galaxy Gateway v3
Syntax ls Description Used to list all files in a directory.
Issue 9 January 2008
107
Galaxy Gateway v3
Appendix D: Telnet Supported Commands Note: All T1.317 commands supported by the controller using a terminal emulation program are also accepted when using Telnet for access. A listing of these commands can be found in the Galaxy Controller product manuals. Network specific T1.317 commands are listed below: Network Communication Card obj,attr Description ncc1,ver Application Software Version ncc1,verw Web Page Software Version ncc1,brd Board code ncc1,sn Serial number ncc1,key Feature key ncc1,post Power-self test results
Related Commands sta cha ope x
Network Administration obj,attr Description net1,ead Ethernet address net1,ip IP address net1,sub Subnet mask net1,gtwy Default gateway net1,host Host name net1,dom Domain name
Related Commands sta cha ope x x x x x x x x x x x
Network Alarm Management obj,attr Description nam1,sev Notification severity nam1,psh1 Push address 1 nam1,psh2 Push address 2 nam1,psh3 Push address 3 nam1,msrv Mail server address nam1,em1 Email address 1 nam1,em2 Email address 2 nam1,em3 Email address 3
Issue 9 January 2008
Type Text
Range of Values text
x
Text
text
x x x x
Text Text Hexadecimal Text
up to12 characters 12 characters XXXXXXXX multiple lines of text
Type Ethernet addr IP address IP address IP address Text Address
Range of Values XX-XX-XX-XX-XX-XX ddd.ddd.ddd.ddd ddd.ddd.ddd.ddd ddd.ddd.ddd.ddd up to 15 characters up to 35 characters
x
Related Commands sta cha ope x x x x x x x x x x x x x x x x
Type Text IP address IP address IP address IP address e-mail e-mail e-mail
Range of Values NONE, CRIT, MAJ+, or MIN+ ddd.ddd.ddd.ddd ddd.ddd.ddd.ddd ddd.ddd.ddd.ddd ddd.ddd.ddd.ddd up to 35 characters up to 35 characters up to 35 characters
108
Galaxy Gateway v3
nam1,pg1 nam1,pg2 nam1,pg3
Pager address 1 Pager address 2 Pager address 3
x x x
Network Security Management obj,attr Description nsm1,idle Idle connection time-out nsm1,suse Super-user IP source enable nsm1,sus1 Super-user IP source 1 nsm1,sus2 Super-user IP source 2 nsm1,sus3 Super-user IP source 3 nsm1,sus4 Super-user IP source 4 nsm1,sus5 Super-user IP source 5
x x x
e-mail e-mail e-mail
Related Commands sta cha ope x x x x x x x x x x x x x x
up to 35 characters up to 35 characters up to 35 characters
Type Number Number IP address IP address IP address IP address IP address
Range of Values 1 to 60 minutes 0:disable 1:enable ddd.ddd.ddd.ddd ddd.ddd.ddd.ddd ddd.ddd.ddd.ddd ddd.ddd.ddd.ddd ddd.ddd.ddd.ddd
The Telnet Reboot command is the equivalent of pressing the local microprocessor reset switch on the Gateway to generate a microprocessor reset. This command logs off the user and processes a reboot of the Gateway card.
Issue 9 January 2008
109
Galaxy Gateway v3
Appendix E: Local Port Command Interface T1.317 Command Language The command language is based on the T1.317 standard. The T1.317 standard has been adapted to the needs of a low-end controller. This section describes the commands, objects and attributes used to access measurements, configuration, and control parameters in the controller.
Objects and Attributes The T1.317 standard organizes system parameters called attributes into groups called objects. The tables below lists the objects supported for remote access. An object-attribute pair uniquely identifies a measurement, configuration, or control parameter. For example, the object-attribute pair “net1,ip” identifies the network IP address while the object-attribute pair “new1,sub” identifies the network subnet mask. In each of these examples “net1” identifies the network administration object and “ip” and “sub” identify IP address and subnet mask respectively. The table below summarizes the object-attribute pairs supported by the NCC along with the commands that can be used with the pair and the valid range that the attribute may have. Commands are defined in detail in the following section.
Network Communication Card obj,attr Description ncc1,ver Application Software Version ncc1,verw Web Page Software Version ncc1,brd Board code ncc1,sn Serial number ncc1,key Feature key
Related Commands sta cha
Network Administration obj,attr Description net1,ead Ethernet address net1,ip IP address net1,sub Subnet mask net1,gtwy Default gateway net1,host Host name net1,dom Domain name
Related Commands sta cha
Issue 9 January 2008
x
Type Text
Range of Values text
x
Text
text
x x x
text text hexadecimal
up to12 characters 12 characters XXXXXXXX
Type Ethernet addr IP address IP address IP address text Address
Range of Values XX-XX-XX-XX-XX-XX ddd.ddd.ddd.ddd ddd.ddd.ddd.ddd ddd.ddd.ddd.ddd up to 15 characters up to 35 characters
x x x x x x
x
x x x x x
110
Galaxy Gateway v3
Issue 9 January 2008
111
Galaxy Gateway v3
Network Administrator Commands This section describes commands the network administrator uses to configure the network interface and perform upgrades. bye
Log-Off
Syntax bye Return logging off... Description This command is used to terminate the current command line session.
Change Value
cha Syntax cha obj,attr=value
where: obj,attr is an object-attribute pair. For example, net1,ip. Return nothing Description This command is used to change system configuration parameters. A couple examples are listed below to illustrate how this command works. cha net1,ip=135.107.96.1
- change the network IP address to 135.107.96.1
cha net1,sub=255.255.254.0 - change the network subnet mask to 255.255.254.0
Issue 9 January 2008
112
Galaxy Gateway v3
help
Display Help
Syntax help
list commands
Return BYE CHA NCC1,KEY=key CHA NET1,GTWY=ddd.ddd.ddd.ddd CHA NET1,HOST=name CHA NET1,IP=ddd.ddd.ddd.ddd CHA NET1,SUB=ddd.ddd.ddd.ddd PAS password,password STA NCC1,BRD STA NCC1,KEY STA NCC1,SN STA NET1,EAD STA NET1,GTWY STA NET1,HOST STA NET1,IP STA NET1,SUB UPGRADE A UPGRADE W
log-off change license key change default gateway change host name change IP address change subnet mask change network administrator password read board code read license key read board serial number read Ethernet address read default gateway read host name read IP address read subnet mask upgrade application code upgrade manufacturer web pages
Note: In the commands above ddd stands for a number between 0 and 255. Description This command is used to list the available commands to the network administrator.
pas
Change Network Administrator Password
Syntax pas “password”,”password” Return !-223,INVALID PASSWORD !-224,NEW PASSWORD MISMATCH
Password rejected Passwords did not match
Description This command changes network administrator password. The password is sent twice in the command line in order to avoid mistakes. The password must have at least 6 characters but no more than 15 characters.
Issue 9 January 2008
113
Galaxy Gateway v3
sta
Report Status
Syntax sta obj,att where: obj,attr is an object-attribute pair. For example, net1,ip. Description This command reports the value of the configuration parameters in the system. A couple examples are listed below to illustrate how this command works. sta net1,ip sta net1,sub
- report network IP address - report network subnet mask
The command line would respond as follows for first command listed above. * sta net1,ip :NET1 IP=135.107.96.1 . *** _ The “***” in the example above is the user command line prompt. The line “:NET1” indicates that the information that follows is for the plant object. The line starting with “IP” identifies the IP address. The “.” line is the end-of-command identifier.
upgrade
Upgrade Software
Syntax upgrade a upgrade w
upgrade application code upgrade default web pages
Return See description Description This command initiates an upgrade. After entering this command the Galaxy Gateway responds with a prompt similar to the following: Upgrade Application Code 1 - 9600 baud 2 - 19200 baud 3 - 38400 baud 4 - 57600 baud 5 - 115200 baud 0 - cancel Please enter choice:_
Issue 9 January 2008
114
Galaxy Gateway v3
If you choose 0, the upgrade is cancelled and the Galaxy Gateway returns to the command line. If one of the other options is chosen, then the upgrade process continues. While upgrading the application code, messages similar to the following are displayed: Please wait...begin upload at 38400 baud Uploaded checksum...passed Programming devices...done Final checksum...passed Please return to 9600 baud and press enter
T1.317 Error Messages The following are error message that may be encountered while logging into the system or entering commands: !-112,SYNTAX ERROR !-221,EXCESSIVE LOGIN ATTEMPTS !-223,INVALID PASSWORD !-224,NEW PASSWORD MISMATCH !-304,INVALID VALUE
Issue 9 January 2008
Command syntax is incorrect The wrong password was entered too many times when trying to login. An attempt was made to change the password to an invalid one. The first and second password entries did not match when attempting to change a password. An attempt was made to change an attribute to an invalid value.
115
Galaxy Gateway v3
Appendix F: TL1 (Transaction Language 1) Galaxy TL1 Configuration The TL1 interface is provided by the Galaxy SC and Millennium Intelligent Controller boards. Any existing objects in the controller can be retrieved or reported via TL1. Any object that is to be enabled for TL1 must be added and then linked to a TL1 object (see Section 7). The system supports up to 256 TL1 objects. You must configure the attributes of every TL1 object added. See Appendix G for a list of T1.317 objects and attributes. The following table describes the parameters required when configuring TL1 objects.
Description Condition Description Access Identification (AID) Condition Type
Service Affecting Reporting
Description Enable TCP/IP Port Number
Issue 9 January 2008
TL1 Managed Objects Up to 30 characters associated with the TL1 object ID. Up to 14 characters to describe the object when reporting the alarm or event. Up to 20 characters used to describe the access code which contains the information needed to access or address entities within the target NE. Up to 20 characters that tell the OS the type of alarm condition. For each TL1 channel, the user must configure the condition type for the alarm. “Yes” or “No” to tell the OS whether the alarm condition is service affecting or not. Classifies the object as an environment, equipment, or present type of alarm or event. TL1 Manager Up to 30 characters used to describe the name of the TL1 management system. Enable or disable the use of TL1 over TCP/IP. Port assignment for TL1 in the TCP/IP stack.
116
Galaxy Gateway v3
Telcordia Reference Documents The following Telcordia documents give the details of the communication architecture between network elements and the OS centers: • TR-TSY-000827 Operations Technology Generic Requirements (OTGR): Generic Operations Interfaces - Non-OSI Communications Architecture • TR-TSY-000828 Operations Technology Generic Requirements (OTGR): Generic Operations Interfaces - OSI Communications Architecture The message format and other details about TL1 are available in the following Bellcore documents: • TR-TSY-000831 Operations Technology Generic Requirements (OTGR): Operations Application Messages - Language for Operations Application Messages • GR-833-CORE Operations Technology Generic Requirements (OTGR): Network Maintenance: Network Element and Transport Surveillance Messages • TR-NWT-000835 Operations Technology Generic Requirements (OTGR): Operations Application Messages - Network Element and Network System Security Administration Messages
Issue 9 January 2008
117
Galaxy Gateway v3
Appendix G: Safety Safety Statements Please read and follow all safety instructions and warnings before installing, maintaining, or repairing the Galaxy Controller. Also refer to the peripheral monitoring system product manual for safety statements related to the installation and use of these devices. The Global Power System (including the peripheral monitoring modules) is Listed by Underwriters Laboratories Inc. to the requirements of UL Subject 1801 as a controller for use with DC Power Distribution Centers for Communications Equipment. The Listing is based on the items noted below. Install only in restricted access areas (dedicated equipment rooms, equipment closets, or the like) in accordance with articles 110-16, 110-17, and 110-18 of the U.S. National Electric Code (NEC), ANSI/NFPA No. 70, and pursuant to applicable local codes. This equipment is to be used in controlled environments (an area where the humidity is maintained at levels that cannot cause condensation on the equipment, the contaminating dust is controlled, and the steady-state ambient temperature is within the range specified). This equipment has been evaluated for use in a continuous ambient temperature of up to 50° C. This equipment must not be installed over combustible surfaces. This equipment is to be connected to 24Vdc or 48Vdc systems that are electrically isolated from the ac mains and are reliably earth grounded, or connected to systems where the rectifiers were evaluated to UL1950 and identified as Safety Extra Low Voltage (SELV) outputs.
Issue 9 January 2008
118
Galaxy Gateway v3
Warning and Safety Symbols The symbols may sometimes be accompanied by some type of statement; e.g., “Hazardous voltage/energy inside. Risk of injury. This unit must be accessed only by qualified personnel.” Signal words as described below may also be used to indicate the level of hazard.
DANGER
WARNING
CAUTION
Indicates the presence of a hazard that will cause death or severe personal injury if the hazard is not avoided. Indicates the presence of a hazard that can cause death or severe personal injury if the hazard is not avoided. Indicates the presence of a hazard that will or can cause minor personal injury or property damage if the hazard is not avoided. This symbol identifies the need to refer to the equipment instructions for important information. These symbols (or equivalent) are used to identify the presence of hazardous ac mains voltage. This symbol is used to identify the presence of hazardous ac or dc voltages. It may also be used to warn of hazardous energy levels. One of these two symbols (or equivalent) may be used to identify the presence of rectifier and battery voltages. The symbol may sometimes be accompanied by some type of statement, for example: “Battery voltage present. Risk of injury due to high current. Avoid contacting conductors with uninsulated metal objects. Follow safety precautions.” One of these two symbols may be used to identify the presence of a hot surface. It may also be accompanied by a statement explaining the hazard. A symbol like this with a lightning bolt through the hand also means that the part is or could be at hazardous voltage levels. This symbol is used to identify the protective safety earth ground for the equipment. This symbol is used to identify other bonding points within the equipment.
This symbol is used to identify the need for safety glasses and may sometimes be accompanied by some type of statement, for example: “Fuses can cause arcing and sparks. Risk of eye injury. Always wear safety glasses.”
Issue 9 January 2008
119
Galaxy Gateway v3
Precautions When working on or using this type of equipment, the following precautions should be noted: • This unit must be installed, serviced, and operated only by skilled and qualified personnel who have the necessary knowledge and practical experience with electrical equipment and who understand the hazards that can arise when working on this type of equipment. • Hazardous energy and/or voltages may be present in the unit and on the interface cables that can shock or cause serious injury. Follow all safety warnings and practices when servicing this equipment. In addition to proper job training and safety procedures, the following are some basic precautions that should always be used: ° Use only properly insulated tools. ° Remove all metallic objects (key chains, glasses, rings, watches, or other jewelry). ° Wear safety glasses. ° Test circuits before touching. ° Lock out and tag circuit breakers/fuses when possible to prevent accidental turn on. ° Be aware of potential hazards before servicing equipment. ° Identify exposed hazardous electrical potentials on connectors, wiring, etc. (note the condition of these circuits, especially wiring). ° Use care when removing or replacing covers; avoid contacting circuits. ° Electricity produces magnetic fields that can affect implanted electronic medical devices. The strength of the magnetic field depends on the amount of current in the circuit, as well as other conditions (such as: number of conductors, placement, and distance from the conductor). DC power and distribution systems, including the batteries, which are typically used in telecommunication utility rooms can operate at high current levels. Personnel with electronic medical devices need to be aware of their restrictions when working around electricity.
Issue 9 January 2008
120
Galaxy Gateway v3
Appendix H: Product Warranty A. Seller warrants to Customer only, that: 1
As of the date title to Products passes, Seller will have the right to sell, transfer, and assign such Products and the title conveyed by Seller shall be good;
2
During the warranty period stated in Sub-Article B below, Seller’s Manufactured Products (products manufactured by Seller), which have been paid for by Customer, will conform to industry standards and Seller’s specifications and shall be free from material defects;
3. With respect to Vendor items (items not manufactured by Seller), Seller warrants that such Vendor items, which have been paid for by Customer, will be free from material defects for a period of sixty (60) days commencing from the date of shipment from Seller’s facility. B. The Warranty Period listed below is applicable to Seller’s Manufactured Products furnished pursuant to this Agreement, commencing from date of shipment from Seller’s facility, unless otherwise agreed to in writing: Warranty Period Product Type Central Office Power Equipment
New Product
Repaired Product
24 Months
6 Months
* The Warranty Period for a repaired Product or part thereof is six (6) months or, the remainder of the unexpired term of the new Product Warranty Period, whichever is longer.
C. If, under normal and proper use during the applicable Warranty Period, a defect or nonconformity is identified in a Product and Customer notifies Seller in writing of such defect or nonconformity promptly after Customer discovers such defect or nonconformity, and follows Seller's instructions regarding return of defective or nonconforming Products, Seller shall, at its option attempt first to repair or replace such Product without charge at its facility or, if not feasible, provide a refund or credit based on the original purchase price and installation charges if installed by Seller. Where Seller has elected to repair a Seller’s Manufactured Product (other than Cable and Wire Products) which has been installed by Seller and Seller ascertains that the Product is not readily returnable for repair, Seller will repair the Product at Customer’s site. With respect to Cable and Wire Products manufactured by Seller which Seller elects to repair but which are not readily returnable for repair, whether or not
Issue 9 January 2008
121
Galaxy Gateway v3
installed by Seller, Seller at its option, may repair the cable and Wire Products at Customer’s site. D. If Seller has elected to repair or replace a defective Product, Customer shall have the option of removing and reinstalling or having Seller remove and reinstall the defective or nonconforming Product. The cost of the removal and the reinstallation shall be borne by Customer. With respect to Cable and Wire Products, Customer has the further responsibility, at its expense, to make the Cable and Wire Products accessible for repair or replacement and to restore the site. Products returned for repair or replacement will be accepted by Seller only in accordance with its instructions and procedures for such returns. The transportation expense associated with returning such Product to Seller shall be borne by Customer. Seller shall pay the cost of transportation of the repaired or replacing Product to the destination designated by Customer. E. Except for batteries, the defective or nonconforming Products or parts which are replaced shall become Seller's property. Customer shall be solely responsible for the disposition of any batteries. F. If Seller determines that a Product for which warranty service is claimed is not defective or nonconforming, Customer shall pay Seller all costs of handling, inspecting, testing, and transportation and, if applicable, traveling and related expenses. G. Seller makes no warranty with respect to defective conditions or nonconformities resulting from actions of anyone other than Seller or its subcontractors, caused by any of the following: modifications, misuse, neglect, accident, or abuse; improper wiring, repairing, splicing, alteration, installation, storage, or maintenance; use in a manner not in accordance with Seller’s or Vendor’s specifications or operating instructions, or failure of Customer to apply previously applicable Seller modifications and corrections. In addition, Seller makes no warranty with respect to Products which have had their serial numbers or month and year of manufacture removed, altered, or experimental products or prototypes or with respect to expendable items, including, without limitation, fuses, light bulbs, motor brushes, and the like. Seller’s warranty does not extend to any system into which the Product is incorporated. This warranty applies to Customer only and may not be assigned or extended by Customer to any of its customers or other users of the Product. THE FOREGOING WARRANTIES ARE EXCLUSIVE AND ARE IN LIEU OF ALL OTHER EXPRESS AND IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMER’S SOLE AND EXCLUSIVE REMEDY SHALL BE SELLER’S OBLIGATION TO REPAIR, REPLACE, CREDIT, OR REFUND AS SET FORTH ABOVE IN THIS WARRANTY.
Issue 9 January 2008
122
Galaxy Gateway v3
Revision History Issue 9 Rebranding.
Issue 8 Updated with latest web pages and clarifications for several sections.
Issue 9 January 2008
123
Galaxy Gateway v3
Issue 9 January 2008
124
