RX3i Ethernet Interface Module IC695ETM001-HW IPI
9
August 2017
GFK-2332Y
Release History
Catalog Number
Firmware
Version
Date
Comments
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 only as an upgrade kit.
Restrictions and Open Issues
Restrictions and Open Issues
Subject
Description
Number of SRTP requests
tallied may vary
When running multiple SRTP client channels, the number of requests, as
reported by the client and the server, may differ between the connections.
SRTP connections remain open
after IP address changed
The Ethernet Interface does not terminate all open SRTP connections
before changing its IP address. If the local IP address has changed, any
existing 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
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 of
aborted PING
The Station Manager REPP command does not retain the results of a PING
that 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
synchronization
Under moderately heavy EGD traffic load, the Ethernet Interface may
occasionally lose synchronization with its SNTP time server and generate
exception log event 29, entry 2=bH.