44A294554-101 GE Power module Brand new

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. The PING 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.

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-70 SRTP Servers to RX7i may need 

to lengthen SRTP timeout parameters.

Spurious ‘Ethernet Failure’ error On rare occasions, the error “Module hardware fault” may be reported on 

the 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.

Web server failure under heavy load After several hours of heavy load on the web server, the web server may 

fail to return pages and may cause a LAN system-software fault to be 

logged. The web server will resume serving pages when the load is 

reduced. 

Reference table web page restriction After the user selects a user defined table, if the user then tries to go back 

to the pre-defined table of %R1-%R60, an error message may be 

displayed stating “An error was detected when trying to retrieve setting 

from PC cookie”.

Fault table web page restriction On both the I/O and Controller Fault Table web pages, the controller 

program name is not currently displayed in the area provided.

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.

Release 2.00 Controller faults are not 

identified on web page

When any Controller Fault Table entries defined for Release 2.00 are 

displayed using the Ethernet interface web server, the Controller Fault 

description contains only a generic message instead of the proper fault 

text.

Unexpected EGD COMMREQ status EGD Commands may return COMMREQ Status 9590H (= internal error) 

instead of the expected B190H (= Can’t locate remote node) when unable 

to locate a remote device on the network. 

SRTP server errors can cause timeouts 

at channels client

The SRTP Server in the PACSystems Ethernet Interface can encounter 

various errors when the 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.