GE IC695ETM001-HW Manual page 11

RX3i Ethernet Interface Module IC695ETM001-HW IPI
March 2016
Subject
EGD command range failure
can write partial data to
controller bit memory
Do not operate with CPU in
incorrect slot
No CPU fault logged when
Ethernet interface in fatal blink
code
EGD I/O has unexpected
variability under heavy load
Clear of large hardware
configurations may cause log
event 08/20
Reset pushbutton
Restrictions and Open Issues
When an EGD Command attempts a write operation to a bit-mode
reference memory range (%I, %Q; %T, %M, %SA, %SB, %SC) where the
amount of data 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.
The operation of the Ethernet interface is disrupted if the RX3i CPU is
placed in a 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).
The CPU does not log any Controller or I/O Faults when the Ethernet
Interface has a fatal blink code. The application should monitor the LAN
interface OK status bit to detect loss of module.
EGD I/O has intermittent unexpected variability under heavy load. For a
Produced Exchange, EGD samples may occasionally be delayed by as
much as a production period or more.
A Log event 08/20 may occur when very large hardware configurations
are cleared and transfers are active on other Server connections. This log
event can be safely ignored.
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.
Description
11
GFK-2332X