5. TROUBLESHOOTING
5
−
1
5. TROUBLESHOOTING
Remedies for trouble are described in this section.
Refer to this section when you are in trouble.
5.1
GSV[ ][ ]P or DOSCP does not start or it is terminated during operation
No
.
Phenomenon
Corresponding
Version
Cause and remedy
1
When monitor, DOSCP or other application is
started from the menu, the following message
describing failure to find "sscpdr.dll" is displayed.
•
Windows NT/2000
•
Windows 98
SW3RN-
GSV[ ][ ]P
SW3RN-
DOSCP
2
The communication starting procedure causes the
following error and termination of the process.
3
Even when a Jump icon (monitor, digital oscilloscope
or other applications for performing communication)
of GSV[ ][ ]P is clicked on, jumping does not occur.
(However, no error is caused.)
SW3RN-
GSV[ ][ ]P
1) SNETP is not installed.
Even if communication with the CPU is not made
actually, SNETP must be installed.
Refer to section 3.4.6(1) to install the best SNETP.
If communication is made only with the A motion,
install SW3RN-SNETP.
•
A list of applications for communication with the
CPU is displayed.
The following applications cause the phenomenon
described to the left. (Applications other than
those listed below operate without SNETP.)
GSV[ ][ ]P : Monitor, communication, program
editor, install, mechanical system
editor, test, backup, servo data
setting (for writing to servo
amplifier)
SW3RN-DOSCP: Digital oscilloscope
2) The PATH specified as the long name has been
described in AUTOEXEC.BAT.
*: Long name: Folder name of 9 or more characters
Describe the SNETP PATH before the PATH
specified as the long name, and always add
"%PATH%" before the part where the long name has
been specified. It is not required if it has already
been described.
(Example)
•
Before change
SET PATH="C:\Program Files\ABC;"
(*1)
SET PATH=%PATH%;C:\PROGRA~1\Snetp;
(*2)
•
•
After change
SET PATH=%PATH%;"C:\PROGRA~1\Snetp;"
SET PATH=%PATH%;"C:\Program Files\ABC;"
*: Always described the (wiggly line) part.
(*1): Long name PATH
(*2): SNETP PATH