User guide

228
6000 Series Programmer's Guide
Troubleshooting Basics
When your system does not function properly (or as you expect it to operate), the first thing
that you must do is identify and isolate the problem. When you have accomplished this, you
can effectively begin to resolve the problem.
The first step is to isolate each system component and ensure that each component functions
properly when it is run independently. You may have to dismantle your system and put it
back together piece by piece to detect the problem. If you have additional units available, you
may want to exchange them with existing components in your system to help identify the
source of the problem.
Determine if the problem is mechanical, electrical, or software-related. Can you repeat or re-
create the problem? Random events may appear to be related, but they are not necessarily
contributing factors to your problem. You may be experiencing more than one problem. You
must isolate and solve one problem at a time.
Log (document) all testing and problem isolation procedures. Also, if you are having difficulty
isolating a problem, be sure to document all occurrences of the problem along with as much
specific information as possible. You may need to review and consult these notes later. This
will also prevent you from duplicating your testing efforts.
Once you isolate the problem, refer to the problem solutions contained in this chapter. If the
problem persists, contact your local technical support resource (see Technical Support below).
Electrical Noise
If you suspect that the problems are caused by electrical noise, refer to your 6000 product's
Installation Guide
for help.
Solutions to Common Problems
NOTES
Some hardware-related causes are provided because it is sometimes difficult to identify a
problem as either hardware or software related.
Refer to other sections of this manual for more information on controller programming
guidelines, system set up, and general feature implementation. You may also need to
refer to the command descriptions in the
6000 Series Software Reference
. Refer
to your product's
Installation Guide
for hardware-related issues.
Problem Cause Solution
Communication errors
(bus-based products).
1. Communication program looking for
card at wrong address.
1. Select correct address for communication program.
2. Address conflict. 2. Refer to the configuration instructions in your Installation Guide
(make
sure it is matched by the setup in Motion Architect,
if using Motion
Architect
)
3. AT6n00 card not properly seated. 3. Seat board properly in slot. Apply pressure directly over area with
gold card edge fingers.
Communication (serial)
not operative, or receive
garbled characters
1. Improper interface connections or
communication protocol.
1. See troubleshooting section in your product's Installation Guide.
2. COM port disabled. 2.a. Enable serial communication with the E1 command.
2.b. If using RS-485, make sure the internal jumpers are set accordingly
(see Installation Guide). Make sure COM 2 port is enabled for sending
6000 language commands (execute the PORT2 and DRPCHKØ
commands).
3. In daisy chain, unit may not be set to
proper address.
3. Verify DIP switch settings (see Installation Guide), verify proper
application of the ADDR command.
Computer will not boot
with AT6nn0 card installed.
1. Interrupt conflict.
2. See problem:
Communication Errors.
1.a. Turn interrupt DIP switches OFF.
1.b. Refer to the configuration instructions in your Installation Guide
(make sure it is matched by the setup in Motion Architect,
if using Motion
Architect
)