Omron NS-RUNTIME - SOFTWARE, Руководство пользователя

Страница: 151 / 157

7-2 Troubleshooting Errors during NS-Runtime Operation
7-3
7-2 Troubleshooting Errors during NS-Runtime Operation
This section describes possible errors occurred during NS-Runtime operation and their
countermeasures.
This section explains errors specific to NS-Runtime. For information on other errors, refer to 5
Troubleshooting and Maintenance in the NS Series Programming Manual.
Symptom Cause Possible countermeasure
Cannot start a
project with the NS-
Runtime. The project model is not
NSA12/15-TX01[] or NS-Runtime. Change the project to NSA12/15-TX01[]
or NS-Runtime.
Or, transfer a project which model is
NSA12/15-TX01[] or NS-Runtime.
The project is not downloaded. Download a project using the screen
transfer function.
USB dongle is not connected. Connect the USB dongle provided with
the NS-Runtime.
Cannot display a
document. Adobe(R) Reader is not installed. Install Adobe(R) Reader.
An invalid file is specified. Specify a correct PDF file.
A document number, for which a
document file is not set, or a
document number out of range has
been specified.
Specify a correct document number.
The document display direction
address is turned OFF. Turn ON the document display direction
address. When selecting the document
display direction address, the document
will be refreshed only when the
specified address is ON.
Cannot check a
screen using the
data check of the
system menu. Screen data that you are trying to
check does not exist. Specify an existing screen data
number.
Cannot start up CX-
Programmer from
the system menu. CX-Programmer is not installed. Install the CX-Programmer.
Cannot start up
SwitchBox Utility
from the system
menu. SwitchBox Utility is not installed. Install the SwitchBox Utility.
Slow display refresh Frequent opening/closing of
screens and pop-up screens or
frequent switching of frames.
If screens or frames are switched or
pop-up screens are opened and closed
too frequently, the display may update
slowly and communications may be
delayed. Adjust the interval between
screen switches to prevent system
overload.
Frequent executing of macros
including READCMEM and
WRITECMEM that communicate
with the PLC.
Too many communication points or
inconsecutive addresses may slow
communications. Try to read and write
consecutive addresses all at once.
Short save cycle for the Internal
Holding Memory. Adjust the save cycle to prevent system
overload.
Operation is not
stable. The computer is malfunctioning,
e.g., due to noise. Use an environment with less noise.