Reading L5X file

[jasond149]

I am trying to automate code dev for VFDs and I was looking at the L5X for a VFD, I am wondering how to parse the cdata. Below is a small snippet of the cdata I am trying to understand, if more of the L5X file is need, please let me know.

4,34,0,0,4,0,0,0,0,0,0,0,0,0,0,0,25,0,0,0,8,-106,0,0,0,1,0,0,0,1,0,0,0,8,0,0,0,75,2,32,-110,36,0,-1,-1,0,0,0,81,33,0,0,8,30,0,0,0,1,0,0,0,1,0,0,0
,9,0,0,0,16,3,32,-109,36,0,48,2,3,1,0,0,0,10,0,0,0,16,3,32,-109,36,30,48,9,1,0,1,0,0,0,10,0,0,0,16,3,32,-109,36,31,48,9,-52,1,1,0,0,0,10
,0,0,0,16,3,32,-109,36,32,48,9,60,0,1,0,0,0,10,0,0,0,16,3,32,-109,36,33,48,9,105,0,1,0,0,0,10,0,0,0,16,3,32,-109,36,34,48,9,64,0,1,0
,0,0,10,0,0,0,16,3,32,-109,36,35,48,9,4,0,1,0,0,0,10,0,0,0,16,3,32,-109,36,36,48,9,-42,6,1,0,0,0,10,0,0,0,16,3,32,-109,36,37,48,9,-112

 

[JeremyM]

PowerFlex 525?

The CDATA blob of bytes is assembled by an add-on-profile and represents the parameter set provided to the drive each time the connection is established - the drive then unpacks these to configure itself.

Keep in mind the bytes here are represented by the SINT type in Logix, so the 'negative' values aren't really that.

If you modify parameters in the AOP, you can see the CDATA change after you export it; the AOP-defined type hides the connection 'C' data, so export is necessary to see the change.