To expand on Jeff's post above...
When you add a Powerflex drive to your ethernet tree, it creates a tag structure. That tag structure must, of course, have a data type, the same as any other tag or UDT.
Let's say you had a UDT called "MyUDT" with three elements, a BOOL called BoolTag, a DINT called DintTag and a REAL called RealTag. If you create a new tag of type MyUDT, the software knows that it needs to create structure with a BOOL, a DINT and a REAL, named as I just described.
Likewise, if you add a VSD to the ethernet tree, the software knows that it needs to create a tag structure...
but with which tags? You see, that depends entirely on which datalinks you decide to use. There are a huge number of possible combinations, and every single possible combination will result in a different tag structure, meaning each combination must by necessity have a different
data type. The data type will always start with "AB
owerFlex525", and then what follows is a largely meaningless (to the end user), but unique code of sorts which defines which tags to place in the tag structure.
Why does this matter to you? Well, in many cases, it wouldn't. You don't care what randomesque name the software has assigned to your specific data type; you just want to use the tags. But, let's say you're passing that tag structure directly into an Add-On Instruction, or using it as part of a UDT.
Now you have a problem. That AOI or UDT needs to know *exactly* what tag structure is coming in, and you need to give it *exactly* that tag structure. If you try to pass it a different tag structure - one with, say, an additional acceleration datalink - it will give you exactly the error you're describing. Basically, the AOI/UDT is saying "I require data in
exactly this structure, and you are giving me data that does not match this structure". If I had to guess, I'd say that's exactly what's going on here. It *is* just a guess of course - if that's not the case then please just ignore everything that follows, and instead post back with some more information about where the fault points you to specifically, or else zip and post the program so we can have a look.
Still here? Righto. So, how to fix it? Well, that may or may not be straightforward. The whole point of an AOI is that it's re-usable. If you have this AOI talking to 10 drives, and you've only updated the datalinks in one of them, you can't just update the AOI to accept the
new tag structure, because the other nine AOI's will then give you the exact same fault. If that's your situation, your only real option is to split out the AOI for that particular motor into a new AOI. I've had to do that before - I had a panel where 6 VSD's used my standard AOI with standard datalinks, but on the 7th, I needed to read back an encoder signal. So I had two AOI's: one called PF525, and another called PF525_ENC.
If you only have the one AOI in this situation, you can just update that AOI. In the AOI setup window, where you define all the parameters, you'll see that each Input, Output and InOut parameter has a datatype defined. All you need to do is change the datatype of the VSD tag data that's being passed in or out from whatever it is now, to AB
owerFlex525V_E_FCF91FD2:O:0.