16
TROUBLESHOOTING
16.2 Troubleshooting
16.2.7 When no communication is available between the development environment (personal computer) and C Controller module
16 - 14
9
DEVICE DESCRIPTION
10
MULTIPLE CPU SYSTEM
OVERVIEW
11
MULTIPLE CPU SYSTEM
CONFIGURATION
12
CONCEPT OF MULTIPLE
CPU SYSTEM
13
COMMUNICATIONS
BETWEEN CPU
MODULES
14
PARAMETERS ADDED
FOR MULTIPLE CPU
SYSTEMS
15
STARTING A MULTIPLE
CPU SYSTEM
16
TROUBLESHOOTING
(2) When the C Controller module is not accessible from the development
environment (personal computer) by FTP
Check the following:
• Steps 1) to 4) of the flowchart in (1) in this section
• Priority of the task in the user program
(3) When Workbench or Tornado on the development environment
(personal computer) cannot be connected to the C Controller module
Check the following:
• Steps 1) to 4) of the flowchart in (1) in this section
• Settings of Workbench or Tornado
(1) If the problem cannot be resolved by taking actions with the C Controller
module executing a script file, check the script file and user program.
• Correct the script file and user program.
• Disable the script file execution.
( Page 16-22, Section 16.2.13)
Specify a correct script file and user program with special care. Specifying an
incorrect script file or user program may result in unreliable C Controller
module operation (the error status, communication failure, illegal error code
return, etc.)
(2) If a stop error occurs in another CPU in a multiple CPU system,
communication between the development environment (personal computer)
and C Controller module may be disabled.
In such a case, remove the cause of the stop error in advance.
For precautions on the functions and program debugging, and script files, refer to
the following.
C Controller Module User's Manual (Utility Operation, Programming)
To Next Page
Loading...
