Troubleshooting NS-Designer RS232 Connection to NS7/NS12 PT

1. Problem Overview

Engineers integrating Omron NS-series Programmable Terminals (NS7, NS8, NS10, NS12, NS15) with NS-Designer version 5 frequently encounter a "Cannot connect to PT" or "Communications Error" dialog when attempting to download a project over RS-232. The error is reported in NS-Designer after a 30-60 second timeout with messages such as 0x0C05 (Communications timeout) or a generic "Failed to establish connection with PT" prompt. Symptoms include:

• NS-Designer hangs at Transfer → Connect indefinitely
• Transfer dialog reports "PLC connection failed" even though the PT is powered and the screen is active
• FINS gateway service reports "Serial unit: Active" but the PC never receives a response from the PT node
• The same USB-to-Serial converter works with another Omron peripheral (e.g., CS1 / CJ2 via CSW1-CN226) but never establishes a session with the NS

This article isolates the most common root causes — wrong cable, mismatched protocol, and COM-port parameter drift — and provides the diagnostic sequence used by Omron-certified integrators.

2. System Architecture & Communication Paths

The NS7 and NS12 PTs expose a single RS-232C port (DB-9 male, port labeled COM1 on the rear faceplate) used for both project transfer and runtime Host Link / NT-Link communication to a PLC. The PC running NS-Designer v5 connects to this port through one of two paths:

1. Direct RS-232 using an Omron-branded serial cable and a physical COM port (or USB-to-Serial converter emulating COMx).
2. Ethernet (TCP) using NS-Designer's built-in FINS/UDP gateway on the NS's Ethernet port. This path bypasses the RS-232 stack entirely and is the recommended first step when verifying basic TCP/IP connectivity.

If Ethernet is unavailable or the customer specifically requires serial transfer, the RS-232 path must use an NT-Link 1:1 or Host Link (SYSWAY) protocol on the PT side. The protocol setting is configured in the PT itself under System Menu → Communication Settings → Serial Port A → Protocol, while the matching setting in NS-Designer is under PT Configuration → Communication → Serial Port A → Protocol.

3. Cable Selection: C200H-CN229 vs XW2Z-S002

Two cables are commonly cited in the field for NS-series PT connections:

• C200H-CN229 — 2 m, DB-9 female to DB-9 female, factory-configured for Host Link (SYSWAY) between a PC and an Omron PT or C-series/CJ-series CPU peripheral port. This is the cable most field engineers reach for first.
• XW2Z-S002 — 2 m, DB-9 female to loose-end or DB-9 male, sold under the XW2Z family for wiring-duct and PT applications. Pin assignments vary by sub-variant; the -S002 suffix designates a specific crossover used for NS/NT-series PTs running NT-Link 1:1.

The pin assignments are not identical. Using a C200H-CN229 against a PT configured for NT-Link will leave the SD/RD crossover disconnected, producing silent timeouts. Conversely, an XW2Z-S002 connected to a PT running Host Link will leave DTR/RTS handshaking floating, producing intermittent resets.

The PT-side DB-9 pinout for the NS-series is consistent with the standard Omron host-link convention: pin 2 = RD, pin 3 = SD, pin 5 = SG, pin 7 = RTS, pin 8 = CTS. If you are terminating a custom cable, follow the columns above rather than relying on cable-jacket labeling.

4. Pinout Reference — DB-9 Female (PC End)

Use this reference when building a replacement cable from scratch or when troubleshooting a suspected bad cable with a breakout box.

PC DB-9F (looking at sockets)
  1  CD  ───┐
  2  RXD   │   4 DTR ── 6 DSR ── 1 CD (loopback)
  3  TXD   │
  4  DTR ──┘
  5  GND ──────────── PT pin 5 (SG)
  6  DSR ──┐
  7  RTS ──┴── PC RTS to PT CTS (Host Link only)
  8  CTS ─────── PC CTS to PT RTS (Host Link only)
  9  RI  (unused)

5. Protocol Selection — NT-Link 1:1 vs Host Link

Choosing the wrong protocol is the single most common cause of an NS-Designer connection failure on a bench test. The PT will silently ignore any frame whose initial byte does not match the configured protocol's header.

5.1 NT-Link 1:1

• Native protocol of the NS-series PT serial port
• Point-to-point only; PT must be node 1
• Baud: 19200 (also supports 9600, 38400, 57600, 115200 in PT firmware ≥V4.0)
• Data: 8 bits, no parity, 1 stop bit (8-N-1)
• No hardware handshaking required
• Highest throughput for project transfer

5.2 Host Link (SYSWAY)

• Legacy protocol inherited from C-series PTs (NT-series)
• Multi-drop capable; PT node typically 0 or 1
• Baud: 9600 (default) or 19200
• Data: 7 bits, even parity, 2 stop bits (7-E-2)
• Requires full RTS/CTS handshaking — pin 7 ↔ pin 8 crossover mandatory
• Slower transfer; useful when migrating an NT31/NT631 project to NS hardware

5.3 Decision Path

1. Open the existing NS-Designer project file (.ipp) and check PT Configuration → Communication → Serial Port A → Protocol.
2. Match the PT System Menu setting to exactly the same protocol.
3. Select the matching cable from the table above.
4. If the project file is unavailable (recover-from-PT scenario), set the PT to NT-Link 1:1, 19200, 8-N-1, node 1 as the default; this is the most common factory state for the NS7/NS12.

6. NS-Designer COM Port Configuration

In NS-Designer v5, the PC-side serial parameters live under Transfer → Communications Setup → Serial. The dialog exposes:

If any field on this dialog disagrees with the PT, NS-Designer will not detect the mismatch — it will simply hang until its internal retry counter expires. Always click Test Connection after editing these fields. A successful test shows a green indicator and reads back the PT model and firmware version (e.g., NS12-V1, FW 8.10).

7. FINS Gateway Configuration

When the connection path is Ethernet, NS-Designer communicates through the FINS Gateway Service installed by the NS-Designer setup. The gateway routes UDP/TCP FINS frames between the PC's logical network and the target device's serial port. Confirm the following before opening NS-Designer:

1. Open FinsGateway Settings from the Start menu.
2. Expand Serial Unit — the COM port you intend to use must show Status: Active. If it shows Stopped, right-click and select Start Service.
3. Click Serial Unit → New if no entry exists, then map it to the COMx number assigned by Windows to your USB-Serial converter.
4. Set the baud rate and frame format to match the PT. For NT-Link 1:1 use 19200, 8-N-1; for Host Link use 9600, 7-E-2.
5. Set the local FINS node number to a value that does not collide with the PT (e.g., PC = 200, PT = 1).

8. USB-to-Serial Converter Considerations

Modern PCs ship without native DB-9 ports. The two most common USB-Serial chipsets in the field are:

Verify the converter electrically with a loopback test before suspecting the PT. Short pin 2 to pin 3 on the PC end of the cable, open NS-Designer Communications Setup, click Test Connection, and confirm the dialog reports echoed bytes. A counter-based diagnostic utility such as Windows HyperTerminal, PuTTY (Serial mode), or Tera Term with echo enabled is a faster verification than waiting for NS-Designer's 60-second timeout.

9. Step-by-Step Troubleshooting Procedure

Execute the following sequence in order. Each step ends with a binary Pass / Fail gate — if a step fails, do not advance; the failure mode is itself diagnostic.

Step 1 — Verify Windows COM Port Assignment

1. Open Device Manager → Ports (COM & LPT).
2. Confirm the USB-Serial adapter appears (e.g., USB Serial Port (COM4)).
3. If the device has a yellow exclamation mark, reinstall the chipset driver.
4. Right-click → Properties → Port Settings → Advanced and force a COM number between COM1 and COM9 to avoid legacy Windows path conflicts.

Step 2 — Loopback-Test the Cable

1. Disconnect the cable from the PT.
2. Short pin 2 to pin 3 (TD ↔ RD) at the PT end of the cable.
3. Open PuTTY in Serial mode at 19200 8-N-1, no flow control.
4. Type characters; each character must echo locally. If not, the cable or converter is bad.

Step 3 — Verify PT System Menu Protocol

1. Power the NS7/NS12 and tap the upper-left corner four times within three seconds to enter the System Menu.
2. Navigate to Comm. Settings → Serial Port A.
3. Record: Protocol, Baud, Data bits, Parity, Stop bits, Node No.

Step 4 — Match NS-Designer to PT Settings

1. In NS-Designer, open the project file.
2. Go to PT Configuration → Communication → Serial Port A.
3. Set each parameter to match Step 3 exactly.
4. Save and click Transfer → Communications Setup → Test Connection.

Step 5 — Validate FINS Gateway

1. Open FinsGateway Settings.
2. Confirm Serial Unit is Active and bound to the COM number from Step 1.
3. Set baud and frame format to match the PT protocol.

Step 6 — Attempt Transfer

1. In NS-Designer, choose Transfer → Download to PT.
2. Select Serial as the transport.
3. If transfer starts, the connection is healthy; complete the project download.
4. If transfer times out, capture the error code and consult the matrix in Section 11.

10. Verification Tests

Once a successful transfer has completed, run the following sanity checks before commissioning the line:

1. Round-trip project download: Read the project back from the PT via Transfer → Upload from PT and diff against the original .ipp file. Any difference indicates partial transfer or noisy line.
2. Online edit test: With the PT connected, change a tag value from NS-Designer's Monitor view and confirm the screen updates within 200 ms.
3. Power-cycle persistence: Power off the PT for 30 seconds, restore power, and verify the downloaded project boots and the serial session can be re-established.
4. Noise margin test: Run the production machine and any VFDs in the cabinet. Re-establish the NS-Designer session. If the link drops, install a shielded cable and ground the shield at the PT end only.

11. Fault Code Matrix

12. FAQ