Honeywell TC-CCN013 Redundant Net Interface Module

Honeywell TC-CCN013 Redundant Net Interface Module

Configured for redundant ControlNet communication in Honeywell process control networks, the Honeywell TC-CCN013 (TC-CCN013 Redundant Net Interface Module) provides direct network interface functionality between ControlNet segments and compatible Honeywell control platforms. The module supports redundant media architectures, deterministic data exchange, and controller communication within Experion PKS and legacy C200 system environments.

Hardware Specifications

Channel Isolation and Deterministic Network Communication

The TC-CCN013 is designed to support ControlNet communication between Honeywell control components operating on deterministic industrial networks. Redundant media capability permits communication continuity when a network path becomes unavailable, allowing the secondary communication path to maintain network accessibility.

Within distributed control system architectures, the module manages scheduled ControlNet data transfer at 5 Mbps while supporting communication across as many as 99 network nodes. The interface is frequently deployed where redundant controller-to-network communication paths are required to maintain process data availability.

Frequently Asked Questions

Q: Does the module support redundant network media connections?
A: Yes. The TC-CCN013 supports dual-path ControlNet network configurations for redundant communication architectures.

Q: Can the module operate with legacy Honeywell control platforms?
A: Yes. Documentation identifies compatibility with both Experion PKS and older C200 control systems.

Q: What power resources are required by the module?
A: The module requires 970 mA from the 5 VDC system supply and 1.7 mA from the 24 VDC network supply.

Field Installation Guidelines

• Verify chassis compatibility before installation.
• Connect redundant ControlNet media according to system network design.
• Maintain separation between communication and power wiring.
• Secure network terminations before energizing the controller.
• Confirm node addressing and network configuration during commissioning.
• Inspect communication status indicators after startup.