ETHlpDRV Read Error on Ethernet comm between PLC and KRC, need insight!

    Hello,

    I am trying to troubleshoot an issue that is coming up when the PLC is trying to send data to the KRC. Any help would be greatly appreciated!

    Info:

    The robot is the slave to the PLC. There is Ethernet communication between the PLC and KRC, and DeviceNet between the KRC and a Turck DNET module which controls the gripper open/close functions. The Ethernet data size is 128 bits, and the devicenet size is 16 bits. I have assigned the first 16 bits of the KRC communications data table to devicenet and 33 to 161 for the PLC to KRC comms (16 to 32 bits being a buffer zone I guess).

    I have the KRC ethernet card correctly set up as well as the generic ethernet module present in the PLC. The assembly instances and data size are good on the PLC side.

    When the PLC goes online, the generic module on the PLC shows it is talking to the KRC without error. However, on the KRC teach pendant the error 'EIP Device 0 in idle mode' and "Error Reading Ethlpdrv driver' pops up.

    On the pendent, I am able to change the data values of the DeviceNet outputs however I cannot change any data values that are shared between the PLC and the Robot.

    Please see below for the information I have entered to set this system up:

    PLC is Allen Bradley 1769-L32E

    Taken From the am.ini:

    [Archive]
    Name=u:\archive.zip\
    Config=All
    DiskNo=0
    LastDisk=1
    ID=38498b2e-77b5-425d-b794-bd679404e1af
    Date=2012-01-17_09-56-38
    [Roboter]
    RobName=KR210-2
    IRSerialNr=922112
    [Version]
    Version=V5.6.8
    [TechPacks]
    TechPacks=EtherNet/IP|
    EtherNet/IP=V2.1.0

    Taken from the IOSYS.ini:

    [CONFIG]
    VERSION=2.00


    [DRIVERS]
    ETHERNETIP=23,eipInit,eipdrv.o
    ;CNKE2=21,cnke2CPInit,cnke2drv.o
    ;DNSC6=20,dnsc6Init,dnsc6drv.o
    ;DNSC5=19,dnsc5Init,dnsc5drv.o
    ;DNSC4=18,dnsc4Init,dnsc4drv.o
    ;DNSC3=17,dnsc3Init,dnsc3drv.o
    ;CNKE1=16,cnke1CPInit,cnke1drv.o
    ;INTERBUSPCI=15,ibsCPPciInit,ibpcidrv.o
    ;DSEIO=14,dseIoInit,dseiodrv.o
    ;DNSC2=13,dnsc2Init,dnsc2drv.o
    ;DNSC1=12,dnsc1Init,dnsc1drv.o
    ;PBMASL=11,pbmsInit,pfbmsdrv.o
    DEVNET=2,dnInit,dn2drv.o
    ;INTERBUS=1,ibusInit,ibusdrv.o
    ;MFC=0,mfcEntry,mfcdrv.o

    [ETHERNETIP]
    inb4=0,0,x16 ;$in[33] to $in[161]
    outb4=0,0,x16 ;$out[33] to $out[161]

    [DEVNET]
    $inb0=5,0,x2 ;0 to 16
    $outb0=5,0,x2 ;0 to 16


    I have much more information so please ask if you feel that it would help. I am in contact with 2 KUKA techs but they are stumped and unable to work on this machine without traveling a far distance.

    Any help is greatly appreciated!!!

    Edited once, last by funkhauser (March 8, 2012 at 9:24 PM).

    EIP is still one of those things that people don't seem to know very well yet. The configuration file setup is always tricky. Unfortunately, I'm not one of those people who know EIP yet.

    I do know the config file is generally very nit-picky about seemingly insignificant details, especially when setting up the scanlist. I also know the EIP setup manual had (has?) at least one error in it.

    There should be a log file specific to the EIP driver in the log directory. That might have some additional clues.

    Yes I used the Ethernet/IP Console to set up the KUKA ethernet card. I assigned the proper IP addresses to the FTP server and the card. I also triple checked that I had the proper data size set up as well. Is this what you mean by the applicomIO configuration tool?

    I have been through the KUKA docs manuals of all kinds for EthernetIP set up as well as the configuration manuals for the KRC Software. I also spent Friday on the phone with a KUKA tech using all types of debug tools such as telelnet to see if any errors were popping up. No resolution has come of this.

    At this point I am hoping that I can get someone who says 'Oh yea, this happened to me! Check this..'. I thank all of you for providing help, please keep it coming! :applaus:

    Edited once, last by funkhauser (March 10, 2012 at 8:29 PM).

Advertising from our partners