6503 Configuration Error I/O DN2DRV

    Hello everyone,

    I would like to ask your help for an issue we have here.

    We have a robot with a C2 controller. The robot is operating for many years now with no problems and is controlled by an Allen Bradley PLC connected with DeviceNet.

    Last week we had a scheduled power outage. The robot was properly shut down and the only thing I did was to replace the CMOS battery because it time.

    When power was restored the system started well but '6503 Configuration Error I/O DN2DRV' appears in the alarm list and communication with the PLC is down.

    Power on DeviceNet is ok (24VDC) and also they are CAN+ and Can- both showing 2VDC and there's a chance the PLC is to blame (I already checked and everything seems OK).

    In the meantime I'm going deeper into all manuals and documentation by myself, is anybody of you that has already seen a similar behaviour?

    Any good suggestion?

    Thanks in advance,

    Vinz

  • Go to Best Answer
    Quote from Vincent

    Power on DeviceNet is ok (24VDC) and also they are CAN+ and Can- both showing 2VDC and there's a chance the PLC is to blame (I already checked and everything seems OK).

    There should NOT be 24V between CAN+ and CAN-. That voltage should be between the V+ and V- lines. The CAN lines won't normally show a stable voltage, given that they carry a high-frequency differential signal, but should average somewhere around 10-12VDC.

    In the robot's Log directory (probably C:/KRC/ROBOTER/LOG), examine the contents of IOSYS.LOG and the DeviceNet log file (you didn't say which DevNet interface you're using, but it should be DEVNET.LOG or possibly DNSC*.LOG)

    Hi,

    yes 24VDC are correctly across V+ and V-.

    Approx. 2VDC on CAN+ and on CAN- and this is confirmed from another robot we have that has no problems.

    This is iosys.log file:

    KUKA IOSYS LOGFILE

    ------------------

    Log Date 18.8.21 : 14:22

    open ini-file successful, version 2.00

    driver rsiLib.o information

    object file

    driver ready 1

    driver version 20003

    function entry

    input objects 0

    output objects 0

    driver DN2DRV information

    object file

    driver ready 0

    driver version 0200

    function entry

    input objects 29

    output objects 18

    IOLINKING: 0 links configured

    and this is devnet.log file

    FILE_PTR_POS=000101

    DN2Drv : Log Date 18.8.21 : 14:22

    ===== LAST_ENTRY =====

    I see IOLINKING: 0 links configured and this sounds strange, doesn't it?

    Thanks again,

    Vinz

    Hi,

    as an update I tried the command Configure > I/O Driver > Reconfigure I/O Driver that I read on papers but unfortunatelly still the driver is not running.

    Also using Telnet I executed the 'dnWho' with no answer.

    I start to think I have an hardware problem somewhere.

    Cheers,

    Vinz

    • Best Answer

    Problem is fixed now, thanks to the guidance by a very kind guy:smiling_face_with_heart_eyes:.

    One device on Devicenet is faulty, in this case a Joystick Control Unit we had for years and actually never used.

    The main suggestion I had was that if one device fails all the net crashes and so you get the alarm '6503 Configuration Error I/O DN2DRV'. Consequentelly you can't see the driver loaded nor you can try to reconfigure. Telnet also is not answering. This really surprised me but it is how apparently Devicenet works in Kuka's world:astonished_face:.

    To isolate the problematic unit it was sufficient to disable in turn each device by putting a semicolon before its macid in the devnet.ini file. Also scanning from the unit is to be disabled in the same manner in iosys.ini.

    Once the first unit is out of the polling you can see if the alarm disappears or otherwise you need to try another one.

    I hope this thread will be beneficial for another guy as me, always in search of the good answers in the weekdays and then be free for the weekend :smiling_face_with_sunglasses:.

    Edited once, last by Vincent (August 19, 2021 at 5:19 PM).

Advertising from our partners