Resolving Omron NT21 'Terminal Not Compatible' Error in NT

1. Problem Overview

The "Terminal not compatible" message is one of the most common blocking errors encountered when transferring (downloading) a compiled project file from Omron NT Support Tool to an NT21 programmable terminal. The download aborts immediately at the connection handshake stage, before any screens, macros, or system tables reach the HMI. In most cases the symptom is not a broken serial cable or a wrong COM port — it is a version mismatch between the System Program installed on the NT21 hardware and the System Version the project was compiled against in the NT Support Tool.

This article consolidates the field-proven resolution procedure, then expands it with version-identification tables, the System Program (firmware) update workflow, communication-parameter checks, a fault-to-cause matrix, and a verification checklist. It applies to the original NT21, the later NT21-V2, and legacy Omron PT-to-PLC hosts that share the NT Support Tool editor chain.

2. Root Cause Analysis

There are five distinct root causes that produce the "Terminal not compatible" string at download time. Identifying the actual one requires the engineer to inspect three independent variables: project System Version, host System Program version, and host hardware model code.

2.1 Project / Host System Version Mismatch

The NT Support Tool embeds a "System Version" inside every compiled .ntp project file. When the upload/download transfer reaches the NT21, the host returns its own System Version string. If the two strings do not match exactly, the tool rejects the transfer with the compatibility error.

2.2 Hardware Model Mismatch (NT11 / NT20 / NT30 / NT31 / NT631)

Selecting the wrong terminal model in File → New (or modifying the project header post-build) writes the wrong model code into the project. The NT21 will refuse a project built for an NT31, NT631, or other PT family even if the System Versions happen to match.

2.3 Original NT21 vs NT21-V2 Generation Gap

NT21 and NT21-V2 hardware are physically and electrically interchangeable in most mounting footprints but ship with different System Program branches. Projects compiled with V2-era tooling (NT Support Tool release 2.47 or later for the V2 product line) cannot be pushed to first-generation NT21 units without first downgrading the project to a compatible V1 System Version.

2.4 System Program (Firmware) Corruption

Power-loss during a firmware transfer, an interrupted System Program upgrade, or a failed recovery boot can leave the NT21 with a corrupted or partial System Program. The host then identifies as "unknown" or reports a shorter version number, producing the same compatibility error.

2.5 Memory Card / Transfer Tool Stale Data

If the project is being moved via a memory card or a non-Omron transfer utility (e.g., a Windows file copy rather than the NT Support Tool transfer function), the header bytes that store System Version may be overwritten or stripped, while the project body remains intact. The result is a corrupt project that triggers a compatibility refusal.

3. Affected Models, System Versions, and Supported Files

The following matrix enumerates the NT21 product lines and the System Program versions (System Version strings) compatible with each NT Support Tool release that ships an NT21 project template.

4. Prerequisites

1. NT Support Tool release matching the NT21 host System Version (V1: NT-ZA3EAT-V4 or V2: 2.47+). Install both the editor and the matching transfer utilities; older installers leave the wrong helper DLLs behind.
2. Serial cable: Omron XW2Z-200S or equivalent RS-232C D-Sub 9-pin cable with the standard NT21 pinout (TXD pin 2, RXD pin 3, GND pin 5, RTS/CTS handshake tied or jumpered per host DIP switch setting). Confirm part number on the cable label.
3. System Program file matching the target hardware revision. Download only from Omron eData — verify the part string on the terminal nameplate matches the firmware package folder.
4. Host PLC cable terminations: for bench programming without a PLC, fit terminating resistors or jumper handshake per the host PT manual (typical: 120 Ω across RS-422A, RTS-CTS shorted for RS-232C download ports).
5. Backup of the existing project (.ntp or exported .snt file) and any present terminal image data before any upgrade attempt.

5. Step-by-Step Resolution Procedure

Work through the steps in order. Each step contains a verification check before moving to the next; do not skip the verification even if the symptom appears resolved.

Step 1 — Confirm the Hardware Model and System Program Version

1. Power the NT21 and enter the System Menu by pressing the corner soft-key combination (typically the F1 + F4 keys held while powering on, or the dedicated SYS menu key on V2 units).
2. Navigate to System Information (varies by System Program release; commonly → Maintenance → System Information).
3. Record: Model Code, System Version, and ROM Check Sum exactly as displayed.
4. Compare the model code to the catalog suffix on the nameplate label. Mismatches point to a previous field-replacement or labeling error.

Step 2 — Compare to the Project System Version

1. In NT Support Tool on the engineering PC, open the suspect .ntp project.
2. Select Project → Properties → System Information.
3. Read the Project System Version field.
4. If the host and project strings differ, this is the root cause. Proceed to Step 3.

Step 3 — Re-target the Project to the Host Version

1. Close any open .ntp project; back up the file with a new name (e.g., projectname_v2_revA_backup.ntp).
2. Launch NT Support Tool and choose File → New → NT21. Confirm the dialog displays the correct generation (V1 versus V2) — this is determined by the catalog suffix and the System Program recorded in Step 1.
3. Choose Project → Properties → System Version and select the host-matching version.
4. If the NT Support Tool was originally opened against the wrong model, close every project, exit the tool, and re-launch so the project wizard initializes against the correct DLL set.

Step 4 — Re-import Application Content

1. Import the screens, macros, and tables from the backed-up project using File → Import → NT Project or the legacy Transfer upload from the live unit.
2. Validate every screen (F5 / Run-Time Validation).
3. Recompile (Project → Compile or Ctrl+F7). Address any compilation warnings before transfer.

Step 5 — Update the NT21 System Program If Necessary

If the host System Version is corrupt, partial, or below a level the new project requires:

1. From the System Menu, choose Maintenance → System Program Transfer.
2. Send the new System Program (.ntsys) file via the same RS-232C transfer function.
3. Do not power-cycle the terminal during transfer. Loss of power here causes the corruption described in §2.4.
4. After successful transfer, the terminal restarts. Re-verify Model Code and System Version (Step 1).

Step 6 — Configure Communication Parameters

The PT transfer speed and parity are independent of the runtime PLC link speed. Confirm both. Recommended download settings for the NT Support Tool are:

Step 7 — Perform the Transfer

1. In NT Support Tool, select Transfer → Download to PT.
2. Confirm the dialog matches the host (model code and System Version).
3. Click Start. The progress bar should pass through Connecting → Project Header → System Tables → Screens → Macros → Completion without halting on the compatibility check.
4. If the bar halts at Connecting, see §10 Troubleshooting Matrix.

6. Hardware Identification Field Reference

PT identification is straightforward but easy to get wrong in low-light cabinets. Use both the visible nameplate and the firmware-reported identifier.

DIP switch quick reference (typical NT21 layout — confirm against your unit's printed legend):

7. NT21 Display and Memory Specifications

Knowing the host capability envelope prevents the engineer from inheriting a project whose resource demands exceed what the targeted NT21 host can carry — which can also surface as a denial at transfer time (when the System Version check passes but memory verification fails).

8. Communication Parameter Verification Procedure

Misalignment between the PC, the NT Support Tool Transfer Setup, and the host DIP switches produces sub-symptoms that mimic a compatibility error (the dialog stalls at Connecting with no terminal identification returned). Run this checklist before assuming a System Version mismatch.

1. Verify the engineering PC COM port device number matches the NT Support Tool setting (Transfer → Transfer Setup → COM Port).
2. Verify the cable is a cross-over RS-232C cable (not straight-through). NT21 transfer port: pinout = TXD 2, RXD 3, GND 5, RTS 7, CTS 8.
3. Verify DIP SW1-3 selects the correct port (RS-232C for bench download).
4. Set SW1-1 ON so the terminal is in Stop / System Menu and ready to receive.
5. In the NT Support Tool transfer setup, set the correct COM port and click Test; the tool should report "Connected to PT".

9. Project Conversion Between NT21 V1 and V2

When the existing project was authored against the other generation, the cleanest path is a directed conversion.

V1 Project → V2 Host

1. Open the V1 project in NT Support Tool at its original V1 release.
2. Compile and export via File → Export → Legacy Project to a portable .snt file.
3. Open NT Support Tool V2 edition (2.47+) and select File → New → NT21-V2.
4. Import the .snt via File → Import → Legacy Project.
5. Resolve any screen-resource references flagged during import (often macro-namespace and lamp-prefix paths).
6. Re-validate, recompile, and transfer.

V2 Project → V1 Host

1. Trim any screens, macros, or features that exceed V1 capacity (see §7 table).
2. Save the project under a new filename reserved for the V1 target.
3. Open the trimmed project with the V1-capable NT Support Tool release and re-compile against System Version V1.
4. Import the result and transfer per §5.

10. Troubleshooting Matrix

Use this matrix to triage repeated or marginal cases. Each symptom lists its most common root cause and the corrective action with the success-verification check.

11. Verification and Commissioning Checks

After a successful transfer, complete this verification list before handing the terminal back to operations.

1. Version verification — SYS menu displays the same System Version string shown in Project → Properties.
2. Screen cycle — Cycle through every screen via the navigation button or macro. Confirm no Screen Not Registered or Address Over-range errors.
3. Touch calibration — Re-enter calibration from the System Menu and confirm the four corners track within 2 mm of physical input.
4. PLC link test — Toggle a known PLC address with a temporary screen button; verify the value updates within two poll intervals.
5. Backup — Upload the now-running project back to the PC (Transfer → Upload from PT) and archive the working .ntp on a versioned share.
6. Project transfer logs — Save the NT Support Tool transfer log file alongside the project for traceability.

12. Preventive Practices

Apply the following controls to prevent recurrence:

• Maintain a single canonical project library per terminal, with filename conventions that encode the System Version (e.g., line3_pt21_v2_4_19.ntp).
• Document the matching NT21 System Program file in the project's release notes.
• Tag the terminal's nameplate with the System Version last flashed to it; revisit the tag every time the firmware is updated.
• Use the Omron USB-serial adapter (or a known-good industrial USB-RS-232C converter) for all downloads, rather than random commodity converters.
• Cycle the DIP switches to OFF / ON / OFF during commissioning to confirm the resume-from-System-Menu behavior is well understood by every technician on shift.

13. Inline Topology — NT21 Bench Programming Connection

14. Related Documentation

Refer to the official NT21 Programmable Terminal Setup Manual (V068-E1-01) for the full setup, communication-recovery, and diagnostic procedures referenced throughout this article. Refer to the matching System Program release notes on Omron eData whenever transferring firmware, since host-side behavior changes are documented release-by-release.

15. FAQ