Creating a text read out to display PowerFlex 525 faults based on fault integer tag

Ignition Exchange
1

Hello,
I am working with a PowerFlex 525 and want a text display that will give a readout of the fault based on the VFD’s integer tag. It would be nice if it went into a table and one object changed text based off this value instead of having to do separate objects changing visibility for every fault. I am working in Studio
5000, VFD is on revision 2.003, and I am working on the newest version of Ignition Vision.

2

Assuming its one tag, you can use PARAM with a style. based off of the value, will change the custom style, you can control color, text, etc…

3

Create an expression tag that maps integers to text.

1 Like
4

I did this with a client tag, see attached. I grabbed these from a FTView application. You could also shove into a database table.
PF525.zip (3.5 KB)

5

Here is a link to the drive’s documentation

There are about 30 fault codes, and each code has a name, type, description and action.

Given that VFDs should not be faulting that often, I’d prefer to see all of this data in a DB table somewhere, and then do a lookup based on fault code. This would give you flexibility and keep all of the information in one location (especially if you are displaying faults for multiple drives)

1 Like
6

+1, although a dataset tag should be acceptable for only 30 lines.

2 Likes
7

+1 for an expression tag. You could use a dataset tag as well to store the faults and use the lookup function to get the description. This way you’re defining the tag value at the source rather that at the component level, so it’s far simpler to display at the component level

8

I know this is an old thread, but I figured this might still help someone who finds it later.

I’d also go with the dataset/expression-tag approach mentioned above. Keep the fault number, fault name and description in one dataset or DB table, then have the display component do a lookup from the integer coming from the drive. That seems much cleaner than maintaining a separate component for every possible fault.

I’ve been working with PowerFlex 525s quite a bit and I often use these blogs as an extra reference when I’m trying to understand what a parameter or fault is actually related to:

It’s not an Ignition-specific guide and I’d still use the Rockwell manual as the source of truth for the complete fault-code table, but it has some useful context around the PF525 parameter groups and several of the faults. That can be handy if you want the HMI to show something more useful than just “Fault 109” and later add descriptions or troubleshooting notes to the same dataset.

For multiple drives I’d definitely keep that mapping in one place and reuse it rather than building the fault text separately on each screen.