PACSystems* RX3i

IC695ETM001-EP
GFK-2332N Ethernet Interface Module
July 2012

The Ethernet Interface Module, IC695ETM001, connects a PACSystems* RX3i

controller to an Ethernet network. It enables the RX3i controller to communicate
with other PACSystems equipment and with Series 90 and VersaMax
controllers. The Ethernet Interface provides TCP/IP communications with other
control systems, host computers running the Host Communications Toolkit or
programmer software, and computers running the TCP/IP version of the
programming software. These communications use the SRTP, Modbus TCP,
and Ethernet Global Data (EGD) protocols over a four-layer TCP/IP (Internet)
stack.

Features of the RX3i Ethernet Interface include:

▪ Full programming and configuration services. Firmware upgrades from the

RX3i CPU using the WinLoader software utility, which is supplied with
updates to the Ethernet Interface software.
▪ Periodic data exchange using Ethernet Global Data (EGD).
▪ EGD Commands to read and write controller and EGD exchange memory
over the network.
▪ TCP/IP communication services using SRTP.
▪ Support for SRTP Channels, Modbus/TCP Server, and Modbus/TCP Client
▪ Built-in Station Manager for on-line supervisory access to the Ethernet
Interface. Dedicated Station Manager port.
▪ Two auto-sensing 10Base T / 100Base TX RJ-45 shielded twisted-pair
Ethernet ports for direct connection to either a 10BaseT or 100BaseTX
IEEE 802.3 network without an external transceiver. There is only one
interface to the network (only one Ethernet MAC address and only one IP
address).
▪ Internal network switch with Auto negotiate, Sense, Speed, and crossover
detection.
▪ Recessed Ethernet Restart pushbutton to manually restart the Ethernet
firmware without power cycling the system.
▪ LEDs: Ethernet OK, LAN OK, Log Empty, individual port activity and speed
LEDs.
▪ Configurable stand-alone Redundant IP addressing, which allows a single IP address to be assigned to
corresponding Ethernet modules in two different controllers. The Redundant IP address is configured in addition to
the normal unique IP address of each Ethernet module. Under application logic control, only the Ethernet module in
the active unit can use the Redundant IP address.
▪ Time synchronization to SNTP Time Server on Ethernet network (when used with Release 5.00 or later CPU
module).

*
indicates a trademark of GE Intelligent Platforms, Inc. and/or its affiliates. All other trademarks are the property of their
respective owners. All rights reserved.
2 RX3i Ethernet Interface Module
GFK-2332N

IC695ETM001 Specifications
Ethernet processor speed 200 MHz
Connectors - Station Manager (RS-232) Port: 9-pin female D-connector
- Two 10BaseT / 100BaseTX Ports: 8-pin female shielded RJ-45
LAN IEEE 802.2 Logical Link Control Class I
IEEE 802.3 CSMA/CD Medium Access Control 10/100 Mbps
Number of IP addresses One
Number of Ethernet Port Two, both are 10BaseT / 100BaseTX with auto-sensing RJ-45 connection.
Connectors
Embedded Ethernet Switch Yes – Allows daisy chaining of Ethernet nodes.
Serial Port Station Manager Port: RS-232 DCE, 1200 - 115200 bps.
Refer to the PACSystems RX3i System Manual, GFK-2314, for product standards and general specifications.

For additional information about the Ethernet Interface Module, refer to the following publications:
▪ TCP/IP Ethernet Communications for PACSystems, GFK-2224
▪ PACSystems TCP/IP Communications, Station Manager Manual, GFK-2225

Installation in Hazardous Areas

The following information is for products bearing the UL marking for Hazardous Areas:

 WARNING - EXPLOSION HAZARD - SUBSTITUTION OF COMPONENTS MAY IMPAIR SUITABILITY FOR

CLASS I, DIVISION 2;

 WARNING - EXPLOSION HAZARD - WHEN IN HAZARDOUS LOCATIONS, TURN OFF POWER BEFORE
REPLACING OR WIRING MODULES; AND

 WARNING - EXPLOSION HAZARD - DO NOT CONNECT OR DISCONNECT EQUIPMENT UNLESS POWER

HAS BEEN SWITCHED OFF OR THE AREA IS KNOWN TO BE NONHAZARDOUS.

 EQUIPMENT LABELED WITH REFERENCE TO CLASS I, GROUPS A, B, C & D, DIV. 2 HAZARDOUS

LOCATIONS IS SUITABLE FOR USE IN CLASS I, DIVISION 2, GROUPS A, B, C, D OR NON-HAZARDOUS
LOCATIONS ONLY.
RX3i Ethernet Interface Module 3
GFK-2332N

Ethernet Interface Status Bits

Note: Unless LAN Interface OK (Status Bit 16) is set, the other status bits are invalid.
LAN Interface Status Bits
1 Port 1A full duplex
2 Port 1A 100Mbps
3 Port 1B full duplex
4 Port 1B 100 Mbps
5 Network Time Locked
6 Redundant IP address is active
7-8 Reserved
9 Any Channel Error (error on any channel)
10–12 Reserved
13 LAN OK
14 Resource problem
15 Module Overtemperature
16 LAN Interface OK
Channel Status Bits (Two for each channel)
17 Channel 1 Status (SRTP: Data Transfer)
18 Channel 1 Status (SRTP: Channel Error)
... ...
79 Channel 32 Status (SRTP: Data Transfer)
80 Channel 32 Status (SRTP: Channel Error)

Indicators
LED State Indicates
ETHERNET OK Fast Blink Performing Diagnostics
LAN OK Off
LOG EMPTY Off
ETHERNET OK Slow Blink Waiting for Ethernet configuration
LAN OK Off from CPU
LOG EMPTY Off
ETHERNET OK Slow Blink* Waiting for IP Address
LAN OK On/Traffic/Off (* EOK and STAT blink in
unison)
LOG EMPTY Slow Blink*
ETHERNET OK On Operational
LAN OK On/Traffic/Off
LOG EMPTY On/Off
ETHERNET OK Blink error code Hardware failure. See chapter 11 for
LAN OK Off blink code definitions.
LOG EMPTY Off
ETHERNET OK Slow Blink* (* All LEDs blink in Firmware Update
LAN OK Slow Blink* unison; pattern same for
awaiting or performing
LOG EMPTY Slow Blink*
load)
4 RX3i Ethernet Interface Module
GFK-2332N

Field Wiring Station Manager (RS-232) Port Pin Assignment

Pin No Signal Direction Description
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 Ready
7 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
as viewed from the front of the module.
RX3i Ethernet Interface Module 5
GFK-2332N

Release History
Catalog Number Firmware Date Comments
Version
IC695ETM001-EP** 6.14 Jul. 2012 Resolves an issue with a spurious blink code being
displayed during SRTP communications with
CIMPLICITY Plant Edition software.
IC695ETM001-EN 6.13 Apr. 2012 Addresses a field issue and a product security
issue. For details, refer to GFK-2332M.
IC695ETM001-EM 6.12 Dec. 2011 Disables several unnecessary services in the
firmware that otherwise could result in disruption of
system operation and/or data corruption. For
details, refer to GFK-2332L.
IC695ETM001-EL** 6.11 Nov. 2011 Resolves an issue with missed EGD samples. For
details, refer to GFK-2332K.
IC695ETM001-EK 6.10 Sep. 2011 For problems resolved, refer to GFK-2332J.
IC695ETM001-EJ 6.00 Sep. 2009 Adds an SRTP inactivity timeout for better recovery
from lost communication with the programmer. For
details and problems resolved, refer to GFK-2332H.
IC695ETM001-EH 5.51 Jan. 2009 Adds new diagnostics capabilities. For details and
problems resolved, refer to GFK-2332G.
Hardware version Ex updates the IC695ETM001 for
RoHS compliance.
IC695ETM001-DG 5.50 May 2008 Adds ability to modify produced and consumed
EGD exchanges during run mode store. For
problems resolved, refer to GFK-2332F.
IC695ETM001-DF 5.01 Dec. 2007 For problems resolved, see GFK-2332E.
IC695ETM001-DE 5.00 Aug. 2007 Hardware changes to improve performance during
hot swaps. For additional new features and
problems resolved, refer to GFK-2332D.
IC695ETM001-CD 3.81 May 2006 Added support for eight Ethernet interfaces in the
RX3i main backplane. For details and problems
resolved, refer to GFK-2332C.
IC695ETM001-CC 3.60 Nov. 2005 Added support for Modbus/TCP client and Ethernet
plug-in applications. For details and problems
resolved, refer to GFK-2332B.
IC695ETM001-AB 3.00 Apr. 2005 For new features and problems resolved, refer to
GFK-2332A.
IC695ETM001-AA 2.51 Aug 2004 Initial release
** Available as only as an upgrade kit.
6 RX3i Ethernet Interface Module
GFK-2332N

Important Product Information for this Release

This release resolves an issue with a spurious blink code being displayed during SRTP communications with CIMPLICITY
Plant Edition software. For details, see “Problems Resolved by Firmware Release 6.14” on page 7.
Important Note: It is recommended that the user change the station manager password to a password other than the
default password. Access to Remote Station Manager will be disabled when the station manager password is set to the
default password.

Updates
The IC695ETM001 is field upgradeable using the firmware upgrade utility. To upgrade an existing ETM001 to firmware
version 6.14, you will need the upgrade kit 44A753032-G13, which can be downloaded from
http://www.ge-ip.com/support.

The hardware cannot be upgraded in the field.

Functional Compatibility
Subject Description
Hot Swap requires CPU Do not remove or insert the IC695ETM001 while powered unless the CPU is running
firmware 2.51 firmware release 2.51 or higher. This firmware is available in upgrade kit 44A7522290-
G01.
SRTP and EGD SRTP and EGD performance in the RX3i differs slightly from the Series 90-30. Each
performance differs RX3i Ethernet Interface supports a greater number of SRTP connections and EGD
from Series 90*-30 exchanges.
The RX3i currently has several SRTP and EGD operational restrictions compared to the
Series 90-30. When migrating Series 90-30 Ethernet applications to the RX3i, please
carefully read the Ethernet Operational Notes.
Series 90-30 LAN The Series 90-30 LAN Interface Module (IC693CMM321) is not supported by the RX3i
Interface module and should not be placed in an RX3i rack. (Series 90-30 CPUs with embedded LAN
(IC693CMM321) not Interface, IC693CPU364 and IC693CPU374, like any Series 90-30 CPU, should not be
supported by RX3i placed in an RX3i rack.)
Modbus/TCP support Release 3.60 of the PACSystems Ethernet Interface adds Modbus/TCP Client Channels
capability. It supports Modbus Conformance Class 0 function codes 3 and 16,
Conformance Class 1 function codes 1, 2, 4, 5, 6, and 7, and Conformance Class 2
function codes 15, 22, 23, and 24. PACSystems Ethernet supports 32 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.
Programmer version Proficy* Machine Edition Logic Developer 5.8 or later must be used to perform Run-
requirements mode Store of EGD exchanges.
Proficy Machine Edition Logic Developer 5.7 or later must be used for Release 5.00 new
features.
Proficy Machine Edition Logic Developer 5.5 Service Pack 2 or later must be used for
Release 4.00 new features.
Proficy Machine Edition Logic Developer 5.0 Service Pack 3 or later must be used to
program the RX3i CPU for Modbus/TCP Server operation.
CIMPLICITY* Plant CIMPLICITY* Plant Edition 6.1 Service Pack 1a with Update 040204_s90tcp_6101or
Edition version Service Pack 2 or later must be used for Ethernet communications with PACSystems.
requirements
RX3i Ethernet Interface Module 7
GFK-2332N

Problems Resolved by Firmware Release 6.14

Subject Description
ETM displays a blink code During SRTP communication with CIMPLICITY Plant Edition software under
during SRTP communication certain conditions, the ETM module would display the 0x25 (run time exception)
with CIMPLICITY Plant Edition blink code.
software Release 6.14 resolves this issue.

Restrictions and Open Issues

Subject Description
Number of SRTP requests When running multiple SRTP client channels, the number of requests, as
tallied may vary reported by the client and the server, may differ between the connections.
SRTP connections remain The Ethernet Interface does not terminate all open SRTP connections before
open after IP address changing its IP address. If the local IP address has changed, any existing open
changed TCP connections are unable to normally terminate. This can leave SRTP
connections open until their underlying TCP connections time out. If quicker
recovery of the SRTP connection is needed, modify the “wkal_idle” Advanced
User Parameter to reduce the TCP keep-alive timer to the desired maximum time
for holding open the broken connection. Refer to TCP/IP Ethernet
Communications for PACSystems, GFK-2224, for details.
REPP does not save results The Station Manager REPP command does not retain the results of a PING that
of aborted PING is aborted due to error. Results are reported when the PING is aborted, but
subsequent REPP commands give the results of the last successfully terminated
PING.
Multiple log events The Ethernet Interface sometimes generates multiple exception log events and
Controller Fault Table entries when a single error condition occurs. Under
repetitive error conditions, the exception log and/or Controller Fault Table can be
completely filled with repetitive error messages.
Intermittent SNTP loss of Under moderately heavy EGD traffic load, the Ethernet Interface may
synchronization occasionally lose synchronization with its SNTP time server and generate
exception log event 29, entry 2=bH.
SRTP communication delays Average latency of communications on SRTP channels may vary considerably
due to TCP retransmissions. SRTP client applications should be designed to take
this variance into account. In particular, SRTP client applications migrating from
Series 90 SRTP servers to PACSystems may need to lengthen SRTP timeout
parameters.
Spurious ‘Ethernet Failure’ On rare occasions, the error “Module hardware fault” may be reported on the
error Ethernet daughterboard. The corresponding fault in the exception log is Event =
1, followed by text "Ethernet failure". This fault is a nuisance fault and may be
ignored.
Spurious Ethernet fault In rare instances, after power cycle, the Ethernet Interface may log the following
fault, Event = 28H, Entry 2 = 000eH. This fault can be safely ignored.
Unexpected EGD COMMREQ EGD Commands may return COMMREQ Status 9590H (= internal error) instead
status of the expected B190H (= Can’t locate remote node) when unable to locate a
remote device on the network.
Very heavy EGD production/ Very heavy EGD production and/or consumption at a server device may cause
consumption at server may EGD command timeout errors when another device attempts to send EGD
cause EGD command commands to that server. If EGD commands must preempt normal production,
timeouts you may set the “gcmd_pri” Advanced User Parameter to 2 (see GFK-2224,
Appendix A). Note that by doing so, EGD exchange production may be delayed.
8 RX3i Ethernet Interface Module
GFK-2332N

Subject Description
SRTP server errors can cause The SRTP Server in the PACSystems Ethernet Interface can encounter various
timeouts at channel client errors if a remote Series 90 client takes down an SRTP connection and then
establishes a new connection. This can cause unexpected channel timeout
errors 0190H or 0290H at the client. The SRTP server errors in the Ethernet
exception log are identified as Event = 2; Entry 2 may be 001cH, or 0021H.
EGD command range failure When an EGD Command attempts a write operation to a bit-mode reference
can write partial data to memory range (%I, %Q; %T, %M, %SA, %SB, %SC) where the amount of data
controller bit memory to be written exceeds the configured size of that reference memory, the
command will return failure status but partial data may be written into the
reference memory. The amount of partial data written depends upon the starting
bit memory location and the data length as follows:
▪ If data starts on a byte boundary (location = (8*n) + 1), no partial data is
written.
▪ If data does not start on a byte boundary (location = (8*n)+1) and data
exceeds the configured reference memory by 8 or more bits, partial data is
written from the starting location to the next byte boundary after the starting
location.
▪ If data does not start on a byte boundary (location = (8*n)+1) and data
exceeds the configured reference memory by less than 8 bits, partial data is
written from the stating location to the end of configured reference memory.
For a Write PLC Memory command, this can occur when writing data into the
target PLC. For Read PLC Memory or Read Exchange commands, this can
occur when writing data received from the target controller into the local CPU
memory. The logic application must not use any data returned to the local CPU if
the EGD command status indicates failure.
To avoid writing partial data to the local or remote PLC, be sure bit memory data
transfers do not exceed the configured reference memory sizes at the
appropriate PLC.
Do not operate with CPU in The operation of the Ethernet interface is disrupted if the RX3i CPU is placed in a
incorrect slot slot other than the one in which it is configured. Various Ethernet exception log
events may occur, such as (Entry = 2, Entry 2 = 30 or 35 or 39 or 1e or 1f) or
(Entry = 8, Entry 2 = b).
No CPU fault logged when The CPU does not log any Controller or I/O Faults when the Ethernet Interface
Ethernet interface in fatal has a fatal blink code. The application should monitor the LAN interface OK
blink code status bit to detect loss of module.
EGD I/O has unexpected EGD I/O has intermittent unexpected variability under heavy load. For a
variability under heavy load Produced Exchange, EGD samples may occasionally be delayed by as much as
a production period or more.
Clear of large hardware A Log event 08/20 may occur when very large hardware configurations are
configurations may cause log cleared and transfers are active on other Server connections. This log event can
event 08/20 be safely ignored.
Reset pushbutton Reset pushbutton action is different from other PACSystems Ethernet products.
On the RX3i Ethernet module, the state of the pushbutton when the module
powers up can change the behavior of the Restart pushbutton. Under normal
operation, a pushbutton press produces a rising-edge signal that triggers a
module restart. However, if the pushbutton is pressed when power is activated
(either by pressing the pushbutton before turning power on or by continuing to
hold the pushbutton in after a restart), the functionality of the pushbutton is
inverted. When the pushbutton is later released, an "incorrect" rising-edge is
detected, which triggers an inappropriate module restart. This does not occur on
other PACSystems Ethernet products.
COMMREQ Status Word value Occasionally a COMMREQ Status Word value of 0x54A0 is returned after
of 0x54A0 occasionally COMMREQs for Ethernet Global Data commands when the previously-
returned for EGD commands transferred command has experienced retries in the network. Executing the
COMMREQ again results in successful transfer of the command.
RX3i Ethernet Interface Module 9
GFK-2332N

Subject Description
Modbus/TCP channel aborted After powering up an RX3i running Modbus/TCP client channels, the establish
during power-cycle connection occasionally fails because the server rejects the "open" request from
the client. The connection will then succeed if the application retries the open
when it sees a 0x9690 or 0xAA90 response to an open request or to the first
write request.
Controller response timeout Under extremely heavy SRTP traffic conditions, the Ethernet Interface may log
errors (8/08) in Ethernet an event in the Ethernet exception log (Event 8, Entry 2 = 08H) indicating an
exception log under overload condition. This error terminates the SRTP connection. If this event
extremely heavy SRTP traffic appears, either the traffic load should be reduced, or the application should use
an alternate communications method to verify that critical data transfers were not
lost due to the overload.
SRTP channel transfers may When SRTP communications are interrupted by a power cycle, the Ethernet
take up to 20 seconds after interface may require up to 20 seconds to reestablish TCP connection used for
power cycle SRTP communications.
"rmdir" Station Manager The "rmdir" Station Manager command does not operate properly with a multi-
command does not work for level directory path. Instead, first change to the parent directory, then delete the
multi-level directory path target directory without specifying a path. For example, the "rmdir dir1/dir2"
results in "RMDIR Failed, dir1/dir2 does not exist". Instead, first do "cd dir1" and
then "rmdir dir2".
Intermittent Ethernet log When starting after a power cycle, the Ethernet Interface may intermittently log
event 8H/15H after power an exception (entry 8H, Entry 2 = 15H, Entry 3 = 0000H, Entry 4 = 00aaH). This
cycle exception is benign and may be ignored.
Intermittent Modbus/TCP When using the "killms" Station Manager command to manually terminate an
Server log events when using active Modbus/TCP server connection, the following Modbus/TCP errors may
"killms" Station Manager occur in the Ethernet exception log: Event 2fH, Entry 2 = 209H, 212H, 21bH, or
command 221H. These errors may be ignored.
Module intermittently Intermittently, when the module is restarted by using the pushbutton or Station
unresponsive after reset
Manager command, the module will blink its OK LED for 5 minutes before
completing the restart. After the restart is complete the module fails to
communicate with the CPU module. The remedy is to power-cycle the PLC.
A890 Commreq status after When using a Commreq to open a Modbus/TCP Channel to a remote server, if
multiple Modbus open
the initial Commreq returned an AA90 status, then future Open Commands
command attempts
may return A890 status. This indicates that local networking resources have
been consumed and are not available for further connection attempts. If this
occurs, the application must wait at least 60 seconds before making the next
connection attempt. This will allow networking resources to be released and
made available for the next Modbus Open Command.
Modbus/TCP request packets The Modbus/TCP server expects to receive each Modbus/TCP request in a
separate TCP packet. If multiple requests are sent in a single packet, the
server may or may not send a response to each request. If responses are sent
to the client, they will be sent in separate TCP packets.
EGD production delayed after When a produced EGD exchange is added or modified by a Run-mode Store, the
RMS of EGD exchange will not be produced until one production period of time has elapsed
after the completion of the run-mode store.
Station Manager PING When initiating ICMP echo requests from the PLC via the Station Manager’s
commands PING command, the operation occasionally fails and an exception is logged
(Event eH, Entry 2 = 6H).
Station Manager “referr” tally The EGD Station Manager “referr” tally may be incremented twice when an
exchange timeout occurs. Exchange status word reporting works correctly and is
not affected.
10 RX3i Ethernet Interface Module
GFK-2332N

Subject Description
“wkal_idle” AUP parameter Zero is allowed for the “wkal_idle” (TCP keepalive timer) but it is an invalid value.
should not allow zero
TCP connection may timeout If the TCP connection timeout is set higher than 10 minutes, the connection may
early if the timeout is set timeout before the configured value. The connection timeout is derived from
greater than 10 minutes three AUP parameters: wkal_idle + (wkal_cnt + 1) * wkal_intvl.

Ethernet Operational Notes

Subject Description
Remote Station Manager User should change the station manager password to other than the default
access is disabled until password. The remote station manager access is disabled until the station
Station manager password is manager password is changed to other than the default password.
changed The station manager password can be changed using an AUP file. (Refer to
Appendix A, Configuring Advanced User Parameters in TCP/IP Ethernet
Communications for PACSystems User’s Manual, GFK-2224K.)
Changing the default GE Intelligent Platforms strongly recommends that you change the Station
Station Manager password Manager password to a value other than the default. Before a configuration has
is strongly recommended been stored to the CPU, you can change the password by using the CHPARM
command to modify the Advanced User parameter (AUP) stpasswd. For details
on using this command, refer to the Station Manager Manual, GFK-2225.
It is not recommended that you change any AUP other than stpasswd.
1. Use the current password to access the Modify level of the Station Manager.
The default password is system.
2. Change the password.
Example: = chparm stpasswd newpass
3. Restart the Ethernet interface or cycle power. Changes made via the
CHPARM command do not take effect until the Ethernet interface is restarted
or power is cycled. Advanced User Parameters are saved in non-volatile
memory. Changes made by the CHPARM command are retained over restart
and power cycles, until changed again by the CHPARM command.
4. To permanently change the Station Manager password, you must change the
stpasswd parameter in the AUP file. See the TCP/IP Ethernet
Communications for PACSystems User’s Manual, GFK-2224 for details. (After
the CPU configuration has been stored into the CPU, the CHPARM command
is prohibited and any previous changes made with it are no longer effective.)
One TTL value configuration The system accepts only one TTL value. If you configure a separate TTL value
for all EGD groups for each EGD group, the minimum TTL value is configured for all EGD groups.
Protection against attack on When the FTP connection is not in use, the configuration parameter, Maximum
FTP server FTP Server Connections should be set to 0. This protects against attack on FTP
server.
RX3i Ethernet Interface Module 11
GFK-2332N

Subject Description

Configuration of IP Address is The Ethernet Interface cannot operate on a network until a valid IP address is
configured. The Ethernet addressing information must be configured prior to
required before using
actual network operation, or to recover from inadvertent changes to the Ethernet
Ethernet communications addressing data at the Ethernet Interface. Use one of the following methods to
initially assign an IP address:
▪ Connect a serial terminal to the Interface’s Station Manager port. Then use
the CHSOSW command to enter the desired IP address. For details, see
PACSystems TCP/IP Communications Station Manager Manual, GFK-2225.
▪ Temporarily assign an IP address to the module using the SetIP tool over
the Ethernet network. For details, see TCP/IP Ethernet Communications for
PACSystems, GFK-2224.
▪ The Ethernet Interface automatically obtains a temporary IP Address from a
BOOTP server on the network. For details, see TCP/IP Ethernet
Communications for PACSystems, GFK-2224.
Once a temporary IP address has been set up, the Ethernet Interface can be
accessed over the network (by the Machine Edition programming software). The
programmer should then be used to configure the proper IP address for the
Ethernet Interface.
Default IP address (0.0.0.0) The default IP address value (0.0.0.0), whether obtained from HW Configuration
attempts to set IP address or backup configuration, causes the Ethernet Interface to request a temporary IP
via BOOTP address from a BOOTP server device on the network.
LAN must be tree, not ring The two Ethernet network ports on the PACSystems RX3i Ethernet Interface
must not be connected, directly or indirectly, to the same network device. The
hub or switch connections in an Ethernet network must form a tree and not a
ring; otherwise duplication of packets and network overload may result. In this
situation, the RX3i Ethernet modules will continually reset.
Reporting of duplicate IP The PACSystems RX3i does not log an exception or a fault in the Controller
address Fault Table when it detects a duplicate IP address on the network.
Multiple zero period EGD If more than one EGD produced exchange is configured for a production period
exchanges may not produce of zero, the exchanges may not produce similar numbers of samples. Due to the
similar numbers of samples way that scheduling occurs when multiple exchanges are scheduled “as fast as
possible”, some zero period exchanges may produce significantly more samples
than others. For more consistent EGD production, configure the produced EGD
exchanges with non-zero production periods.
Changing IP address while Open SRTP Server connections established with a remote SRTP client are not
SRTP connection open may terminated as expected when the RX7i’s IP address is changed (typically by
generate log events storing a new HW Configuration to the RX7i). A Series 90 SRTP client (“SRTP
channels”) reports either a 9690H or 0190H status; the SRTP connection may
remain open until the connection is terminated as a result of a client timeout.
Please refer to Open Ethernet Problems, Internal Problem ID Code CR-1434 for
more information.
Series 90-30 datagram Series 90-30 – format datagrams are supported, but cannot access %P or %L
restrictions memory.
Advanced User Parameter The Advanced User Parameter “wsnd_buf” should not be changed. Changing
wsnd_buf should not be this value may cause the LAN LED to go out and the Ethernet Interface to drop
changed connection.
Heavy load can block Station As explained in PACSystems TCP/IP Station Manager Manual, GFK-2225,
Manager Chapter 1, a heavy EGD and/or SRTP load can block Station Manager operation.
12 RX3i Ethernet Interface Module
GFK-2332N

Subject Description
One-time delay of EGD If more than 24 SRTP Server connections are established simultaneously, EGD
Production (and possibly Production may be briefly delayed for each connection after the 24th when the
Consumption) if more than 24 connections are first made after power is applied. If EGD consume acceleration
SRTP Server connections are has been disabled, then EGD Consumption is also delayed. The delay only
started simultaneously occurs once when the SRTP Server connection is established for the first time
after Powerup. No delay is experienced for the first 24 SRTP Server
connections.
Very heavy EGD Very heavy EGD production and/or consumption at a server device may cause
production/consumption at EGD command timeout errors when another device attempts to send EGD
server may cause EGD commands to that server. If EGD commands must preempt normal production,
command timeouts you may set the “gcmd_pri” Advanced User Parameter to 2 (see GFK-2224,
Appendix A). Note that by doing so, EGD exchange production may be delayed.

SRTP Application Timeouts The application timeouts within SRTP Channels also include the time needed to
must accommodate network establish and maintain the underlying network and STRP connection. Examples
connection overhead are establishing the TCP connection for a new channel, establishing
communication with the remote device, and TCP retransmissions during Channel
operations. If the time needed for TCP connection establishment or maintenance
exceeds the user-specified channel application timeout values, an application
timeout will occur. Channel application timeouts are temporary errors; the
channel continues to run.
Client Channels and In a Redundancy System, Client Channel COMMREQs can only be initiated from
Redundant IP the unit that owns the Redundant IP address. Therefore, the user application
logic should use Bit 6 in the LAN Interface Status bit area, “Redundant IP Active”
as part of their enabling logic that drives a client channel COMMREQ.
Idle Modbus/TCP connection An idle Modbus/TCP connection between a Series 90 controller and the
between a Series 90 and a PACSystems Ethernet Interface may be prematurely terminated. There is an
PACSystems may be incompatibility between the TCP "Keep-Alive" timer values on the PACSystems
prematurely terminated Ethernet Interfaces and Series 90 Ethernet Interfaces. The default value of the
keep-alive timer for the Series 90 modules is set to a much higher value than for
the PACSystems. To keep TCP connections open between a Series 90 Ethernet
Interface and a PACSystems Ethernet Interface, the Series 90 Interface
Advanced User Parameter wkal_time should be set to the value 750 to match
that of PACSystems. With this change, TCP connections remain open
indefinitely. This also applies to SRTP Client Channels that have infrequent
traffic and can be resolved by using the same technique.
Attempt to open 17 or more If more than the maximum 16 supported Modbus Server Connections are
Modbus server connections attempted, the TCP connection may succeed, but no data may be subsequently
may appear successful transferred.
SRTP Connections Remain The Ethernet Interface does not terminate all open SRTP connections before
Open After IP Address changing its IP address. Once the local IP address has changed, any existing
Changed open TCP connections are unable to normally terminate. This can leave SRTP
connections open until their underlying TCP connections time out. If quicker
recovery of the SRTP connection is needed, modify the “wkal_idle” Advanced
User Parameter to reduce the TCP keep alive timer down to the desired
maximum time for holding open the broken connection. Refer to TCP/IP Ethernet
Communications for PACSystems, GFK-2224, for details.
RX3i Ethernet Interface Module 13
GFK-2332N

Subject Description
RX3i CPU Time Used for Changing the Ethernet interface time via the CHTIME command does not affect
Produced EGD Timestamps the timestamp value within EGD exchanges produced from this Ethernet
interface. The EGD timestamp value reflects the current CPU time. In Series 90-
70 products and the Series 90-30 CPU364, EGD timestamps are taken from the
Ethernet interface and do reflect CHTIME modifications.
ENIU Stale Data During Run In a large PPS system running 20 ENIUs, when a Run-mode Store is performed
Mode Store of EGD that deletes the EGD exchanges for 10 of the ENIUs, the other ENIUs will see
the status on their exchanges indicate consumption timeouts during the RMS. At
the completion of the RMS, the exchanges operate normally.