Mitsubishi USB SC09 Cable Setup Guide 2026

The USB-SC09 family of cables connects your laptop to a Mitsubishi FX-series PLC for programming, monitoring, and download. Setup looks simple on paper — install driver, plug in cable, set the COM port — and goes wrong about 30% of the time on Windows 11 in 2026, almost always for the same handful of reasons. This guide covers the cable variants, driver install on Windows 10 and 11, GX Developer / GX Works2 transfer setup, and the troubleshooting checklist that resolves most "PLC not responding" failures.

Cable variants — what's actually different

Several cables share the SC09 name and look superficially similar. The differences matter.

Original SC09 / SC-09

The original. RS-422 to RS-232, designed for a serial COM port on a desktop. With no native serial port on modern laptops, the SC09 needs a USB-to-RS-232 adapter to be usable in 2026. Generally only seen on legacy maintenance benches.

USB-SC09

Genuine Mitsubishi USB-native version of the original SC09. Single connection from a USB-A port on the laptop to the Mini-DIN-8 port on the FX-series CPU. Supports the FX0, FX0S, FX0N, FX1S, FX1N, FX2N, FX2NC, FX3U, FX3UC, FX3GA, and FX3G families.

USB-SC09-FX

Refined variant of the USB-SC09. More reliable on long downloads, better Windows-side driver behaviour. The default choice for FX-only work in 2026.

USB-SC09-PLUS

Multi-protocol variant — supports both FX-series and the older A / QnA series. Pricier than the FX-only variants. Worth it if you maintain a mix of FX and legacy A / QnA panels.

Clone cables

A large secondary market exists for clone USB-SC09 cables. Most are functional with FX2N and FX3U for short programs and read operations. The trouble starts with long downloads (large project transfers) and Windows 11 driver-signing. Clone cables typically use CH340, PL2303, or FT232 USB-UART chips, and the genuine Mitsubishi cable uses an FT-series chip in most batches.

Honest take: clones are fine for hobby and educational work, hit-or-miss for maintenance, and not worth the risk for production commissioning. If a single bad cable failure costs you a return trip to a customer site, the £50 saved isn't worth it.

Driver install on Windows 10 and 11

Step 1 — identify the chip

Before installing anything, plug the cable into a Windows machine and look at Device Manager. Expand "Other devices" or "Ports (COM & LPT)". The cable announces itself as one of:

CH340 / CH341 — Chinese-made clone with the WCH UART chip
PL2303 — Prolific UART chip (used on some clones)
FT232 / FT-series — FTDI chip (genuine Mitsubishi cable usually)
USB Serial Device — Windows-supplied generic driver, sometimes works on later Win11 builds

The chip identity dictates which driver to install.

Step 2 — install the right driver

CH340 / CH341: download from WCH's official site (wch.cn / wch-ic.com). Look for "CH341SER" or "CH343SER" depending on chip variant. Run the installer; reboot if prompted.
PL2303: download from Prolific's official driver page. Note that older PL2303HXA chips were declared end-of-life by Prolific and the modern driver refuses to load them — that's the #1 reason clone PL2303 cables fail on Windows 10 / 11.
FT232 / FTDI: install the VCP (Virtual COM Port) driver from FTDI's official site (ftdichip.com). FTDI drivers are signed and reliable.
Genuine Mitsubishi USB-SC09 / USB-SC09-FX: Mitsubishi ships a dedicated driver bundle on the cable's CD or via the Mitsubishi customer download portal. Use this in preference to a generic FTDI driver.

Step 3 — verify

Plug the cable in. Open Device Manager → "Ports (COM & LPT)". You should see an entry like:

"USB-SERIAL CH340 (COM5)"
"Prolific USB-to-Serial Comm Port (COM7)"
"USB Serial Port (COM4)" — FTDI

Note the COM number — you'll need it in GX Developer / GX Works2.

Step 4 — note common Windows 11 driver-signing issues

Windows 11 has tightened driver-signing enforcement. Symptoms of a signing-related failure:

Cable shows in Device Manager with a yellow warning triangle
Code 52 ("Windows cannot verify the digital signature for the drivers required for this device")
Cable disappears from Device Manager after a few seconds

The fix path depends on driver source:

Try the WCH / Prolific / FTDI latest driver — often resolves signing issues with current builds.
If using a Mitsubishi-supplied driver from a 10-year-old CD, replace it with the latest from Mitsubishi's portal.
As a last resort, boot Windows 11 with "Disable driver signature enforcement" via the Advanced startup options, install the driver, then reboot. Note that signed drivers are strongly preferred for production work.

Setting the COM port number

If GX Developer / GX Works2 only enumerates COM1 through COM10, and Windows assigned the cable to COM12, you'll need to remap it. In Device Manager:

Right-click the cable's COM-port entry → Properties.
Port Settings tab → Advanced.
Change "COM Port Number" to a free low-numbered port (COM3, COM4, etc.).
Apply, close, replug the cable.

This step trips up first-time SC09 users every week. If GX Developer says "no PLC response" but the cable is plugged in and the CPU is powered, the COM number is the first thing to check.

Configuring transfer setup in GX Developer / GX Works2

GX Developer

Online → Transfer Setup.
PC side I/F: Serial USB.
Click the Serial USB icon → set "RS-232C" or "USB" depending on your cable variant. Most USB-SC09 setups select USB here even though the cable presents as a virtual COM port — counter-intuitive but correct.
Set the Transmission speed to 19.2 kbps for FX2N (38.4 kbps if the CPU and cable support it; FX3U and later support faster).
PLC side I/F: PLC Module. Select the FX-series target.
Connection Test. If the cable, driver, and CPU all line up, the test reports success and the CPU model is recognised.

GX Works2

Online → Transfer Setup.
PC side I/F: Serial USB (same icon as GX Developer).
The dialog usually offers USB-SC09 / USB-SC09-FX as a direct option — pick it. If only a generic "Serial" option appears, fall back to the COM-port approach: select Serial, pick the COM number Windows assigned, set baud to 19200 / 38400 / 115200 to match the CPU.
PLC side I/F: PLC Module.
Connection Test verifies end-to-end.

Project CPU type must match

A common failure: Connection Test passes, but read / write fails because the project was created for FX3U and the connected CPU is an FX2N (or vice versa). Always confirm the project CPU type matches the live CPU before download.

"PLC No Response" troubleshooting checklist

When the connection test or download fails with a generic timeout, work through this in order:

Cable plugged into PLC programming port? Mini-DIN-8, not the spare RS-485 port on the FX2N-485-BD if installed.
PLC powered up? Check the POWER and RUN LEDs.
CPU in RUN mode? Some operations need RUN; others need STOP. CPU-front-panel switch position matters.
Driver showing in Device Manager with no warning triangle?
COM port number matches what GX Developer / GX Works2 is configured to use?
No other application holding the COM port open? Close any HMI design tool or terminal program.
Baud rate matches between cable, driver, and PLC? Default is 19.2 kbps; some FX3U configurations use 38.4 or 115.2 kbps.
Project CPU type matches the connected CPU?
Cable seated firmly at both ends? The Mini-DIN-8 connector seats deeper than feels right.
Try a different USB port on the laptop, especially USB 2.0 vs USB 3.0. Some clone cables behave better on USB 2.0 ports.

If none of those resolve, swap to a known-good cable. A spare USB-SC09-FX in your toolbox saves hours of guessing.

When to switch to Ethernet

The USB-SC09 is fine, but Ethernet-equipped CPUs are objectively better when available:

FX3U-ENET / FX3U-ENET-L — Ethernet adapter for FX3U; allows programming over LAN
FX5U built-in Ethernet — programming over the network is the default

If you're maintaining a panel that already has an FX3U-ENET-L installed, configure GX Works2 to transfer over Ethernet instead of USB. It's faster, more reliable on Windows 11, and works over a remote VPN if your customer's site is set up for it.

Pinout — what's actually on the wire

The Mini-DIN-8 connector on the FX-series CPU exposes RS-422 differential signalling. Pin layout (looking into the female socket on the PLC):

Pin 1 — RD- (receive negative)
Pin 2 — RD+ (receive positive)
Pin 3 — Not connected (some variants)
Pin 4 — SD+ (send positive)
Pin 5 — SD- (send negative)
Pin 6 — SG (signal ground)
Pin 7 — VCC (5 V supply, used by some HMIs)
Pin 8 — Not connected

The USB-SC09 cable hides this from you — the laptop sees a virtual COM port and the cable does the RS-422 ↔ USB conversion internally. You only need the pinout if you're building a custom interface or diagnosing a damaged port.

Summary

The USB-SC09 / USB-SC09-FX is the workhorse Mitsubishi FX-series programming cable. Get the right variant for your hardware, install the matching driver from the chipset vendor (WCH, Prolific, or FTDI) or from Mitsubishi for the genuine cable, set the COM port number low, configure Transfer Setup in GX Developer / GX Works2, and run the Connection Test before attempting a download. When something fails, work the checklist top-to-bottom rather than guessing — the same five issues account for most failures. For broader FX2N maintenance context see the Mitsubishi FX2N legacy programming guide; for modern FX work see the Mitsubishi FX5U programming tutorial.

Mitsubishi USB SC09 Cable Setup: Driver, COM Port, and Troubleshooting (2026)