S - what can go wrong when loading tasks and files, Appendix s, What can go wrong when loading tasks and files – Rockwell Automation 57C620 AutoMax Programming Executive Version 3.8 User Manual

Page 291: S.1 error messages on the personal computer screen

Advertising
background image

SĆ1

What Can Go Wrong When Loading Tasks and Files

Appendix S

What Can Go Wrong When

Loading Tasks and Files

This appendix describes some problems you might encounter when loading

tasks and files to the rack.

S.1

Error Messages on the Personal Computer

Screen

Error messages that appear on the personal computer screen are

usually specific enough to help you pinpoint any problems you are

experiencing. In most cases error messages are also specific to the

operation that was in process when the error occurred. When you

see an error message on the screen during any loading operation,

first write down the message. Then, after checking to make sure

your connection to the rack is good, and that you are loading the

correct file to the designated Processor or UDC module, reĆtry the

operation. Generally, it is best to load every file (except operating

system files, which are loaded separately) and task to the rack at

one time using the LOAD ALL option.
This section will describe errors that might be difficult to resolve

using error messages only. The section is organized by when the

error could occur. However, if you load tasks and files to the rack

using the LOAD ALL command, you might see any of these errors

during the procedure.

S.1.1

Errors that Occur When Loading an AutoMax

Processor Operating System or UDC Operating

System

In most cases, errors that occur when loading an operating system

to the rack are due to improper cabling or high Processor or UDC

utilization (a combination of large tasks executing very fast,

accompanied by error code 00" on a Processor faceplate). Always

make sure that you have a good connection between the personal

computer and the rack before trying to communicate with the rack.

In addition, it is good practice to stop any tasks that are running in

the rack (using the STOP ALL command) before trying to reĆload an

operating system to the rack. In most cases, reĆtrying the loading

operation will be successful. In rare cases, it may be necessary to

replace a Processor module or UDC module in the rack.

S.1.2

Errors that Occur When Loading a Rack

Configuration or Drive Parameter Object File

Errors that can occur when loading a rack configuration are usually

due to a mismatch between the actual hardware in the rack and

what is described in the configuration. For example, it is possible

that the configuration describes a hardware module that was

mistakenly placed into the wrong slot in the rack, or one that was

not installed in the rack at all. It is also possible that the

configuration file or parameter object file is actually meant for

Advertising