Responding to Displayed Error Messages
Section 7-2
7-2 Responding to Displayed Error Messages
When the NT20 displays an error message, find the corresponding symptoms in the appropriate table below and respond by following the “Remedy” indicated in the table.
7-2-1 Errors Occurring When the Power Is Turned ON
The table below shows the errors that can occur when the power supply to the
NT20 is turned ON, and their remedies.
Message
Screen Data
Corrupted
Mark Data
Corrupted
No direct information is set!
Cause
There is an error in the registered screen data.
Remedy
After initializing the screen data memory in the Maintenance Mode, transmit the screen data once more with the
Support Tool.
There is an error in the registered mark data.
After initializing the screen data memory in the Maintenance Mode, transmit the screen data once more using the
Support Tool.
The allocated words for the
PT status control area and
PT status notify area have not been set.
Use the Support Tool to set the head words of the PT status control area and
PT status notify area, and transmit the screen data again.
There is no screen data. Transmit screen data from the Support
Tool.
7-2-2 Errors Occurring during Operation
The table below shows the errors that can occur during operation of the NT20, and their remedies.
Message
Setting Error
QQ command is not available
Cause
Bits or words allocated to the
PLC memory cannot be found in the screen data.
The PLC cannot be connected to the NT20.
Remedy
Check the memory area in the
PLC used and correct the bit and word allocations in the screen data.
Select a type of PLC that can be connected to the NT20.
7-2-3 Errors Occurring on Screen Data Initialization
The table below shows the errors that can occur when data is written to the
NT20 screen data memory, and their remedies.
Message
Initialization Error
Cause
Hardware fault or screen data memory life reached
Remedy
If the same message is displayed even after executing screen data memory initialization or screen data transmission several times, contact your OMRON service center.
249
Responding to Displayed Error Messages
Section 7-2
7-2-4 Errors Occurring on Resource Transmit Mode
The table below shows the errors that can occur when erasing resource, downloading resource or when NT20 is power on, and their remedies.
Message
Erasing failed.
Downloading failed.
Resource Error!
Cause
Hardware fault or resource memory life reached
Noise caused data corruption during communications
Resource is missing or fragmentary. Checksum of
Resource is wrong. There are any two items unmatched among system program, Font
Data and System Information
Data.
Remedy
Push the reset switch and erase again. If the same message is displayed even after executing erase several times, contact your OMRON service center.
Push the reset switch and download again. Use noiseresistant cable if communications occurs in an environment with high levels of noise.
Turn ON the DIP switch 2-5 and push the reset switch to download resource.
7-2-5 Errors Occurring on System Program Transmit Mode
The table below shows the errors that can occur when erasing system program, downloading system program or when NT20 is power on, and their remedies.
Message
Erasing failed.
Communications
Error Time Out
System program error!
Cause
Hardware fault or resource memory life reached
The connectors or the connecting cable have become disconnected.
The power to the NT20 is switched off, or the NT20 is reset, during transfer.
The power to the personal computer that is running the system transfer tool is switched off, or the personal computer is reset, during transfer.
The cable connecting the personal computer running the system transfer tool and the
NT20 becomes disconnected or sustains a wire breakage during transfer.
Transfer is terminated by pressing any two of the function keys on the panel of the
NT20.
Transfer is terminated by pressing the ESC key of the personal computer running the system transfer tool.
Remedy
Push the reset switch and erase again.
Reconnect the cable. Push the reset switch and download again.
Please download system program again.
250
Responding to Displayed Error Messages
Section 7-2
7-2-6 Communications Errors
This section describes the errors relating to communications with the PLC/
Host that can occur during operation, and their remedies.
• Operation When a Communications Error Occurs
When a communications error occurs, the error message is displayed at the NT20, and the buzzer sounds. Error messages are displayed when the
“Automatic Reset” memory switch is not set.
Some error messages are displayed even if the “Automatic Reset” memory switch is set.
• Procedure When a Communications Error Occurs
When an error message is displayed, press the [EXIT] touch switch displayed on the screen. The screen display will return to the RUN mode.
• Display of Communications Errors
As shown below, communications errors are displayed in the center of the screen, together with a classification indicating whether they are receive or send errors.
Screen When an Error Has Occurred while Receiving
RECEIVING ERROR
EXIT
<Error Description>
Parity Error
Overrun Error
Overflow Error
Framing Error
Buffer Overflow
Time Out
NAK Received
Unit No. Error
FCS Error
Screen When an Error Has Occurred while Sending
RECEIVING ERROR
<Type of error>
Time Out
EXIT
Message
(ACIA)
Parity Error
Framing Error
Overflow Error
Overrun
Buffer Overflow
(NT20-ST128 only)
Cause
Communications parameters/ conditions of communications set incorrectly.
Noise caused data corruption during communications.
Remedy
Check whether the parity bit, frame length, baud rate, stop bit length, and flow control settings of the PLC match the settings of the NT20.
Use a noise-resistant cable if communications occurs in an environment with high levels of noise.
Reconnect the cable.
The connectors of the connecting cable are not connected correctly.
The NT20 receive buffer is full.
Lengthen the command transmission intervals. If this error occurs frequently, set flow control for communications.
251
Responding to Displayed Error Messages
Section 7-2
Message
Time Out
NAK Received
(end code simultaneously displayed)
Unit No. Error
FCS Error
Cause
The connectors of the connecting cable have become disconnected.
The PLC is stopped.
Remedy
Reconnect the cable.
During transmission of one command, a time lapse exceeding 5 seconds is detected.
Noise caused data corruption during communications.
Make sure the PLC is able to communicate with the NT20.
Confirm the proper command length.
Reconnect the cable.
Error returned by host.
The unit # does not match that set on the PLC.
The PLC is transmitting incorrect data.
Noise caused data corruption during communications.
Use a noise-resistant cable if communications occurs in an environment with high levels of noise.
Check the end code by referring to the PLC operation manual.
Set the PLC unit # to “0”.
Check PLC operation.
Use a noise-resistant cable if communications occurs in an environment with high levels of noise.
Check PLC operation.
The PLC is transmitting incorrect data.
Noise caused data corruption during communications.
Use a noise-resistant cable if communications occurs in an environment with high levels of noise.
252