PowerFlex 7 Series Hour Accumulator

gmferg

Lifetime Supporting Member + Moderator
Join Date
Feb 2008
Location
Modesto, CA
Posts
340
I have a customer that has a VFD that stopped unexpectedly and no one can say whether or not the drive faulted. The drive records the fault code and time for the last 8 faults. I don't know when the last fault was recorded, was it Yesterday, last week, or 3 months ago. The time recorded is a free-running hour accumulation.

According to AB tech support, the only way to figure out when the faults happened is to cycle power to the drive. A snapshot of the current hour accumulation will be stored in the "Power Up Marker" parameter. This power cycle is only required if you don't know when the drive was last powered up. If you know the time when the "Power Up Marker" was updated, you can calculate the "real time" of the fault by subtracting the fault time from the power up marker and subtract that from the "real time" at power cycle.

My question to AB tech support was: "If the drive has a free running hour accumulator, how can I access it so I can see the accumulation without doing a power cycle?" Answer: "Can't be done."

Does anyone know of a trick to read the live hour accumulator via HIM, RSNetworx for Devicenet, Drive Executive, Explicit MSG, or whatever?

CP02_CV03_FaultCodes_2011_12_12.JPG
 
Yeah, I had to sort this out sitting atop a crane on the shore of the Gulf of Arabia.

Let me see if I can find my notes.

It's in the Diagnostic Objects somewhere.

The reason I didn't pursue it more is that the drive doesn't have a battery-backed clock: the timer only increments while the drive is actually powered up. Since these drives were spending a lot of time powered down (during comissioning) I really had to way of knowing if the drive had faulted or if the power had just been switched off.

I ended up watching the drive for a Fault bit, then timestamping it inside the ControlLogix.

For your purposes, if the drive isn't spending a lot of time powered down, the DPI clock might help.

Edit: I think I used the DPI Time object, as described in the 20-COMM-D user manual appendices. All the project files for my experiment were on a hard drive I had to give back as work product to my former employer, though.
 
Last edited:
Thanks for your help Ken. You've pointed me in the right direction again. I found the DPI Time Object in the 20-COMM-D manual. I will give it a try when I get a chance.

This customer is supposed to be trending the drive fault bit and fault code now so the next time this drive faults it will be easier to troubleshoot.

For future projects, I think I will be adding time stamp extensions to my motor UDT.
 

Similar Topics

Looking over the technical data for a PowerFlex 755 & noticed they specify a minimum enclosure volume for their drives: (1)When using a circuit...
Replies
1
Views
565
Hi, Quick one passing through as I'm quite busy at the moment... Two-day head scratcher here trying to flash upgrade a bunch of out-of-the-box...
Replies
10
Views
11,005
I have a controls system that has multiple PF400's. All of them are older series A drives. They all communicate with 22-comm-e's with a...
Replies
1
Views
1,575
I keep getting a Net IO error message F037 on a brand new drive and after researching it, AB says that it has to be connected to a managed...
Replies
3
Views
2,310
We are using Powerflex 700 VFD to drive the starting motor of gas turbine. Reference speed signal to VFD comes from AB control logic PLC. When we...
Replies
6
Views
3,510
Back
Top Bottom