Help with Powerflex 4M drives

[plcdp 11]

Help with powerflex 4m drive communication Hello, I have a machine with 4 powerflex 4m drives that are networked using a 22-XCOMM-DC-BASE with a 22-comm-e card attached. Backstory....There was a power surge at the plant that took out the power supply portion of this module. Dead short. After getting some bad info from tech support, they told me I could remove the 22-comm-e chip and install in the new unit and all should be good. Here's where I screwed up....even though the chip looked to be soldered in, I believed them and proceeded to try and to remove the chip. In the process I broke one of the tangs that was soldered in. I have a replacement module, and even though I can successfully send an IP address to it via bootp dhcp tool, it is not happy and doesn't properly communicate with the drives. Been back and forth with support from my distributer, and still not having any luck. I was able to position the bent/broken tang to touch consistently and got the machine up and running, but I don't know how long it will last. I can connect via ethernet to the working unit via CCW and see all its parameters. I need to know what I need to upload those parameters and download them to the new unit I have as a spare. When I install the new unit and give it the proper IP address, I can see it on RS links, but get an error when I try to connect via CCW. I feel like I am close, but definitely missing something. Any ideas would be appreciated. Thank you, Dave

[BobLfoot 302]

Just to clarify is your spare item a 22-XCOMM-DC-BASE , a 22-COMM-E Card or a Powerflex 4M Drive?

First thought that comes to mind is firmware mismatch.

[plcdp 11]

11 hours ago, BobLfoot said:

Just to clarify is your spare item a 22-XCOMM-DC-BASE , a 22-COMM-E Card or a Powerflex 4M Drive?

First thought that comes to mind is firmware mismatch.

My spare is both the base and the comm-e card. How can I determine if there is a firmware mismatch?

 

Thank you for the reply,

Dave

[VFD Guy 13]

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