Configuring Omron NT20M PT Direct Information Areas

The NT20M returns to an operational project after both direct-information areas are assigned in the DOS NT Support Tool and the corrected file is transferred. The message NO DIRECT INFORMATION IS SET indicates missing project configuration after the terminal data was erased; it does not, by itself, identify a cable, DIP-switch, or serial-port fault.

Recovery prerequisites

Before anything else, confirm whether a usable NT20M project file exists. If it does, work from a backup copy. If it does not, create a new file, but recognize that setting the two special areas only clears this configuration fault; it does not reconstruct deleted screens, objects, messages, or application logic.

Do not start by changing DIP switches. The displayed message already identifies a missing project definition. Switch settings become relevant only if the subsequent transfer cannot establish communication. Do not move on until the correct project file or a deliberate new-project starting point has been identified.

NT20M project file preparation

1. Start the DOS NT Support Tool.
2. Open the recoverable NT20M project. If no project exists, create a new program file.
3. Check that the project target is the intended terminal before editing or transferring it.
4. Preserve an unchanged copy of any recovered project so address assignments can be compared or reversed.

A newly created file supplies a configuration container, not the erased machine application. If the terminal previously contained production screens, the practical recovery path is to locate the original project and apply the missing direct-area settings there.

Do not move on until the Support Tool displays the intended NT20M project and the file can be saved without an application error.

PT direct-area assignment

From the project screen, press F10 for Next, then press F2 for Direct. In the resulting dialog, specify the first two parameters:

Both entries are required. Do not invent address values merely to remove the message. An arbitrary address can overlap coils, registers, recipes, or machine commands even though the terminal accepts the project. Read the intended locations from the original NT project, PLC program, memory map, or machine documentation. For a new application, choose locations valid for the connected PLC and reserve every location occupied by each area according to the NT20M documentation.

The two areas form the shared control interface between the terminal and PLC. Erasing the terminal removed their definitions, so the NT20M cannot initialize direct operation and displays NO DIRECT INFORMATION IS SET. Do not move on until both fields contain reviewed, nonconflicting addresses.

Project save and terminal transfer

1. Accept the direct-area dialog after checking both entries.
2. Save the project file under a controlled filename.
3. Connect the programming computer to the NT20M using the interface and cable intended for the Support Tool transfer.
4. Place the terminal in the transfer-ready state required by the installed configuration.
5. Start the project transfer and wait for the Support Tool to report completion.
6. Return the terminal to its normal operating state or restart it if the transfer workflow requires that transition.

Do not interrupt power or disconnect the cable during the write. A saved computer file does not alter the terminal; the corrected project must be transferred successfully. Do not move on until the Support Tool reports a completed transfer rather than merely opening or saving the file.

Communication fault isolation

If the transfer does not start, separate the communication problem from the direct-information problem. The missing-area message is corrected in the project, while a failed transfer is diagnosed at the physical and serial-configuration layers.

1. Confirm that the cable is connected to the intended terminal and computer ports.
2. Verify that the cable type and pinout match the selected interface. A connector that fits mechanically does not prove signal compatibility.
3. Compare communication settings at both ends. The serial mode, data format, and rate must agree; read their actual values from the terminal configuration and Support Tool rather than guessing.
4. Check the terminal operating or transfer state. Normal runtime and programming transfer may require different terminal states.
5. Inspect DIP-switch positions against the NT20M hardware documentation for the installed connection. Record existing positions before changing anything, and change only the switch tied to a verified communication requirement.
6. Retry the transfer after correcting one condition at a time.

If the tool communicates but the terminal still shows the message, reopen F10 → F2 Direct and confirm that both parameters were stored in the file that was actually transferred. Do not move on until transfer completion can be repeated without a communication error.

End-to-end verification

1. Restart or return the NT20M to runtime and confirm that NO DIRECT INFORMATION IS SET no longer appears.
2. Confirm that the expected initial screen loads. If only a blank or newly created screen appears, the direct-area repair succeeded but the deleted application screens still require restoration from backup.
3. With the PLC connected, observe the configured control and notify locations using the PLC programming software.
4. Operate one safe HMI function and confirm the intended PLC-side response.
5. Trigger one safe PLC-driven display or control condition and confirm the intended terminal response.
6. Check that unrelated PLC data near the selected areas does not change. Unexpected changes indicate an address overlap or incorrect area assignment.

Do not release the terminal for service until the startup message is absent, bidirectional exchange works through the intended areas, and adjacent PLC data remains unchanged.

FAQ