Emerson Exchange 365

I have not used these particular devices before, but I've found with allen bradley devices, the manuals aren't always clear that generally there are 4 bytes of padding on the input assembly you have to take into account. Don't know if you've tried this, but it might be worth a quick test.

The other thing when I get a device I can't figure out is put wireshark on the ethernet IP network. The error packets can be looked at easier there than deltav and sometimes point to what's incorrect.

In reply to Matt Forbis:

Thanks for the reply Matt. I tried to add 4 bytes to the input assembly but same thing.

I put wireshark on the network and got the error "Invalid segment in connection path (0x0315). Have you encountered this error before?

Doesn't seem like this drive works with third-party controllers aside from those from Allen-Bradley.

In reply to Michael Caparros:

Since I had not really heard of these drives before, I did a bit of looking this morning and I was struggling greatly to find an EDS file for this drive to look at much information at all. It does seem that they put Motion Controllers in a separate category and that requires special features in the PLC's as well, so there might be something to the not working with third party controllers. I'm also not familiar with that error message as a common one I've seen with wireshark.

Sorry I'm not much help. I'm sure Rockwell isn't going to be much help either and I see you've already opened a call with the GSC. Good luck! If you do figure it out, let us know here so we can help others in the future.

In reply to Matt Forbis:

This Kinetix appears to support stand alone mode - which should enable it to be programmed to allow control via conventional IO. If that is not acceptable:
If you have Rockwell Tech Connect support (or your customer?) you need call and get put through to the drives / motion group to ask about Class 1 interfacing.
If you do not have tech connect support, then call your local electrical supply house (who sells AB equipment) and ask for their help with getting that info. Kirby Risk in our area is excellent at helping us get help - but we also have tech connect support.
I've not looked but the support number might be in the manual for the drive.

You are lucky. on a recent project, the only servo drive for a particular motor that the vendor could get was a Kinetix with no ability to operate in stand alone. so we have a CompactLogix to translate between a PK and the drive using the Logix Tags interface in the PK.

NOTE to Greg Lonza: Would be very nice if PK Ethernet IP options could handle all the permutations that the VIM2 can!

I haven't seen any examples of integrations of the Kinetix 1500 but there are several reports of other users integrating the Kinetix 300 using Explicit messaging.

The EtherNet/IP user manual for the 1500 (literature.rockwellautomation.com/.../2198-um004_-en-p.pdf) states the following on page 228:

**The Kinetix 5100 drive is working in I/O mode when the Control Mode
parameter ID117 (P1.001) is set to 0x0C**. In this mode, commands come from
the programmable controller through the I/O assembly.

Three assembly instances, Output 104, Output 106, and Input 154 are supported
only with Class 1 I/O mode communication with the Kinetix 5100 drive.

**No configuration assembly is supported by the Kinetix 5100 drive.**

I would check to make sure that the 1500 is correctly set to I/O mode first.

The error message, "Invalid segment in connection path (0x0315)" is a general error message reported by the device indicating that something is wrong in the connection path used by the controller. The statement that "No configuration assembly instance is supported by the Kinetix 5100 drive" could suggest that the 1500 does not support a configuration assembly as part of the connection. By default the PK controller uses a configuration assembly instance 0 of size 0 which might explain the exception response.

Alternatively, the user manual on page 19 seems to suggest that the 1500 supports Class 3 EtherNet/IP Explicit Messaging Control from 3rd Party controllers.

In reply to Jake Nichelson:

literature.rockwellautomation.com/.../2198-um004_-en-p.pdf

In reply to Jake Nichelson:

Thanks Jake! We've got confirmation from Kinetix specialists that the 5100 does not support Class 1 messaging from third-party controllers. Class 3 Messaging can be used instead.

However, I tried to configure a Class 3 LDT but I'm getting an "Attribute not supported" error in Wireshark. The PK sends an attribute of "0" but the Kinetix may be expecting a different value. But I can't figure out where to change this attribute parameter. I believe in VIMs you can explicitly specify the the attribute parameter but not in PK.

In reply to Michael Caparros:

Found the Attribute ID in the signal and changed it to 1. Got it communicating.

In reply to Michael Caparros:

Can you provide any more information on how you set up your LDT for this? Thank you!

In reply to timothy.sullivan:

We´re having the same issue to get the communication to work using Class 3 LDS´s to 5100.
Can you please provide some more information how to get it working?