IC693CPU370 GE Fanuc Series 90-30 PLC CPU 133 MHz

GE Fanuc IC693CPU370 Series 90-30 PLC Central Processing Unit

The GE Fanuc IC693CPU370 is a central processing unit for the Series 90-30 programmable logic controller platform. It executes the PLC control program, manages system data and coordinates communication with compatible I/O and communication modules. It is relevant to industrial facilities maintaining established Series 90-30 control systems where a CPU fault, program execution issue or hardware replacement can affect production availability.

For maintenance engineers, selecting this CPU requires more than matching the catalog number. The installed rack, power supply, firmware revision, program memory, communication modules and configured I/O addressing must also be considered. These checks are especially important when restoring an existing machine or replacing a controller in a legacy production line.

01 | Controller Identity Card

• Manufacturer: GE Fanuc
• Product series: Series 90-30
• Catalog number: IC693CPU370
• Product type: PLC central processing unit (CPU)
• Processor speed: 133 MHz, as stated in the supplied product information
• Register memory: 240 KB, as stated in the supplied product information
• Floating-point math: Listed as supported
• Clock: Battery-backed clock, as stated in the supplied information
• Memory technology: RAM and Flash are listed
• System architecture: Described in the supplied information as 32-bit
• Intended use: Compatible Series 90-30 PLC installations, subject to hardware and firmware verification

Important specification check: The source information identifies both an 80386EX processor and an AMD SC520 processor. These are different processor designations, so the exact processor identification should be verified against the official IC693CPU370 documentation. Do not use the conflicting descriptions as interchangeable specifications.

02 | Program Execution and Data Handling

The CPU is the execution center of a PLC system. It processes the control logic, updates internal data and coordinates the controller's interaction with connected I/O and communication hardware.

• Floating-point calculations: The supplied information lists floating-point math support. Verify the relevant programming software, instruction support and firmware requirements before migrating or modifying a program that uses floating-point operations.
• Register memory: The supplied source lists 240 KB. Confirm the official memory specification and the actual program and data capacity applicable to the installed revision.
• RAM and Flash: The source identifies both memory technologies and states that firmware resides in Flash. Confirm the specific program-storage and backup behavior in the applicable manual.
• Timers and counters: The source lists up to 2,000 timers and counters. Verify the supported instruction limits and resource usage against the original program.
• Internal coils and temporary storage: The supplied information lists 3,096 internal-coil bits and 256 temporary-coil bits. Check the applicable memory map before reusing addresses in a modified program.
• System registers: The source lists 28 words. Confirm the exact register definitions and reserved areas in the relevant CPU reference documentation.

When replacing a legacy CPU, preserve the original program and document its version before making changes. A CPU with a matching catalog number should not be assumed to contain the application program, retain the original configuration or reproduce the existing machine behavior without restoration and validation.

03 | I/O Capacity and Rack Integration

The IC693CPU370 is intended to operate within the Series 90-30 PLC architecture. The usable I/O configuration depends on the CPU specification, rack arrangement, supported I/O modules, communication hardware and application configuration.

• I/O capacity: The supplied information mentions 2,048 I/O points in one description and up to 4,096 points in another. These figures conflict and must be checked against the official manual before using either as a design limit.
• Bus and module support: Compatibility with bus modules is mentioned in the supplied description. Verify the specific module catalog numbers and hardware configuration.
• Rack installation: Confirm the CPU's required slot, compatible baseplate and power-supply arrangement from the applicable Series 90-30 installation documentation.
• Remote I/O: If the application uses remote or distributed I/O, verify the required communication interface, supported topology and configuration limits.
• Programmer support: The source states that handheld programmers are not supported. Confirm the appropriate programming software, interface and connection method for the installed revision.

Engineering recommendation: Before ordering a replacement, record the existing CPU catalog number, rack and power-supply models, I/O module list, communication modules and program backup status. This information helps identify configuration differences that a part-number comparison alone may miss.

04 | Communication and Timekeeping

The supplied description mentions Ethernet communication and an RS-485 port on the power supply, while also stating that the CPU itself has no serial ports. These statements do not establish the exact communication interfaces built into the CPU or the supported network configuration.

• Ethernet connectivity: Determine whether Ethernet is provided by a separate compatible communication module. Confirm its catalog number, firmware and configuration requirements.
• Serial communication: Identify the physical port and its host device before selecting a cable or programming interface. Do not assume the power supply's interface is a CPU-integrated port.
• Battery-backed clock: Verify the battery condition and timekeeping behavior using the applicable manual. A depleted battery can affect supported backup functions, depending on the hardware and configuration.
• Program transfer: Confirm the supported programming tool and connection method. The source notes that an EZ program store device requires an Ethernet module, but this detail should be verified against the exact CPU and device documentation.

For a legacy system, communication compatibility should be checked separately from logic execution. A CPU may execute its program while a connected HMI, supervisory computer or engineering workstation fails to communicate because of an interface, addressing or configuration issue.

05 | Suitable Equipment and Application Scenarios

The IC693CPU370 is most relevant where a compatible Series 90-30 controller is already installed and the objective is to maintain, repair or restore the existing automation system.

• Manufacturing production lines: Maintaining sequence logic, interlocks and machine control in established equipment.
• Packaging and material handling: Supporting PLC logic that coordinates sensors, actuators, drives and machine sequences through compatible I/O.
• Water and wastewater equipment: Maintaining pump-control sequences, status monitoring and process interlocks where the existing system uses Series 90-30 hardware.
• Utility and auxiliary systems: Supporting established control panels for pumps, fans and other equipment with compatible field interfaces.
• OEM machinery: Maintaining legacy machines whose original control architecture and application program depend on Series 90-30 hardware.
• Industrial retrofit projects: Providing a potential replacement CPU when retaining the original PLC architecture is preferred over a complete migration, subject to compatibility checks.

These are potential application scenarios rather than confirmation of compatibility with every machine. The original program, I/O configuration, communication hardware and power arrangement must be checked for each installation.

06 | Troubleshooting and Diagnostic Workflow

CPU does not start normally

• Check the rack power supply and verify that the supply voltages meet the hardware requirements.
• Inspect CPU status indicators and record the startup sequence before resetting or removing the module.
• Check the seating of the CPU and other rack modules, following the manufacturer's power-down and handling procedures.
• Review available fault records and the applicable manual to distinguish a power problem from a CPU, memory or configuration fault.

PLC starts, but the machine sequence does not run correctly

• Check the controller's operating state and the program's execution status.
• Review the relevant input states, permissive conditions, interlocks and output commands.
• Compare the current program and configuration with the last known-good backup.
• Check for changes in I/O addressing, module configuration or data interpretation.

Communication with the engineering workstation or HMI fails

• Identify the actual communication interface used by the system.
• Check cables, connectors, network settings and the status of any separate communication module.
• Confirm that the programming software and communication drivers are compatible with the installed hardware.
• Determine whether the PLC is still executing its control logic before attempting a communication-related reset.

Program or data retention is uncertain after a power interruption

• Check the battery condition and the manufacturer's documented backup behavior.
• Verify the program and configuration against a known-good offline copy.
• Confirm which data areas and application settings are expected to be retained.
• Do not assume that replacing a battery or CPU will automatically restore the original application.

Intermittent faults occur after a CPU replacement

• Compare the replacement's catalog number and revision with the original unit.
• Verify rack compatibility, module configuration and the installed program version.
• Inspect the power supply, connectors and communication interfaces.
• Record diagnostic indications and reproduce the fault under controlled conditions before concluding that the replacement CPU is defective.

Diagnostic indicators and fault-reporting capabilities depend on the specific hardware and software revision. Use the relevant GE Fanuc documentation rather than interpreting an LED or a single symptom in isolation.

07 | Global PLC Spare HUB's Insight

For a legacy PLC such as the IC693CPU370, the biggest replacement risk is often the surrounding configuration rather than the physical installation itself. An apparently compatible CPU may still require careful program restoration, communication setup and validation of the existing I/O map.

Before removing the original CPU, where it is safe and practical to do so, back up the application program and document the hardware configuration, firmware details, communication settings and current fault indications. If the controller has already failed, preserve all available project files and maintenance records before attempting recovery.

For a replacement inquiry, send the full model number and a clear label photo. Include the rack and power-supply model, installed I/O modules, communication hardware and the reason for replacement. If the CPU is part of a production-critical system, confirm the recovery plan and test procedure before scheduling the changeover.

08 | Supply, Warranty and Shipping

• Warranty: 12-month warranty, subject to the agreed sales terms.
• Pre-shipment checks: Product identification and condition checks, as applicable to the supplied unit.
• Shipping methods: FedEx, UPS and DHL, subject to destination and service availability.
• Quotation support: Contact Global PLC Spare HUB with the required quantity, destination and existing system details to request a quotation.

For obsolete or legacy control hardware, confirm the exact catalog number and compatibility requirements before placing an order. Availability, condition and delivery arrangements should be confirmed in the quotation.

09 | Frequently Asked Questions

Q1: What should I back up before replacing an IC693CPU370?

Where possible, save the application program and configuration using the supported programming tools. Record the CPU and module catalog numbers, firmware details, I/O assignments, communication settings and any special data-retention requirements. If the original CPU is no longer accessible, look for the latest verified offline project and commissioning records before attempting restoration.

Q2: Can I use this CPU as a direct replacement without modifying the existing PLC program?

Do not assume this without checking the hardware revision, firmware compatibility, program format, memory usage, module configuration and communication setup. Even when the catalog number matches, the original program may need to be restored and validated. Plan a controlled commissioning test covering I/O behavior, interlocks, communications and machine restart conditions.

Q3: How can I tell whether a startup problem is caused by the CPU or the rack power supply?

Start by checking the power-supply status and the specified supply conditions, then record the CPU's startup indicators and available diagnostic information. Inspect module seating and visible connector issues using the manufacturer's safe maintenance procedures. If the supply is stable but the CPU continues to report a hardware or startup fault, use the relevant diagnostic procedure to investigate the CPU and configuration rather than replacing parts at random.

Q4: What details should I check if the replacement CPU cannot communicate with the HMI?

Identify whether the HMI connects through an Ethernet module, a serial interface or another communication device. Check the hardware model, network or serial settings, cable and connector condition, driver compatibility and the HMI's configured controller path. A communication fault does not necessarily mean that the CPU has stopped executing the control program.

Q5: How should I choose a spare CPU for a production-critical legacy machine?

Prioritize exact catalog-number verification, hardware and firmware compatibility, program-recovery requirements and a practical changeover plan. Confirm the rack, power supply, I/O modules and communication interfaces, then check that the application program and required documentation are available. If the system is difficult to shut down, plan the replacement around a verified backup and a documented commissioning procedure rather than relying on the CPU label alone.

Tags