tcp_ip ethernet communications for pacsystems user's manual, gfk-2224k.pdf

8/10/2019 TCP_IP Ethernet Communications for PACSystems User's Manual, GFK-2224K.pdf

1/270

GEIntelligent Platforms

Programmable Control Products

TCP/IP EthernetCommunicationsfor PACSystems*

Users Manual, GFK-2224K

January 2012


2/270

GFL-002

Warnings, Cautions, and Notesas Used in this Publication

Warning

Warning notices are used in this publication to emphasize that hazardous voltages,currents, temperatures, or other conditions that could cause personal injury exist in thisequipment or may be associated with its use.

In situations where inattention could cause either personal injury or damage to equipment,a Warning notice is used.

Caution

Caution notices are used where equipment might be damaged if care is not taken.

Note: Notes merely call attention to information that is especially significant tounderstanding and operating the equipment.

This document is based on information available at the time of its publication. While effortshave been made to be accurate, the information contained herein does not purport to cover alldetails or variations in hardware or software, nor to provide for every possible contingency inconnection with installation, operation, or maintenance. Features may be described hereinwhich are not present in all hardware and software systems. GE Intelligent Platforms assumesno obligation of notice to holders of this document with respect to changes subsequently made.

GE Intelligent Platforms makes no representation or warranty, expressed, implied, or statutorywith respect to, and assumes no responsibility for the accuracy, completeness, sufficiency, orusefulness of the information contained herein. No warranties of merchantability or fitness forpurpose shall apply.

* indicates a trademark of GE Intelligent Platforms, Inc. and/or its affiliates. All othertrademarks are the property of their respective owners.

Copyright 2012 GE Intelligent Platforms, Inc.All Rights Reserved


3/270

Contact Information

iii TCP/IP Ethernet Communications for PACSystems* Users ManualJanuary 2012 GFK-2224K

If you purchased this product through an Authorized Channel Partner, please contact the seller

directly.

General Contact Information

Online technical support and

GlobalCare

http://support.ge-ip.com

Additional information http://www.ge-ip.com/

Solution Provider [email protected]

Technical Support

If you have technical problems that cannot be resolved with the information in this manual, please

contact us by telephone or email, or on the web athttp://support.ge-ip.com

Americas

Online Technical Support http://support.ge-ip.com

Phone 1-800-433-2682

International Americas Direct Dial 1-780-420-2010 (if toll free 800 option is unavailable)

Technical Support Email [email protected]

Customer Care Email [email protected]

Primary language of support English

Europe, the Middle East, and Africa


Phone +800-1-433-2682

EMEA Direct Dial +352-26-722-780 (if toll free 800 option is unavailable or if

dialing from a mobile telephone)

Technical Support Email [email protected]


Primary languages of support English, French, German, Italian, Czech, Spanish

Asia Pacific


Phone +86-400-820-8208

+86-21-3217-4826 (India, Indonesia, and Pakistan)

Technical Support Email [email protected](China)

[email protected](Japan)

[email protected](remaining Asia customers)


[email protected](China)
http://support.ge-ip.com/http://support.ge-ip.com/http://www.ge-ip.com/http://www.ge-ip.com/mailto:[email protected]:[email protected]://support.ge-ip.com/http://support.ge-ip.com/http://support.ge-ip.com/http://support.ge-ip.com/http://support.ge-ip.com/mailto:[email protected]:[email protected]:[email protected]:[email protected]://support.ge-ip.com/http://support.ge-ip.com/mailto:[email protected]:[email protected]:[email protected]:[email protected]://support.ge-ip.com/http://support.ge-ip.com/mailto:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]://support.ge-ip.com/mailto:[email protected]:[email protected]://support.ge-ip.com/mailto:[email protected]:[email protected]://support.ge-ip.com/http://support.ge-ip.com/mailto:[email protected]://www.ge-ip.com/http://support.ge-ip.com/


4/270


5/270

Contents

GFK-2224K v

Introduction .................................................................................................................... 1-1

Other PACSystems Manuals ............................................................................................1-2

Ethernet Interfaces for PACSystems Controllers .............................................................1-3

PACSystems Ethernet Interface Communications Features ............................................1-4Ethernet Redundancy Operation ....................................................................................1-10

Installation, Startup and Configuration: RX3i Embedded Interface ......................... 2-1

RX3i Embedded Ethernet Interface Indicators .................................................................2-2

Module Installation ............................................................................................................2-3

Configuring the RX3i Embedded Ethernet Interface ........................................................2-5

Diagnostics .......................................................................................................................2-8

Installation and Startup: Rack-based and RX7i Embedded Interfaces .................... 3-1

Ethernet Interface Controls and Indicators .......................................................................3-2

Module Installation ............................................................................................................3-6Ethernet Port Connectors .................................................................................................3-8

Station Manager Port ......................................................................................................3-13

Verifying Proper Power-Up of the Ethernet Interface after Configuration ......................3-14

Pinging TCP/IP Ethernet Interfaces on the Network ......................................................3-15

Ethernet Plug-in Applications ..........................................................................................3-16

Configuration: Rack-based and RX7i Embedded Interfaces ..................................... 4-1

Configuration Data ............................................................................................................4-2

Initial IP Address Assignment ...........................................................................................4-3

Configuring the Ethernet Interface ....................................................................................4-7

Configuring Ethernet Global Data ...................................................................................4-12

Ethernet Global Data ..................................................................................................... 5-1

Ethernet Global Data Operation .......................................................................................5-2

EGD Exchanges ...............................................................................................................5-3

Sending an Ethernet Global Data Exchange to Multiple Consumers ...............................5-6

Ethernet Global Data Timing ............................................................................................5-9

Timestamping of Ethernet Global Data Exchanges ........................................................5-12

Effect of PLC Modes and Actions on EGD Operations ..................................................5-23

Run Mode Store of EGD .................................................................................................5-24

Monitoring Ethernet Global Data Exchange Status ........................................................5-28

Programming EGD Commands .................................................................................... 6-1

General Use of EGD Commands .....................................................................................6-1

Using EGD Commands in a Redundancy System ...........................................................6-1

COMMREQ Format for Programming EGD Commands ..................................................6-2

COMMREQ Status for the EGD Commands ....................................................................6-3

Read PLC Memory (4000) ................................................................................................6-4


6/270

Contents

vi TCP/IP Ethernet Communications for PACSystems* Users ManualJanuary 2012 GFK-2224K

Write PLC Memory (4001) ................................................................................................6-7

Read EGD Exchange (4002) ............................................................................................6-9

Write EGD Exchange (4003) ..........................................................................................6-12

Masked Write to EGD Exchange (4004) ........................................................................6-15

Programming SRTP Channel Commands ................................................................... 7-1

SRTP Channel Commands ..............................................................................................7-2

COMMREQ Format for Programming Channel Commands ............................................7-7

Establish Read Channel (2003) ......................................................................................7-10

Establish Write Channel (2004) ......................................................................................7-14

Send Information Report (2010) .....................................................................................7-18

Abort Channel (2001) .....................................................................................................7-21

Retrieve Detailed Channel Status (2002) .......................................................................7-22

Programming for Channel Commands ...........................................................................7-24

Monitoring Channel Status .............................................................................................7-30

Differences between Series 90 and PACSystems SRTP Channels ..............................7-31

Modbus/TCP Server ...................................................................................................... 8-1

Modbus/TCP Server .........................................................................................................8-2

Reference Mapping...........................................................................................................8-3

Modbus Function Codes ...................................................................................................8-6

Modbus/TCP Client ........................................................................................................ 9-1

The Communications Request .........................................................................................9-2

COMMREQ Function Block and Command Block ...........................................................9-5

Modbus/TCP Channel Commands ...................................................................................9-8

Status Data .....................................................................................................................9-24

Controlling Communications in the Ladder Program ......................................................9-27

Differences between Series 90 and PACSystems Modbus/TCP Channels ...................9-36

RX7i PLC Monitoring Via the Web ............................................................................. 10-1

System Requirements ....................................................................................................10-1

Disabling Pop-up Blocking (Required for Newer Web Browsers) ..................................10-2

Web Server Operation in a Redundant System ............................................................. 10-3

Standard Web Pages ......................................................................................................10-4

Downloading PLC Web Pages ..................................................................................... 10-10

Viewing the RX7i PLC Web Pages ............................................................................... 10-12

Diagnostics .................................................................................................................. 11-1

What to do if You Cannot Solve the Problem .................................................................11-2

Diagnostic Tools Available for Troubleshooting .............................................................11-3

States of the Ethernet Interface ......................................................................................11-4

EOK LED Blink Codes for Hardware Failures ................................................................ 11-6

Controller Fault Table .....................................................................................................11-7


7/270

Contents

GFK-2224K Contents vii

Monitoring the Ethernet Interface Status Bits ...............................................................11-10

Monitoring the FT Output of the COMMREQ Function Block. ......................................11-12

Monitoring the COMMREQ Status Word ......................................................................11-13

Using the EGD Management Tool ................................................................................11-24Troubleshooting Common Ethernet Difficulties ............................................................11-29

Network Administration .............................................................................................. 12-1

IP Addressing ..................................................................................................................12-2

Gateways ........................................................................................................................12-4

Subnets and Supernets ..................................................................................................12-5

Configuring Advanced User Parameters ...................................................................A-1

Format of the Advanced User Parameters File ................................................................A-2

Advanced User Parameter Definitions..............................................................................A-3

AUPs Supported by RX3i CPE305/CPE310 Embedded Ethernet Interface ....................A-8


8/270


9/270

GFK-2224K 1-1

Introduction

This chapter includes basic information about Ethernet Interfaces for the PACSystems family of

controllers. It describes features of the Ethernet Interfaces in both conventional and redundancy

systems. The rest of this manual provides instructions for installing and applying the PACSystems

Ethernet Interfaces:

Chapter 2, Instal lat ion and Startup: RX3i Emb edded Interfacesdescribes user features, basic

installation procedures and configuration.

Chapter 3, Instal lat ion and Startup: Rack -based and RX7i Embedded Interfacesdescribes user

features and basic installation procedurese.

Chapter 4, Config uration: Rack -based and RX7i Emb edded Interfacesdescribes assigning a

temporary IP address, configuring the Ethernet interface, configuring Ethernet Global Data (EGD), and

setting up the RS-232 port for Local Station Manager operation.

Chapter 5, Ethernet Global Datadescribes basic EGD operation for a PACSystems Ethernet

Interface.

Chapter 6, EGD Commandsdescribes a set of commands that can be used in the application

program to read and write PLC data or Ethernet Global Data exchange data over the network.

Chapter 7, Programm ing SRTP Channel Commandsexplains how to implement PLC to PLC

communications over the Ethernet network using Service Request Transfer Protocol (SRTP) Channel

commands.

Chapter 8, Modbu s/TCP Serverdescribes the implementation of the Modbus/TCP Server feature for

the PACSystems family of products.

Chapter 9, Modbus /TCP Client explains how to program communications over the Ethernet network

using Modbus/TCPChannel commands.

Chapter 10, RX7i PLC Monitorin g Via the Webdescribes the Web browser feature provided by a

PACSystems RX7i CPU with Embedded Ethernet.

Chapter 11, Diagnost icsdescribes diagnostic techniques for a PACSystems Ethernet Interface. This

chapter also lists COMMREQ Status codes.

Chapter 12, Network Admin istrationdiscusses how devices are identified on the network and how

data is routed among devices.

Appendix A, Conf igur ing A dvanced User Parametersdescribes optional configuration of internal

operating parameters used by the Ethernet interface. For most applications, the default Advanced User

Parameters (AUPs) should not be changed.

Note: The RX3i CPE305/CPE310 embeddedEthernet interface provides a maximum of two

programmer connections. It does not support the full set of features described in this manual.

For a summary of RX3i embedded Ethernet interface features, refer to page 1-5.

Chapter

1


10/270

1-2 TCP/IP Ethernet Communications for PACSystems* January 2012 GFK-2224K

1

Other PACSystems ManualsThe manuals listed below provide more information about the PACSystems family of products.

PACSystems CPU Reference Manual, GFK-2222 PACSystems RX7i Installation Manual, GFK-2223

PACSystems RX3i System Manual, GFK-2314

PACSystems Hot Standby CPU Redundancy Users Guide,GFK-2308

TCP/IP Ethernet Communications for PACSystems Station Manager Manual,GFK-2225

PACSystems RX7i User's Guide to Integration of VME Modules, GFK-2235

C Programmers Toolkit for PACSystemsUsers Manual, GFK-2259

Proficy* Logic Developer-PLC Getting Started, GFK-1918

PACSystems RX3i Ethernet NIU User Manual, GFK-2434.

In addition to these manuals, datasheets and Important Product Information documents describe

individual modules and product revisions. The most recent PACSystems documentation is available

online on the Support website.


11/270

GFK-2224K Chapter 1 Introduction 1-3

1

Ethernet Interfaces for PACSystems ControllersA PACSystems Ethernet Interface enables a PACSystems controller to communicate with other

PACSystems equipment and with Series 90 and VersaMax controllers. The Ethernet Interface provides

TCP/IP communications with other PLCs, host computers running the Host Communications Toolkit orCIMPLICITY software, and computers running the TCP/IP version of the programming software. These

communications use the proprietary SRTP and Ethernet Global Data (EGD) protocols over a four-layer

TCP/IP (Internet) stack.

The Ethernet Interface has SRTP client/server capability. As a client the Interface can initiate

communications with other PLCs that contain Ethernet Interfaces. This is done from the PLC ladder

program using the COMMREQ function. As a server,the Ethernet Interface responds to requests from

devices such as PLC programming software, a Host computer running an SRTP application, or another

PLC acting as a client.

Network

Connection

Ethernet Cable

Host Computer or ControlDevice running a Host

Communications Toolkit

EthernetInterface

PACSystems and Series 90 PLCS

Computer RunningProgramming Software-

TCP/IP Ethernet

Ethernet

Interface

Ethernet

Interface

Network

Connection

RX3i CPE305/CPE310 Embedded Ethernet Interface

The RX3i embedded Ethernet port is available for programmer use onlyThe CPE310 provides two

SRTP-server connections for use by the programmer. Use with other SRTP enabled devices (HMI,

etc.) is not supported by the initial release.


12/270


1

PACSystems Ethernet Interface Communications FeaturesNote: The RX3i CPE305/CPE310 embedded Ethernet interface supports a subset of these features.

For a list of features provided by the RX3i embedded Ethernet, see page 1-5.

Full PLC programming and configuration services with inactivity timeout

Periodic data exchange using Ethernet Global Data (EGD)

EGD Commands to read and write PLC and EGD exchange memory over the network.

TCP/IP communication services using SRTP

SRTP Client (Channels)

Modbus/TCP Server, supporting Modbus Conformance classes 0, 1, and 2.

Modbus/TCP Client, supporting Modbus Conformance classes 0, 1, and Function Codes 15,22, 23, and 24 for Conformance class 2.

Redundant IP Addressing capability.

Basic remote PLC monitoring from a web browser (RX7i CPU Ethernet interface only)

Comprehensive station management and diagnostic tools

Extended PLC connectivity via IEEE 802.3 CSMA/CD 10Mbps and 100Mbps Ethernet LAN portconnectors.

Network switch that has Auto negotiate, Sense, Speed, and crossover detection.

Direct connection to BaseT (twisted pair) network switch, hub, or repeater without an externaltransceiver.

Protocol is stored in flash memory in the Ethernet interface and is easily upgraded through theCPU serial port.

Communications with remote PLCs and other nodes reachable through routers. The gatewayIP address must be configured.

Internet access via web pages served up to standard web browsers, for the Ethernet interfaceembedded in the PACSystems CPU.


13/270


1

RX3i CPE305/CPE310 Embedded Ethernet Interface Features

Full PLC programming and configuration services with inactivity timeout

TCP/IP communication services using SRTP. (A maximum of two SRTP-server connections foruse by the programming software.)

Comprehensive station management and diagnostic tools. For supported commands, refer tothe Station Manager Manual,GFK-2225J or later.

Extended PLC connectivity via IEEE 802.3 CSMA/CD 10Mbps and 100Mbps Ethernet LAN portconnectors.

Direct connection to BaseT (twisted pair) network switch, hub, or repeater without an externaltransceiver.


14/270


1

Ethernet Interface Specifications

All RX7i Ethernet Interface Modules and RX3i Rack-Based Ethernet Interface Modules

Ethernet processor speed 200 MHz

Connectors - Two 10BaseT / 100BaseTX Ports: 8-pin female shielded RJ-45,autosensing

- Station Manager (RS-232) Port: 9-pin female D-connector

LAN IEEE 802.2 Logical Link Control Class IIEEE 802.3 CSMA/CD Medium Access Control 10/100 Mbps

Number of IP addresses One

Embedded Ethernet Switch YesAllows daisy chaining of Ethernet nodes.

Serial Port Station Mgr Port: RS-232 DCE, 1200 - 115200 bps.

RX3i Embedded Interface Modules

Connector One 10BaseT / 100BaseTX Port: 8-pin female shielded RJ-45

LAN IEEE 802.2 Logical Link Control Class IIEEE 802.3 CSMA/CD Medium Access Control 10/100 Mbps

Number of IP addresses One

Max. no. of connections Two programmer connections

Remote Station Manager overUDP

Yes. Refer to the Station Manager Manual, GFK-2225J or later forsupported commands.

Ethernet Interface Ports

The PACSystems Ethernet interface use auto-sensing 10Base T / 100Base TX RJ-45 shielded twisted

pair Ethernet ports for connection to either a 10BaseT or 100BaseTX IEEE 802.3 network. The RX3i

embedded Ethernet interface provides one such port; all other models provide two.

The port automatically senses the speed (10Mbps or 100Mbps), duplex mode (half duplex or full

duplex) and cable (straight-through or crossover) attached to it with no intervention required.

Ethernet Media

The Ethernet Interface can operate directly on 10BaseT/100BaseTX media via its network ports.

10BaseT:10BaseT uses a twisted pair cable of up to 100 meters in length between each node and a

switch, hub, or repeater. Typical switches, hubs, or repeaters support 6 to 12 nodes connected in a star

wiring topology.

100BaseTX:100BaseTX uses a cable of up to 100 meters in length between each node and a

switch, hub, or repeater. The cable should be data grade Category 5 unshielded twisted pair (UTP) or

shielded twisted pair (STP) cable. Two pairs of wire are used, one for transmission, and the other for

collision detection and receive. Typical switches, hubs, or repeaters support 6 to 12 nodes connected in

a star wiring topology.


15/270


1

Station Manager

The built-in Station Manager function of the Ethernet Interface provides on-line supervisory access to

the Ethernet Interface, through the Station Manager port or over the Ethernet cable. Station Manager

services include:

An interactive set of commands for interrogating and controlling the station.

Unrestricted access to observe internal statistics, an exception log, and configuration parameters.

Password security for commands that change station parameters or operation.

For remote Station Manager operation over the Ethernet network, the Ethernet interface uses IP

addressing. A PACSystems Ethernet Interface cannot send or receive remote Station Manager

messages sent to a MAC address.

Refer to the PACSystems TCP/IP Ethernet Communications Station Manager Manual, GFK-2225 for

complete information on the Station Manager.

Firmware Upgrades

PACSystems Ethernet interfaces receive their firmware upgrades indirectly from the PLC CPU using

the WinLoader software utility. WinLoader is supplied with any updates to the Ethernet Interface

software. The user connects WinLoader to the PLC CPU serial port and specifies the target module by

its Rack/Slot location in the PLC.

For the CPU module, the embedded Ethernet interface firmware is upgraded along with the rest of the

CPU firmware. WinLoader seamlessly upgrades first the CPU firmware and then the embedded

Ethernet firmware without user intervention. Each Ethernet Interface modules firmware must be

explicitly upgraded by specifying the rack and slot location of the module to the WinLoader utility.

Built-In Web ServerThe embedded RX7i CPU Ethernet Interface provides Web Server capability. Each IC698 Ethernet

interface supports World Wide Web access via FTP and HTTP to allow web pages to be stored and

maintained on the Ethernet interface and served up via the web to standard web browsers. A standard

API allows you to generate customized web pages that display desired PLC data in a desired format.

You store the web pages to the Ethernet interface via FTP. A basic set of predefined web pages in

English are provided; they include a home page, Reference Table data, Controller Fault Table, and I/O

Fault Table. Rack-based Ethernet Interface modules do not provide Web Server capability.


16/270


1

SRTP Client (Channels)1

SRTP channels can be set up in the PLC application program. SRTP supports COMMREQ-driven

channel commands to establish new channels, abort existing channels, transfer data on an existing

channel, and retrieve the status of an existing channel.

The PACSystems Ethernet interface supports up to 32 simultaneous Client connections shared

between all Client protocols. For example, if 16 Client connections are used for SRTP Channels, there

are 16 Client connections available for Modbus/TCP Channels. Any given channel can be assigned to

only one protocol at a time.

SRTP Client allows the PACSystems PLC to initiate data transfer with other SRTP-capable devices on

the network.

Modbus/TCP Client (Channels)1

Modbus/TCP channels can be set up in the application program. The Modbus/TCP Client supports

COMMREQ-driven channel commands to open new channels, close existing channels, and transferdata on an existing channel.

The PACSystems Ethernet interface supports up to 32 simultaneous Client connections shared

between all Client protocols. For example, if 16 Client connections are used for SRTP Channels, there

are 16 Client connections available for Modbus/TCP Channels. Any given channel can be assigned to

only one protocol at a time.

Modbus/TCP Client allows the PACSystems PLC to initiate data transfer with other Modbus/TCP server

devices on the network.

Ethernet Global Data (EGD)1

Each PACSystems CPU supports up to 255 simultaneous Ethernet Global Data (EGD) exchanges.

EGD exchanges are configured using the programmer and stored into the PLC. Both Produced and

Consumed exchanges can be configured. PACSystems Ethernet Interfaces support both selective

consumption of EGD exchanges and EGD exchange production and consumption to the broadcast IP

address of the local subnet.

The PACSystems Ethernet interface can be configured to use SNTP to synchronize the timestamps of

produced EGD exchanges.

Beginning with PACSystems release 2.00, PACSystems Ethernet interfaces implement the capabilities

of a Class 1 and Class 2 device. COMMREQ-driven EGD Commands can be used in the application

program to read and write data into PACSystems PLCs or other EGD Class 2 devices.

PACSystems releases 5.5 and later support run mode store of EGD so that you can add, delete or

modify EGD exchanges without stopping the controller. For details on using this feature, refer to Run-Mode Store of EGD in chapter5.

1Not supported on the RX3i CPE305/CPE310 embedded Ethernet Interface.


17/270


1

SRTP Inactivity Timeout

Starting with Release 6.00, the PACSystems Ethernet interface supports inactivity checking on SRTP

server connections with any Proficy Machine Edition (PME) PLC programmer. With this feature, the

Ethernet interface removes an abandoned SRTP server connection and all of its resources when thereis no activity on the connection for a specified timeout interval. (For example, when communication with

the programmer is lost.) Until the server connection is removed, other programmers cannot switch

from Monitor to Programmer mode.

Without the SRTP inactivity timeout, an abandoned SRTP server connection persists until the

underlying TCP connection eventually times out (typically 7 minutes). All network PME programmer

connections initially use an SRTP inactivity timeout value of 30 seconds (as set by the "vconn_tout"

AUP parameter). Revision 6.00 and higher PME programmers can override the initial timeout value on

a particular server connection. Typically the PME programmer sets the SRTP inactivity timeout to 20

seconds. An inactivity timeout value of zero disables SRTP inactivity timeout checking.

The SRTP server uses an internal inactivity timeout resolution of 5 seconds. This has two effects. First,

any non-zero inactivity timeout value (either set by AUP parameter or overridden on the programmerconnection) is rounded up to the next multiple of 5 seconds. Additionally, the actual SRTP inactivity

timeout detection for any individual connection may vary up to an additional 5 seconds. The actual

inactivity detection time will never be less than the specified value.

Note: The SRTP inactivity timeout applies only to programmer connections over SRTP. It does not

affect HMI or SRTP channels.


18/270


1

Ethernet Redundancy Operation1The Redundant IP feature of the Ethernet Interface allows a single IP address called the Redundant IP

address to be assigned to two Ethernet modules. The two modules are in two different PLCs that are

configured as a redundant system.

The Redundant IP Address is configured in additionto the normal unique (direct) IP address of each

interface.

Only one of the two Ethernet interfaces that share the Redundant IP address may use the Redundant

IP address at any time; this is the active unit. When commanded by its PLC CPU, this Ethernet

interface activates the Redundant IP address and starts responding to the Redundant IP address in

addition to its direct IP address. The active unit continues responding to the Redundant IP address until

it is commanded to deactivate the Redundant IP or until the Ethernet interface determines that it has

lost communications with the PLC CPU.

The other unit (the backup unit) does not initiate communications or respond on the network using the

Redundant IP address. It can only use the Redundant IP address if it is commanded by its CPU to

become the active unit.

Both the active and backup unit may continue to use their individual direct IP addresses, permitting

programmer connection to the active or backup PLC at any time.

PLC A

PLC B

Redundant System

ProgrammerRemote host

(HMI, PLC, etc.)Redundant

IP Address

Direct IP

Addresses

The Redundant IP feature is supported by Hot Standby (HSB) CPUs and non-HSB CPUs.

HSB CPU Redundancy

An HSB system uses redundancy CPUs that provide the coordination between the PLC units in the

system and determine which is the active unit and which is the backup unit. HSB redundancy requires

dedicated links to provide communications between the units in a redundancy system. Redundancy

CPUs that include an embedded Ethernet Interface have a CRE designation, for example

IC698CRE040. For information about HSB architectures, refer to the PACSystems Hot Standby CPU

Redundancy Users Guide, GFK-2308.

1Not supported on the RX3i CPE305/CPE310 embedded Ethernet Interface.


19/270


1

Non-HSB Redundancy

Non-HSB redundancy systems use RX7i or RX3i CPUs that do not have specialized firmware for

controlling redundancy operations. (These CPUs have a CPE or CPU designation.) In these

systems, the application logic coordinates between CPUs that act as redundant partners, anddetermines which CPU is the active unit and which are backup units. The figure below illustrates the

use of the redundant IP feature in a non-HSB redundancy system. Two non-HSB CPUs (designated

primary and secondary) are linked by a communications connection. An Ethernet interface in each

controller is configured with Redundant IP enabled so that they share a Redundant IP address. As in

an HSB system, only the active Ethernet interface can communicate through the Redundant IP address

to produce EGD exchanges or to initiate Channel operations.

The application logic must monitor the status of the Ethernet modules in the system to manage the

active/backup status of each controller.

C

P

U

Primary Controller

C

P

U

Secondary Controller

Ethernet

E

T

M

E

T

M

Remote Device

L

IN

K

L

I

N

K

Basic non -HSB System w i th Redundant IP


20/270


1

Effect of Redundancy Role Switching on Ethernet Communications

When a redundancy role-switch occurs, Ethernet communications switch to the backup unit, which has

no knowledge of any communication state at the previously-active unit. The application must include

logic to detect loss of communication during a redundancy role switch and to then reinitiatecommunication.

To remote hosts on the network, the redundant system is viewed as a single PLC with high reliability;

the remote host neither knows nor cares which PLC is the active unit. By using the Redundant IP

address, the remote host always communicates with the active unit. When a redundancy role switch

occurs, the formerly-active PLC gives up ownership of the Redundant IP address and takes down all

connection-oriented communications currently using the Redundant IP address. The applications in the

redundant system and remote hosts must reestablish any such communications; the new Redundant IP

connections will use the newly active PLC.

The programmer can still communicate directly with each PLC in the redundant system (for example, to

store new logic or configuration) using the direct IP address of each Ethernet Interface.

Role Switching In HSB Redundancy Systems

In HSB redundancy systems, a role switch is initiated automatically by the redundancy CPU when the

active unit detects a fatal fault, is placed in Stop mode, or is powered off. An HSB role switch can also

be initiated manually or by the application logic. For additional information about role switches in HSB

systems, refer to the PACSystems Hot Standby CPU Redundancy Users Guide, GFK-2308.

Role Switching in Non-HSB Redundancy Systems

When redundant IP is enabled for an Ethernet module in a non-HSB CPU system, it is the responsibility

of application logic to set the redundancy mode of the Ethernet module. The Set Application

Redundancy ModeService Request (SVC_REQ 55) instruction is used to inform the Ethernet module

of the current redundancy role of the host CPU. This SVC_REQ should be used to provide redundancyrole switch notification to all Ethernet interfaces in the controller that are configured for redundant IP

operation.

After commanding a role switch for an Ethernet interface, the application logic can monitor the modules

LAN Interface Status (LIS) block to determine when it has activated the Redundancy IP address. For

details about the LIS, refer to Monitoring the Ethernet Interface Status Bits in chapter 11.

Note: The application must allow sufficient time for Redundant IP activation (at least 120 msec)

before commanding another redundancy role switch.

When an Ethernet interface recognizes that a redundant IP address has been configured for it, the

module sends a mail message to the CPU to register for redundancy role switch notification. In non-

HSB systems, the Ethernet interface is initially put into backup mode. After power up, the application

logic must use a SVC_REQ to set the redundancy state to the desired value. Once running, the CPU

remembers the last commanded redundancy role sent to that Ethernet interface. When an Ethernet

interface is restarted, the CPU automatically commands the Ethernet interface to its last redundancy

state without explicit action by the application logic.


21/270


1

Going to Stop Mode

When a non-HSB CPU goes to Stop mode, Ethernet interfaces that are configured for redundant IP are

automatically set to backup mode. When the CPU is subsequently returned to Run mode, the Ethernet

interfaces remain in backup mode until the application logic sets the redundancy mode to active.

Stop/IO Scan Enabled Mode

In this mode, I/O scanning including EGD service continues when the non-HSB CPU is stopped.

However, Ethernet interfaces configured for redundant IP operation are automatically set to backup

mode and normal EGD production for those interfaces is stopped. Only the EGD exchanges with

Produce in backup modeenabled are produced while the CPU is in Stop/IO Scan Enabled mode. To

stop production for all EGD produced exchanges including Produce in backup modeexchanges,

choose the Stop/IO Scan Disabled mode of operation.

Commanding a Role Switch in a Non-HSB Redundancy System

Use the Set Application Redundancy Mode service request (SVC_REQ 55) with non-HSB CPUs to

request that the CPU send redundancy role switch commands to all Ethernet interfaces in that PLC that

are configured for redundant IP operation. For details on using the Service Request function, refer tothe PACSystems CPU Reference Manual, GFK-2222.

This function has an input parameter block with a length of one word.

address 0=Backup redundancy role1=Active redundancy role

SVC_REQ 55 is recognized in non-HSB CPUs only. This service request sends a role switch command

to all Ethernet interfaces in the PLC that are configured for redundant IP operation. The application

must monitor the LAN Interface Status (LIS) word for each Ethernet interface to determine whether the

Redundant IP address is active at that interface.

SVC_REQ 55 has no effect on Ethernet interfaces that are not configured for redundant IP operation.


22/270


1

SRTP Server Operation in a Redundancy System

Only the active unit maintains SRTP Server connections at the Redundant IP addressand is able to

respond to SRTP requests. The backup unit does not respond to the Redundant IP address. When an

Ethernet interface changes from active to backup state, it takes down all SRTP Server connections andtheir underlying TCP connections that use the Redundant IP address.

Both the active and backup units maintain SRTP Server connections at the direct IP address for

network communication with the programmer. Other remote hosts should use the Redundant IP

address when communicating to a redundant system. Existing SRTP Server connections at the direct

IP address are not disturbed when the Ethernet interface switches between active and backup states.

SRTP Client Operation in a Redundancy System

Only the active unit establishes and maintains SRTP Client connections (channels). The backup unit

does not initiate any SRTP Client operations. If SRTP Client operations are attempted, a COMMREQ

error status is returned to the local logic program. When the Ethernet interface changes from active to

backup state, it takes down all SRTP Client connections and their underlying TCP connections.

Because it can take some time to take down a TCP connection, the redundant system should reserve a

spare SRTP Client connection for each connection using the Redundant IP address. That will prevent

temporary resource problems when establishing new SRTP Client connections to the new active unit

while the previous connections to the old active unit are being taken down.

Modbus/TCP Server Operation in a Redundancy System

Only the active unit maintains Modbus/TCP Server connections at the Redundant IP addressand is

able to respond to Modbus/TCP requests. The backup unit does not respond to the Redundant IP

address. When an Ethernet interface changes from active to backup state, it takes down all

Modbus/TCP Server connections and their underlying TCP connections that use the Redundant IP

address.

Remote hosts should use the Redundant IP address when communicating to a redundant system.

Existing Modbus/TCP Server connections at the direct IP address are not disturbed when the Ethernet

interface switches between active and backup states.

Modbus/TCP Client Operation in a Redundancy System

Only the active unit establishes and maintains Modbus/TCP Client connections (channels). The backup

unit does not initiate any Modbus/TCP Client operations. If Modbus/TCP Client operations are

attempted, a COMMREQ error status is returned to the local logic program. When the Ethernet

interface changes from active to backup state, it takes down all Modbus/TCP Client connections and

their underlying TCP connections.Because it can take some time to take down a TCP connection, the redundant system should reserve a

spare Modbus/TCP Client connection for each connection using the Redundant IP address. That will

prevent temporary resource problems when establishing new Modbus/TCP Client connections to the

new active unit while the previous connections to the old active unit are being taken down.


23/270


1

EGD Class 1 (Production & Consumption) in a Redundancy System

The active unit produces Ethernet Global Data exchanges to the network. The backup unit produces

only the EGD exchanges for which Produce in Backup Mode is enabled. When the active Ethernet

interfaces changes to backup, it stops production of all EGD exchanges.

When configured for Redundant IP operation, the active and backup Ethernet interfaces should be

configured to consume EGD exchanges via multicast host groups or the local subnet broadcast

address. This permits both the active and backup units to receive the latest data from the network.

Unicast operation is not recommended. The backup unit does not consume any unicast exchanges at

the Redundant IP address.

EGD Class 2 Commands in a Redundancy System

Remote hosts should use the Redundant IP address when communicating to a redundant system. Only

the active unit responds to EGD commands. The backup unit does not respond to the Redundant IP

address. When the active Ethernet interface changes to backup, any EGD command currently in

process over the Redundant IP address is ended.

When configured for Redundant IP operation, only the active unit sends EGD commands on the

network. If the backup unit tries to initiate any EGD commands, a COMMREQ error status is returned

to its application program. When the active Ethernet interfaces changes to backup, any EGD

commands in process are ended.

Although not recommend, EGD commands may be issued to the direct IP address. Both the active and

backup units will respond to EGD commands received at the direct IP address.

Web Server Operation in a Redundancy System

Only the active unit processes Web Server requests at the Redundant IP address and responds to web

page requests. The backup unit does not respond to the Redundant IP address. When the active

Ethernet interface changes to backup, it takes down all Web Server connections and their underlyingTCP connections. The Web Server maintains its underlying TCP connection only long enough to

process each web page request; a new TCP connection is opened, used, and closed for each

subsequent web page display or update. So unless a web page change or update is requested during

the redundancy role switch, the operation of the Redundant IP address is transparent to the Web

remote browser. Any web page request in process over the Redundant IP when a role switch occurs is

terminated.

Although not recommended, the remote browser may issue Web Server requests to the direct IP

address. Both the active and backup units respond to Web server requests received at the direct IP

address. Remote web browsers are expected to use the Redundant IP address when communicating

to a redundant system.

FTP Operation in a Redundancy System

FTP operations are used to transfer setup and configuration data to the Ethernet interface, not for

communication with the actual PLC application. Therefore, FTP operations should only be performed

using the direct IP address.


24/270


1

SNTP Operation in a Redundancy System

A PACSystems Ethernet Interface can operate as an SNTP client only, so it only receives broadcast

time messages from an SNTP Server on the network. SNTP operation is unaffected by the current

Ethernet redundancy state or by redundancy role switches.

Remote Station Manager Operation in a Redundancy System

The remote Station Manager should respond to the direct IP address regardless of whether the unit is

active or backup, or whether or not Redundant IP is configured.

Only the active unit responds to remote Station Manager commands at the Redundant IP address. The

backup unit does not respond to the Redundant IP address. (Station Manager responses from the

Redundant IP address can be misleading because it is difficult to determine which Ethernet interface is

actually responding.)

IP Address Configuration in a Redundancy System

Redundancy systems should explicitly configure both the direct IP address and the Redundant IPaddress. Do not set up the direct IP address via BOOTP.

The Redundant IP address must be configured on the same local sub-network as the direct IP address

and gateway IP address (if used).


25/270


26/270


2

RX3i Embedded Ethernet Interface IndicatorsThe Ethernet port has two LED indicators, 100and LINK. The 100LED indicates the network data

speed (10 or 100 Mb/sec). This LED is lit if the network connection at that network port is 100 Mbps.

The LINKLED indicates the network link status and activity. This LED is lit when the link is physically

connected. It blinks when traffic is detected at that network port.

Ethernet Port LEDs Operation

LED LED State

On Blinking Off CPU Operating State

100 On, Green Network data speed is 100 Mbps.

Off Network data speed is 10 Mbps.

LINK On, Green The link is physically connected.

Blinking green Traffic is detected at the port.


27/270

GFK-2224K Chapter 2 Installation, Startup and Configuration: RX3i Embedded Interface 2-3

2

Module InstallationFor general information about CPU module and system installation refer to thePACSystems RX3i

System Manual, GFK-2314.

Connection to a 10Base-T / 100Base Tx Network

The RX3i CPE305 and CPE310 CPUs provide a

10BaseT/100BaseTX Ethernet network port connector.

Note: When a CPE310 is configured as a CPU310, Ethernet properties cannot be configured and

there should be no cable connected to the Ethernet port.

Either shielded or unshielded twisted pair cable may be attached to a port. The 10Base-T/100Base Txtwisted pair cable must meet the applicable IEEE 802 standards. Category 5 cable is required for

100BaseTX operation.

The Ethernet port automatically senses whether it is connected to a 10BaseT or 100BaseTX network,

half duplex or full duplex. (The automatic negotiation of speed and/or duplex mode can be explicitly

overridden using Advanced User Parameter settings).

10Base-T/100Base Tx Port Pinouts

Pin Number Signal Descr ipt ion

1* TD+ Transmit Data +

2 TD Transmit Data

3 RD+ Receive Data +

4 NC No connection

5 NC No connection

6 RD Receive Data

7 NC No connection

8 NC No connection

* Pin 1 is at the bottom of the Ethernet port connector

as viewed from the front of the module.

Note: Pin assignments are provided for troubleshooting purposes only. 10Base-T/100Base-Tx cables

are readily available from commercial distributors. We recommend purchasing rather thanmaking 10Base-T/100Base-Tx cables.

ETHERNE


28/270


2

The programmer is connected to the Ethernet Interface through a 10Base-T or 100Base-Tx network.

10BaseT/100Base Tx Twisted Pair Cable

Hub/Switch/Repeater

To other network devices

Ethernet Porton RX3iCPE305/CPE310

Programmer


29/270


2

Configuring the RX3i Embedded Ethernet InterfaceBefore you can use the Ethernet Interface, you must configure it using Proficy Machine Edition Logic

Developer-PLC software (PME).

1. Using Proficy Machine Edition (PME) software, configure the CPE3xx CPU in an RX3i target and

assign a new IP address to the embedded Ethernet interface:

To configure the embedded Ethernet interface, expand the CPU slot

to display the Ethernet interface. Right click the Ethernet interface to

display its parameters: IP Address, Subnet Mask and Gateway IP

Address. Consult your network administrator for the proper values for these parameters.

Note: The initial releases of these CPUs do no tsupport the alternate methods of setting a

temporary IP address: the Set Temporary IP Address tool in PME, BOOTP or the Station

Manager CHSOSW command.

2. Go online with the target and download the configuration. You can use one of the following

methods for the initial connection to the CPE3xx: Through the embedded Ethernet port, using the factory-loaded default IP address. This

address is intended only for initial connection in order to complete the configuration and must

be changed before connecting to the Ethernet network. (To set the IP address PME will use to

connect to the RX3i, open the target properties and set Physical Port to ETHERNET.)

Through the Ethernet connection of an ETM001 in the same rack with a known IP address

configuration.

Through the RS-232 COM1 serial portThis is a DCE (data communications equipment) port

that allows a simple straight-through cable to connect with a standard nine-pin AT-style RS-232

port.

CPE310:Through the RS-485 COM2 serial portUse SNP programming cable IC690ACC901


30/270


31/270


2

Terminals Tab

This configuration tab is displayed only when the Ethernet interfaces Variable Mode property is set to

True. When Variable Mode is selected, the Ethernet Status bits are referenced as I/O variables that are

mapped to the Ethernet status bits on this configuration tab.

The use of I/O variables allows you to configure the Ethernet interface without having to specify the

reference addresses to use for the status information. Instead, you can directly associate variable

names with the status bits. For more information, refer to I/O Variables in the PACSystems CPU

Reference Manual, GFK-2222.

Pinging TCP/IP Ethernet Interfaces on the Network

PING (Packet InterNet Grouper) is the name of a program used on TCP/IP networks to test reachability

of destinations by sending them an ICMP echo request message and waiting for a reply. Most nodes

on TCP/IP networks, including the PACSystems Ethernet Interface, implement a PING command.

You should ping each installed Ethernet Interface. When the Ethernet Interface responds to the ping,itverifies that the interface is operational and configured properly. Specifically it verifies that acceptable

TCP/IP configuration information has been downloaded to the Interface.

Pinging the Ethernet Interface from a UNIX Host or Computer Running TCP/IP Software

Apingcommand can be executed from a UNIX host or computer running TCP/IP (most TCP/IP

communications software provides apingcommand) or from another Ethernet Interface. When using a

computer or UNIX host, you can refer to the documentation for thepingcommand, but in general all

that is required is the IP address of the remote host as a parameter to thepingcommand. For example,

at the command prompt type:

ping 10.0.0.1

Determining if an IP Address is Already Being Used

Note: This method does not guarantee that an IP address is not duplicated. It will not detect a device

that is configured with the same IP address if it is temporarily off the network.

It is very important not to duplicate IP addresses. To determine if another node on the network is using

the same IP address:

1. Disconnect your Ethernet Interface from the LAN.

2. Ping the disconnected Interfaces IP address. If you get an answer to the ping, the chosen IP

address is already in use by another node. You mustcorrect this situation by assigning a unique IP

addresses.


32/270


2

DiagnosticsThere are several tools to assist you in diagnosing problems with the Ethernet Interface and the

network.

Use the Ethernet Interface LEDsto troubleshoot a problem on power-up of the EthernetInterface and for an immediate visual summary of the operational state of the Interface.

Use the Controller Fault Table to troubleshoot a problem once the Interface is running. Itprovides a record of exceptions logged by the PLC, the Ethernet Interface, and other I/O and

communications modules. The Controller Fault Table is accessed through the programming

software.

For Controller Fault Table entries generated by the Ethernet Interface, the Detailed Fault Datafor that entry contains the same data as the corresponding event in the Ethernet Interfaces

exception log. Refer to GFK-2225, TCP/IP Ethernet Communications for the PACSystems

Station Manager Manual,for information on how to interpret Ethernet exception log events.

Use the Ethernet Status Data to troubleshoot the Ethernet Interface status

Use the Station Manager to troubleshoot a problem with the Ethernet Interface, the network,backplane communication, or with your application. The LOG, TALLY, and STAT Station

Manager commands are especially useful.

- The LOG command provides a complete record of exceptions occurring with the network

and Interface.

- The TALLY command provides statistics about operation and performance of the network

and Interface. The RX3i embedded Ethernet interface supports the C, I, J, L, U, V, and W

tasks.

- The STAT command provides the current status of specific components of the Ethernet

interface. The RX3i embedded Ethernet interface supports the B, C, I, L, U, V and W tasks.

Refer to the TCP/IP Ethernet Communications for PACSystems Station Manager Manual,

GFK-2225, for information on how to access and use the Station Manager software.


33/270


2

Monitoring the Ethernet Interface Status Bits

The Ethernet Interface status bits occupy a single block of either reference memory, or I/O variables.

The access type and location of the Ethernet Interface Status bits is specified during configuration of

the Ethernet Interface. The Ethernet Status bits are updated in the CPU once each PLC scan by theEthernet Interface.

The first 16 bits of the block are the LAN Interface Status (LIS) bits. Unless the LAN Interface OK bit

is set (Status Bit 16), the other status bits are invalid.

Status Bi ts Br ie f Descr ip t ion

1 Full duplex

2 100Mbps

312 Reserved

13 LAN OK

14 Resource problemsee Controller Fault Table

16 LAN Interface OK

1780 Reserved

LAN Interface Status (LIS) Bits

The LAN Interface Status bits monitor the health of the Ethernet Interface.

Bit 1, Full Duplex:This bit is set to 1 when the port is set to full duplex. Full-duplex or half-duplex

operation is automatically negotiated between the Ethernet Interface and its immediately-connected

network device, usually a network hub or switch. If this bit is 0, the port is in half-duplex Ethernet mode.

This bit is only valid if bit 13 (LAN OK) is 1.

Bit 2, 100Mbps:This bit is set to 1 when the port is operating at 100Mbps.

Bit 13, LAN OK:This bit is 1 as long as the Ethernet Interface software is able to communicate on the

network. If the network becomes inaccessible due to local or network problems, this bit is set to 0. If

LAN communication becomes possible again, it is set to 1.

Bit 14, Resource Problem: This bit is set to 1 if the Ethernet Interface software has a resource

problem (i.e., lack of data memory). The bit is reset to 0 on a subsequent PLC sweep. The Ethernet

Interface may or may not be able to continue functioning, depending on the severity of the problem.

Look in the Controller Fault Table for details. In addition, the Station Manager STAT B and LOG

commands can be used. See the Station Manager Manual, GFK-2225, for more information.

Bit 16, LAN Interface OK Bit:This bit is set to 1 by the Ethernet Interface each PLC scan. If the

Ethernet Interface cannot access the PLC, the CPU sets this bit to 0. When this bit is 0, all other

Ethernet Interface Status bits are invalid.


34/270


35/270

GFK-2224K 3-1

Installation and Startup: Rack-based and RX7iEmbedded Interfaces

This chapter describes the Ethernet Interfaces user features and basic installation procedures.

Ethernet Interface Controls and Indicators

- Ethernet LEDs

- Ethernet Restart Pushbutton

Module Installation

RX7i CPU with Embedded Ethernet Interface

Rack-based Ethernet Interface Modules

Ethernet Port Connectors

Embedded Switch

Connection to a 10Base T / 100Base Tx Network

Station Manager Port

Verifying Proper Power-Up of the Ethernet Interface After Configuration

Pinging TCP/IP Ethernet Interfaces on the Network

Features of the embedded RX7i CPU Ethernet Interface and the rack-based RX3i/RX7i Ethernet

interfaces are the same unless noted otherwise.

Note: For features, installation and startup of the RX3i embedded Ethernet interface, see chapter 2.

Chapter

3


36/270


3

Ethernet Interface Controls and IndicatorsFeatures of the RX7i embedded CPU Ethernet Interface and the RX7i and RX3i

rack-based Ethernet Interface modules are the same unless noted otherwise.

The Ethernet Interface provides:

1. Seven light emitting diode (LED) indicators

Ethernet Module OK (EOK)

LAN Online (LAN)

Status (STAT)

Two Ethernet network activity LEDS (LINK)

Two Ethernet network speed LEDS (100)

2. Ethernet Restart Pushbutton

3. Two 10BaseT/100BaseTX Ethernet network port connectors. There is only one

interface to the network (only one Ethernet address and only one IP address).

4. Station Manager (RS-232) serial port

ETHERNETRESTART

EOK

LAN

STAT

10/100ENET

A2

100LINK

StaMgr

10/

100ENET

A1

100

LINK


37/270


38/270


3

STAT LED Operation

The STAT LED (LOG EMPTY on the RX3i Ethernet module) indicates the condition of the Ethernet

interface in normal operational mode. If the STAT LED is off, an event has been entered into the

exception log and is available for viewing via the Station Manager interface. The STAT LED is onduring normal operation when no events are logged.

In the other states, the STAT LED is either off or blinking and helps define the operational state of the

module.

EOK LED Operation

The EOK LED (ETHERNET OK on the RX3i Ethernet module) indicates whether the module is able to

perform normal operation. This LED is on for normal operation and flashing for all other operations.

When a hardware or unrecoverable runtime failure occurs, the EOK LED blinks a two-digit error code

identifying the failure. For a list of blink codes and their meanings, see chapter 11.

Ethernet Port LEDs Operation (100Mb and Link/Activity)Each of the two Ethernet ports (Ports 1A and 1B) has two LED indicators, 100and LINK. The 100LED

indicates the network data speed (10 or 100 Mb/sec). This LED is lit if the network connection at that

network port is 100 Mbps.

The LINKLED indicates the network link status and activity. This LED is lit when the link is physically

connected. It blinks when traffic is detected at that network port. Traffic at the port does not necessarily

mean that traffic is present at the Ethernet interface, since the traffic may be going between ports of the

switch.


39/270

GFK-2224K Chapter 3 Installation and Startup: Rack-based and RX7i Embedded Interfaces 3-5

3

Ethernet Restart Pushbutton

The Ethernet Restart pushbutton is used to manually restart the Ethernet firmware without power

cycling the entire system. It is recessed to prevent accidental operation.

Restart Pushbutton Operation for Version 3.6 and Later

For PACSystems Ethernet interfaces version 3.6 and later, an Ethernet restart occurs when the Restart

pushbutton is released. The duration that the Restart pushbutton is pressed determines the operation

after the restart occurs. In all cases, the EOK, LAN and STAT LEDs briefly turn on in unison as an LED

test. The Ethernet port LEDs are not affected by a manual restart of the Ethernet firmware.

To restart the Ethernet interface normally, press the Ethernet Restart pushbutton for less than 5

seconds.

If the Ethernet interface uses any optional Ethernet plug-in applications, these applications are

ordinarily started upon each powerup or restart. To restart the Ethernet interface without starting any

Ethernet plug-in applications, press and hold the Ethernet Restart pushbutton between 5 and 10

seconds.

To restart the Ethernet interface into firmware update operation, press and hold the Ethernet Restart

pushbutton for more than 10 seconds. This is typically done during troubleshooting to bypass possibly

invalid firmware and allow valid firmware to be loaded using WinLoader.

Pushbutton-controlled restart operations are listed below, with the LED indications for each.

Restart Operation Depress Ethernet

Restar t pushbu tton for

Ethernet LEDs

Il luminated

Restart the Ethernet interface normally, and startany optional Ethernet plug-in applications that arebeing used.

Less than 5 seconds EOK, LAN,STAT

Restart the Ethernet interface without starting anyEthernet plug-in applications.

5 to 10 seconds LAN, STAT

Restart the Ethernet interface into firmware updateoperation.

More than 10 seconds STAT

When forced into firmware update operation, but before the firmware update actually begins, pressing

the Ethernet Restart pushbutton again exits the firmware update mode and restarts with the existing

firmware. Once the firmware update actually begins, the existing firmware is erased and the Ethernet

Restart pushbutton is disabled until the firmware update is complete.

Restart Pushbutton Operation Prior to Version 3.6

For PACSystems Ethernet interfaces earlier than version 3.6, pressing the Ethernet Restart pushbutton

restarts the module immediately. The EOK, LAN and STAT LEDs briefly turn on in unison as an LEDtest. These three LEDs are turned on for second and are then turned off when the firmware is

restarted. The Ethernet port LEDs are not affected by a manual restart of the Ethernet firmware.


40/270


3

Module InstallationFor general information about module and system installation, or if the installation requires CE Mark

compliance, refer to thePACSystems RX7i Hardware Installation Manual,GFK-2223 or the

PACSystems RX3i System Manual, GFK-2314.

Installing an RX7i CPU with Embedded Ethernet Interface

Warning

Do not insert or remove modules with power applied. This could cause the CPUto Stop, damage the module, or result in personal injury.

1. Record the 12-digit hexadecimal MAC Address from the printed label located on the rear wall of

CPU battery compartment. The label is visible when the battery is removed from its compartment.

(The battery does not need to be disconnected to

temporarily remove it from the compartment.)

2. Connect the battery to either of the battery

connectors on the module.

3. Put the toggle switch in the STOP position.

4. Make sure that rack power is off.

5. Install the CPU module in slot 1 of rack 0. Press

the module firmly in place, but do not force the

board. Tighten the screws on the top and bottom

tabs.

6. Connect one or bothof the Ethernet ports on the

Ethernet Interface to the network.

7. Turn on power to the PACSystems rack.

8. Set the PLC to Stop mode via the Run/Stop

switch or the programming software.

Battery

Compartment

Three-cell

Battery Pack

MAC Labellocated on rear wall ofbattery compartment


41/270


3

Installing an RX7i Ethernet Interface Module

1. Record the 12-digit hexadecimal MAC Address from the

printed label on the Ethernet Interface. The label is

visible only with module out of the rack.

2. Be sure the rack power is OFF.

3. Slide the module into the slot for which it was configured

in the system. (Must go into main rack.)

4. Press the module firmly in place, but do not force the

module. Tighten the screws on the top and bottom tabs.

5. Connect one or both of the network ports on the

Ethernet Interface to the Ethernet network.

6. Turn on power to the PACSystems rack.

7. Set the PLC to Stop mode via the Run/Stop switch orthe programming software.

Installing an RX3i Ethernet Interface Module

1. Record the 12-digit hexadecimal MAC Address from the printed

label located on the front of the Ethernet Module.

2. PLC rack power may be off or on (hot insertion). For hot

insertion, be sure that all cables are disconnected from the

Ethernet module

3. Slide the module into the slot for which it was configured in the

system. (Must go into main rack.)

4. Press the module firmly in place, but do not force.

5. Connect one or both of the network ports on the Ethernet

Interface to the Ethernet network.

6. Unless this is a hot insertion, turn on power to the PACSystems

rack.

7. Set the PLC to Stop mode via the Run/Stop switch or the

programming software.

MAC Address

Label


42/270


3

Ethernet Port ConnectorsThe Ethernet Interface has two Ethernet port connectors, each of which supports both 10Base-T and

100Base-Tx operation using either full duplex or half duplex operation. These 8-pin RJ-45 connectors

are used to connect the Ethernet Interface to a hub, repeater, switch, or other Ethernet device.

Embedded Switch

The two Ethernet port connectors are controlled by an embedded network switch in the module. The

module has only one interface to the network (one Ethernet address and one IP address).

PACSystemsEthernet Interface

Ethernet

Processor

Ethernet

MAC

10/100 Network

Switch

Port 1A Port 1B

For simple installations, the embedded switch allows devices to be connected without additional

components.

Operator

Interface

PLC PLC Personal

Computer

It is possible to daisy-chain PLCs together without additional components, but that should be done with

great care. Power loss or reset at an Ethernet interface causes loss of communication to any devices

downstream from that Ethernet interface in the daisy chain. Restarting the Ethernet interface (via the

Ethernet Restart pushbutton, for example) disrupts daisy chain communication.Each switch port auto-negotiates (by default) to the correct link speed and duplex mode for the device

connected to the other end of the link. Each port operates independently, so devices at two different

speeds and/or duplex modes may be attached to the two ports. Each port also automatically detects

the attached cable and will work properly with either straight-through or crossover cables (by default).


43/270


3

Caution

The two Ethernet ports on the Ethernet Interface must not be connected, directly orindirectly, to the same device. The connections in an Ethernet network based on twistedpair cabling must form a tree and not a ring, otherwise duplication of packets and network

overload may occur.

Caution

The IEEE 802.3 standard strongly discourages the manual configuration of duplex modefor a port (as would be possible using Advanced User Parameters). Before manuallyconfiguring duplex mode for an Ethernet Interface port using advanced user parameters(AUP), be sure that you know the characteristics of the link partner and are aware of theconsequences of your selection. Setting both the speed and duplex AUPs on an IC698Ethernet Interface port will disable the ports auto-negotiation function. If its link partneris not similarly manually configured, this can result in the link partner concluding anincorrect duplex mode. In the words of the IEEE standard: Connecting incompatibleDTE/MAU combinations such as full duplex mode DTE to a half duplex mode MAU, or a

full-duplex station (DTE or MAU) to a repeater or other half duplex network, can lead tosevere network performance degradation, increased collisions, late collisions, CRCerrors, and undetected data corruption.

Note: If both speed and duplex mode of an Ethernet interface port are forced using the Advanced

User Parameters file, that port will no longer perform automatic cable detection. This means

that if you have the Ethernet interface port connected to an external switch or hub port you

must use a crossover cable. If you have the Ethernet interface port connected to the uplink port

on an external switch or hub, or if you have the Ethernet interface port directly connected to

another Ethernet device, you must use a normal cable.


44/270


3

Connection to a 10Base-T / 100Base Tx Network

Either shielded or unshielded twisted pair cable may be attached to a port. The 10Base-T/100Base Tx

twisted pair cables must meet the applicable IEEE 802 standards. Category 5 cable is required for

100BaseTX operation.

Each Ethernet port automatically senses whether it is connected to a 10BaseT or 100BaseTX network,

half duplex or full duplex. (The automatic negotiation of speed and/or duplex mode can be explicitly

overridden using Advanced User Parameter settings).

10Base-T/100Base Tx Port Pinouts

Pin Numb er Signal Descr ipt ion

1* TD+ Transmit Data +

2 TD Transmit Data

3 RD+ Receive Data +

4 NC No connection

5 NC No connection

6 RD Receive Data

7 NC No connection

8 NC No connection

* Pin 1 is at the bottom of the Ethernet port connector


Note: Pin assignments are provided for troubleshooting purposes only. 10Base-T/100Base-Tx cables

are readily available from commercial distributors. We recommend purchasing rather thanmaking 10Base-T/100Base-Tx cables.


45/270


46/270


3

Direct Connection to the PACSystems Ethernet Interface

Connection of Ethernet devices directly to the Ethernet Interface is shown below:

10/100

10/100

10BaseT/100Base TxTwisted Pair Cable

Other Ethernetdevices such as PCs,

Ethernet Interfaces

on other PLCs,

Operator Interfaces

Ethernet

Interface


47/270


3

Station Manager PortThe RX7i and embedded RX3i Ethernet interfaces provide a dedicated RS-232 serial port for local

Station Manager use. This nine-pin D connector accepts a standard straight-through nine-pin RS-232

serial cable to connect to a standard AT-style RS-232 port.

The following cable is available:

IC200CBL001 Cable, CPU Programming

Port Settings

The serial (COM) port of the terminal or computer that is connected to the Ethernet Interface must use

the same communications parameters as the Ethernet Interface.

The default values for the Station Manager port are 9600 bps, 8 bits, no parity, and 1 stop bit. If the

Ethernet Interface is configured with default values for this port, or the Ethernet Interface has not been

configured, use these default values. If the Ethernet Interface is configured with non-default values for

this port, use those values for the serial port settings of the terminal or computer.

Station Manager (RS-232) Port Pin Assignment

Pin No Signal Direction Descriptio n

1* DCD IN Data Carrier Detect

2 TX OUT Transmit Data

3 RX IN Receive Data

4 DSR IN Data Set Ready

5 GND Signal Ground

6 DTR OUT Data Terminal Ready7 CTS IN Clear to Send

8 RTS OUT Ready to Send

9 RI IN Ring Indicator

* Pin 1 is at the bottom right of the Station Manager port connector



48/270


3

Verifying Proper Power-Up of the Ethernet Interface after ConfigurationAfter configuring the interface as described in chapter 4, turn power OFF to the CPU for 35 seconds,

then turn the power back ON. This starts a series of diagnostic tests. The EOK LED will blink indicating

the progress of power-up.

The Ethernet LEDs will have the following pattern upon successful power-up. At this time the Ethernet

Interface is fully operational and on-line.

LED Ethernet Interface Online

EOK On

LAN On, Off, or blinking, depending on network activity

STAT On

If a problem is detected during power-up, the Ethernet Interface may not transition directly to the

operational state. If the Interface does not transition to operational, refer to Diagnostics, chapter 11 for

corrective action.


49/270


3

Pinging TCP/IP Ethernet Interfaces on the NetworkPING (Packet InterNet Grouper) is the name of a program used on TCP/IP networks to test reachability

of destinations by sending them an ICMP echo request message and waiting for a reply. Most nodes

on TCP/IP networks, including the PACSystems Ethernet Interface, implement a PING command.

You should ping each installed Ethernet Interface. When the Ethernet Interface responds to the ping,it

verifies that the interface is operational and configured properly. Specifically it verifies that acceptable

TCP/IP configuration information has been downloaded to the Interface.

For configuration details, including setting an initial IP address, refer to chapter 4.

Pinging the Ethernet Interface from a UNIX Host or Computer Running TCP/IPSoftware

Apingcommand can be executed from a UNIX host or computer running TCP/IP (most TCP/IP

communications software provides apingcommand) or from another Ethernet Interface. When using a

computer or UNIX host, you can refer to the documentation for thepingcommand, but in general allthat is required is the IP address of the remote host as a parameter to thepingcommand. For example,

at the command prompt type:

ping 10.0.0.1

Determining if an IP Address is Already Being Used

Note: This method does not guarantee that an IP address is not duplicated. It will not detect a device

that is configured with the same IP address if it is temporarily off the network.

It is very important not to duplicate IP addresses. To determine if another node on the network is using

the same IP address:

1. Disconnect your Ethernet Interface from the LAN.

2. Ping the disconnected Interfaces IP address. If you get an answer to the ping, the chosen IP

address is already in use by another node. You mustcorrect this situation by assigning unique IP

addresses.


50/270


3

Ethernet Plug-in ApplicationsEthernet interface versions 3.6 and later support the use of additional firmware images called Ethernet

plug-in applications, which may implement additional communication protocols. Up to three Ethernet

plug-in applications may be loaded into the Ethernet interface along with the Ethernet firmware via theWinLoader utility. Each plug-in application is identified by a number (1-3). Once loaded, each Ethernet

plug-in application is stored in non-volatile memory where it is preserved until it is overwritten by

WinLoading another Ethernet plug-in application with the same number, or it is explicitly deleted via the

pluginappStation Manager command (see TCP/IP Ethernet Communications for PACSystems Station

Manager Manual, GFK-2225).

All Ethernet plug-in applications are started during normal Ethernet powerup or restart. During

troubleshooting, the Ethernet Restart pushbutton may be used to startup the Ethernet interface without

the plug-in applications (see Ethernet

tcp_ip ethernet communications for pacsystems user's manual, gfk-2224k.pdf

Documents