Ethernet communications for power monitoring system

[0001] This invention is directed generally to the power monitoring arts, and more particularly, to an Ethernet communication system for use with a power monitoring device.

[0002] While the invention may find other uses, the embodiment described herein is configured for use with a POWERLOGIC® power monitoring and control system which combines microprocessor-based instrumentation and control with internet software to provide information from an electrical distribution system. The system has such capabilities as alarm reporting, automatic control, high-accuracy instrumentation, power quality and disturbance monitoring and data sharing.

[0003] Heretofore, the communications for this POWERLOGIC system were provided by an Ethernet gateway device, which was a stand-alone device capable of communicating through an RS485 daisy chain with one or more power monitoring and/or control devices. The Ethernet gateway device (EGW) did not include a Hyptertext transfer protocol server, and hence was unable to communicate with HTML pages of browsers or other servers. The EGW uses an MMS (Manufacturing Message Specification) protocol capable of 10 MBS communications on the Ethernet side. Essentially, the EGW provided a gateway device only. While the EGW has found widespread acceptance in the market, there is room for further improvement. The Ethernet communications device and system of the present invention presents such an improvement.

[0004] Briefly, in accordance with the foregoing, an Ethernet communications system for a power monitoring system comprises a processor capable of functioning as a master device, a communications interface capable of gathering, under control of said processor real-time information from one or more slave devices, said processor and said communications interface further being operative for presenting said real-time information in a format useable by Hypertext Markup Language (HTML) pages.

[0005] In another embodiment of the invention, an industrial power metering device comprises a power monitoring device, and an Ethernet communications device operatively coupled with said power monitoring device, said Ethernet communications device including a processor and a communications interface capable, under control of said processor, of gathering real-time information from said power monitoring device; and a web server capable of communicating through said communications interface for dynamically gathering, formatting and verifying real-time information from the power monitoring device.

[0006] In another embodiment of the invention, an Ethernet communications method for a power monitoring system comprises gathering real-time information from said power monitoring system and presenting said real-time information in a format useable by Hypertext Markup Language pages.

[0014] Referring now to the drawings, and initially to FIG. 1, in accordance with one embodiment of the invention, an Ethernet communications device comprises a Circuit Monitor 3000/4000 series Ethernet Communications Card (ECC) 20 is an installable option card, which can be utilized by the Square D CM3000/4000 series of meters (CM) 22. This option card will allow the meters to be accessed over Ethernet media and provide a Gateway function by allowing Ethernet access to other Square D PowerLogic compatible Modbus, Jbus, and/or SyMax slave RS485 devices.

[0015] The ECC provides a fast, direct Ethernet communication connection for the Series 4000 Circuit Monitor and allow Ethernet gateway functionality to a wide variety of POWERLOGIC-compatible MODBUS, JBUS, and/or SY/MAX devices. A typical application example is shown in FIG. 3.

[0016] The ECC allows access to custom HTML pages (stored in the circuit monitor) via a standard web browser. The pages are best viewed using Internet Explorer version 5.0 or higher. These HTML pages may display information from the host circuit monitor and/or daisy-chained devices.

[0017] In FIG. 3, a POWERLOGIC System Manager 40 and a and a Standard Web Browser 42 are coupled to an Ethernet Network 44. One or more Series 4000 Circuit Monitor 22 with ECC 20 and NOE Ethernet Cards 46 may be coupled to the network 44 by means of a MODBUS® TCP/IP 48. The Series 4000 Circuit Monitors 22 may be daisy chained with the power monitoring devices, such as circuit monitors 50, power meters 52 and Enercept® meters 54 via the ECC's 20.

[0018] The RS-485 serial port 210 of the ECC 20 is used for communications with daisy-chained devices and is designed to support up to 31 defined devices without a repeater (FIG. 4), or up to 63 defined RS-485 devices with a repeater. The RS-485 enables communications via a 4-wire plus shield cable (Tx+, TX−, RX++, RX−, and Shld). It can also be configured for 2-wire plus shield.

[0019] For a 4-wire communication, Belden 8723 or 9842 cable or equivalent is recommended. For 2-wire communication, Belden 9841 or equivalent is recommended. If Enercept® meters are on the daisy chain, use Belden 1120A or equivalent.

[0020] The ECC 22 has two on-board Ethernet ports (see FIG. 1) 10/100Base TX Twisted Pair 112 and 100Base Fx 114. FIG. 5 shows a typical network application.

[0021] Table 1 below illustrates a number of functions of the ECC.

[0022]

TABLE 1
ECC General Functionality
	High-speed, direct Ethernet communications to the CM the
ECC is inserted into
	RS485 support for up to 31 PowerLogic compatible,
Modbus, Jbus, and/or SyMax slave devices
	RS485 2 and 4-wire communications with parity as even
or none up to 38.4K baud
	10/100baseT Ethernet twisted pair (TP) communications support
	100baseFx Ethernet (Fiber) communications
	Access to attached slave devices from client Modbus/TCP Ethernet
communications
	ECC setup/configuration/diagnostics by password protected HTML
Ethernet communications
	ECC firmware download by password protected FPT Ethernet
communications
	HTML custom device table download by password protected FTP
Ethernet communications
	Multi-lingual HTML support
	ECC setup/configuration download by password protected FTP
Ethernet communications
	Access to attached devices from client MMS/TCP Etherenet
communications
	Time synchronization to attached slave devices by SNTP Ethernet
communications
	Ability for CM/Sub-net master initiated communications

[0023] Microprocessor

[0024] The microprocessor or CPU 100 in the illustrated embodiment (see FIG. 2) is the NET silicon NET+ARM−40. This hardware architecture was developed by NET silicon to optimize network performance. The microprocessor 100 can run at 15 MIPS (million Instructions Per Second) but can actually reach 30 MIPS peak performance with the correct peripherals and configuration of the onboard 4K cache. The internal frequency is 33 MHz driven by the external clock generator at 18.432 MHz. The external bus speed is 33 MHz. The following is a list of the main components contained in the NET+ARM chip that is utilized in the design.

[0025] 32 bit 3.3V ARM7TDMI RISC Processor (not 5V tolerant)

[0026] 10/100 Ethernet MAC

[0027] Glueless interface to 8, 16, and 32 bit peripherals

[0028] 10 Channel DMA Controller

[0029] 1 of 2 Asynchronous Serial Ports with FIFO

[0030] 5 programmable chip selects

[0031] Programmable wait states

[0032] DRAM refresh controller

[0033] 2 programmable timers

[0034] Programmable watchdog timer

[0035] Programmable Phase Lock Loop (PLL)

[0036] ARM embedded MULTI-ICE JTAG (not to be confused with 1149.1 JTAG Testing)

[0037] Chip Selects

[0038] Various peripheral devices are connected to one of five programmable chip selects. These chip selects can be configured for 8, 16, or 32 bit peripherals. The following is a table of how the chip selects are configured for use

[0039]

TABLE 2
Chip Selects
Chip Select	Peripheral	Wait States	Start Address	Size	Width
CS0	Flash (102)	1	0x0000000	1 Mbyte	16
CS1	DRAM RAS 1 (104)	0	0x1000000	4 Mbytes	32
CS2	—	—	—	—	—
CS3	EEPROM (106)	4	0x2000000	8 Kbytes	8
CS4	Dual Port RAM (108)	0	0x3000000	2 Kbyte	8

[0040] Input/Output Pins

[0041] There are three ports of eight signals that can be configured to be used for either general purpose I/O bits, asynchronous serial channel signals, or interrupt inputs. Each port's signals can be configured independently. The following is a table of how the ports' signals are used.

[0042]

TABLE 3
Input/Output Pins
Signal	Type	Description
PortA0	—	Not used
PortA1	—	Not used
PortA2	—	Not used
PortA3	RXDA	Receive data serial channel A signal
PortA4	—	Not used
PortA5	RTSA	Request to send serial channel A signal
PortA6	—	Not used
PortA7	TXDA	Transmit data serial channel A signal
PortB0	—	Not used
PortB1	—	Not used
PortB2	—	Not used
PortB3	—	Not used
PortB4	—	Not used
PortB5	—	Not used
PortB6	—	Not used
PortB7	—	Not used
PortC0	Interrupt Input	External interrupt input signal
		for the Ethernet PHY
PortC1	Output	Output signal for serial channel A
		transmit LED
PortC2	Output	Output signal for serial channel A receive LED
PortC3	Interrupt Input	External interrupt input signal for the
		dual port RAM
PortC4	HDRS	Hardware reset output signal for soft resets
PortC5	Input	Optional Ethernet fiber transceiver detection
		input signal
PortC6	Input	Ethernet link input status signal
PortC7	—	Not used

[0043] Fast Media Access Controller (MAC)

[0044] The NET+ARM has an integrated 10/100 Mbit Media Access Controller (MAC) for Media Independent Interfaces (MII). This interface is utilized in conjunction with an external Fast Ethernet PHY (Physical Interface) 110 to allow for 10/100 Mbit TP and 100 Mbit Fiber communications.

[0045] Memory

[0046] Memory is commonly referred to as volatile and non-volatile types. The ECC is designed using memory peripherals of both types. It has 4 Mbytes of DRAM 104 and 2 Kbytes of Dual Port RAM 108. Both of these peripherals are of the volatile memory type. It has 1 Mbytes of Flash 102 and 8 Kbytes of EEPROM 106. Both of these peripherals are of the non-volatile memory type. The following table shows the memory ranges for the peripherals used in the design of the ECC.

[0047]

TABLE 4
Memory Map
Peripheral	Type	Size	Memory Range
Program Storage Flash (102)	Non-	1 Mbytes	0x0000000-
	Volatile		0x00F9FFF
Program Execution/Stack DRAM	Volatile	4 Mbytes	0x1000000-
(104)			0x13E7FFF
Configuration storage EEPROM	Non-	8 Kbytes	0x2000000-
(106)	Volatile		0x2001FFF
Inter-processor Communications	Volatile	2 Kbytes	0x3000000-
DPRAM (108)			0x30007FF

[0048] Flash

[0049] The Flash peripheral 102 is used for program (firmware) storage. At boot-up, the program code will be copied into DRAM for fast execution. The Flash is an 8 Mbit (512K×16) part with an access time of 90 ns.

[0050] Dram

[0051] The DRAM peripherals (104) are used for program execution, stack space, and firmware downloads. There are two 16 Mbit (1M×16) DRAM peripherals with access times of 50 ns. These two peripherals are used together to allow for 32 bit wide data bus accesses by the processor. This combination of bus size and fast access speeds will allow for maximum execution of the processor with zero wait states.

[0052] EEPROM

[0053] The EEPROM peripheral 106 is used for limited configuration storage relevant to each particular ECC. Probably, the most important information is the Ethernet Media Access Controller (MAC) address. The EEPROM 106 is a 64 Kbit (8K×8) part with an access time of 200 ns.

[0054] Dual Port RAM

[0055] The dual port RAM peripheral 108 is used for the high-speed inter-processor communications between the ECC and the CM3000/4000 series devices. The dual port RAM is a 16 Kbit (2K×8) part with an access time of 55 ns. This speed will allow access to this peripheral with no wait states at the full speed of the processor.

[0056] Other Peripherals and Components

[0057] There are a few other peripherals and components that are used to complete the ECC. These peripherals complement the processor and memory to allow for the fulfillment of all the functional requirements implemented.

[0058] RS485 Interface

[0059] The RS485 communications interface 112 is a 4-wire plus shield interface (Tx+, Tx−, Rx+, Rx−, and Shld). This interface has electrical isolation to internal circuitry up to 7500 Vac(pk) for duration of one second or less by means of optical isolation and DC-to-DC converter. The transceiver used is protected against 15 kV electrostatic discharge (ESD) shocks using the Human Body Model. Also, the transceiver features reduced slew-rate drivers that minimize Electromagnetic Interference (EMI) and reduce reflections caused by improperly terminated cables.

[0060] The connector used to wire into this interface is a 5-point screw type commonly known as a “Phoenix” or “Terminal Block” connector.

[0061] Like all RS485 daisy chains (see FIG. 3), correct biasing is required to ensure reliable communications. Traditionally, a Multipoint Communications Adapter (MCA) is used at the beginning/master of the daisy chain. This adapter circuitry is built into the ECC so no adapter will be needed externally. This internal biasing is calculated based on the daisy chain always being terminated and on using cabling with a 120 ohm impedance characteristic (Belden cable 9842). Also, RS485 daisy chain termination is required to ensure reliable communications. The last device on the daisy chain usually needs to have a Multipoint Communications Terminator (MCT). Ideally, the last device on the daisy chain should have a termination resistor of 120 ohms across its receive plus and minus pair only.

[0062] The RS485 interface is designed to support up to 31 slave RS485 4-wire devices. The “guaranteed” maximum number of devices capable of being supported on a single daisy chain is determined based on the relation of baud rate, the length of the daisy chain, and the types of slave RS485 devices (2-wire/4-wire). The RS485 interface will support daisy chains that fall within the following specifications.

[0063]

TABLE 5
4-wire RS485 Distances
Baud
Rate	Max distance for 1-16 devices	Max distance for 17-32 devices
1200	10,000 ft (3,048 m)	10,000 ft (3,048 m)
2400	10,000 ft (3,048 m)	5,000 ft (1,524 m)
4800	10,000 ft (3,048 m)	5,000 ft (1,524 m)
9600	10,000 ft (3,048 m)	4,000 ft (1,219 m)
19200	5,000 ft (1,524 m)	2,500 ft (762 m)
38400	5,000 ft (1,524 m)	1,500 ft (457 m)

[0064]

TABLE 6
2-wire RS485 Distances
Baud Rate	Max distance for 1-8 devices	Max distance for 9-16 devices
1200	10,000 ft (3,048 m)	10,000 ft (3,048 m)
2400	10,000 ft (3,048 m)	5,000 ft (1,524 m)
4800	10,000 ft (3,048 m)	5,000 ft (1,524 m)
9600	10,000 ft (3,048 m)	4,000 ft (1,219 m)
19200	5,000 ft (1,524 m)	2,500 ft (762 m)
38400	2,500 ft (1,524 m)	1,500 ft (457 m)

[0065] Fast Ethernet Physical (PHY) Transceiver Interface

[0066] The Fast Ethernet Transceiver (PHY) 110 provides a Media Independent Interface (MII) for easy attachment to the 10/100 Media Access Controller (MAC) which is integrated into the NET+ARM processor. The PHY is capable of directly driving an RJ45 interface through magnetics and termination resistors. The PHY also provides a pseudo-ECL interface for use with 100BaseFX fast fiber transceivers.

[0067] 10/100BaseTX Interface (RJ45)

[0068] The RJ45 112 interface uses two signal pairs (one for transmit and one for receive) and a center tap for the transmit transformer. These same signal pairs, magnetics, and termination resistors are used for both 10 Mbit and 100 Mbit operation. This interface can drive a twisted pair cable up to 100 m (328 ft) in length when using data grade twisted-pair wire that has a characteristic impedance of 100 ohms and meets the EIA/TIA Category Five standard wire specifications.

[0069] The cable used can be either shielded twisted pair (STP) or unshielded twisted pair (UTP). Great care should be taken here to not use IBM type 1 cabling, which is STP at 150 ohm. In the past, STP meant IBM 150 ohm cabling. Today, there is Cat 5 shielded cabling which is 100 ohm. In the USA, the cable type used is usually unshielded, in Europe it is often shielded. Most shielded 4 pair cables used today are 100 ohm, either with overall foil shield (FTP) or individually shielded pairs within a braided sheath (ScTP) Most of the industry appears to be going to ScTP.

[0070] The RJ45 interface is capable of auto negotiation for speed and duplex mode. If the link partner is also capable of auto negotiation, the two devices will exchange Fast Link Pulse (FLP) bursts to communicate their capabilities to each other. The highest common capabilities of the two will then be agreed upon. If the link partner is not capable of auto negotiation, the partner will be transmitting either 10 Mbits Normal Link Pulses (NLP) or 100 Mbit idle symbols. The RJ45 interface will detect either NLPs or Idle symbols and will automatically configure itself to match the speed but only in half-duplex mode.

[0071] The magnetics used here are determined by the requirements of the Fast Ethernet Physical (PHY) transceiver, for example, a transformer module with a “transmit turns ratio” of 1:1.

[0072] Fast Fiber Transceiver

[0073] The Fast Fiber Transceiver 114 is compliant with the optical performance requirements of the physical layer of the 100BaseFX version of the IEEE 802.3u specifications. This specification is defined as the FDDI PMD Standard ISO/IEC 9314-3:1990 and ANSI X3.166-1990.

[0074] The transceiver has a duplex LC connector receptacle and is compatible with 1300 nm wavelength multimode fiber connections. It is optimized for 62.5 or 50/125 micron multimode graded index glass optical fiber per TIA-568A and ISO 11801. Also, the transceiver is capable of signal integrity up to 2000 m in length of multimode full duplex fiber.

[0075] A few things to note, there is no industry standard for auto-negotiation on 100BaseFX. To use this interface, the user will have to force this mode by means of the setup interface. It may be possible to auto-negotiate to 100BaseFX with logic in the Firmware. Also, this interface does not support 10FL (10 Mbits fiber) applications.

[0076] This component is presently the most expensive one in the design. The board will be designed to have the ability to detect if this component is present or not. This will allow for the manufacture of two types of boards if needed. The primary board will have the fast fiber transceiver populated and will allow for the use of the twisted pair or the fiber interface. The secondary board will not have the fast fiber transceiver populated and will allow for the use of only the twisted pair interface.

[0077] Light Emitting Diodes (LEDs)

[0078] There are two tri-level LED indicators 24, 26 (see FIG. 1). The first one 24 will be of color green/green/yellow (Tri-level 1), and the other one 26 will be of color yellow/green/yellow (Tri-level 2). The following table shows what each individual LED represents.

[0079]

TABLE 7
LED Descriptions
Unit and Color	Description
Tri-level 1 green	Power is being received from the source (CM)
Tri-level 1 green	RS485 Transmit in progress
Tri-level 1 yellow	RS485 Receive in progress
Tri-level 2 yellow	Ethernet link good
Tri-level 2 green	Ethernet Transmit in progress
Tri-level 2 yellow	Ethernet Receive in progress

[0080] Circuit/Processor Reset

[0081] The overall circuit board power is kept in check by a voltage monitor 202 (see FIG. 6). This device monitors three vital system conditions. It monitors the 5-volt supply from the CM 22, the 3.3-volt supply from the CM, and the external override/reset controlled by the CM.

[0082] When an out-of-tolerance condition is detected on either of the voltages, this device will reset the board 200. This capability helps ensure against firmware corruption and other “flaky” operations that occur due to out-of-tolerance power events.

[0083] Also, this device will allow an easy way for the CM to be able to control the board in the need of a reset.

[0084] Power Supply

[0085] The ECC does not have its own power supply. The ECC will receive its power requirements from the CM it is inserted into. The CM will need to supply +5 Vdc and +3.3 Vdc to the ECC through the Option slot connectors 204. The amount of the supply is based on the following feasibility study.

[0086]

TABLE 8
ECC Estimated Power Consumption
		Typical	Maximum
Quantity	Description	Power (mW)	Power (mW)
1	Fast Fiber LC Connector	165	165
1	IC, NETA 40-3	330	495
1	IC, Altima PHY	280.5	330
1	IC, 8 Mbit Flash Memory	49.5	99
2	IC, 1M × 16 (16-MBIT)	957	1056
	DRAM
1	IC, 8K × 8 EEPROM	0.165	26.4
1	IC, 1K × 8 Dual-Port RAM	247.5	297
1	Crystal, 18.432 MHZ SMT
1	Crystal, 25 MHZ SMT
1	Microprocessor Reset	0.25	0.25
3	Opto Isolator	375	600
1	DC/DC Converter	400	625
1	RS485 Dual Driver/Receiver	0.6	5
1	Single Port Xformer
1	PCB RJ-45 Shielded Jack
1	Tri-Level LED
1	Tri-Level LED
1	5 Position Terminal Plug
1	5 Position Terminal Plug
1	Connector 48Pin Eurocard
1	Misc Passive/PCB	49.5	108.9
	Twisted Pair Only Total >	2690.015	3642.55
	Total >	2855.015	3807.55
	3.3V Burden Total >	2079.165	2577.3
	5V Burden Total >	775.85	1230.25

[0087] Mechanical

[0088] The size and dimensions of the ECC has already been pre-determined by the specifications of the option slots in the CM. The FIGS. 6 and 7 and Table 9 show the board layout.

[0089]

TABLE 9
Component Key for Mechanical Feasibility Drawing
Key #	Quantity	Component	Key #	Quantity	Component
102	1	Flash	208	1	DC to DC
202	1	Reset	104	2	Dram
203	2	Crystal	210	1	Terminal Block
110	1	PHY	106	1	EEProm
112	1	RS485	108	1	Dual Port Ram
114	1	Fiber	212	3	Optocouplers
206	1	Transformer	204	1	Eurocard
					Connector
112	1	RJ45	214	1	Jtag Connector
24, 26	2	LEDs	216	1	Bus Switch
100	1	CPU

[0090] Ethernet Communications

[0091] Ethernet communications will be utilized, wherever possible and feasible to do so, to allow for the “remote” control/maintenance of the ECC. The goal of this design is to make the ECC a passive/reactive device requiring minimal setup. The ECC will basically react to the “outside” world and do what it “thinks” is the best thing to do unless configured to do something different via setup. The Ethernet capabilities will be primarily used for ECC setup, diagnostics, firmware update, and access to attached slave devices by means of Hypertext Markup Language (HTML) and Hypertext Transfer Protocol (HTTP), File Transfer Protocol (FTP), Modbus over TCP/IP (ModbusTCP), and future plans for Manufacturing Message Specification over TCP/IP (MMSTCP).

[0092] HTTP Server and HTML Pages

[0093] A small subset of HTML v1.0 will be used with the HTTP server in the ECC primarily for ECC setup and diagnostics. With the onset and popularity of the World Wide Web and the Internet, the use of a browser is practically commonplace. This capability of the ECC allows for almost any user of an Internet browser to easily access and configure the ECC device. The recommended browser of choice should be Internet Explorer v5.0 or greater.

[0094] FIG. 8 shows one embodiment of the ECC's HTML flow page.

[0095] HTML Security

[0096] The ECC's HTML security allows for four configurable account password access levels. These password access levels will be divided into three Password Accounts and one Administrator Account.

[0097] HTML Security Theory of Operation

[0098] When a user attempts to access the ECC for the first time during a web browser session, the ECC will force that user into the password logon page. Once there, the users will login to the ECC using one of the four defined passwords. During this login, the ECC will generate a random number and associate that password access level with it. The random number will then be the users “access token” and will automatically be appended to all the HTML page transactions during that session. This token will stay “alive” as long as the user keeps the session active by making requests to the ECC. Once this token is inactive for more than the default of ten minutes, the ECC will “expire” the token. The ECC will allow any combination, including redundant use, of all the passwords to allow up to ten access tokens to be active at any given time. This limits the number of active users viewing HTML pages to ten. The amount of time the ECC will wait during the inactivity period before “expiring” an access token will be configurable. For normal operations, it is recommended that the user return to the main links page and select to “log out” when fished interfacing with the ECC to immediately release that token slot for another user.

[0099] HTML Administrator Account

[0100] One of the four password accounts in the ECC will always be the Administrator password. This password account will always be granted full access to every HTML page available in the ECC and will also overlap to be the only password used for FTP operations. The only part of this account that is configurable is the password itself. The Administrator password will default to “admin”. The Administrator password will be from one to eight characters and stored in four registers like the following table.

[0101]

TABLE 10
Administrator Password Setup Parameters
Register*	HiByte	LoByte
514	Admin password ASCII character 1	Admin password ASCII character 2
515	Admin password ASCII character 3	Admin password ASCII character 4
516	Admin password ASCII character 5	Admin password ASCII character 6
517	Admin password ASCII character 7	Admin password ASCII character 8
*Register numbers used in the tables throughout this document are CM registers.

[0102] HTML User Password Accounts

[0103] Three of the four password accounts in the ECC will be left to be used only for HTML access and will be called the User Password Accounts. Only the Administrator Account sets up these passwords. The parts of these accounts that are configurable are the passwords themselves and the level of access each password will allow to each HTML page in the ECC. These passwords will be configurable to allow no access, view-only access, or full access to each individual HTML page in the ECC. These four passwords can be selectively given to and used by multiple users. The user passwords will default to “master”, “engineer”, and “operator”. The passwords will be from one to eight characters and stored in four registers each like the following tables

[0104]

TABLE 11
Pass1 Password Setup Parameters
Register	HiByte	LoByte
518	Pass1 password ASCII character 1	Pass1 password ASCII character 2
519	Pass1 password ASCII character 3	Pass1 password ASCII character 4
520	Pass1 password ASCII character 5	Pass1 password ASCII character 6
521	Pass1 password ASCII character 7	Pass1 password ASCII character 8

[0105]

TABLE 12
Pass2 Password Setup Parameters
Register	HiByte	LoByte
526	Pass2 password ASCII character 1	Pass2 password ASCII character 2
527	Pass2 password ASCII character 3	Pass2 password ASCII character 4
528	Pass2 password ASCII character 5	Pass2 password ASCII character 6
529	Pass2 password ASCII character 7	Pass2 password ASCII character 8

[0106]

TABLE 13
Pass3 Password Setup Parameters
Register	HiByte	LoByte
534	Pass3 password ASCII character 1	Pass3 password ASCII
		character 2
535	Pass3 password ASCII character 3	Pass3 password ASCII
		character 4
536	Pass3 password ASCII character 5	Pass3 password ASCII
		character 6
537	Pass3 password ASCII character 7	Pass3 password ASCII
		character 8

[0107] The access level each password will have to each HTML page will be held in four registers, totaling twelve. This means that each password will have four registers associated with it according to the following table.

[0108]

TABLE 14
Passwords Access Setup Parameters
Register	HiByte       LoByte
522	Pass1 Password HTML Page Access Bitmap (Most Significant Word)
523	Pass1 Password HTML Page Access Bitmap (2nd Most Significant Word)
524	Pass1 Password HTML Page Access Bitmap (2nd Least Significant Word)
525	Pass1 Password HTML Page Access Bitmap (Least Significant Word)
530	Pass2 Password HTML Page Access Bitmap (Most Significant Word)
531	Pass2 Password HTML Page Access Bitmap (2nd Most Significant Word)
532	Pass2 Password HTML Page Access Bitmap (2nd Least Significant Word)
533	Pass2 Password HTML Page Access Bitmap (Least Significant Word)
538	Pass3 Password HTML Page Access Bitmap (Most Significant Word)
539	Pass3 Password HTML Page Access Bitmap (2nd Most Significant Word)
540	Pass3 Password HTML Page Access Bitmap (2nd Least Significant Word)
541	Pass3 Password HTML Page Access Bitmap (Least Significant Word)

[0109] Within these registers, the bits are utilized to represent the access ability of each password to each HTML page. Each HTML page will be represented by two bits. This means that there can be up to thirty-two pages secured by one of four access levels. The following table shows the value representation of the access levels.

[0110]

TABLE 15
Password Access Values
	Bit Values	Access Level
	0x00	No access
	0x01	Reserved
	0x02	View only access
	0x03	Full access

[0111] The following table shows the representation of the access levels that the passwords have to each HTML page

[0112]

TABLE 16
Password HTML Access Bitmaps
Register	Bits	HTML page
522	15 and 14	Pass1 access to Home Page
522	13 and 12	Pass1 access to CM Instantaneous Readings View
522	11 and 10	Pass1 access to Custom Device Page 1 View
		(Future)
522	9 and 8	Pass1 access to Custom Device Page 2 View
		(Future)
522	7 and 6	Pass1 access to Custom Device Page 3 View
		(Future)
522	5 and 4	Pass1 access to Custom Device Page 4 View
		(Future)
522	3 and 2	Pass1 access to Custom Device Page 5 View
		(Future)
522	1 and 0	Pass1 access to Communication Settings Setup
523	15 and 14	Pass1 access to RS485 Daisy chain Device Setup
523	13 and 12	Pass1 access to Diagnostics
523	11 and 10	Pass1 access to MMS/ModbusTCP Server
		Security Setup (Future)
523	9 and 8	Pass1 access to Remote Device Connection
		Setup (Future)
523	7 and 6	Reserved
523	5 and 4	Reserved
523	3 and 2	Reserved
523	1 and 0	Reserved
524	15 and 14	Reserved
524	13 and 12	Reserved
524	11 and 10	Reserved
524	9 and 8	Reserved
524	7 and 6	Reserved
524	5 and 4	Reserved
524	3 and 2	Reserved
524	1 and 0	Reserved
525	15 and 14	Reserved
525	13 and 12	Reserved
525	11 and 10	Reserved
525	9 and 8	Reserved
525	7 and 6	Reserved
525	5 and 4	Reserved
525	3 and 2	Reserved
525	1 and 0	Reserved
530,		This format is duplicated for registers 530,
531,		531, 532, 533 (Pass2 access) and
532,		538, 539, 540, 541 (Pass3 access)
533,
538,
539,
540, 541

[0113] A Password Administration Setup HTML page will be provided. This page will be accessible by the administrator password only.

[0114] ECC Setup via HTML

[0115] All the setup information will be stored in the CM that the ECC is inserted into. This will allow for the ECCs to be “swappable”. The ECC setup will primarily be done with HTML pages, but the CM display will have to be used during the initial steps.

[0116] Initial Setup

[0117] After the physical installation, the first step to completing the ECC setup will be via the CM display. The CM display will be used to setup the initial TCP/IP address, TCP/IP subnet mask, the TCP/IP router, and the Ethernet physical connection to use (fiber or twisted pair). With these parameters in place, the ECC will be accessible via the Ethernet, and the rest of the ECC setup can be done via HTML and a standard web browser by FTP.

[0118] HTML Ethernet—TCP/IP Setup

[0119] After the one-time initial step of getting the TCP/IP address assigned to the ECC through the CM display, the ECC can, from that point on, have its TCP/IP setup changed with HTML pages and a standard web browser. The following is the information used for the TCP/IP setup.

[0120]

TABLE 17
TCP/IP Setup Parameters
Register	HiByte	LoByte
500	IP Address 1st Octet	IP Address 2nd Octet
	(0-255)	(0-255)
501	IP Address 3rd Octet	IP Address 4th Octet
	(0-255)	(0-255)
502	IP Sub-net Mask 1st Octet	IP Sub-net Mask 2nd Octet
	(0-255)	(0-255)
503	IP Sub-net Mask 3rd Octet	IP Sub-net Mask 4th Octet
	(0-255)	(0-255)
504	IP Router Address 1st Octet	IP Router Address 2nd Octet
	(0-255)	(0-255)
505	IP Router Address 3rd Octet	IP Router Address 4th Octet
	(0-255)	(0-255)
506	Ethernet physical connection (0 = UTP, 1 = Fiber)

[0121] An Ethernet TCP/IP Setup HTML page will show communication settings. An “Update” button will not be seen if the user has “view only” access.

[0122] HTML RS485 Device Definition Setup

[0123] Keeping in mind that the user should have to do as little setup as possible, all the devices on the daisy chain normally do not have to be defined. The ECC will be designed to function primarily as a passive Gateway. This means that the ECC will be able to pass through all Ethernet messages to the RS485 daisy chain based on the Ethernet protocol/format that the message was made. There are, however, scenarios in which this technique will not work, and the RS485 device must be defined so the ECC will be able to translate from one protocol to another. The devices that have to be selectively defined are PowerLogic protocol devices. PowerLogic protocol devices only have to be defined when a user wishes to communicate to them with the Ethernet protocol ModbusTCP. There will be a default list of 16 available device identification slots in the setup page interface for device definitions that will consist of an RS485 address and a protocol associated with it. The first entry will always show the slave address of the CM the ECC is inserted into. The following table shows the information used for defining a device.

[0124]

TABLE 18
RS485 Device Setup Parameters
Register	HiByte	LoByte
542	RS485 Device Definitions -	RS485 Device Definitions -
	Protocol (3 = PowerLogic,	Address (0-254)
	8 = Modbus)
543-604	62 more registers for up to 62 more Device definitions
605	Number of viewable defined devices, includes CM that the ECC
	is attached to (2-62)

[0125] One thing to note, the ECC will use the LoByte of these registers to build the route of 30, 130, x to communicate to daisy-chained PowerLogic slave devices. Otherwise it will be used as the daisy-chained Modbus/Jbus slave ID.

[0126] A RS485 Device Setup HTML page will be provided. An “Update” button will not be seen if the user has “view only” access.

[0127] HTML RS485 Setup

[0128] The RS485 Setup information will include baud rate, parity, and port mode. The following table shows the storage format of this setup information.

[0129]

TABLE 19
RS485 Setup Parameters
Register	HiByte	LoByte
512	RS485 Baud Rate
	(1200, 2400, 4800, 9600, 19200, 38400)
513	RS485 Parity	RS485 Mode
	(0 = none, 2 = even)	(0 = 4-wire Smart, 1 = 2-wire Smart)

[0130] An RS485 Serial Port Setup HTML page will show communications settings. An “Update” button will not be seen if the user has “view only” access.

[0131] HTML Remote Device Connection Setup

[0132] For sub-net initiated communications (the scenario where a serial master utilizes the ECC's RS485 port to gain access to remote locations/devices on the Ethernet, or the CM utilizes the ECC to gain access to remote locations/devices on the Ethernet), there has to be a way to define the remote nodes'locations. The ECC will have the ability to define up to ten remote Ethernet node locations. Also, the ECC will have the ability to define and associate up to eighty devices with these remote nodes. The following table is the format for the storage of the remote node/device information.

[0133]

TABLE 20
Remote Device Connection Setup Parameters
Registers	HiByte	LoByte
606	Associated	Remote Node	Device Address 100's
	Remote Node	Connection Type	ID to be used in the
	ID (0-9)	(1 = MMS SyMax	Ethernet transaction
		format Port 1	(0-247)
		2 = MMS SyMax
		format Port 2
		3 = MMS
		Modbus format
		Port 1
		4 = MMS
		Modbus format
		Port 2
		5 = ModbusTCP)
607-685	79 more registers for remote devices address 101 through 179
686	Remote Node ID 0 IP Address 1st	Remote Node ID 0 IP
	Octet	Address 2nd Octet
	(0-255)	(0-255)
687	Remote Node ID 0 IP Address 3rd	Remote Node ID 0 IP
	Octet	Address 4th Octet
	(0-255)	(0-255)
688-705	18 more registers worth for remote node IDs 1 through 9

[0134] The device initiating the communications will have to address to the ECC using addresses 100 through 179. These addresses will then serve as an identifier to “lookup” the information in that identifier's location. For Modbus initiators, the ECC will use the slave ID. For SyMax initiators, the ECC will use the last drop in the route. The information found in the location will then be used to make the Ethernet transaction. The following table shows the values for the connection types.

[0135]

TABLE 21
Remote Node Connection Types
Remote Node Connection Type	Description
1	MMS SyMax format Port 1
2	MMS SyMax format Port 2
3	MMS Modbus format Port 1
4	MMS Modbus format Port 2
5	ModbusTCP

[0136] A Remote Device Connections Setup HTML page will be provided. The Add/Change and Delete sections of the page will not be seen if the user has “view only” access.

[0137] HTML MMS/ModbusTCP Server Security Setup

[0138] The ECC can allow for the MMS/ModbusTCP server connections to have definable client access. This means that the IP addresses of the MMS/ModbusTCP clients will have to be defined in the ECC before the ECC will allow access for communications. This feature can be “turned on” in one of two ways. The first way is to turn it on so that all clients attempting to connect have read only access except for the defined clients that will have full access. The other way is to turn it on so all clients attempting to connect have no access except for the defined clients that will have a definable read only or full access. The ECC will have the ability to define ten clients.

[0139] Note: this mechanism works well until multiple clients access the ECC by way of a TCP/IP proxy server. In this scenario, all the clients would be connecting to the ECC with the same IP address (the one of the proxy server). Thus, the ECC would be checking access levels for multiple clients based on a single TCP/IP address.

[0140] The following table shows the format for the information for the client security access.

[0141]

TABLE 22
MMS/Modbus TCP Security Setup Parameters
Register	HiByte	LoByte
706	Client IP Address 0-1st Octet	Client IP Address
	(0-255)	0-2nd Octet (0-255)
707	Client IP Address 0-3rd Octet	Client IP Address
	(0-255)	0-4th Octet (0-255)
708-725	18 more registers for client IP addresses 1 through 9
726	Bits 15 and 14 signify how the	Bit 0 represents client
	security is turned on or if it is turned	0, bit 1 represents
	off.	client 1, through bit 9.
	(00 = Security off	(0 = Full Access, 1 =
	01 = Security on, all undefined	Read Only Access,
	clients have read only access and	these bits are ignored
	defined clients have automatic full	if bits 15 and 14 = 10)
	access
	10 = Security on, all undefined
	clients have no access and defined
	clients must have access level
	defined)

[0142] A MMS/Modbus TCP Security Setup HTML page will be provided. The “Update Settings” button will not be seen if the user has “view only” access.

[0143] HTML ECC Advanced Parameters Setup

[0144] The ECC will have an advanced parameters setup page that will be accessible by the administrator password only. This setup page will allow for advanced users to “tweak” ECC timing values that normally should never be changed. The administrator will also be able to change the default language the ECC will use at the login page. The following table shows the storage format for these values.

[0145]

TABLE 23
Advanced Setup Parameters
Register	HiByte	LoByte
507	ModbusTCP Client Timeout in	MMSTCP Client
	seconds	Timeout in seconds
	(5-60)	(5-60)
508	HTML Access token expiration time
	in minutes
	(1-255)
509	RS485 Timeout in seconds	DPR Timeout in
	(3-10)	seconds (3-10)
510	CM/RS485 Time Synchronization
	Interval in seconds
	(0 = disabled, 30-65535)
511	HTML default language type
	(0 = English, 1 = French, 2 = Spanish)

[0146] HTML Diagnostics View

[0147] The ECC will have the ability to accumulate diagnostics information for display to the user for troubleshooting or performance knowledge. Also, the ECC version information will be shown here. The counters and watermarks will be volatile and are shown in the following table.

[0148]

TABLE 24
ECC Diagnostic Counters/Watermarks
	RS485 Timeouts
	RS485 Checksum Errors
	RS485 Protocol Errors
	RS485 Outbound Read Messages
	RS485 Inbound Read Messages
	RS485 Outbound Write Messages
	RS485 Inbound Write Messages
	Dual Port Ram Timeouts
	Dual Port Ram Checksum Errors
	Dual Port Ram Protocol Errors
	Dual Port Ram Outbound Read Messages
	Dual Port Ram Inbound Read Messages
	Dual Port Ram Outbound Write Messages
	Dual Port Ram Inbound Write Messages
	MMS Timeouts (Future)
	MMS Protocol Errors (Future)
	MMS Outbound Read Messages (Future)
	MMS Inbound Read Messages (Future)
	MMS Outbound Write Messages (Future)
	MMS Inbound Write Messages (Future)
	MMS Inbound Connections (Future)
	MMS Outbound Connections (Future)
	MMS Active Inbound Connections (Future)
	MMS Active Outbound Connections (Future)
	MMS Maximum Inbound Connections (Future)
	MMS Maximum Outbound Connections (Future)
	ModbusTCP Timeouts
	ModbusTCP Protocol Errors
	ModbusTCP Outbound Read Messages
	ModbusTCP Inbound Read Messages
	ModbusTCP Outbound Write Messages
	ModbusTCP Inbound Write Messages
	ModbusTCP Inbound Connections
	ModbusTCP Outbound Connections
	ModbusTCP Active Inbound Connections
	ModbusTCP Active Outbound Connections
	ModbusTCP Maximum Inbound Connections
	ModbusTCP Maximum Outbound Connections
	Ethernet CRC Errors
	Ethernet Alignment Errors
	Ehernet Code Errors
	Ethernet Long Frame Errors
	Ethernet Short/Runt Frame Errors
	Ethernet Maximum Collision

[0149] An HTML Diagnostics View page will be provided. A “Reset” button will not be seen if the user has “view only” access.

[0150] Multilingual HTML

[0151] To be able to have the ECC available outside the United States and even more acceptable within, it will need to have all displays available in English, French, and Spanish. The user may choose a language for the browser session at login. The default language selection at login will be English, but the default language may be changed by entering the Advanced Setup HTML page with the administrator password. This means that all parts of the ECC firmware that has viewable strings will have to be designed in such a fashion to be displayed in multiple languages. The following table shows the storage of the HTML language type.

[0152]

TABLE 25
HTML Default Language
Register	HiByte	LoByte
511	HTML default language type
	(0 = English, 1 = French, 2 = Spanish)

[0153] A Login HTML page will be provided pertaining to being Multilingual.

[0154] HTML Home Page

[0155] The user will be transferred to the ECC home page after the login. Only the links that the user has access to will appear in the list.

[0156] HTML Real Time Data Device Tables

[0157] The ECC will have the capability to show limited, real time, tabular data from the attached devices to the users in the form of HTML pages. These pages will include one static page for viewing information from the CM the ECC is inserted into and the possibility for up to five custom/downloadable HTML pages for viewing devices on the local RS485 daisy chain. These pages will be stored in the CM that the ECC is inserted into and must not exceed 20 kilobytes in size each.

[0158] HTML CM Instantaneous Readings View

[0159] A CM device HTML real-time data table page will be configurable by the administrator password for view only or no access.

[0160] HTML Custom Device Readings Tables

[0161] The custom device tables will be available for use preferably by our Engineering Services group or by users very knowledgeable in the realm of HTML and JavaScript. The pages will be written in HTML with special delimiters that will tell the ECC to dynamically get register information from a device. Great care will have to be taken by the page author to try to get the optimal performance out of these pages and to keep the sizes within the allowed range. The delimiters at the beginning (PL_) and end (_PL) of a string signify to the ECC to parse this string and dynamically fill it with register data. The following Table 26 is a table of the supported PowerLogic tags and also, an HTML example of how they could be used.

[0162]

TABLE 26
PowerLogic HTML Tags
Func-
tion	Function
Code	Name	PowerLogic Tag
0	SyMax	<DeviceID>{circumflex over ( )}<RegisterAddress>[<NumberOfRegis
	Block	ters>]
	Read -	example tag =PL_1{circumflex over ( )}1003[5]_PL
	Registers	example of data returned = 85,86,84,25,56
4	SyMax	<DeviceID>{circumflex over ( )}<RegisterAddress1>,<RegisterAddre
	Scattered	ss2>,etc
	Read -	example tag =
	Registers	PL_1{circumflex over ( )}1003,1004,1005,1006,1007_PL
		example of data returned = 85,86,84,25,56
3	Modbus	<DeviceID>{circumflex over ( )}H<RegisterAddress>[<NumberOfRe
	Block	gisters>]
	Read -	example tag = PL_1{circumflex over ( )}H1003[5]_PL
	Holding	example of data returned = 85,86,84,25,56
	Registers
4	Modbus	<DeviceID>{circumflex over ( )}I<RegisterAddress>[<NumberOfRegi
	Block	sters>]
	Read -	example tag = PL_1{circumflex over ( )}I1003[5]_PL
	Input	example of data returned = 85,86,84,25,56
	Registers
100	Modbus	<DeviceID>{circumflex over ( )}S<RegisterAddress1>,<RegisterAddr
	Scattered	ess2>,etc
	Read -	example tag =
	Holding	PL_1{circumflex over ( )}S1003,1004,1005,1006,1007_PL
	Registers	example of data returned = 85,86,84,25,56

The following source code is one example of implementing Power Logic Tags in Javascript inside an HTML page.
Source:

[0163]

<html>
<head>
<META HTTP-EQUIV=“refresh” CONTENT=“5”>
<title>CM2350 - Slave Device 3</title>
</head>
<body>
<form name=“view_form”>
	<p align=“center”>
	<input type = “text” name = “time_spot” size = “40”>
	<table border=“1” width=“600”>
	<tr>
	<td width=“600”><p align=“center”><font size=“4”><b>CM2350
- Slave
	Device 3</b></font></p>
	</td>
	</tr>
	</table>
	<table border=“1” width=“600”>
	<tr>
	<td width=“300”>
	<p align=“center”>Frequency</p>
	</td>
	<td align=“center” width=“90”><p align=“center”><input
	type=“text” size=“5” name=“frequency”></p>
	<td width=“100”>
	<p align=“center”>Hz</p>
	</td>
	</tr>
	<tr>
	<td width=“300”>
	<p align=“center”>Current Phase A</p>
	</td>
	<td a1ign=“center” width=“90”><p align=“center”><input
	type=“text” size=“5” name=“currentphasea”></p>
	<td width=“100”>
	<p align=“center”>Amps</p>
	</td>
	</tr>
	<tr>
	<td width=“300”>
	<p align=“center”>Current Neutral</p>
	</td>
	<td align=“center” width=“90”><p align=“center”><input
	type=“text” size=“5” name=“currentneutral”></p>
	<td width=“100”>
	<p align=“center”>Amps</p>
	</td>
	</tr>
	<tr>
	<td width=“300”>
	<p align=“center”>Current Ground</p>
	</td>
	<td align=“center” width=“90”><p align=“center”><input
	type=“text” size=“5” name=“currentground”></p>
	<td width=“100”>
	<p align=“center”>Amps</p>
	</td>
	</tr>
	</table>
	<br><HR SIZE=“1” width=“66%”><CENTER><font face=“Times Roman”
	size=“2”>Copyright © 2000 SchneiderElectric. All rights
	reserved.</font></CENTER>
	</form>
	<script language=“JavaScript”>
	function ShowFreq( )
	{
	Registers = [PL_3{circumflex over ( )}2020,2021,2022,2025,1001,1003,1006,1007_PL];
	ScaleFactorA = Registers[0];
	ScaleFactorB = Registers[1];
	ScaleFactorC = Registers[2];
	ScaleFactorF = Registers[3];
	Frequency = Registers[4];
	CurrentPhaseA = Registers[5];
	CurrentNeutral = Registers[6];
	CurrentGround = Registers[7];
	ScaleFactorAMultiplier = 0;
	ScaleFactorBMultiplier = 0;
	ScaleFactorCMultiplier = 0;
	ScaleFactorFMultiplier = 0;
	TheTime = new Date( );
	switch (ScaleFactorA)
	{
	case −2:
	ScaleFactorAMultiplier = 0.01;
	break;
	case −1:
	ScaleFactorAMultiplier = 0.1;
	break;
	case 1:
	ScaleFactorAMultiplier = 10;
	break;
	default:
	ScaleFactorAMultiplier = 1;
	break;
	}
	switch (ScaleFactorB)
	{
	case −2:
	ScaleFactorBMultiplier = 0.01;
	break;
	case −1:
	ScaleFactorBMultiplier = 0.1;
	break;
	case 1:
	ScaleFactorBMultiplier = 10;
	break;
	default:
	ScaleFactorBMultiplier = 1;
	break;
	}
	switch (ScaleFactorC)
	{
	case −2:
	ScaleFactorCMultiplier = 0.01;
	break;
	case −1:
	ScaleFactorCMultiplier = 0.1;
	break;
	case 1:
	ScaleFactorCMultiplier = 10;
	break;
	default:
	ScaleFactorCMultiplier = 1;
	break;
	}
	switch (ScaleFactorF)
	{
	case −1:
	ScaleFactorFMultiplier = 0.1;
	break;
	default:
	ScaleFactorFMultiplier = 0.01;
	break;
	}
	Frequency *= ScaleFactorFMultiplier;
	CurrentPhaseA *= ScaleFactorAMultiplier;
	if (CurrentNeutral == −32768)
	CurrentNeutral = “N/A”;
	else
	CurrentNeutral *= ScaleFactorBMultiplier;
	if (CurrentGround == −32768)
	CurrentGround = “N/A”;
	else
	CurrentGround *= ScaleFactorCMultiplier;
	document.view_form.frequency.value = Frequency;
	document.view_form.currentphasea.value = CurrentPhaseA;
	document.view_form.currentneutral.value = CurrentNeutral;
	document.view_form.currentground.value = CurrentGround;
	document.view_form.time_spot.value = TheTime;
}
ShowFreq( );
</script>
</body>
</html>

[0164] ModbusTCP Server

[0165] The ECC will be able to provide the ModbusTCP server functionality to allow external ModbusTCP clients access to the ECC's attached slave devices and the CM the ECC is inserted into. The ECC will post TCP/IP connection listens on TCP port 502. The ECC will allow a maximum often ModbusTCP clients to connect at any given time.

[0166] The following table shows the supported ModbusTCP function codes the ECC will allow.

[0167]

TABLE 27
Modbus TCP Server Function Codes
Function Code	Sub-function Code	Description
1	X	Block Read - Coil Status
2	X	Block Read - Input Coil Status
3	X	Block Read - Holding Registers
4	X	Block Read - Input Registers
5	X	Single Write - Coil
6	X	Single Write - Holding Register
16	X	Block Write - Holding Registers
20	X	Block Read - General Reference/
		File
21	X	Block Write - General Reference/
		File
100	4	Scattered Read - Holding Registers
101	50	Set Time
102	X	Security Operations

[0168] MMSTCP Server

[0169] The ECC will be able to provide the MMSTCP (RFC-1006) server functionality to allow external PowerLogic compatible MMSTCP clients access to the ECC's attached slave devices. The ECC will allow a maximum of ten MMSTCP connections at any given time. The ECC will post MMSTCP connection listens on TCP port 102 with the MMS parameters in the following table.

[0170]

TABLE 28
MMSTCP Server Connect Parameters
	MMS Parameter	Value
	AP Title	0 0 00 0
	AP Invoke ID	0
	AE Qualifier	0
	AE Invoke ID	0
	Psel	00 00 00 02
	Ssel	00 01
	Tsel	00 01

[0171] MMSTCP Services

[0172] The following table shows the MMS services supported in the ECC and gives a slight definition of how each is used.

[0173]

TABLE 29
ECC Supported MMSTCP Services
MMS
Service	Description
Initiate	The ECC responds to all Initiate indications and is able to
	initiate connections for sub-net initiated communications.
Conclude	The ECC is able to respond to a Conclude indication and is
	able to conclude a connection in the case of inactivity on a
	channel or a request from sub-net initiated communications.
Abort	The ECC can respond to an Abort indication and generate a
	serial error code, if needed, in the case of sub-net initiated
	communications.
Cancel	The ECC responds to a Cancel by generating a serial error
	code, if needed, in the case of sub-net initiated
	communications.
Reject	The ECC can receive a Reject indication from another
	device and generate a serial error code, if needed, in the
	case of sub-net initiated communications.
Identify	The ECC returns the appropriate device information
	(vendor name, model, and firmware version) in response to
	an Identify indication.
Variable	The ECC responds to data access requests for symbolically
Read/Write	addressed variables Additionally, the ECC accepts serial
	read/write requests from a sub-net initiating device,
	converts them to a MMS symbolic address request, and
	returns the data appropriately.

[0174] MMSTCP Server Security Backwards Compatibility

[0175] Due to the new IP connection-based security implementation, the ECC will not need to support the old security scheme implemented in existing EGWs. This should not cause any problems in systems still needing security or even in existing systems where an ECC is installed with other EGWs. The new mechanism in the ECC can still be utilized in conjunction with the old mechanism in the EGWs with no problems.

[0176] MMSTCP Symbolic Variable Strings

[0177] Character-based symbolic addressing will be used for data access. The basic format will be a two-part address separated by a “^”. The first part is the end Device ID; the second part is protocol-specific. The following table shows the representation of each of the MMSTCP symbolic variable representations of the sub-network requests.

[0178]

TABLE 30
MMSTCP SyMax Symbolic Variable Formats
SyMax
Function Code	Name	SyMax Format for MMS
0	Block Read -	<DeviceID>{circumflex over ( )}<RegisterAddress>[<NumberOfRegisters>],
	Registers	*,
2	Block Write -	<DeviceID>{circumflex over ( )}<RegisterAddress>[<NumberOfRegisters>],
	Registers	*,
4	Scattered Read	<DeviceID>{circumflex over ( )}<RegisterAddress>,
	- Registers	<DeviceID>{circumflex over ( )}<RegisterAddress>,
4	Record Read -	<DeviceID>{circumflex over ( )}<RegisterAddress>[<NumberOfRegisters>],
	File	<DeviceID>{circumflex over ( )}RecordNumber[r]

[0179]

TABLE 31
MMSTCP Modbus/Jbus Symbolic Variable Formats
Modbus/Jbus
Function
Code	Name	Modbus/Jbus Format for MMS
1	Block Read -	<DeviceID>{circumflex over ( )}C<CoilAddress>[<NumberOfCoils>],
	Coil Status	*,
2	Block Read -	<DeviceID>{circumflex over ( )}D<CoilAddress>[<NumberOfCoils>],
	Input Coil	*,
	Status	*
3	Block Read -	<DeviceID>{circumflex over ( )}H<RegisterAddress>[<NumberOfRegisters>
	Holding	],
	Registers	*,
		*
4	Block Read -	<DeviceID>{circumflex over ( )}I<RegisterAddress>[<NumberOfRegisters>]
	Input Registers	*,
5	Single Write -	<DeviceID>{circumflex over ( )}C<CoilAddress>
	Coil
6	Single Write -	<DeviceID>{circumflex over ( )}H<RegisterAddress>
	Register
16	Block Write -	<DeviceID>{circumflex over ( )}H<RegisterAddress>[<NumberOfRegisters>
	Holding	],
	Registers	*,
		*
20	Block Read -	<DeviceID>{circumflex over ( )}F<RegisterAddress>[<NumberOfRegisters>]
	General	<FileNumber>,
	Reference/File	*,
		*
21	Block Write -	<DeviceID>{circumflex over ( )}F<RegisterAddress>[<NumberOfRegisters>]
	General	<FileNumber>,
	Reference/File	*,
		*
100	Scattered Read	<DeviceID>{circumflex over ( )}S<RegisterAddress>,
	- Holding	<DeviceID>{circumflex over ( )}S<RegisterAddress>,
	Registers	<DeviceID>{circumflex over ( )}S<RegisterAddress>
102	Security	<DeviceID>{circumflex over ( )}Z<SecurityCode>{circumflex over ( )}regular formats minus
	Operations	device ID

[0180] MMSTCP Symbolic Variable String Examples

[0181] A SyMax Block Read of registers 1002 through 1004 from a SyMax device defined as Device ID 12 in the ECC should be done with a single MMS read of a list of 3 individual symbolic variables in the following format.

[0182]

	12{circumflex over ( )}1002[3]	= Variable 1
	*	= Variable 2
	*	= Variable 3

[0183] A SyMax Block Write of registers 6800 through 6802 from a SyMax device defined as Device ID 12 in the ECC should be done with a single MMS write of a list of 4 individual symbolic variables in the following format.

[0184]

12{circumflex over ( )}6800[3]	= Variable 1	−32768 to 32767 for data
*	= Variable 2	−32768 to 32767 for data
*	= Variable 3	−32768 to 32767 for data
*	= Variable 4 with mask value to be applied to the written
	registers' data

[0185] Note that there is (1+NumberOfRegisters) variables. This is because the last variable's data must be used as a mask value in the SyMax operation. This last variable's data is usually FFFF because all the bits for all the values are to be written into the associated registers. The FFFF value can be changed if only certain bits are to be written.

[0186] A SyMax Scattered Read of registers 1002, 1004, 1008 from a SyMax device defined as Device ID 12 in the ECC should be done with a single MMS read of a list of 3 individual symbolic variables in the following format:

[0187]

	12{circumflex over ( )}1002	= Variable 1
	12{circumflex over ( )}1004	= Variable 2
	12{circumflex over ( )}1008	= Variable 3

[0188] A Modbus/Jbus Block Read of coils 20 through 22 from a Modbus/Jbus device defined as Device ID 12 in the ECC should be done with a single MMS read of a list of 3 individual symbolic variables in the following format:

[0189]

	12{circumflex over ( )}C20[3]	= Variable 1
	*	= Variable 2
	*	= Variable 3

[0190] A Modbus Block Read of Input coils 100020 through 100022 from a Modbus device defined as Device ID 12 in the ECC should be done with a single MMS read of a list of 3 individual symbolic variables in the following format:

[0191]

	12{circumflex over ( )}D20[3]	= Variable 1
	*	= Variable 2
	*	= Variable 3

[0192] A Jbus Block Read of Input coils 20 through 22 from a Jbus device defined as Device ID 12 in the ECC should be done with a single MMS read of a list of 3 individual symbolic variables in the following format:

[0193]

	12{circumflex over ( )}D20[3]	= Variable 1
	*	= Variable 2
	*	= Variable 3

[0194] A Modbus Block Read of Holding registers 401002 through 401004 from a Modbus device defined as Device ID 12 in the ECC should be done with a single MMS read of a list of 3 individual symbolic variables in the following format:

[0195]

	12{circumflex over ( )}H1002[3]	= Variable 1
	*	= Variable 2
	*	= Variable 3

[0196] A Jbus Block Read of Holding registers 1002 through 1004 from a Jbus device defined as Device ID 12 in the ECC should be done with a single MMS read of a list of 3 individual symbolic variables in the following format:

[0197]

	12{circumflex over ( )}H1002[3]	= Variable 1
	*	= Variable 2
	*	= Variable 3

[0198] A Modbus Block Read of Input registers 301002 through 301004 from a Modbus device defined as Device ID 12 in the ECC should be done with a single MMS read of a list of 3 individual symbolic variables in the following format.

[0199]

	12{circumflex over ( )}I1002[3]	= Variable 1
	*	= Variable 2
	*	= Variable 3

[0200] A Jbus Block Read of Input registers 1002 through 1004 from a Jbus device defined as Device ID 12 in the ECC should be done with a single MMS read of a list of 3 individual symbolic variables in the following format:

[0201]

	12{circumflex over ( )}I1002[3]	= Variable 1
	*	= Variable 2
	*	= Variable 3

[0202] A Modbus/Jbus Single Coil Write to coil 20 to a Modbus/Jbus device defined as Device ID 12 in the ECC should be done with a single MMS write of a single symbolic variable in the following format:

[0203]

	12{circumflex over ( )}C20	= Variable 1	1 or 0 for data

[0204] A Modbus Single Register Write to register 406800 to a Modbus device defined as Device ID 12 in the ECC should be done with a single MMS write of a single symbolic variable in the following format:

[0205]

	12{circumflex over ( )}H6800	= Variable 1	−32768 to 32767 for data

[0206] A Jbus Single Register Write to register 6800 to a Jbus device defined as Device ID 12 in the ECC should be done with a single MMS write of a single symbolic variable in the following format:

[0207]

	12{circumflex over ( )}H6800	= Variable 1	−32768 to 32767 for data

[0208] A Modbus Block Write to registers 406800 to 406802 to a Modbus device defined as Device ID 12 in the ECC should be done with a single MMS write of a list of 3 individual symbolic variables in the following format:

[0209]

	12{circumflex over ( )}H6800[3]	= Variable 1	−32768 to 32767 for data
	*	= Variable 2	−32768 to 32767 for data
	*	= Variable 3	−32768 to 32767 for data

[0210] A Jbus Block Write to registers 6800 to 6802 to a Jbus device defined as Device ID 12 in the ECC should be done with a single MMS write of a list of 3 individual symbolic variables in the following format:

[0211]

	12{circumflex over ( )}H6800[3]	= Variable 1	−32768 to 32767 for data
	*	= Variable 2	−32768 to 32767 for data
	*	= Variable 3	−32768 to 32767 for data

[0212] A Modbus/Jbus Read from General Reference File 1 registers 2 to 4 from a Modbus/Jbus device defined as Device ID 12 in the ECC should be done with a single MMS read of a list of 3 individual symbolic variables in the following format:

[0213]

	12{circumflex over ( )}F2[3]1	= Variable 1
	*	= Variable 2
	*	= Variable 3

[0214] A Modbus/Jbus Write to General Reference File 1 registers 2 to 4 to a Modbus/Jbus device defined as Device ID 12 in the ECC should be done with a single MMS write of a list of 3 individual symbolic variables in the following format:

[0215]

	12{circumflex over ( )}F2[3]1	= Variable 1	−32768 to 32767 for data
	*	= Variable 2	−32768 to 32767 for data
	*	= Variable 3	−32768 to 32767 for data

[0216] A Modbus Scattered Read of registers 401002, 401004, 401008 from a Modbus device defined as Device ID 12 in the ECC should be done with a single MMS read of a list of 3 individual symbolic variables in the following format:

[0217]

	12{circumflex over ( )}S1002	= Variable 1
	12{circumflex over ( )}S1004	= Variable 2
	12{circumflex over ( )}S1008	= Variable 3

[0218] A Jbus Scattered Read of registers 1002, 1004, 1008 from a Jbus device defined as Device ID 12 in the ECC should be done with a single MMS read of a list of 3 individual symbolic variables in the following format:

[0219]

	12{circumflex over ( )}S1002	= Variable 1
	12{circumflex over ( )}S1004	= Variable 2
	12{circumflex over ( )}S1008	= Variable 3

[0220] A Modbus Secured Scattered Read of registers 401002, 401004, 401008 from a Modbus device defined as Device ID 12 in the ECC should be done with a single MMS read of a list of 3 individual symbolic variables in the following format:

[0221]

	12{circumflex over ( )}Z3546{circumflex over ( )}S1002	= Variab1e 1
	12{circumflex over ( )}Z3546{circumflex over ( )}S1004	= Variable 2
	12{circumflex over ( )}Z3546{circumflex over ( )}S1008	= Variable 3

[0222] ModbusTCP Client

[0223] The ECC will have the ability to initiate communications as a ModbusTCP client when configured to do so based on the Remote Device Connections Setup. The ECC will do all transactions based on a connection to TCP port 502 and will support the same Modbus function codes listed in the ModbusTCP Server Function Codes Section. Each read or write operation will be accompanied by a connect and a disconnect message over the Ethernet.

[0224] MMSTCP Client

[0225] The ECC will have the ability to initiate communications as a MMSTCP client when configured to do so based on the Remote Device Connections Setup The ECC will do all transactions based on a connection to TCP port 102 and will support the MMS functionality explained in the MMSTCP Services Section. Each read or write operation will be accompanied by a connect and a disconnect message over the Ethernet.

[0226] SNTP Server

[0227] The ECC will have the ability to listen on TCP port 123 for an SNTP server to send time synchronization information to the ECC. This information will then update the ECC's internal time and will allow this updated internal time to be used in the time synchronization mechanism which will update all the attached devices (CM and RS485) to the ECC on configurable intervals.

[0228] FTP Server

[0229] The ECC has the ability to act as an FTP server. This capability will allow the ECC to listen on the Ethernet at TCP port 21 for file transfers. Utilizing this capability will allow a good mechanism for quick downloadable ECC basic setup, downloadable ECC firmware updates, and downloadable custom device HTML tables.

[0230] FTP Download for Basic Setup

[0231] The ECC will have the ability to accept an FTP download to accomplish limited setup changes/additions. The initial setup of the ECC through the CM display must already be completed to get the ECC configured properly on the TCP/IP network prior to attempting the setup download. Most any desktop PC running Windows NT/95/98 and using TCP/IP will have the capability to FTP a setup file to the ECC. The setup file will be an ASCII text file with a list of strings for the ECC to execute. The user will have to open an FTP session from within the DOS prompt and “put/send” the text file to the ECC. The text file must be named “setup.txt” and the user must login to the ECC FTP server with the administrator password (user name is ignored by the ECC). The following table shows what each line in the text file should be.

[0232]

TABLE 32
Basic Setup FTP File Format
Line Number	Description
1	RS485 Port Baud Rate (1200, 2400, 4800, 9600,
	19200, 38400)
2	RS485 Port Parity (0 = none, 2 = even)
3	RS485 Port Timeout in seconds (3-10)
4	RS485 Time Sync Interval in seconds (0 = disabled,
	30-65535)
5	Device ID 2's RS485 Address (0-247)
6	Device ID 2's RS485 Protocol (4 = PowerLogic, 6 =
	Modbus, 11 = Jbus, any value other than these specified
	will remove this device from the list)
7	Device ID 3's RS485 Address (0-247)
8	Device ID 3's RS485 Protocol (4 = PowerLogic, 6 =
	Modbus, 11 = Jbus, any value other than these specified
	will remove this device from the list)
66	Through Device ID 32's info
The following shows what an example setup text file would look like
	9600
	2
	5
	300
	3
	4
	5
	6
	10
	11
	24
	4
	Note A “Wizard” application could be provided here to automatically generate this file for the user.

[0233] FTP Download for Firmware Update

[0234] The ECC will have the ability to accept an FTP transfer to accomplish a firmware download. The ECC must be configured properly on the TCP/IP network prior to attempting the firmware download. Most any desktop PC running Windows NT195/98 and using TCP/IP will have the capability to FTP the firmware file to the ECC. The user will have to open an FTP session from within the DOS prompt and “put/send” the firmware file to the ECC. The file will be named “firmware.bin” and the user must login to the ECC FTP server with the administrator password (user name is ignored by the ECC). The new firmware binary will be accepted by the ECC into DRAM space. Once the FTP transaction is complete, the firmware binary will be copied into flash, and the ECC will reset to load and run with the new image.

[0235] FTP Download for Custom Device View Tables (Future)

[0236] The ECC will have the ability to accept an FTP download to allow for five custom designed HTML device view pages. The ECC will be configured properly on the TCP/IP network prior to attempting the download. Most any desktop PC running Windows NT/95/98 and using TCP/IP will have the capability to FTP the file to the ECC. The HTML file will be an ASCII text file written in standard HTML language.

[0237] Note that it is up to the user to correctly construct the HTML page. The ECC will only confirm that there is a correct HTML title tag, and then accept the whole file as correct. Once the file is accepted, a link to the page will appear on the ECC Home page. The link name will be the page's title up to 32 characters.

[0238] The user will have to open an FTP session from within the DOS prompt and “put/send” the HTML file to the ECC. The user must login to the ECC FTP server with the administrator password (user name is ignored by the ECC). Once the file is accepted by the ECC, the HTML file's title will show up in the list on the ECC Home page.

[0239] Post FTP Download for Custom Device View Tables (Future)

[0240] The ECC will normally have the custom HTML pages loaded into DRAM at runtime. When a new one is downloaded, the ECC will update its image in DRAM then have to store the HTML page in a file in the CM. According to the CM Design Specification, the following table signifies each file for the pages.

[0241]

TABLE 33
Downloadable HTML Page Storage
File Type	Description	File Size	Record Size
35	HTML File #1	Dynamic	Static
36	HTML File #2	Dynamic	Static
37	HTML File #3	Dynamic	Static
38	HTML File #4	Dynamic	Static
39	HTML File #5	Dynamic	Static

[0242] Each downloadable HTML page will be buffered to fit the static record size. This means that the HTML page will be evenly divisible by 100 because each record size is limited to 100 bytes.

[0243] Serial Communications

[0244] The ECC will have the ability to have its single RS485 port utilized for communications in combinations of the following: 2-wire, 4-wire, multi-protocol, master, slave (Future). To try to keep with the goal of having the user do as little setup as possible, the goal of the ECC RS485 logistics will be to have only two modes of operation. These two modes will be able to be as “dynamic” as possible and respond/react to the protocols supported as needed. These two modes will be called “4-wire Smart Mode” and “2-wire Smart Mode”.

[0245] 4-wire Smart Mode

[0246] The 4-wire Smart Mode will be the default and primary setup for the ECC RS485 communications. This mode will allow for fall-duplex bi-directional communications when needed. The ECC will be able to “know” when the port is being utilized as a slave or master by reacting to what is connected to it during communications. This “knowledge” also includes the ability to determine between SyMax, Modbus, and Jbus protocols on the fly. This ability helps the ECC adept even better to the use of “mixed-protocol” devices.

[0247] 2-wire Smart Mode

[0248] The 2-wire Smart Mode will be the secondary setup for the ECC RS485 communications. This mode will allow for half-duplex communications only. This means that all the devices (master and slaves) together share the communication signals and can only communicate one at a time. In this mode, just like the 4-wire Smart Mode, the ECC will be able to “know” when the port is being utilized as a slave or master by reacting to what is connected to it during communications. This mode will accommodate Modbus/Jbus 2-wire communications only. This ability also helps ease the ECC setup for the user.

[0249] Inter-processor Communications

[0250] The primary purpose of the ECC is for high-speed communications to the CM the ECC is inserted into. This inter-processor communications will be based on a high-speed dual-port RAM interface between the bus of the ECC's processor and the bus of the CM's processor The actual speed of the communications will be determined during development/testing.

[0251] Inter-processor Communications Theory of Operation

[0252] The inter-processor communications will be based on a proprietary “flavor” of Modbus. This choice was made since the Modbus protocol is one already well adapted into both devices, and since the characteristics of the protocol fit the dual-port RAM interface fairly well. Because the CM will have the ability to initiate communications and cause a potential for full-duplex, bi-directional communications (collisions) through the dual-port RAM in the ECC, the dual-port RAM will have to be split into four main memory regions.

[0253] One half (upper half), from the point-of-view of the ECC, will be the incoming side for communications from the CM. This half will then be split into two equal memory regions that will be designated for incoming commands and incoming replies. The other half (lower half), again from the point-of-view of the ECC, will be the outgoing side for communications to the CM. This half will also be split into two more equal memory regions that will be designated for outgoing commands and outgoing replies.

[0254] To ease the message management on the CM and the ECC, no more than one command message per direction should be outstanding at any given time. There may also need to be “control” messages between just the CM and the ECC for movement of specific types of data unknown to the “outside”. In these cases, the CM and the ECC should use a Modbus slave ID of 255 in the Modbus command message to signify to the device receiving the message that it is a “control” message.

[0255] As previously mentioned, there will be a slight adaptation of the Modbus packet structure. There will be two bytes (one word) added as the first part of the message that will be the count of the bytes contained in the rest of the message. The rest of the message will then be a regularly formatted Modbus message. The ECC will read the CM's RS485 slave port address out of the CM at boot and that address will be used for MBTCP communications to the CM the ECC is inserted into.

[0256] After the ECC fills the appropriate region of the dual-port RAM with the appropriate message needed, the offset address of 0x7FF should be written with the appropriate interrupt ID to trigger an interrupt to the CM processor. Likewise, after the CM fills the appropriate region of the dual-port RAM with the appropriate message needed, the offset address of 0x7FE should be written with the appropriate interrupt ID to trigger an interrupt to the ECC processor.

[0257] FIG. 9 shows the memory map of the dual-port ram followed by an explanation of each of the numbered memory regions.

[0258]

TABLE 34
Dual-Port Ram Memory Region Descriptions
Memory
Region	Description
1	The ECC writes the interrupt ID here to trigger an interrupt to
	the CM.
	Or
	The CM reads this address after being triggered by the
	interrupt to see what the interrupt ID is.
2	The CM writes the interrupt ID here to trigger an interrupt to
	the ECC.
	Or
	The ECC reads this address after being triggered by the
	interrupt to see what the interrupt ID is.
3	Reserved
4	The ECC, after interrupt and reading the interrupt ID from
	0x7FE, will read this memory region from offset 0x600 for
	number of bytes shown in 0x5FE and 0x5FF to get a Modbus
	command message from the CM.
	Or
	The CM, before writing the appropriate interrupt ID value in
	0x7F, will write the Modbus command message in this
	memory region from offset 0x600 and write the number of
	bytes in the message into 0x5FE and 0x5FF.
5	The ECC, after interrupt and reading the interrupt ID from
	0x7FE, will read this memory region from offset 0x401 for
	number of bytes shown in 0x3FF and 0x400 to get a Modbus
	reply message from the CM
	Or
	The CM, before writing the appropriate interrupt ID value in
	0x7FE, will write the Modbus reply message in this memory
	region from offset 0x401 and write the number of bytes in the
	message into 0x3FF and 0x400.
6	The CM, after interrupt and reading the interrupt ID from
	0x7FF, will read this memory region from offset 0x202 for
	number of bytes shown in 0x200 and 0x201 to get a Modbus
	command message from the ECC.
	Or
	The ECC, before writing the appropriate interrupt ID value in
	0x7FF, will write the Modbus command message in this
	memory region from offset 0x202 and write the number of
	bytes in the message into 0x200 and 0x201.
7	The CM, after interrupt and reading the interrupt ID from
	0x7FF, will read this memory region from offset 0x003 for
	number of bytes shown in 0x001 and 0x002 to get a Modbus
	reply message from the ECC.
	Or
	The ECC, before writing the appropriate interrupt ID value in
	0x7FF, will write the Modbus reply message in this memory
	region from offset 0x003 and write the number of bytes in the
	message into 0x001 and 0x002.
8	Option Card Identification

[0259] Table 35 shows the combinations for the flow of messages through the dual-port RAM and the associated interrupt ID.

[0260]

TABLE 35
Dual-port RAM Logistics
Direction	Interrupt ID	Description
Incoming Command	1 (command)	Incoming command from the CM
(memory region 4)		to the ECC (designated by slave
		id 255), or from the CM to the
		ECC to be routed to the outside
Incoming Reply	2 (reply)	Incoming reply from the CM to
(memory region 5)		the ECC (designated by slave id
		255), or from the CM to the ECC
		to be routed to the outside
Outgoing Command	3 (command)	Outgoing command from the ECC
(memory region 6)		to the CM (designated by slave id
		255), or from the outside to be
		routed by the ECC to the CM
Outgoing Reply	4 (reply)	Outgoing reply from the ECC to
(memory region 7)		the CM (designated by slave id
		255), or from the outside to be
		routed by the ECC to the CM.

[0261] Inter-processor Communications Boot-up Sequence

[0262] Because the entire ECC configuration will be stored in the CM the ECC is inserted into, the ECC will have to be able to get this information from the CM at every boot-up. Also, if the user changes the initial setup information (IP Address, IP Subnet Mask, IP Router, or Ethernet Physical Connection) via the CM display, the CM will have to re-boot the ECC to have the new settings take effect.

[0263] At initial power-up, the ECC will set its CM option card identifier in the lowest address of the dual-port RAM as soon as possible before starting any of the main firmware tasks. At this point, the ECC will finish its boot sequence based on the last known good initial setup information. This information will be held in the first thirteen bytes of the EEPROM based on the following Table 36.

[0264]

TABLE 36
Last Known Good Boot State
Byte Offset into EEPROM	Description
0	IP Address - 1st Octet
1	IP Address - 2nd Octet
2	IP Address - 3rd Octet
3	IP Address - 4th Octet
4	IP Sub-net Mask - 1st Octet
5	IP Sub-net Mask - 2nd Octet
6	IP Sub-net Mask - 3rd Octet
7	IP Sub-net Mask - 4th Octet
8	IP Router Address - 1st Octet
9	IP Router Address - 2nd Octet
10	IP Router Address - 3rd Octet
11	IP Router Address - 4th Octet
12	Ethernet Physical Connection

[0265] After the completion of the boot sequence based on the last known good information, the ECC will then begin the first of a sequence of Modbus reads getting the basic ECC setup information from the CM If the ECC finds a difference between what it has as the last known good information and what the CM has as the initial setup information, the ECC will update its last known good information and request a reboot of the CM. Once there is a match between the initial setup information between the ECC and the CM, the ECC will finish its boot sequence with all the appropriate basic setup information and continue to request any advanced information (Custom HTML pages) from the CM.

[0266] CM Communications Card Identification

[0267] The CM option card identifier used by the ECC is defined by the CM and is the value of six according to the CM Design Specification. This number will be placed in the lowest offset of the dual-port RAM by the ECC as soon as possible during boot-up.

[0268] Manufacturing Parameters

[0269] The ECC will need some specific parameters set for each unit during manufacturing. Some of the parameters that appear to be needed at this time are the Organizationally Unique Identifier (OUI), the serial number, the model number, the hardware revision number, and the date of manufacture (DOM).

[0270] Organizationally Unique Identifier (OUI)

[0271] An OUI is a 24 bit globally unique assigned number referenced by various standards. An OUI is used in the family of 802 LAN standards (Ethernet, Token Ring, etc). The OUI defined in IEEE Std 802-1990 can be used to generate 48 bit Universal LAN MAC addresses to identify LAN and MAN stations uniquely, and Protocol Identifiers to identify public and private protocols. These are used in Local and Metropolitan Area Network applications. The relevant standards include CSMA/CD (IEEE Std 802.3, ISO 8802-3), Token Bus (IEEE Std 802.4, ISO 8802-4), Token Ring (IEEE Std 802.5, ISO/IEC 8802-5), IEEE Std 802.6 (ISO/IEC DIS 8802-6), and FDDI (ISO 9314-2).

[0272] The ECCs will carry Square D's IEEE OUI “signature” of 00-80-67. The Power Management Operations (PMO) has a range of the OUIs for Ethernet MAC addresses and will be 00-80-67-80-00-00 through 00-80-67-FF-FF-FF. This range gives PMO a total of 8,388,608 MAC addresses to distribute and be used among our Ethernet devices.

[0273] The unique MAC addresses will have to be able to be assigned to each individual ECC during manufacturing. There are a few possibilities to accomplish this. One possibility is to have the MAC assignment done by writing the EEPROM before board manufacture and/or have an EEPROM socket for removal of the EEPROM to have the ability to re-write if needed The other option would be to have firmware capabilities to set/change the MAC address when needed. This option requires more functionality in the firmware and also leaves open the potential of “lost” or duplicate MAC addresses. The following table shows the storage format of the MAC address in the EEPROM on the ECC.

[0274]

TABLE 37
MAC Address Storage Map
Byte
Offset into EEPROM	Description
13	Byte one of the MAC address (most significant)
14	Byte two of the MAC address
15	Byte three of the MAC address
16	Byte four of the MAC address
17	Byte five of the MAC address
18	Byte six of the MAC address (least significant)

[0275] Serial Number

[0276] Another piece of information that will need to be stored in the ECC EEPROM will be a serial number. Here again, there are a few possibilities to accomplish this. One possibility is to have the serial number assignment done by writing the EEPROM before board manufacture and/or have an EEPROM socket for removal of the EEPROM to have the ability to re-write if needed. Another option would be to have firmware capabilities to set/change the serial number when needed. A third option would be to come up with a scheme to drive a serial number from the MAC address. By having the MAC address set, the serial number would also inherently be set. The following table shows the storage format of the 32 bit value of the serial number in the EEPROM on the ECC

[0277]

TABLE 38
Serial Number Storage Map
Byte
Offset into EEPROM	Description
19	Byte one of the Serial Number (most significant)
20	Byte two of the Serial Number
21	Byte three of the Serial Number
22	Byte four of the Serial Number (least significant)

[0278] Model Number

[0279] Another piece of information that will need to be stored in the ECC EEPROM will be a model number. Here again, there are a few possibilities to accomplish this. One possibility is to have the model number assignment done by writing the EEPROM before board manufacture and/or have an EEPROM socket for removal of the EEPROM to have the ability to re-write if needed. The other option would be to have firmware capabilities to set/change the model number when needed. The following table shows the storage format of the 16 bit value of the model number in the EEPROM on the ECC.

[0280]

TABLE 39
Model Number Storage Map
Byte
Offset into EEPROM	Description
23	Byte one of the Model Number (most significant)
24	Byte two of the Model Number (least significant)

[0281] Hardware Revision Number

[0282] Another piece of information that will need to be stored in the ECC EEPROM will be a hardware revision number. Here again, there are a few possibilities to accomplish this. One possibility is to have the hardware revision number assignment done by writing the EEPROM before board manufacture and/or have an EEPROM socket for removal of the EEPROM to have the ability to re-write if needed. The other option would be to have firmware capabilities to set/change the hardware revision number when needed. The following table shows the storage format of the four ASCII characters that represent the hardware revision number in the EEPROM on the ECC.

[0283]

TABLE 40
Model Number Storage Map
Byte Offset
into EEPROM	Description
25	ASCII character one of the Hardware Revision Number
26	ASCII character two of the Hardware Revision Number
27	ASCII character three of the Hardware Revision Number
28	ASCII character four of the Hardware Revision Number

[0284] Date of Manufacture (DOM)

[0285] Another piece of information that will need to be stored in the ECC EEPROM will be a Date of Manufacture value. Here again, there are a few possibilities to accomplish this. One possibility is to have the date assignment done by writing the EEPROM before board manufacture and/or have an EEPROM socket for removal of the EEPROM to have the ability to re-write if needed. The other option would be to have firmware capabilities to set/change the date when needed. The following table shows the storage format of the date of manufacture in the EEPROM on the ECC.

[0286]

TABLE 41
DOM Storage Map
Byte Offset into EEPROM	Description
29	Month byte of the DOM
30	Day byte of the DOM
31	Year byte of the DOM, since 1900
32	Hour byte of the DOM
33	Minute byte of the DOM
34	Seconds byte of the DOM

[0287] Manufacture Process Info

[0288] The final piece of information that will need to be stored in the ECC EEPROM will be an area of memory that will be used as a “scratch pad” for use during Manufacturing. This area will be written during manufacturing/testing of each unit. The following table shows the region in the EEPROM dedicates for this purpose.

[0289]

TABLE 42
Manufacturing Process Info Storage Map
Byte Offset into EEPROM	Description
35-74	Manufacturing “scratch pad”

[0290] Environmental

[0291] The ECC design will attempt to meet the same environmental requirements as the CM. This will prove difficult, however, due to the lack of availability of Industrial Ethernet components capable of doing the needed speeds/interfaces. The following table will show acceptable ranges for the environmental requirements that the ECC will attempt to meet.

[0292]

TABLE 43
Environmental Requirements
	Description	Values
	Operating Temperature Range	−40° C. to +70° C.
	Storage Temperature Range	−40° C. to +85° C.
	Humidity Rating	5% to 95% rh (non-condensing)
	Vibration	Equivalent to CM

[0293] Agency Compliance

[0294] The ECC design will attempt to meet the same agency compliance as the CM. The following table shows the agency compliance that the ECC will attempt to meet.

[0295]

TABLE 44
Agency Compliance
Type		Description
Electromagnetic	Radiated Emissions	FCC Part 15 Class A/CE
Interference		Heavy
		Industrial
Electromagnetic	Conducted Emissions	FCC Part 15 Class A/CE
Interference		Heavy
		Industrial
Electrostatic	Air Discharge	IEC pub 1000-4-2 level 4
Discharge
Immunity to	Transients	ANSI/IEEE C37.90A, IEC
Electrical Fast		pub 1000-4-4 level 3
Transients
Immunity to	Impulse Wave	IEC pub 1000-4-5 level 4
Electrical Fast
Transients
Breakdown	Dielectric Withstand	UL 508, CSA
Voltage		C22.2-14-M1987,
		IEC pub 1000-4
Immunity to	RFI	IEC pub 801.3 level 4
Radiated Fields
Safety	USA	UL 508
Safety	Canada	CSA C22.2-14-M1987
Safety	Europe	VDE/TUV Equivalent to
		UL508

[0296] System Manager Software Drivers

[0297] The ECC will be designed in such a way to be as completely compatible as possible with the existing SMS PowerLogic Network Server MMSTCP and ModbusTCP Drivers. This will allow the integration of the new communications device without major impact on SMS.

[0298] ECC Operating System

[0299] The operating system used in the ECC design will be the pSOSystem operating system from Integrated Solutions, Inc. (ISI). pSOSystem has been established as a leading real-time operating system (RTOS) for embedded applications. pSOSystem is a modular, high-performance, real-time operating system, designed specifically for embedded microprocessors. A few of the main components that will be utilized during development will be the pSOSystem pSOS+Real-time Multi-tasking Kernel, pNA+TCP/IP Protocol Stack, pREPC+ANSI C Standard Library, pROBE+, and pMONT+. All the firmware work will be done in ISI's pRISM+development environment. For detailed information on these pSOSystem and pRISM+components, refer to the ISI pSOSystem and pRISM+documentation.

[0300] ECC Register List

[0301] The ECC will have nearly all configuration data stored in the CM it is inserted into. The required storage size will need to be a minimum of 300 words (registers). The is the “quick list” of the registers.

[0302]

TABLE 45
ECC Register List
Register	HiByte	LoByte
500	IP Address 1st Octet	IP Address 2nd Octet
	(0-255)	(0-255)
501	IP Address 3rd Octet	IP Address 4th Octet
	(0-255)	(0-255)
502	IP Sub-net Mask 1st Octet	IP Sub-net Mask 2nd Octet
	(0-255)	(0-255)
503	IP Sub-net Mask 3rd Octet	IP Sub-net Mask 4th Octet
	(0-255)	(0-255)
504	IP Router Address 1st Octet	IP Router Address 2nd Octet
	(0-255)	(0-255)
505	IP Router Address 3rd Octet	IP Router Address 4th Octet
	(0-255)	(0-255)
506	Ethernet physical connection
	(0 = UTP, 1 = Fiber HD,
	2 = Fiber FD)
507	ModbusTCP Client Timeout in	MMSTCP Client Timeout in
	seconds (5-60)	seconds (5-60)
508	HTML Access token expiration
	time in minutes (1-255)
509	RS485 Timeout in seconds	DPR Timeout in seconds
	(3-10)	(3-10)
510	CM/RS485 Time Synchronization
	Interval in seconds
	(0 = disabled, 30-65535)
511	HTML default language type
	(0 = English, 1 = French,
	2 = Spanish)
512	RS485 Baud Rate
	(1200, 2400, 4800, 9600, 19200, 38400)
513	RS485 Parity	RS485 Mode
	(0 = none, 2 = even)	(1 = 2-wire Smart, 2 = 4-wire Smart)
514	Admin password ASCII character 1	Admin password ASCII character 2
515	Admin password ASCII character 3	Admin password ASCII character 4
516	Admin password ASCII character 5	Admin password ASCII character 6
517	Admin password ASCII character 7	Admin password ASCII character 8
518	Pass1 password ASCII character 1	Pass1 password ASCII character 2
519	Pass1 password ASCII character 3	Pass1 password ASCII character 4
520	Pass1 password ASCII character 5	Pass1 password ASCII character 6
521	Pass1 password ASCII character 7	Pass1 password ASCII character 8
522	Pass1 Password HTML Page Access Bitmap (Most Significant Word)
523	Pass1 Password HTML Page Access Bitmap (2nd Most Significant Word)
524	Pass1 Password HTML Page Access Bitmap (2nd Least Significant Word)
525	Pass1 Password HTML Page Access Bitmap (Least Significant Word)
526	Pass2 password ASCII character 1	Pass2 password ASCII character 2
527	Pass2 password ASCII character 3	Pass2 password ASCII character 4
528	Pass2 password ASCII character 5	Pass2 password ASCII character 6
529	Pass2 password ASCII character 7	Pass2 password ASCII character 8
530	Pass2 Password HTML Page Access Bitmap (Most Significant Word)
531	Pass2 Password HTML Page Access Bitmap (2nd Most Significant Word)
532	Pass2 Password HTML Page Access Bitmap (2nd Least Significant Word)
533	Pass2 Password HTML Page Access Bitmap (Least Significant Word)
534	Pass3 password ASCII character 1	Pass3 password ASCII character 2
535	Pass3 password ASCII character 3	Pass3 password ASCII character 4
536	Pass3 password ASCII character 5	Pass3 password ASCII character 6
537	Pass3 password ASCII character 7	Pass3 password ASCII character 8
538	Pass3 Password HTML Page Access Bitmap (Most Significant Word)
539	Pass3 Password HTML Page Access Bitmap (2nd Most Significant Word)
540	Pass3 Password HTML Page Access Bitmap (2nd Least Significant Word)
541	Pass3 Password HTML Page Access Bitmap (Least Significant Word)
542	RS485 Device Definitions - Protocol	RS485 Device Definitions - Address
	(3 = PowerLogic, 8 = Modbus)	(0-254)
543-604	62 more registers for up to 62 more Device definitions
605	Number of viewable defined devices, includes CM that the ECC is attached
	to (1-62)
606	Web Page Passwords Disabled (Most Significant Word)
607	Web Page Passwords Disabled (Least Significant Word)
608	MAC Address Byte 1	MAC Address Byte 2
609	MAC Address Byte 3	MAC Address Byte 4
610	MAC Address Byte 5	MAC Address Byte 6
611	Serial Number Byte 1 (32 bit	Serial Number Byte 2
	number)
612	Serial Number Byte 3	Serial Number Byte 4
613	Model Number (16 bit number)
614	Hardware Revision Number	Hardware Revision Number
	Character 1	Character 2
615	Hardware Revision Number	Hardware Revision Number
	Character 3	Character 4
616	Date of Manufacture Month Byte	Date of Manufacture Day Byte
617	Date of Manufacture Year Byte,	Date of Manufacture Hour Byte
	since 1900
618	Date of Manufacture Minutes Byte	Date of Manufacture Seconds Byte
619-638	Scratch Pad/Process Area
639	Firmware Version Number (2000 = 2.000)
640	Refresh Rate for Static Tables in seconds
	(1-300)
641	Force Manufacturing Parameters Flag (AAAA means the ECC excepts the
	manufacturing parameters from the register list)
642-991	Reserved
992-998	CM4 Ghost of registers 500-506
999	CM4 Ghost of CM4 RS485 port address

[0303] While particular embodiments and applications of the present invention have been illustrated and described, it is to be understood that the invention is not limited to the precise construction and compositions disclosed herein and that various modifications, changes, and variations may be apparent from the foregoing descriptions without departing from the spirit and scope of the invention as defined in the appended claims.