IMDHMIControls LibraryShop main store

How-to

Wiring four drives to a shared 1756-OF8 analog return

Controllers and I/O Published 7 min read

Short answer

Yes, the four drives can share the return, because the 1756-OF8 already shares it internally: every RTN terminal is one common node, so all four loops sit on a single reference. Run a separate return conductor from each 1336 signal common to the module, and give each drive its own output channel.

On this page
  1. Do the four drives share one return on a 1756-OF8?
  2. Which terminals does each speed-reference loop use?
  3. Should you daisy-chain the drive commons instead?
  4. Can one output channel feed all four drives?
  5. How do you land the wiring, step by step?
  6. How do you verify the loops before releasing the drives?
  7. What if a reference reads wrong after the wiring is in?
  8. When should these references move off analog loops altogether?
  9. Questions asked

Yes, the four 1336 drives can share the module's return, because the 1756-OF8 shares it for you already: the module is a non-isolated design with one internal common behind its RTN terminals. What you decide is field layout. Land a separate return conductor from each drive's signal common on the module's RTN, give each drive its own output channel, and the four speed references stay independent even though all four loops share one electrical reference.

Do the four drives share one return on a 1756-OF8? #

Yes. The module is non-isolated: its RTN terminals at pins 5, 6, 15 and 16 are tied to one common inside the module, so all four drive loops already sit on a single electrical reference however you land the wires.

The ControlLogix analog I/O manual files the 1756-OF8 with the non-isolated output modules and shows one return network serving every channel; whichever RTN terminal you land on, you are on the same node. For a current output, the manual wires the field device in series between the IOUT-x terminal and RTN, which is exactly what a 1336 speed-reference loop is: out on the channel terminal, through the drive's input, home on the return. The sharing is fixed inside the module. The only decision left to you is where in the panel the four loops meet that common.

Which terminals does each speed-reference loop use? #

One pair per drive: the signal leaves on a channel terminal (IOUT-0 through IOUT-3 is a clean assignment for four drives), enters the 1336 analog input, and returns from the drive's signal common at TB-2 terminal 4 to any RTN terminal.

Loop Module signal terminal Drive return terminal Module return
Drive 1 IOUT-0 TB-2 terminal 4 RTN
Drive 2 IOUT-1 TB-2 terminal 4 RTN
Drive 3 IOUT-2 TB-2 terminal 4 RTN
Drive 4 IOUT-3 TB-2 terminal 4 RTN

Confirm each channel-terminal position against the wiring diagram for your module revision before landing wire. Configure all four channels for current, 4-20 mA, in the module properties: the channels are software-configured for voltage or current, and a channel left in voltage mode sources no loop current.

Should you daisy-chain the drive commons instead? #

No. Run one return conductor per drive back to the module: a daisy chain makes one drive's return current flow through the next drive's terminals, and the shared wire's voltage shifts every time any loop's current changes.

Electrically the daisy chain closes every loop, since the commons are one node anyway, but it puts shared copper between drives, and shared copper couples them. Illustrative example, with the inputs chosen and the arithmetic shown: copper at 20 °C has a resistivity of 1.72×10⁻⁸ Ω·m, and a 100 m return of 1.0 mm² cross-section has a resistance of R = ρL/A = (1.72×10⁻⁸ Ω·m × 100 m) ÷ (1.0×10⁻⁶ m²) = 1.72 Ω.

  • Four loops at full scale through one shared segment: I = 4 × 0.020 A = 0.080 A, and V = 0.080 A × 1.72 Ω = 0.14 V of shift on the shared return node.
  • One drive stepping its reference from the minimum to full scale alone: ΔI = 0.016 A, so ΔV = 0.016 A × 1.72 Ω = 0.028 V, about 28 mV injected into the other three loops' returns.
  • The same 100 m as one loop's dedicated return: V = 0.020 A × 1.72 Ω = 0.034 V, constant and confined to that one loop.

Those voltages are examples, not specs — they scale with run length and shrink with cross-section — but their direction never changes: shared copper couples the loops, and the coupling moves with every speed change. Separate returns also let you lift one drive's return for fault-finding without opening the other three loops. Decision: four return conductors, all landing on the module's RTN, none jumping drive to drive.

Can one output channel feed all four drives? #

No — not if any drive must run at its own speed. Four independent speed references need four of the eight channels; sharing one output makes every drive follow the same command, which is a different control scheme rather than a wiring shortcut.

The symptom of a shared channel is unmistakable: all four drives ramp together when you command one. Fix the channel count before anything else. If an arrangement ever puts more than one drive on a channel, the documented gate is the module's published current-output load limit in the 1756 ControlLogix I/O Specifications technical data — stay inside it. With one channel per drive the question never arises. The pattern is the same as wiring a 1769-OF2 analog output to a drive input, four times over on an eight-channel card.

How do you land the wiring, step by step? #

Pair by pair: configure the channels first, then wire one shielded twisted pair per drive with the signal on the channel terminal and the return on RTN, and verify before energizing, in that order.

  1. Set each of the four channels to current mode with the loop range chosen in the module properties.
  2. Lock out drive power and inhibit motion per your machine's procedure before touching any loop wiring — these references start rotating equipment.
  3. Pull one shielded twisted pair per drive: channel terminal to the 1336 analog input, drive signal common back to RTN.
  4. Twist each signal with its own return only; never pair one loop's signal with another loop's return.
  5. Route the analog pairs away from drive output conductors and other switched power.
  6. Terminate shields as the module and drive manuals direct; the shield is never the return conductor.
  7. Label both ends of every pair with loop and drive.
  8. Write down the channel-to-drive map so the commissioning tests hit the right loops.

How do you verify the loops before releasing the drives? #

Command one channel at a time to minimum, mid-scale and full scale, measure the loop current in series, and confirm only the target drive's reference moves; a healthy scaling reads exactly the commanded current at each point.

The mid-scale value is the arithmetic check: 4 mA + 16 mA × 0.50 = 12 mA. Then run the cross-coupling test: step one channel from the minimum to full scale and watch the other three drives' displayed references. The injection worked out above is what a daisy-chained return does to its neighbors, so visible movement on the wrong drives means shared copper somewhere. Mind the drive's loss threshold while testing: the 1336 takes an input below 4 mA, or below 2 V on its voltage input, as a lost reference, with the response chosen by the [4 - 20mA Loss Sel] parameter once its loss-selection bits are enabled. Hold the minimum command at 4 mA unless you are deliberately proving the loss response. Record the measured current and the drive's displayed reference together at each step.

What if a reference reads wrong after the wiring is in? #

Measure the loop current first: correct mA at the module with a wrong or dead drive reading points at the drive side — input mode, polarity, terminal choice or scaling — while wrong mA at the module points at the channel configuration.

Work the list in that order. Check the channel assignment and the current-mode configuration. Check that the drive's analog input is set for the same current range as the module. Single-ended current loops are polarity-sensitive, so verify the signal conductor is on the input and the return is the common, and swap only on evidence. Confirm every return lands on RTN and no loop borrows a shield. Check that nothing bonds the common to chassis unless a manual calls for it, since an unintended earth path invites circulating current. A reference that is stable alone but shifts when another drive loads tells you the returns share copper: split them. Decision: correct topology, mode and polarity before replacing hardware or adding grounds.

When should these references move off analog loops altogether? #

When you need more than one number per drive — named scaling, fault text, or drive diagnostics at the controller — network the drives and send telegrams, because a current-loop pair carries the reference and nothing else.

For a sense of what the networked alternative looks like per drive, how a CU320-2 DP maps six words for each of four drives shows the bus-side footprint next to four analog pairs. Until the machine needs that, the one-pair-per-drive scheme above is the right wiring for this module.

Questions asked

How many drives can one 1756-OF8 reference?

Eight. The module has eight software-configured channels and each drive needs exactly one, so four drives leave four channels free. The shared internal return does not reduce that count; it only means all eight loops sit on one electrical reference, which matters for isolation choices, not capacity.

Why does a 1336 trip or hold at minimum speed?

The drive treats an input below 4 mA, or below 2 V on its voltage input, as a lost reference, and the [4 - 20mA Loss Sel] parameter, once its loss-selection bits are enabled, chooses the response. Hold the minimum command at 4 mA, and leave the loss detection armed as your broken-wire alarm for each loop.

Should the analog common be earthed at the panel?

Not by assumption. The four loops run fine floating on the module's internal common, and an extra bond to chassis can add a circulating-current path that shows up as reference noise. Add an earth connection only where the module or drive manual's grounding instruction calls for one.

What if all four drives should follow one reference?

Then one channel is enough: current inputs share a single loop by wiring in series, so the same loop current passes through every drive. The check is the module's published current-output load limit in the 1756 I/O specifications, because the series sum of the drive input burdens must stay inside it. Every drive then moves together, so this only fits drives that never need independent speeds.

What wire size do the returns need?

Whatever the terminals grip well: voltage drop does not select it here. The illustrative 100 m run of 1.0 mm² copper above drops 0.034 V at full-scale loop current, and because the module regulates the loop as a current, series resistance of that order is not an error term. Pick the conductor for termination quality, and keep it twisted with its signal.

Keep reading

  • Selection guide

    Add 4-20 mA analog inputs when the CompactLogix rack is full

    Swap the installed four-channel analog input card for an eight-channel one when channel isolation matches; that adds four inputs against a need of three, with no rack, power-supply or enclosure change. If isolation rules the swap out, reposition the existing power supply to free an end slot. When the cabinet itself is full, add a POINT I/O analog module or IO-Link converters over EtherNet/IP.

    Controllers and I/O

  • Troubleshooting

    Detect a failed analog input channel and report it to SCADA

    Read the raw input word and the module's per-channel diagnostics before you touch the SCP scaling, then alarm channel health as its own tag that names the channel number. A failed channel then reaches SCADA as a fault with an identity, not as a plausible scaled level, so you know whether to carry a card, a transducer, or wire.

    Controllers and I/O

  • Troubleshooting

    Fixing 4-20 mA scaling on a Quantum AVI030 analog input

    On the Quantum AVI030 analog input, the raw range follows the channel resolution: 12-bit reports 0-4095 counts and 16-bit maps 4-20 mA to 6400-32000 counts. Neither 0-64000 nor a mismatched 0-4095 will scale or hold; set the block's raw limits to match the configured resolution and verify with 4, 12 and 20 mA test currents.

    Controllers and I/O