|
When
the eBeam application launches, it communicates directly
with the hardware through the COM port. What this means
is that if the board can't be found there is either a physical
problem (hardware, serial cable, COM port, PC) or there
is another device holding the COM port open.
If
you are using a ThinkPad
or PalmPilot,
please go directly to either of these linked sections.
Physical
Components
The first step is to determine if a physical component
is causing the problem.
- Determine
if the hardware is functioning via the Initial
Diagnostic section. After reviewing this section,
return here if the hardware appears to be functioning
correctly.
-
The next component to rule out is the Serial Cable. After
reviewing this section, return here if your cable
meets the correct specifications.
- The third
component to check is the COM port.
- If another device, such as a modem or a PalmPilot
PDA ,
has used the COM port successfully, then the physical
COM port is fine and you probably have a logical
COM port conflict with another serial device.
- If the COM port has never been used, determine
if it is enabled in BIOS and configured correctly.
- The
final component to check is the PC. Because there
are so many variations regarding a PC's configuration,
there are also a variety of possibilities for something
configured within the PC to be conflicting with
eBeam that can't be accounted for.
To rule out the PC as the cause of the problem,
attach the eBeam
hardware to another PC. If
you connect eBeam to another PC and it too cannot
be found by the eBeam application, please contact Technical Support.
Logical
Components
At this point, if you have
checked your hardware and are still unable to establish communications with the hardware, you are
probably experiencing a COM port conflict (the most common of all problems).
Please view the COM port section.
If you believe it may be faulty hardware, or if you are uncertain what to do next, you
can walk through the eBeam Troubleshooting
Diagnostic or contact Technical Support.
|
