User`s manual

PK220066 s Troubleshooting
Out of the Box
Check the items mentioned in this section before starting development.
 Verify that the PK2200 runs in standalone mode before connecting any
expansion boards or I/O devices.
 Verify that the entire host system has good, low-impedance, separate
grounds for analog and digital signals. Often the controller is con-
nected between the host PC and another device. Any differences in
ground potential from unit to unit can cause serious problems that are
hard to diagnose.
 Do not connect analog ground to digital ground anywhere.
 Double-check the connecting ribbon cables to ensure that all wires go
to the correct headers.
 Verify that the host PCs COM port works by connecting a good serial
device to the COM port. Remember that COM1/COM3 and COM2/
COM4 share interrupts on a PC. User shells and mouse drivers, in
particular, often interfere with proper COM port operation. For
example, a mouse running on COM1 can preclude running Dynamic C
on COM3.
 Use the supplied Z-World power supply. If another power supply must
be used, verify that it has enough capacity and filtering to support the
PK2200.
 Use the supplied Z-World cables. The most common fault of user-
made cables is failure to properly assert CTS at the RS-232 port of the
controller Without CTSs being asserted, the controllers RS-232 port
will not transmit. Assert CTS by either connecting the RTS signal of
the PCs COM port or looping back the PK2200s RTS.
 Experiment with each peripheral device connected to the controller to
determine how it appears to the controller when powered up, powered
down, and/or when its connecting wiring is open or shorted.
 If a DB9 connector or an RJ-12 connector is wired up to a 10-pin
connector, carefully check the connections. These wires do not run
pin-for-pin.
Note: Telephone company wiring does not follow a standardized color
code.