Owner's manual
Hornet and Bee Installation Guide Installation
MAN-HRBEIG (Ver. 1.304)
www.elmomc.com
24
1. When wiring the traces of the above functions, on the Integration Board, the Returns of
each function must be wired separately to its designated terminal on the Hornet or Bee.
DO NOT USE A COMMON GROUND PLANE. Shorting the commons on the Integration
Board may cause performance degradation (ground loops, etc).
2. Inputs: The 6 inputs are optically isolated from the other parts of the Hornet/Bee. All 6
inputs share a single common “Return” (INRET - J1/15). To retain isolation, the Input Return
pin, as well as other conductors on the input circuit, must be laid out separately.
3. Outputs: The 2 outputs are optically isolated from the other parts of the Hornet/Bee. Each
output has a separate floating return (OUTRET1 - J1/17 for output 1 and OUTRET2 J1/16 for
output 2). To retain isolation, the Output Return pins, as well as other conductors on the
output circuit, must be laid out separately.
4. Return Traces: The return traces should be as large as possible, but without shorting each
other, and with minimal crossovers.
5. Main Power Supply and Motor Traces: The power traces must be kept as far away as
possible from the feedback, control and communication traces.
6. PE Terminal: The PE terminal is connected directly to the Hornet's heatsink or to the Bee's
2 PE strips on its lower board. In the Hornet, the heatsink serves as an EMI common plane.
The PE terminal should be connected to the system's Protective Earth. Any other metallic
parts (such as the chassis) of the assembly should be connected to the Protective Earth as
well.
7. Under normal operating conditions, the PE trace carries no current. The only time these
traces carry current is under abnormal conditions (such as when the device has become a
potential shock or fire hazard while conducting external EMI interferences directly to
ground). When connected properly the PE trace prevents these hazards from affecting the
drive.
Caution:
Follow these instructions to ensure safe and proper implementation. Failure to
meet any of the above-mentioned requirements can result in drive, controller
or host failure.