IMDHMIControls LibraryShop main store

Troubleshooting

Why a Kinetix 5500 needs a motion-capable Logix controller

Drives and motion Published 7 min read

Short answer

A Kinetix 5500 servo drive used as a Logix integrated motion axis requires a motion-capable CompactLogix controller such as the 5069-L306ERM. A non-motion 5069-L306ER cannot add the drive to the module tree and is reported to read only some drive parameters over explicit messaging. Confirm the controller catalog number and the required axis count before troubleshooting anything else.

On this page
  1. What the module tree rejection is telling you
  2. Read the controller catalog number first
  3. The reader's case: a 2198-H025-ERS with a VPL motor on a 5069-L306ER
  4. Two hardware paths out, and the motor picks the path
  5. When no motion processor is needed
  6. Verify the axis after the controller change
  7. The decision for each case
  8. Questions asked

A Kinetix 5500 servo drive that the Logix project must command as an integrated motion axis needs a motion-capable CompactLogix controller, and the 5069-L306ER is not one. Studio 5000 V35 refuses to let you add the drive under that controller because motion capability is fixed in the catalog number, not switched on in software. The like-for-like motion model, the 5069-L306ERM, is the specification change that resolves it, once you have confirmed the axis count fits. What the non-motion controller keeps is a monitoring role: the field report is that it reads a handful of drive parameters over explicit messaging, and that is not motion control. This article reads the symptom, works the decision end to end on the machine as specified, and ends with the decision for each control architecture.

What the module tree rejection is telling you #

In an integrated motion system, the Kinetix 5500 is not a generic Ethernet device. It enters the project as a motion axis that the controller's motion processor plans and commands through the Logix motion instructions and the motion profiler. That motion engine exists only in the motion-capable catalog numbers, which in the 5380 family are the ones ending in M.

So when the add fails under a 5069-L306ER, Studio 5000 is enforcing the controller's capability boundary, not reporting a network fault. The drive pings, explicit messages get through, and the module-tree entry still refuses. Repeating the add, swapping switch ports or re-addressing the drive cannot change the outcome; the decision point is the controller catalog number.

Vendor literature draws the same line: the CompactLogix System Selection Guide (1769-SG003) lists the 5069-L306ER and the motion-capable 5069-L306ERM side by side, and the CompactLogix 5380 technical data (5069-TD002) documents integrated motion on EtherNet/IP networks per catalog number.

Read the controller catalog number first #

Read the catalog number from the controller label and compare it with the controller type set in the project — the project's controller properties show what Studio 5000 thinks is installed. If the label reads 5069-L306ER and the machine specification expects Logix motion axes, you have found the fault before touching anything else.

What you see on site What it means The move
Studio 5000 will not allow the drive under the controller A non-motion catalog number is set against an integrated-motion drive Confirm the catalog number, then specify the motion model
The drive pings and answers parameter reads, but no axis can be created The monitoring path works; the motion path does not exist on this controller Treat explicit messaging as diagnostics only and spec the motion controller
A motion-capable controller is installed but the axis will not come up Axis count or axis configuration, not capability Count the axes against the documented limit, then check the axis configuration

The reader's case: a 2198-H025-ERS with a VPL motor on a 5069-L306ER #

This is the machine as it was put to us, and it is the case that settles the customer reply.

Inputs, each with its source:

  • Drive: Kinetix 5500 servo drive, catalog number 2198-H025-ERS — as specified for the machine.
  • Motor: VPL low-inertia servo motor, catalog number VPL-A0752E-CK14AA — the companion motor on that drive.
  • Controller: CompactLogix 5069-L306ER, the non-motion 5380 catalog number — installed and customer-specified.
  • Software: Studio 5000, version 35 — as planned.
  • Symptom: the drive cannot be added as an Ethernet module under that controller — observed in Studio 5000 V35.
  • Motion load: one servo axis, no other axes specified.

Rule in words: a Kinetix 5500 commanded as a Logix integrated motion axis requires a motion-capable controller catalog number, and the motor family decides whether the drive or the controller is the hardware that changes.

The decision chain, written out:

  1. The 2198-H025-ERS is specified as a Logix integrated motion axis, so a motion processor is required; the 5069-L306ER is excluded.
  2. The motor VPL-A0752E-CK14AA is a VPL, so the drive-family swap that applies to MPL machines does not apply here; the controller is the hardware that changes.
  3. Axis count: 1 servo axis + 0 planned additional axes = 1 motion axis the replacement controller must carry.
  4. The like-for-like motion model in the same 5380 family is the 5069-L306ERM. One axis is within the capacity of any motion-capable catalog number, so the count clears for this machine; confirm the documented axis limit in 5069-TD002 before the specification goes out, because axis count is the check that catches larger machines where even a motion model is too small.

Result: with the 5069-L306ERM specified, Studio 5000 accepts the drive in the module tree, and the drive and motor keep exactly the catalog numbers the customer listed.

Decision: the reply to the customer is to spec the 5069-L306ERM; the 2198-H025-ERS and VPL-A0752E-CK14AA stay as specified; stop re-trying the module tree against the L306ER, because the boundary is the catalog number, not the network.

Two hardware paths out, and the motor picks the path #

Two hardware routes resolve this kind of mismatch, and the motor catalog number selects between them.

Controller swap — this machine's route. A VPL motor stays with its Kinetix 5500, and the controller becomes motion-capable. For a like-for-like 5380 replacement of the L306ER that is the 5069-L306ERM, as worked above.

Drive swap — reported for MPL motors. The field report is that with an MPL motor the drive family can change from the Kinetix 5500 to a Kinetix 5100, which is not an integrated-motion drive and is commanded through the provided AOIs instead of the motion profiler. Do not carry that substitution across to this VPL machine: it belongs to a different motor case, and any drive change needs a drive-and-motor compatibility check against the drive documentation before hardware is ordered.

Both routes change customer-specified hardware, so both go back to the customer: invite them to spec the correct controller, or get the alternative approved in writing.

Decision: VPL motor — change the controller. MPL motor and the application tolerates control without integrated motion — the 5100 drive swap is the reported route, subject to a compatibility check.

When no motion processor is needed #

The motion requirement comes from the control architecture, not from the word servo on the crate.

Third-party motion systems command their drives through their own interfaces, and Logix integrated motion is not involved; confirm the command interface with that drive manufacturer before promising control from the Logix project.

Ordinary VFDs run from any controller with no motion processor at all. The reported exception is the drives that are themselves integrated-motion products, such as the PowerFlex 527, which need the motion-capable controller exactly as the Kinetix 5500 does.

For a plain VFD the design questions are command path and drive ownership, the same questions behind controlling a PowerFlex 525 drive from two PLC controllers.

Decision: VFD speed control or third-party motion — no motion processor needed; integrated-motion products such as the Kinetix 5500 and the PowerFlex 527 — motion-capable controller.

Verify the axis after the controller change #

  1. Record the starting point before anything changes: controller catalog number, drive catalog 2198-H025-ERS, motor catalog VPL-A0752E-CK14AA, Studio 5000 version, and the intended control method.
  2. Make the controller change in the project, install the 5069-L306ERM, and bring the drive in through the supported EtherNet/IP motion workflow in the Kinetix 5500 user manual (2198-UM001) and the Connect Kinetix 5500 drives over an EtherNet/IP network quick start.
  3. Confirm the axis: the drive sits under the controller as a motion axis, associated with the correct drive and VPL motor catalogs, inside the project's motion group.
  4. Re-run the axis count against the controller's documented motion limit, including any axes planned for later.
  5. Commission with the same discipline as a remote I/O commissioning checklist for a modular station: one device at a time, states and diagnostics verified before any move is commanded.
  6. Prove the motion behavior against the machine specification: the axis follows commanded position, feedback agrees, and limits and stops act as specified.

Before sign-off, remember that a clean download and a live module-tree entry do not prove the machine can stop safely — prove the limits, the stop behavior and the guard response under controlled test moves before product runs.

The decision for each case #

  • Servo specified as a Logix integrated motion axis, any motor: a motion-capable controller catalog number — for a like-for-like 5380 swap, the 5069-L306ERM — with the axis count confirmed against its documented limit; drive and motor catalog numbers stay as specified.
  • Monitoring and parameter reads only: the 5069-L306ER is sufficient, via explicit messaging, and the reads are diagnostics, never a control solution.
  • MPL motor with control without integrated motion accepted: the reported route is the Kinetix 5100 drive swap with the provided AOIs, after a drive-and-motor compatibility check.
  • Motion commanded by a third-party controller: use that manufacturer's documented interface; no Logix integrated motion; confirm the interface with the manufacturer.
  • Plain VFD: no motion processor; an integrated-motion VFD such as the PowerFlex 527 needs the motion-capable controller like a servo does.

For the machine in question — a 2198-H025-ERS driving a VPL-A0752E-CK14AA, one axis, Studio 5000 V35 — the reply that holds up is that the customer should spec the 5069-L306ERM.

Questions asked

Does a Compact GuardLogix controller run a Kinetix 5500?

GuardLogix follows the same rule as any Logix controller: the specific catalog number must carry integrated motion support, and the safety function alone does not provide motion. Rockwell's support knowledgebase carries a dedicated answer on Compact GuardLogix support for Kinetix 5500, Kinetix 5700 and PowerFlex 527 integrated motion and network safety; use it to confirm which safety-controller catalog numbers qualify before you write the specification.

Can I swap the Kinetix 5500 for a Kinetix 5100 to keep the existing PLC?

Only in the reported case where the motor is an MPL. The 5100 route is not integrated motion: the drive is commanded through the provided AOIs, reported as indistinguishable for a single-servo system and different once high-speed integrated motion with distributed clocks is involved. This machine carries a VPL motor, so the swap does not apply, and any drive substitution needs a drive-and-motor compatibility check against the drive documentation first.

What works if the 5069-L306ER stays and only explicit messaging is used?

Monitoring, not motion. The field report is that a non-motion controller reads a handful of drive parameters over explicit messages while the drive still cannot enter the module tree, join a motion group, or accept axis commands. Keep the path for diagnostics and status panels, but a successful parameter read is not evidence that the axis can move and should not be presented as a control solution.

Can a 5069-L306ER be upgraded to add motion capability?

No. Motion capability comes with the catalog number: the 5069-L306ER and the 5069-L306ERM are separate hardware catalog numbers, and no software option turns the non-motion controller into a motion processor. Plan the change as a controller replacement — new hardware, the controller type updated in the project, and the axis re-commissioned — not as a configuration edit on the existing unit.

How many axes does the replacement controller need to carry?

Count every servo axis the project will create, including any planned for later, and confirm the total against the motion axis limit published for that catalog number in the CompactLogix 5380 technical data, publication 5069-TD002. For the machine in this article the total is one 2198-H025-ERS axis, which is within the capacity of any motion-capable catalog number in the family.

Keep reading

  • How-to

    Control a PowerFlex 525 drive from two PLC controllers

    Yes — add the PowerFlex 525 to the Logix controller's Ethernet tree and its command tags appear, but a cyclic drive connection has exactly one owner. Give the Logix controller that ownership, read the MicroLogix machine's request into it, and let one rung select the command the drive follows. Never let two controllers write the speed reference.

    Drives and motion

  • Troubleshooting

    PLC-5 not visible in RSLinx after processor replacement

    A replacement PLC-5 stays invisible in RSLinx because the 1785-ENET sidecar answers the network on its own while the processor waits for an application that configures the Ethernet channel 3A. Leave the non-isolated serial port disconnected until the cable is checked, bring the processor up over serial DF1 or DH+, download the saved program, and the Ethernet path returns.

    PLC programming

  • Troubleshooting

    Start and stop a PowerFlex 700 over EtherNet/IP from CompactLogix

    Yes — set PowerFlex700:O.DriveLogicRslt_Start and PowerFlex700:O.DriveLogicRslt_Stop in the controller output image; those :O members are the network start and stop commands. Parameter 271 [Drive Logic Rslt] inside the drive is a read-only diagnostic of the combined command, so writing it fails. Keep the hardwired drive enable as the safety path and set the comm-loss action to fault, then prove both by test.

    Drives and motion