VFD Guy

In my opinion, the first thing should be to determine if the drive is doing what is told. Compare the commanded speed to the output via its parameters. If they don’t match, use 750-pm001 manual block diagrams to see where the problem is. Divide and conquer 

As stated, the rpm in wrong. Also, the flux current appears very high. I would correct nameplate info and retune. Sounds like your drive is hitting a limit and folding back

Does the 3rd party servo support CIP sync and CIP motion protocols?

This is correct. If no 22 comm module installed then you need a 1203-usb 

The basics of VFD troubleshooting is to identify if the VFD is doing what it’s told. Compare commanded speed with output. Based on what you’ve stated it sounds like it’s not. This tells me the drive is hitting a limit and folding back. There should be alarms and limit statuses you can monitor. Another quick trick if you are in an open loop mode is to run without motor connected. If the it still cycles, you know to focus on the drive. If not, it’s a load or failure of the drive. At that point, I’d be looking at the logged alarms to understand more. There are regulators in the drive to overwrite the command to protect itself

1203-USB is what you need for using the DSI port. The old model was the 1203-SSS. If the drive is on a CIP network that RSLinx supports then just use CCW to connect via the network 

I think you can do this with source protection which is outside of factorytalk. Not a password but still lock it down

I use the new enet commissioning tool that is much better than the bootp tool

There are many on the knowledge base site. Some are tech connect so I don’t think I can post those here. Just search the fault name or number. My experience is that synch issues are caused by devices between the controller and plc. Check switches are set up with PTP, enable time synch with any enet modules. Things like that

Apologies. I understood the opposite in the initial post that said stand alone worked

Seems like some good convo here. If I summarize it right. Your system works stand alone but not on enet. So I go to the basics of divide and conquer. If on the problematic drive, you disconnect enet and set the settings to keypad and pot and it works then adc is not the issue. Adc only triggers on comm establishments. If you still have the issue, I would look for not fault config params on comm loss. With enet unplugged and you power cycle, set up for him and pot and it works. It has to be some setting. Can you attach .iuux CCW file so I can take a look?

K5500 don't need to be on DLR. Interesting that upgrading RSLinx fixed the issue. Nice find. I would look at the motion timing statistics in Studio to see collect data with this issue. Too much jitter will cause a synch fault.  I use FactoryTalk  Updater software (Free) to notify me when Rockwell's PCDC site has newer versions of software so you might be interested in that.

Has anyone asked if ADC is configured?

This is caused be the planner not seeing enough counts of position and the motor is not where it’s supposed to be like stated above. Could be many things. I would start with motion direct commands to verify motor and encoder are working. Obviously open the brake if one is equipped

Can you explain what the chip you replaced was?  Was this on the x comm box or 22 comm e?  Info on your error would help