• Powerflex Drive Fault Codes
• Powerflex 700 Manual

PLC, HMI, DCS, SCADA Instrumentation, Process Control Please report any spam you see General information about PLCs: by A.D. On Youtube on Wikipedia on Wikipedia More in depth learning about PLCs: Examples of PLC Brands: Allen Bradley, Siemens, Omron, GE, Schneider, Modicon, Mitsubishi, Toshiba, Automation Direct, Beckhoff, B&R, Phoenix Contact, Unitronics No ebay or purchase links anywhere please.

The examples and diagrams in this manual are included solely for illustrative purposes. PowerFlex 700 Dimensions. NFPA 70 - US National Electrical Code. That, if the condition persists, it may lead to a drive fault. PowerFlex 700 Issues - Flashing 'Stopping'/'Stop Asserted' on new program. Drive fault code is 75. Try checking for fault codes on the 20-comm card as well. View and Download Allen-Bradley Powerflex 700 user manual online. And/or electrical codes. Version Clr Fault Queue PowerFlex 700 Drive Alarm 1.

It starts to look like spam. And plain text only in the user flair, no links. Memes are allowed. Craigslist type submissions are not.

Related subreddits. Here's the infrastructure layout -. Logix 24.11 L73. EN2T cards. 20-COMM-E for the drive cards. Hooked up with EtherNet/IP. PVSD PlantPAx objects (AOI/Faceplate) The existing program functions perfectly when we re-download it, but ours gets stuck in an AOI loop between stopping/stopped states.

So far we've tried:. Scan times. Deleting all instances of the PVSD instruction, deleting the AOI and importing from the existing program. Power-cycling the drives Has anyone seen this before? Everyone at the plant is at a loss.

Edit: We fixed it! It was a one button click fix (as it always is.). When doing your input/output/AOI mapping, make sure to put the input first, the AOI second, and the output last.

That way when the task scans, the inputs update, the AOI executes, then the outputs trigger. It was stuck in a loop because the AOI was last in the program structure. So dumb, but since I'm new to PLCs I wasn't thinking about scan order. Few things right off the bat I would try in troubleshooting this, as looking at the Rockwell website its saying this is a comm card fault, though if I'm reading your description of the problem correctly the old program works, the new program isn't(?): -Has everything involved gotten a firmware update the most recent version?

Drive, Comm Card, EN2T Cards? We just had an issue with communications being lost between our PLC's and main plant network because of firmware issues with the brand new EN2T cards (like fresh out of the box by a couple of weeks new).Has the ethernet wiring to this drive been tested to make sure that connections are good on both ends?

Are you terminating into a RJ45 jack then running a patch cord to the drive or doing a RJ45 male on each end cable run? Can you ping the drive on the network and are the response time appropriate -Can you swap the 20-Comm-E out with another card on another drive.

By doing this you will see if the com card is causing the problem as the problem will follow the card, or if the problem is on the drive.Are all of your VFD jumpers in the proper position? -Are all of your interlocks and running/not running feedbacks working correctly and not toggling or in a 'stuck' state causing the drive to not function? This is a little away from the Comm Card Fault error.

Thanks for the response. Firmware shouldn't (shouldn't.) matter.

Powerflex Drive Fault Codes

Another program with the exact same AOI revision and module works perfectly. Nothing is changing between the two systems, just a download. Same IP's in the controller, and we can access the drive parameters from Logix. We can't, we're just system integrators. If it comes down to it, we'll find the electricians and switch them out. Works in the old system!.

The faults only start happening when the device interlocks are cleared and the drive is available to start. After a looooong talk with TechConnect, we've narrowed it down to the AOI instance itself. There's an issue with scan times, not sure what yet, but that's the problem. Try checking for fault codes on the 20-comm card as well. From a overall general view it seems like the drive is holding/loosing the stop command over and over; hence the stopping/stop asserted. If the start stop is over ENET and not hardwired then I would say the issue is related to something on the ENET network (20-comm, connecting media, clx ENET cards, or software) as you have already seemed to diagnose.

You can try removing all references to the drive in the logic, code and all. Then re-add it with only the stop/start commands in a new routine and internal test bits to trigger each. Disconnect the motor leads if your worried about that as well.

Powerflex 700 Manual

Then start/stop using new logic in the new routine. If it runs and stops fine here I would say previously programed code for start stop should be investigated. If it still happens I would investigate physical hardware.

We offer a hassle free, no-charge evaluation for Allen Bradley PowerFlex 700 repair and our low repair prices provide great cost savings to all who utilize our services. Our repair process for all items ensures that all components found to be defective, damaged, out of tolerance, aged or known to have a high failure rate are replaced, with the result being that your defective unit is not just repaired, it is actually refurbished. Our testing process for all units, including PowerFlex 700 repairs, requires all functions to be fully tested including inputs, outputs, communications ports, keypads, options and other functions. Every PowerFlex 700 repair is also burned in under dynamic load on our custom designed loading equipment to make sure the unit will function as required when re-installed at your facility. This attention to detail allows us to provide an all-inclusive warranty that covers the entire unit, not just what is repaired or replaced.