KUKA KRC4 AB PLC COMMUNICATION

    I am having trouble with establishing communication between PLC and kuka KRC4 using Ethernet/IP.

    I have version KRC4 - 8.3.34

    WoV version 6.0.27

    Used network settings:

    IP address detection range set: 192.168.1-200

    IP address on PLC 192.168.1.10

    IP address on robot 192.168.155

    The OPT package version is KRC4 EthernetIP 2.0.3.15

    I ping robot and PLC from computer and I do get a replay.

    When I click run after doing all my settings, I get the error "The wrong device is connected at the address 192.168.1.10 expected device manufacturer 121. But 1 was found. All online function will be deactivated. "

    Any ideas on what might be the error?

    the message suggests that KRC is setup as scanner (master) and expects PLC to be the adapter (slave).

    then it tries to talk to the slave (PLC) and finds that PLC is made by KUKA(121) instead of AB (1) which does not make sense... so it aborts.

    creating connection starts by determining role of each node.

    one node must be a master, the other node(s) must be slave(s).

    usually robot is the slave and PLC is the master (when CIP safety is involved, it must be like that).

    master configuration required EDS for each of connected slaves. \so your PLC project will need EDS for KRC (and not the other way around).


    if you do want PLC to be the slave and KRC to act as a master, no problem.

    in that case KRC configuration must use EDS for the PLC (not a KRC) and PLC will have no idea about KRC (PLC project will NOT have EDS for KRC).

    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

    I actually was trying for Robot to be Slave and PLC master, how do I know I have my setup this way?

    I was able to communicate them by now, now I only have the doubt if I did set the PLC as master since it is what I am trying to do.

    Don't change the input output assembly number. Keep it as 101 and 102. Then use the kuka scanner adapter 4.1 (assuming you have 4.1 ethernet IP) eds on your PLC side. Or use a generic eds with the input output and configuration assembly as show in the kuka workvisual Local Slave 1 I.e. 101, 102 and 103. And also make sure that the byte sizes are matching on either side. I have done this setup many a times. Don't forget that the AB input output are defined in word while kuka defines it in bytes.

    Lemme know if you stuck

    Quote from dalex10

    I actually was trying for Robot to be Slave and PLC master, how do I know I have my setup this way?

    I was able to communicate them by now, now I only have the doubt if I did set the PLC as master since it is what I am trying to do.

    did you install eds on kuka side or PLC?

    If PLC then PLC is master

    IF KUKA then KUKA is master

    Master always needs the EDS file

Advertising from our partners