GE IS400TVBAS1A
2.2.3.7 CPE310 versus CPU310 Performance DifferencesThe following differences should be considered when converting legacy applications or developing
new applications.
▪ Some exceptionally lengthy CPE backplane operations, such as MC_CamTableSelect, Data Log
and Read Event Queue functions, will take longer to complete compared to other RX3i CPU
models, and may delay backplane operations to IC695 modules.
For example, when an MC_CamTableSelect function block is executed on the PMM335 module,
the CPU’s acknowledgement of the PMM355 module interrupt may be delayed. In this situation,
you may see the following fault in the I/O Fault Table, even when the interrupt has not been
dropped: Error initiating an interrupt to the CPU.
▪ Performance specifications for many features, such as power-up time, function block execution
times and I/O module sweep times have changed. For details, refer to Appendix A.
▪ The RS-232 port on the CPE310 does not provide 5Vdc power on pin 5.
2.2.3.8 CPU305 Performance Differences vs. CPE310 and Legacy RX3i CPUs
The CPE305 exhibits the same performance differences as listed above for the CPE310.
The CPE305 supports legacy CPU310 projects that fit within 5 Mbytes of user memory. The project
configuration must be changed to support this conversion.
Because the CPE305 has less user memory than the other RX3i CPUs, operations that involve
transferring large files could fail.
For example, depending on the number and sizes of Data Log files already stored, the Get_DL (Get
Data Log) command could fail with a C10 hex (file transfer failure occurred while sending the data log
file to the CPU) error. To correct this error
1. Upload the data logs to Machine Edition and delete the logs from the CPU.
2. Take steps to reduce the size of the log file, such as reducing the number of samples, the
sample rate, or the number of parameters logged.

2.2.4.2 Indicators CPU315, CPU320 & CRU320
Eight CPU LEDs indicate the operating status of various CPU functions.
Two Comm LEDs indicate activity on COM1 and COM2.
LED State
On Blinking Off
CPU Operating State
CPU OK On Green CPU has passed its power-up diagnostics and is
functioning properly. 41
Off CPU problem. RUN and OUTPUTS ENABLED LEDs
may be blinking in an error code pattern, which
can be used by technical support for
troubleshooting. This condition and any error
codes should be reported to your technical support
representative.
Blinking Green
Other LEDs off
CPU in Stop/Halt state; possible watchdog timer
fault. Refer to the fault tables. If PME cannot
connect, cycle power with battery attached and
refer to fault tables.
CPU OK Blinking in unison CPU is in boot mode and is waiting for a firmware
update through a serial port. RUN
OUTPUS ENABLED
RUN On Green CPU is in RUN Mode.
Off CPU is in STOP Mode.
OUTPUTS
ENABLED
On Green Output scan is enabled.
Off Output scan is disabled.
I/O FORCE On Yellow Override is active on a bit reference.
BATTERY Off Normal battery42
Blinking Red Battery low42
On Red Battery has failed or is not attached3
SYSTEM FAULT On Red CPU is in Stop/Faulted mode because a fatal fault
has occurred.
COM1 Blinking Green Signals activity on corresponding serial port.