226A1359-1 GE Module cards in stock

Restriction/Open Issue Description

GBC30 may not resume 

operation after power cycle.

In rare instances, a GBC30 in an expansion rack may not resume normal operation after a 

power cycle of either the expansion rack or the main rack.

To restore GBC operation, power cycle the rack again.

Configuration of third-party 

modules.

Do not specify a length of zero in the configuration of a third-party module. The module will 

not work properly in the system.

Power supply status after CPU 

firmware update.

The controller will report a Loss of or Missing Option Module fault for the IC695PSD140 RX3i 

power supply following an update of CPU firmware. Also, the slot will appear empty in the 

programmer’s online status detail view. The power supply continues to operate normally. 

Power cycle to restore normal status reporting.

Power supply status after 

power cycling.

Rarely, turning a power supply on or off may fail to result in an Add or Loss fault. Also, the slot 

will appear empty in the programmer’s online status detail view. The power supply continues 

to operate normally. Power cycle to restore normal status reporting.

Don’t use multiple targets. In a system in which the hardware configuration is stored from one target and logic is stored 

from a different target, powering-up from flash will not work. The observed behavior is that, 

following a power up from flash, Machine Edition reports hardware configuration and logic 

Not Equal.

Missing Loss of Terminal Block 

fault.

The IC695ALG600/608/616 analog input modules do not produce a Loss of Terminal Block

fault when hardware configuration is stored or the module is hot-inserted, and the terminal 

block is not locked into place. 

Sequence Store failure. When downloading projects with very large hardware configuration or which use large 

amounts of user memory, it is possible to encounter a controller Sequence Store Failure error 

when writing the project to flash. To work around this error, either or both of the following 

actions may be helpful:

1. Perform an explicit clear of flash prior to performing the write.

2. Increase the operation timeout used by Machine Edition prior to performing the write. 

This is done by expanding the Additional Configuration in the Inspector window for the 

target controller, and adjusting the Request Timeout. The timeout may need to be 

increased to as much as 60,000 msec, depending on the amount of memory used and 

the condition of the flash memory