Page - 9
AAppendix A:

Troubleshooting eMCee™

THE EMCEE SOFTWARE DOES NOT RECOGNIZE THE CONTROLLER?
The error message that the controller is not responding or that it is not a
known controller indicates a break” in the serial communications bet ween
eMCee and the har dw ar e c ontroller. Bef or e trou bleshooting the eMCee soft-
war e, please make sur e that all y our co nnections between the computer and
the hardw ar e contro ller are pr operly setup . F o llow thru the list below f or the
most common hardware checks:
The Serial cable is plug ged into the serial port.
The DB- 25 pin end of t he Serial cable is plugged into the Sin8 conv erter (blue).
The slide switch on the converter is in the “P” position.
The one end of the flat RJ-45 cable is plugged into the Sin8 Converter.
The other end of the flat R J-45 cable is plugged into the serial input on the
controller.
I HAVE CHECKED ALL MY SERIAL CONNECTIONS AND THE CONTROLLER STILL ISNT RESPONDING?
Once you have checked your serial connections, a non-r esponding controller
may be the result of the wr ong serial port selection in the eMCee pref erences .
Please verify that the serial port which your cabling is plugged into is the same
serial port selected in eMCees prefer ences.
For Macintosh users: Under the Apple Menu go to Control Panels -
AppleTalk. In the Apple Talk Control Panel, make sure that Appletalk is not
trying to use the port eMCee is using. If the serial port is being used by
AppleTalk, change the port or disable AppleTalk in the Chooser.
ApplePowerBooks: ApplePowerBooks have a combination Printer/Mo-
dem port. The eMCee software will only recognize the port when the Mo-
dem port is the selected serial port in eMCee’s preferences. PowerBook users
must al so make AppleTalk inactive when using eMCee.
ALL MY CONNECTIONS AND PREFERENCES ARE SET BUT STILL THE CONTROLLER IS NOT RESPONDING?
Once you have verified that the controller connections are appropriate and
that the pref erenc es in eMCee are set f or y our c onfiguration, if the c ontroller
will still not respond, the culprit in most cases, is a system extension conflict.