AB Powerflex 400 Parameters

[kamenges]

What is parameter 260? I don't see it listed in the PF400 manual?

Keith

 

[andrewbe]

It is Q.Stop Amps - by default it is 37.5 (at least on this drive it is) and it is being changed to 60.

 

[Ken Roach]

Let's decode Post #23, where your software is trying to read N150:321.

10 02 01 00 0F 00 B1 00 A2 02 96 89 41 00 10 03

10 02 Start of Transmission
01 Destination
00 Source
0F Command 0x0F
00 Status
B1 00 TNSW
A2 Function 0xA2
02 Data size = 2 bytes
96 Data File Number = 0x96 hex = 150 decimal
89 Data File Type = Integer
41 Data File Element = 0x41 hex = 65 decimal
00 Data File Sub-Element
10 03 End of Transmission

So there's a problem looking us in the eye. We think we're requesting N150:321, and the actual command going out over the wire is reading N150:65.

What do the values 321 and 65 have in common ?

321 decimal = 0x141 hex
65 decimal = 0x41 hex

It looks to be that the Automated Solutions software is converting the decimal value for the Element Number, but not accounting for the possibility that it's two bytes, and just taking the first byte.

So we know what's going wrong with some of your data reads.

The first unexplained issue is the Elements between 251 and 255 not being read correctly.

Could you capture the AS software reading N150: 251, 252, 253, 254, 255 ?

You guys are moving too fast for me today.... I'll go look at the Write captures now.

 

[andrewbe]

251, 252, 253, and 254 actually DO read correctly at N150 (there is no parameter 255, the next valid parameter is 260) For whatever reason, N151:1 starts at 250 (instead of 260, as you might expect)

 

[Ken Roach]

To examine the N151 write to N151:10:


Request: 10 02 01 00 0F 00 75 00 AA 02 97 89 0A 00 58 02 10 03 4B

10 02 Start of Transmission
01 Destination
00 Source
0F Command
00 Status
75 00 TNSW
AA Function 0xAA
02 Data size 2 bytes
97 Data File 0x97 = 151 decimal
89 Data File Type = Integer
0A Data File Element = 0x0A = 10 decimal
00 Data File sub-element 0
58 02 Data Values 0x0258 = 600 decimal
10 03 End of Transmission
4B BCC Checksum

Answer: 10 06 10 02 00 01 4F F0 75 00 06 10 03 45

10 06 Acknowledge Command
10 02 Start of Transmission
00 Source
01 Destination
4F Command Successfully Executed
F0 Status = 0xF0, Remote Status code is in the Extended Status byte
75 00 TNSW
06 Extended Status value = 6 "Address doesn't point to something usable"
10 03 End of Transmission
45 BCC Checksum

 

[andrewbe]

So that address clearly ISN'T a valid writing address, although my program isn't throwing me back the error (but the port is receiving an error) So where do we go from here? There has got to be some place I can write those parameters above 250, I just need to find the right memory location.

 

[andrewbe]

To confirm, I captured the result string of the control right after attempting this write and it does return that error. Not sure why my program didn't capture it and halt execution, but oh well.

 

[kamenges]

Can you tell me which manual you are looking at? I am looking at manual 22c-um001_-en-p, which you can find here:

http://literature.rockwellautomation.com/idc/groups/literature/documents/um/22c-um001_-en-p.pdf

In that manual there are no parameters defined between 354 and 301. In addition, everything above 301 is a display parameter, which makes it read only.

Keith

 

[andrewbe]

Yeah, I have that manual and I am not sure why there are no parameters listed between 254 - 300, because there are a bunch of them (they are right there on the drive) All of the parameters above 250 that I am attempting to edit are not listed in that manual (the ones over 300 are over 355 and are editable) I used DriveExplorer Lite to view all parameters on the drive and they also tell me which ones are read-only and which ones I can change. All the parameters I am accessing show up and the ones I need to edit are editable.

 

[kamenges]

In Drive Explorer, does this drive show up as a PF400, or does it show up as a PF40 or other?


Keith

 

[andrewbe]

In Drive Explorer, the drive shows up as "PowerFlex 400E 3P 230V 25HP"

 

[andrewbe]

I do also have a PF40 that we can test some reads and writes with, not sure if that will help at all - but I am at a standstill right now, heh.

 

[kamenges]

Did you need to copy an alternate drive template to get your copy of DriveExecutive to recognize the drive? I created an offline PF400 instance in DriveExecutive and it shows a gaping hole between 254 and 301.

You may want to try to recreate the database for the PF400 you have. Each drive is shipped with a copy of it's internal parameter structure and you you can upload that. In DriveExecutive, under the 'Drive' pulldown menu you will find 'Create Database...'. Select that and pick the path to your drive. The software should take care of the rest. It will upload the drives copy of its parameter structure and store it on your computer. If you still get those parameters displayed (260 - 300) then I am at a loss. I can't find anything that refers to them.

Keith

 

[andrewbe]

I don't think there is a different drive template, but I really have no idea. I also have DriveExplorer Lite, which doesn't give me all the options I need (mainly, the 'Drive' pulldown you speak of here) Not only does DE show those parameters, but the drive itself also shows them (I can cycle through and view them all) so I don't know...

 

[kamenges]

I'm at a loss. If you can cycle through the parameters using the HIM then the drive certainly has them. I'm just not sure why.


I have DE Lite also (V2.02). If you don't have the 'Drive' pulldown menu, how do you connect to a drive? Thatr is where the 'Connect to Drive...' selection is?

Keith