Omron NT20M-DT131 Transfer Mode Lock: Screen Memory Init Fix

1. Problem Overview — NT20M-DT131 Transfer Mode Inaccessible

The Omron NT20M-DT131 programmable terminal is a 5.7-inch monochrome STN LCD operator interface from the legacy NT20M/NT2000M family. The unit accepts screen data uploads and downloads through a detachable communication adapter — in the failure case described here, an NT600M-LK201 serial (Host Link / RS-232C) interface unit is installed. The reported symptom is:

• The System Menu opens normally when the operator presses the system-menu touch zone at power-up.
• Selecting Transfer Mode from the System Menu produces no state change; the unit remains in the System Menu.
• The display shows the banner: Screen Data Corrupted.
• The NTSS V2.33 transfer tool on the host PC cannot complete a transmit (download) operation, even when initiated from the PC side first.

This is a known multi-fault condition: the unit's on-board screen-data flash memory has lost integrity, and one or more hardware DIP switches on the rear of the display are mis-configured, blocking the menu-driven path to transfer mode. Both must be addressed. Source resolution path comes from the NT20M/NT2000M Operation Manual (V001-E1-02), Section 7 (Transferring Screens Online) and Section 8 (Troubleshooting and Basic Maintenance).

2. Affected Hardware, Firmware, and Tooling

3. Root Cause Analysis — Two Independent Faults

The symptom set indicates two overlapping faults that must both be cleared. Diagnosing only one will leave the unit non-recoverable from the operator side.

3.1 Fault A — Screen Data Memory Corruption

The Screen Data Corrupted message is generated by the PT's boot-time self-test when the checksum or signature of the screen-data block fails to validate. Common contributing causes:

• Power removed mid-write during a previous NTSS transfer.
• Battery-backed SRAM (where applicable) has been allowed to discharge below the data-retention threshold.
• Firmware/handshake mismatch between an older NTSS revision and the unit's PROM.
• Flash write-cycle exhaustion (rare on NT20M, but observed after tens of thousands of partial updates).

Until the corrupted block is wiped, the PT will refuse to enter Transfer Mode even if the operator forces it through the menu — the boot loader short-circuits to the corruption handler.

3.2 Fault B — DIP Switch 6 in Wrong Position

The 8-position DIP switch on the rear of the NT20M body controls host-protocol selection, screen-data protection, and the Transfer Mode entry gate. The critical bit in this failure mode is:

If SW6 is OFF, the System Menu does not allow selection of Transfer Mode — the menu item either does not appear, or selecting it returns the operator to the System Menu. The firmware treats SW6=OFF as a hard interlock, which is exactly the symptom described.

4. Pre-Procedure Verification and Safety

Before opening the unit, verify the following to avoid wasted cycles and to protect stored data:

1. Confirm the host PC has NTSS V2.33 installed and that the project to be transferred opens without errors.
2. Inspect the RS-232C cable for bent pins; the NT600M-LK201 uses a D-sub 9-pin female connector with standard Host Link pin-out (2=TXD, 3=RXD, 5=GND, 4=CTS, 6=RTS — verify against the operation manual).
3. Verify supply voltage at the PT terminals: 24 VDC ±10% for the NT20M-DT131. Brown-outs during transfer are a leading cause of new corruption events.
4. Identify the DIP switch bank on the rear of the main body (not on the LK201 adapter — the LK201 has its own setting, but it does not control Transfer Mode gate).
5. Power down before changing any DIP switch position. Changes made while powered are not guaranteed latched until the next power cycle.

5. DIP Switch Configuration Procedure

1. Power down the NT20M-DT131 and disconnect 24 VDC.
2. Remove the rear cover to expose the DIP switch bank.
3. Record the current settings of SW1–SW8 for restoration later.
4. Set SW6 = ON. This is the single change required to re-enable menu access to Transfer Mode.
5. Verify SW7 (write-protect) is OFF for the duration of the transfer; otherwise the PT will reject the download.
6. Leave SW8 in its prior state for now (do not use SW8 to force initialization until the menu-driven path is attempted first).
7. Reinstall the rear cover, restore 24 VDC, and allow the PT to boot to either the user screen or the System Menu.

With SW6=ON, the Transfer Mode option in the System Menu becomes selectable. The next task is to clear the corruption so the menu can actually reach the transfer state.

6. Step-by-Step — Initializing Screen Data Memory

With SW6=ON and power cycled, perform the following sequence exactly. The Maintenance Menu is reached from the System Menu and is the only path that initializes the screen-data block.

1. Hold the upper-left touch zone while applying 24 VDC, or — if a user screen is running — press the system-menu touch zone. The System Menu appears.
2. Use the on-screen arrow keys to navigate to Maintenance Menu and press SET.
3. From the Maintenance Menu, select Init Screen.
4. Select Initialize Screen Data Memory. The PT prompts for confirmation.
5. Press YES (or SET, depending on firmware rev) to confirm. The screen-data block is wiped and re-initialized to factory state. This takes 5–15 seconds.
6. Wait for the PT to return to the Maintenance Menu completion message: Screen Data Memory Initialized.
7. Power down the PT.
8. Restore DIP switches to original positions except: leave SW6=ON and SW7=OFF until the new project has been transferred successfully.
9. Apply 24 VDC and proceed to Section 7.

7. Restoring Transfer Mode Access and Connecting to NTSS

1. With SW6=ON and the PT at the freshly initialized screen, enter the System Menu again.
2. Select Transfer Mode. The PT now transitions into Transfer Mode and displays Transferring… or shows a node number, depending on firmware revision.
3. On the host PC, launch NTSS V2.33.
4. Configure the COM port: 9600 bps (default), 7 data bits, even parity, 2 stop bits for Host Link (default). Unit number = 00 unless SW1–SW4 specify otherwise.
5. Open the target .ntw project.
6. Select Transfer → Transmit to PT (or press the transmit icon). Confirm any overwrite prompt.
7. Monitor progress in the NTSS status bar. A 320×240 monochrome project typically transfers in 30–90 seconds.
8. Wait for Transfer Complete, then power-cycle the PT from NTSS (or manually) to load the new project.

8. Upload Path (Recovery Without Existing Project)

If the on-host project has been lost, the same Transfer Mode enables an upload. From NTSS:

1. Select Transfer → Receive from PT.
2. Specify a destination filename.
3. Execute. The PT sends its current screen data — useful only if the project had not yet been wiped by the initialization in Section 6.

9. Verification Procedure and Acceptance Test

10. Related Transfer Errors and Diagnostics

Where transfer still fails after Section 6, cross-reference the failure message against the Omron manual's transfer-error table and the ProFace transfer-error reference (which mirrors similar RS-232C failure modes):

For an additional cross-vendor reference on RS-232C transfer-error categories (module-missing, mid-transfer abort, framing error), see the ProFace GP-Pro EX transfer-error troubleshooting page. Although the product family differs, the underlying serial-transfer fault model is identical.

11. Preventive Maintenance and Data Backup

• Maintain a versioned archive of every NTSS project file on the engineering network with checksum logging. A corrupted PT that can still enter Transfer Mode can be uploaded from, not only downloaded to.
• Add a small UPS or hold-up capacitor on the 24 VDC feed to the PT cabinet. Brown-outs during writes are the dominant cause of Screen Data Corrupted events.
• Label the PT's DIP switch bank at the cabinet with a laminated map of production settings. SW6 and SW7 are the two bits most often mis-set by maintenance technicians.
• Establish a change-control rule: SW6 is moved to ON only for the duration of an authorized transfer, then restored to OFF in production. SW7 follows the same pattern in reverse (OFF for transfer, ON for production).
• Log every transfer event with operator ID, project version, and time stamp. NTSS supports this via its project-history file.

12. Field-Commissioning Notes and Edge Cases

• If the LK201 has its own DIP switches, those control Host Link station number and terminator only — they do not affect Transfer Mode gate. Do not confuse them with the PT body's bank.
• Some early NT20M firmware revisions require SW8=ON to be set before the Init Screen procedure, in addition to the Maintenance Menu path. If the menu-driven Init Screen fails, set SW8=ON, power-cycle, allow the PT to wipe automatically, then power-cycle again with SW8=OFF before attempting transfer.
• Mixing an NT20M with a non-matching LK201 adapter (e.g., LK202 for Ethernet) requires CX-Designer, not NTSS. Confirm the adapter model before assuming NTSS V2.33 is the correct tool.
• Battery-backed SRAM variants retain data for years on a healthy CR2032-style cell. If the PT has been de-energized for more than the data-retention window, expect a corruption event on the next boot and follow Section 6.