Honeywell FC-R/PB2/N/12 | Experion PKS Remote I/O Processor Module
Honeywell FC-R/PB2/N/12 | Experion PKS Remote I/O Processor Module - Image 2
Honeywell FC-R/PB2/N/12 | Experion PKS Remote I/O Processor Module - Image 3
Honeywell FC-R/PB2/N/12 | Experion PKS Remote I/O Processor Module - Image 4

Honeywell FC-R/PB2/N/12 | Experion PKS Remote I/O Processor Module

  • Model: FC-R/PB2/N/12
  • Brand: Honeywell
  • Series: Experion PKS (Process Knowledge System)
  • Core Function: This module acts as the critical gateway, bridging field I/O signals to the main C300 controller via the redundant Process Bus.
  • Type: Remote I/O Processor / Process Bus Interface Module
  • Key Specs: Redundant Process Bus support, 24VDC power input, Hot-swappable design
Category: SKU: HONEYWELL FC-R/PB2/N/12

Description

Key Technical Specifications

  • Part Number: FC-R/PB2/N/12
  • System Compatibility: Honeywell Experion PKS / C300 Controller
  • Module Type: Remote I/O Processor (Process Bus Interface)
  • Communication: Redundant Process Bus (Dual Channel)
  • Input Voltage: 24V DC (Nominal)
  • Mounting: DIN Rail (Standard Honeywell I/O Carrier)
  • Redundancy: Supports module and bus redundancy
  • Hot-Swap: Yes (Supported without system shutdown)
  • Environmental Rating: Conformal coated for industrial environments
  • Status Indicators: LED diagnostics for Power, Comm, and Fault

Product Introduction

In the world of Honeywell Experion PKS, the C300 controller gets all the glory, but the FC-R/PB2/N/12 is the unsung hero that actually makes the system talk to the real world. If you are running a remote I/O drop, this processor module is the brain of that cabinet. It takes all those analog and discrete signals from your field instruments and packages them up to send over the redundant Process Bus back to the main controller.What makes this specific unit a lifesaver is its true redundancy. I’ve seen plants take a direct hit to their primary communication bus during a thunderstorm, and because they had these modules set up correctly with the secondary bus, the operators never even saw a blip on the screens. It is a rugged, industrial-grade piece of hardware designed to sit in a hot, dusty cabinet and keep your process data flowing without interruption.

 

Quality SOP & Tech Pitfalls (The Reality Check)

The Lab Report (SOP)
Every FC-R/PB2/N/12 module goes through a rigorous pre-shipment checklist:

  1. Visual & Pin Inspection: We check the backplane connectors for any bent pins and verify the exact part number against the Honeywell label.
  2. Insulation Resistance: A quick check with a multimeter to ensure there are no shorts on the 24VDC power terminals.
  3. Live Rack Test: We install the module in a powered Experion I/O carrier. We verify that the Power LED lights up solid green and that it establishes communication on the Process Bus without throwing a “Comm Fail” alarm.
  4. Anti-Static Packaging: Once it passes, it is immediately sealed in a shielded anti-static bag to protect the sensitive bus interface components.

The Engineer’s Warning (Pitfalls)
Here is the number one way to ruin your day with this module: Ignoring the Node Address switches. Before you even think about powering this up, you must set the physical rotary switches (or DIP switches, depending on the exact sub-revision) to match the node address defined in your Control Builder database. If the physical switch says “5” and your software expects “6”, that module will sit there flashing red and your remote I/O drop will be completely dead. I once spent an entire night shift troubleshooting a “failed” processor, only to realize the previous tech bumped the switch during installation. Always double-check your hardware against the I/O map.

 

Installation & Configuration Guide

Follow this routine to swap the module without tripping your remote I/O drop.

  1. Pre-Installation: If possible, place the affected I/O drop in “Out of Service” (OOS) in the Control Builder or Operator Station. Do not just yank it out live if you can avoid it.
  2. Removal: Release the top and bottom latches on the carrier. Pull the module straight out. Inspect the old module’s rotary switches and write down the exact Node Address setting.
  3. Configuration Check: Take your new FC-R/PB2/N/12 and set the physical Node Address switches to match the old one exactly. This prevents 90% of startup headaches.
  4. Installation: Align the module with the carrier guides and slide it in firmly until it seats. You should feel a solid connection.
  5. Power-On: The module should power up immediately. Watch the LEDs—the Power light should be green, and the Comm lights should start flashing or go solid (indicating bus activity).
  6. Verification: Take the I/O drop out of OOS in the software. Check your diagnostics page to ensure the module is reporting “Healthy” and scanning its child I/O cards correctly.

Compatible Replacement Models

  • ✅ Drop-in Replacement: FC-R/PB2/N/12 (Same Revision). Replacing a failed unit with the exact same part number is a true drop-in. As long as your Node Address matches, the C300 controller will recognize it instantly.
  • ⚠️ Software Compatible: FC-R/PB2/N/10 or N/11. These are earlier revisions of the same Process Bus module. They are functionally identical, but you may need to acknowledge a hardware revision change in the Honeywell system diagnostics. No logic changes are typically required.
  • ❌ Hardware Mod Required: FC-RTE (Remote Terminal Unit). This is an entirely different architecture. You cannot swap a Process Bus module with an RTU module without completely rewiring the cabinet and rewriting your control strategy.

 

Frequently Asked Questions (FAQ)

Can I hot-swap this module while the plant is running?
Yes, the Experion PKS architecture supports hot-swapping for this module. However, I always recommend putting the specific I/O drop in “Out of Service” via the software first if the process allows it. It prevents the controller from throwing a flurry of “Bad PV” alarms while the module reboots.What do the LED lights actually mean?
Generally, a solid Green Power LED means you have good 24VDC. A flashing or solid Green Comm LED means it is talking to the C300 controller. If you see a solid Red Fault LED, it usually means a hardware failure or a major configuration mismatch (like that Node Address issue I mentioned earlier).Does this module need a firmware download?
If you are replacing it with the exact same part number (FC-R/PB2/N/12), the C300 controller will recognize it and sync it automatically. You do not need to manually flash firmware unless you are upgrading from a very old legacy revision.Will this work with my older TDC 3000 system?
No. This module is designed specifically for the Experion PKS and C300 controller environment. It is not backward compatible with the legacy TDC 3000 or GUS architectures.My module has power but no communication. What gives?
9 times out of 10, it is one of three things: The Node Address switch is set wrong, the Process Bus cable is loose or terminated incorrectly, or the module is not defined in the Control Builder database. Check your physical wiring and your software I/O map before condemning the hardware.

Related products