FX2N-16CCL-M Mitsubishi MELSEC FX2N CC-Link Module | Master Station Ver.1 Special Function

The FX2N-16CCL-M is Mitsubishi Electric’s CC-Link Ver.1 master station special function module for the MELSEC FX2N compact PLC series, enabling any FX2N base unit to act as a CC-Link master — managing cyclic data exchange with up to 16 CC-Link slave stations for distributed I/O and device communication in FX2N-based automation systems. As the master station counterpart to the FX2N-32CCL local station module, the FX2N-16CCL-M empowers FX2N controllers to build and manage their own CC-Link field networks, connecting remote I/O blocks, intelligent sensors, valve manifolds, and drive components on a single CC-Link cable without individual point-to-point wiring. Atlantech Drives holds stock of the FX2N-16CCL-M. Contact us for fast worldwide delivery and competitive pricing.

What Is the FX2N-16CCL-M?

The FX2N-16CCL-M is a MELSEC FX2N series special function module implementing the CC-Link Ver.1 master station protocol. Installed in the FX2N extension bus, the FX2N-16CCL-M manages cyclic data exchange with up to 16 CC-Link slave stations (remote I/O stations, remote device stations, and intelligent device stations) connected on a single CC-Link cable. The master’s remote I/O data (RX input data from slaves, RY output data to slaves) is mapped to FX2N device memory via auto-refresh — the FX2N program reads slave input states and writes slave output states using standard X/Y/M device ladder instructions without FROM/TO buffer memory programming. The FX2N-16CCL-M’s 16-station limit (versus 64 stations for the MELSEC-Q QJ61BT11N) reflects the FX2N platform’s compact PLC positioning — adequate for machine-level distributed I/O networks but not for plant-wide CC-Link architectures requiring more than 16 stations. Network configuration is performed using GX Works2’s CC-Link network parameter editor, with each slave station’s GSD-equivalent station data defined in the parameter settings.

Key Technical Specifications

• Model: FX2N-16CCL-M
• Function: CC-Link Ver.1 master station
• Network: CC-Link Ver.1 (CLPA standard)
• Maximum Slave Stations: 16
• Transmission Speed: 156 kbps to 10 Mbps (configurable)
• Remote I/O Points (RX/RY): Up to 256 points (16 stations × 16 RX/RY each)
• Remote Register Points (RWr/RWw): Up to 64 words (16 stations × 4 each)
• Bus Connector: 5-pin CC-Link dedicated connector
• Extension Bus Occupation: 16 I/O points
• External Power Supply: 24 VDC ±10%, 80 mA (required)
• Current Consumption (FX2N bus): 80 mA at 5 VDC
• Operating Temperature: 0°C to 55°C
• Compatible FX2N base units: All FX2N models
• Weight: Approx. 0.18 kg

Compatibility & System Integration

The FX2N-16CCL-M is compatible with all CLPA-certified CC-Link Ver.1 slave devices from any manufacturer — Mitsubishi AJ65SBTB remote I/O blocks, AJ65BT-R2 RS-232C intelligent device stations, Mitsubishi FR-series inverter drive CC-Link option boards, and third-party CC-Link slaves from Banner, Balluff, Pepperl+Fuchs, Keyence, and other industrial automation component manufacturers. The FX2N-16CCL-M auto-refresh function maps remote I/O data from all configured slave stations directly to FX2N X/Y and M device addresses, enabling the FX2N ladder program to read remote inputs and write remote outputs using standard FX2N device instructions without the complexity of FROM/TO buffer memory programming. For Mitsubishi FR-A700 and FR-E700 inverter drives with CC-Link option boards (FR-A7NC, FR-E7NC), the FX2N-16CCL-M provides direct speed command and status monitoring from the FX2N program via the CC-Link remote register data — the FX2N writes the frequency setpoint to the slave’s RWw register and reads the actual output frequency, current, and fault code from the RWr register each network scan cycle. The FX2N-16CCL-M supports both remote I/O stations (providing simple binary I/O data) and remote device stations (providing remote register data for intelligent device communication) simultaneously on the same network, enabling mixed I/O block and drive communication on a single CC-Link segment. The module’s CC-Link cable uses standard CC-Link shielded twisted-pair cable (110 Ω impedance) with 5-pin dedicated connectors — the same cable infrastructure used by MELSEC-Q CC-Link networks, enabling FX2N machine networks to share cable trays with plant-level CC-Link networks without additional cabling infrastructure.

Troubleshooting Guide

If the FX2N-16CCL-M reports communication errors after initial installation, verify the CC-Link cable termination first — install 110 Ω termination resistors at both physical ends of the CC-Link trunk cable using the integrated termination switch on the CC-Link connector housing at each end station. Omitting termination causes signal reflections that prevent all stations from reaching the DATA_EXCHANGE state, manifesting as communication errors across all stations simultaneously. Check the FX2N special register D8090 (CC-Link error information register) — specific bit patterns in D8090 indicate which stations are in error (bit 0 = station 1 fault, bit 1 = station 2 fault, etc.), enabling rapid identification of the failing station without a CC-Link network analyser. For individual station communication faults where other stations remain operational, verify the failing station’s DIP switch address settings match the address configured in the FX2N-16CCL-M’s network parameters — a station address mismatch prevents the master from initialising that station while allowing other correctly-addressed stations to operate normally. For systems where the CC-Link communication scan time is slower than expected (causing delayed FX2N input response from remote I/O), verify the CC-Link transmission speed setting — lower baud rates increase the network scan time proportionally. At 10 Mbps with 8 remote I/O stations, the CC-Link scan time is typically 0.5–1 ms; reducing to 156 kbps increases the scan time to approximately 30–50 ms, which may be unacceptable for time-critical FX2N I/O applications.

Frequently Asked Questions

Q: Can the FX2N-16CCL-M master communicate with CC-Link Ver.2 slave devices?
A: The FX2N-16CCL-M supports CC-Link Ver.1 only. CC-Link Ver.2 slave devices with Ver.2-only features (extended cyclic data beyond Ver.1 limits) are not supported. However, most CC-Link Ver.2 slave devices are backward compatible with Ver.1 masters — they operate in Ver.1 mode when connected to a FX2N-16CCL-M master, providing standard Ver.1 I/O data exchange without the extended cyclic capacity of Ver.2. Verify with the slave device manufacturer that Ver.1 backward compatibility is confirmed before specifying Ver.2 slaves with the FX2N-16CCL-M.

Q: What happens to remote I/O outputs on CC-Link slaves when the FX2N CPU enters STOP mode?
A: When the FX2N CPU enters STOP mode, the auto-refresh device mapping from the FX2N output devices to the CC-Link RY output data is suspended — the RY data last transmitted to slaves is held at its last value by default. The FX2N-16CCL-M can be configured to clear all RY outputs (set all slave outputs to 0) on CPU STOP via the module parameter settings in GX Works2. For machine safety applications, configure the clear-on-stop function for any CC-Link slaves controlling actuators that should return to safe state when the FX2N CPU is in STOP mode.

Q: Can the FX2N-16CCL-M be installed in the same FX2N system as an FX2N-32CCL local station module?
A: No. An FX2N system cannot simultaneously act as both a CC-Link master (FX2N-16CCL-M) and a CC-Link local station (FX2N-32CCL) — each module provides a different CC-Link network role, and both cannot coexist in the same FX2N base unit. The FX2N must be configured as either master or local station for a given CC-Link network, not both simultaneously.

Do you need more references from this brand? Explore our full catalog of Mitsubishi here: https://atlantechdrives.com/manufacturers/mitsubishi/