This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM2434: Can’t change the IP configuration mode by Rockwell EtherNet/IP Address Commissioning Tool

Part Number: AM2434

Hi Nilabh,

The problem about the device with fiemware v9.0.0.3 can’t change the IP configuration mode by Rockwell EtherNet/IP Address Commissioning Tool is described here.

  1. When we use the tool to send the request to change the IP configuration mode to “Static”, the
    tool responds the device don’t support CIP and the mode change fail.
    We wonder if it’s also a firmware issue, and if it could be fixed.

The WireShark data is as below.

IPConfigModeFail.zip

Thank you for the support.

Bo-Cheng

  • Hi

    We are check on this with Kunbus, We will get back on it by early next week

  • Hi Nilabh,

    Could you ask Kunbus for update?

    thank you

    Bo-cheng

  • Hi Nilabh,

    ==== previous answer from Kunbus ====

    Can’t change the IP configuration mode by Rockwell EtherNet/IP Address Commissioning Tool

    1. Q) When we use the tool to send the request to change the IP configuration mode to “Static”, the tool responds the device don’t support CIP and the mode change fail.  We wonder if it’s also a firmware issue, and if it could be fixed.

      A) From Wireshark log is visible that Rockwell EtherNet/IP Address Commissioning Tool tries to get the class attribute 2 (Max Instance) - not required or conditional attribute, which is not supported by our device, that´s why it responds with an error code in this case. But seems that this tool requires this attribute to be supported and that´s why it stops requesting after this.

    ===============================

    After many test with Rockwell controller/PLC tools (studio 5000), I think we have the necessary to support the class attribute 2 and class attribute 3 because it's very important for customers' usages, and it does also support by other brands' drives, like Festo and A-B.

    The reason is that if we don't support these two attributes, customers can't not change the IP configuration modes between the DHCP mode and the static mode by Rockwell tools. That means the IP address setting will be lost every time under the DHCP mode when a drive power is turned off, but a customer have no way to config it to the static mode to keep the IP addresss setup.

    Plases help to forward our message to Kunbus teams.

    We are very appreciated for your help.

    Bo-Cheng

  • Response from Kunbus:

    I now tried locally with my launchpad to add Class Attributes 2 and 3, each with fixed value 1 to the TCP/IP Interface Object and the EtherNet/IP Address Commissioning Tool permits me to change from static to dynamic configuration. It only switches between Stored Value and DHCP in the Configuration Control Attribute (Attribute 3) of the TCP/IP Interface Object.

    I will create a Jira ticket and we will pick it up for the next release.

    Martin

    PS: I have not yet run any conformance test with those modifications

  • The IP configuration feature has confirmed at V9.0.7.

    Thank you for the help

  • Thanks Bo-Cheng will close the thread now.