If Communication Over Sscnet Fails With Doscp - Mitsubishi Electric MELSEC System Q Installation Manual

5. TROUBLESHOOTING
5.3

If communication over SSCNET fails with DOSCP

No.
Communication error "50" or "51" occurred.
1
Communication error "10" occurs.
2
Communication error "-255" occurs.
3
Phenomenon
• SW3RN-SNETP is not booted.
Boot SW3RN-SNETP.
• SW6RN-SNETP (Ver. 00B or later) has been booted.
Exit from SW6RN-SNETP (Ver. 00B or later) and boot
SW3RN-SNETP.
When SW3RN-DOSCP is in use, the phenomenon described
on the left may occur.
• Refer to "3.7 Updating Instructions and Procedures" and
update one set of SW3RNC-GSVE.
After that, boot SW3RN-DOSCP.
• When SW3RN-DOSCP is in use, follow the remedy since
the possible cause is any of the following 1) to 5).
1) SNETP of an early version is used.
Uninstall the early version and install the new version of
SNETP that supports the A motion. (*1)
2) Two or more copies of SNETP of different versions are
installed.
Uninstall all copies of SNETP.
If any system directory (file) of SNETP remains after they
are uninstalled, delete using Explorer or the like.
Next, install only one copy of SNETP of a version that
supports the A motion. (*1)
3) Both SW3RN-SNETP and SW6RN-SNETP are installed
in one PC.
Uninstall both SW3RN-SNETP and SW6RN-SNETP and
install either one again. (*1)
4) Windows 98, Windows NT and Windows 2000 are
installed in one PC and SNETP of different versions is
installed in each drive.
Uninstall all copies of SNETP then install SNETP of a
single version that supports the A motion to both the
Windows 98 , Windows NT and Windows 2000 drives.
(*1)
5) Windows 98, Windows NT and Windows 2000 are
installed in one PC and SW3RN-SNETP and SW6RN-
SNETP are installed in each drive.
Uninstall all copies of SNETP then install SNETP of a
single version that support the A motion to both the
Windows 98, Windows NT and Windows 2000 drives.
(*1)
5 − 4
Cause and remedy