KRC2 EIP Configuration

    Hello. I've been visiting the forum for a while now, but I've never posted anything here.

    Cabinet: KRC2 ed05;

    Arm: KR 2210;

    KSS: V5.6.7

    EIP: V2.3.3


    I'm trying to configure the Robot as an Adapter (Slave) and configure my PLC as a Scanner (Master). Within the robot configuration (through the EIP board software) I used the "Local/Slave" file and associated 8 input bytes and 8 output bytes - As shown in the images.
    Then I declared the variables in IOSYS with the input and output byte sizes.

    Through my PC: I can find the KRC EIP board and I can find the PLC (ping test).

    However, I don't know what I might be doing wrong in the configuration, but I can't communicate with the KRC with the PLC.

    • Is there a need to use the "generic EDS" on the KR side, even if it is a Slave?
    • I'm using a Nexto (Altus) PLC: XP325, within this PLC I configure it as a Scanner and use a generic module to try to find the KR;


    Imgur
    Discover the magic of the internet at Imgur, a community powered entertainment destination. Lift your spirits with funny jokes, trending memes, entertaining…
    imgur.com

    [EDIT: Posting images Through imgur.]

    Edited once, last by Lamoglia (March 17, 2025 at 8:13 PM).

  • massula March 17, 2025 at 7:37 PM

    Approved the thread.

    please post any images in this forum rather than external site. when setting up EIP you need to match settings of the master and slave. on the PLC side you would use generic EDS and have input and output instances reversed (normally this is already done by different order of the entry boxes in the software you use). as always size of I/O blocks muist match.

    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

    Hello panic mode, sorry about the images.

    So, to test the EIP Board, i changed my PLC for a Rockwell (AB) PLC. But I still unsucessfull at this point. I kind newbie regarding EIP protocols, but I've done some and I've never had so many difficulties like this.

    when I tried AB PLC i configured usging the generic EDS File, but communication has not been established yet.

    Please, let me know if Im doing something wrong here, but i don't think so.


    IMAGE 01 - Configuration Generic EDS


    IMAGE 03 - When I Scan the network, I found the board; but I receive this error. But I can't generate the EDS File from KUKA Console.




    well... it is quite a while since i have done this on KRC2 but is not quite that simple... there is a bunch of steps to make that work and i am not sure which of the not mentioned things are done and if they are done correctly.

    the way i look at things is one has to have a plan... something like:

    1. decide role of each node; you stated that PLC is master and KRC is slave

    2. decide on network settings, this means addresses and mask of each node; so far i only see KRC side, not sure if PLC etc are matching that or not. this could be one or two subnets (PLC, EIP board and PC used to configure PLC need to be on one; KRC2 and PC used to configure EIP board could be on separate subnet but do not have to...)

    3. decide on size of I/O blocks; you opted for 8byte in and 8 byte out

    4. connect everything; not sure what you connected and how, in case of EIP setup on KRC2 there are 4 or 5 ethernet cables that need to be connected to an ethernet switch, two of them go to KRC2 (one to EIP board and one to KRC2 own ethernet port to transfer config to the EIP board), the third one is for PLC and the remaining one or two are for computer(s) used for configuring KRC and PLC (usually the same machine but could be separate). if only setting up KRC2, you can skip for now the PLC and the PC used to configure PLC.

    5. complete setup of the KRC2 side; this is the complicated part... more about it later

    6. complete setup of the PLC side


    so... about the complicated part... this one has many steps. one of the problems is that software used to configure the EIP board in KRC need to run on an old OS (WinXP). for that i use an old laptop (if available) or VM. one possibility is to simply run that on the KRC itself. in that case it is a good idea to use monitor as KCP display is small and cumbersome.

    so once everything is connected and networked with correct settings, one can:

    1. start EIP console,

    2. enter EIP board network settings,

    3. pick configuration name, allow "download configuration to KUKA robot" and enter KRC2 IP address (not EIP board address) with FTP user name and password.

    4. allow "Direct Access to EIP board" and select it.

    5. add "EtherNet/IP Local Slave" from Equipment Library (lower left part of the window) to your EIP board configuration (right side of the window). this should look like a tree (Ethernet > TCP/IP with board IPO > [Node] EtherNet/IP Local Slave > Item Configuration...)

    6. Under "General Configuration" you can name the device but Node need to be a unique number (i usually pick the same number as last octet of the assigned IP address) and Active Configuration need to be checked.

    7. Under "Assembly Instances" specify instances and sizes.

    8. Expand Item Configuration and edit properties of each instance. the Sizes you defined need to be processed. For example to link all inputs, select them all and click on Define Item(s) and name them and click OK. Then you will see all the signals created. Do the same for outputs.

    9. after deployment of the configuration, EIP board setup should be complete. you can ping it to see that it responds on assigned IP (note that PING test is only the very basic check)

    10. edit IOSYS.INI to enable EIP driver

    11. map the EIP signals to robot I/O. for this use unique node number that was assigned under "General Configuration"

    12. Reboot robot or use Reconfigure Driver...

    13. Now the KRC2 side should be complete.

    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

    So, lets go. I made the steps exactly as you said. But I'll check part by part here.

    1. decide role of each node; you stated that PLC is master and KRC is slave;
    R.: PLC MASTER AND KRC SLAVE;

    2. decide on network settings, this means addresses [...];
    R.: PLC - 192.168.250.255 - 255.255.255.0

    3. Pick configuration name, allow "download configuration to KUKA robot" and enter KRC2 IP address (not EIP board address) with FTP user name and password.
    R.: Did this config.

    4. Decide on size of I/O blocks; you opted for 8byte in and 8 byte out
    R.: IMAGE ATTACHED IN THIS RESPONSE.

    4. connect everything.
    R.:



    9. after deployment of the configuration, EIP board setup should be complete. you can ping it to see that it responds on assigned IP (note that PING test is only the very basic check).


    R.: I did exactly those steps for the KRC side too - The ping test is working too, I can ping the PLC from robot too (certified). I used the EIP console direct on KRC.

    as said i do not have all of my resources right now and this is something i have not seen in rather long time, so my recollection may be hazy... nah.. definitely is :smiling_face:

    so just try entering correct major/minor values in the EDS according to your EIP option version.

    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

    Quote from panic mode

    as said i do not have all of my resources right now and this is something i have not seen in rather long time, so my recollection may be hazy... nah.. definitely is :smiling_face:

    so just try entering correct major/minor values in the EDS according to your EIP option version.

    To be honest i tried all EDS that could fit from AB, but none of them worked :frowning_face:

    Quote from SkyeFire

    I'm pretty sure any address ending in .255 is an invalid IP. IIRC, .255 is used as a "broadcast" address. I would avoid using that one.

    I already tried others.


    Still no sucess into this.

    Edited once, last by Lamoglia (March 21, 2025 at 7:29 PM).

    Hello guys.

    Just for knowledge: I did it.

    1- I certified the board has no defects - Take it off and tryied to up the EIP config withou the board. To be 100% sure, I tried another EIP board (requested from KUKA);

    2- After that I installed the EIP Console on a VM (Windows XP 64 Bits - WindowsXPPro64bit);

    3- When I installed the Console on VM: I was able to Scan my network and identify my PLC. IMPORTANT: To Scan our network, you must have the "Ethernet/IP Local Slave" on your EIP project; note that it isn't activated.



    4- Then I generated the EDS on my PLC and configure the IOSys normally;

    5- Don't Forget to Reconfigure the IO Driver and make a cold start;

Advertising from our partners