KUKA Ethernet - EKI 2.2

  • Hello everyone


    I have been facing a strange issue with the EKI data (XML over TCP/IP) exchange between KUKA KRC4 and Beckhoff at EXT Mode.


    We use DHCP for IP assignment at Robot Interface and PLC. The firewall assigns a fixed IP.


    Beckhoff is the server and KUKA is the client.


    When the first EKI connection is established between KUKA and PLC, KUKA sends the first message which is recieved by Beckhoff. The acknowledgement message sent from Beckhoff is getting delayed in reception at the KUKA Robot. Once the first message is exchanged between Robot and PLC, other communications are faster. I tried replacing the Beckhoff here with the EKI Simulator and the case is the same.


    However, when I restart only the Robot in the network and try the EKI data communication in EXT Mode, I donot face any delay.



    I dont get this strange behaviour of the system.


    Had anyone faced this situation before, kindly guide me .


    Thanks.

  • Place your Ad here!
  • Firewall does not assign IP addresses, it blocks unauthorized traffic.

    DHCP server assigns IP addresses to nodes seeking one.


    I am not sure why would one choose to use DHCP here... but i would run WireShark to see what is going on.

    My guess is that nodes do not have correct addresses assigned on time so when KRC (and EKI client) tries to connect to server, connection times out.

    this is why it all works if KRC is rebooted - everything else is ready (already up and running)

    1) read pinned topic: READ FIRST...

    2) if you have an issue with robot, post question in the correct forum section... do NOT contact me directly

    3) read 1 and 2

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account
Sign up for a new account in our community. It's easy!
Register a new account
Sign in
Already have an account? Sign in here.
Sign in Now

Advertising from our partners