500CPU05 1MRB150081R0001 ABB DCS Central Processing Unit Module

• Brand
  ABB
• Model
  500CPU05
• Product Name
  Symphony Plus DCS Central Processing Unit Module
• Place of Origin
  Sweden
• Customs HS Code
  85389000
• Part number
  1MRB150081R0001
• Dimensions
  128 mm × 110 mm × 35 mm
• Weight
  0.45 kg
• Operating Temperature
  0 °C ~ +60 °C
• Storage Temperature
  ‑40 °C ~ +85 °C
• Warranty
  12 month
• Product Status
  new and original

ABB 500CPU05 (1MRB150081R0001) Input-Output, Compatible Systems, Software and Protocols

Input and Output

The 500CPU05 serves as the core central processing module for ABB INFI90 and Symphony Plus DCS racks, featuring no physical field analog or digital process I/O terminals for on-site signal collection and output.

Power Input DC operating power is obtained from the rack backplane (+5 VDC, ±15 VDC), supplied by the matched 500PSM03 power supply module, with no independent external power input terminals.

Backplane Interface Equipped with a dedicated internal parallel backplane bus, supporting real-time data interaction with rack-mounted I/O modules, power supply modules and redundant CPU units.

Communication Interfaces 1× RJ45 Ethernet port for engineering program downloading and upper system data communication; dedicated INFI90 Plant Loop interface for cross-node DCS interconnection; exclusive redundancy synchronization port for data consistency backup between primary and standby CPUs.

Diagnostic Output Front-panel LED indicators display running status, fault alerts and redundancy working state; internal system fault and alarm status can be output via backplane signals for system-level diagnosis.

Note All field sensor and actuator signal acquisition & output functions are implemented by independent INFI90 series I/O modules. The module supports hot-swap operation for non-stop maintenance.

Compatible Systems

Native Matching System Fully adapted to ABB INFI90 DCS and Symphony Plus process control systems.

Hardware Rack Matching Compatible with standard INFI90 8-slot / 16-slot control racks, paired exclusively with the 500PSM03 power supply module.

Redundancy Architecture Supports hot-standby dual-CPU redundant configuration, realizing seamless failover with identical 500CPU05 modules.

Downstream Hardware Fully compatible with all INFI90 series analog/digital I/O modules and special functional modules.

Upper Monitoring System Supports data interaction with Symphony Plus HMI workstations, third-party SCADA and remote monitoring platforms.

Compatible Software

Engineering Configuration Software ABB Composer: Responsible for hardware configuration, control logic programming, firmware upgrading, online debugging and event log query.

Operation Monitoring Software Symphony Plus Operations: Applied for real-time process monitoring, on-site operation and system alarm management.

Firmware Program Dedicated INFI90/Symphony Plus CPU firmware; primary and standby CPUs must run identical firmware versions to ensure normal redundancy synchronization.

Note Incompatible with ABB AC500 series Automation Builder software.

Supported Communication Protocols

Internal DCS Bus Protocol INFI90 Plant Loop (ABB proprietary protocol) for multi-rack and multi-node internal DCS data transmission.

Ethernet Protocol Standard TCP/IP protocol, used for engineering connection and HMI upper computer data interaction.

Redundancy Synchronization Protocol High-speed dedicated synchronization protocol to ensure real-time data consistency between dual redundant CPUs.

Extended External Protocols With additional gateway modules, it supports mainstream open protocols including Modbus RTU/TCP and OPC-DA for data interconnection with third-party automation devices.

Common Troubleshooting Cases for ABB 500CPU05 (1MRB150081R0001)

Case 1: CPU Boot Failure, Run LED Off, Fault LED Constantly Lit

Phenomenon: The CPU fails to enter operational state after rack power-up. The Run indicator stays dark while the Fault LED remains continuously on. Root Cause: Corrupted firmware image, poor backplane contact, insufficient rack power supply, or internal CPU hardware defect. Resolution: Power down the rack, remove and reinstall the CPU module, and clean the gold-plated backplane connectors. Measure the 5 V backplane voltage supplied by the 500PSM03 power module. Re-download firmware and user application through the engineering software. Replace the CPU module if the fault still exists after reloading.

Case 2: Unplanned Cold Restarts and Spontaneous Reboots During Runtime

Phenomenon: The controller reboots randomly without definite triggering conditions, and no relevant alarm entries are found in the event log. Root Cause: Fluctuating backplane power supply, loose module connections, excessive cabinet ambient temperature, or watchdog timeout triggered by program logic infinite loops. Resolution: Test all rack DC power rails to detect voltage variations. Clean contact pins on modules and the backplane, and optimize cabinet ventilation performance. Audit application logic to eliminate endless loops and overly long execution paths that exceed watchdog thresholds. Inspect system grounding and electromagnetic interference generated by adjacent high-power equipment.

Case 3: Backplane Communication Breakdown Between CPU and Local I/O Modules

Phenomenon: The CPU generates alarms indicating missing or faulty I/O modules; process data exchange with on-rack I/O boards is interrupted. Root Cause: Degraded backplane contact, firmware incompatibility between CPU and I/O modules, or damage to the internal backplane bus. Resolution: Verify firmware version compatibility across the CPU and all associated I/O modules. Re-seat individual suspect I/O modules step-by-step to isolate the faulty unit. Examine the backplane for scratches and oxidation. Simultaneous offline alerts from multiple modules suggest potential backplane bus damage.

Case 4: Intermittent Fieldbus Communication Drop-outs (INFI90 / Ethernet)

Phenomenon: Periodic loss of communication between the CPU and remote nodes or upper-level DCS systems; alarms occur randomly and clear automatically. Root Cause: Incorrect shield-grounding practices, missing bus termination resistors, defective communication cables, or degradation of CPU communication ports. Resolution: Inspect cable shielding and single-point grounding implementation. Confirm proper termination resistance fitted at both bus ends. Substitute test cables for verification. Swap with a spare CPU module to differentiate between port hardware failure and external wiring defects.

Case 5: Application Download Failure from Engineering Workstation

Phenomenon: The engineering tool cannot establish an online connection, or program transmission terminates unexpectedly mid-download. Root Cause: Mismatched IP address settings, PC firewall interception, defective CPU flash memory, or incompatible firmware revisions. Resolution: Ensure the engineering PC and CPU belong to the same network segment and temporarily disable PC firewall functions. Validate that firmware versions match project specifications. If online connection succeeds yet downloading consistently fails, internal flash memory damage is probable and module replacement is required.

Case 6: Watchdog Trip Triggering CPU Fault Mode

Phenomenon: Fault LED illuminates, user logic execution halts, and watchdog trip alarm is logged in the event history. Root Cause: Excessive task cycle duration, program infinite loops, illegal variable access, or heavy bus load consuming CPU processing resources. Resolution: Work offline to adjust task scheduling parameters and optimize application code; remove endless loops and redundant logic segments. Lower fieldbus burden by extending refresh cycles for non-critical variables. Clear fault status and perform a warm restart after modifications are completed.

Case 7: Redundancy Switchover Malfunction in Dual-CPU Configuration

Phenomenon: Automatic failover does not activate upon primary CPU failure; redundancy synchronization error alarm is reported. Root Cause: Version discrepancy between primary and standby CPU firmware, loose or damaged synchronization cable, or electromagnetic interference on sync bus signals. Resolution: Load identical firmware and application software onto both primary and standby controllers. Inspect the redundancy sync cable and connector terminals. Evaluate grounding quality and EMI influences. Re-establish synchronization for the redundant CPU pair after corrective measures.

Case 8: Missing Event Logs or Failed New Alarm Recording

Phenomenon: Historical alarms and event records cannot be preserved or retrieved after power cycling. Root Cause: Defective CPU non-volatile internal memory or incorrect log-storage parameter configuration. Resolution: Complete project backup as a priority. Review log-related configuration items within engineering software. Replace the CPU module if hardware memory error messages are returned.

Summary of Quick-Check Checklist

Inspect power-supply quality and front-panel LED status;

Confirm secure module installation and reliable backplane contact;

Guarantee consistent firmware versions for all rack-based modules;

Examine grounding, shielding treatment and fieldbus cabling;

Analyze event logs to distinguish hardware malfunctions from application-logic faults.

GDB021BE
Unitrol 1020
698B275U01
SM810K01
BC810K02
PP886
PBA800
RED615