The FX2N-32CCL is Mitsubishi Electric’s CC-Link Ver.1 local station special function module for the MELSEC FX2N compact PLC series, enabling FX2N base units to participate in CC-Link field networks as a local station — sharing link relay (B) and link register (W) data with a CC-Link master controller while the FX2N CPU executes its own program autonomously, providing the inter-PLC data exchange capability required for FX2N controllers to integrate into Mitsubishi MELSEC-A, MELSEC-Q, or iQ-R supervised CC-Link architectures. As the primary CC-Link network interface for the FX2N platform, the FX2N-32CCL enables legacy FX2N machine controllers to remain in active service as CC-Link network participants long after the FX2N platform itself was discontinued, reducing forced migration timelines in multi-machine facilities. In stock at Atlantech Drives. Request your quote within 24-48 hours with worldwide shipping and 12-month warranty.
What Is the FX2N-32CCL?
The FX2N-32CCL is a MELSEC FX2N series special function module implementing the CC-Link local station protocol, installed in the FX2N right-side extension bus. As a local station, the FX2N-32CCL enables the FX2N CPU to access the CC-Link network’s shared link device space — link relays (B devices, up to 256 points) and link registers (W devices, up to 64 words) are refreshed between the FX2N-32CCL and the CC-Link master in each network scan cycle, making shared network data available in the FX2N program via standard B and W device ladder instructions as if the data were stored locally. The local station architecture differs from an intelligent device station — the FX2N program reads and writes B/W network devices directly using standard ladder instructions (SET B0, MOV W0 D100) without FROM/TO buffer memory programming. The FX2N-32CCL’s station number (1–64) and occupied station count (1–4) are configured via hardware DIP switches on the module front panel, with the occupied station count determining the B/W link device capacity allocated to this station on the network.
Key Technical Specifications
- Model: FX2N-32CCL
- Function: CC-Link Ver.1 local station
- Network: CC-Link Ver.1 (CLPA standard)
- Station Type: Local station (autonomous CPU with shared B/W link device access)
- Occupied Stations: 1 to 4 (DIP switch configurable)
- Link Relays (B devices): Up to 256 points (4 occupied stations)
- Link Registers (W devices): Up to 64 words (4 occupied stations)
- Transmission Speed: 156 kbps to 10 Mbps (auto-detected from master)
- Station Number: 1 to 64 (DIP switch)
- Bus Connector: 5-pin CC-Link dedicated connector
- Extension Bus Occupation: 8 I/O points
- External Power Supply: 24 VDC ±10%, 50 mA (required)
- Current Consumption (FX2N bus): 50 mA at 5 VDC
- Operating Temperature: 0°C to 55°C
- Weight: Approx. 0.15 kg
Architecture & Design Overview
The FX2N-32CCL implements the CC-Link local station protocol stack in a dedicated communication processor within the module, managing the CC-Link token passing, cyclic data exchange, and error handling independently of the FX2N CPU scan cycle. The module maintains a local copy of the CC-Link shared link device space — B relays and W registers — that is refreshed from the master’s transmitted data in each CC-Link network scan cycle. The FX2N CPU accesses the shared B and W devices directly via standard FX2N ladder instructions without the overhead of FROM/TO buffer memory programming — this direct device access is the defining architectural advantage of the local station approach and the reason the FX2N-32CCL is specified for multi-controller coordination applications rather than the simpler intelligent device station architecture. In the FX2N program, B devices (B0, B1, B2…) accessed in the ladder rung represent the corresponding network link relay states — B0 written by the FX2N-32CCL local station is immediately visible in the master’s link relay B0 address and in other local stations’ B0 addresses after the next network scan cycle. This transparent data sharing model enables FX2N controllers on a CC-Link network to exchange handshake signals, production counts, fault codes, and recipe parameters with a supervising MELSEC-Q controller and with each other through direct device manipulation, without explicit network communication programming in the FX2N ladder.
Expert Tips
When configuring the FX2N-32CCL in a CC-Link network alongside MELSEC-Q or iQ-R master stations, use GX Works2’s CC-Link network parameter editor to assign each FX2N local station’s link device address range — the master station’s network parameter defines which B and W addresses are allocated to each station’s send data (data that station writes to the network) and receive data (data the station reads from the network). Carefully plan the B/W address allocation before commissioning to avoid address conflicts between multiple FX2N local stations writing to overlapping B/W address ranges — a common misconfiguration that causes one station’s data to overwrite another’s in the master’s link device space. For CC-Link networks where the FX2N-32CCL must coexist with CC-Link remote I/O stations (AJ65SBTB-16DT, for example), remember that remote I/O stations use RX/RY address space while local stations use B/W address space — the two address spaces are separate, and the total station count limit of 64 applies to the combined count of all station types on the network. Monitor the FX2N-32CCL’s communication status via the special relay M8070 (data link error) and special register D8070 (data link error station information) in the FX2N ladder program — these special devices reflect the CC-Link communication status and can be used to trigger alarm outputs or safe-state logic when CC-Link communication fails due to cable fault or master controller stoppage.
Frequently Asked Questions
Q: Can the FX2N-32CCL communicate with a MELSEC iQ-R RJ61BT11 CC-Link master?
A: Yes. The FX2N-32CCL implements CC-Link Ver.1 local station protocol, which is backward compatible with Ver.2 masters including the RJ61BT11. The iQ-R master’s GX Works3 CC-Link network parameter editor includes FX2N local station configuration options, and the link B/W data exchange between the iQ-R master and the FX2N-32CCL local station operates identically to the communication between a MELSEC-Q QJ61BT11N master and the FX2N-32CCL.
Q: What is the difference between the FX2N-32CCL and the FX3U-32CCL?
A: Both modules implement CC-Link local station protocol for their respective FX platform — the FX2N-32CCL for FX2N base units, and the FX3U-32CCL for FX3U base units. The FX3U-32CCL supports CC-Link Ver.2 with extended cyclic data (up to 512 B relays and 128 W registers with 4 occupied stations and ×8 extended cyclic), while the FX2N-32CCL supports only CC-Link Ver.1 (up to 256 B relays and 64 W registers). The modules are physically incompatible — the FX2N-32CCL cannot be installed in an FX3U base unit extension bus, and vice versa.
Q: Can the FX2N-32CCL be used in a CC-Link network operating at Ver.2 extended cyclic speeds?
A: The FX2N-32CCL supports CC-Link Ver.1 only — it does not support Ver.2 extended cyclic data expansion. When installed in a CC-Link network managed by a Ver.2-capable master, the FX2N-32CCL operates in Ver.1 compatibility mode with its standard B/W link device capacity (maximum 256 B relays and 64 W registers at 4 occupied stations). The master’s network configuration must assign the FX2N-32CCL as a Ver.1 station to avoid attempting Ver.2 extended cyclic communication with a module that does not support it.
Do you need more references from this brand? Explore our full catalog of Mitsubishi here: https://atlantechdrives.com/manufacturers/mitsubishi/
