PF525 Data Type Reverse Decipher

Super Koop

Member
S
Join Date
Nov 2004
Location
NorCal
Posts
48
We have a PF525 inserted into the project but it appears that there should be an alternate "CLX5k Data type applied to the Hardware Module Defined Data Typer. The Data Type assigned when you add the hardware also includes the extended memory.

The typical hardware install reads STATUS, and FREQUENCY
write CONTROL and Command Hz.

When you add additional data for instance, Accel-Decel Setpoints to the OUTput area. OR Motor Current and Fault Code One to the INput data. When these are added the CLX5k hardware data type changes.

Does anyone know how to reverse engineer this data dype?
 
Are you asking to reverse AB AOP for PFLX525?

PFLX525-Module-Define-Data.png
 
Sort of yes.
In your image, I am trying to find the meaning behind the AB:powerFlex525V_E_846C9999:I:0 portion of the Hardware
Data-Type used.
Our Output image includes the ability to write Accel1 and Decel 1, in
addition to the typical CONTROL & FREQUENCY words. Our Hardware
exactly matches this previously generated AOI OUTput Data Type.

Unfortunately
I have not been able to decipher the VFD INput data code that matches
our AOI.
At the moment, we do not have the correct Drive Configuration, as the
Bold numerals above do not match the original AOI.

I do know they are expecting to receive:
* Motor Current
* Fault 1 Code
* VFD Maximum Hz
I am not certain of the order of values, nor if we are missing an
additional value (not referenced within the AOI, but expected).
I have tried multiple combinations, but I'm not able to find an INput
arrangement that matches:
"AB:powerFlex525V_E_55B460AE:I:0"

This is a 3Phase, 460v, 2HP, 525, V5.001 with extended data in the

I have found that by re-arranging the additional data in the Hardware,
I receive alternate Hardware "Data-Types". I've not been able to find
the appropriate INput sequence to match the original AOI expectation.

A couple of hours of overseas AB-Support could not help, with a similar
issue listed for TechNote: QA29960. Different drives, but similar issue
related to a replacement drive version.
 
Super Koop said:
Sort of yes.
In your image, I am trying to find the meaning behind the AB:powerFlex525V_E_846C9999:I:0 portion of the Hardware
Data-Type used.
Our Output image includes the ability to write Accel1 and Decel 1, in
addition to the typical CONTROL & FREQUENCY words. Our Hardware
exactly matches this previously generated AOI OUTput Data Type.

Unfortunately
I have not been able to decipher the VFD INput data code that matches
our AOI.
At the moment, we do not have the correct Drive Configuration, as the
Bold numerals above do not match the original AOI.

I do know they are expecting to receive:
* Motor Current
* Fault 1 Code
* VFD Maximum Hz
I am not certain of the order of values, nor if we are missing an
additional value (not referenced within the AOI, but expected).
I have tried multiple combinations, but I'm not able to find an INput
arrangement that matches:
"AB:powerFlex525V_E_55B460AE:I:0"

This is a 3Phase, 460v, 2HP, 525, V5.001 with extended data in the

I have found that by re-arranging the additional data in the Hardware,
I receive alternate Hardware "Data-Types". I've not been able to find
the appropriate INput sequence to match the original AOI expectation.

A couple of hours of overseas AB-Support could not help, with a similar
issue listed for TechNote: QA29960. Different drives, but similar issue
related to a replacement drive version.
Click to expand...

Maybe im missing something on what you are trying to do but those parameters that you are trying to read are not usually in the default AOP. Those parameters are datalinks and would need to be setup in the drive config, Once setup they will display in the AOP. This could be the reason why your AOI cant read them.
 
Correct me if I'm wrong, Super Koop, but it sounds like your base issues is that the AOI you have written uses the PF525 instance data as InOut parameters. Now the new drive doesn't have the same data type as your AOI and the AOI won't accept it as an InOut parameter. Correct?

If so, I think your solution is getting pretty deep under the hood of how Rockwell defines that type. You might find someone who can explain it to you but I don't know who. In effect it may not help anyway, at least in the long run. It would not surprise me if the datatype name isn't based in some way on the drive version.

Keith
 
We do not have the original hardware configuration / PLC File, to determine the "Additional Data".

Someone had copied the original AOI and pasted it into a new file.
The VFD Hardware they added to this new file, has an inappropriate
extended data-link configuration. This means the data type expected
by the AOI, does not exist in the New PLC File. I am trying to reverse
engineer the VFD INput extended data-link, so it will match what the
AOI is expecting. I have had success exactly mathing the OUTput Data-
-Type, but the INput data-Type string has been proving elusive.

We have an AOI, that referenced the original PF525 IN/Out Hardware Data-Types.
The Data-Type "text string" is unique to the VFD and the specific additional
data-links, and sequence.

At the moment, we do not know the exact original VFD Hardware INput
configuration as the device is placed into the hardware tree. I've exhausted
my attempts at re-arranging the data being recieved, to try to match the original AOI.

Trying not to revise the Original AOI, but so far I am required to do so.

I do not want to introduce identically named / modified versions of the original
AOI.

In a nutshell, I am getting "RED X's" for the VFD's INput parameter.
An image is worth a thousand words, put i've not figured out how to
attach / add images.
 
Do you have the PLC program? original will be good, otherwise let us see what you got.
Also goto its controller tags and X-reference it, you maybe able to find out what those extra inputs that way.
 
Last edited:
Super Koop said:
An image is worth a thousand words, put i've not figured out how to
attach / add images.
Click to expand...




A single image*, if added as the only attachment, shows up in-line with the post. Even if it doesn't, people can click on it.


* e.g. PrtSc => paste into Paint => crop => save as PNG
 
If the AOI still contains the original datatype name you should be able to use that to reconstruct the drive I/O configuration. The datatype for the previous drive should have come over with the AOI import or should have been there from the original development. Open the parameters section of the AOI and you should see the parameters included. If reproducing that doesn't get you the correct datatype name I would say you are out of luck.

Keith
 
Check the routine with the AOI in, it will tell you the tags it can't understand. These are likely your data links. You have a few to choose from, but you can only choose 4 IIRC.

OutputCurrent, Voltage and Fault Code are the most common.
 

Similar Topics

P
E300 and PF525 lost ethernet connection device tag data frozen at last state
When E300 powered off, the ethernet device tag data stayed at last know state, for example, fault bit is still Off, ready bit is still ON, status...
Replies
8
Views
996
JeremyM
JeremyM
D
analog control of PF525
I seem to be on here often lately but cant find specifics about my situation I am trying to control the drive using both ethernet and analog(for...
Replies
1
Views
743
dp96
D
R
Pf525 -- pf70
Hello all, New to this site - I am adding a new conveyor and using a powerflex 525, though the rest of the drives operating this line are...
Replies
7
Views
1,275
randers
R
J
400VAC / 60Hz supply into a PF525.
I have a (*) PowerFlex 525 being supplied with 400VAC, 60 cycle, 3-phase. This is not a type-o, this is accurate. Now, the drive clearly states...
Replies
3
Views
1,167
rupej
R
A
PF525 to a PanelView Plus
Has anyone had any success using a PanelView Plus to directly control a PF525 over ethernet, I tried to use the file provided with TechNote...
Replies
1
Views
1,054
alan_505
A
Back
Top Bottom