REL 512 DNP 3.0 AUTOMATION TECHNICAL GUIDE

REL 512 DNP 3.0 Automation Technical Guide REL 512 DNP 3.0 AUTOMATION TECHNICAL GUIDE TG 7.11.1.7-62 Version 0.1 11/02 Page i REL 512 DNP 3.0 Automation Technical Guide Contents Section 1 – Introduction Introduction .................................................................................................................................................................1 Section 2 – Communication Card Identification and Physical Port Characteristics Communication Identification and Physical Port Characteristics ...............................................................................3 Communication Card Part Number Options...............................................................................................................5 Unit Communication Card Verification........................................................................................................................7 Communication Card Installation................................................................................................................................9 Parallel Interface Module..........................................................................................................................................14 Main Board #1 ..........................................................................................................................................................15 Main Board #2 ..........................................................................................................................................................15 Reclosing Board, #1 and #2 .....................................................................................................................................15 DNP Board................................................................................................................................................................15 Making the Connection.............................................................................................................................................16 Firmware...................................................................................................................................................................16 CPROG32W Installation...........................................................................................................................................18 Program File Installation...........................................................................................................................................18 Loading the Firmware ...............................................................................................................................................19 Serial Port 2 Configuration .......................................................................................................................................20 Section 3 – REL 512 Device Connectivity REL 512 Device Connectivity ...................................................................................................................................21 RS 232 Interface Connectivity ..................................................................................................................................21 Port Isolation.............................................................................................................................................................21 RS 232 Handshaking Defined ..................................................................................................................................22 RS 232 Cable Connectivity.......................................................................................................................................23 RS 485 Device Connectivity With REL 512..............................................................................................................25 DNP Card RS 485/RS 232 Configuration.................................................................................................................26 IRIG B Implementation in the REL 512 ....................................................................................................................27 Hardware Configuration...........................................................................................................................................29 Section 4 – REL 512 Device Parameterization REL 512 Device Parameterization ...........................................................................................................................32 Port Configuration.....................................................................................................................................................32 Hypertermian Setup for REL 512 Configuration.......................................................................................................32 Hyperterminal Based Port Configuration Visualization Sequence ...........................................................................34 COM 0 Port (Front Port) and Serial Port 2 Configuration Screens ..........................................................................37 Front Panel Interface COM Port Configuration Sequence .......................................................................................40 Front Panel Interface COM Port Parameterization...................................................................................................41 Serial Port 2 Front Panel Interface Configuration Sequence ...................................................................................42 Network Port 1 Configuration ...................................................................................................................................42 Communications Settings.........................................................................................................................................44 Device Address.........................................................................................................................................................44 Baud Rate.................................................................................................................................................................44 Frame Type ..............................................................................................................................................................45 Inter-char Gap Time..................................................................................................................................................45 Transceiver ...............................................................................................................................................................45 RS-232 Handshaking ...............................................................................................................................................45 RS-485 Duplex .........................................................................................................................................................45 Receive LED Light On ..............................................................................................................................................45 Transmit Delay..........................................................................................................................................................46 Page ii REL 512 DNP 3.0 Automation Technical Guide Protocol Settings.......................................................................................................................................................46 Data Link Confirm Mode...........................................................................................................................................46 Data Link Confirm Timeout.......................................................................................................................................46 Data Link Retries ......................................................................................................................................................46 Application Layer Confirm ........................................................................................................................................47 Application Layer Confirm Timeout ..........................................................................................................................47 Application Layer Fragment Size..............................................................................................................................47 Unsolicited Response Delay.....................................................................................................................................47 Unsolicited Response Destination Address .............................................................................................................47 Class 1 Event Response ..........................................................................................................................................47 Class 2 Event Response ..........................................................................................................................................47 Class 3 Event Response ..........................................................................................................................................48 Application Settings ..................................................................................................................................................48 Local/Remote Input...................................................................................................................................................48 Time Synchronization Source...................................................................................................................................48 Time Synchronization Interval ..................................................................................................................................48 Class 0 Mask 1-5 ......................................................................................................................................................48 Control Point Paired..................................................................................................................................................50 Rollover Flag.............................................................................................................................................................51 Deadband Values .....................................................................................................................................................51 Deadband Mask........................................................................................................................................................51 Default Variations .....................................................................................................................................................51 Section 5 – DNP V3.0 Device Profile DNP V3.0 Device Profile ..........................................................................................................................................53 DNP V3.0 Implementation Table ..............................................................................................................................55 Cold and Warm Restart Capabilities ........................................................................................................................58 Internal Indication (IIN) Field Data Returns ..............................................................................................................58 DNP V3.0 Point List ..................................................................................................................................................59 Binary Input Points....................................................................................................................................................59 Binary Input Points (67 Indices Defined) ..................................................................................................................59 Binary Counters (2 Elements Defined) .....................................................................................................................61 Counter Access (6 Elements Defined) .....................................................................................................................61 Analog Inputs (195 Elements) ..................................................................................................................................61 Binary Output Status Points & Control Relay Output Blocks ...................................................................................62 Control Code Configuration ......................................................................................................................................67 Paired Point Operation .............................................................................................................................................68 Appendix A-Revision History ....................................................................................................................................71 Appendix B-ASCII Conversion Table .......................................................................................................................73 Appendix C-Modem Communications to ABB Relays..............................................................................................76 Appendix D-B & B RS 232/485 Converter Connection to ABB Protective Relays.................................................122 Appendix E-Telebyte RS 232/485 Converter Connection to ABB Protective Relays ............................................132 The following are trademarks of AEG Schneider Automation Inc. Modbus, Modbus Plus, Modicon IBM, OS 2, and IBM PC are registered trademarks of International Business Machines Corporation. The following are registered trademarks of the Microsoft Corporation: Windows NT Windows 3.1 Windows 95 Windows 98 Hyperterminal MS-DOS Microsoft  USDATA is a registered trademark of the USDATA Corporation. INCOM and Standard Ten Byte Protocol are registered trademarks of Asea Brown Boveri Incorporated. Page iii REL 512 DNP 3.0 Automation Technical Guide Tables Section 2 – Communication Card Identification and Physical Port Characteristics Table 2-1. Table 2-2. Table 2-3. Table 2-4. Table 2-5. ???............................................................................................................................................................4 REL 512 Communication Options............................................................................................................6 REL 512 Communication Card Identification Matrix ................................................................................6 Files Required for Loading New Firmware.............................................................................................18 Physical Interface Emulation and Configuration ....................................................................................20 Section 3 – REL 512 Device Connectivity Table 3-1. Physical Interface Options......................................................................................................................21 Table 3-2. DNP Card Jumper Settings for the DNP 3.0 Port or the Serial Port 2 Ports..........................................26 Table 3-3. DB-9 Connector Pin-out .........................................................................................................................26 Section 4 – REL 512 Device Parameterization Table 4-1. Table 4-2. Table 4-3. Table 4-4. REL 512 Com Port 0, Serial Port 2 Front Panel Interface Parameters..................................................41 DNP Scan Group Masks ........................................................................................................................50 Paired Control Point Values ...................................................................................................................51 Configurable Default Variations .............................................................................................................52 Section 5 – DNP V3.0 Device Profile Table 5-1. Table 5-2. Table 5-3. Table 5-4. Table 5-5. REL 512 Device Profile ..........................................................................................................................53 Device Profile Documentation ................................................................................................................56 Trouble Bit 3 Instance Occurrence Definitions.......................................................................................58 Binary Input Index ..................................................................................................................................59 ???..........................................................................................................................................................62 Page iv REL 512 DNP 3.0 Automation Technical Guide Figures Section 1 – Introduction Figure 1-1. REL 512 Product Format ........................................................................................................................1 Section 2 – Communication Card Identification and Physical Port Characteristics Figure 2-1. COM 0 Port Location...............................................................................................................................3 Figure 2-2. Physical Optional Communication Card Port Locations .........................................................................3 Figure 2-3. REL 512 Communication Card ...............................................................................................................4 Figure 2-4. Physical Communication Card Location for the REL 512.......................................................................5 Figure 2-5. Startup Screen With Unit Information .....................................................................................................7 Figure 2-6. Root Menu Screen ..................................................................................................................................8 Figure 2-7. Unit Information Screen ..........................................................................................................................8 Figure 2-8. Front Panel Interface Part Number Identification Sequence ..................................................................9 Figure 2-9. Removal of Front Plate .........................................................................................................................10 Figure 2-10. Front Panel Interface Connector.........................................................................................................10 Figure 2-11. Separation of Inner Chassis From Outer Chassis ..............................................................................11 Figure 2-12. Screw Location for Removal of Upper I/O Control Board ...................................................................12 Figure 2-13. Slide I/O Board From Edge Card Connector Example ......................................................................12 Figure 2-14. I/O and Logic Board Interconnection Cable ........................................................................................13 Figure 2-15. Communication Card Interface Mounting Connector..........................................................................13 Figure 2-16. DNP Card Installation..........................................................................................................................13 Figure 2-17. Jumper Locations for the DNP Card ...................................................................................................14 Figure 2-18. Parallel Interface Module and Connections ........................................................................................15 Figure 2-19. Connections to the Relay for Different Board Configurations Using Main Board #1 ..........................16 Figure 2-20. Connections to the Relay for Different Board Configurations Using Main Board #2 ..........................16 Figure 2-21. Serial Port 1 COM Card Jumper Locations.........................................................................................20 Section 3 – REL 512 Device Connectivity Figure 3-1. Point to Point Architecture Using RS 232 .............................................................................................22 Figure 3-2. Multi-Drop Topology Using RS 232 ......................................................................................................23 Figure 3-3. COM 0 DB 9 to DB 9 Cable Pinout .......................................................................................................23 Figure 3-4. Rear Serial Port 2 COM Port Cable ......................................................................................................24 Figure 3-5. Connection of a DB25 Connector to a REL 512 Front Port Interface...................................................25 Figure 3-6. DNP 3.0 COM Card Jumper Locations.................................................................................................27 Figure 3-7. Typical IRIG B Architecture..................................................................................................................27 Figure 3-8. IRIG B Frame Construction...................................................................................................................28 Figure 3-9. IRIG B Port Locations ...........................................................................................................................29 Figure 3-10. Load Impedance Calculation ..............................................................................................................30 Figure 3-11. Pin to Pin Illustration of ABB Protective Daisy Chain Link for IRIG B.................................................31 Figure 3-12. IRIG B Pinout ......................................................................................................................................31 Section 4 – REL 512 Device Parameterization Figure 4-1. Figure 4-2. Figure 4-3. Figure 4-4. Figure 4-5. Figure 4-6. Figure 4-7. Figure 4-8. Figure 4-9. Initial WinECP Configuration Naming Screen.......................................................................................33 Personal Computer Port Identification Screen......................................................................................33 Personal Computer COM Port Parameter Configuration......................................................................33 Communication Port Buffer and Terminal Configuration Screen..........................................................34 Hyperterminal ASCII Setup Screen ......................................................................................................34 REL 512 Root Menu Configuration Screen...........................................................................................35 Configuraton View Submenu Screen....................................................................................................35 Port View Screen ..................................................................................................................................36 COM Port 1 Parameter Reporting Screen ............................................................................................36 Page v REL 512 DNP 3.0 Automation Technical Guide Figure 4-10. Figure 4-11. Figure 4-12. Figure 4-13. Figure 4-14. Figure 4-15. Figure 4-16. Figure 4-17. Figure 4-18. Figure 4-19. Figure 4-20. Figure 4-21. Figure 4-22. Figure 4-23. Serial Port 2 Communication Port Visualization Screen.....................................................................37 Password Entry Screen.......................................................................................................................37 REL 512 Password Protected Submenu ............................................................................................38 COM Port Configuration Access Screen.............................................................................................38 COM Port Selection Screen ................................................................................................................39 COM 0 Port Setting Screen ................................................................................................................39 Serial Com Port 2 Setting Screen .......................................................................................................40 Front Panel Interface Menu Selection Sequence ...............................................................................42 Serial Port 2 Configuration Selection Sequence.................................................................................42 Comm Ports: DNP Menu.....................................................................................................................43 DNP Configuration Screen #1.............................................................................................................43 DNP Configuration Screen #2.............................................................................................................43 DNP Configuration Screen #3.............................................................................................................44 DNP Configuration Screen #4.............................................................................................................44 Page vi REL 512 DNP 3.0 Automation Technical Guide Section 1 - Introduction With the introduction of a microprocessor based protective relay, today’s relay protection engineer must be familiar with topics outside of traditional relaying schemes. It is intended that the production of this manual will enable the relay engineer to understand the principles of a microprocessor-based relay’s inclusion in a substation automation project. Substation automation is heavily dependent upon integration of the appropriate components to allow reporting of metering and event data. The foundation of a successful automation solution is thorough engineering of a communication system. The REL 512 is the culmination of intensive design efforts and relaying experience, which combine protective relaying and communication capabilities at an economical price. Through the evolution of protective relays, it was decided that a special manual needed to serve today’s power automation specialist. This manual is intended to give the reader an in-depth explanation of the communication interfaces available with the REL 512. Successful integration of microprocessor based relays like the REL 512 depends on not just understanding the bits and bytes of a particular protocol. It is the inherent understanding and application of such esoteric topics as physical interfaces, real time control, manufacturer independent device integration, throughput vs. speed of communication, … which influences the success of an automation project. In many cases the individual performing the SCADA integration is not a relay protection engineer. This manual departs from the standard type of relay manual in that each data type is explained and each bit, byte and word meaning is explained. Several application examples are given within each section. A description of each protocol command is illustrated for the benefit of the user. Appendices are included detailing application notes, which augment the text. An explanation of the product’s physical interfaces and the connectivity required is explored in depth. Explanations of register’s uses to increase overall throughput are also explored. Throughput is always an issue when the system is commissioned. Understanding ways to improve the system data update is explained. Several steps are required to permit successful communication between devices: 1. Identification of the hardware components (Section 2). 2. Correct physical connection between devices (Section 3). 3. Correct device configuration of port protocol and operation parameters (Section 4). 4. Generation and interpretation of the protocol command strings (Section 5). The following sections shall explore the following procedures in depth when establishing a communication automation system, utilizing the REL 512. Figure 1-1 shows the general look of the units as viewed from the front. REL 512 Figure 1-1. REL 512 Product Format Page 1 of 145 REL 512 DNP 3.0 Automation Technical Guide The REL 512 offers three protocols, DNP 3.0, Modbus Plus, and REL 512 MENU ASCII. Modbus Plus is a hybrid protocol refinement of Modbus. Modbus Plus has a proprietary physical interface which is available to device manufacturers through a connectivity program with Groupe Schneider. The interface offers greater speed and communication features than Modbus. The REL 512 does have this interface available with the addition of a communication card. DNP 3.0 is a protocol, which has its roots deep in the utility industry. It is an asynchronous protocol that allows connectivity through a standard RS 232 or RS 485 port. It includes such defined capabilities as file transfer, and timestamping as part of the protocol, which makes it desirable for a utility implementation. Within this document, only DNP 3.0 protocol shall be covered in depth. Documentation explaining the REL 512 MENU ASCII PROTOCOL will be attached to this document and explained in Appendix B. Modbus Plus is explained in another document and is available to the user upon request from ABB. Page 2 REL 512 DNP 3.0 Automation Technical Guide Section 2 – Communication Card Identification and Physical Port Characteristics Communciation Card Identification and Physical Port Characteristics The communication connector at the front of the unit (near the target LED’s) communicates to a HYPERTERMINAL utility. This communication port is referred to as COM 0 and is illustrated in Figure 2-1. The protocol emulated through this front port is a REL 512 MENU ASCII PROTOCOL. The front panel port of the REL 512 is a DCE emulation of RS 232. The protocol is not addressable and is intended to be a point to point communication for configuration of the REL 512. COM PORT 0 - REL 512 MENU ASCII REL 512 Figure 2-1. COM 0 Port Location REL 512 Chassis (Rear View) NETWORK PORTS TB1 Model xxxx ct xx pt xx GND TB 2 Network Port 1 Modbus Plus Serial Port 2 Network Port 2A IRIG B Unmod. IRIG B Mod. Unit Identification Label Figure 2-2. Physical Optional Communication Card Port Locations The REL 512 also offers ports at the rear of the relay which echo’s the same communication strings as is done through the front port. The port labeled SERIAL PORT 2 (as illustrated in Figure 2-2) is a hardware configurable port offers DTE RS 232 or RS 485 physical port operation. The operation is configurable via jumpers located on the card. The configuration process is explained in Section 3 of this Automation Technical Guide. Table 2-1 lists the various communication port options available for the REL 512. Page 3 of 145 REL 512 DNP 3.0 Automation Technical Guide Table 2-1. ??? Port Number COM 0 Front Port Network Port 1 Serial Port 2 Network Port 2A Protocol REL 512 MENU ASCII DNP 3.0 REL 512 MENU ASCII Not Available Notes Not Addressable – Hyperterminal attachment OPTION BOARD – Depends on Part Number Not Addressable – Hyperterminal attachment – echo’s the command from the front port. Not Available IRIG B YES YES YES COM 0 and SERIAL PORT 2 are essentially the same port with two different physical interfaces. One cannot use the ports simultaneously. REL 512 COMMUNICATION CARD (DNP 3.0) Figure 2-3. REL 512 Communication Card The REL 512 Communication card is housed within a removable chassis. The communication card mates with edge card connectors located at the front and bottom of the removable chassis. Figure 2-4 illustrates the mounting location of the REL 512 Communication card. Figure 2-2 illustrates the communication port locations of the REL 512. Figure 2-3 illustrates the physical look of the card permitting easy identification. The REL 512 mates with the unit’s main board to enable/disable the Com ports. The communication card’s physical interfaces protrude through the sheet metal back plate housing of the unit and allow for access to the physical connection ports. Figure 2-5 illustrates the location of the communication board assembly. AUX/COM 3.0 Page 4 of 145 REL 512 DNP 3.0 Automation Technical Guide REL 512 NETWORK COMMUNICATION CARD REL 512 RECLOSER BOARD (OPTIONAL) REL 512 Communication Card REL 512 REL 512 DRAW OUT CHASSIS SIDE VIEW TOP VIEW Figure 2-4. Physical Communication Card Location for the REL 512 CAUTION: Removal of the draw out chassis components will de-energize the electronics of the unit thereby preventing system protection. Extreme care must be taken when removing the electronic drawer from the chassis since all protective relay functionality will be terminated. CAUTION: If the unit is under power- the CT’s are shorted internall throught the chassis internal connectors. However, extreme caution must be exercised when removing the draw out case from an energized unit. ABB takes no responsibility for actions resulting from avoidance of this warning and caution notice. CAUTION: Sensitive electronic components are contained within the REL 512 unit. The individual removing the component boards from the fixed chassis must be grounded to the same potential as the unit. If the operator and the case are not connected to the same ground potential, static electricity may be conducted from the operator to the internal components resulting in damage to the unit. Communication Card Part Number Options The REL 512 may be ordered with a variety of communication options as listed in Table 2-1. The communication option card installed in the unit is identified by the part number located on the unit or identified through the front RS 232 port REL 512 MENU ASCII or Front Panel (LCD) interfaces. The protocols available are: DNP 3.0 - This is a Utility industry standard protocol allowing communication between host and slave devices. DNP 3.0 is a byte oriented (asynchronous) protocol, which is physical interface device independent. The protocol allows for time synchronization, and unsolicited event reporting. It is a very popular protocol in utility installations. The discussion of DNP 3.0 protocol is included in this document. MODBUS PLUS – This protocol is also and industrial standard. Modbus Plus allows up to 64 devices to communicate among each using token passing techniques. The Modbus Plus protocol is fast (1 megabaud) and uses several advanced techniques to maximize bandwidth. The physical interface to Modbus Plus is proprietary and regulated by Groupe Schneider. Modbus Plus is the incorporation of Modbus commands on a HDLC- like protocol using a current injection interface. The discussion of Modbus Plus protocol is not included in this document. Please reference the REL 512 Modbus/Modbus Plus Automation Document for a discussion of this protocol. REL 512 MENU ASCII – This protocol is resident on each REL 512 and is a text based ASCII PROTOCOL incorporation. It allows upload/download of oscillographic information and unit settings. Page 5 of 145 REL 512 DNP 3.0 Automation Technical Guide The device configuration for the REL 512 is illustrated in Table 2-1 illustrating the configuration options. The generic part number for the REL 512 is R512H6B1N4ZN1N, where the “Z” digit denotes the type of communication card is resident within the unit. Deciphering the part numbers: found on the labels of the unit or obtained through the front port Hyperterminal connection or the FRONT PANEL LCD INTERFACE, allows easy identification of the communication options found on the unit. Table 2-2. REL 512 Communication Options Options Mounting Frequency Current Rating Battery Voltage Horizontal Vertical 50 Hz 60 Hz 1A 5A 24 V dc 48/60 V dc 110/125 V dc 220/250 V dc Single Breaker BF None with volt / sync check No Reclosing MODBUS Plus DNP 3.0 None None Standard (4-6 ms) High Speed (1 ms) None Cat. # R512 H 6 B 1 N 4 Z N H H . . . . . . . V . . . . . . . . . . . . . . 5 . . . . . . . 6 6 . . . . . . . . . . . . A . . . . . . B . B . . . . . . . . . . 5 . . . . . 4 . . . . . . . 1 1 . . . . 2 . . . . . . . . B . . . . N . . . . N . . . . . . . . . 3 4 . . . . . 4 . . M D N N 1 2 N . . . . . . . . . . . . . . . . . . . . . N . . . . . . . . . . . . N . . 1 . . . . . . . . . . . . . . . . . . . . . . . . . . 1 N . . . . . . . . . . . . . . . . . . . Breaker Failure Multi-shot Reclosing Network Port #1 Network Port #2 Trip Outputs Future . . . . . . . . . . . N The visual identification of a REL 512 communication card is completed through visual inspection of the card component location and of the part number of the base printed circuit board as illustrated in Table 2-3. Table 2-3. REL 512 Communication Card Identification Matrix “Z” Digit M D Description COMM 485 PCB MODBUS PLUS CARD 2000R AUX COM DNP 3.0 CARD Circuit Board Part Number 1618C83G01 1619C18G01 Page 6 of 145 REL 512 DNP 3.0 Automation Technical Guide Unit Communication Card Verification There are several ways to identify the communication cards inserted in the REL 512. Some of the methods require the unit to be powered up. Other methods require the unit to be taken out of service. To identify the unit part number of the present REL 512, the following steps may be executed to facilitate unit identification. UNIT IDENTIFICATION USING HYPERTERMINAL When the unit has HYPERTERMINAL attached and the unit immediately powered the following startup screen as illustrated in Figure 2-5 is visible. The lower right section of the startup screen contains communication card and version information. If the unit is already powered, the information may be obtained in the following way: 1. Return to the ROOT MENU. The screen illustrated in Figure 2-6 shall be visible. 2. Enter selection number [1] View Product Information. The screen illustrated in Figure 2-7 shall be visible. The product number and option cards installed with the appropriate firmware version numbers are available in the unit. UNIT INFORMATION Figure 2-5. Startup Screen With Unit Information Page 7 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 2-6. Root Menu Screen Communcation Card Version and Type. Figure 2-7. Unit Information Screen If a HYPERTERMINAL interface is not available the same information is available through the front panel interface using the procedure illustrated in Figure 2-8. Page 8 of 145 REL 512 DNP 3.0 Automation Technical Guide E -> E -> E -> View Only ID H6B1B3DN1N C PRODUCT ID FRONT PANEL INTERFACE DEVICE NUMBER KEY AND SCREEN SEQUENCE Figure 2-8. Front Panel Interface Part Number Identification Sequence To verify the information obtained via the front panel interface or the HYPERTERMINAL INTERFACE, two additional steps may be performed to verify the options installed in the unit. 1. At the back of the REL 512 chassis, in the left-hand lower section of the unit, a label shall appear indicating the serial number and model number of the unit. It should match the data presented in the Hyperterminal or Front Panel Interface (FPI) menus. If it does not, please contact the factory. 2. As a final check, if the REL 512 can be powered-down and protection can be interrupted, loosen the front panel screws at the front of the unit. Remove the product component drawer from the chassis and verify that the card installed using the procedure described in the card replacement section. If they do not, please contact the factory. Communication Card Installation Communication cards in the REL 512 are field replaceable. Two steps are required in order to install such an option: 1. Installation of the hardware option. 2. Download of the executive firmware to the unit. WARNING: THE RELAY MUST BE TAKEN OUT OF SERVICE AND POWERED DOWN IN ORDER TO COMPLETE THE STEPS ILLUSTRATED. STEP 1: As per Figure 2-9, loosen the front panel interface plate by turning the thumbscrews counter-clockwise. Pull Back the front panel sheet metal plate slightly from the unit to reveal the interconnection ribbon cable. Remove the cable attached to the LED board as illustrated in Figures 2-9 and 2-10. Page 9 of 145 REL 512 DNP 3.0 Automation Technical Guide Interconnection Cable Remove This End from Board. REL 512 REL 512 DRAW OUT CHASSIS SIDE VIEW TOP VIEW Figure 2-9. Removal of Front Plate Figure 2-10. Front Panel Interface Connector STEP 2: While facing the front of the unit, two black card ejectors are available on the unit. One ejector is on the left of the inner chassis and the other is on the right of the inner chassis. Cantilever the ejectors simultaneously to slide the inner chassis and separate it from the outer chassis. Figure 2-11 illustrates the position of the inner and outer chassis after executing this step. Page 10 of 145 REL 512 DNP 3.0 Automation Technical Guide CARD EDGE EXTRACTORS REL 512 REL 512 DRAW OUT CHASSIS SIDE VIEW TOP VIEW Figure 2-11. Separation of Inner Chassis From Outer Chassis STEP 3: Using a flat blade screw driver, loosen and remove the 9 (nine) screws securing the upper I/O PCB as illustrated in Figure 2-12. STEP 4: Using a flat blade screw driver, remove the two screws from the LED PCB. Pull the board towards yourself separating it from the upper and lower circuit board assemblies. This is illustrated in Figure 2-13. STEP 5: FACING THE FRONT OF THE UNIT and raising the edge card connector, a ribbon cable interconnecting the I/O board chassis with the main control board is visible. Detach the cable interconnecting the boards. This step is illustrated in Figure 2-14. STEP 6: Viewing the unit as illustrated in Figure 2-15 and Figure 2-16, the communication board can be installed or removed from the main unit assembly. The communication board mates with the main board through standoff pins resident on the communication card PC assembly. Six (6) screws and one threaded standoff secure the communication board with the main board. PRIOR TO INSTALLING THE BOARD, it should be configured for RS 232 or RS 485 TWO WIRE or RS 485 FOUR-WIRE operation. Please refer to the port configuration instructions at the end of this section. Installation of this board requires that the screws be installed on the unit to secure the board to the chassis. The Jumper locations for RS 232/RS 485-card installation are illustrated in Figure 4-17. STEP 7: Reinstall the PC I/O board. REMEMBER TO FIRST CONNECT THE RIBBON CABLE BETWEEN THE I/O BOARD AND THE MAIN BOARD as illustrated in Figure 2-14. Slide the I/O PCB to mate with the LED EDGE CARD CONNECTOR. Page 11 of 145 REL 512 DNP 3.0 Automation Technical Guide SCREW LOCATIONS Figure 2-12. Screw Location for Removal of Upper I/O Control Board STEP 8: Install the screws to secure the board to the inner chassis. The location of the screws are shown in Figure 2-12. STEP 9: Attach the front panel interface board and secure the front panel interface to the inner chassis motherboard and recloser board with the two screws removed during the installation procedure. Figure 2-13. Slide I/O Board From Edge Card Connector Example Page 12 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 2-14. I/O and Logic Board Interconnection Cable COM CARD STANDOFFS COMMUNICATION CARD CONNECTOR COM CARD STANDOFFS Figure 2-15. Communication Card Interface Mounting Connector DNP COM. CARD Figure 2-16. DNP Card Installation Page 13 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 2-17. Jumper Locations for the DNP Card STEP 10: Slide the board into the chassis back into the REL 512 using the reverse process as illustrated in Figure 2-12. STEP 11: If the installation of the DNP 3.0 board is accomplished in the field, the flash executive may need to be executed in the field. If the existing DNP 3.0 board is in the product and the executive must be downloaded to the DNP board or to the mainboard. The following procedure must be executed to exchange the executive. Please call ABB technical support to verify the latest executive version which operates with the latest DNP 3.0 board and executive firmware. As new firmware releases are made available for the various firmware modules of the REL 512, your existing relay may be upgraded from your PC using a simple and inexpensive parallel interface to the relay. This note discusses the software requirements and how to use the interface to upgrade the REL 512 firmware to new version releases. Parallel Interface Module The interface modules and cables defined in Figure 2-18 are required for the parallel connection of the computer to the relay’s main, reclosing, or network board, depending on the firmware to be loaded. Page 14 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 2-18. Parallel Interface Module and Connections There are three boards (modules) to program with new firmware. The availability of each board depends on the relay’s configuration (options). The boards to be programmed are: Main Board, #1 or #2 (protection functions) Reclosing Board, #1 or #2 (reclosing functions) DNP Board (network communications) Figures 2-19 and 2-20 show the locations and connector (jack) number . . . J47, J90, J5 and JP14, of each board connector to which the 10-pin BDM interface must mate. Main Board #1 The 10-pin connector for the main board #1 is J47 and is located on the main board in front of the large 68360 CPU. If the reclosing board is attached connector J47 is not accessible and the main board 10-pin programming connector is J9 on the right front of the reclosing board and is identified as the main board programming port. Main Board #2 The 10-pin connector for the main board #2 is J90 and is located on the left front of the main board. This connector is accessible with the reclosing board attached and must be used to program the main board. If the reclosing board is attached do not use the main board programming port that is located on the reclosing board. Reclosing Board, #1 and #2 The 10-pin connector for the reclosing board is J5 on the left front of the reclosing board and is identified as the 331 processor programming port. DNP Board The 10-pin connector for the DNP board is JP14 and is located on the front of the DNP board. If the reclosing board is installed the connector will be on the left side under the reclosing connector recessed about two inches. Page 15 of 145 REL 512 DNP 3.0 Automation Technical Guide Making the Connection As you face the relay, pin 1 of the main and reclose connectors are to the right. Make sure the red side of the ribbon cable is also to the right when making the connection. Pin 1 of the DNP connector is to the left. Make sure the red side of the ribbon cable is also to the left when making the connection. Firmware As previously stated there are up to three boards to upgrade with new firmware, each requiring individual programming. Upgrades are executed from Windows and are made separately to the main board, the reclosing board and the network board. The downloadable firmware files for each board are provided in files with .s19 file extensions. The files for each board are described in Table 2-4. Page 16 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 2-19. Connections to the Relay for Different Board Configurations Using Main Board #1 Figure 2-20. Connections to the Relay for Different Board Configurations Using Main Board #2 Page 17 of 145 REL 512 DNP 3.0 Automation Technical Guide Table 2-4. Files Required for Loading New Firmware Main Board #1 MnabvXXX .s19 a=5 -50Hz 6 -60Hz b=1 –1A 5 –5A XXX = Version Main Board #2 MnabvXXX .s19 a=5 -50Hz 6 -60Hz b=1 –1A 5 –5A XXX = Version Reclosing Board #1 Rcl1vXXX .s19 XXX = Version Reclosing Board #2 Rcl2vXXX .s19 XXX = Version DNP Dnpvxxx .s19 XXX = Version Description This is new firmware that is to be loaded on the main board and is provided with a file name that identifies the new version number and applicable rating information . . . frequency, CT input. (XXX = 220 = version 2.20) NOTE: Versions of 2.00 and higher for the Main Board will run only on Main Board #2. NOTE: Versions of 2.00 and higher for the Reclosing Board will run only on Reclosing Board #2. MnabvXXX MnabvXXX Rcl1vXXX Rcl2XXX .cfg .cfg .cfg .cfg a=5 -50Hz 6 -60Hz b=1 – 1A 5 – 5A XXX = Version a=5 -50Hz 6 -60Hz b=1 –1A 5 –5A XXX = Version XXX = Version XXX = Version DnpvXXX .cfg XXX = Version This is a configuration file that calls *.32p and *.s19 files. It may need to be edited to the .s19 file name above (XXX = 220 = version 2.20) NOTE: Versions of 2.00 and higher for the Main Board will run only on Main Board #2. NOTE: Versions of 2.00 and higher for the Reclosing Board will run only on Reclosing Board #2. Main1.32p Main2.32p Recl1.32p Recl2.32p Dnp.32p This is a flash program file for the boards CPU processor. If a different file name is used then configuration file (*.cfg) will need to be modified accordingly. CPROG32W Installation This Step can be skipped if CPROG32W is already installed on your Computer. Go on to next section. Insert the floppy disk with Prog32w 95, 98, NT Version 1.08.exe on it into your floppy drive. From the START menu select RUN. Using the Browse button select the drive with the floppy disk in it and the select the EXE file select OPEN then select OK. Then follow instructions to install the files and use the default installation directory. After installing you will then have to install the NT driver on your computer. This utility along with the associated files will be extracted and put on your computer but, will have to be run separately. Read the TXT files that are supplied during the installation for more information. Program File Installation Insert the floppy disk with MAIN Board label on it into your floppy drive. Using Explore (Press the Key with the windows symbol on it and ‘E’ simultaneously) copy the REL512 directory to the root of your C: or D: drive. If it says that the directory already exists do you want to over write? Say YES. Repeat this with the disk that contains the Recloser and DNP board software as well if you need them. Page 18 of 145 REL 512 DNP 3.0 Automation Technical Guide Each disk contains in its root a REL512 directory. This directory on each disk will contain a CONFIG directory and a PLATFORM directory. If the disk contains DNP code, then in addition to the two directories (CONFIG and PLATFORM) it will contain a DNP directory. Under the DNP directory will be another directory that will have a name VerX.XX where X.XX will be the version of code contained there in. If the disk contains RECLOSER code then in addition to the two directories (CONFIG and PLATFORM) it will contain a RECLOSER directory. Under the RECLOSER directory will be two directories HW1 and HW2 each will contain a directory that will have a name VerX.XX, where X.XX will be the version of code contained there in. If the disk contains MAIN code then in addition to the two directories (CONFIG and PLATFORM) it will contain one of four directories either 60HTZ_1A, 60HTZ_5A, 50HTZ_1A or 50HTZ_5A directory depending on the platform ordered. Under the 60HTZ_1A, 60HTZ_5A, 50HTZ_1A or 50HTZ_5A directory will be another directory that will have a name VerX.XX where X.XX will be the version of code contained there in. If you have ordered 60 hertz 5 amp ver 1.57 code with a hardware platform 1 recloser version 1.25 and DNP version 2.20 then the directory structure will look like: \REL512 \PLATFORM \CONFIG \DNP \VER2.20 \60HTZ_5A \VER1.57 \RECLOSER \HW1 \VER1.25 \HW2 \VER2.00 After installation find the directory that CPROG32W.EXE is located in (C:\PEMICRO) and right click on it and select ‘Create Shortcut’. Right click on the shortcut just created, select COPY and then go to the directory X:\REL512\CONFIG (Where X is the drive the files are located on) and place the shortcut to CPROG32W.EXE in this directory with PASTE. The directory should now contain the shortcut just copied and several *.CFG files copied from the firmware disk(s). Loading the Firmware The following procedure is recommended to reliably load the firmware: 1. De-energize the REL 512 to be upgraded. 2. Remove the front panel and disconnect the LCD display (UI) cable. Set the front panel aside. WARNING: DO NOT CONNECT OR DISCONNECT THE FRONT PANEL LCD DISPLAY WHILE THE REL512 IS ENERGIZED. 3. Draw out the inner boards to the extent necessary to make the connections. 4. Make the relay to computer connection per Figure 1. 5. Reinsert the inner boards to their installed position. 6. Energize the relay and check the power LED on the main board to assure it is lit. The LED’s on the UI module will not illuminate when programming the main board. 7. Go to the directory X:\REL512\CONFIG. (Where X is the drive the files are located on) 8. Highlight the CFG file required for the board you are programming. 9. Left click on that file and drag it over the shortcut to CPROG32W.EXE and release it. This will start the program and begin programming the board. 10. Observe the loading operation. Microprocessor will be reset and the 32P file will be loaded. This will be done twice. Then the srecord will be loaded, the FLASH will be erased, then it will be Programmed and then verified. If this process was successful the CPROG32W program will terminate. If there was an error the Page 19 of 145 REL 512 DNP 3.0 Automation Technical Guide 11. 12. 13. 14. CPROG32W.EXE program WILL NOT TERMINATE and will display the point where the error occurred. If any error occurs recheck all connections and repeat this step. When the new firmware is loaded, de-energize the relay and remove the connection. Replace the front panel making sure to connect the LCD cable. Energize the relay. Observe firmware version number during the boot process. The relay should boot correctly. Once the relay has booted check menu item #1, Product Information, to insure the correct firmware has been loaded. Run a simple test to verify relay operation with the new firmware. Serial Port 2 Configuration Within the REL 512 are two serial ports which are configured for point to point operation. As illustrated in Table 25, some of the ports may be configured for RS 232 or RS 485 whereas some ports are fixed configuration. Table 2-5. Physical Interface Emulation and Configuration Port Number COM 0 Front Port Network Port 1 Serial Port 2 Physical Interface REL 512 MENU ASCII DNP 3.0 REL 512 MENU ASCII RS 485 Configurable NO YES – 2 WIRE or 4 WIRESoftware AND Hardware Configurable YES 2 WIRE or 4 WIRE – Hardware Configurable RS 232 Configurable NO - FIXED RS 232– DCE EMULATION YES - JUMPER CONFIGURABLE –RS 232 DTE EMULATION YES - JUMPER CONFIGURABLE –RS 232 DTE EMULATION The method to configure the hardware jumpers is covered in Section 3 of this technical guide. Locating the hardware jumpers for the com port 1, is an extension of the procedure as previously discussed in this section. Figure 2-21 illustrates the location of RS232/RS 485 hardware configuration jumpers. SERIAL PORT JUMPERS Figure 2-21. Serial Port 1 COM Card Jumper Locations Page 20 of 145 REL 512 DNP 3.0 Automation Technical Guide Section 3 – REL 512 Device Connectivity REL 512 Device Connectivity Communication between devices is only possible through connectivity of the units through a physical media interface. There are two physical interface types on a REL 512. Those physical interfaces are: RS 232 (non-isolated) RS 485 (non-isolated) Table 3-1 lists the characteristics for each of the port types. Table 3-1. Physical Interface Options Front Port Network Port 1 Serial Port 2 Port Type RS 232 NON ISOLATED RS 232/RS 485 NON ISOLATED Modbus Plus RS 232 or RS 485 NON ISOLATED Notes REL 512 MENU ASCII – DCE EMULATION of RS 232 Dependent on HARDWARE and SOFTWARE SETTINGS AND CARD SELECTED. REL 512 MENU ASCII DTE EMULATION FOR RS 232 RS 232 Interface Connectivity RS 232 is perhaps the most utilized and least understood communication interface in use. RS 232 is sometimes misinterpreted to be a protocol; it is in fact a physical interface. A physical interface is the hardware and network physical media used to propagate a signal between devices. Examples of physical interfaces are RS 232 serial link, printer parallel port, current loop, V. 24, IEEE Bus… Examples of network media are, twisted copper pair, coaxial cable, free air… RS 232 gained widespread acceptance due to its ability to connect to another RS232 device or modem. A modem is a device, which takes a communication signal and modulates it into another form. Common forms of modems include telephone, fiber optic, microwave, and radio frequency. Modem connectivity allows attachment of multiple devices on a communication network or allows extension of communication distances in a network with two nodes. Physical connection of two devices or more than two devices require differing approaches. Figure 3-1 illustrates a topology using two devices (point to point topology). Figure 3-2 illustrates a multi-drop topology between many nodes. RS 232 was designed to allow two devices to communicate without using intermediate devices. Port Isolation Network installation within a substation requires special considerations. A substation environment is harsh in that high levels of electromagnetic interference are present. Additional ground currents are present in such installations. RS232 is an unbalanced network in that all signals are referenced to a common ground. On longer cable runs, the potential of the signals at the sending device can be significantly lower than at the receiving end due to electrical interference and induced ground current. This increases with long runs of cable and use of unshielded cable. ABB’s Substation Automation and Protection recommends the length of RS232 cable be less than 10 feet (3 meters) for an un-isolated port and that the cable be shielded. Internal to a typical device, the RS232 transceivers are referenced to the electronic components internal ground. Any electrical interference could be coupled through the chip set and fed back to the device. All COM PORTS ON THE REL 512 are non – isolated. RS 232; isolated ports are limited in connection distance for a maximum of fifty feet. Page 21 of 145 REL 512 DNP 3.0 Automation Technical Guide Point to Point Topology Personal Computer Hyperterminal Front Panel Port C E REL 512 Figure 3-1. Point to Point Architecture Using RS 232 RS 232 Handshaking Defined Handshaking is the ability of the device to control the flow of data between devices. There are two types of “handshaking”, hardware and software. Hardware handshaking involves the manipulation of the RTS (Request to Send) and CTS (Clear to Send) card control signal lines allowing data communication direction and data flow rates to be controlled by the DTE device. Also the flow is controlled by the DTR (Data Terminal Ready) signal which allows the DCE operation. Software handshaking involves the data flow control by sending specific characters in the data streams. To enable transmission, the XON character is transmitted. To disable reception of data, the transmitting device sends an XOFF character. If the XOFF character is imbedded within the data stream as information, the receiving node automatically turns off. This is the main weakness of software handshaking, inadvertent operation due to control characters being imbedded within data streams. Software handshaking is usually used in printer control. The REL 512 front panel interface does not incorporate handshaking. The Network 2 and Serial Port 2 may support handshaking if the port is configured as such. If an interconnection cable between a PC and the REL 512 is constructed for the front port, the control lines need not be added as illustrated in Figure 4. However, some PC software utilizes handshaking, thus the port on the personal computer may require a special hardware configuration of the cable to the port. Consult with the software vendor to determine RS232 control and buffering requirements and the need for signal jumpers required in RS232 cabling. The ports on the REL 512 have been tested for operation up to a speed of 115,200 baud. 19,200 baud is the typical data rate applicable for the operation of an asynchronous communication connection over RS 232 without the use of additional timing lines. Page 22 of 145 REL 512 DNP 3.0 Automation Technical Guide Host Executing HMI Software The Cloud. C E REL 512 C E REL 512 STATUS C E TPU 2000 Figure 3-2. Multi-Drop Topology Using RS 232 with Modems RS 232 Cable Connectivity A cable diagram is illustrated in Figure 3-3 and 3-4. Figure 3-3 shows the direction of communication signal transmission and the gender of the connectors used in constructing a communication cable. Protective Relay 2 3 5 Transmit Data Receive Data Ground PC 2 Transmit Data 3 Receive Data 5 Ground 1 * Data Carrier Detect 6 *Data Set Ready 4 * Data Terminal Read 7 *Request To Send 8 *Clear To Send -No connection9 Ring Indicator DCE 9 pin D shell Male Connector DTE 9 pin D shell Female Connector REL 512 Connection for the Front Panel COM 0 to PC Cable 9 to 9 Pin-out Figure 3-3. COM 0 DB 9 to DB 9 Cable Pinout Page 23 of 145 REL 512 DNP 3.0 Automation Technical Guide Protective Relay 3 5 PC 2 Transmit Data 3 Receive Data 5 Ground 1 * Data Carrier Detect 6 *Data Set Ready 4 * Data Terminal Read 7 *Request To Send 8 *Clear To Send -No connection 2 Receive Data Transmit Data Ground 7 *Request To Send 8 *Clear To Send DTE 9 pin D shell Male Connector DTE 9 pin D shell Female Connector REL 512 Connection for the Rear Panel Serial Port 2 to PC Cable 9 to 9 Pin-out Figure 3-4. Rear Serial Port 2 COM Port Cable An RS 232 interface was designed to simplify the interconnection of devices. Definition of terms may demystify issues concerning RS 232 interconnection. Two types of RS 232 devices are available, DTE and DCE. DTE stands for Data Terminal Equipment whereas DCE stands for Data Communication Equipment. These definitions categorize whether the device originates/receives the data (DTE) or electrically modifies and transfers data from location to location (DCE). Personal Computers are generally DTE devices while line drivers/ modems/ converters are DCE devices. The rear Serial port when configured for RS 232 devices have RS232 DTE implementation. The front panel serial port on the REL 512 is a DCE emulation. Generally, with a few exceptions, a “straight through cable”(a cable with each pin being passed through the cable without jumpering or modification) will allow a DTE device to communicate to a DCE device. If one wishes to install modem connectivity between a host device and a REL 512 , please consult the modem application note presented in APPENDIX B of this document. Connection of a PC to a REL 512 front panel interface does not require a cable modification since the interconnected devices are DTE and DCE. The classifications of DTE/DCE devices allow the implementers to determine which device generates the signal and which device receives the signal. Studying Figure 3-5, Pins 2 and 3 are data signals, pin 5 is ground whereas pins 1,6,7,8,9 are control signals. The arrows illustrate signal direction in a DTE device. Depending upon the port selected, handshaking signals may be enabled or disabled for Serial Port 2 or Network port 2. The configuration procedure is accomplished via the REL 512 FRONT PANEL INTERFACE screens available through the Hyperterminal utility. Page 24 of 145 REL 512 DNP 3.0 Automation Technical Guide If a host device has an RS 232 physical interface with a DB 25 connector, reference Figure 3-5 for the correct wiring interconnection. RE L 5 12 Relay 3 2 5 Tra nsm it D at a R ec eive Da ta G roun d 3 2 5 8 6 20 4 5 -N o co n ne ction 22 PC Tra nsm it D at a R ec eiv e Da ta G ro un d D ata C arrie r De tec t D ata Se t R ea dy D ata Term inal R ead y R eq ue st To S end C le ar To S en d R in g In di cat o r D CE 9 p in D sh ell M a le C o nn e c to r D TE 2 5 pin D she ll M a le C o nn e c to r Figure 3-5. Connection of a DB 25 Connector to a REL 512 Front Port Interface Another common method to interface relays. RS 485 Device Connectivity With REL 512 RS 485 is one of the more popular physical interfaces in use today. It was developed as an enhancement of the RS422 physical interface. Its inherent strength is its ability to transmit a message over a twisted pair copper medium of 3000 feet in length. An RS 485 interface is able to transmit and receive a message over such a distance because it is a balanced interface. That is, it does not reference the signal to the system’s electrical ground, as is the case in an RS 232 interface. RS 485 references the communication voltage levels to a pair of wires isolated from system ground. Depending on the manufacturer’s implementation, isolation may be optical or electronic. RS 485 has two variants, two-wire and four-wire. In the two-wire format, communication occurs over one single wire pair. In four-wire format, communication occurs over two wire pairs, transmit and receive. The two-wire format is the most common in use. The REL 512 supports half duplex two-wire and four wire full duplex format. The RS 485 network supported and recommended by ABB requires the use of three or 5 conductor shielded cable. Suggested RS 485 cable and the respective manufacturer’s wire numbers are: • • • • ALPHA 58902 Belden 9729 Belden 9829 Carol 58902 ABB does not support deviations from the specified cables. The selected cable types listed are of the type which have the appropriate physical and electrical characteristics for installation in substation environments. There are many manufacturers of RS 232 to RS 485 converters. Included in Appendices D and E contain additional application notes for using B & B and Telebyte physical interface converters with ABB protective relays. Although many 232/485 converter devices operate well using DNP 3.0 and ABB relays, the appended application notes are intended to convey to the reader that knowledge of interconnecting devices is important when implementing various vendors equipment. Page 25 of 145 REL 512 DNP 3.0 Automation Technical Guide DNP Card RS 485/RS 232 Configuration The DNP Module is capable of communicating with either an RS232 or RS485 interface. This interface is user selectable; but requires both hardware and software configuration. The following notes and tables describe how to configure the hardware: • Factory jumper settings on the DNP card are set for RS-232 communications (JP1-4 position 1-2) 9600, 8-N1, RTS and CTS disabled. The female RS-232 DB-9 connector is configured as DCE meaning it may be connected through a straight cable to DTE device like a PC com port, or a null modem cable when connected to another DCE device like a modem. The DNP card is also capable of communicating over full-duplex or half-duplex RS-485. The card will have to be removed from the unit in order to make the jumper selections between the different communication options. The table below describes jumper settings. It is also printed on the PCB silkscreen. • Table 3-2. DNP Card Jumper Settings for the DNP 3.0 Port or the Serial Port 2 Ports Jumper Pins 1,2 2,3 Mode Selection: JP1-4 RS-232 RS-485 RS-485 Configuration JP5 Half duplex Full duplex JP6 2 wire 4 wire JP7 2 wire 4 wire RS-485 Termination/Bias Resistors: JP8 121Ω Open JP9 523Ω Open JP10 523Ω Open The female DB-9 connector has the following pin-out: Table 3-3. DB-9 Connector Pin-out DB-9 Pin-out: 1 2 3 4 5 6 7 8 9 RS-232 n/c TxD RxD n/c GND n/c RTS CTS 5V RS-485 n/c Y Z A GND B n/c n/c 5V 2 Wire Connection --Non-inverted Inverted --GND ------5V 4 Wire Connection --Tx Non-inverted Tx Inverted Rx Non-inverted GND Rx Inverted ----5V The internally provided termination and biasing resistors are designed for a two-wire system. External termination may be required across the Y-Z transmitter pair for a four-wire network topology. Page 26 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 3-6. DNP 3.0 COM Card Jumper Locations IRIG B Implementation in the REL 512 IRIG B is a time code, which allows devices across the world to synchronize with a common time source to a resolution of one millisecond. IRIG B allows each device to synchronize with the frame received by an IRIG B receiver. ABB’s DPU/TPU/GPU 2000/R and REL 512 relays (herein referred to as an IED) offer IRIG B time synchronization capabilities. Figure 3-7 illustrates a typical IRIG B installation. An IRIG B time receiver accepts the RF signal and transforms it into a one second time synch frame. IEDs in the substation use the one second time synch frame to govern their internal clocks and event recorders. A. Satellite Synch Signal Received. B. Dish Sends received signal to the downlink/receiver. In the Substation C E True Time C. Demodulated signal transferred to IEDs. C E C E Figure 3-7. Typical IRIG B Architecture IRIB B receivers/converters can format the IRIG B synchronization frames as a TTL-level pulse width, Manchester Encoded or Modulated Carrier Frequency signal. TTL-level signals are pulse DC with a voltage range of 0 to 5V. Modulated Carrier Frequency signals are pulse coded AM signals with modulation (tone bursts). IRIG B is a general designation for time synchronization. There are many subsets to the IRIG B format. These were developed to provide functionality primarily for military applications dealing with missile and spacecraft tracking, telemetry systems, and data handling systems. IRIG B was embraced by the utility industry to answer a need to provide a sequence of events capability between a group of substations. Care must be exercised to Page 27 of 145 REL 512 DNP 3.0 Automation Technical Guide match the device demodulating the signal from the satellite (downlink converter) with the IED’s requiring specific IRIG B code formats. DPU/TPU/GPU products support Pulse Width Code (X= 0), whereas, REL 3XX products having an IRIG B Poni Card and the REL 512 supports Pulse Width Code and Sine Wave Amplitude Modulated. If the IRIG signal supplied to the device is one in which the attached device cannot decode, the IED shall not synchronize with the signal and IED will not calculate time correctly. The IRIG B time code has a one second time frame. Every frame contains 30 bits of Binary Coded Decimal time information representing seconds, minutes, hours, days and a second 17 bit straight binary time-of-day. The frame has internal time markers, which insure time-stamping accuracy to the millisecond. An eight millisecond frame reference marker appears during the first ten milliseconds of each frame. Another eight millisecond position identifier appears during the ninetieth millisecond of each one hundred millisecond period mark. The 30 bit Binary Coded Decimal time data occurs in the first one hundred millisecond of each 1 second frame. Optional control functions are sometimes encoded in the data stream. These functions control deletion commands and allow different data groupings within the synchronization strings. Decoding an IRIG B pulse is quite a complex undertaking. A typical 1 second time frame is illustrated in Figure 3-8. It is interesting to note that the year is not included within the IRIG B frame. If the Control Function frame (CF) or Straight Binary Time of Day frame (SBT) is not used , the bits defined within those fields are to be set as a string of zeroes and sent to the IED IRIG B receiver. 1 Second Frame in 10 mS increments 0 10 20 30 40 50 60 70 80 90 0 Seconds Minutes Hours Days Control Functions Straight Binary Time of Day Marker Pulses every 10 mS for an 8 mS duration Figure 3-8. IRIG B Frame Construction IRIG B is defined for code format sets identified by a three digit format number. Permissible format numbers for the IRIG B subsets are: IRIG B XYZ Where: The first field "X" identifies the encoding type of the IRIG B signal. DPU/TPU/GPU products support Pulse Width Code (X= 0), whereas, REL 3XX products having an IRIG B PONI Card support Pulse Width Code and Sine Wave Amplitude Modulated, and REL5XX products support Sine Wave Amplitude Modulated IRIG. Manchester Modulated code was added in IRIG Standard 200-98 Dated May 1998. It is not supported in the ABB protective relay products which are IRIG B capable. The second field "Y" determines if a carrier is included within IRIG B Data format. The third field "Z" determines if a combination of the BCD time/ Control Function/ Straight Binary Time is included within the IRIG B time frame. The inclusion or exclusion of any of the fields may cause errors in receivers not designed for the field’s inclusion/ exclusion. The following combinations may seem daunting, but only a subset of the listed formats are actually defined within the specification. If X = 0 1 2 = Pulse Width Code (Supported by the REL 512). = Sine Wave Amplitude Modulated (Supported by the REL 512). = Manchester Modulated Code Page 28 of 145 REL 512 DNP 3.0 Automation Technical Guide If Y = 0 2 3 4 5 If Z= 0 1 2 3 = No Carrier =1Khz , 1mS =10Khz, 0.1 mS =100 Khz, 10 mS =1Mhz, 1mS =BCD Time,Control Function, Straight Binary Seconds =Binary Coded Decimal Time, Control Function =Binary Coded Decimal Time =Binary Coded Decimal Time, Straight Binary Seconds For the REL 512, TPU/GPU/DPU 2000/2000R products, IRIG B 000 and 002 formats are supported. Additionally, the REL 512 supports the modulated IRIG B 110 and 112 formats. Consult the IRIG B generator manufacturer so that the correct IRIG B code format is supplied to the receiving IED’s. Hardware Configuration REL 512 Chassis (Rear View) TB1 Model xxxx ct xx pt xx GND TB 2 Network Port 1 Modbus Plus Serial Port 2 Network Port 2A IRIG B Unmod. IRIG B Mod. IRIG B Unmodulated Port IRIG B Modulated Port Figure 3-9. IRIG B Port Locations ABB’s implementation of IRIB B requires that the signal be daisy-chained to each device. Each device in the IRIG B network presents a load to the IRIG B receiver/converter. Daisy-chained inputs are simple parallel circuits. A sample calculation is shown for the example illustrated in Figure 3-910 If the input impedance of each DPU/TPU/GPU 2000/R OR PONI is measured at its IRIG B connection, the impedance would be 1000 ohms. If THE REL 512 IMPEDANCE IS MEASURED AT THE IRIG B Unmod Port the IMPEDANCE IS 1000 ohms. If the REL 512 IMPEDANCE IS MEASURED AT IRIG B Mod. THE IMPEDANCE IS 50 ohms. Each IRIG B input requires at least 6 mA / per IED to drive the internal circuitry. A typical unmodulated IRIG B source generates a voltage of 5V as per definition. One should perform a load calculation and a current budget to match the source capability with the loading of the IEDs attached to the IRIG B circuit. Calculating the load impedance presented to the IRIG B unmodulated source generator is illustrated in Figure 310. Each IED load on the IRIG B link presents parallel impedance to the source. The general equation for parallel impedance is: Page 29 of 145 REL 512 DNP 3.0 Automation Technical Guide 1 = 1 ZTotal Z1 ITotal = I1 + + 1 Z2 I2 + + 1 Z3 I3 + + ... ... This impedance equation simplifies to the form in Figure 3-10 when all IED loads are identical. If the loads are not identical, the general equation listed above must be used to calculate the load. 1000 ohms = 1 unit load. Ztotal = Load presented to the IRIG B Generator as per example in Figure 1 1000 Ohms 1000 Ohms 1000 Ohms Ztotal = 1/(N*(1/1000)) Z total = 1/(3*(1/1000)) Z total = 333.33 ohms. where N = number of DPU/GPU/TPU 2000/R Units. Thus the Source must be capable of driving a 333.33 ohm load. Figure 3-10. Load Impedance Calculation The calculated load impedance for the architecture presented in Figure 3-10 is 333.33 ohms. In this example the IRIG B receiver/converter must be capable of sending a three milli-amp TTL-level signal to a 333.33 ohm load. If the source is not matched with the load impedance, IRIG B will not operate correctly. The cable recommended to connect the IRIG B devices shall have the following characteristics: Capacitance: Construction: less than 40 pF per foot line to shield 2-wire twisted pair shielded with PVC jacket Cable types and vendors The maximum lead length of the entire relay is to be no more than 1000 feet. recommended and supported by ABB to interconnect the IRIG B devices are: BELDEN 9841, BELDEN YM29560, or equivalent An example of the terminal to terminal daisy chain interconnection of three units is illustrated in Figure 3-11. Page 30 of 145 REL 512 DNP 3.0 Automation Technical Guide IRIG B SOURCE IRIG B Positive (to Source Terminals IRIG B Negative (to Source Terminals) Shield At Ground (one point only) 74 73 72 71 70 69 68 67 66 65 AUX COM PORT 55 56 57 58 59 60 61 62 63 64 AUX COM PORT Unmod IRIG B Com 3 TB1ct xx pt xx Model xxxx TB 2 . . TPU 2000 DPU 2000R REL 512 Figure 3-11. Pin to Pin Illustration of ABB Protective Daisy Chain Link for IRIG B IRIG B PIN DESIGNATION Unmodulated Port IRIG B (-) Modulated Port IRIG B (-) UNUSED IRIG B (+) IRIG B (+) VIEWED FROM FRONT Figure 3-12. IRIG B Pinout Page 31 of 145 REL 512 DNP 3.0 Automation Technical Guide Section 4 – REL 512 Device Parameterization REL 512 Device Parameterization Establishing REL 512 communication depends upon correct parameterization of the communication ports. Parameterization may occur via the unit’s FPI (for the front panel interface), or through the RS 232 COM 0 serial port at the front of the unit or via the Serial Port 2 interface resident at the back of the REL 512. Configuration via the communication ports are accomplished via a HYPERTERMINAL utility (or other dumb terminal emulator utility) . Modbus, Modbus Plus and DNP require parameterization, however, only the parameterization methods for DNP port configuration are covered in this section. Even COM 0 requires certain parameterization to communicate with the configuration program. Port Configuration In order to attach a configuration terminal to the REL 512 front port, the correct parameters must be set up within the unit. The supported parameters are listed in Table 4-1 below. The protocol for the unit is non addressable REL 512 MENU ASCII. Initial identification of communication port parameters should be viewed via the unit’s front panel interface. Twelve Front Panel pushbutton operations are required to obtain the menu to view the configured parameters for COM 0 or Serial Port 2. If the front panel interface parameters are known, then parameterization may occur through a dumb terminal emulator. An example of a dumb terminal emulator is Hyperterminal. Hyperterminal Setup for REL 512 Configuration Configuration of the Hyperterminal Utility is a simple and straightforward procedure. The configuration sequence is illustrated as follows: STEP 1: Start HYPERTERMINAL. From the Drop Down Windows menu beneath the File heading, a NEW CONNECTION will be visible once selection is accepted. The screen for naming the new connection being created is illustrated in Figure 4-1. STEP 2: Once the connection session is configured, the communication port with which the personal computer will attach to the REL 512 must be identified. The screen illustrated in Figure 4-2 is shown and in this case, the personal computer will be using COM 1. STEP 3: Upon identification of the port , the settings for that port must be configured as illustrated in Figure 4-3. The illustrated port parameters are the default parameters for the REL 512. The parameters are available from the File menu selection and selecting the Properties submenu selection. Enter the appropriate Baud Rate, Data Bit Selection, and Parity for the associated devices. Note that handshaking is not required and therefore is not selected in any of the checkboxes of the illustrated menu. STEP 4: The selection button labeled Advanced, when selected will allow the user to configure the HYPERTERMINAL selection for the port. Figure 4-4 illustrates the selection for the associated communication port. STEP 5: Depressing the Ascii Setup Pushbutton visible on the HYPERTERMINAL screen allows for visualization of the diagram illustrated in Figure 4-5. This screen configures the duplex of the communication connection (using the ECHO CHARACTER field to configure half or full duplex). Set the parameters as illustrated. STEP 6: The HYPERTERMINAL configuration procedure is now complete. Save the session by selecting the Save option beneath the File menu heading. Page 32 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 4-1. Initial New Configuration Naming Screen Figure 4-2. Personal Computer Port Identification Screen Figure 4-3. Personal Computer COM Port Parameter Configuration Page 33 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 4-4. Communication Port Buffer and Terminal Configuration Screen Figure 4-5. Hyperterminal ASCII Setup Screen Hyperterminal Based Port Configuration Visualization Sequence All the communication ports on the REL 512 may be configured via the Hyperterminal Interface. Only COM 0 (the front port) and the rear Serial Port 2 may be configured via the front panel interface. The REL 512 Communication Configuration Sequence using Hyperterminal is covered in this section. The ROOT REL 512 menu is illustrated in Figure 4-6. Page 34 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 4-6. REL 512 Root Menu Configuration Screen To view the existing settings on the communication ports, select option [2] View Configuration Settings. It is important to realize that to maneuver between screens, the “/” key allows paging to the previously viewed screens. If selection [2] is accepted, the screen shown in Figure 4-7 will be visible. It should be remembered that this screen only allows for visualization of the communication parameters. Modification of REL 512 port parameters may only be accomplished via selection [6] Password Functions. Figure 4-7. Configuration View Submenu Screen If menu item [3] COM PORT is selected, each parameter of the communication ports may be visualized. If menu item [3] COM PORT is selected the screen illustrated in Figure 4-8 is available for viewing. Page 35 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 4-8. Port View Screen Figures 4-9 and 4-10 illustrate the submenus for viewing the com port parameter visualization screens for submenus [1] Front Com Port and [2] Rear Com Port. Selection [3] Modbus Plus will not be covered in this manual. Selection [4] DNP shall be covered in the Network Port 1 DNP configuration section. Figure 4-9. COM Port 1 Parameter Reporting Screen Page 36 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 4-10. Serial Port 2 Communication Port Visualization Screen COM 0 (Front Port) and Serial Port 2 Configuration Screens As opposed to the previous section where the communication port parameters were viewed via HYPERTERMINAL screens, the following setup procedure shall enable the user to change the settings as opposed to viewing the configured parameters. STEP 1: From the ROOT MENU illustrated in Figure 4-6, Selecton [6] PASSWORD FUNCTIONS will enable the user to access submenus allowing modification of the REL 512 parameters. Enter “6” to enter this submenu system. STEP 2: The PASSWORD menu shall be displayed as illustrated in Figure 4-11. Enter the associated password. The default password for the REL 512 is ABB. Depress the “ENTER” key to accept the password. STEP 3: The submenu to access and change the communication port parameters is located in the selection [1] EDIT CONFIGURATION SETTINGS. Enter “1” to enter this submenu system. The screen of this submenu is illustrated in Figure 4-12. Figure 4-11. Password Entry Screen Page 37 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 4-12. REL 512 Password Protected Submenu STEP 4: The screen shown in Figure 4-13 should now be visible. Submenu selection [3] COM PORTS shall allow the user to access the final submenus for configuration of the communication ports. Enter “3” to display the submenu illustrated in Figure 4-14 allowing for selection of the appropriate communication port to be configured. Figure 4-13. COM Port Configuration Access Screen Page 38 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 4-14. COM Port Selection Screen STEP 5: If COM Port 0 is to be configured, Enter “1” to display the Front Panel Parameters. Enter “2” to display the Rear Com Port Parameters (Network Port 2). The screens displayed are illustrated in Figures 4-15 and 4-16. Each parameter which may be modified is highlighted. To change the setting, use the “↓” or “↑” to navigate between the settings fields. Depress the “ENTER” key to select the appropriate setting as denoted in Table 4-1. Figure 4-15. COM 0 Port Setting Screen Page 39 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 4-16. Serial Com Port 2 Setting Screen Front Panel Interface COM Port Configuration Sequence The keystrokes required for visualizing the communication port parameters from the metering display are illustrated in Figure 4-17. Once this Front Panel Interface screen is visible, menu options are available for front port (COM 0) or rear port (Serial Port 2) configuration. E Fault Records > Device Info < Edit Settings C Metering E Device Info > View Settings < Edit Settings C Metering E Edit Settings > Fault Records < View Settings C Metering E Edit Settings > Fault Records < View Settings C Metering E Password ****** C Edit Settings E Password < ACCEPTED C Edit Settings E Sys Settings > Act Settings C Edit Settings E Change Act Grp > Identification C Sys Settings E Identification > System Params < Date & Time C Sys Settings E System Params > Comm Ports < Identification C Sys Settings E Comm Ports > Data Recording < System Params C Sys Settings E FRONT Port > REAR Port < Modbus ID C Comm Ports Step 1 Step 2 Step 3 Step 4 Step 7 Step 8 Step 9 Step 10 Step 5 Step 6 Step 11 Step 12 One may change parameters via the front panel interface. The selections for each parameter required in Front Panel Port configuration is shown in Table 4-1. Step 1: Depress E to display the screen illustrated in Figure 4-17 STEP 1. Step 2: Depress the “→” key to display the Device Info submenu illustrated in STEP 2 in Figure 4-17. Step 3: Depress the “←” key to display the Edit Settings Submenu as illustrated in STEP 3 in Figure 4-17. Page 40 of 145 REL 512 DNP 3.0 Automation Technical Guide Step 4: Depress the “E” key to display the View Settings Submenu as illustrated in STEP 4 in Figure 4-17. Step 5: Enter the password using the “→”,“←” keys to move between the password digits. The “↑” and “↓” to cursor up and down for different numeric and alphabetic digits. When the complete password is entered depress “E” to accept the input data. The menu for password selection is visible in Figure 4-17 Step 5. If the REL 512 accepts the password, the submenu illustrated in Figure 4-17 Step 6 is visible. Step 6: Depress the “←” key to Accept the password and transition the display to show the menu illustrated in Step 7 Figure 4-17. Step 7: Depress the “→” Actual settings submenu then depress the “E” key to display the menu as illustrated in Step 8 Figure 4-17. Step 8: The Identification Submenu should be selected by depressing the “→” key to allow visualization of the menu illustrated in Step 9 Figure 4-17. Step 9: Depress the “→” System Params key to view the submenu as illustrated in Step 10 Figure 4-17. Step 10: Depress the “→” Com Ports Selection to display the submenu as illustrated in Step 11 Figure 4-17. Step 11: Depress the “E” key to obtain the submenu for parameterization of the Front or Rear communication ports. Selection of the “E” Front Port or “→” Rear Port will allow visiualization of the parameterization screens available for changing or viewing the communication parameters for the aforementioned ports. The visible screen is illustrated in Figure 4-17 Step 12. Table 4-1. REL 512 Com Port 0, Serial Port 2 Front Panel Interface Parameters Option Baud Selection 2400 9600 19200 115200 7 8 Odd Even None 1 2 Notes Selectable Baud Rates for the Standard Ten Byte Front Panel Port. Data Frame Length Word Length Parity Stop Bits Front Panel Interface COM Port Parameterization Modification of the front port COM 0 settings is accomplished by continuing the following keystroke sequences as continued from Figure 4-17 and illustrated in Figure 4-18. Page 41 of 145 REL 512 DNP 3.0 Automation Technical Guide If Front Port Selected “E” E FRNT Bit Rate > FRNT Data Lgth < FRNT Stop Bits C FRONT Port E FRONT Port > REAR Port < Modbus ID C Comm Ports E Enter System Group < 9600 C FRNT Bit Rate IF E Selected to change Baud. E FRNT Data Lngth > FRNT Parity < Frnt Bit Rate C Front Port E FRNT Stop Bits > FRNT Bit Rate < Frnt Parity C Front Port E FRNT Data Lngth > FRNT Parity < Frnt Bit Rate C Front Port E Enter System Group <8 C FRNT Data Lgth E Enter System Group <2 C FRNT Stop Bits E FRNT Parity > FRNT Stop Bits < Frnt Data Lgth C Front Port If “>” Selected to set Data Length. If “<“ Selected to set Stop Bits. E Enter System Group < Even C FRNT Parity To Select Parity Enter through “>” then “>” to access the menu. Figure 4-18. Front Panel Interface Menu Selection Sequence Serial Port 2 Front Panel Interface Configuration Sequence The rear Serial Port 2 may be configured via the Front Panel Interface following the keystroke sequence illustrated in Figure 4-17 and continuing the sequence illustrated in Figure 4-19. If Rear Port Selected “>” E Rear Bit Rate > Rear Data Lgth < Rear Stop Bits C Rear Port E FRONT Port > REAR Port < Modbus ID C Comm Ports E Enter System Group < 9600 C Rear Bit Rate IF E Selected to change Baud. E Rear Data Lngth > Rear Parity < Rear Bit Rate C Rear Port E Rear Stop Bits > Rear Bit Rate < Rear Parity C Rear Port E Rear Data Lngth > Rear Parity < Rear Bit Rate C Rear Port E Enter System Group <8 C Rear Data Lgth E Enter System Group <2 C Rear Stop Bits E Rear Parity > Rear Stop Bits < Rear Data Lgth C Rear Port If “>” Selected to set Data Length. If “<“ Selected to set Stop Bits. E Enter System Group < Even C Rear Parity To Select Parity Enter through “>” then “>” to access the menu. Figure 4-19. Serial Port 2 Configuration Selection Sequence Network Port 1 Configuration The DNP 3.0 port may NOT be configured via the Front Panel interface on the REL 512. The parameterization must occur using the Hyperterminal (or other dumb terminal interface program) program through the Front COM 0 port or the rear port labeled Serial Port 2. Page 42 of 145 REL 512 DNP 3.0 Automation Technical Guide Reference the data in Section X.XX and Figure 4-14. Selection [4] DNP 3.0 is available to access the four configuration screens enabling the operator to configure the DNP capabilities in the REL 512. Mode=VIEW Active Group=1 Mon Oct 25 1999 13:25:00 [1] [2] [3] [4] DNP DNP DNP DNP Configuration Configuration Configuration Configuration #1 #2 #3 #4 Selection => Figure 4-20. Comm Ports: DNP Menu The screen shown in Figure 4-20 provides direct access to all the user configurable DNP parameters. On the following screens (Figures 4-21 through 4-25) the “default” settings for each of these parameters is shown. The italicized text on each screen provides a reference to the section in this document where each parameter is described in detail. This text will not appear on you actual terminal. DNP Protocol Configuration #1 Device Address: Baud Rate: Frame Type: Inter-char Gap Time: Data Link Confirm Timeout: Data Link Retires: Transmit Delay: Class Zero Mask 1: Class Zero Mask 2: Class Zero Mask 3: Class Zero Mask 4: Class Zero Mask 5: 5 9600 N,8,1 0.05 3.0 2 0 0 0 0 0 0 Figure 4-21. DNP Configuration Screen #1 DNP Protocol Configuration #2 App Layer Fragment Size: 2048 Bytes App Layer Confirm Timeout: 5.0 Unsolicited Response Delay: 15 Unsolicited Rsp Dest Address: 3 Class 1 Event Response: 10 Class 2 Event Response: 25 Class 3 Event Response: 50 Data Link Confirm Mode: 0 Figure 4- 21. DNP Configuration Screen #2 Page 43 of 145 REL 512 DNP 3.0 Automation Technical Guide DNP Protocol Configuration #3 RS-485 Duplex: App Layer Confirm: Transceiver: RS-232 Handshaking: Local/Remote Input: Receive LED on with: Time Synch Source: Time Synch Interval: Control Point Paired: Rollover Flag: FULL DISABLE RS-232 None DISABLED ANY CHAR None 60 0 0 Figure 4-22. DNP Configuration Screen #3 DNP Protocol Configuration #4 load Current deadband: load voltage deadband: sequence Current deadband: sequence voltage deadband: watts deadband: vars deadband: power factor deadband: deadband mask: Binary input Default variation: Binary input Change Default variation: Binary Output Default variation: Control Relay Output Block Default variation: 32 Bit Analog Default variation: 32 Bit Analog Change Default variation: 5 5 5 5 5 5 5 127 VAR2 VAR2 VAR2 VAR1 VAR3 VAR3 Figure 4-23. DNP Configuration Screen #4 Communications Settings Device Address This parameter specified the “network” address of the REL 512 with respect to all other devices communicating on the same physical network as the REL 512. The value may range between 0 and 65534 decimal (FFFE hex). The default address is 5. Note: The DNP protocol permits 65535 (FFFF hex) as a valid address; but it is also reserved as a global address and may not be entered on this screen. Baud Rate The serial baud rate for the DNP communications. It may be set to 300, 1200, 2400, 4800, 9600, 19200 and 38400. Pressing the space bar will cycle through the above baud rates. The default baud rate is 9600. Page 44 of 145 REL 512 DNP 3.0 Automation Technical Guide Frame Type Describes the number of data bits, parity and the number of stop bits. Supported values are “N-8-1”, “E-8-1”, “O8-1”, “N-8-2”, “E-7-1”, “O-7-1” and “N-7-2”. Pressing the space bar will cycle through the above framing choices. N-8-1 is the default frame type. Inter-char Gap Time The Inter-character timeout gap specifies the maximum time between characters received within a data frame. It is specified in seconds (with steps of 0.01 seconds). It map be set between 0 and 2.55 seconds, with a default of 0.05 seconds. If set to zero, the functionality provided by this parameter is disabled. Otherwise, if the time value represented by this parameter is exceeded after receiving one character and before receiving another, the current message frame will be deemed corrupted, and discarded. When another character is finally received, it will be considered to be the beginning of the next frame and tested as such. Setting this parameter smaller than the maximum expected inter-character delays generated by the master computer, may result in valid frames being erroneously discarded. However, if corruption occurs on an incoming message, setting this value too large may result a good frame being concatenated with the corrupt frame. The error will eventually be detected (using, at the lowest level, CRCs), but now two frames will need to be retransmitted. Transceiver This parameter should reflect the RS-232 or RS-485 jumper selections on the DNP Module. It has these possible values: RS-232 RS-485 Specifies that hardware jumpers JP1 through JP4 are in position 1,2 to enable RS-232 communications (default). Specifies that hardware jumpers JP1 through JP4 are in position 2,3 to enable RS-232 communications. Note: the RS-232 handshake parameter must also be set to None. RS-232 Handshaking This parameter is used to enable RTS/CTS handshaking when configured for RS-232 communications. It can be set to the following values by pressing the space bar: None RTS/CTS Specifies no handshaking. It must be set to this value if using RS-485 communications. Enables RTS/CTS handshaking on the RS232 port (default). RS-485 Duplex This parameter is not presently used. It may be set to the following values by pressing the space bar: Full Half Sets RS-485 port to operate in full duplex mode (default). Sets RS-485 port to operate in half duplex mode. Receive LED Light On The parameter controls the operation of the Receive LED located adjacent to Network Port 1 on the rear of the REL 512. It is provided for network trouble-shooting. It may be toggled between the following states by pressing the space bar: ANY CHAR ADDRESSED Receive LED flashes when a character is received. A DNP message addressed to this unit will turn the Receive LED on. Any message addressed to another DNP device will turn the Receive LED off. Page 45 of 145 REL 512 DNP 3.0 Automation Technical Guide Transmit Delay The Transmission Delay specifies the minimum time after a data frame is received before a data frame is transmitted. It is specified in milliseconds, and may range from 0 to 255, inclusive. The default value is 0. This parameter is intended for physical network environments using a multi-drop configuration such as RS-485. In these environments, many active receivers are allowed, but only one transmitter can be active, or else a “collision” will occur and data transmission will be corrupted. This parameter allows master computers, or other computers on the same physical network, time to turn off their transmitter after transmitting a message. A similar configuration parameter should exist on the other computers to allow the REL 512 time to turn off its transmitter after it has finished transmitting. In environments where this functionality is not needed, this parameter may left at the default, zero. Note that there is always a delay between receipt of a DNP message and the response due to the amount of time it takes to build the response. This parameter will cause that delay to be extended to meet the entered value. Protocol Settings Data Link Confirm Mode This parameter specifies what type of Data Link confirmation should be used. It may be set to 0, 1 or 2, where these values have the following meaning: 0 1 2 Specifies that data link confirmations never be used (default). Specifies that data link confirmations only be used for multi-frame fragments. Specifies that data link confirmations always be used. If data link confirmations are used, then the REL 512 will request a confirmation from the master computer when transmitting data link frames. If a confirmation is not received within the timeout specified by Data Link Confirm Timeout, then an error is indicated. If Data Link Retries is enabled, and if the maximum number of retries have not been attempted, then the REL 512 will attempt to retransmit the data frame. A value 1 for this parameter is included for cases when the functionality of confirmations is desired for each frame, but application layer confirmations can only cover an entire fragment. Data Link Confirm Timeout The Data Link Confirmation Timeout value specifies the data link layer confirmation time-out. It is specified in seconds (with steps of 0.10 of a second), and may range from 0.1 to 25.5 seconds. It has a default value of 0.05, or 50 milliseconds. It is valid only when the REL 512 is acting as a data link primary; i.e., when the REL 512 is transmitting a data frame with a request for a data link layer confirmation from the master computer, or the REL 512 is transmitting a reset link frame. Specifically, if a confirmation is not received or if the link is not reset within the time specified by this parameter, then a data link error is indicated. If data link layer retries are enabled (see Data Link Retries below), and if the maximum number of retries have not been attempted, then another data link layer retry will be attempted; i.e., the frame will be retransmitted. Data Link Retries This value specifies the maximum number of data link layer retries attempted. It can be set from 0 to 255 inclusive. The default for this value is 2. The Data Link Retry count comes into play when, the REL 512 is transmitting a data frame with a request for a data link layer confirmation from the master computer, or when the REL 512 is transmitting a reset link frame. In these two cases, if the time-out specified by Data Link Confirm Timeout (described above) has elapsed without receiving a confirmation or without detecting the link reset, the data frame will be re-transmitted the number of times specified by this parameter. The default value of zero indicates that no retries will be attempted. Page 46 of 145 REL 512 DNP 3.0 Automation Technical Guide Application Layer Confirm This parameter determines how the REL 512 requests application layer confirmations when transmitting messages to the master computer. It has two possible values: Disabled Enabled Specifies that an application confirmation will only be requested when a transmitted fragment contains event data (default). It is only when the master computer confirms the reception of event data that the REL 512 will clear the event data from its event queues. Specifies that an application confirmation will be requested when a transmitted fragment contains event data, or when the fragment is a non-final part of a multi-fragment response – regardless of whether the fragment contains event data or not. This allows the master computer to use the functionality of application layer confirms as flow control. It is intended to be used when data link layer confirmations are not used and when the master computer requires flow control in order to provide time to process the data within REL 512 transmitted fragments. Application Layer Confirm Timeout This parameter specifies the application layer confirmation time-out. It is specified in seconds (with a step of tenths (0.10) of a second), and may range from 0.1 to 25.5 with a default of 5 seconds. Application Layer Fragment Size The Application Layer Fragment Size specifies the maximum size of an application layer response. It is specified in number of data link frames and may range from 1 to 8. (Since, for the REL 512, the maximum size of a data-link frame is 256 bytes, this signifies a range of maximum application fragment size of 256 to 2048 bytes). In a technical bulletin published by the DNP Users Group Technical Committee, it was recommended that the application fragment size be reduced to the largest amount that will fit in a single data link layer frame (the value of this parameter would be 1). As part of the same recommendation, it was recommended that data link confirmations not be used, and that application layer confirmations be used instead. The reasoning behind this recommendation is that application layer confirmations are more robust and informative, and that data link layer confirmations are redundant and useless if all application layer fragments use only a single data link frame. However, if a response message cannot fit in a single application layer fragment, the DNP implementation in the REL 512 will respond with a multi-fragment response, and not all master computer DNP implementations correctly parse multi-fragment responses. Therefore, if the master computer cannot handle multi-fragment responses, this parameter must be set large enough to hold the largest response message. For the REL 512, an example of a large response message would be the response to a Class 0 scan. Unsolicited Response Delay This setting is reserved for future use. Unsolicited response reporting is not presently available on the REL 512. Unsolicited Response Destination Address This setting is reserved for future use. Unsolicited response reporting is not presently available on the REL 512. Class 1 Event Response This setting is reserved for future use. Unsolicited response reporting is not presently available on the REL 512. Class 2 Event Response This setting is reserved for future use. Unsolicited response reporting is not presently available on the REL 512. Page 47 of 145 REL 512 DNP 3.0 Automation Technical Guide Class 3 Event Response This setting is reserved for future use. Unsolicited response reporting is not presently available on the REL 512. Application Settings Local/Remote Input This parameter determines whether or not the Local/Remote Lockout feature is enabled and defines which input should be used for Local/Remote Lockout control. Pressing the space bar will cycle through the following selections: Disabled Input n The Local/Remote Lockout feature is not operational (default). This option means DNP control requests are always accepted. Incates which physical input should be used to determine the state of the Local/Remote Lockout feature. When “n” can be any of the physcial inputs (1 through 12). When an Input n is selected, the state of that input is used to determine whether or not DNP control requests should be processed. A state of 1 indicates that control operations should be blocked. Time Synchronization Source This parameter indicates the source of the external time synchronization signal. None IRIG-B DNP The internal clock is not being synchronized (default). An external time synch is bring provided by an IRIG-B signal that is directly connected to the Host Module. The external time synch is provided by a periodic Write Time command sent by the SCADA DNP Master. Time Synchronization Interval This parameter determines when the Need Time internal indicator (IIN) bit should be set to request a time synch from the DNP Master. It specifies the periodicity with which the REL 512 will request another time synch from the SCADA DNP Master following receipt of a Write Time request. It may be set from 0 to 300 minutes (5 hours). The default is zero, meaning the REL 512 will never request time synchronization. This parameter does not prevent a time synch from occurring, as long DNP is the Time Synchronization Source. The relay will always accept a Write Time request; but will not solicit one from the Master unless this value is greater than 0. Class 0 Mask 1-5 The Class 0 Masks provide a means for reducing the number of points returned in a Class scan. These masks are primarily intended to reduce the count of “static” points returned by a Class 0 scan. However, points that are masked out from Class 0 reporting do not generate events for Class 1, 2 or 3 scans. Each Binary Input, Binary Output, Counter and Analog Input is defined as being in one of the Scan Groups listed below. These Scan Group assignments are defined in the Point List portion of the Device Profile Document. The “masking” feature allows all points in a given Scan Group to be filtered out when performing Class scans. These points are always available when scanning for individual objects, such as all Binary Outputs. By default the five mask words are all set to zero, enabling reporting for all points in the relay. To disable one or more scan groups the indicated bits must be set in the mask words. The following procedure describe how to determine the scan mask for a given Scan Group using Table 4-2 below: Page 48 of 145 REL 512 DNP 3.0 Automation Technical Guide For masking out a single Scan Group: Step a. First locate the Scan Group # in the left half of the table. Step b. At the head of the column determine which of the Class 0 Mask Words needs to be modified. Step c. Verify that the designated Class 0 Mask Word is already 0. If not skip to procedure for masking multiple Scan Groups. Step d. Reading across to the Mask Value – Decimal tells you the value that need to be entered in the Mask Word. For determining which Scan Groups are being masked: Step a. The following steps need to be repeated for each of the five Mask Words. Step b. Note the present “mask value” of the Mask Word. If it is zero (0), skip to the last step; none of the Scan Groups for this word are masked. Step c. Starting at the bottom of the “decimal” column in Table 4-2 locate the first entry less than or equal to the present value. Step d. Look up the Scan Group number by cross-referencing the Mask Word # with the result of step c. Step e. Obtain a new “mask value” by subtracting the step c result from the current “mask value”. Step f. Repeat steps b through e. For masking out multiple Scan Groups: This procedure covers the cases where the current Mask Word is non-zero and when masking multiple Scan Groups. Step a. First follow the previous procedure for all non-zero Mask Words to determine which Scan Groups are already being masked. Step b. Note these Scan Groups in Table 4-2. Step c. Note any new Scan Groups that are to be masked in Table 4-2. Step d. Now all the Scan Groups that need to be masked are marked in the appropriate column in Table 4-2. Step e. For each column total the “decimal” values for all the marked Scan Groups. The resulting sum is the new Mask Word. Page 49 of 145 REL 512 DNP 3.0 Automation Technical Guide Table 4-2. DNP Scan Group Masks Class 0 Mask Word for Scan Group # Word #1 Word #2 Word #3 Word #4 Word #5 Mask Value Hexidecimal 0001 0002 0004 0008 0010 0020 0040 0080 0100 0200 0400 0800 1000 2000 4000 8000 Decimal 1 2 4 8 16 32 64 128 256 512 1024 2048 4096 8192 16384 32768 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Example: 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 Control Point Paired Most of the Binary Control points in the REL 512 relay can be operated either singularly (default) or in pairs. Normally, control operations operation only on the requested point. However, some SCADA implementations use a single point to control two outputs. A Trip command will act on the first output, and a Close command will act on the second output. In order to provide this capability in the REL 512, the user may combine two outputs into a pair. A Trip command operates on the first point of the pair and a Close command operates on the second. Normally, no other outputs are sent to either of these points. The Control Point Paired setting allows up to eleven separate pairings. A full description of the paired points appears in the DNP Point List in the Device Profile Document. The following table describes how determine the value for this setting: Page 50 of 145 REL 512 DNP 3.0 Automation Technical Guide Table 4-3. Paired Control Point Values Binary Control Points 0&1 2&3 4&5 6&7 8&9 10 & 11 12 & 13 14 & 15 16 & 17 18 & 19 20 & 21 Pair All Points Bit Assignment 0 1 2 3 4 5 6 7 8 9 10 0 through 10 Paired Value 1 2 4 8 16 32 64 128 256 512 1024 2047 The above table describes the setting for a single pair of Binary Control points or all possible pairs of Binary Control points. For any other combination the appropriate values in the last column should be summed. Rollover Flag This flag indicates whether or not the “rollover bit” will be set in the flag byte for Binary Counters when a rollover occurs. This in not presently used because the present implementation does not support any variations of Binary Counter that require the flag byte. The following values may be entered in this field: 0 1 Do not set the “rollover bit” when the counter wraps around. The default value for this flag is zero, as per the DNP User Group Technical Note. Set the “rollover bit”. Deadband Values These settings are reserved for future use. The following description is subject to change. The value in each of these fields represents the deadband for this type of data. It is entered as a decimal value between 0 and 1000. This value is treated as either an absolute count or percent deadband, depending on the setting of the Deadband Mask. If specified as a count this indicates how many counts the designated value must change by before an analog change event is generated. If specified as a percent deadband it indicates the percentage change in the current value before an analog change event is generated. Deadband Mask This setting is reserved for future use. The following description is subject to change. The value in this field contains a bit mask for the above Deadband Values. It is entered as a decimal value between 0 and 127. It consists of a single bit for each of the deadband values. The bit settings indicate whether this deadband value should be treated as an absolute count for a percent deadband. Default Variations These settings are reserved for future use. The following description is subject to change. Page 51 of 145 REL 512 DNP 3.0 Automation Technical Guide Table 4-4. Configurable Default Variations Description Binary Input Binary Change Binary Output Control Relay Output Block Counter* Frozen Counter* Analog Input Analog Change Object 1 2 10 12 20 21 30 32 Default Var. Var2 Var2 Var2 Var1 Var6 Var10 Var3 Var3 Other Variations Var1 Var1 Var3 Var1 Var2 Var3 Var1 Var1 Var2 Var2 Var4 Var4 * these objects are not configurable; italicized variations are not yet supported These settings allow the user to reconfigure the default variation that is used for each type of DNP object. The values shown in Figure 5 and the table above are the defaults. Changes made here take affect after they are saved and the DNP Module is restarted. They determine the response to all requests for Class data and requests for individual objects when variation 0 is transmitted in the request. Changes to these settings are made by repeatedly pressing the space bar to cycle through the possible variations for each object type. Note that some objects do not support changing the default variation, and some (italicized) variations listed above are not presently supported by the REL 512. Page 52 of 145 REL 512 DNP 3.0 Automation Technical Guide Section 5 – DNP V3.0 Device Profile DNP V3.0 Device Profile The following table provides a Device Profile Information in the standard format defined in the DNP 3.0 Subset Definitions Document. Table 5-1, in combination with the Implementation Table provided as Table 5-2 and the Point List Tables provided in Section 5, should provide complete application implementation details for including the REL 512 in any DNP environment. Table 5-1. REL 512 Device Profile DNP V3.0 DEVICE PROFILE DOCUMENT (Also see the DNP 3.0 Implementation Table, beginning on page 55.) Vendor Name: ABB Inc. Substation Automation and Protection Device Name: REL 512 Highest DNP Level Supported: Device Function: For Requests: Level 2 Master For Responses: Level 2 Slave Notable objects, functions, and/or qualifiers supported in addition to the Highest DNP Levels Supported (the complete list is described in the attached table): For static data requests, in addition to qualifier code 06 (no range), qualifier codes 00 and 01 (start-stop), 07 and 08 (limited quantity). 16-bit and 32-bit Analog Change Events with Time may be requested. The read function code for Object 50 (Time and Date), variation 1, is supported. Maximum Data Link Frame Size (octets): Transmitted: Received 292 292 Maximum Application Fragment Size (octets): Transmitted: 2048 (default) Configurable - see REL 512 – DNP Configuration Guide Received 2048 Maximum Application Layer Re-tries: None Configurable Maximum Data Link Re-tries: None Fixed Configurable from 0 to 255 (default = 2). See REL 512 – DNP Configuration Guide Requires Data Link Layer Confirmation: Never Always Sometimes Configurable as: Never(default), Only for multi-frame messages, or Always. See REL 512 – DNP Configuration Guide Page 53 of 145 REL 512 DNP 3.0 Automation Technical Guide DNP V3.0 DEVICE PROFILE DOCUMENT (Also see the DNP 3.0 Implementation Table, beginning on page 55.) Requires Application Layer Confirmation: Never Always When reporting Event Data (Slave devices only) When sending multi-fragment responses (Slave devices only) Sometimes Configurable as: Only when reporting event data (default), or When reporting event data and/or multi-fragment messages. See REL 512 – DNP Configuration Guide Timeouts while waiting for: Data Link Confirm: None Fixed at ____ See REL 512 – DNP Configuration Guide Complete Appl. Fragment: None Fixed at ____ Variable Configurable. Variable Variable Configurable Configurable. Application Confirm: None Fixed at ____ See REL 512 – DNP Configuration Guide Complete Appl. Response: None Fixed at ____ Variable Configurable Others: Inter-character Delay, configurable. See REL 512 – DNP Configuration Guide Sends/Executes Control Operations: WRITE Binary Outputs Never SELECT/OPERATE Never DIRECT OPERATE Never DIRECT OPERATE - NO ACK Never Count > 1 Never Pulse On Never Pulse Off Never Latch On Never Latch Off Never Queue Never Clear Queue Never Always Sometimes Configurable For above items marked sometimes see the DNP V3.0 Point List Always Sometimes Configurable Always Sometimes Configurable Always Sometimes Configurable Always Sometimes Configurable Always Sometimes Configurable Always Sometimes Configurable Always Always Always Always Sometimes Sometimes Sometimes Sometimes Configurable Configurable Configurable Configurable Page 54 of 145 REL 512 DNP 3.0 Automation Technical Guide DNP V3.0 DEVICE PROFILE DOCUMENT (Also see the DNP 3.0 Implementation Table, beginning on page 55.) Reports Binary Input Change Events when no specific variation requested: Never Only time-tagged Only non-time-tagged Configurable to send either (default time tagged). See REL 512 – DNP Configuration Guide Sends Unsolicited Responses: Never Configurable Only certain objects Sometimes (attach explanation) ENABLE/DISABLE UNSOLICITED Function codes are not supported Default Counter Object/Variation: No Counters Reported Configurable (attach explanation) Default Object 20 Default Variation: 6 Point-by-point list attached May also be configured to report object 21 – see Section 5 Binary Counters Sends Multi-Fragment Responses: Yes No Reports time-tagged Binary Input Change Events when no specific variation requested: Never Binary Input Change With Time Binary Input Change With Relative Time Configurable (attach explanation) Sends Static Data in Unsolicited Responses: Never When Device Restarts When Status Flags Change No other options are permitted. Counters Roll Over at: No Counters Reported Configurable (attach explanation) 16 Bits 32 Bits Other Value: none Point-by-point list attached DNP V3.0 Implementation Table The following table identifies which object variations, function codes, and qualifiers the REL 512 supports in both request messages and in response messages. Note that while the REL 512 may parse many object variations, it will respond to the request variations identified below with entries in the response column. The shaded areas represent functionality beyond that required by a DNP Level 2 device. DNP 3.0 in the REL 512 is a robust implementation allowing the following capabilities: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. Acquisition of Metering Data Contact Test Functionality Forcing Capabilities Function Status Reporting Counter Acquisition Fault Record Reporting Alarm Reportin Class Data Reporting Function Enabled Status Reporting Time Synchronization Through DNP 3.0 and IRIG B The REL 512 does not support Unsolicited Response (or Report By Exception as referred to by some). This new DNP 3.0 Profile document lists the supported commands in a format more conducive to that specified in the DNP 3.0 Subset Definitions Document. It is recommended that the reader consult the text titled: GE HARRIS DISTRIBUTED NETWORK PROTOCOL – DNP 3.0 BASIC 4 DOCUMENT SET – Part Number 994-0007 dated July 30, 1995 REV. 3 Page 55 of 145 REL 512 DNP 3.0 Automation Technical Guide The device protocol tables follow: Table 5-1 provides a Device Profile Information in the standard format defined in the DNP 3.0 Subset Definitions Document. The table, in combination with the Implementation Table (Table 5-2) provided and the Point Lists provided in this user document should provide complete application implementation details for the REL 512 DNP environment. Table 5-2. Device Profile Documentation OBJECT Object Number 1 1 1 2 2 2 2 10 10 12 Variation Number 0 1 (default) Description Binary Input – Any Variation Binary Input Binary Input with Status Binary Input Change – Any Variation Binary Input Change without Time Binary Input Change with Time Binary Input Change with Relative Time Binary Output – Any Variation Binary Output Status Control Relay Output Block REQUEST (REL 512 will parse) Function Qualifier Codes (dec) Codes (hex) 1 1 1 1 1 1 1 1 1 (read) RESPONSE (REL 512 responds with) Function Qualifier Codes (dec) Codes (hex) (read) 2 0 1 2 (default) (read) (read) (read) (read) 3 (parse only) (read) 0 2 (default) (read) (read) 1 20 0 Binary Counter – Any Variation 20 6 (default) 16-Bit Binary Counter without Flag 21 21 22 30 0 10 (default) Frozen Counter – Any Variation 16-Bit Frozen Counter without Flag Counter Change Event – Any Variation Analog Input – Any Variation 3 (select) 4 (operate) 5 (direct op) 6 (dir. op, noack) 1 (read) 7 (freeze) 8 (freeze noack) 9 (freeze clear) 10 (frz. cl. noack) 1 (read) 7 (freeze) 8 (freeze noack) 9 (freeze clear) 10 (frz. cl. noack) 1 (read) 1 1 1 00, 01 (start-stop) 06 (no range) 07, 08 (limited qty) 00, 01 (start-stop) 06 (no range) 07, 08 (limited qty) 00, 01 (start-stop) 06 (no range) 07, 08 (limited qty) 06 (no range) 07, 08 (limited qty) 06 (no range) 07, 08 (limited qty) 06 (no range) 07, 08 (limited qty) 06 (no range) 07, 08 (limited qty) 00, 01 (start-stop) 06 (no range) 07, 08 (limited qty) 00, 01 (start-stop) 06 (no range) 07, 08 (limited qty) 00, 01 (start-stop) 07, 08 (limited qty) 17, 28 (index) 00, 01 (start-stop) 06 (no range) 07, 08 (limited qty) 00, 01 (start-stop) 06 (no range) 07, 08 (limited qty) 129 129 (response) 00, 01 (start-stop) 00, 01 (start-stop) (response) 129 129 (response) 17, 28 17, 28 (index) (response) (index) 129 129 (response) 00, 01 (start-stop) echo of request (response) 129 (response) 00, 01 (start-stop) (read) 0 (parse only) (read) 0 (read) 00, 01 (start-stop) 06 (no range) 07, 08 (limited qty) 00, 01 (start-stop) 129 06 (no range) 07, 08 (limited qty) 06 (no range) 07, 08 (limited qty) 00, 01 (start-stop) 06 (no range) 07, 08 (limited qty) (response) 00, 01 (start-stop) Page 56 of 145 REL 512 DNP 3.0 Automation Technical Guide OBJECT Object Number 30 30 30 30 32 32 32 32 32 40 40 41 Variation Number 1 2 (default) Description 32-Bit Analog Input 16-Bit Analog Input 32-Bit Analog Input without Flag 16-Bit Analog Input without Flag Analog Change Event – Any Variation 32-Bit Analog Change Event without Time 16-Bit Analog Change Event without Time 32-Bit Analog Change Event with Time 16-Bit Analog Change Event with Time Analog Output Status – Any Variation 16-Bit Analog Output Status 16-Bit Analog Output Block REQUEST (REL 512 will parse) Function Qualifier Codes (dec) Codes (hex) 1 1 1 1 1 1 1 1 1 1 1 (read) RESPONSE (REL 512 responds with) Function Qualifier Codes (dec) Codes (hex) 129 129 129 129 (response) (read) 3 4 0 1 2 3 4 (default) (read) (read) (read) (read) (read) (read) (read) 0 2 (default) (read) (read) 2 50 0 Time and Date 3 (select) 4 (operate) 5 (direct op) 6 (dir. op, noack) 1 (read) 00, 01 (start-stop) 06 (no range) 07, 08 (limited qty) 00, 01 (start-stop) 06 (no range) 07, 08 (limited qty) 00, 01 (start-stop) 06 (no range) 07, 08 (limited qty) 00, 01 (start-stop) 06 (no range) 07, 08 (limited qty) 06 (no range) 07, 08 (limited qty) 06 (no range) 07, 08 (limited qty) 06 (no range) 07, 08 (limited qty) 06 (no range) 07, 08 (limited qty) 06 (no range) 07, 08 (limited qty) 00, 01 (start-stop) 06 (no range) 07, 08 (limited qty) 00, 01 (start-stop) 06 (no range) 07, 08 (limited qty) 00, 01 (start-stop) 07, 08 (limited qty) 17, 28 (index) 00, 01 (start-stop) 00, 01 (start-stop) 00, 01 (start-stop) 00, 01 (start-stop) (response) (response) (response) 129 129 129 129 (response) 17, 28 17, 28 17, 28 17, 28 (index) (response) (index) (response) (index) (response) (index 129 129 (response) 00, 01 (start-stop) echo of request (response) 2 (write) 50 1 (default) Time and Date 1 (read) 2 (write) 52 60 60 60 60 2 0 1 2 3 Time Delay Fine Class 0, 1, 2, and 3 Data Class 0 Data Class 1 Data Class 2 Data 1 1 1 1 (read) 00, 01 (start-stop=0) 06 (no range) 07, 08 (limited qty) 17, 28 (index=0) 00, 01 (start-stop=0) 07, (where quantity=1) 08 (where quantity=1) 17, 28 (index=0) 00, 01 (start-stop=0) 129 06 (no range) 07, 08 (limited qty) 17, 28 (index=0) 00, 01 (start-stop=0) 129 07, (where quantity=1) 08 (where quantity=1) 17, 28 (index=0) 129 06 06 (no range) (response) 00, 01 (start-stop) 17, 28 (index) (response) (response) 7 (quantly = 1) (read) (no range) (read) (read) 06 (no range) 07, 08 (limited qty) 06 (no range) 07, 08 (limited qty) Page 57 of 145 REL 512 DNP 3.0 Automation Technical Guide OBJECT Object Number 60 80 Variation Number 4 1 Description Class 3 Data Internal Indications No Object (function code only) No Object (function code only) REQUEST (REL 512 will parse) Function Qualifier Codes (dec) Codes (hex) 1 2 (read) RESPONSE (REL 512 responds with) Function Qualifier Codes (dec) Codes (hex) (write) 06 (no range) 07, 08 (limited qty) 00 (start-stop) (index must =7) 13 (cold restart) 23 (delay measurement) (Default variations are responded when variation 0 is requested and/or in class 0, 1, 2, or 3 scans.) Cold and Warm Restart Capabilities The DNP 3.0 implementation to the WARM and COLD restart (Application Control Function Codes 13 and 14) will generate a time delay object (object 52 variant 1). The response also requests an application level confirm. When this confirm is received from the host, then the REL 512 will halt all communication activity. This in turn will cause the watch dog time to time out and reset the REL 512 internal communication buffers. Five seconds after the watch dog timer is reset, the REL 512 will again respond to DNP requests from the host. Internal Indication (IIN) Field Data Returns DNP 3.0, is a protocol which includes status bytes within a data transfer frame. The decode of the defined bits within the protocol are defined in Figure X-X. The REL 512 supports all the bits as defined in the protocol. However the definition of when the defined bits are given as a reference to the operator. The IIN field is useful to determine if Class Data is available, or if commands have been accepted or if diagnostics and the device are operational. First byte, Bit 4 - Time-synchronization required, set at power up, cleared by host. First byte, Bit 5 - Outputs offline - always zero. Second byte, Bit 5 - Configuration corrupt - always zero. First byte, Bit 6 - Device Trouble - set if any of the following binary inputs are true. Table 5-3. Trouble Bit 6 Instance Occurrence Definitions Description Self Test Status DSP ROM Failure DSP Internal RAM Failure DSP External RAM Failure DSP +/-5V Failure DSP +/-15V Failure DSP +5V Failure DSP Comm. Failure ADC Failure CPU RAM Failure CPU EPROM Failure CPU NVRAM Failure CPU EEPROM Failure Page 58 of 145 REL 512 DNP 3.0 Automation Technical Guide IIN CODE FORMAT Bit 0 = All Stations Message Bit 1 = Class 1 Data Bit 2 = Class 2 Data Bit 3 = Class 3 Data Bit 4 = Time Synch Required from Master Bit 5 = Digital Output Point(s) in LOCAL Bit 6 = Device Trouble Bit 7 = Device Restart OCTET 1 Bit Bit 7 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Bit 0 = RESERVED Bit 1 = Requested Object(s) Unknown Bit 2 = Qualifier, Range, or Data Invalid Bit 3 = Event Buffers Overflowed Bit 4 = Request Understood/Command Processing Bit 5 = Current Configuration Corrupt Bit 6 = RESERVED (Always 0) Bit Bit Bit 7 = RESERVED (Always 0) 7 OCTET 2 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Figure 5-1. DNP 3.0 Device IIN Bit Definition Assignment DNP V3.0 Point List Binary Input Points Binary Input Points (67 Indices Defined) Binary Input Points are reported a variety of ways using Object 1 (Single Bit Binary Data with or without status reporting) or Object 2 (Single Bit Binary Input Change with or without status/time reporting). If the point as defined in Table 5-4. Table 5-4. Binary Input Index Binary Input Points Static (Steady-State) Object Number: 1 Change Event Object Number: 2 Request Function Codes supported: 1 (read) Static Variation reported when variation 0 requested: 1 (Binary Input without status) Change Variation reported when variation 0 requested: 2 (Binary Input without status) Note: For Static points the response for variation 0 is configurable 1 Default Change Event Assigned Class Point Name/Description (1, 2, 3 or none) I.D. 0 Input 1 Energized (programmable) 1 1 Input 2 Energized (programmable) 1 2 3 4 5 6 7 8 9 10 11 Input 3 Energized (programmable) Input 4 Energized (programmable) Input 5 Energized (programmable) Input 6 Energized (programmable) Input 7 Energized (programmable) Input 8 Energized (programmable) Input 9 Energized (programmable) Input 10 Energized (programmable) Input 11 Energized (programmable) Input 12 Energized (programmable) 1 1 1 1 1 1 1 1 1 1 Scan Group 0 0 0 0 0 0 0 0 0 0 0 0 Page 59 of 145 REL 512 DNP 3.0 Automation Technical Guide Binary Input Points Static (Steady-State) Object Number: 1 Change Event Object Number: 2 Request Function Codes supported: 1 (read) Static Variation reported when variation 0 requested: 1 (Binary Input without status) Change Variation reported when variation 0 requested: 2 (Binary Input without status) Note: For Static points the response for variation 0 is configurable 1 Default Change Event Assigned Class Point Name/Description (1, 2, 3 or none) I.D. 12 Output 1 Relay Energized (In Service/Alarm) 1 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 Output 2 Relay Energized (programmable) Output 3 Relay Energized (programmable) Output 4 Relay Energized (programmable) Output 5 Relay Energized (programmable) Output 6 Relay Energized (programmable) Output 7 Relay Energized (programmable) Output 8 Relay Energized (programmable) Output 9 Relay Energized (programmable) Output 10 Relay Energized (Breaker Failure Initiate) Output 11 Relay Energized (Time Delay Reclose Initiate) Output 12 Relay Energized (High Speed Reclose Initiate) Output 13 Relay Energized (Fault Inception) Output 14 Relay Energized (Pilot Channel Stop) Output 15 Relay Energized (Pilot Channel Start) Output 16 Relay Energized (Trip 3 pole or SPT Phase A) Output 17 Relay Energized (Trip 3 pole or SPT Phase B) Output 18 Relay Energized (Trip 3 pole or SPT Phase C) LED 1 (Trip) LED 2 (Self Test) LED 3 (Fault) LED 4 (Trip Circuit – 2) LED 5 (50/51) LED 6 (52B – 2) LED 7 (G/Q) LED 8 (52B – 1) LED 9 (C Phase) LED 10 (Trip Circuit – 1) LED 11 (B Phase) LED 12 (Recloser Hot Line Dead Bus) LED 13 (A Phase) LED 14 (Recloser Hot Bus Dead Line) LED 15 (Zone 3) LED 16 (Recloser Sync Check) LED 17 (Zone 2) LED 18 (Recloser Lockout) LED 19 (Zone 1) LED 20 (Recloser In Service) LED 21 (Pilot) LED 22 (LOP/LOI) 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 none 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Scan Group 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 Page 60 of 145 REL 512 DNP 3.0 Automation Technical Guide Binary Input Points Static (Steady-State) Object Number: 1 Change Event Object Number: 2 Request Function Codes supported: 1 (read) Static Variation reported when variation 0 requested: 1 (Binary Input without status) Change Variation reported when variation 0 requested: 2 (Binary Input without status) Note: For Static points the response for variation 0 is configurable 1 Default Change Event Assigned Class Point Name/Description (1, 2, 3 or none) I.D. 52 LED 23 (Protection in Service) 1 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 LED 24 (Pilot In Service) OUTPUT – In service OUTPUT – Time Delay Reclose Initiate OUTPUT – High Speed Reclose Initiate OUTPUT – Fault inception OUTPUT – Pilot Channel Stop OUTPUT – Pilot Channel Start OUTPUT – Trip A OUTPUT – Trip B OUTPUT – Trip C 52A – 1 (Logical) 52B – 1 (Logical) 52A – 2 (Logical) 52B – 2 (Logical) Pilot Status (Logical) 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Scan Group 2 2 3 3 3 3 3 3 3 3 3 4 4 4 4 5 Note: 1 at present the default assignments are not configurable. The capability of changing assignments with the Assign Class function may be provided in the future. Binary Counters (2 Elements Defined) Counter Access (6 Elements Defined) The REL 512 allows for access of several counter values including those associated with: 1. Breaker Operations 2. Reclose Operations Counters may be read, written, or frozen. The frozen counter objects require an explicit freeze request from the host. Each freeze request will capture one sample of the related static counter up to a maximum of 32 samples. A DNP read request for a frozen counter will return all frozen samples for each point specified in the read request in ascending time order. Once read, further read requests for a point will not return frozen data for the previously read counter until another freeze request occurs. Table 5-5 lists the index list of the counters defined for the REL 512. Page 61 of 145 REL 512 DNP 3.0 Automation Technical Guide Table 5-5. ??? Binary Counters Static (Steady-State) Object Number: 20 Request Function Codes supported: 1 (read), 7 (freeze), 8 (freeze noack), 9 (freeze and clear), 10 (freeze and clear, noack) Static Variation reported when variation 0 requested: 6 (16-Bit Binary Counter without Flag) Change Event Variation reported when variation 0 requested: none – not supported Frozen Counters Static (Steady-State) Object Number: 21 Request Function Codes supported: 1 (read) Static Variation reported when variation 0 requested: 10 (16-Bit Frozen Binary without Flag) Change Event Variation reported when variation 0 requested: none – not supported Default Change Event Assigned Class (1, 2, 3 or none) none none 1 Point I.D. 0 1 Name/Description Breaker Operations Counter Reclose Counter Scan Groups2 6 and 7 6 and 7 Note: 1 2 at present the default assignments are not configurable. The capability of changing assignments with the Assign Class function may be provided in the future. Object 20 – Binary Counters –use Scan Group 6 Object 21 – Frozen Counters –use Scan Group Analog Inputs (195 Elements) The REL 512 has 195 data elements assigned to Analog Input objects. The types of data retrievable via the analog input data objects are: 1. Metering Data 2. Fault Data (the present and up to 15 prior faults) Analog Input Points Static (Steady-State) Object Number: 30 Change Event Object Number: 32 Request Function Codes supported: 1 (read) Static Variation reported when variation 0 requested: 2 (16-Bit Analog Input) Change Event Variation reported when variation 0 requested: 2 (16-Bit Analog Change Event w/o Time) The Data Size for all points is 32 bits Default1 Range / Units Point Name/Description Change Event Scan Group (0 to 16777215 for I.D. Assigned Class 32 bit data - FS), Scaling (*10) (1, 2, 3 or none) 0 Ia 0 - FS Amps 3 8 1 Ib 0 - FS Amps 3 8 2 Ic 0 - FS Amps 3 8 3 Ip 0 - FS Amps 3 8 4 Van 0 - FS Volts 3 9 5 Vbn 0 - FS Volts 3 9 6 Vcn 0 - FS Volts 3 9 7 Vs 0 - FS Volts 3 9 8 Phase A Watts 0 - FS Watts 3 10 9 Phase B Watts 0 - FS Watts 3 10 10 Phase C Watts 0 - FS Watts 3 10 11 Phase A Vars 0 - FS Vars 3 11 12 Phase B Vars 0 - FS Vars 3 11 13 Phase C Vars 0 - FS Vars 3 11 Page 62 of 145 REL 512 DNP 3.0 Automation Technical Guide Analog Input Points Static (Steady-State) Object Number: 30 Change Event Object Number: 32 Request Function Codes supported: 1 (read) Static Variation reported when variation 0 requested: 2 (16-Bit Analog Input) Change Event Variation reported when variation 0 requested: 2 (16-Bit Analog Change Event w/o Time) The Data Size for all points is 32 bits 1 Range / Units Default Point Name/Description Change Event Scan Group (0 to 16777215 for I.D. Assigned Class 32 bit data - FS), Scaling (*10) (1, 2, 3 or none) 14 Vab Mag 0 - FS Volts 3 12 15 Vbc Mag 0 - FS Volts 3 12 16 Vca Mag 0 - FS Volts 3 12 17 Kwatt3 0 - FS Watts 3 13 18 Kvar3 0 - FS Vars 3 14 19 I0 0 - FS Amps 3 15 20 I1 0 - FS Amps 3 15 21 I2 0 - FS Amps 3 15 22 V0 0 - FS Volts 3 16 23 V1 0 - FS Volts 3 16 24 V2 0 - FS Volts 3 16 25 Power Factor -100 to +100 3 17 26 Power Factor Angle -1800 to 1800 degrees 3 18 27 PT Ratio 100 to 1000 3 19 28 CT Ratio 20 to 5000 3 19 29 Ia Phase Angle -1800 to 1800 degrees 3 20 30 Ib Phase Angle -1800 to 1800 degrees 3 20 31 Ic Phase Angle -1800 to 1800 degrees 3 20 32 Ip Phase Angle -1800 to 1800 degrees 3 20 33 Van Phase Angle -1800 to 1800 degrees 3 21 34 Vbn Phase Angle -1800 to 1800 degrees 3 21 35 Vcn Phase Angle -1800 to 1800 degrees 3 21 36 Vs Phase Angle -1800 to 1800 degrees 3 21 37 I0 Angle -1800 to 1800 degrees 3 25 38 I1 Angle -1800 to 1800 degrees 3 25 39 I2 Angle -1800 to 1800 degrees 3 25 40 V0 Angle -1800 to 1800 degrees 3 26 41 V1 Angle -1800 to 1800 degrees 3 26 42 V2 Angle -1800 to 1800 degrees 3 26 -1 – unknown 0 – none 1 – AG 2 – BG 3 – CG Fault Type – Newest Fault 4 – AB 43 5 – BC 2 22 6 – CA 7 – ABG 8 – BCG 9 – CAG 10 – ABC 44 Fault Location – Newest Fault 0 to 10000 miles 2 22 45 Fault Number – Newest Fault 0 to 65535 2 22 46 Settings Group – Newest Fault Group # 1 to 8 2 22 47 Breaker Operations Counter – Newest 0 to 65535 2 22 Fault 48 Trip Bits – Newest Fault 0 - normal trip 2 22 1 - time delayed trip 49 Fault Time – Newest Fault (DNP time 0 to 65535 2 22 format 16 msb bits) 50 Fault Time – Newest Fault (DNP time 0 to 65535 2 22 Page 63 of 145 REL 512 DNP 3.0 Automation Technical Guide Analog Input Points Static (Steady-State) Object Number: 30 Change Event Object Number: 32 Request Function Codes supported: 1 (read) Static Variation reported when variation 0 requested: 2 (16-Bit Analog Input) Change Event Variation reported when variation 0 requested: 2 (16-Bit Analog Change Event w/o Time) The Data Size for all points is 32 bits 1 Range / Units Default Point Name/Description Change Event Scan Group (0 to 16777215 for I.D. Assigned Class 32 bit data - FS), Scaling (*10) (1, 2, 3 or none) format 16 middle bits) 51 Fault Time – Newest Fault (DNP time 0 to 65535 2 22 format 16 lsb bits) 52 Fault Type – Record #1 none 23 53 Fault Location – Record #1 none 23 54 Fault Number – Newest Fault none 23 55 Settings Group – Record #1 Same as points none 23 56 Breaker Operations Counter – Record #1 43 to 51 none 23 57 Trip Bits – Record #1 none 23 58 Fault Time (high 16 bits) – Record #1 none 23 59 Fault Time (middle 16 bits) – Record #1 none 23 60 Fault Time (low bits) – Record #1 none 23 61 Fault Type – Record #2 none 23 62 Fault Location – Record #2 none 23 63 Fault Number – Record #2 none 23 64 Settings Group – Record #2 Same as points none 23 65 Breaker Operations Counter – Record #2 43 to 51 none 23 66 Trip Bits – Record #2 none 23 67 Fault Time (high 16 bits) – Record #2 none 23 68 Fault Time (middle 16 bits) – Record #2 none 23 69 Fault Time (low bits) – Record #2 none 23 70 Fault Type – Record #3 none 23 71 Fault Location – Record #3 none 23 72 Fault Number – Record #3 none 23 73 Settings Group – Record #3 Same as points none 23 74 Breaker Operations Counter – Record #3 43 to 51 none 23 75 Trip Bits – Record #3 none 23 76 Fault Time (high 16 bits) – Record #3 none 23 77 Fault Time (middle 16 bits) – Record #3 none 23 78 Fault Time (low bits) – Record #3 none 23 79 Fault Type – Record #4 none 23 80 Fault Location – Record #4 none 23 81 Fault Number – Record #4 none 23 82 Settings Group – Record #4 Same as points none 23 83 Breaker Operations Counter – Record #4 43 to 51 none 23 84 Trip Bits – Record #4 none 23 85 Fault Time (high 16 bits) – Record #4 none 23 86 Fault Time (middle 16 bits) – Record #4 none 23 87 Fault Time (low bits) – Record #4 none 23 88 Fault Type – Record #5 none 23 89 Fault Location – Record #5 none 23 90 Fault Number – Record #5 none 23 91 Settings Group – Record #5 Same as points none 23 92 Breaker Operations Counter – Record #5 43 to 51 none 23 93 Trip Bits – Record #5 none 23 94 Fault Time (high 16 bits) – Record #5 none 23 95 Fault Time (middle 16 bits) – Record #5 none 23 96 Fault Time (low bits) – Record #5 none 23 Page 64 of 145 REL 512 DNP 3.0 Automation Technical Guide Analog Input Points Static (Steady-State) Object Number: 30 Change Event Object Number: 32 Request Function Codes supported: 1 (read) Static Variation reported when variation 0 requested: 2 (16-Bit Analog Input) Change Event Variation reported when variation 0 requested: 2 (16-Bit Analog Change Event w/o Time) The Data Size for all points is 32 bits 1 Range / Units Default Point Name/Description Change Event Scan Group (0 to 16777215 for I.D. Assigned Class 32 bit data - FS), Scaling (*10) (1, 2, 3 or none) 97 Fault Type – Record #6 none 23 98 Fault Location – Record #6 none 23 99 Fault Number – Record #6 none 23 100 Settings Group – Record #6 Same as points none 23 101 Breaker Operations Counter – Record #6 43 to 51 none 23 102 Trip Bits – Record #6 none 23 103 Fault Time (high 16 bits) – Record #6 none 23 104 Fault Time (middle 16 bits) – Record #6 none 23 105 Fault Time (low bits) – Record #6 none 23 106 Fault Type – Record #7 none 23 107 Fault Location – Record #7 none 23 108 Fault Number – Record #7 none 23 109 Settings Group – Record #7 Same as points none 23 110 Breaker Operations Counter – Record #7 43 to 51 none 23 111 Trip Bits – Record #7 none 23 112 Fault Time (high 16 bits) – Record #7 none 23 113 Fault Time (middle 16 bits) – Record #7 none 23 114 Fault Time (low bits) – Record #7 none 23 115 Fault Type – Record #8 none 23 116 Fault Location – Record #8 none 23 117 Fault Number – Record #8 none 23 118 Settings Group – Record #8 Same as points none 23 119 Breaker Operations Counter – Record #8 43 to 51 none 23 120 Trip Bits – Record #8 none 23 121 Fault Time (high 16 bits) – Record #8 none 23 122 Fault Time (middle 16 bits) – Record #8 none 23 123 Fault Time (low bits) – Record #8 none 23 124 Fault Type – Record #9 none 23 125 Fault Location – Record #9 none 23 126 Fault Number – Record #9 none 23 127 Settings Group – Record #9 Same as points none 23 128 Breaker Operations Counter – Record #9 43 to 51 none 23 129 Trip Bits – Record #9 none 23 130 Fault Time (high 16 bits) – Record #9 none 23 131 Fault Time (middle 16 bits) – Record #9 none 23 132 Fault Time (low bits) – Record #9 none 23 133 Fault Type – Record #10 none 23 134 Fault Location – Record #10 none 23 135 Fault Number – Record #10 none 23 136 Settings Group – Record #10 Same as points none 23 137 Breaker Operations Counter – Rec. #10 43 to 51 none 23 138 Trip Bits – Record #10 none 23 139 Fault Time (high 16 bits) – Record #10 none 23 140 Fault Time (middle 16 bits) – Record #10 none 23 141 Fault Time (low bits) – Record #10 none 23 142 Fault Type – Record #11 none 23 143 Fault Location – Record #11 none 23 144 Fault Number – Record #11 none 23 145 Settings Group – Record #11 Same as points none 23 146 Breaker Operations Counter – Rec. #11 43 to 51 none 23 Page 65 of 145 REL 512 DNP 3.0 Automation Technical Guide Analog Input Points Static (Steady-State) Object Number: 30 Change Event Object Number: 32 Request Function Codes supported: 1 (read) Static Variation reported when variation 0 requested: 2 (16-Bit Analog Input) Change Event Variation reported when variation 0 requested: 2 (16-Bit Analog Change Event w/o Time) The Data Size for all points is 32 bits 1 Range / Units Default Point Name/Description Change Event Scan Group (0 to 16777215 for I.D. Assigned Class 32 bit data - FS), Scaling (*10) (1, 2, 3 or none) 147 Trip Bits – Record #11 none 23 148 Fault Time (high 16 bits) – Record #11 none 23 149 Fault Time (middle 16 bits) – Record #11 none 23 150 Fault Time (low bits) – Record #11 none 23 151 Fault Type – Record #12 none 23 152 Fault Location – Record #12 none 23 153 Fault Number – Record #12 none 23 154 Settings Group – Record #12 Same as points none 23 155 Breaker Operations Counter – Rec. #12 43 to 51 none 23 156 Trip Bits – Record #12 none 23 157 Fault Time (high 16 bits) – Record #12 none 23 158 Fault Time (middle 16 bits) – Record #12 none 23 159 Fault Time (low bits) – Record #12 none 23 160 Fault Type – Record #13 none 23 161 Fault Location – Record #13 none 23 162 Fault Number – Record #13 none 23 163 Settings Group – Record #13 Same as points none 23 164 Breaker Operations Counter – Rec. #13 43 to 51 none 23 165 Trip Bits – Record #13 none 23 166 Fault Time (high 16 bits) – Record #13 none 23 167 Fault Time (middle 16 bits) – Record #13 none 23 168 Fault Time (low bits) – Record #13 none 23 169 Fault Type – Record #14 none 23 170 Fault Location – Record #14 none 23 171 Fault Number – Record #14 none 23 172 Settings Group – Record #14 Same as points none 23 173 Breaker Operations Counter – Rec. #14 43 to 51 none 23 174 Trip Bits – Record #14 none 23 175 Fault Time (high 16 bits) – Record #14 none 23 176 Fault Time (middle 16 bits) – Record #14 none 23 177 Fault Time (low bits) – Record #14 none 23 178 Fault Type – Record #15 none 23 179 Fault Location – Record #15 none 23 180 Fault Number – Record #15 none 23 181 Settings Group – Record #15 Same as points none 23 182 Breaker Operations Counter – Rec. #15 43 to 51 none 23 183 Trip Bits – Record #15 none 23 184 Fault Time (high 16 bits) – Record #15 none 23 185 Fault Time (middle 16 bits) – Record #15 none 23 186 Fault Time (low bits) – Record #15 none 23 187 Fault Type – Record #16 none 23 188 Fault Location – Record #16 none 23 189 Fault Number – Record #16 none 23 190 Settings Group – Record #16 Same as points none 23 191 Breaker Operations Counter – Rec. #16 43 to 51 none 23 192 Trip Bits – Record #16 none 23 193 Fault Time (high 16 bits) – Record #16 none 23 194 Fault Time (middle 16 bits) – Record #16 none 23 195 Fault Time (low bits) – Record #16 none 23 Page 66 of 145 REL 512 DNP 3.0 Automation Technical Guide Note: 1 at present the default assignments are not configurable. The capability of changing assignments with the Assign Class function may be provided in the future. Binary Output Status Points & Control Relay Output Blocks The following table lists both the Binary Output Status Points (Object 10) and the Control Relay Output Blocks (Object 12). The status points are read-only, and represent the current status of their corresponding control relay output block. For Trip and Close operations, points 0 through 21 can be thought to be organized in pairs: a trip command applying to the even numbered point and a close command applying to the following odd numbered point. This pairing is configurable with REL 512 DNP Configuration Settings. Each even/odd point couplet may be configured as paired or unpaired. This pairing organization allows a close command that is executed on an even point to actually be applied to the following odd point for SCADA Systems that only support single point control. For pulsed commands the pulse width is fixed at 300 msec for Trip and Close; the pulse width specified in the control request is ignored. For the Pulse On/Off command, variable pulse widths are accepted; but the minimum pulse width is fixed at 60 msec. Control Code Configuration The second set of parameters which must be specified for control are particular to the control object 12. The specified control arguments required for in the Relay parameters field of the test set is: Control Code Count (Number of Times Control operation is to be executed) Length of Pulse ON (in mS) (Length of Pulse Control ON) Length of Pulse OFF (in mS) (Length of Pulse Control OFF) Status (TPU2000/TPU2000R this argument is always = 0) The Pulse Control OFF argument is useful when the count is greater than 1. The Pulse ON and Pulse OFF time creates a pulse train duration useful for execution of specific consecutive timed events. The control codes are defined in DNP 3.0 as per the bit pattern as outlined in Figure 5-2. The following permutations are as such: 00 (hex) 01 (hex) 02 (hex) 03 (hex) 04 (hex) 81 (hex) 41 (hex) NULL Control (Cancels the Control Operation Depending on the Control function) Momentary Pulse ON (Duration = Pulse ON Value Field) Momentary Pulse OFF (Duration = Pulse OFF Value Field) Latch ON (Set Control Value to ON until reset or Latch OFF) Latch OFF (Set Control Value to OFF until reset of Latch ON) Trip Designation with Momentary On (Paired Point Operation) Close Designation with Momentary Off (Paired Point Operation) Each of the above control functions included in Table 5-1 shall be explained using single point control are reviewed in the following sections. It is noted that the NULL CONTROL CODE is not supported and sending such a control code shall generate a returned message that the request is not accepted. This does not affect the operation of the relay. Page 67 of 145 REL 512 DNP 3.0 Automation Technical Guide Bit 7 Bit 6 Bit 3 Bit 2 Bit 1 Bit 0 Trip = 01 Close = 10 For Control Code Bits 0000 = Null Operation 0001 = Pulse On (for the specific On Time) 0010 = Pulse Off (for the specific Off Time) 0011 = Latch On 0100 = Latch Off • • The control code for Trip would be 41x (hex) The control code for Close would be 81x (hex) Figure 5-2. DNP Control Field Bit Designation The following sections explain the control operations for each of the aforementioned grouping of points. The supported objects and variants for each of the REL 512 control types are listed in REL 512 / 2000R Implementation of the DNP 3.0 User Guide Revision 3.0. Paired Point Operation Several indices are configured as paired points. Paired point operation, as per the DNP 3.0 definition operates with the TRIP (81x) and CLOSE (41x) commands. Paired Point implementation occurs with the following groups. Physical Output Test Control Trip Operate Control Reset Element Control User Logical Control Several Groups of data have a PAIRED POINT operation implementation with respect to control codes TRIP 81x and CLOSE 41x. Although the REL 512 supports the DNP close command, command execution of the physical breaker (close), only follows the defined index. Each point in a PAIRED POINT IMPLEMENTATION group operates as such: EVEN POINT NUMBER: If a TRIP Command is sent to this point the corresponding function is energized (for example, trip physical output [index 0], Output 1 [index 2], or ULO 1 [index 14]). If a CLOSE command is sent to an even index, the next corresponding function [odd paired index] is energized (for example, spare [index 1], Output 2 [index 3] or ULO 2 [index 15]). The groups described as being paired points shall have the odd index- even index point pairing. ODD POINT NUMBER: If a CLOSE Command (41x) is sent to an ODD index, the defined operation shall occur as the index is defined in Table 5-1. If a TRIP (81x) command is sent, the command shall be accepted but ignored. The advantage of a PAIRED POINT implementation is that some legacy host devices perform trip and close on the same point index. The PAIRED POINT implementation allows ABB protective relays to provide superior automation control via DNP 3.0 with a wide variety of host implementations. PAIRED POINT index implementation is not configurable from the operator or from the host device. Page 68 of 145 REL 512 DNP 3.0 Automation Technical Guide Binary Output Status Points Object Number: 10 Request Function Codes supported: 1 (read) Default Variation reported when variation 0 requested: 2 (Binary Output Status) Control Relay Output Blocks Object Number: 12 Request Function Codes supported: 3 (select), 4 (operate), 5 (direct operate), 6 (direct operate, no acknowledge) Point Name/Description Paired Control Supported Control Relay Output I.D. Points Block Fields 0 Output Relay 1 P Trip, Close1, Pulse On, Pulse Off, 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Output Relay 2 Output Relay 3 Output Relay 4 Output Relay 5 Output Relay 6 Output Relay 7 Output Relay 8 Output Relay 9 Output Relay 10 Output Relay 11 Output Relay 12 Output Relay 13 Output Relay 14 Output Relay 15 Output Relay 16 Output Relay 17 Output Relay 18 Trip Breaker 2 Close Breaker Trip Breaker (duplicate of #18) Close Breaker, with 3 Supervision Pilot Enable/Disable Reset Front Panel Release DNP Control Points P P P P P P P P P P Scan Group 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 24 Latch On, Latch Off Trip, Close, Pulse On, Pulse Off, Latch On, Latch Off Trip, Close1, Pulse On, Pulse Off, Latch On, Latch Off Trip, Close, Pulse On, Pulse Off, Latch On, Latch Off Trip, Close1, Pulse On, Pulse Off, Latch On, Latch Off Trip, Close, Pulse On, Pulse Off, Latch On, Latch Off Trip, Close1, Pulse On, Pulse Off, Latch On, Latch Off Trip, Close, Pulse On, Pulse Off, Latch On, Latch Off Trip, Close1, Pulse On, Pulse Off, Latch On, Latch Off Trip, Close, Pulse On, Pulse Off, Latch On, Latch Off Trip, Close1, Pulse On, Pulse Off, Latch On, Latch Off Trip, Close, Pulse On, Pulse Off, Latch On, Latch Off Trip, Close1, Pulse On, Pulse Off, Latch On, Latch Off Trip, Close, Pulse On, Pulse Off, Latch On, Latch Off Trip, Close1, Pulse On, Pulse Off, Latch On, Latch Off Trip, Close, Pulse On, Pulse Off, Latch On, Latch Off Trip, Close1, Pulse On, Pulse Off, Latch On, Latch Off Trip, Close, Pulse On, Pulse Off, Latch On, Latch Off Trip, Close1, Pulse On Trip, Close, Pulse On Trip, Close1, Pulse On Trip, Close, Pulse On Latch On, Latch Off Pulse On4 Pulse On4 Page 69 of 145 REL 512 DNP 3.0 Automation Technical Guide Note: 1 2 3 4 when paired, this function operates on the next (even numbered) point in the table. When unpaired it operates on the selected point. the Close function must be mapped to one of the output relays in order for this function to operate. the relay must be in lockout mode in order for this point to function correctly. the other functions are not meaningful, however, Trip, Close and Latch On requests are accepted and the Pulse On function is performed. Pulse Off and Latch Off requests are accepted but no action is performed. Page 70 of 145 REL 512 DNP 3.0 Automation Technical Guide Appendix A - Revision History The following lists the DNP 3.0 history for the software history of each revision change. Software History: V2.3 - Base Version V2.4 - Provides capability for communications via the Aux Comm RS232 port using switched carrier (RTS/CTS), as needed for PECO system. - Corrected definition of User Logical Output (ULOx) points as Binary Outputs. These points now contain the status of the ULOx points not the last change-of-state message sent to the DPU. V2.6 - Corrected handling of “spare” points when performing DNP group scans. - Added address checking for 10-Byte protocol. Previously, units with DNP responded to any 10-Byte commands regardless of address. - Corrected problems with decoding global address (x’FFFF’) when communicating with DNP master station. V2.8 - The thirty-two 16-bit User Definable (Modbus) Registers have been added as static analog points (97 to 128 on the DPU and 319 to 350 on the TPU). This provides user scaleable analog points to circumvent the 32-bit processing limitations of the Harris D20 RTU. These additional points are processed as signed analogs. - Numerous performance enhancements have reduced the worst case turnaround for DNP requests to approximately 350 msec on the DPU. Typical response for most requests is less than 200 msec. - The control logic was revised to detect busy conditions and support multiple concurrent operations. This fixes the problems with ULO3. - Collection of fault records by DNP is delayed until the fault distance calculation is completed. - The processing of spare points has been corrected. - The Application Layer Headers are now properly built when all the qualifier code requests “all” objects. V2.9 - Support added for new Auxillary Communications Card (Type 8) with two RS485 ports. - Additional control point added for “Reset all Seal Ins”. - Additional class 3 digital event points added (see list at end of Binary Input Points). - Additional analog point for 3 phase volt-amps V3.0 - Corrected processing of control requests as per DNP Basic 4 Document Set. - Automatically reset seal-in points after they have been reported by DNP, depending on the status of Mode Parameter 5. - Added DNP support for Forced I/O points (Logical Inputs and Physical Inputs/Outputs) - Added event masking for Binary Input events. - Prevented accumulation of Class 2 or 3 changes for points not enabled via Scan Groups or the Binary Input Event Masking. - Performance enhancements added to reduce the turn-around time when requesting class 1, 2 or 3 data. V3.4 - Provided Binary Event (change) reporting for most Binary Input points as indicated in documentation. Binary changes for sealed-in points are now limited to current state reporting (i.e., a seal-in must be reset before another “set” event will be reported). - Added capability to configure the period for requesting a time synchronization from the master via Parameter 9. - Added performance improvements secondary rear port (non-DNP port) to enhance communications with ECP program. - Add support for running with the CPU clock stopped (required for final manufacturing tests). - Revise start-up processing to support revisions to Motorola processor used in Aux. Comm. boards. - Removed support for Null (canceled) control requests. These are now treated as NOPs. - Repeat counts (>1) are now only permitted for ULO points. Multiple controls to other points were meaningless and did not work properly. - Fixed support for Data Link Acknowledge to allow data link layer confirms to work properly. - Fixed problem with control point becoming permently “active”. - Fixed internal RTS problem the caused failed control requests and errors when saving changed settings. - Fixed problems with handling requests for multiple “ranges” of objects. - Add support for running with the CPU clock stopped (required for final manufacturing tests). Page 71 of 145 REL 512 DNP 3.0 Automation Technical Guide Document History: V2.0 - Base Version V2.1 - 52A Closed event point changed from #80 to #11. V2.3 - Document changed to incorproate new features. Main change is definition of “scan type” for each DNP point. V2.8 - Document changed to include additional static analog points (97 to 128) and clarify and expand on descriptions of Parameter Settings. V2.9 - Updated to add new points as described above. V3.0 - Moved Revision History from Appendix B to Appendix C. - Inserted new Appendix B - Event Masking - Extended point list to allow for Forced I/O points, Binary Outputs 32-137. - Added points 128 and 129 to tables. - Changed status of bits used for Event Masking in Appendix B. - Added description for Mode Parameter 5. - Indicated points unique to DPU2000 or DPU2000R. - Added description of processing for sealed-in points. V3.4 - Added description for Parameter 9. - Revised description of Mode Parameter 1 based on changes to V3.4 DNP Software. - Revised description of Mode Parameter 5 based on changes to V3.4 DNP Software. - Expanded description of Forced I/O points (default assignments) and corrected these assignments for points 38 thru 71. - Expanded description of control processing to include types of control request allowed. - Added Binary Inputs 131-168 for TPU2000R 3 winding - Added Analog Inputs 351-354 for TPU2000R 3 winding - Updated point tables to properly indicate points that are unique to the TPU2000 and TPU2000R (2 and 3 winding versions). - Changed point tables to use DNP Type, ES-01-R, to indicate points that support both Binary Static and Binary Event reporting. - Revised Appendix B to update description of Event Masking. - Changed formatting of document for laser printer. - Added Binary Inputs 131-168 for TPU2000R 3 winding - Added Analog Inputs 351-354 for TPU2000R 3 winding Page 72 of 145 REL 512 DNP 3.0 Automation Technical Guide Appendix B - ASCII Conversion Table Decimal Value 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 Hexadecimal Control Value Character 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E OF 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 Character NUL (CTRL @) Null SOH (CTRL A) STX ( CTRL B) ETX (CTRL C) EOT (CTRL D) ENQ (CTRL E) ACK(CTRL F) BEL (CTRL G) Beep BS (CTRL H) Backspace HT (CTRL I) Tab LF (CTRL J) Line-feed VT (CTRL K) Cursor home FF (CTRL M) Form-feed CR (CTRL N) Carriage Return (Enter) SO (CTRL O) Shift Out SI (CTRL P) Shift In DLE Data Link Escape DCI DC2 DC3 DC4 NAK SYN ETB CAN EM SUB ESC Cursor right Cursor left Cursor up Cursor down Space ! “ # $ % & ‘ ( ( * + , . / 0 1 2 3 Page 73 of 145 REL 512 DNP 3.0 Automation Technical Guide 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 4 5 6 7 8 9 < > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l m n Page 74 of 145 REL 512 DNP 3.0 Automation Technical Guide 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 6F 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F o p q r s t u v w x y z { | } ~ DEL Page 75 of 145 REL 512 DNP 3.0 Automation Technical Guide Appendix C - Modem Communications to ABB Relays REV 1.1 6/05/2001 Abstract: Advances in telephony switching systems and semiconductor technologies have made digital communication via analog public telephone systems an affordable reality. Advances from the initial Bell 202 modems operating at speeds of 300 baud to modern day V.90 modems which can theoretically operate at 56K have made fast data transfer within a substation a reality. This paper explains the theory of modern day modems and their use with ABB protective relays and configuration software. Although many manufacturer’s of modem equipment are available, this application note covers the theory and application of 10 bit dial-up telephone modems. ABB does not specify specific modem vendors equipment, this application note is to be a guide to configuration of general vendor’s telephony equipment with various ABB products. This application note is intended to present four examples of modem connectivity between ABB products and a personal computer. Modem Theory EARLY MODEMS In the beginning, telephony operated using analog signals. The legacy public telephone network required that the standard Bell Telephone. Signals placed upon the telephone network consisted of voice communication. The channels were limited (which led to the creation of the party- line) and communication consisted of much dead time in which no activity was occurring on the expensive phone connection. When digital computers were evolving, there came a need to interconnect the various sites for a limited period of time. Expensive digital data exchange networks were available for device interconnection. Installation of these systems for limited use was impractical due to installation costs but also for their operational costs. Some systems (such as ARPA net [precursor to the internet]) were available but only to the military and select universities. Another method had to be developed to allow general industries to communicate via a public medium. It was widely known that Analog signals have three distinct characteristics. a. Frequency ( which may be varied and measured in communication systems). b. Amplitude ( which may be increased decreased). c. Phase ( which may be shifted with respect to a particular reference at any time). Engineers at Western Electric (the R&D arm of Bell Telephone) took advantage of these characteristics of an analog signal and created a device called a modem. MO – MODULATOR : DEM – DEMODULATOR. The public telephone network communication channel was able to carry signals from 300 Hz to 4,000 Hz. The modem translated the signal from a digital waveform to an analog waveform (modulator) and transferred it to a telephone line analog grade signal. Figure 1 illustrates this transformation. The receiving modem translated the analog signal to a digital signal (demodulator)Thus the initial methods of communicating were developed to use the operating analog bandwidth of the telephone systems. The physical interface employed for the digital interface was a recently specified RS 232 interface. For a more in depth explanation of RS 232, please reference other application notes available from ABB’s FAXBACK service or WEB Site. 1 0 1 0 Figure 1. Frequency Shift Keying Modulation Page 76 of 145 REL 512 DNP 3.0 Automation Technical Guide The first Bell 202 modems used data transmission rates from 300 Baud to 1200 baud using Frequency Shift Keying. FSK modems used one of two methods of implementation. Half Duplex FSK and Full Duplex FSK. Half duplex FSK: One frequency band pair is used to transmit/receive data. The one modem transmitting data uses one frequency to denote a binary “1” and another to denote a binary “0”. The other modem decodes the 1’s and 0’s for corresponding to the specific frequency. The signal is then translated from the analog encoding to the digital encoding. Turn around time is an issue when the modems switch from transmitting data to receiving data. Less of the telephone bandwidth range is used for communications, but communications are slower in that each modem must signify whether it is to transmit or receive data. One cannot transmit or receive data at the same time. Full duplex FSK: Two frequency bands are employed. One set of frequencies represent the transmit channel (frequencies allocated to the transmitted “1”’s or “0”’s). The other set of frequencies are allocated to the receive channel (frequencies allocated to the receivers “1”’s or “0”’s). This type of encoding has advantages in that no delay results for channel turnaround delay results and that full duplex communications is possible. The first Bell 202 modems were developed using FSK. With these limitations, FSK technologies are not used in modern modems. NEXT DEVELOPMENTS However innovative these FSK methods were, there was still a limitation on the bandwidth of the telephone network. FSK used an entire phase in the frequency. The next innovation was to use analog to digital converters to send/receive more information at faster data rates than the maximum frequency of 4,000 Hz that a telephone system may allow. New A/D or D/A converters were able to convert signals dependent upon the phase shift of the signal. Using fast analog to digital (A/D) and digital to analog (D/A) converters made data transfer rates in excess of 4000 baud possible. Intermediate developments using the combination of phase and multiple bits could be encoded into a symbol. Four symbols could be represented by two bits. The transmission of the bits could be referenced with relation to the frequency and phase shift. For a brief time, a method using the analog signal phase shift, frequency allowed data to be transmitted/received in excess of 4000 Hz. The method was referred to as Quad Phase Shift Keying or Differential Phase Shift Keying. However, this method was short lived due to the fact that more efficient methods of data encoding were developed. The next development which elevated modem data transfer rates to those from 9600 to 33,600 baud. The method is referred to as Quadrature Amplitude Modulation (QAM). Modern modems (such as those sold in electronics stores) use this technique in that the amplitude, phase, and frequency encode the digital bits into a symbol. A simplified explanation is provided. Figure 2 illustrates the possible combinations of data, which may be represented by two bits. Four possible symbols may be transmitted/received using this method (as was the case with QPSK methods). If, for example a sine wave is split into four quadrants each part of the phase could represent each of the two bit combinations in an analog fashion. Thus the phase from 0 – 90 degrees could represent the value 00, 90-180 degrees could represent the value 01, 180-270 degrees could represent the value 10, and logically 270 – 360 could represent the value 11. A rapid A/D and D/A converter could determine the phase of the conversion area and determine the value depending upon the amplitude of the signal being converted. Thus, four symbols could be transferred in a single phase. Page 77 of 145 REL 512 DNP 3.0 Automation Technical Guide TWO BIT REPRESENTATION 0 0 01 4 Bit Combinations 10 11 00 01 0 90 180 270 360 DEGREES 0 90 90 180 180 270 270 360 01 WAVEFORM 11 BIT MAP ASSIGNMENT VERSUS FREQUENCY Figure 2. QAM Analysis 4 Bit Analysis Expanding this concept, Figure 3 illustrates what could occur if a 16 symbols could be transferred using an extended sine wave interpretation. The proper designation for this encoding is 16-QAM. Thus 16 is the number of symbols which may be expressed in one waveform. Each ¼ cycle could represent a quadrature 00 –01- 10- 11. Each ¼ cycle could then be designated to two bit values depending upon the phase angle location upon the cycle. QAM modem manufacturers have a quadrature plot illustrating the phase/bit encoding which occurs in their design. This technology allows modems to transfer data at rates of 33,600 bits per second over telephone lines designed to carry voice at 4000 hz. This is pretty impressive in that the average cost of a 10 bit synchronous modem capable of operating at 56K bits per second (theoretically) is $100. FOUR BIT REPRESENTATION 1 000 1001 1010 1011 1100 1101 1110 1111 0 000 0001 0010 0011 0100 0101 0110 0111 16 Bit Combinations 11 00 00 QUAD01 00 10 01 01 QUAD 10 11 0 90 180 270 360 DEGREES 0 90 90 180 180 270 270 360 10 QUAD WAVEFORM 11 QUAD BIT MAP ASSIGNMENT VERSUS FREQUENCY Figure 3. QAM – 16 Bit Encoding Another new technology used in modems is one called, Trellis Encoding Technology. One of the modems presented in this paper uses this technology which evaluates speed optimization and fast forward error detection/correction technology. Within the present V. standards, error detection/correction and line speed balancing improves with each technology. One modem shall be used in this paper which uses Trellis Encoding Technology. Page 78 of 145 REL 512 DNP 3.0 Automation Technical Guide THE TRICKY THING ABOUT BAUD RATES Baud rate is defined as the amount of changes a signal can undergo in 1 second. With FSK modems in the initial days of the Bell 202 modem, 1 baud = 1 bit. Today, with the complexity of modem technology, one bit does not equal one baud. As illustrated in the descriptions of DPSK and QAM, one transition of signal may not equal one baud in that two bits may represent 4 combinations, 3 bits may represent 8 combinations, 4 bits may represent 16 combinations, 8 bits may represent 256 combinations, and 12 bits may represent 4,096 combinations. Thus operation over a standard frequency 300, 600, or 2400 hertz (audio) may yield ( when signals are decoded into digital signals) baud rates of up to 33, 600 bits per second. Standards Early modems were defined as per their operating baud rate. An international committee the ITU-T (International Telecommunications Union) developed standards defining the operation of modems. Today, the V. (VEE DOT) standard is recognized as the modem definition standard to which modems are designed. Some standards are listed below: V.29 BIS - 2,400 Baud : 9,600 Bits per second: 2 Wire Full Duplex, 4-DSPK, 16 QAM V.32 BIS - 2,400 Baud: 14,400 Bits per second: 2 Wire Full Duplex 64- QAM, V.34 + - 2,400 Baud: 33,600 Bits per second: 2 Wire Full Duplex 4,096 QAM. With the increasing complexity of modem technology, another innovation came about increasing the acceptance of telephone modem technology in circuits, Hayes AT command set. Hayes was one of the pre-eminent manufacturers of modem technology in the early 70’s. They developed a command set which allowed a modem to be placed in several operational modes. Modems could be configured “on the fly” to auto-answer, change transmission/reception speeds, enable data encoding modes, dial out phone numbers ….. as well as other capabilities. With the introduction of the Hayes AT command set, integration of modems into more common acceptance within a variety of applications. Configuration could occur using a commonly supplied “WINDOWS” Terminal Emulator program. When the terminal connected with the modem the “AT” command could be sent to the modem with the appropriate command. Unfortunately over time there has been a deviation in the HAYES command set in that there is no such thing as a “STANDARD HAYES AT COMMAND” set. 10 Bit Versus 11 Bit Modems Commercially available dial-up modems, such as those generally sold through chain electronic stores may be used with many of the protocols offered in the ABB Protective relays. Modems such as those allowing telephone connectivity using 10 bit protocols are generally those available inexpensively. A 10 bit telephone modem is in the cost area of $100 (120 VAC operation) whereas 11 bit modems are in the area of cost of $1500 (120 VAC operation) [COSTS QUOTED ARE FOR YEAR 2000]. Modems using 125 VDC power sources are much more expensive than those quoted for 120 VAC operation. 10 BIT PROTOCOL START 1 2 3 4 5 6 7 PARITY STOP With Parity Checking START 1 2 3 4 5 6 7 STOP STOP Without Parity Checking Figure 4. 10 Bit Protocol Packet Page 79 of 145 REL 512 DNP 3.0 Automation Technical Guide 11 BIT PROTOCOL START 1 2 3 4 5 6 7 8 PARITY STOP With Parity Checking START 1 2 3 4 5 6 7 8 STOP STOP Without Parity Checking Figure 5. 11 Bit Protocol Packet The difference in packet size is illustrated in Figures 4 and 5. An 10 bit protocol is comprised of 1 Stop Bit, 1 Stop Bit, 1 Parity Bit, and 7 Data Bits or in the case of no parity, a stop bit is inserted to complete the 10 bit packet. Thus the total of bits transferred is 10 bits. 10 bit protocols usually are those encoded in ASCII. The ASCII encoding is defined to be a code from 00 to 7E (7 bits of data per character). A modem must be able to anticipate the data packet size in order to transfer the protocol bytes. A 10 bit modem is only able to reliably transmit/receive such 10 bit data packets. An 11 Bit protocol is one in which a byte’s worth of data may be transferred. An 11 bit protocol is comprised of 1 Stop Bit, 1 Parity Bit, 1 Start Bit, and 8 Data Bits or in the case of no parity an additional stop bit is substituted. Thus byte data may be transferred using an 11 bit modem without any data encoding. This is why 11 bit data may not be transferred/received via a 10 bit modem. It is important to match the modem with the protocol being used. Modem Cabling Options Cabling is dependent upon the devices attached and modem control options enabled. Through the “AT” modem command set such capabilities as RTS/CTS control, CD, DTR enable is possible. However, if one requires that a standard modem setting shall not be changed from location to location, signal jumpering through the cable may be preferable. What follows are a few diagrams illustrating cable connection between some devices. If one is unsure as to the function or emulation of RS 232 please reference one of the many fine ABB application notes on the subject. The Modem is generally a DCE RS232 device. It is configured via a personal computer using a terminal emulator program such as: DOS OPERATING SYSTEM – PROCOMM WINDOWS 3.1 - TERMINAL or a similar 16 bit application program commonly available. WINDOWS 95,98, or NT – Hyperterminal or similar 32 bit application programs commonly available. Such programs are available to be configured for handshake control, no handshake, XON/XOFF control. A variety of cables are illustrated for connection of a device to the modem for AT terminal command configuration, or device operation connectivity. Knowledge of the RS 232 port design is important when interconnecting a modem and an IED. Also if configuration software is required to communicate and configure the device through the com port, knowledge of the software’s requirement to control the RTS/CTS, CD, DSR, or DTR RS 232 lines must be known. Table 1 lists the variety of ABB products and the emulation of each of the ports and applicability of cable design. Page 80 of 145 REL 512 DNP 3.0 Automation Technical Guide Table 1. Product Cable Guidelines for Connection to a Modem Product DPU 2000 (Front and Back Ports) DPU 2000R (Front and Back Ports) TPU 2000 (Front and Back Ports) TPU 2000R (Front and Back Ports) GPU 2000R (Front and Back Ports) PONI R REL 512 Front Port REL 512 Rear Port (Serial Port 1) REL 512 Network Port (DNP 3.0 Card) RCP SOFTWARE RS 232 Port 9 Pin Female 9 Pin Female 9 Pin Female 9 Pin Female 9 Pin Female 9 Pin Male 9 Pin Female 9 Pin Male 9 Pin Female RS232 Emulation DTE DTE DTE DTE DTE DTE DCE DTE DTE CTS/RTS – DSR/DTR* Support NO NO* NO NO* NO NO* NO NO* NO NO* YES NO* NO NO* NO NO YES** NO* NO NO* Notes for Modem Connection USE FIGURE 6 CABLE USE FIGURE 6 CABLE USE FIGURE 6 CABLE USE FIGURE 6 CABLE USE FIGURE 6 CABLE USE FIGURE 7 or 8 Cable dependent on handshake options. USE FIGURE 9 CABLE USE FIGURE 12 CABLE (Modem Handshake options disabled). USE FIGURE 10 or 11 Cable dependent on handshake options. Sample cables are illustrated in FIGURES 12 and 13. IBM “XT” USUALLY 25 Pin DTE Female Hardware IBM Dependent COMPAT. 9 Pin Male ECP SOFTWARE IBM “XT” USUALLY NO OR 25 Pin DTE NO* WIN ECP SOFTWARE Female Hardware IBM Dependent COMPAT. 9 Pin Male PONI M COMSET IBM “XT” USUALLY YES SOFTWARE 25 Pin DTE NO* Female Hardware IBM Dependent COMPAT. 9 Pin Male ** PONI – R Card does not support DTR/DSR HANDSHAKE LINES Sample cables are illustrated in FIGURES 12 and 13. Sample cables are illustrated in FIGURES 12 and 13. Additionally, Figures 14 and 15 illustrate a communication cable configuration when a Modicon PLC is connected to a Modem (as is the case when it is using a Ladder Logic XMIT block allowing the port to operate as a host device). Page 81 of 145 REL 512 DNP 3.0 Automation Technical Guide IED Cable Male Cable Gender ( 9 Pin Connector) Modem Cable Male Cable Gender (25 Pin Connector) RCD TXD 2 3 3 RCD 2 TXD GND 5 DTE *OPTIONAL DEPENDENT ON MODEM CONTROL LINE CONFIGURATION 7 GND 8 CD * 4 RTS * 5 CTS * 6 DSR * 20 DTR * DCE (Signal Flow Direction Denoted By Arrow) Figure 6. Example Cable 1: GPU 2000R, TPU 2000, TPU 2000R, DPU 2000, DPU 2000R, MSOC, or DPU 1500R. It is recommended that DSR, CD, and CTS control be disabled via modem. If control is disabled, jumpers are optional as shown. PONI -R Female Cable Gender ( 9 Pin Connector) Modem Cable Male Cable Gender (25 Pin Connector) RCD TXD GND RTS CTS 2 3 5 7 8 DTE *OPTIONAL DEPENDENT ON MODEM CONTROL LINE CONFIGURATION 3 RCD 2 TXD 7 GND 4 RTS 5 CTS 6 DSR * 20 DTR * DCE (Signal Flow Direction Denoted By Arrow) Figure 7. Example Cable 2: ABB PONI R (installed in a REL 301, 302, 350, 352, 356 or MDAR), using hardware handshaking configured in the modem. Install optional jumper if modem configured for supplying DSR signal. Page 82 of 145 REL 512 DNP 3.0 Automation Technical Guide PONI -R Female Cable Gender ( 9 Pin Connector) Modem Cable Male Cable Gender (25 Pin Connector) RCD TXD 2 3 3 RCD 2 TXD GND RTS CTS 5 7 8 DTE *OPTIONAL DEPENDENT ON MODEM CONTROL LINE CONFIGURATION 7 GND 6 DSR * 20 DTR * DCE (Signal Flow Direction Denoted By Arrow) Figure 8. Example Cable 3: ABB PONI R (installed in a REL 301, 302, 350, 352, 356 or MDAR), NOT using hardware handshaking configured in the modem. Install optional jumper if modem configured for supplying DSR signal. REL 512 Front Port Cable Male Cable Gender ( 9 Pin Connector) Modem Cable Male Cable Gender (25 Pin Connector) RCD TXD 2 3 2 TXD 3 RCD GND 5 DCE *OPTIONAL DEPENDENT ON MODEM CONTROL LINE CONFIGURATION 7 GND 8 CD * 4 RTS * 5 CTS * 6 DSR * 20 DTR * DCE (Signal Flow Direction Denoted By Arrow) Figure 9. Example Cable 4: ABB REL 512 Connected to a Modem Through the RS 232 Front Port. It is recommended that RTS/CTS and DSR/DTR handshaking be disabled so optional jumpers need not be installed within the cable. Page 83 of 145 REL 512 DNP 3.0 Automation Technical Guide REL 512 Network Port Cable Male Cable Gender ( 9 Pin Connector) Modem Cable Male Cable Gender (25 Pin Connector) RCD TXD CTS RTS GND DCE 2 3 8 7 5 *OPTIONAL DEPENDENT ON MODEM CONTROL LINE CONFIGURATION 2 TXD 3 RCD 4 RTS 5 CTS 7 GND 6 DSR * 20 DTR * DCE (Signal Flow Direction Denoted By Arrow) Figure 10. Example Cable 5: REL 512 Network Port Cable Connection to a Modem. It is advisable that the DSR/DTR control be disabled in the modem so that the optional DSR/DTR jumpers not be inserted in the cable. REL 512 Network Port Cable Male Cable Gender ( 9 Pin Connector) Modem Cable Male Cable Gender (25 Pin Connector) RCD TXD CTS RTS GND DCE 2 3 8 7 5 *OPTIONAL DEPENDENT ON MODEM CONTROL LINE CONFIGURATION 2 TXD 3 RCD 4 RTS * 5 CTS * 7 GND 6 DSR * 20 DTR * DCE (Signal Flow Direction Denoted By Arrow) Figure 11. Example Cable 5: ABB REL 512 Connected to a Modem Through theRS 232 Network Port With Handshaking from the REL 512 Disabled. It is recommended that RTS/CTS and DSR/DTR handshaking be disabled in the Modem so optional jumpers need not be installed within the cable. Page 84 of 145 REL 512 DNP 3.0 Automation Technical Guide IBM PC Female Cable Gender ( 9 Pin Connector) Modem Cable Male Cable Gender (25 Pin Connector) RCD TXD DSR DTR GND RTS CTS 2 3 6 4 5 7 8 DTE (Signal Flow Direction Denoted By Arrow) 3 RCD 2 TXD 6 DSR 20 DTR 7 GND 4 RTS 5 CTS NOTE: If Software does not support DSR/DTR - install hardware signal jumpers in the cable and disable the modem control for DSR/DTR. If RTS/CTS is not controlled via software. Install RTS/CTS jumpers for each side of the cable. As an option, disableRTS/CTS handshaking on the modem. DCE Figure 12. Cable 6: IBM PC 9 Pin Port Cable Connecting to a Modem With Handshaking Enabled. Please refer to the NOTE for optional jumpers and modem configuration options. IBM PC “XT” Cable Male Cable Gender ( 25 Pin Connector) Modem Cable Male Cable Gender (25 Pin Connector) TXD RXD RTS CTS DSR GND CD DTR 2 3 4 5 6 7 8 20 DTE (Signal Flow Direction Denoted By Arrow) 2 TXD 3 RXD 4 RTS 5 CTS 6 DSR 7 GND 8 CD 20 DTR DCE Figure 13. Cable 7: IBM PC 25 Pin Port Cable Connecting to a Modem With Handshaking Enabled. Please refer to the NOTE for optional jumpers and modem configuration options. Note: Check Software With Respect for Supported RS 232 Pin Handshaking Options. Page 85 of 145 REL 512 DNP 3.0 Automation Technical Guide PLC Cable Male Cable Gender ( 9 Pin Connector) Modem Cable Male Cable Gender (25 Pin Connector) RCD TXD DSR DTR GND RTS CTS 2 3 4 6 5 7 8 9 DTE (Signal Flow Direction Denoted By Arrow) 3 RCD 2 TXD 7 GND 4 RTS 5 CTS 6 DSR 20 DTR DCE Figure 14. Cable 8: PLC Cable Connectivity to a Modicon PLC With Handshaking Enabled on the PLC and Modem Side. PLC Cable Male Cable Gender ( 9 Pin Connector) Modem Cable Male Cable Gender (25 Pin Connector) RCD TXD DSR DTR GND RTS * CTS * 2 3 4 6 5 7 8 9 DTE 3 RCD 2 TXD *OPTIONAL DEPENDENT ON MODEM CONTROL LINE CONFIGURATION 7 GND 4 RTS * 5 CTS * 6 DSR * 20 DTR * DCE (Signal Flow Direction Denoted By Arrow) Figure 15. Cable 8: PLC Cable Connectivity to a Modicon PLC With Handshaking Disabled on the PLC and Modem Side. AT Command Set Within these examples, a Hayes Compatible external telephone modem from 3Com and ZOOM is used. The command sets and S Registers differ slightly based upon the chip set used. For example, the ZOOM modem uses a chipset from LUCENT TECHNOLOGIES. The description of the command set is available from the internet web-site www.lucent.com. The 3Com modem has their command set available on the Internet web-site www.3com.com : The AT “&” commands are usually the same for both manufacturers, However, the definition of the AT “X” (Where X may be a letter or a “\” or && and a letter) commands vary widely between the manufacturers. Also the AT”S” (S register commands) register definitions vary widely between the two manufacturers. US Robotics (3COM) 56 K (V.90 or X2) Sportster Faxmodem The Sportster FAXMODEM is an external modem. This modem allows visualization of a variety of parameters allowing for visual troubleshooting in the event of trouble. The Sportster also has a set of dipswitches allowing for quick configuration without connection of a “Terminal Emulator” to configure the unit through “AT commands. Please refer to the web-site documents for a more complete explanation of configuration strings. Page 86 of 145 REL 512 DNP 3.0 Automation Technical Guide Prior to configuring the modem, attach the proper cable between the terminal emulator and the modem. One Should Type “AT” (without the quotation marks) and depress the enter key. The modem shall echo back an “OK” to acknowledge the communication. It is recommended that the dipswitches for this unit be set as follows: 1: Down – Data Terminal Ready Overriden (EXCEPT IF USING THE BIRT) 2: Down – Numeric Results Code Displayed 3: Down – Display Results Code 4: UP – Echo OFFLINE Commands 5: Dependent upon application – AUTO ANSWER 6: Down- Carrier Detect Override ( EXCEPT IF USING THE BIRT) 7: UP – Load NVRAM DEFAULTS 8: Down – Smart Mode Operation If the modem does not answer, please check the terminal emulator settings to be the following: 9600 Baud 7 Data Bits 1 Stop Even Parity Hardware or No Flow Control depending upon the cable selected and configuration of modem. VT 100 Terminal Emulation Inbound Communications : Carriage Return = Carriage Return and Line Feed If the modem does connect, then the following command may be sent to initialize the modem to parameterize the RS 232 com ports to the proper mode as explained below. AT=&F1 &F1 = Initialize the modem to Hardware Control Factory Defaults. AT = &A3 &B1 &C1 &D0 &G0 &H1 &I0 &K1 &M4 &N0 &P0 &R2 &S0 &T5 &U0 &Y1 &A = Protocol Indicators Added (error control and data compression) (3 = Yes) &B = Serial Port Rate (0= Follows Connection Rate) &C = Carrier Detect Override (1 = Overridden) &D = Data Terminal Ready Control (0= Overridden) &G= Guard Tone (0 = USA & Canada) &H = Hardware Flow Control (1 = CTS Enabled, 0 = Disabled) & I = Software Flow Control (0 = Disabled) & K = Data Control Compression (Auto Enable Disabled =0) & M = Error Control (4 = Normal) & N = Sets Connect Speed (0 = Determined by remote modem). & P = Rotary Dial Ratio Pulse (0 = USA & Canada) & R = RD Hardware Flow Control (RTS) ( 2 = Received Data To Computer) & S = Data Set Ready Operation (0 = DSR Overridden – Always ON) & T = Test Loop Enable (5 = Inhibits Test Mode) & U = Floor Connect Speed (Determined by &N Codes 0 = Best Possible Speed) & Y = Break Handling (1 = Expedited, Destructive) For this modem, Register S0 controls the Auto-answer feature. Autoanswer is controlled via the dip-switch position 5 and a combination of the value in register S0. To change the value of auto answer pickup (number of rings) send the command: ATS0= X, where X is the number of rings which the device shall sense for phone pickup. Note if the host is to dial out the number at all times, this parameter may be set to a “0” thereby disabling the auto answer feature. Page 87 of 145 REL 512 DNP 3.0 Automation Technical Guide Once the commands are written to the modem, one must write them into the modem’s non-volatile memory. The command should be sent as follows to the modem: AT=&W0 Or AT=&W1 The US ROBOTICS Sportster Modem offers two NVRAM profiles. W0 places the parameters in to Profile 1, whereas W1 places the parameters in Profile 2. ZOOM 56Kx Dual Mode Faxmodem Configuration The ZOOM modem offers more LED’s on their external modem than the US Robotics device. However, the ZOOM modem must be configured for each parameter via a “TERMINAL EMULATOR” program. The ZOOM modem does not offer a dipswitch for configuration of the different operation modes. AT “\” commands and AT “X” (where X is a letter) performs the setup of the device. Prior to configuring the modem, attach the proper cable between the terminal emulator and the modem. One Should Type “AT” (without the quotation marks) and depress the enter key. If the modem does not answer, please check the terminal emulator settings to be the following: 9600 Baud 7 Data Bits 1 Stop Even Parity Hardware or No Flow Control depending upon the cable selected and configuration of modem. VT 100 Terminal Emulation Inbound Communications : Carriage Return = Carriage Return and Line Feed If the modem does connect, then the following command may be sent to initialize the modem to parameterize the RS 232 com ports to the proper mode as explained below. AT=&F0 &F0 = Initialize the modem to Hardware Control Factory Defaults. AT = &C1 &D0 &G0 &K3 &Q0 &S0 &C = Carrier Detect Override (1 = Overridden) &D = Data Terminal Ready Control (0= Overridden) &G= Guard Tone (0 = USA & Canada) & K = Local Flow Control (0 = Disabled, 3 = Hardware RTS/CTS, 4 = XON/XOFF) &Q = Asynchronous Communication Mode (0 = Asynchronous Mode Buffered) & S = Data Set Ready Operation (0 = DSR Overridden – Always ON) For this modem, Register S0 controls the Auto-answer feature. Autoanswer is controlled via the dip-switch position 5 and a combination of the value in register S0. To change the value of auto answer pickup (number of rings) send the command: ATS0= X, where X is the number of rings which the device shall sense for phone pickup. Note if the host is to dial out the number at all times, this parameter may be set to a “0” thereby disabling the auto answer feature. To view the configuration, one may issue the following command: Page 88 of 145 REL 512 DNP 3.0 Automation Technical Guide AT=&V &V = View Active Configuration and Stored Profile This can view the programmed profiles. To store this configuration, the command AT=&W0. Refer to the document at www.lucent.com for an explanation of the AT “L” commands where L is the defined commands for dial-up, speaker control, and other modem functions. Connectivity Example 1- TPU 2000R to WINECP Configuration Software Connectivity Example If one was to connect a TPU 2000R to a configuration program such as WIN ECP over a long distance, a method to accomplish this is via a telephone dialup modem. As illustrated in Figure 17, a personal computer with WIN ECP is at the headquarters attached to a Public Telephone Switched Network. A standard 10 bit telephone modem is providing connection of the digital signals to the analog telephone line. At a remote location is a TPU 2000R attached to a modem providing connectivity. At both ends, the modem must be configured for appropriate auto-answer capabilities and RS 232 port capabilities. The protocol used to connect is ABB’s Standard 10 Byte protocol. This is a 10 bit protocol which may be transmitted asynchronously via a telephone dialup modem as those discussed via this application note. The Standard 10 byte protocol is a Master-Slave protocol. The device at the PC terminal end (WIN ECP End) sends the command dial up string whereas the DPU 2000R modem end must be configured to AUTOANSWER capabilities. If a ZOOM Modem is placed at the Host end and a US Robotics modem is placed at the IED end, the following configuration must be configured for each. Personal Computer With WIN ECP Installed Example Cable 1Figure 6. Example Cable 6 or 7 Figures 12 or 13. 10 Bit Dial Up MODEM 10 Bit Dial Up MODEM Auto- Answer Enabled C E Public Switched Telephone Network Address 1 9600 Baud Std 10 Byte Protocol TPU 2000R Figure 17. Application Topology Diagram PC to TPU 2000R Point to Point Figures 18 and 19 illustrate the WIN ECP screens required for connectivity to the device upon dial up. Upon execution of the ABB WIN ECP program, the initial screen shown in Figure 18 appears. One should select Remote Access which allows attachment to the remote modem if the proper AT command strings and numeric dial out instructions are given. Page 89 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 18. Initial ABB WIN ECP Access Screen If one depresses the OK button after selecting the WINDOWS RADIO button Selection for Remote Access, the screen as illustrated in Figure 19 appears. Figure 19. Parameter Selection Screen for Remote Dial-up Access The COM PORT is that of the PC’s modem port for attachment to the phone line. The Baud Rate is that for the remote modem and must match that of the Standard 10 Byte port which the modem is attached to the TPU 2000R. The Frame is that selected for the Remote TPU 2000R. The Unit Address is the unit address of the Remote TPU 2000R node. If Pulse Dial is selected, then the the Modem Command for sending the Pulse command is sent when dialing the number, otherwise, if Tone Dial is selected the command ATDT is sent to prefix the modem dial out string. In this case, the Tone Dial selection is activated. The dialup string is: ATDT ,,,,18005551212 ( the substation number of the remote device) To hang up the device the WIN ECP program must be able to send the command: ATH0 Page 90 of 145 REL 512 DNP 3.0 Automation Technical Guide Additionally, one must be sure that the appropriate modem configuration strings have been accepted by the modem for correct handshake control and remote auto answer configuration. Connectivity Example 2– REL 3XX to RCP Configuration Software If one wished to connect an ABB transmission relay such as a REL 300 (MDAR), REL 301, REL 302, REL 350, REL 352 or REL 356 to its configuration software (RCP – Remote Communication Program), using a dial up configuration as illustrated in Figure 20 is quite possible. The REL transmission relay uses a PONI R card for direct point to point communication via a cable or a modem. Please reference Instruction Leaflet 40-603 titled RCP Communication Program Users Guide and Instruction Leaflet 40-610 titled RS-PONI RS 232 Product Operated Network Interface User’s Guide. Personal Computer With RCP Installed Example Cable 1Figures 7 or 8.. Example Cable 6 or 7 Figures 12 or 13. 10 Bit Dial Up MODEM 10 Bit Dial Up MODEM Auto- Answer Enabled ABBABB ABB ABB ABB Public Switched Telephone Network - ANALOG LINE 9600 Baud Std 10 Byte Protocol REL 350 Figure 20. RCP to REL 350 Communication Topology Example In this example, a REL 350 shall be connected together with two US ROBOTIC Model 005686 Sportster Modems as described previously in this application note. RCP software shall be configured to communicate to the REL 350 via the aforementioned modems. Several steps are to be completed in this example. 1. Configure the PONI R dipswitches to correspond to the appropriate baud rates of the modem and RCP software. 2. Attach the correct cables as to the relay devices as indicated in Figure 20. In this example however, we shall disable handshaking (RTS/CTS) in the modem, so a straight through DTE to DCE cable is necessary. 3. Configure the US ROBOTIC modems to enable/disable the appropriate features. 4. Configure the RCP software to connect to the modem and enable communications. 5. Execute the communication command sequence and establish communications. STEP 1 In this example, the communication baud rate selection shall be set for 9600 baud. The baud rate of the PONI R card is configured via dipswitches located at the rear of the card, consult the PONI R manual referenced in this document. Also configure the PONI R card for NO COMMAND ISSUED mode. If one is to view the dipswitches of the PONI R (installed in the REL 350) card, the four dipswitch positions (left to right) are upward, and the rightmost dipswitch is downward. This corresponds to dipswitch positions 1 through 5 being 1 0 0 0 0 or ON, OFF, OFF, OFF, OFF. The PONI R CARD is now configured. STEP 2 As per Figure 20, connect the cables as indicated for the personal computer to modem and the REL 350 PONI R to modem connection. In this example, the handshaking shall be disabled on the PONI R card modem. Thus even using standard off the shelf cables (9 to 25 pin cables with each pin run straight through) shall operate in this example. Page 91 of 145 REL 512 DNP 3.0 Automation Technical Guide STEP 3 Now the modems shall be configured. Using the HYPERTERMINAL program supplied with Windows 95, 98, NT or 2000 can be used to configure the modems. Using hyperterminal as illustrated in Figure 21, one can issue the AT commands to configure the modem. Figure 21. Hyperterminal AT Command Set Example Each modem must be configured in this method. The modem parameters and dipswitch settings shall be covered for each modem location. DIPSWITCH SETTINGS FOR THE MODEM LOCAL TO RCP: Modem Dipswitch Position Position 1 UP – Data Terminal Position 2 UP – Verbal Results Codes Position 3 DOWN – Display Results Codes Position 4 UP-Echo Offline Commands Position 5 DOWN – Disable auto answer Position 6 DOWN – Carrier Detect Override Position 7 UP – Load NVRAM defaults Position 8 DOWN – Smart Mode DIPSWITCH SETTINGS FOR THE MODEM LOCAL TO THE REL 350/ PONI R card: Modem Dipswitch Position Position 1 UP – Data Terminal Position 2 UP – Verbal Results Codes Position 3 DOWN – Display Results Codes Position 4 UP-Echo Offline Commands Position 5 UP – Auto Answer on the first ring, or higher if specified in NVRAM Position 6 DOWN – Carrier Detect Override Position 7 UP – Load NVRAM defaults Position 8 DOWN – Smart Mode In setting the modems via the AT command set, it was determined that the modem closest to the computer executing the RCP program shall use the factory defaults of the modem right out of the box. If one was to view the USROBOTICS troubleshooting guide (available on the www.3com.com website) the factory defaults are listed in the downloadable files. Page 92 of 145 REL 512 DNP 3.0 Automation Technical Guide For the modem attached to the RCP program, one must change a few parameters within the modem to ensure connectivity. Starting with the factory default settings with the modem right out of the box, one should issue the AT commands: AT&H0&D0&K0&R1&S0 Which corresponds to the following definitions as designated in the USROBOTICS literature: &H0 = Flow Control Disabled &D0 = DTR Override ( Default) &K0 = DATA COMPRESSION DISABLED &R1=MODEM IGNORES RTS &S0 = DSR OVERRIDE ALWAYS ON As stated previously, other commands could be issued to the modem to allow it to peacefully co-exist and operate with the PONI R card. It is highly recommended to write the settings to the EEPROM in the modem by issuing the AT&W 1 or AT&W2 command STEP 4 The RCP program must now be configured to operate with the modem and issue the commands. The steps to use this are as follows: One must start RCP and enter the standard start screen as illustrated in Figure 22. Figure 22. RCP Standard Setup Screen One must configure a substation file for the REL 350 connection. Depress the Alternate key and S simultaneously to enter the Substation menu and depress the down arrow “↓” once to select “New Substation File” menu selection as illustrated in Figure 23. Page 93 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 23. New Substation Setup Screen A file must be configured for the REL 350 connection. Since a PONI R card is not addressable, it is considered a point to point device. As illustrated in Figure 24, one must pick an option for the configuration . In our example (as shown in the topology of Figure 20), although the REL 350 is networked through a modem, the connection is still point to point, one must select the selection “1” to allow correct connectivity. Figure 24 illustrates the screen queries and answers for this specific example. As illustrated in Figure 25, the operator must supply additional configuration data. Figure 25 lists the configuration responses for this example. Configuration data to be supplied is as such: RELAY TYPE – in this case selection 5 (REL 350) is selected. DEVICE DESCRIPTION – This field is used only for documentation purposes. LOGON SEQUENCE – In this example, the ATDT command is used for a pulse tone telephone system. Also in this example, an analog system is used and an additional prefix of “9” must be dialed to access the external public telephone system, the comma “,” is used to insert a delay before dialing the telephone number of the remote location (where the REL 350 resides). In this instance, the substation is located in a telephone overlay area where the area code must be dialed with the main number. Additionally, since the remote modem is resident at an analog extension, several commas “,” are added to create a delay for the phone line to transfer to that extension and then synchronize with the remote modem. A query is generated to accept the configuration and a request for the file name to store the information is then requested (without the operating system file extension). Figure 24. Initial Substation Configuration Screen Page 94 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 25. Final Substation Configuration Screen Query One must then configure the RCP program to execute the dial up sequence and configure the personal computer communication port selected. One must depress the Alternate key and “C” key simultaneously to access the “COMMUNICATE” menu shown in Figure 26. Figure 26. Communicate Menu Selections One should depress the down arrow key ““↓” once to select the settings menu to configure the port type, baud rate, and communication port selection as illustrated in Figure 27. Page 95 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 28. RCP Settings Selection Screen For this example, one must configure the RCP program for the same parameters as the PONI R card, in other words, 9600 Baud. (Selection 9 in the Bit Rate Selection Submenu) shown in Figure 29. Figure 29. Communication Baud Rate Setting Screen Execute the same procedure to access the RS232/MODEM Selection submenu. The selection for modem must be selected. By using this selection, the query for ATDT dial out command screen will be issued when issuing the connect command prompt. Figure 30 illustrates the screen presented for the RS 232/ MODEM prompt. Page 96 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 30. Modem/RS 232 Screen Prompt Selection Submenu The COM PORT Selection menu must be used to select the PC computer port though which RCP will issue commands. In the sample case, the PC used has only one com port port “1’”. The selections for the communication port parameters are shown on the bottom right hand side of the communication screen. One must now select the previously configured file for operation. Simultaneously depress the “ALT” and ”S” keys on the keypad to select the Substation Screen as illustrated in Figure 23. Highlight the “SELECT SUBSTATION” selection. The screen as shown in Figure 31 will be presented. As illustrated, the file REL350md .sub is available for selection. Depress the right arrow key “→” twice to select the file (highlighted as shown) and depress the enter key. Depress the enter key again to select the REL 350 description of the intended IED to be attached. Finally, one must initiate communications with the relay. Depress the alternate “C” keys simultaneously to view the menu as illustrated in Figure 26. Highlight the “INITIATE “ selection and depress the enter key to display the dial out query shown in Figure 32. Notice that the dial out telephone number is visible. Depress the “Y” key on the keyboard to initiate communications. One should notice a black screen as illustrated in Figure 33 which follows. Once the modem connects end to end, one will be prompted to depress the enter key to return to the main screen as shown in Figure 22. One may then proceed to the “RELAY COMMANDS” menu to query the relay for information. The modem is configured to operate the speaker (there is a volume control on the left hand side of the modem as one faces the front of the modem) until connection occurs. Figure 31. Substation File Selection Screen Page 97 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 32. Dial Out Initiation Figure 33. Modem Command Mode Screen Upon Device Connection At the conclusion of the communication session, one must remember to “hang up” the modem and disconnect the device. Depressing the Alternate key and the “C” key simultaneously will display the screen as illustrated in Figure 26. Use the down arrow “↓” to select the “HANG UP” selection. The program will issue the AT&H0 command. Example 3 – Connection of a REL 512 ASCII Front Port to Hyperterminal Software PREFACE - The REL 512 differs from the other two relays presented in EXAMPLE 2 and EXAMPLE 1 above. The communication port is a master/slave port design. The configuration port uses ASCII strings in that a dumb terminal interface is able to attach and display the device settings/metering parameters …. The REL 512 sends out (via its RD line) a time/date ASCII string every minute for display on the attached device. This fact is very critical in that the modem or device attached must be able to tolerate this string. Additionally, the REL 3XX products or the TPU/DPU 2000R, GPU 2000R or DPU 1500R communication ports are slave only in their protocol design. The port only responds to requests. The REL 512 differs in that it sends out at time string without any prompting to the attached device. Page 98 of 145 REL 512 DNP 3.0 Automation Technical Guide The REL 512 also uses a numeric character or alphabet character to move through its menus. The other devices discussed in the other examples use protocols and do not respond to the attached device strings. The REL 512 will respond to each character. As shown in this example, the attached device (in this case the modem) must be able to tolerate this operational characteristic. The REL 512 has settings capabilities configurable and viewable via its front com port (which is a DCE RS232 port) or its front panel interface. Any dumb terminal emulator is able to connect to the front port and synchronize with the unit to allow visualization of the REL 512 parameters. Within this example, two US ROBOTIC model 002806 (V.EVERYTHING modem using trellis technology encoding [which differs from the QAM encoding]). As illustrated in Figure 34, the modems are configured via a point to point connection. The REL 512 ASCII protocol is not addressable and therefore cannot be multi-dropped unless port switch devices are added to the system. The steps to establish communications are: 1. Connect the correct cable between the REL 512 front and the modem. 2. Connect the correct cable between the PC executing the HYPERTERMINAL program (in this case the operating system used is WINDOWS 95). 3. Parameterization of the REL 512 front port communication parameters. 4. Parameterization of the HYPERTERMINAL settings. 5. Parameterization of the US ROBOTICS modems using its particular AT command set. 6. Execution of the connectivity procedure to establish communications. As illustrated in Figure 34, the topology of the REL 512 interconnection with the HYPERTERMINAL software is illustrated. Please note on the diagram, the appropriate cables used to connect the device. In this example, the communication handshaking cannot be used since RTS/CTS, DCD, DSR, DTR signals are not supported on the REL 512 front communication RS 232 port. Personal Computer With An Operating System Offering a HYPERTERMINAL Utility Example Cable 6 or 7 Figures 12 or 13. 10 Bit Dial Up MODEM Example Cable 4Figure 5.. 10 Bit Dial Up MODEM Auto- Answer Enabled ABBABB ABB ABB ABB LOCAL LOCATION Public Switched Telephone Network - ANALOG LINE 19200 Baud REL512 MENU ASCII REL 512 REMOTE LOCATION Figure 34. Modem Connection Between a REL 512 Front Port and Hyperterminal Configuration Software Step 1 and Step 2: Attach the Correct Cables to the Devices Connect the cables as illustrated in Figure 34 above. Step 3: Configure the REL 512 Communication Port Configure the front port interface of the REL 512 with the correct parameters. The default configuration for the REL 512 front port interface is: 8 Data Bits No Parity Page 99 of 145 REL 512 DNP 3.0 Automation Technical Guide 2Stop Bits 9600 Baud Configure the front port with these parameters so that it may operate with a 10 bit modem as is used in this example: 8 Data Bits No Parity 1Stop Bit 19200 Baud The procedure to configure the front port interface is as follows: When connecting a device to the front port of the relay, the communication parameters for the port must be changed to reflect those of the device to which it is connecting. To change the parameters via the REL 512 front panel interface one could follow the procedure as follows: 1. From the screen of the Front Panel Interface viewing the meter readings, Depress the “E” key to get the menu E Fault Records → Device Info ← Edit Settings C Metering 2. Depress the Left Arrow Key “←” to Display the Menu E Edit Settings → Fault Records ← View Settings C Metering 3. Depress the “E” Key to display the menu E Password ******** C Edit Settings One must enter the CORRECT password to change the relay settings for this procedure. The default password for the REL 512 is “ABB” (without the quotation marks). If the password has been changed, please enter the correct password as follows • • Depress the up arrow “↑” or down arrow “↓” to page through the numeric and alphabet selections for the password. Depress the left arrow “←” or the right arrow ”→” to move through the different positions of the password. 4. Depress the “ E” key to accept the password selection you have entered. If the password is accepted the following screen shall be visible. E Password ← Accepted C Edit Settings 5. Depress the left arrow “←” key to accept the settings and proceed to the next menu which is shown E Sys Settings → Act Settings C Edit Settings 6. Depress “E” so that the System Settings may be changed. The following menu item shall be displayed: E CHG ACTIVE GRP → IDENTIFICATION C System Settings Page 100 of 145 REL 512 DNP 3.0 Automation Technical Guide 7. Depress the right arrow key “→” to display the following screen: E IDENTIFICATION → SYSTEM PARAM ← DATE & TIME C Sys Settings 8. Depress the right arrow key “→” to display the following screen: E SYSTEM PARAM → COMM PORTS ← IDENTIFICATION C Sys Settings 9. Depress the right arrow key “→” to display the following screen: E COMM PORTS → DATA RECORDING ← SYSTEM PARAMS C Sys Settings 10. Depress the “E” key to display the following screen: E FRONT PORT → REAR PORT ← MODBUS ID C COM PORTS Since this example is a guide to configuring the communication settings for the FRONT COM ASCII port, please refer to step 11 for FRONT PORT CONFIGURATION INSTRUCTIONS. 11. Depress the “E” key to display the following screen: E FRNT BIT RATE → FRNT DATA LGTH ← FRNT STOP BITS C FRONT PORT 12. Depress the “E” key to display the following screen: E ENTER System Group ← 115200 C FRNT BIT RATE By depressing the “←” left arrow key, one can view the baud rate selections for the REL 512 front port interface. The available selections are: 115200 2400 9600 19200 Select the desired baud rate by depressing the “E” key. 13. Depress the “C” key to display the following screen E FRNT BIT RATE → FRNT DATA LGTH ← FRNT STOP BITS C FRONT PORT 14. One must then select the Front panel data length depress the “→” to reveal the following screen. E FRNT DATA LNGTH → FRNT PARITY Page 101 of 145 REL 512 DNP 3.0 Automation Technical Guide ← C FRNT BIT RATE FRONT PORT 15. One must select the Front Port Data Length. Depressing the “E” key allows visualization of the following menu. E ENTER System Group ← 8 C FRNT DATA LNGTH Depressing the left arrow key “←” allows the operator to select from the following data lengths: 8 7 16. Depress “E” to accept the parameters and then depress the “C” to return to the menu: E FRNT DATA LNGTH → FRNT PARITY ← FRNT BIT RATE C FRONT PORT 17. One must set the parity by depressing the left arrow key “←” to display the following screen. E EDIT PARITY → FRNT STOP BITS ← FRNT DATA LNGTH C FRONT PORT 18. Depress “E” to display the following screen E ENTER System Group ← NONE C FRNT PARITY By depressing the left arrow key “←” the choices for parity are displayed. The choices for selection are: NONE ODD EVEN 19. Depress the “C” key to display the following screen E FRNT BIT RATE → FRNT DATA LGTH ← FRNT STOP BITS C FRONT PORT 20. Depress the left arrow key “←” to select the Front Panel Stop Bit selections. The following Screen should be visible. E ENTER System Group ← 1 C FRNT STOP BITS The selections for Stop Bits are 1 or 2. 21. Depress the “E” key to accept the selections. 22. Depress the “C” key to back out of the relay and accept the settings when prompted by the front panel interface. Page 102 of 145 REL 512 DNP 3.0 Automation Technical Guide Step 4: Configure Hyperterminal Configuration of HYPERTERMINAL requires a few easy steps. The same configuration of hyperterminal may be used for two tasks: • • Configuration of the MODEMS with the AT command sets. Dial out and query of the REL 512 MENU ASCII SCREENS for device configuration and file retrieval. The REL 512 FRONT port as illustrated in Table 1 does not offer handshaking. Therefore, setup requires that no handshaking be used for HYPERTERMINAL. HYPERTERMINAL MUST BE SET UP WITH COMMUNICATION PARAMETERS WHICH MATCH THAT OF STEP 3 ABOVE, namely: 8 Data Bits 1 Stop Bit No Parity 19200 Baud The steps to accomplish this are as follows: 1. Select HYPERTERMINAL from the WINDOWS menu to reveal the following screen illustrated in Figure 35. 2. Select the icon labeled Hyperterminal.exe The screen illustrated in Figure 36 should be visible. The operator will be prompted for a name as illustrated. Figure 35. Hyperterminal Selection Screen Page 103 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 36. Hyperterminal Setup Screen 3. Once the OK icon has been depressed, the screen for port setup will be displayed. Note that the port setup menu is illustrated for display and COM 1 selection is highlighted for this example and selection. Notice that with the MODEM selection (for the built in computer internal modem) deselected, the some of the fields are “greyed out”. 4. The COM properties for the modem must be selected for this example to those selected for the REL 512. In this case the same settings configured for the REL 512 in STEP 3 are selected for the interface. Notice that the settings are selected in Figure 37 for those configured in STEP 3. Notice for this example, hardware handshaking is enabled for RTS/CTS configuration (since HYPERTERMINAL TO MODEM CONFIGURATION IS OCCURING NOTE: REL 512 DOES NOT HAVE HANDSHAKING AND THE MODEM WILL BE CONFIGURED AS SUCH). 5. Once the OK pushbutton is depressed, a blank screen is presented to the operator. AT commands can now be typed to configure the modem with the appropriate parameters for operation in this system. Figure 37. COM Port Configuration for Attachment of Hyperterminal Session Page 104 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 38. COM Port Settings Configuration Screen The configuration process for this step is now complete. Step 5: Configuration of the Modem Parameters for the Local and Remote Sites The US ROBOTICS modems used (Model 002806- V.Everything) have commands similar to those of the previous US ROBOTIC modems. Several differences are apparent with respect to their “S” register configurations and auto configurability. Additional sessions may be set up to allow remote configuration. However, it is strongly advised that remote configuration and automation dial up capabilities not be used with the REL 512 since difficulties may result since handshaking is not available. Another word of caution should be issued in that the V.Everything modem may experience difficulties connecting with the REL 512 master/slave emulation of the port during dial-up sessions. If the MODEM is undergoing the attachment process and the REL 512 happens to send out its time ASCII string to the MODEM simultaneously, the modem will disconnect and display the prompt “NO CARRIER” at the host site. This process will take a few minutes to occur and until this occurs, no communications will occur. If a command string is sensed via the SD line (remote modem LED will illumintate) during the dialing process, the remote modem will hang up ( the remote modem OH [On Hook]) LED will extinguish. There is no way to overcome this limitation in operation with this model of modem. Some important words covering the configuration of the MODEM when used with the REL 512: • • • • DISABLE DTR (&D0) USE THE DEFAULT DISABLE OF SOFTWARE FLOW CONTROL (&I0) DSR ALWAYS ON (&S0) DISABLE CARRIER DETECT (&C0) Thus the command string should look like this: AT&D0&S0&I0&C0&W Note the &W writes the current setting to the Non-Volitile RAM. Additional tips are covered in the following tips for LOCAL modem configuration (that modem attached to the HYPERTERMINAL Personal Computer) and the REMOTE modem (that modem attached to the REL 512). Attach the cable from the PC to the modem undergoing the configuration process. It is advisable to label each modem location since the LOCAL modem will be configured slightly differently from the remote modem. Page 105 of 145 REL 512 DNP 3.0 Automation Technical Guide LOCAL MODEM Local Modem parameters are illustrated in Figure 39. To display the current list of parameters, the command string ATI4 should be typed in the HYPERTERMINAL environment . A list of the parameters used is shown. The LOCAL modem also may be configured via the dipswitches located underneath the relay. The dipswitches correspond to the AT& commands. The US ROBOTICS modem allows the modem to be programmed via dipswitches (which are read upon power up). This allows the user to program select parameters without connection to a HYPERTERMINAL screen and use of the AT command set. Dipswitch Positions are: POSITION 1 –DOWN = DTR Always ON (&D0) POSITION 2 –UP =VERBAL RESULTS CODE (V1) POSITION 3 –DOWN = DISPLAY RESULTS CODE (Q1) POSITION 4 –UP =ECHO OFFLINE COMMANDS (E1) POSITION 5 –DOWN =SUPPRESS AUTO ANSWER POSITION 6 –DOWN = CARRIER DETECT OVERRIDE (&C0) POSITION 7 –UP =DISPLAY ALL RESULTS CODE POSITION 8 –DOWN =ENABLE AT COMMAND SET POSITION 9 –UP =NO DISCONNECT WITH +++ (O0) POSITION 10 –DOWN =LOAD NVRAM DEFAULTS NOTE 1: This local modem is only configured for DIAL OUT capability – no auto answer. Additionally, all commands are echo’ed back to the terminal for easy access and troubleshooting. Upon Power UP the NVRAM defaults are loaded into memory. It is also illustrates in Figure 35 that handshaking is enabled. No other parameters have been changed from the default settings. NOTE 2: The modem has a reference key etched on the underside of the device. OFF is denoted as the down dipswitch position. ON is denoted as the DOWN dipswitch position. Figure 39. Local Modem Configuration Parameters REMOTE MODEM The configuration requirements for the remote modem vary slightly from the local modem. The configured commands in the REMOTE modem are illustrated in Figure 40. The parameters configured in your remote modem may be accessable using the command AT&I4. It is important to connect the HYPERTERMINAL program to the modem being configured as REMOTE to accomplish this. It is also advisable to label the modem as being a REMOTE device for identification purposes only. Page 106 of 145 REL 512 DNP 3.0 Automation Technical Guide The remote modem should have all its handshaking requirements turned off. Additionally, the COMMAND MODE ECHO and the ONLINE MODE ECHO must be disabled. Failure to disable these parameters will lockup the buffer of the modem and the REL 512 since the connect strings, REL 512 time ASCII strings (on a 1 minute basis) will be returned to the REL 512 for response. The important command strings to configure are: • • • • • • • • DISABLE DTR (&D0) USE THE DEFAULT DISABLE OF SOFTWARE FLOW CONTROL (&I0) DSR ALWAYS ON (&S0) ONLINE ECHO OFF (E0) ONLINE LOCAL ECHO OFF (F1) DISABLE CARRIER DETECT (&C0) DISABLE TRANSMIT FLOW CONTROL (&H0) DISABLE RECEIVED DATA RTS CONTROL (&R1) The AT command set string should look like this: AT&A0&D0&I0&S0E0F1&C0&H0&R1&W As with the previous example, the &W writes the command string to NVRAM. Since this modem is configured for AUTO ANSWER, certain “S” registers should be configured for optimal performance. In this example, sample “S “ register values are given as an example. The user should engineer appropriate values for their application: • • • ATS0=3 (3 Rings before Auto Answer) ATS41=10 ( 10 Attempts before disconnect of Auto Answer) ATS19 = 1 (1 Minute Inactivity causes hang up) The “S” register definitions are particular to this particular brand of modem. Refer to the website or CD ROM included with the modem to verify correctness. As explained previously, the command AT&W should be sent to the device to write the parameters into NVRAM. An echo of the results code does not occur in that the Q0 and E0 command was issued to the remote modem to inhibit response. Figure 40. Remote Modem Settings As described in for the local modem, the following dipswitches could be configured for power-up autoconfiguration: Page 107 of 145 REL 512 DNP 3.0 Automation Technical Guide Dipswitch Positions are: POSITION 1 –UP = DTR Always ON POSITION 2 –UP =VERBAL RESULTS CODE POSITION 3 –UP = SUPPRESS RESULTS CODE POSITION 4 –DOWN =NO ECHO OFFLINE COMMANDS POSITION 5 –UP = AUTO ANSWER ON RING POSITION 6 –DOWN = CARRIER DETECT OVERRIDE POSITION 7 –DOWN =INHIBIT DISPLAY NORMAL RESULTS CODE POSITION 8 –DOWN =ENABLE AT COMMAND SET *** (see note that follows) POSITION 9 –UP =NO DISCONNECT WITH +++ POSITION 10 –UP =LOAD NVRAM DEFAULTS ***NOTE 1– Once configuration is complete it may be advisable to place dipswitch 8 in the UP position to disable AT commands. In this way if an “AT” command string is contained within the modem upload or download file strings or ASCII command strings, the modem will not respond unpredictable or disrupt communications. NOTE 2: The modem has a reference key etched on the underside of the device. OFF is denoted as the down dipswitch position. ON is denoted as the DOWN dipswitch position. Step 6: Connection and Execution of Attachment Procedure Attach the modem to analog lines (local and remote). Use the ATDT command string to access the modem as illustrated in Figure 41 using HYPERTERMINAL. Since the command echo is not suppressed for the local modem, the example screen in Figure 41 shows the RING and CONNECT prompts returned upon successful communication. Figure 41. ATDT Sample String and Successful Connection Banner If the modem does not connect, then the REL 512 may have been sending its time string during the dial up procedure. If this is the case, redial or modify the reconnect tries in the S19 register. If the modem does connect, then depress the “/” key or Backspace key on the keyboard to reveal the REL 512 startup screen illustrated in Figure 42. To exit the session, depress the hang up icon located on the HYPERTERMINAL screen or the HANG UP submenu located on the TERMINAL screen. Also one may send the AT&H0 string for hang up. Page 108 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 42. REL 512 Configuration Menu Screen Example 4 – Connection of a REL 512 ASCII Serial Port 2 (Rear Port) to Hyperterminal Software The REL 512 has settings capabilities configurable and viewable via its rear com port (which is a DTE RS232 port). Any dumb terminal emulator is able to connect to the rear port and synchronize with the unit to allow visualization of the REL 512 parameters. Within this example, two US ROBOTIC model 002806 (V.EVERYTHING modem using trellis technology encoding [which differs from the QAM encoding]). As illustrated in Figure 43, the modems are configured via a point to point connection. The REL 512 ASCII protocol is not addressable and therefore cannot be multi-dropped unless port switch devices are added to the system. The steps to establish communications are: 1. Connect the correct cable between the REL 512 SERIAL 2 port and the modem. 2. Connect the correct cable between the PC executing the HYPERTERMINAL program (in this case the operating system used is WINDOWS 95). 3. Parameterize the REL 512 rear port communication parameters. 4. Set the jumpers internal to the relay for correct RS 232 port configuration 5. Configure and set HYPERTERMINAL settings. 6. Parameterize each US ROBOTICS modem using its particular AT command set. 7. Execute the connectivity procedure to establish communications. As illustrated in Figure 42, the topology of the REL 512 interconnection with the HYPERTERMINAL software is illustrated. Please note on the diagram, the appropriate cables used to connect the device. In this example, handshaking will be used to provide coordination between the modems. The USROBOTIC modems allow Carrier Loss Redial capability along with dial back security capability. Although these features will not be configured and examined in this rudimentary application note, the RS 232 handshaking features will be set up to its fullest capability to allow addition (and reliability in operation) of these capabilities at a later date. Page 109 of 145 REL 512 DNP 3.0 Automation Technical Guide Personal Computer With RCP Installed Example Cable 5Figures 11.. Example Cable 6 or 7 Figures 12 or 13. 10 Bit Dial Up MODEM 10 Bit Dial Up MODEM Auto- Answer Enabled Public Switched Telephone Network - ANALOG LINE 19200 Baud REL Menu ASCII Protocol REL 512 REMOTE LOCATION Figure 42. Modem Connection Between a REL 512 Serial Port 2 (Located at the Back of the Relay) and Hyperterminal Configuration Software Step 1: Construct and attach the cable as illustrated in Figure 42 above for the REL 512 / modem connection. (REMOTE LOCATION). Step 2: Construct and attach the cable as illustrated in Figure 42 above for the personal computer to modem connection. (LOCAL LOCATION). Step 3: Configure the rear port interface of the REL 512 with the correct parameters. The default parameters for all ports are 9600 baud, 8 data bits, No parity, 2 Stop bits. However, with the standard configuration, the port cannot be used with a 10 bit modem as previously explained. The Serial port 2 (located at the back side of the REL 512) must be configured following the attached procedure. Configure the font port with these parameters which are compatible for operation with a 10 bit modem: 19200 Baud 8 Data Bits No Parity 1 Stop Bit The procedure to configure the REAR port interface is as follows: When connecting a device to the front port of the relay, the communication parameters for the port must be changed to reflect those of the device to which it is connecting. To change the parameters via the REL 512 front panel interface one could follow the procedure as follows: 1. From the screen of the Front Panel Interface viewing the meter readings, Depress the “E” key to get the menu E Fault Records → Device Info ← Edit Settings C Metering 2. Depress the Left Arrow Key “←” to Display the Menu E Edit Settings → Fault Records ← View Settings Page 110 of 145 ABB ABB LOCAL LOCATION ABBABB ABB REL 512 DNP 3.0 Automation Technical Guide C Metering 3. Depress the “E” Key to display the menu E Password ******** C Edit Settings One must enter the CORRECT password to change the relay settings for this procedure. The default password for the REL 512 is “ABB” (without the quotation marks). If the password has been changed, please enter the correct password as follows: • • Depress the up arrow “↑” or down arrow “↓” to page through the numeric and alphabet selections for the password. Depress the left arrow “←” or the right arrow ”→” to move through the different positions of the password. 4. Depress the “ E” key to accept the password selection you have entered. If the password is accepted the following screen shall be visible. E Password ← Accepted C Edit Settings 5. Depress the left arrow “←” key to accept the settings and proceed to the next menu which is shown E Sys Settings → Act Settings C Edit Settings 6. Depress “E” so that the System Settings may be changed. The following menu item shall be displayed: E CHG ACTIVE GRP → IDENTIFICATION C System Settings 7. Depress the right arrow key “→” to display the following screen: E IDENTIFICATION → SYSTEM PARAM ← DATE & TIME C Sys Settings 8. Depress the right arrow key “→” to display the following screen: E SYSTEM PARAM → COMM PORTS ← IDENTIFICATION C Sys Settings 9. Depress the right arrow key “→” to display the following screen: E COMM PORTS → DATA RECORDING ← SYSTEM PARAMS C Sys Settings 10. Depress the “E” key to display the following screen: E FRONT PORT → REAR PORT ← MODBUS ID C COM PORTS Since this example is a guide to configuring the communication settings for the FRONT COM ASCII port, please refer to step 11 for FRONT PORT CONFIGURATION INSTRUCTIONS. Page 111 of 145 REL 512 DNP 3.0 Automation Technical Guide 11. Depress the “→” key to display the following screen: E REAR BIT RATE → REAR DATA LGTH ← REAR STOP BITS C REAR PORT 12. Depress the “E” key to display the following screen: E ENTER System Group ← 115200 C REAR BIT RATE By depressing the “←” left arrow key, one can view the baud rate selections for the REL 512 REAR port interface. The available selections are: 115200 2400 9600 19200 Select the desired baud rate by depressing the “E” key. 13. Depress the “C” key to display the following screen E REAR BIT RATE → REAR DATA LGTH ← REAR STOP BITS C REAR PORT 14. One must then select the Front panel data length depress the “→” to reveal the following screen. E REAR DATA LNGTH → REAR PARITY ← REAR BIT RATE C REAR PORT 15. One must select the Front Port Data Length. Depressing the “E” key allows visualization of the following menu. E ENTER System Group ← 8 C REAR DATA LNGTH Depressing the left arrow key “←” allows the operator to select from the following data lengths: 8 7 16. Depress “E” to accept the parameters and then depress the “C” to return to the menu: E REAR DATA LNGTH → REAR PARITY ← REAR BIT RATE C REAR PORT 17. One must set the parity by depressing the left arrow key “←” to display the following screen. E EDIT PARITY → REAR STOP BITS ← REAR DATA LNGTH C REAR PORT Page 112 of 145 REL 512 DNP 3.0 Automation Technical Guide 18. Depress “E” to display the following screen E ENTER System Group ← NONE C REAR PARITY By depressing the left arrow key “←” the choices for parity are displayed. The choices for selection are: NONE ODD EVEN 19. Depress the “C” key to display the following screen E REAR BIT RATE → REAR DATA LGTH ← REAR STOP BITS C REAR PORT 20. Depress the left arrow key “←” to select the REAR Panel Stop Bit selections. The following Screen should be visible. E ENTER System Group ← 1 C REAR STOP BITS The selections for Stop Bits are 1 or 2. 21. Depress the “E” key to accept the selections. 22. Depress the “C” key to back out of the relay and accept the settings when prompted by the REAR panel interface. Step 4: The REL 512 Serial Port 2 is able to be configured for RS232 or RS 485 connectivity. The configuration procedure is achieved via jumpers located near the Serial Port 2 interface on the relay. The default configuration for the relay is RS232. However one should verify jumper settings via the following procedure: 1. The technician performing this operation should be wearing anti-static wrist straps and work on an anti-static environment to ensure that static electricitiy is not conducted between the operator and REL 512 internal components. 2. Rotate the knurled screws to the left and right of the REL 512, which secure the front panel interface to the housing of the unit. The knurled screws should be turned counterclockwise (or to the left) to loosen the screws. 3. Remove the blue and red ribbon cable interconnecting the electronic signals between the front panel interface and the REL 512 motherboard. The internal assembly of the unit should be visible. 4. While grasping the internal assembly ejectors, and cantilevering the ejectors towards you, remove the internal assembly board from the chassis. 5. As illustrated, 5 jumpers are located near the rear serial port connector. The jumper locations for RS 232 and RS 485 operation are listed in Table 2. Ensure that the jumpers placed in the locations corresponding to the RS232 positions listed in the table. 6. Place the board into the REL 512 housing pressing the assembly ejectors with even force to mate the connections within the assembly with the REL 512 motherboard. 7. Carefully reattach the blue and red ribbon cable interconnecting the electronic signals between the front panel interface and the REL 512 motherboard. 8. With the front panel interface in the correct position, secure the front panel interface with the housing by tightening the knurled screws on the left and right side of the panel. The screws should be rotated clockwise (or to the right). Page 113 of 145 REL 512 DNP 3.0 Automation Technical Guide Table 2. Card Jumper Settings Jumper Pins 1,2 2,3 Mode Selection: JP1-4 RS-232 RS-485 RS-485 Configuration JP5 Half duplex Full duplex JP6 2 wire 4 wire JP7 2 wire 4 wire RS-485 Termination/Bias Resistors: JP 121 Ohms Open JP9 523 Ohms Open JP10 523 Ohms Open Step 5: The operator should configure the HYPERTERMINAL settings to match those of the configuration made for the REL 512. The procedure is as follows: 1. Select HYPERTERMINAL from the WINDOWS menu to reveal the following screen illustrated in Figure 43. 2. Select the icon labeled Hyperterminal.exe The screen illustrated in Figure 44 should be visible. The operator will be prompted for a name as illustrated. Figure 43. Hyperterminal Selection Screen Page 114 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 44. Hyperterminal Setup Screen 3. Once the OK icon has been depressed, the screen for port setup will be displayed. Note that the port setup menu is illustrated for display and COM 1 selection is highlighted for this example and selection. Notice that with the MODEM selection (for the built in computer internal modem) deselected, the some of the fields are “greyed out”. 4. The COM properties for the modem must be selected for this example to those selected for the REL 512. In this case the same settings configured for the REL 512 in Step 3 are selected for the interface. Notice that the settings are selected in Figure 45 for those configured in Step 3. Notice for this example, hardware handshaking is enabled for RTS/CTS configuration. 5. Once the OK pushbutton is depressed, the screen depicted in Figure 46 is presented to the operator. AT commands can now be typed to configure the modem with the appropriate parameters for operation in this system. Figure 45. COM Port Configuration for Attachment of Hyperterminal Session Page 115 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 46. COM Port Settings Configuration Screen Figure 47. Hyperterminal Screen for Data Communication Entry Steps 6 and 7: Configuration of the Modem Paramenters for the Local and Remote Sites THE US ROBOTICS modems used (Model 002806- V.Everything) have commands similar to those of the previous US ROBOTIC modems. Several differences are apparent with respect to their “S” register configurations and auto configurability. Additional sessions may be set up to allow remote configuration. However, it is strongly advised that remote configuration and automation dial up capabilities not be used with the REL 512 since difficulties may result since handshaking is not available. Another word of caution should be issued in that the V.Everything modem may experience difficulties connecting with the REL 512 master/slave emulation of the port during dial-up sessions. If the MODEM is undergoing the attachment process and the REL 512 happens to send out its time ASCII string to the MODEM simultaneously, the modem will disconnect and display the prompt “NO CARRIER” at the host site. This process will take a few minutes to occur and until this occurs, no communications will occur. If a command string is sensed via the SD line (remote modem LED will illumintate) during the dialing process, the remote modem will hang up (the remote modem OH [On Hook]) LED will extinguish. There is no way to overcome this limitation in operation with this model of modem. Page 116 of 145 REL 512 DNP 3.0 Automation Technical Guide Some important words covering the configuration of the MODEM when used with the REL 512: • • • • DISABLE DTR (&D0) USE THE DEFAULT DISABLE OF SOFTWARE FLOW CONTROL (&I0) DSR ALWAYS ON (&S0) DISABLE CARRIER DETECT (&C0) Thus the command string should look like this: AT&D0&S0&I0&C0&W Note the &W writes the current setting to the Non-Volatile RAM. Additional tips are covered in the following tips for LOCAL modem configuration (that modem attached to the HYPERTERMINAL Personal Computer) and the REMOTE modem (that modem attached to the REL 512). Attach the cable from the PC to the modem undergoing the configuration process. It is advisable to label each modem location since the LOCAL modem will be configured slightly differently from the remote modem. LOCAL MODEM Local Modem parameters are illustrated in Figure 48. To display the current list of parameters, the command string AT&I4 should be typed in the HYPERTERMINAL environment . A list of the parameters used is shown. The LOCAL modem also may be configured via the dipswitches located underneath the relay. Dipswitch Positions are: POSITION 1 –UP = DTR Always ON POSITION 2 –UP =VERBAL RESULTS CODE POSITION 3 –DOWN = DISPLAY RESULTS CODE POSITION 4 –UP =ECHO OFFLINE COMMANDS POSITION 5 –DOWN =SUPPRESS AUTO ANSWER POSITION 6 –DOWN = CARRIER DETECT OVERRIDE POSITION 7 –UP =DISPLAY NORMAL RESULTS CODE POSITION 8 –DOWN =ENABLE AT COMMAND SET POSITION 9 –UP =NO DISCONNECT WITH +++ POSITION 10 –UP =LOAD NVRAM DEFAULTS NOTE 1: This local modem is only configured for DIAL OUT capability – no auto answer. Additionally, all commands are echo’ed back to the terminal for easy access and troubleshooting. Upon Power UP the NVRAM defaults are loaded into memory. It is also illustrates in Figure 35 that handshaking is enabled. No other parameters have been changed from the default settings. Page 117 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 48. Local Modem Configuration Parameters REMOTE MODEM The configuration requirements for the remote modem vary slightly from the local modem. The configured commands in the REMOTE modem are illustrated in Figure 49. The parameters configured in your remote modem may be accessable using the command AT&I4. It is important to connect the HYPERTERMINAL program to the modem being configured as REMOTE to accomplish this. It is also advisable to label the modem as being a REMOTE device for identification purposes only. The remote modem should have all its handshaking requirements turned off. Additionally, the COMMAND MODE ECHO and the ONLINE MODE ECHO must be disabled. Failure to disable these parameters will lockup the buffer of the modem and the REL 512 since the connect strings, REL 512 time ASCII strings (on a 1 minute basis) will be returned to the REL 512 for response. The important command strings to configure are: • • • • • • • • • DISABLE DTR (&D0) USE THE DEFAULT DISABLE OF SOFTWARE FLOW CONTROL (&I0) DSR ALWAYS ON (&S0) ONLINE ECHO OFF (E0) ONLINE LOCAL ECHO OFF (F1) DISABLE CARRIER DETECT (&C0) DISABLE TRANSMIT FLOW CONTROL (&H0) DISABLE RECEIVED DATA RTS CONTROL (&R1) DISABLE RESULTS CODE (&A0) The AT command set string should look like this: AT&D0&I0&S0E0F1&C0&H0&R1&A0&W As with the previous example, the &W writes the command string to NVRAM. Since this modem is configured for AUTO ANSWER, certain “S” registers should be configured for optimal performance. In this example, sample “S “ register values are given as an example. The user should engineer appropriate values for their application: • • • ATS0=3 (3 Rings before Auto Answer) ATS41=10 (10 Attempts before disconnect of Auto Answer) ATS19 = 1 (1 Minute Inactivity causes hang up) Page 118 of 145 REL 512 DNP 3.0 Automation Technical Guide The “S” register definitions are particular to this particular brand of modem. Refer to the website or CD ROM included with the modem to verify correctness. As explained previously, the command AT&W should be sent to the device to write the parameters into NVRAM. Figure 49. Remote Modem Settings As described in for the local modem, the following dipswitches could be configured for power-up autoconfiguration: Dipswitch Positions are: POSITION 1 –DOWN = DTR Always ON POSITION 2 –UP =VERBAL RESULTS CODE POSITION 3 –UP = SUPPRESS RESULTS CODE POSITION 4 –DOWN =NO ECHO OFFLINE COMMANDS POSITION 5 –UP = AUTO ANSWER ON RING POSITION 6 –DOWN = CARRIER DETECT OVERRIDE POSITION 7 –DOWN =RESULTS CODE ORIGINATE MODE ONLY POSITION 8 –DOWN =ENABLE AT COMMAND SET *** (see note that follows) POSITION 9 –UP =NO DISCONNECT WITH +++ POSITION 10 –UP =LOAD NVRAM DEFAULTS ***NOTE – Once configuration is complete it may be advisable to place dipswitch 8 in the UP position to disable AT commands. In this way if an “AT” command string is contained within the modem upload or download file strings or ASCII command strings, the modem will not respond unpredictable or disrupt communications. NOTE 2: The modem has a reference key etched on the underside of the device. OFF is denoted as the down dipswitch position. ON is denoted as the DOWN dipswitch position. Step 8: Connection and Execution of Attachment Procedure Attach the modem to analog lines (local and remote). Use the ATDT command string to access the modem as illustrated in Figure 51 using HYPERTERMINAL. Since the command echo is not suppressed for the local modem, the example screen in Figure 51 shows the RING and CONNECT prompts returned upon successful communication. Page 119 of 145 REL 512 DNP 3.0 Automation Technical Guide Figure 51. ATDT Sample String and Successful Connection Banner If the modem does not connect, then the REL 512 may have been sending its time string during the dial up procedure. If this is the case, redial or modify the reconnect tries in the S19 register. If the modem does connect, then depress the “/” key or Backspace key on the keyboard to reveal the REL 512 startup screen illustrated in Figure 52. To exit the session, depress the hang up icon located on the HYPERTERMINAL screen or the HANG UP submenu located on the TERMINAL screen. Also one may send the AT&H0 string for hang up. Figure 52. REL 512 Configuration Menu Screen Conclusion In using modems, knowledge of many communication topics is required. This brief and rudimentary application note covers only a miniscule amount of information needed to successfully attach a 10 Bit Telephone Modem to an Analog Public Switch Telephone Network. Proper engineering of a communication network requires areas of investigation as: • • Protocol Modem Compatibility With The Protocol Page 120 of 145 REL 512 DNP 3.0 Automation Technical Guide • • • • • • RS 232 DTE or DCE emulation with the IED and Host Device Handshaking Requirements Modem AT Command Set Configuration S Register Configuration Modem Save Command Commands Cabling Options ABB relays have been proven to operate reliably with many manufacturer’s modems. Careful system configuration is the key to a successful project installation. It is hoped that this rudimentary application note assists the user in the task of easily and flawlessly attaching a modem to ABB products. Page 121 of 145 REL 512 DNP 3.0 Automation Technical Guide Appendix D - B & B RS 232/485 Converter Connection to ABB Protective Relays Abstract: There are many RS 232 to RS 485 converters on the market. Although ABB cannot and does not endorse a particular manufacturer of product, it does document several manufacturers’ products with their use in systems using ABB protective relays. This application note illustrates the setup and connection of B & B Models 485HSPR and 485 OISPR optically isolated RS 232 to RS485 (2-wire) physical interface converters. Typical Installation The ABB protective relay is designed with a variety of physical communication interfaces. The ABB distribution relays such as the MSOC, GPU 2000R, TPU 2000R, DPU 2000R, DPU 2000, DPU 2000 and DPU 1500R are available with an RS 232, and/or RS 485 port(s). Other devices such as the PONI M card for the REL 356 have only an RS 485 port. Many host devices only have an RS 232 port(s). A method to connect such a device is required. Several converters are available to transform the physical interface on a device from RS 232 to RS 485. The advantages of RS 485 are that many devices may be attached to a single host in a multi-drop topology. RS 485 may communicate with up to 32 devices with an addressable protocol. An advantage of the B & B model converters 485HSPR and 485 OISPR is that, like the ABB protective relay, they are isolated devices. The B & B converters listed in this document require special configuration in order to communicate with an ABB device. Since the ABB protective relay RS 232 com port does not use handshaking, external power must be supplied to the unit using both the supplied unit converter and an additional converter to assert the circuitry required for RS 232. General Information Figure 1 illustrates the packaging of the B& B converter. The B & B Converter has no visual indication of communication capability. One should use a communication analyzer to troubleshoot during commissioning of the system. Specifications for the physical interface converters are available from the B & B website at www.bbelec.com. The B & B Model 485HSPR and 485OISPR converters have two sets of dB 25 connectors. One connector is a standard RS 232 interface whereas the other connector is the RS 485/RS 422 interface. The B & B converters have a DB 25 female connector for the RS 232 physical interface. The emulation is DTE. Thus Pin 2 is Transmit Data ( Data shall be received from the device attached to the converter on that pin) and Pin 3 is Receive Data (Data is transmitted from the B & B converter to the device attached on that pin). NOTE that the DPU, TPU, GPU, MSOC are DTE RS 232 emulation’s at their port. 485 OISPR CONVERTER RS 232 INTERFACE CONSIDERATIONS The 485OISPR converter is an economical device allowing transformation of RS 232 signals to a RS 485 or RS 422 format. The RS 485/422 format may be configured via two jumpers located internally to the unit. JP 2 provides for RS 232 Transmit data control. Data sensed on Pin 2 of the converter’s RS 232 port shall place the converter in the transmit mode. The turnaround time is specified to be 1 mS. If the ABB device is a MSOC, GPU 2000R, TPU 2000R, DPU 2000R, DPU 2000, DPU 2000 or DPU 1500R, no data handshaking is permitted, thus the RS 232/485 converter must be configured for TD (Transmitted Data) mode (JP 2 inserted). Also, since no power is provided on the DTR, DSR, CD, RTS, or CTS pins from the aforementioned devices, external power must be provided on the RS 232 port at the converter end. The manufacturer recommends that a supply of +12 VDC be provided between pins 25 and 12. If the device attached to the 232 port is a personal computer or other device using the aforementioned pins (DTR [Pin 20 on a 25 pin connector or pin 4 on a 9 pin connector], DSR [Pin 6], CTS [Pin 4 on a 25 pin connector or pin 8 on a 9 pin connector], RTS [Pin 5 on a 25 pin connector or pin 7 on a 9 pin connector], It is advisable to loop them back in the cable to enable the appropriate program to operate. Page 122 of 145 REL 512 DNP 3.0 Automation Technical Guide For connection to ABB protective relays and software packages using ECP for configuration via Standard 10 Byte protocol ports, it is recommended that JP 2 be inserted for RS 232 TD mode with no data echo, and JP 4 be inserted for RS 485 2 Wire emulation Half Duplex mode. Please refer to document 485 OISPR1997 for additional information on this converter. 485 HSPR CONVERTER RS 232 INTERFACE CONSIDERATIONS The Model 485HSPR converter allows devices, which require handshaking. Jumpers JP 2, JP 3, and JP 4 may be configured for handshaking. However, as stated previously, If the ABB device is a MSOC, GPU 2000R, TPU 2000R, DPU 2000R, DPU 2000, DPU 2000 and DPU 1500R, no data handshaking is permitted, thus the RS 232/485 converter must be configured for TD (Transmitted Data) mode. However, if the device attaching to the RS 232 port is a host which utilizes RTS/CTS (Request To Send/ Clear To Send) handshaking, the unit must be configured for handshaking. For connection to ABB protective relays and software packages using ECP for configuration via Standard 10 Byte protocol ports, it is recommended that JP 1 is removed (2 Wire RS 485 mode enabled), JP 3 shall be removed while JP 2 and 4 shall be inserted. The combination of jumpers allow RS 485 4 wire control using the RS 232 Transmit Data Line to provide receiver turn-around and control. As stated previously, this is required since the aforementioned relays do not provide power through the aforementioned pins. Please refer to document 485 HSPR1896 for additional information on this converter. CONVERTER BAUD RATE CONSIDERATIONS According to the manufacturer, the standard off- the shelf configuration for the B & B converters B & B Model 485HSPR and 485OISPR will communicate to a variety of devices using various baud rates. However, the standard model uses an RC (Resistive – Capacitive) circuit controlling timeout. The standard unit is configured to operate at 9600 baud. If other baud rates are required, C9 and C 15 must be un-soldered from the circuit board and the acceptable combinations of the device must be inserted to provide for proper communication. Please refer to the appropriate B& B documentation for the correct resistor and capacitor combinations for your baud rate and application. Successful Communication There are several steps required to successfully install a communication network using a physical interface converter. They are: 1. Knowledge of the RS 232 interfaces. (What type of handshaking is employed?, Is the port DCE or DTE emulation?, Does the program executing on the attached device require certain signals such as CTS [Clear To Send], RTS [ Request To Send], CD [ Carrier Detect], DTR [Data Terminal Ready])? , What is the voltage of the RS 232 interface signals?) 2. Knowledge of the available power required. (If the converter requires external power, what is the voltage required?) 3. Knowledge of the RS 485 devices connected (2 Wire or 4 Wire?, Biasing Required?, Length of network?, Number of Devices Attached? Are the devices isolated?) 4. Proper installation of bias resistors. 5. Proper installation of termination resistors. 6. Proper selection and installation of the physical cable medium. 7. Proper configuration of the RS 232/485 physical interface switches and dipswitches. Page 123 of 145 REL 512 DNP 3.0 Automation Technical Guide TELEBYTE 245 OPTICAL ISOLATOR CONVERTER RS 232 Female Connector RS485/RS422 Male Connector The uses Pins 2 and 5 (TX/RX - or [A]) & Pins 14 and 17 (TX/RX + or [B]), Pin 7 is Ground for its connections to the Two Wire RS-485 Relay. Jumper for MODE (2 wire) RS 485 485 HSPR 485IOSPR JP1 TRANSMIT DATA CONTROL JP2 X X JP3 X X JP 4 JP2 X NA JP4 X NA RTS DATA CONTROL X = Jumper Inserted , NA = Not Applicable. Figure 1. B & B Jumper Settings RS232 Configuration and Cabling The B & B RS 232 section of the converter uses the following pins for connection to ABB protective relay devices without handshaking: Pin 2 – Transmit Data Pin 3 - Receive Data Pin 7 - Ground The RS 232 connector on the converter is a DB 25 female connector. Although the B & B 485HSPR converter does use handshaking and control of the DTR signal (Pin 20), its use is not covered in this application note. The B & B converter requires power on the unit via a DC transformer supplied with the unit. Also the B & B converter requires power on the RS 232 side. If ABB relays are used with this converter, additional +12 VDC must be supplied on pins 12 and 25 as illustrated in Figures 2 and 3. The B & B converter is designed for DTE configuration. Figures 2 and 3 illustrate cable pinouts to connect a PC or ABB to connect to a device. Cable connections are illustrated as such. If additional discussions of RS 232 are required, please consult the ABB Faxback System (610-877-0721) or the ABB website (www.abb.com/substationautomation). Several documents are available explaining RS 232 communication. The B & B converter has a DB 25 connector whereas the ABB IED’s and most personal computers have DB 9 connectors. Figures 2, 3, 4, and 5 illustrate the cable connections are handshaking is used (RTS/CTS) control or if no handshaking (data control using the Transmitted Data line) is employed. Configuration of the data control handshaking mode is performed via jumpers located at the side of the converter. Refer to Figure 1 of this document for jumper configuration. Page 124 of 145 REL 512 DNP 3.0 Automation Technical Guide Cable “A”- RS 232 Cable for Connection from a DCE NODE and the B & B converter. (*** NOTE POWER MUST BE SUPPLIED BY the DEVICES PINS 7 or 8 FOR DEVICE OPERTION OTHERWISE ADD POWER AS ILLUSTRATED). B & B Electonics Converter 3 Receive Data 2 Transmit Data 7 Ground 4 Request To Send 5 Clear To Send 25 --------- + 12 VDC *** 12 ---------- 12 VDC GROUND *** 2 3 5 7 8 DEVICE Transmit Data Receive Data Ground Request To Send Clear To Send 25 pin D shell Male Connector 9 pin D shell Female Connector Figure 2. RS 232 Cable Pinout Handshaking Incorporated (See Figure 1 for Jumper Settings According to Model. DTE to DCE Connection (9 Pin to 25 Pin RS 232 Converter Connection) Cable “A”- RS 232 Cable for Connection from a DCE NODE and the B & B converter. NO HANDSHAKING Data Control via the Transmitted Data (TD) line. B & B Electronics Converter 3 Receive Data 2 Transmit Data 7 Ground 25 ---- +12 VDC 12 ----- 12 V GROUND Additional External Supply DEVICE 2 Transmit Data 3 Receive Data 5 Ground 25 pin D shell Male Connector 9 pin D shell Female Connector Figure 3. RS 232 Cable Connections When No Handshaking is Used. See Figure 1 for Jumper Settings. DTE to DCE Connection. (9 Pin to 25 Pin RS 232 Connection) Page 125 of 145 REL 512 DNP 3.0 Automation Technical Guide Cable “A”- RS 232 Cable for Connection from a DTE NODE and the B & B converter. (*** NOTE POWER MUST BE SUPPLIED BY the DEVICES PINS 7 or 8 FOR DEVICE OPERATION OTHERWISE ADD POWER AS ILLUSTRATED). B & B Electronics Converter 3 Receive Data 2 Transmit Data 7 Ground 4 Request To Send 5 Clear To Send 25 --------- + 12 VDC *** 12 ---------- 12 VDC GROUND *** DEVICE 3 Receive Data 2 Transmit Data 5 Ground 7 Request To Send 8 Clear To Send 25 pin D shell Male Connector 9 pin D shell Female Connector Figure 4. RS 232 Cable Pinout Handshaking Incorporated (See Figure 1 for Jumper Settings According to Model. DTE to DTE Connection (9 Pin to 25 Pin RS 232 Converter Connection) Cable “A”- RS 232 Cable for Connection from a DTE NODE and the B & B converter. NO HANDSHAKING Data Control via the Transmitted Data (TD) line. B & B Electronics Converter 3 Receive Data 2 Transmit Data 7 Ground 25 ---- +12 VDC 12 ----- 12 V GROUND Additional External Supply DEVICE 3 Receive Data 2 Transmit Data 5 Ground 25 pin D shell Male Connector 9 pin D shell Female Connector Figure 5. RS 232 Cable Connections When No Handshaking is Used. See Figure 1 for Jumper Settings. DTE to DTE or connection. (9 Pin to 25 Pin RS 232 Connection). RS485 Configuration and Cabling The B & B converters covered in this note support RS 422, 4 Wire RS 485 and 2 Wire RS 485 connectivity. The ABB line of protective relays supports 2 Wire RS 485 connectivity. The jumper settings in Figure 1 are given only for the RS 485 two wire options. If additional configuration information is desired for RS 485 4 wire or RS 422 configuration please consult the manufacturer’s documentation referenced within this note. The attractive feature of the B & B converter is the isolation of the RS 232 and RS 485/422 ports from external power supplies. This feature is important especially in utility applications where external noise is an issue. RS 485 cabling is usually the source of most communication issues. Several issues must be remembered when installing such a cable: Page 126 of 145 REL 512 DNP 3.0 Automation Technical Guide 1. In attachment to ABB relays in a Utility installation, one must remember to use a cable with 3 wires and a shield. Refer to Figures 4 through 7 for ABB recommended cables. 2. Termination must be attached to the extreme ends of the cable. If ABB relays are at the extreme ends of the cable, internal termination resistors are available to provide termination. If the B & B converter is inserted at the end of the cable, insert a termination resistor of 120 ohms at that end as illustrated in the illustrations 6 through XX. 3. The cable attaching the nodes must be daisy- chained. Drops, Taps and stubs of cables are not supported. The addition of terminals, drops, taps, and cable stubs increase the signal reflections thus increasing the possibility of communication errors. 4. The CABLE SHIELD is grounded at one place only. The cable shield is continuous through all nodes, but it is isolated from the ground potential at each device. 5. The ABB protective device RS 485 ports are optically isolated, the ground wire must be attached to the shield ground at one place only. This is required to reference the field side of the device interface to a common reference. 6. The manufacturer recommends that the ground be of an impedance of 100 ohms. If it is not, solder a resistor of 100 ohms in series with the signal ground as illustrated in the B & B manufacturer’s literature. RS 485 Line Termination RS 485 2 Wire connection diagrams are referenced in Figures 6 through 9. Figures 6 and 7 use the internal resistors within the DPU, GPU, TPU and MSOC units. Figures 8 and 9 illustrate an alternate method of using external resistors to provide biasing and line termination. Topology Diagram for RS 485 Multi-drop Architecture - if jumpers are inserted on end units providing for proper termination. Cable “A” See Attached Diagram +5V Jumper J8 “IN Jumper J6 “IN” Jumper J 7 “IN” 470 Ohms TX/RX + 120 Ohms TX/RX 470 Ohms B & B Elelctronics RS 232/ RS422/485 * Note A - Following Cable Recommended Alpha # 58902 Belden # 9729, # 9829 Carol #58902 Jumper J8 “Out” TX/RX + 120 Ohms TX/RX Jumper J 7 “Out” Jumper J6 “IN” Three-wire cable with shield. Cable “B” - See Attached Diagram. * See Note A. E C E C E C E C Unit 1 End Unit Unit 2 Inline Unit Jumpers J6, J7, J8 “OUT” Unit 30 Inline Unit Unit 31 End Unit 32 Devices and 3000 Feet Maximum loading and distance. Figure 6. RS 485 2 Wire Termination With the RS 232/485 Converter INLINE and ABB Protective Relays At End Of Line Locations Page 127 of 145 REL 512 DNP 3.0 Automation Technical Guide Topology Diagram for RS 485 Multi-drop Architecture - if jumpers are inserted on end units providing for proper termination and converter is at End Unit. * Note A - Following Cable Recommended Alpha # 58902 Belden # 9729, # 9829 Carol #58902 +5V Jumper J8 “IN Jumper J6 “IN” Jumper J 7 “IN” 470 Ohms TX/RX + 120 Ohms TX/RX 470 Ohms Cable “A” See Attached Diagram Pin 2 E C 120 Ohms Three-wire cable with Pin 14 shield. Cable “B” - See Attached Diagram. B & B Electronics RS 232/ RS422/485 * See Note A. E C E C E C Unit 1 End Unit Unit 2 Inline Unit Jumpers J6, J7, J8 “OUT” Unit 30 Inline Unit Unit 31 End Unit 32 Devices and 3000 Feet Maximum loading and distance. Figure 7. Termination Using Internal Jumpers and Converter as an End Unit One should recognize that termination is at both extreme ends of the cable. Also Figures 4 and 5 have the cable daisy-chained, thus minimizing communication signal reflections. Topology Diagram for RS 485 Multi-drop Architecture - if external resistors are installed providing proper termination. NOTE: Termination at end units. Cable “A” See Attached Diagrams 120 Ohms 475 Ohms 475 Ohms * Note A - Following Cable Recommended Alpha # 58902 Belden # 9729, # 9829 Carol #58902 120 Ohms 55 56 57 58 59 60 61 ----AUX Port Three-wire cable with shield. Cable “B” - see attached diagram. 55 56 57 58 59 60 61 ----B & B Electronics RS 232/ RS422/485 AUX Port * - See note A E C E C E C E C Unit 1 End Unit Unit 2 Inline Unit Jumpers J6, J7, J8 “OUT” Unit 31 Inline Unit Unit 32 End Unit 32 Devices and 4000 Feet Maximum loading and distance. Figure 8. Termination Using External Resistors and the B & B Electronics Converter Being an “IN-LINE” Unit Page 128 of 145 REL 512 DNP 3.0 Automation Technical Guide Topology Diagram for RS 485 Multi-drop Architecture - if external resistors are installed providing proper termination. NOTE: Termination at end units. * Note A - Following Cable Recommended Alpha # 58902 Belden # 9729, # 9829 Carol #58902 120 Ohms 475 Ohms 475 Ohms 55 56 57 58 59 60 61 ----AUX Port Unit 3 Cable “A” See Attached Diagrams Pin 2 E C Three-wire cable with 120 Ohms Pin shield. Cable “B” - see attached diagram. 14 TELEBYTE 245 RS 232/ RS422/485 * - See note A E C E C E C Unit 1 End Unit Unit 2 Inline Unit Jumpers J6, J7, J8 “OUT” Unit 31 Inline Unit End Unit 32 Devices and 4000 Feet Maximum loading and distance. Figure 9. Termination Using External Resistors on the IED’s and Using the B & B Electronics Converter as an End Unit RS485 Biasing Figures 6 through 9 illustrate the addition of resistors between the TX/RX (+) line and +V, and TX/RX (-) line and ground. These resistors are called bias resistors. Bias resistors are inserted at one node only, preferably at one extreme end of the network. Note: external resistors must be added with appropriate voltages providing for termination as the diagrams illustrate. The B & B ELECTRONICS 245 is a “passive bias” unit in that when no device is communicating on the network, the data lines float. With the addition of the Pull-Up and Pull –Down resistors, the line is biased when no device is driving the lines. Biasing reduces the communication lines from being saturated with RFI or EMI induced noise from being coupled on the line. Addition of biasing on the network reduces the induced noise on the line. The typical utility installation is an electrically noisy environment. Addition of data line biasing is recommended. RS485 Conductor Connectivity The B and B converters use the following pins for RS 485 communication: PINS 2 and 5 - TX/RX (A) or TX/RX (-) or A PINS 14 and 17 - TX/RX (B) or TX/RX (+) or B PIN 7 – GROUND The B & B ELECTRONICS interface is a DB 25 MALE interface. Figures 10 and 11 illustrate the individual conductor connectivity for attaching the ABB protective relays in the DPU/TPU/2000 and the DPU/TPU/GPU 2000R. It is important to note that Figures 8 and 9 illustrate only the attachment of each device terminal. EACH NODE MUST BE DAISY-CHAINED AS ILLUSTRATED IN FIGURES 6 THROUGH 9. Page 129 of 145 REL 512 DNP 3.0 Automation Technical Guide B & B Electronics RS 232/ RS422/485 Cable “B” RS 485 Connection Shield is Frame Grounded at one point Shield is isolated *Note - Reference the Topology Drawing for Termination configuration if internal or external termination is selected. Pins Pins Pin 2 5 14 17 7 *See Note Shield Isolated 55 56 57 58 59 60 61 ----RS 485 Isolated Port 3 Shield is isolated 55 56 57 58 59 60 61 ----RS 485 Isolated Port 3 55 56 57 58 59 60 61 ----RS 485 Isolated Port 3 End Unit Inline Unit End Unit Figure 10. Conductor Connectivity Diagram for the 2000R Products and the B & B Electronics Converter “INLINE” B & B Electronics RS 232/ RS422/485 Cable “B” RS 485 Connection Shield is Frame Grounded at one point Shield is isolated *Note - Reference the Topology Drawing for Termination configuration if internal or external termination is selected. Pins Pins Pin 2 5 14 17 7 *See Note Shield Isolated 74 73 72 71 70 69 68 ----RS 485 Isolated Port 74 73 72 71 70 69 68 ----RS 485 Isolated Port Shield is isolated 74 73 72 71 70 69 68 ----RS 485 Isolated Port Figure 11. Conductor Connectivity Diagram for the DPU/TPU 2000 Products If an ABB relay uses a TYPE 8 card, COM PORT 3 is actually an RS 485 port presented in a DB 9 format. The Pin designation is presented in Table 1 and lists the cross listing for the AUX COM connector present on the 2000R product and 2000-product line. As illustrated in Figures 7 and 8, the AUX COM PORT connections are given. If one is installing RS 485 on a TYPE 8 card, both the AUX COM PORT and COM 3 have RS 485 connectivity available. Page 130 of 145 REL 512 DNP 3.0 Automation Technical Guide Table 1. RS485 Communication Card RS485 Cross-Reference List PIN DESIGNATION + 5 VDC RS485 Common RS-485 (-) RS-485 (+) COM 3 TYPE 8 COM PORT (2000R Family) 8 7 2 1 AUX COM PORT (2000R Family) 60 57 56 55 AUX COM PORT (2000 Family) 77 74 73 72 Wire attachment on an RS 485 TYPE 8 card’s COM 3 DB 9 port can be tricky in an in-line installation. ABB has a special connector, which changes the female DB 9 port into a PHOENIX contact 9-pin connector (similar in format to the AUX COM PORT). The ABB part number of this 9 Pin male to Phoenix Card Connector is ABB part 602133-009. The same part is also available from Phoenix Contact and the part number is 27 61 50 9. Troubleshooting If communication messages do not appear to be transferred from the RS 232 port to the RS 485 port, one should investigate wiring, DTE/DCE emulation switches, and the wiring on the RS 232 and RS 485 ports. If the error rate of communication message transmission and reception is high, investigate wiring in the areas of: 1. 2. 3. 4. 5. 6. 7. Biasing of the cable in only one location. Installation of termination resistors at two nodes only (at both remote ends). Cable installation with three wires AND A SHIELD. REMEMBER SHIELD IS NOT GROUND. DAISY- CHAINING the RS 485 wiring so no in-line stubs, taps, and junction strips are inserted in the unit. Incorrect installation of the Shield (connected at in line nodes and isolated at ground). Incorrect lengths of RS 485 or RS 232 cables (3000 feet = RS 485 or 50 feet = RS 232). Incorrect selection of “handshake control” for operation with the IED or Host (ABB IED’s do not employ handshaking. Some hosts require RTS/CTS handshaking or the CD and DTR signal must be looped back in the cable.) 8. Incorrect resistor selection for the baud rate used with the converterers. Please consult the B & B literature for correct C9 and R 15 component selection. 9. Power is not being supplied through the handshaking pins or the supply required for RS 232 pins 12 and 25 is absent. Review and correct this installation. In Conclusion There are many converters available on the market. Successful communication can result in using many manufacturers’ physical interface converters. Success in implementing a physical interface relies on the implementor’s knowledge of the software control of the physical interface, IED physical interface operation and knowledge of the particular brand of converter. Page 131 of 145 REL 512 DNP 3.0 Automation Technical Guide Appendix E - Telebyte RS 232/485 Converter Connection to ABB Protective Relays Abstract: There are many RS 232 to RS 485 converters on the market. Although ABB cannot and does not endorser a particular manufacturer of product, it does document several manufacturers’ products with their use in systems using ABB protective relays. This application note illustrates the setup and connection of the TELEBYTE Model 245 optically isolated RS 232 to RS485 (2-wire/4wire) physical interface converter. Typical Installation The ABB protective relay is designed with a variety of physical communication interfaces. The ABB distribution relays such as the MSOC, GPU 2000R, TPU 2000R, DPU 2000R, DPU 2000, DPU 2000 and DPU 1500R are available with an RS 232, and/or RS 485 port(s). Other devices such as the PONI M card for the REL 356 have only an RS 485 port. Many host devices only have an RS 232 port(s). A method to connect such a device is required. Several converters are available to transform the physical interface on a device from RS 232 to RS 485. The advantages of RS 485 are that many devices may be attached to a single host in a multi-drop topology. RS 485 may communicate with up to 32 devices with an addressable protocol. An advantage of the Telebyte 245 converter is that, like the ABB protective relay, it is an isolated device. General Information Figure 1 illustrates the packaging of the Telebyte converter. The Telebyte Converter has two sets of red LED’s indicating transmission and reception of information on its ports. One set of LED’s indicates transmission/reception of data on its RS 232 port. The second set of LED’s indicates transmission/reception of data on its RS 232/RS 485 port. These LED’s are invaluable in visual troubleshooting of communications. The Telebyte converter has two sets of dB 25 connectors. One connector is a standard RS 232 interface whereas the other connector is the RS 485/RS 422 interface. Switches 1 and 2 configure the RS 485 interface. A DTE/DCE (Data Terminal Emulation / Data Communication Emulation) switch configures the RS 232 pins determining where the data is expected (DTE = Data is Transmitted on Pin 2 and Data is Receive on Pin 3| DCE = Data is Transmitted on Pin 3 and Data is Received on Pin 2) on the RS 232 interface. Furthermore, Switch 2 configures the RS 485-control mode from the RS 232 port. In two-wire emulation, data control may occur from the RS 232 port’s RTS (Request To Send) line or whether the data on the TD (Transmitted Data) pin is sensed. If the ABB device is a MSOC, GPU 2000R, TPU 2000R, DPU 2000R, DPU 2000, DPU 2000 and DPU 1500R, no data handshaking is permitted, thus the RS 232/485 converter must be configured for TD (Transmitted Data) mode. However, if the device attaching to the RS 232 port is a host which utilizes RTS/CTS (Request To Send/ Clear To Send) handshaking, the unit must be configured using the RTS dipswitch settings as illustrated in Figure 1. Additional information on the TELEBYTE 245 Optically Isolated converter is available on their website at www.telebyteusa.com. There are several steps required to successfully install a communication network using a physical interface converter. They are: 1. Knowledge of the RS 232 interfaces. (What type of handshaking is employed?, Is the port DCE or DTE emulation?, Does the program executing on the attached device require certain signals such as CTS [Clear To Send], RTS [ Request To Send], CD [ Carrier Detect], DTR [Data Terminal Ready])? , What is the voltage of the RS 232 interface signals?) 2. Knowledge of the available power required. (If the converter requires external power, what is the voltage required?) 3. Knowledge of the RS 485 devices connected (2 Wire or 4 Wire?, Biasing Required?, Length of network?, Number of Devices Attached? Are the devices isolated?) 4. Proper installation of bias resistors. 5. Proper installation of termination resistors. 6. Proper selection and installation of the physical cable medium. 7. Proper configuration of the RS 232/485 physical interface switches and dipswitches. Page 132 of 145 REL 512 DNP 3.0 Automation Technical Guide TELEBYTE 245 OPTICAL ISOLATOR CONVERTER RS 232 SW 2 1 2 3 4 RS232 TD RD RS422/485 SW 1 TD RD 1 2 3 4 DTE DCE RS485/RS422 The 245 uses Pin 2 (TX/RX -) & Pin 14 (TX/RX +), Pin 7 is Ground for its connections to the Two Wire RS-485 Relay. RS 485 SWITCH MODE (2 wire) SW 1 SW 2 1 TRANSMIT DATA CONTROL RTS DATA CONTROL 2 3 UP DOWN 4 DOWN UP 1 X X 2 DOWN DOWN 3 UP UP 4 Y Y UP DOWN UP UP X = TERMINATION RESISTOR , UP = INSERTED : DOWN = OUT Y = DON’T CARE Figure 1. Telebyte Dipswitch Settings RS232 Configuration and Cabling The Telebyte RS 232 section of the converter uses the following pins: Pin 2 – Transmit Data Pin 3 - Receive Data Pin 7 - Ground The RS 232 connector on the converter is a DB 25 male connector. Depending upon the dipswitch settings, the following pins are used for transmit data control. Pin 4 – Request To Send Pin 5 – Clear To Send. Although the TELEBYTE converter does use handshaking and control of the DTR signal (Pin 20), its use is not covered in this application note. The Telebyte converter is an actively powered device requiring attachment to a supplied power transformer. This transformer supplies power to both ports on the unit. No additional power supplies are required for this converter to operate. The TELEBYTE converter has an additional dipswitch configuring the RS 232 port for DCE or DTE configuration. Figures 2 and 3 illustrate cable pinouts to connect a PC or ABB to connect to a device. If the converter is attached to a PC Host device or an ABB IED, a straight through cable may be used (or a 9 pin to 25 pin cable) to attach the devices. The DTE/DCE switch must be placed in the DCE position due to the nature of RS 232 connections. If additional discussions of RS 232 are required, please consult the ABB Faxback System (610-8770721) or the ABB websit0 (www.abb.com/substationautomation). Several documents are available explaining RS 232 communication. The TELEBYTE converter has a DB 25 connector whereas the ABB IED’s and most personal computers have DB 9 connectors. Figures 2 and 3 illustrate the cable connections are handshaking is used (RTS/CTS) control or if no handshaking (data control using the Transmitted Data line) is employed. Configuration of the data control handshaking mode is performed via the dipswitches located at the side of the converter. Refer to Figure 1 of this document for dipswitch configuration. Page 133 of 145 REL 512 DNP 3.0 Automation Technical Guide Cable “A”- RS 232 Cable for Connection from a NODE (DTE OR DCE) and the TELEBYTE converter configured correctly (DTE DEVICE AND TELEBYTE SWITCH IN DCE MODE --OR-- DCE DEVICE AND TELEBYTE SWITCH IN DTE MODE). DATA CONTROL RTS/CTS HANDSHAKING EMPLOYED. TELEBYTE 245 Converter 3 2 7 4 5 Receive Data Transmit Data Ground Request To Send Clear To Send 2 3 5 7 8 DEVICE Transmit Data Receive Data Ground Request To Send Clear To Send 25 pin D shell Female Connector 9 pin D shell Female Connector Figure 2. RS 232 Cable Pinout With Handshaking Incorporated (See Figure 1 for Dipswitch Settings Cable “A”- RS 232 Cable for Connection from a NODE (DTE OR DCE) and the TELEBYTE converter configured correctly (DTE DEVICE AND TELEBYTE SWITCH IN DCE MODE --OR-- DCE DEVICE AND TELEBYTE SWITCH IN DTE MODE). NO HANDSHAKING Data Control via the Transmitted Data (TD) line. TELEBYTE 245 Converter 3 Receive Data 2 Transmit Data 7 Ground DEVICE 2 Transmit Data 3 Receive Data 5 Ground 25 pin D shell Female Connector 9 pin D shell Female Connector Figure 3. RS 232 Cable Connections When No Handshaking is Used. See Figure 1 for Dipswitch Settings Power Requirements The TELEBYTE converter is available using a variety of power supply options. The converter is supplied with a power converter, which attaches to which attaches to the device. For current options, please consult the TELEBYTE website. RS485 Configuration and Cabling The TELEBYTE converter supports RS 422, 4 Wire RS 485 and 2 Wire RS 485 connectivity. The ABB line of protective relays supports 2 Wire RS 485 connectivity. The dipswitch settings in Figure 1 are given only for the RS 485 two wire options. If additional configuration information is desired for RS 485 4 wire or RS 422 configuration please consult the TELEBYTE website. Page 134 of 145 REL 512 DNP 3.0 Automation Technical Guide The attractive feature of the TELEBYTE converter is the isolation of the RS 232 and RS 485/422 ports from external power supplies. This feature is important especially in utility applications where external noise is an issue. RS 485 cabling is usually the source of most communication issues. Several issues must be remembered when installing such a cable: 1. In attachment to ABB relays in a Utility installation, one must remember to use a cable with 3 wires and a shield. Refer to Figures 4 through 7 for ABB recommended cables. 2. Termination must be attached to the extreme ends of the cable. If ABB relays are at the extreme ends of the cable, internal termination resistors are available to provide termination. If the TELEBYTE converter is inserted at the end of the cable, Switch Bank 2, Dipswitch position 1 inserts or removes a 120 ohm resistor in the circuit. 3. The cable attaching the nodes must be daisy- chained. Drops, Taps and stubs of cables are not supported. The addition of terminals, drops, taps, and cable stubs increase the signal reflections thus increasing the possibility of communication errors. 4. The CABLE SHIELD is grounded at one place only. The cable shield is continuous through all nodes, but it is isolated from the ground potential at each device. 5. The ABB protective device RS 485 ports are optically isolated, the ground wire must be attached to the shield ground at one place only. This is required to reference the field side of the device interface to a common reference. RS 485 Line Termination RS 485 2 Wire connection diagrams are referenced in Figures 4 through 7. Figures 4 and 5 use the internal resistors within the DPU, GPU, TPU and MSOC units. Figures 6 and 7 illustrate an alternate method of using external resistors to provide biasing and line termination. Topology Diagram for RS 485 Multi-drop Architecture - if jumpers are inserted on end units providing for proper termination. Cable “A” See Attached Diagram +5V Jumper J8 “IN Jumper J6 “IN” Jumper J 7 “IN” 470 Ohms TX/RX + 120 Ohms TX/RX 470 Ohms TELEBYTE 245 RS 232/ RS422/485 * Note A - Following Cable Recommended Alpha # 58902 Belden # 9729, # 9829 Carol #58902 Jumper J8 “Out” BANK SW 2 Dipswitch 1 = DOWN (Term Out) TX/RX + 120 Ohms TX/RX Jumper J 7 “Out” Jumper J6 “IN” Three-wire cable with shield. Cable “B” - See Attached Diagram. * See Note A. E C E C E C E C Unit 1 End Unit Unit 2 Inline Unit Jumpers J6, J7, J8 “OUT” Unit 30 Inline Unit Unit 31 End Unit 32 Devices and 3000 Feet Maximum loading and distance. Figure 4. RS 485 2 Wire Termination With the RS 232/485 Converter INLINE and ABB Protective Relays At End Of Line Locations Page 135 of 145 REL 512 DNP 3.0 Automation Technical Guide Topology Diagram for RS 485 Multi-drop Architecture - if jumpers are inserted on end units providing for proper termination and converter is at End Unit. * Note A - Following Cable Recommended Alpha # 58902 Belden # 9729, # 9829 Carol #58902 +5V Jumper J8 “IN Jumper J6 “IN” Jumper J 7 “IN” 470 Ohms TX/RX + 120 Ohms TX/RX 470 Ohms Cable “A” See Attached Diagram E C Three-wire cable with shield. Cable “B” - See Attached Diagram. BANK SW 2 Dipswitch 1 = IN (Term Resistor IN) TELEBYTE 245 RS 232/ RS422/485 * See Note A. E C E C E C Unit 1 End Unit Unit 2 Inline Unit Jumpers J6, J7, J8 “OUT” Unit 30 Inline Unit Unit 31 End Unit 32 Devices and 3000 Feet Maximum loading and distance. Figure 5. Termination Using Internal Jumpers and Converter as an End Unit One should recognize that termination is at both extreme ends of the cable. Also Figures 4 and 5 have the cable daisy-chained, thus minimizing communication signal reflections. Topology Diagram for RS 485 Multi-drop Architecture - if external resistors are installed providing proper termination. NOTE: Termination at end units. Cable “A” See Attached Diagrams 120 Ohms 475 Ohms 475 Ohms * Note A - Following Cable Recommended Alpha # 58902 Belden # 9729, # 9829 Carol #58902 120 Ohms BANK SW 2 Dipswitch 1 = DOWN (Term Out) 55 56 57 58 59 60 61 ----AUX Port 55 56 57 58 59 60 61 ----AUX Port Three-wire cable with shield. Cable “B” - see attached diagram. TELEBYTE 245 RS 232/ RS422/485 * - See note A E C E C E C E C Unit 1 End Unit Unit 2 Inline Unit Jumpers J6, J7, J8 “OUT” Unit 31 Inline Unit Unit 32 End Unit 32 Devices and 4000 Feet Maximum loading and distance. Figure 6. Termination Using External Resistors and the Telebyte Converter Being an “IN-LINE” Unit Page 136 of 145 REL 512 DNP 3.0 Automation Technical Guide Topology Diagram for RS 485 Multi-drop Architecture - if external resistors are installed providing proper termination. NOTE: Termination at end units. * Note A - Following Cable Recommended Alpha # 58902 Belden # 9729, # 9829 Carol #58902 120 Ohms 475 Ohms 475 Ohms 55 56 57 58 59 60 61 ----AUX Port Unit 3 Cable “A” See Attached Diagrams BANK SW 2 Dipswitch 1 = UP (Term IN) E C Three-wire cable with shield. Cable “B” - see attached diagram. TELEBYTE 245 RS 232/ RS422/485 * - See note A E C E C E C Unit 1 End Unit Unit 2 Inline Unit Jumpers J6, J7, J8 “OUT” Unit 31 Inline Unit End Unit 32 Devices and 4000 Feet Maximum loading and distance. Figure 7. Termination Using External Resistors on the IED’s and Using the Telebyte Converter as an End Unit RS485 Biasing Figures 4 through 7 illustrate the addition of resistors between the TX/RX (+) line and +V, and TX/RX (-) line and ground. These resistors are called bias resistors. Bias resistors are inserted at one node only, preferably at one extreme end of the network. The TELEBYTE 245 is a “passive bias” unit in that when no device is communicating on the network, the data lines float. With the addition of the Pull-Up and Pull –Down resistors, the line is biased when no device is driving the lines. Biasing reduces the communication lines from being saturated with RFI or EMI induced noise from being coupled on the line. Addition of biasing on the network reduces the induced noise on the line. The typical utility installation is an electrically noisy environment. Addition of data line biasing is recommended. RS485 Conductor Connectivity The TELEBYTE unit uses the following pins for RS 485 communication: PIN 2 - TX/RX (A) or TX/RX (-) or A PIN 14- TX/RX (B) or TX/RX (+) or B PIN 7 – GROUND The TELEBYTE interface is a DB 25 FEMALE interface. Figures 8 and 9 illustrate the individual conductor connectivity for attaching the ABB protective relays in the DPU/TPU/2000 and the DPU/TPU/GPU 2000R. It is important to note that Figures 8 and 9 illustrate only the attachment of each device terminal. EACH NODE MUST BE DAISY-CHAINED AS ILLUSTRATED IN FIGURES 4 THROUGH 7. Page 137 of 145 REL 512 DNP 3.0 Automation Technical Guide TELEBYTE 245 RS 232/ RS422/485 Cable “B” RS 485 Connection Shield is Frame Grounded at one point Shield is isolated *Note - Reference the Topology Drawing for Termination configuration if internal or external termination is selected. Pin 7 Pin Pin 2 14 *See Note Shield Isolated 55 56 57 58 59 60 61 ----RS 485 Isolated Port 3 Shield is isolated 55 56 57 58 59 60 61 ----RS 485 Isolated Port 3 55 56 57 58 59 60 61 ----RS 485 Isolated Port 3 End Unit Inline Unit End Unit Figure 8. Conductor Connectivity Diagram for the 2000R Products and the Telebyte Converter “INLINE” TELEBYTE 245 RS 232/ RS422/485 Cable “B” RS 485 Connection Shield is Frame Grounded at one point Shield is isolated *Note - Reference the Topology Drawing for Termination configuration if internal or external termination is selected. Pin 7 Pin Pin 2 14 *See Note Shield Isolated 74 73 72 71 70 69 68 ----RS 485 Isolated Port 74 73 72 71 70 69 68 ----RS 485 Isolated Port Shield is isolated 74 73 72 71 70 69 68 ----RS 485 Isolated Port Figure 9. Conductor Connectivity Diagram for the DPU/TPU 2000 Products If an ABB relay uses a TYPE 8 card, COM PORT 3 is actually an RS 485 port presented in a DB 9 format. The Pin designation is presented in Table 1 and lists the cross listing for the AUX COM connector present on the 2000R product and 2000-product line. As illustrated in Figures 7 and 8, the AUX COM PORT connections are given. If one is installing RS 485 on a TYPE 8 card, both the AUX COM PORT and COM 3 have RS 485 connectivity available. Page 138 of 145 REL 512 DNP 3.0 Automation Technical Guide Table 1. RS485 Communication Card RS485 Cross-Reference List PIN DESIGNATION + 5 VDC RS485 Common RS-485 (-) RS-485 (+) COM 3 TYPE 8 COM PORT (2000R Family) 8 7 2 1 AUX COM PORT (2000R Family) 60 57 56 55 AUX COM (2000 Family) 77 74 73 72 PORT Wire attachment on an RS 485 TYPE 8 card’s COM 3 DB 9 port can be tricky in an in-line installation. ABB has a special connector, which changes the female DB 9 port into a PHOENIX contact 9-pin connector (similar in format to the AUX COM PORT). The ABB part number of this 9 Pin male to Phoenix Card Connector is ABB part 602133-009. The same part is also available from Phoenix Contact and the part number is 27 61 50 9. Troubleshooting The TELEBYTE RS 232/RS485 converter Model Number 245 has the advantage of four LED’s present at the side of the unit (as indicated in Figure 1) indicating RS232 port transmit data, RS232 port receive data, RS 485 port transmit data and RS 485 port receive data. Visual indication of these LED’s should allow the implementor to troubleshoot a unit, which does not communicate at all. If communication messages do not appear to be transferred from the RS 232 port to the RS 485 port, one should investigate wiring, DTE/DCE emulation switches, and the wiring on the RS 232 and RS 485 ports. If the error rate of communication message transmission and reception is high, investigate wiring in the areas of: 1. 2. 3. 4. 5. 6. 7. Biasing of the cable in only one location. Installation of termination resistors at two nodes only (at both remote ends). Cable installation with three wires AND A SHIELD. REMEMBER SHIELD IS NOT GROUND. DAISY- CHAINING the RS 485 wiring so no in-line stubs, taps, and junction strips are inserted in the unit. Incorrect installation of the Shield (connected at in line nodes and isolated at ground). Incorrect lengths of RS 485 or RS 232 cables (3000 feet = RS 485 or 50 feet = RS 232). Incorrect selection of “handshake control” for operation with the IED or Host (ABB IED’s do not employ handshaking. Some hosts require RTS/CTS handshaking or the CD and DTR signal must be looped back in the cable.) In Conclusion There are many converters available on the market. Successful communication can result in using many manufacturers’ physical interface converters. Success in implementing a physical interface relies on the implementor’s knowledge of the software control of the physical interface, IED physical interface operation and knowledge of the particular brand of converter. Page 139 of 145