239-AN GE Module cards in stock

Restriction/Open Issue Description

WinLoader does not display 

error when it can't connect 

serially with PACS CPU. 

WinLoader does not display an error message if it cannot connect to the PACS CPU when 

attempting to connect to a PACSystems CPU to perform a firmware upgrade. This occurs if 

the cable is physically not connected to the CPU or if the CPU's serial port is not configured for 

the same baud as WinLoader. In this case Winloader displays the status trying to connect

followed by waiting for target. To proceed with the upgrade, press the abort button and 

correct the cable or baud rate setting. 

Operational Notes

Operational Notes

Subject Description

Firmware upgrades using 

Slot 1

Firmware upgrades for modules in Slot 1 will only work for CPUs. Modules other than the CPU 

need to be in Slot 2 or higher to perform a firmware upgrade.

Multiple calls to SVC_REQ 57 

in a single sweep may cause 

CPU watchdog timeouts

Multiple calls to SVC_REQ 57 (Logic Driven Write to Nonvolatile Storage) could result in the CPU 

tripping the watchdog timer and going to STOP-HALT mode. The number of calls to 

SVC_REQ 57 that can be made requires consideration of many variables, what the software 

watchdog timeout value is, how much data is being written, how long the sweep is, age of

nonvolatile storage (flash), etc. If the application attempts to write to flash too frequently, the 

CPU could experience a watchdog timeout while waiting for a preceding write operation to 

complete.

The Logic Driven Read/Write to Flash service requests are not intended for high frequency 

use. GE Intelligent Platforms recommends limiting the number of calls to SVC_REQ 57 to one 

call per sweep to avoid a potential watchdog timeout and the resulting transition to StopHalt.

Error response 1 is no longer 

returned for Modbus RTU 

requests with invalid or 

undefined function codes.

Prior to release 6.70 for the RX3i, the Modbus RTU slave protocol would return an Invalid 

Function Code error response (1) upon receipt of a request with an invalid or undefined 

function code. Starting with release 6.70, the Modbus RTU slave ignores requests with an 

invalid or undefined function code, and no response is sent