IMDHMIControls LibraryShop main store

Troubleshooting

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

Drives and motion Published 7 min read

Short answer

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.

On this page
  1. The two objects that share one name
  2. Symptoms and first causes
  3. Work the checks in this order
  4. Keep the enable hardwired and the network stop honest
  5. Worked example: convert an RPM request to a hertz reference
  6. Decisions
  7. Questions asked

Yes — PowerFlex700:O.DriveLogicRslt_Start and PowerFlex700:O.DriveLogicRslt_Stop are the bits that start and stop the drive. They sit in the controller-to-drive output image that the Logix project generated when the drive was added to the I/O tree, and your rungs write them directly. Parameter 271 [Drive Logic Rslt] inside the drive is a different object with a similar name: a read-only diagnostic that reports the command the drive resolved from every source it has enabled, so a write to it fails. For a PowerFlex 700 Vector (catalog 20BC8P7-A3NYYAEC0) run from a CompactLogix 1769-L23E over EtherNet/IP, keep the hardwired drive enable as the machine's safety stop, configure the drive to fault on loss of the network connection, and prove command ownership at the drive before blaming the network. The checks below sort a tag problem from a permissive problem.

The two objects that share one name #

Follow the data direction and the confusion resolves itself:

  • PowerFlex700:O.DriveLogicRslt_Start requests run and PowerFlex700:O.DriveLogicRslt_Stop requests stop. Both are output-image members: the :O prefix means controller to drive, and both travel on the cyclic EtherNet/IP I/O connection. The name is inherited from the drive's own data layout for its logic command; the prefix, not the wording, tells you the direction.
  • The :I input-image members carry running, faulted and connection status back from the drive to the controller.
  • Parameter 271 [Drive Logic Rslt] lives inside the drive and is documented in the drive user manual, publication 20B-UM001. The drive computes it by combining the commands of every source it has enabled — its DPI communication ports and the hardwired discrete inputs — into the one logic command it will obey. It reports the result; it does not accept a write.

If the output member changes and 271 follows it, the command reached the drive and was accepted. If the output member changes and 271 does not, the drive refused or overrode the request, and the fault is in arbitration at the drive, not in the tag. If the output member does not change, the fault is in your logic or in a competing write, not in the drive or the network.

Symptoms and first causes #

Symptom First thing to check
Feedback updates normally, but the drive never starts A rung writing the wrong object, or another enabled command source owning the drive
A write to parameter 271 is rejected It is the drive's read-only resolved result, not the command path
Start and stop bits toggle, but the drive state never changes Enable input absent, an active fault, or the network not selected as command source
The drive faults whenever the network hiccups The configured communication-loss action working as set — verify the restart procedure instead of disabling it
I/O connection drops appeared after plant traffic was added Switch loading, cable integrity, and segregation of the drive network from general traffic

Work the checks in this order #

  1. Confirm the I/O tree. The module profile must match the installed drive, the connection must be running, and the generated :O and :I tags must exist with the expected members.
  2. Prove the hardwired enable first. Reset the safety circuit and watch the drive's enable status. No network bit moves the drive while the enable is absent, and every tag can look healthy while it is missing.
  3. Watch the write. Go online, run the sequence into its run state, and confirm the rung actually writes PowerFlex700:O.DriveLogicRslt_Start. Cross-reference the member name: a later rung overwrites an earlier request within the same scan, so keep one routine as the only writer of the drive command bits.
  4. Read the resolved result. Watch 271 [Drive Logic Rslt] while the output member changes. If the output moves and the result does not, something at the drive is overriding the network: an enabled HIM, a discrete input, a permissive or an active fault.
  5. Interlock your own logic. Never let Start and Stop be true together — one direction per state — and require a reset after a fault instead of a held start bit.
  6. Supervise with feedback. Use the :I running, faulted and connection members to alarm a refused command. A true start bit is a request, not proof that the motor turns.
  7. Only then touch the network. If steps 1 through 6 pass, the tags and the drive are sound, and an intermittent I/O loss is a switch, cable, noise or segregation problem.

Keep the enable hardwired and the network stop honest #

In this design the drive enable input is the only hardwired control connection, and the safety circuit opens it. Keep that single connection reserved for the safety function. A stop written in the output image exists only while the I/O connection exists, so the safety stop must work with every network cable pulled. IEC 60204-1 defines the machine stop functions as category 0, power removed immediately, and category 1, a controlled stop followed by power removal: build the enable circuit to the category the machine's risk assessment calls for, and prove it by actuating the guard, never by writing a bit.

The network gets the routine work: start, stop, speed reference and status. Configure the drive or its communication adapter to fault when the EtherNet/IP connection is lost, so a broken link produces a deliberate drive fault instead of a motor running on its last command. Test it once at commissioning: unplug the cable with the motor at speed and confirm the result is the deliberate fault the design expects.

Wiring rule: give the cell its own switch and keep the drive I/O connection off the plant backbone. A single small unmanaged switch feeding the controller, the drive, the panel display and the SCADA client is a workable shape for one machine cell; sharing a busy backbone with office and plant-wide traffic is how intermittent I/O losses start.

Worked example: convert an RPM request to a hertz reference #

The reference member in the same output image carries the speed the drive obeys, in whatever unit the drive's configuration presents. If that unit is frequency, convert the operator's RPM request in the controller using the nameplate base values. The numbers below are an illustrative calculation; read the actual values from your motor nameplate and drive configuration.

Example: the nameplate reads 60 Hz at 1800 RPM. The conversion factor is 60 Hz / 1800 RPM = 0.0333 Hz per RPM. The operator requests 900 RPM, so the reference is 900 RPM × 0.0333 Hz/RPM = 30.0 Hz — the same arithmetic as 900 × 60 = 54,000, then 54,000 / 1800 = 30.0. Write 30.0 Hz to the reference member, clamped to the machine's approved span, here 0 to 60 Hz.

The linear map holds only up to base speed. A 2000 RPM request works out to 2000 × 60 / 1800 = 66.7 Hz, which the nameplate relationship does not support: clamp to the drive's configured maximum frequency, 60 Hz here, instead of extrapolating. The conversion also ignores slip, so at load the shaft sits slightly below the request in plain V/Hz mode; that is motor slip, not a scaling error. Commission the mapping by comparing three values at one moment: the operator's RPM request, the number written to the reference member, and the output frequency on the drive display. If the three do not agree through the conversion, the scaling is wrong and the start and stop logic above is not the culprit.

Decisions #

  • Start and stop: write PowerFlex700:O.DriveLogicRslt_Start and PowerFlex700:O.DriveLogicRslt_Stop from one routine. Never write 271 [Drive Logic Rslt]; read it as the verdict on the command you sent.
  • Safety: the enable circuit stays hardwired and delivers the IEC 60204-1 stop category the machine needs; EtherNet/IP carries no safety function in this design.
  • Communication loss: configure a drive fault on connection loss and rehearse the restart once, on purpose, at commissioning.
  • Speed reference: convert RPM with the nameplate base values, clamp at the configured maximum frequency, and verify with the three-point comparison.
  • Network: the cell keeps its own switch; the drive I/O connection never shares the plant backbone.

Questions asked

Should start and stop go over the network or over discrete I/O?

With the enable kept hardwired and a drive fault configured for connection loss, network start and stop is a workable and widely run design; the exposure left is production interruption on a network fault, not safety. Move start and stop to discrete I/O when the process cannot absorb a drive fault from a cable or switch failure, because one or two wires remove that exposure. Whichever path carries the command, keep one routine as its only writer and supervise it with drive feedback.

What happens when the EtherNet/IP connection drops while the motor runs?

The drive follows its configured communication-loss action and stops by the stopping method that action defines. Recovery is a sequence: restore the link, let the I/O connection re-establish, clear the drive fault, then restart from the logic rather than from a held start bit. Prove all of it once at commissioning by unplugging the cable with the motor at speed; the fault, the alarm and the restart should each match what the risk assessment and the operators expect.

Do these tag names apply to other PowerFlex drive families?

No. Those member names come from the module profile a Logix controller generates for a PowerFlex 700. Each drive family generates its own tag set with different member names and data layouts, so the method transfers but the names do not: open the controller tags your own project created and write to the members your I/O tree actually generated. Check data direction and scaling there as well, not in a tag list copied from another job.

The start bit is true and parameter 271 shows run, so why is the shaft still?

The command path is proven at that point, so move to the power path and the drive's inhibits. Confirm the enable input is still present, that no fault or local inhibit is active, and that the drive is not sitting in a ready state you mistook for run. If a contactor or a brake sits between the drive and the motor, the drive can report run with the shaft held; check that device's coil and feedback before rewriting working logic.

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

  • How-to

    Reach a CompactLogix through a ControlNet bridge in RSLinx

    When autobrowse through a 1784-U2CN ControlNet path lists the bridge's EtherNet/IP module but no CompactLogix or third-party EtherNet/IP devices, add the target IP address manually under that module's Ethernet port in RSWho or the FactoryTalk Linx browse tree, then select the resulting device as the online path in the Logix programming software. The devices are reachable; only discovery fails, and a manual entry needs no discovery.

    Industrial networks

  • How-to

    CompactLogix MSG to SLC 5/04 through a DH+ gateway

    The CIP path in the CompactLogix MSG ends at the 1756-DHRIO module in the remote chassis. On the MSG configuration tab, change the communication method from CIP to DH+, then enter Channel A and the SLC 5/04 node address in the DH+ fields; the SLC is never part of the path itself.

    Industrial networks