IMDHMIControls LibraryShop main store

Troubleshooting

Troubleshooting missing Drive Ready on a V60 axis retrofit

Drives and motion Published 6 min read

Short answer

S-rUn on the drive proves the enable reached it; it proves nothing about the return path. Hold the MC_Power enable TRUE for the whole test, then trace the drive-ready contact, its 24 V sense wiring, the PLC input channel and the tag mapping in that order. Local jog proves the motor and power stage, not the PLC interface.

On this page
  1. What the three observations already prove
  2. Hold MC_Power enable and judge it from Status
  3. Trace the ready contact from the drive terminal to the tag
  4. Compare the wiring with the published example for this retrofit
  5. Prove the command path with a controlled jog
  6. The decision at each layer
  7. Questions asked

On a V60 retrofit, the display stepping from S-4 to S-rUn proves one thing: the enable from MC_Power arrived at the drive and the drive took it. It proves nothing about the return path — the drive-ready contact, its wire, the PLC input channel or the tag. The axis sits at standstill with an empty diagnostic list because the technology object is healthy and no motion command has started; the sequence is stuck waiting on feedback that never arrives. Work the fault in that order: hold the enable, prove the ready contact at the drive terminal, follow the pair to the input channel and its common, then check the tag mapping, and only then jog.

What the three observations already prove #

  • Display steps from S-4 to S-rUn: the drive's enable input is being driven and accepted. The enable stage works, so leave it alone.
  • The motor runs from the drive's own jog controls: the power stage, motor and mechanics are good. That path bypasses every PLC signal, so it clears the drive, not the retrofit interface.
  • “Motor at a Standstill” with no error: the technology object has no configuration or device fault and no command is executing. The block sits in the sequence logic and in the missing ready feedback.

Together the observations put the fault in the drive-to-PLC feedback path, and that is where the rest of the checks go.

Hold MC_Power enable and judge it from Status #

MC_Power's Enable is a level, not an edge: set it TRUE and keep it there for the whole test and every motion command after it. The function manual is explicit that the axis must be enabled before it can take on motion jobs, and you confirm that from the block's Status output together with the axis status bit StatusBits.Enable, watched online — not from Busy.

Busy only reports that the block is active. When Busy stays TRUE for as long as Enable is high while the display reads S-rUn, the enable operation took effect at the drive and MC_Power has done its job; that combination is not a motion fault, so move on. The case that would need enable work is Busy TRUE with the display still in S-4: then check the enable wiring and its polarity. This is the same discipline as starting and stopping a drive over EtherNet/IP from the PLC: the command is a held state, never a pulse you release and hope sticks.

Trace the ready contact from the drive terminal to the tag #

  1. Name the output first. The V60 wiring documentation for your control interface gives the drive-ready contact's terminal numbers and its active state — closed when ready or open when ready. Take both from that diagram, never from assumption.
  2. Measure at the drive. Hold the enable so the drive sits in S-rUn and measure DC volts across the ready contact with the sense circuit live. Near 0 V across a conducting contact means it is closed; the full sense voltage across it means the contact is open and the fault is at the drive side.
  3. Measure the loop dead. Pull the fuse on the 24 V sense circuit, leave the drive's control power on so the contact closes, and read resistance across the pair at the PLC end. The worked example below gives the number a healthy loop must show.
  4. Follow the pair to the input. Confirm the physical input terminal, and land the return on the common group that terminal belongs to. The 1214C DC/DC/DC digital inputs are 24 V DC; a contact switching a different supply, or a return landed on the wrong common, reads FALSE forever while everything looks right.
  5. Watch the channel online. Put the raw %I address in a watch table and hold the enable. Terminal state changes but the channel does not: wiring, common or voltage compatibility. Channel TRUE but the ready bit FALSE: the tag points at a different address — fix the mapping.

Worked example: loop resistance of a healthy ready path #

Illustrative inputs: the drive sits 15 m from the PLC cabinet and the ready sense pair is 0.5 mm² copper, so the loop is 2 × 15 m = 30 m. Copper is about 0.0175 Ω·mm²/m at 20 °C, so with the contact closed a healthy loop reads R = 0.0175 × 30 / 0.5 = 1.05 Ω, plus a fraction of an ohm for the contact itself. Three outcomes decide the case: roughly 1–2 Ω says the contact and both conductors are good, so carry the trace into the cabinet; a kilohm-range reading points at a bad termination or a corroded lug; an open circuit puts the fault at the drive contact or a missing jumper in the drive's own terminal block.

Compare the wiring with the published example for this retrofit #

Siemens publishes an application example for exactly this machine — positioning a V60 from an S7-1200 over pulse/direction with an HMI — and its connection diagram lands the drive's 24 V DC supply on terminal X3. Open that connection diagram beside the cabinet and compare it with the as-built wiring: the onboard outputs the technology object assigns to pulse and direction, and every digital input and output the diagram shows for enable and ready. A clean diagnostics list is not evidence that the hardware interface matches; the technology object reports what you configured, not what is wired.

Prove the command path with a controlled jog #

With the ready bit TRUE at the tag, keep Enable high and request a jog with MC_Jog. Give Velocity, Acceleration and Deceleration real values or −1; a −1 tells the block to take that value from the axis technology object's defaults, so confirm those defaults before the first move. Watch the Motion status view move the axis out of standstill, and check the shaft speed at the coupling against the commanded Velocity — a pulse-train axis without feedback reports commanded motion, so a handheld tachometer or your own eyes close that loop. The first commanded motion on a retrofit deserves clear space around the axis and a hand near the drive's enable-off control: local jog already proved the shaft turns.

Decision: a jog at the commanded speed finishes the retrofit. A jog that does nothing with the ready bit TRUE sends you back to the pulse and direction wiring, because the command path is the only layer left.

The decision at each layer #

  • Enable: StatusBits.Enable TRUE with the display in S-rUn — MC_Power is done; a Busy that stays on over that is a block-status reading, not a drive fault.
  • Ready contact: near 0 V across it live, about 1 Ω around the loop dead — the drive side is proven; carry the trace to the cabinet.
  • Input channel: the raw %I follows the contact — the wiring is proven; a ready bit still FALSE now means tag address or overwriting logic.
  • Command path: jog at commanded speed with confirmed defaults — the retrofit is complete.

Worked in that order, each check either clears a layer or hands you the failing one; no layer is guessed at and no parameter is changed just to see what happens.

Questions asked

When can I set MC_Power Enable back to FALSE?

Only after the axis has reached standstill. Dropping Enable disables the axis and aborts all Motion Control commands, so a momentary loss of the enable mid-jog stops the axis and leaves the sequence reading a failed command. Hold Enable through the whole cycle and drop it only from a controlled stop condition.

What do I do with the StopMode input on a retrofit axis?

The S7-1200 motion function manual lists initializing StopMode as a requirement before you set Enable TRUE. It selects how the axis behaves when the enable drops, so give it a deliberate value in the start-up logic that feeds MC_Power instead of leaving it wherever the block lands. Match it to the behavior the machine's stop circuit expects.

The input LED is on but the ready bit stays FALSE. What proves where that breaks?

Watch the raw %I tag online in a watch table rather than the mapped variable, and confirm the physical terminal number matches the absolute address the tag points at. Then search the project for a second coil or move that writes the same address; one duplicated address overrides the ready signal every scan.

Why does the axis diagnostics view show no error while the ready bit is missing?

Because the diagnostics report the technology object's own state, and the object is healthy: no motion command is executing, so it reports the axis standing still. It cannot see the sequence logic or the drive's ready contact. An empty diagnostic list is the expected picture in this fault, not a contradiction.

Keep reading

  • Troubleshooting

    Why a Kinetix 5500 needs a motion-capable Logix controller

    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.

    Drives and motion

  • 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

  • How-to

    Control a PROFINET servo drive with cyclic telegram data

    No motion library is needed when a PLC only exchanges cyclic process data with a PROFINET servo drive: import the device description, attach the drive, select the same telegram the drive is configured for, and map the words. Standard telegram 1, PZD 2/2, is two 16-bit words each way — four bytes per direction — and the PLC logic sequences control word STW1 and reads status word ZSW1.

    Drives and motion