Filter
Top Products
Page - 9
A Appendix 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 between
eMCee and the hardware controller. Before troubleshooting the eMCee soft-
ware, please make sure that all your connections between the computer and
the hardware controller are properly setup. Follow thru the list below for the
most common hardware checks:
• The Serial cable is plugged into the serial port.
• The DB-25 pin end of the Serial cable is plugged into the Sin8 converter (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 RJ-45 cable is plugged into the serial input on the
controller.
I HAVE CHECKED ALL MY SERIAL CONNECTIONS AND THE CONTROLLER STILL ISN’T RESPONDING?
Once you have checked your serial connections, a non-responding controller
may be the result of the wrong serial port selection in the eMCee preferences.
Please verify that the serial port which your cabling is plugged into is the same
serial port selected in eMCee’s preferences.
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 also 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 preferences in eMCee are set for your configuration, if the controller
will still not respond, the culprit in most cases, is a system extension conflict.