1. Home
    1. Dashboard
    2. Search
  2. Forum
    1. Unresolved Threads
    2. Members
      1. Recent Activities
      2. Users Online
      3. Team Members
      4. Search Members
      5. Trophys
  3. Articles
  4. Blog
  5. Videos
  6. Jobs
  7. Shop
    1. Orders
  • Login or register
  • Search
This Thread
  • Everywhere
  • This Thread
  • This Forum
  • Articles
  • Pages
  • Forum
  • Blog Articles
  • Products
  • More Options
  1. Robotforum - Support and discussion community for industrial robots and cobots
  2. Forum
  3. Industrial Robot Support and Discussion Center
  4. KUKA Robot Forum
Your browser does not support videos RoboDK Software for simulation and programming
Visit our Mainsponsor
IRBCAM
Robotics Channel
Robotics Training
Advertise in robotics
Sponsored Ads

Error "Configuration error I/O driver DN2DRV" when configuring Devicenet network device on (V)KRC2ed05.

  • PhunxamLinda
  • February 9, 2025 at 9:23 AM
  • Thread is Resolved
  • PhunxamLinda
    Reactions Received
    1
    Posts
    171
    • February 9, 2025 at 9:23 AM
    • #1

    Hello everyone, Hello experts.

    I am currently getting the error "Configuration error I/O driver DN2DRV" when configuring the Devicenet network device on (V)KRC2ed05. Can everyone help me check the status and if my settings are correct and guide me to fix this error? Thank you very much everyone.

    ==>MY CONNECTED STATUS IS:
    - Omron Digital I/O module includes: DRT2-ID16-1 + XWT-OD16-1. Node Address on DRT2-ID16-1 is (X10=1 and X1=0).
    - Analog Output module: DRT2-DA02. Node Address on DRT2-DA02 is (X10=2 and X1 = 1).

    - The DRT2-ID16-1 and DRT2-DA02 modules have been connected in series to the Devicenet pin on the MCF3 card with 120 Ohm resistors at 3 nodes.
    - The internal power supply for the Devinet module is taken from (V)KRC2ed5.
    - The I/O power supply for the 2 DRT2-ID16-1 and DRT2-DA02 modules is taken from an external source.


    CONTROL PINS ON THE MODULES I HAVE CONNECTED:
    ==> Request to Control Spindle On/Off via Delta C2000 Inverter (VFD110C43A) using Digital Output signal:
    - Connect pin OD0 on Module XWT-OD16-1 to pin MI1 on Delta C2000 inverter.
    - Pins G and V on Module XWT-OD16-1 are connected to an external 24V power supply.
    - Connect Pin G on Module XWT-OD16-1 to the DCM pin on VFD.
    ==> Requirements for Controlling Forward/Reverse Rotation of Spindle via Delta C2000 Inverter (VFD110C43A) using Digital Output signal:
    - Connect pin OD1 on Module XWT-OD16-1 to pin FWD on Delta C2000 Inverter to control Forward running.
    - Connect pin OD2 on Module XWT-OD16-1 to pin REV on Delta C2000 Inverter to control Reverse running.
    ==> Request to Control Spindle Speed via Delta C2000 Inverter (VFD110C43A) using Analog Output signal:
    - Connect pin V0+ on DRT2-DA02 Module to AVI pin on Delta C2000 Inverter.
    - Connect pin 0- on DRT2-DA02 Module to ACM pin on Delta C2000 Inverter.
    ==> Request to Control Open/Close of compressed air supplied for Changing the Knife on Spindle via 24V Solenoid Valve using Digital Output signal:
    - Connect pin OD3 on XWT-OD16-1 Module to 24V+ pin on Solenoid Valve.
    - Connect pin G on XWT-OD16-1 Module to 0V pin on Solenoid Valve.
    ==> Receive feedback signal from the Automatic Knife Compare head (4 wires divided into 2 pairs of Normally Closed Wires (NC) Red - Black and Blue - White) through Digital Input Signal.
    - Connect 2 Black and White wires in 2 pairs of NC wires to Pin G on Module DRT2-ID16-1.
    - Connect 1 Red Wire to ID0 pin.
    - Connect Blue Wire pin to ID1.

    ==>ERROR STATUS.
    - MS (Module Status) light on Module DRT2-ID16-1 is Green.
    - NS (Network Status) light on Module DRT2-ID16-1 is Green.
    - MS (Module Status) light on Module DRT2-DA02 is Green.
    - NS (Network Status) light on DRT2-DA02 Module flashes Blue

    - The screen displays an error message “Configuration error I/O driver DN2DRV”.

     Can everyone please check if the above connections are correct with my control requirements and please check the 2 DEVNET.INI and IOSYS.INI files that I configured below to see where they are wrong and help me fix them? Thank you very much everyone.

    Files

    devnet.txt 113 Byte – 2 Downloads iosys.txt 9.04 kB – 2 Downloads

    Edited 3 times, last by PhunxamLinda (February 9, 2025 at 9:35 AM).

  • PhunxamLinda
    Reactions Received
    1
    Posts
    171
    • February 9, 2025 at 9:36 AM
    • #2

  • PhunxamLinda
    Reactions Received
    1
    Posts
    171
    • February 9, 2025 at 9:37 AM
    • #3

  • PhunxamLinda
    Reactions Received
    1
    Posts
    171
    • February 9, 2025 at 9:38 AM
    • #4

  • hermann
    Reactions Received
    407
    Trophies
    9
    Posts
    2,614
    • February 9, 2025 at 9:54 AM
    • #5
    Quote from PhunxamLinda

    - Omron Digital I/O module includes: DRT2-ID16-1 + XWT-OD16-1. Node Address on DRT2-ID16-1 is (X10=1 and X1=0).
    - Analog Output module: DRT2-DA02. Node Address on DRT2-DA02 is (X10=2 and X1 = 1).

    You have two nodes with same address, fail, every node needs unique address. So devnet.ini is wrong.

    Quote from PhunxamLinda

    The DRT2-ID16-1 and DRT2-DA02 modules have been connected in series to the Devicenet pin on the MCF3 card with 120 Ohm resistors at 3 nodes.

    You need only two resistors, one at each end of the bus.

    In iosys.ini you must move the [DEVNET] section before [END SECTION]

    Just the three first and easy to find fails:icon_mrgreen:

    Descriptions of connections on i/o side of the modules at this stage aren't necessary, as long as you haven't created a short, it doesn't matter.

    When having problems with devicenet modules it's a good idea to connect only one, and try to configure everything until it works. Then adding the other ones.

  • PhunxamLinda
    Reactions Received
    1
    Posts
    171
    • February 9, 2025 at 10:34 AM
    • #6

    Thank you for your response. I think the Node address in the 2 Modules is different: in DRT2-ID16-1 it is: 10, and in DRT2-DA02 it is 21. Can you explain where it is similar and how to fix it? Thank you.

    Quote from hermann

    You have two nodes with same address, fail, every node needs unique address. So devnet.ini is wrong.

    You need only two resistors, one at each end of the bus.

    In iosys.ini you must move the [DEVNET] section before [END SECTION]

    Just the three first and easy to find fails:icon_mrgreen:

    Descriptions of connections on i/o side of the modules at this stage aren't necessary, as long as you haven't created a short, it doesn't matter.

    When having problems with devicenet modules it's a good idea to connect only one, and try to configure everything until it works. Then adding the other ones.

    Display More

    I put one resistor at the beginning of the MCF3 circuit, 1 resistor at DRT2-16-1 and 1 resistor at DRT2-DA02. where is there an extra resistor? can you explain it to me. thank you.

  • PhunxamLinda
    Reactions Received
    1
    Posts
    171
    • February 9, 2025 at 12:30 PM
    • #7

    This is the edited IOSYS file, can you help me see if there is anything wrong, the Configuration error I/O driver DN2DRV error still hasn't disappeared. Thank you.

    (Gigital Input Module DRT2-ID16-1 with actual Node Address is (X10=1, X1=0). Analog Output Module DRT2-DA02 with actual Node Address (X10=2, X1=1). Module DRT2-DA02, DIP on Module DRT2-DA02 has the following positions: (2,5,7,8 ON, 1,3,4,6 OFF).)

    Files

    iosys.txt 9.21 kB – 3 Downloads
  • hermann
    Reactions Received
    407
    Trophies
    9
    Posts
    2,614
    • February 9, 2025 at 1:58 PM
    • #8

    Sorry, thought that you have three modules. Haven't seen your pictures, they weren't there when I red the post:thinking_face:. So the digital i/o is only one module, addresses are OK.

    But in devnet.ini you must change [3] to [2]. You have two modules, so you should have sections [1 ] and [2].

    As already told you need two resistors, when you have three, you have one too much. The resistor at digital i/o module is the one you must disconnect. It is in the middle of the bus, not at the end. From there your bus is continued to the A/D module.

  • PhunxamLinda
    Reactions Received
    1
    Posts
    171
    • February 9, 2025 at 2:50 PM
    • #9

    Thank you. Here is my connection diagram. Does it look correct?

  • hermann
    Reactions Received
    407
    Trophies
    9
    Posts
    2,614
    • February 9, 2025 at 3:22 PM
    • #10

    NO. Remove the resistor in the middle. And you must provide 24v to V+ / V-.

  • PhunxamLinda
    Reactions Received
    1
    Posts
    171
    • February 9, 2025 at 3:27 PM
    • #11

    Thank you very much. Tomorrow I will remove the 120 Ohm Resistor in the DRT2-ID16-1 Module and check it. I used 24V power supply from the 24V source in the electrical cabinet through the fuse to the V+ and V- pins.

  • PhunxamLinda
    Reactions Received
    1
    Posts
    171
    • February 9, 2025 at 3:30 PM
    • #12
    Quote from hermann

    Sorry, thought that you have three modules. Haven't seen your pictures, they weren't there when I red the post:thinking_face:. So the digital i/o is only one module, addresses are OK.

    But in devnet.ini you must change [3] to [2]. You have two modules, so you should have sections [1 ] and [2].

    As already told you need two resistors, when you have three, you have one too much. The resistor at digital i/o module is the one you must disconnect. It is in the middle of the bus, not at the end. From there your bus is continued to the A/D module.

    I have 3 Modules, but XWT-OD16-1 Module is an extension Module of DRT2--ID16-1 Module so I think it shares the same address with this Module.

    Images

    • Screenshot_9.jpg
      • 77.36 kB
      • 841 × 494
      • 2
  • PhunxamLinda
    Reactions Received
    1
    Posts
    171
    • February 10, 2025 at 2:35 AM
    • #13

    Thank you very much. After fixing the errors according to your instructions and removing a resistor in the DRT2-ID16-1 module, I was able to remove the "Configuration error I/O driver DN2DRV" error. The MS (Module Status) and NS (Network Status) lights on the 2 Digital DRT2-ID16-1/Analog DRT2-DA02 modules have turned to a stable Green color.

    Can you tell me why the Robot Axes have to be Mastered again after I cold start?

    And can you give me more instructions on how to Map the connected devices to these 3 modules? Thank you very much.

  • Online
    SkyeFire
    Reactions Received
    1,052
    Trophies
    12
    Posts
    9,431
    • February 10, 2025 at 3:20 PM
    • #14
    Quote from PhunxamLinda

    Can you tell me why the Robot Axes have to be Mastered again after I cold start?

    That's because of the error 284 ("Accu Voltage") in your first photo. The KRC2 cannot retain Mastering through a Cold Start unless the batters (two 12V sealed lead-acid motorcycle-type batteries, located in the bottom of the controller) are healthy and charged. These batteries generally need to be replaced every 3 years. After replacement, leave the KRC powered up for at least 12-24hrs to ensure the batteries are fully charged before shutting down again.

  • PhunxamLinda
    Reactions Received
    1
    Posts
    171
    • February 11, 2025 at 1:38 AM
    • #15
    Quote from SkyeFire

    That's because of the error 284 ("Accu Voltage") in your first photo. The KRC2 cannot retain Mastering through a Cold Start unless the batters (two 12V sealed lead-acid motorcycle-type batteries, located in the bottom of the controller) are healthy and charged. These batteries generally need to be replaced every 3 years. After replacement, leave the KRC powered up for at least 12-24hrs to ensure the batteries are fully charged before shutting down again.

    Thank you very much for taking the time to answer my questions, sorry for the slow response. Regarding the Robot's battery, I have replaced 2 new batteries for the Robot, and charged it for more than 12 hours, but it still does not clear the error. I have consulted many previous questions but no one has a complete answer to clear this error, so I have not opened a topic about this issue.

    As for the issue of connecting Devicenet devices, I have completed it, now there is the task of mapping the devices to the Controller. Do you think I should close this topic and open another topic about how to map external devices to the controller (V)KRC2ed05? Thank you very much again.

  • Online
    SkyeFire
    Reactions Received
    1,052
    Trophies
    12
    Posts
    9,431
    • February 11, 2025 at 4:32 PM
    • #16
    Quote from PhunxamLinda

    I have replaced 2 new batteries for the Robot, and charged it for more than 12 hours, but it still does not clear the error.

    Check the voltage being applied to the batteries while the KRC is powered up. It should be ~27VDC.

    Quote from PhunxamLinda

    As for the issue of connecting Devicenet devices, I have completed it, now there is the task of mapping the devices to the Controller. Do you think I should close this topic and open another topic about how to map external devices to the controller (V)KRC2ed05?

    Might as well keep it here so we retain history.

  • PhunxamLinda
    Reactions Received
    1
    Posts
    171
    • February 13, 2025 at 3:12 PM
    • #17

    Thanks for replying me, sorry to read this message now, I have not been online for a few days. About this error I will probably close this topic. Currently my Robot is having errors about Safety issues, so I will open a topic to discuss it. Once again very grateful for your help, thank you very much.

Advertising from our partners

IRBCAM
Robotics Channel
Robotics Training
Advertise in robotics
Advertise in Robotics
Advertise in Robotics

Job Postings

  • Anyware Robotics is hiring!

    yzhou377 February 23, 2025 at 4:54 AM
  • How to see your Job Posting (search or recruit) here in Robot-Forum.com

    Werner Hampel November 18, 2021 at 3:44 PM
Your browser does not support videos RoboDK Software for simulation and programming

Tag Cloud

  • abb
  • Backup
  • calibration
  • Communication
  • CRX
  • DCS
  • dx100
  • dx200
  • error
  • Ethernet
  • Ethernet IP
  • external axis
  • Fanuc
  • help
  • hmi
  • I/O
  • irc5
  • IRVIsion
  • karel
  • kawasaki
  • KRC2
  • KRC4
  • KRC 4
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • robodk
  • roboguide
  • robot
  • robotstudio
  • RSI
  • safety
  • Siemens
  • simulation
  • SPEED
  • staubli
  • tcp
  • TCP/IP
  • teach pendant
  • vision
  • Welding
  • workvisual
  • yaskawa
  • YRC1000

Thread Tag Cloud

  • abb
  • Backup
  • calibration
  • Communication
  • CRX
  • DCS
  • dx100
  • dx200
  • error
  • Ethernet
  • Ethernet IP
  • external axis
  • Fanuc
  • help
  • hmi
  • I/O
  • irc5
  • IRVIsion
  • karel
  • kawasaki
  • KRC2
  • KRC4
  • KRC 4
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • robodk
  • roboguide
  • robot
  • robotstudio
  • RSI
  • safety
  • Siemens
  • simulation
  • SPEED
  • staubli
  • tcp
  • TCP/IP
  • teach pendant
  • vision
  • Welding
  • workvisual
  • yaskawa
  • YRC1000

Tags

  • KRC2
  • Devnet
  • (V)KRC2ed05
  • Thiết bị mạng

Users Viewing This Thread

  • 3 Guests
  1. Privacy Policy
  2. Legal Notice
Powered by WoltLab Suite™
As a registered Member:
* You will see no Google advertising
* You can translate posts into your local language
* You can ask questions or help the community with your knowledge
* You can thank the authors for their help
* You can receive notifications of replies or new topics on request
* We do not sell your data - we promise

JOIN OUR GREAT ROBOTICS COMMUNITY.
Don’t have an account yet? Register yourself now and be a part of our community!
Register Yourself Lost Password
Robotforum - Support and discussion community for industrial robots and cobots in the WSC-Connect App on Google Play
Robotforum - Support and discussion community for industrial robots and cobots in the WSC-Connect App on the App Store
Download