WhatsApp: +86 16626708626
Email: 
Phone: +86 16626708626Description
Key Technical Specifications
| Parameter | Value |
|---|---|
| Input/Output Model | CC-PCNT02 — C300 Controller Module |
| Matching IOTA | CC-TCNT01 |
| Role | Replaces CC-PCNT01 for new installs and field replacements |
| Extended Functionality | Required for EIM (EtherNet/IP) and Profit Controller integration — CC-PCNT02 only |
| I/O Link Interfaces | 2, redundant |
| I/O Link Types Supported | PMIO Link (375 Kbaud) or Series C IO Link (750 Kbaud) — one per link |
| Supported CEE Modes | 50 ms CEE, 20 ms CEE (20 ms limited to Honeywell Turbine Control Solution use) |
| Device Index Range | 1–510 |
| Max I/O Units per C300 (50 ms) | 64 mixed I/O types, or 80 if using PM IOPs/Series C IOMs only |
| Max I/O Units per I/O Link | 40 |
| Redundancy | Supported — 2 IOTAs, odd/even Device Index pairing |
| Control Processing Switchover Time | 500 ms (50 ms CEE); 200 ms (20 ms CEE) |
| Redundancy Cable | Ethernet STP, 36/48/60/84 in lengths |
| Time Sync | SNTP, PTPv2 |
| Total CEE User Memory | 14,852 MU (1 MU = 1 KB) |
| Max Tagged Blocks per CEE | 4,095 |
| Network Connection | FTE only, via Control Firewall (CF9) |
Product Introduction
The Honeywell CC-PCNT02 is the current controller module for the Experion PKS C300 — the CPU that executes control strategies, runs dual redundant I/O Link interfaces, and handles peer and display communications. Honeywell now ships CC-PCNT02 as the standard replacement for CC-PCNT01 on both new builds and field swaps.
It’s the version required for extended functionality: EtherNet/IP integration through an EIM and Profit Controller blocks run only on CC-PCNT02, not the earlier CC-PCNT01. Confirm your project’s firmware image (50ms_EHB vs. 50ms_Extended) matches the functionality you need before commissioning.
CC-PCNT02
CC-PCNT02
Troubleshooting Quick Reference
| Symptom | Possible Cause | Relevance to This Part | Quick Check Method | Recommendation |
|---|---|---|---|---|
| No status LED / controller won’t boot | IOTA/rack power loss | ❌ Low | Measure 24 VDC bus at CC-TCNT01 IOTA terminals | Check power supply before replacing the module |
| Controller loads but EIM/Profit Controller blocks fail to assign | Wrong firmware image (running as CC-PCNT01 mode) | ✅ High | Check loaded firmware image in Control Builder (20ms / 50ms_EHB / 50ms_Extended) | Load the extended-functionality firmware image — not a hardware fault |
| Redundant switchover takes longer than 500 ms | Dual I/O Link failure or redundancy cable fault | ✅ Medium | Check redundancy cable connection and I/O Link status on both partners | Verify cable length/seating before condemning either module |
| One I/O Link shows no communication | I/O Link type mismatch (PMIO vs. Series C IO) or cable fault | ❌ Low | Confirm I/O Link baud rate setting matches the connected IOTA type | Correct link configuration — usually not a controller fault |
| Controller runs but display data updates lag | Communication load exceeds PPS/PPM capacity limits | ❌ Low | Compare current parameter/display load against C300 capacity limits | Reduce subscription load or redistribute points — not a defect |
| Controller fails to complete initial sync with partner | Sync window exceeded (240-second spec) | ✅ Medium | Check sync status and timestamps in Control Builder | Investigate network latency/FTE health before replacing hardware |
If the fault persists after ruling out firmware image and network configuration, send the controller diagnostic log and firmware version readout to support for faster root-cause turnaround.
Frequently Asked Questions (FAQ)
Is the CC-PCNT02 hot-swappable in a redundant pair?
Yes, that’s the point of C300 redundancy — pull the failed partner while its mate keeps control running, then insert the replacement. Just don’t do this on a non-redundant, single-controller configuration; that’s a full process interruption.
Do I need CC- specifically, or will CC-PCNT01 work?
Depends on what you’re running. If your project uses EIM (EtherNet/IP) or Profit Controller blocks, you need CC- with the extended-functionality firmware image — CC-PCNT01 doesn’t support those. For a standard control-only replacement, CC- units may still be compatible, but Honeywell now ships CC- for all new orders and field replacements regardless.
Will replacing this module wipe my control strategy?
No — control strategy configuration lives in the Experion Control Builder database (ERDB), not on the controller hardware. Swap the module, reload/checkpoint-restore, and the controller picks up its configuration.
Does this module retain my process values across a swap?
On a non-redundant swap, no — you’ll take a control interruption while the replacement loads and initializes. On a redundant pair, switchover to the surviving partner keeps control running while you swap the failed unit; expect the spec’d switchover interruption (200–500 ms depending on CEE speed).
Why is this listed cheaper than a factory-direct quote?
This is a New Surplus/New Original unit — factory-sealed, serial-verified, never installed — sourced outside Honeywell’s direct sales channel. You skip the OEM markup and lead time; our test report and warranty terms stand in for a factory warranty.
What’s actually tested before this ships?
Power-on self-test and boot sequence verification, I/O Link communication handshake on both channels, firmware image confirmation, and a documented burn-in run. Test report and photos available on request.
Can I mix CC- and CC- in the same redundant pair?
Don’t. Redundant partners should match model and firmware image — mismatched controllers in a redundant pair is asking for a switchover that doesn’t behave the way you expect. Verify both units before commissioning a redundant configuration.
