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

Serial Communication (PC -> KUKA KRC2 5.2)

  • Guedes24
  • July 10, 2019 at 2:47 PM
  • Thread is Resolved
  • panic mode
    Reactions Received
    1,295
    Trophies
    11
    Posts
    13,130
    • October 25, 2019 at 3:59 PM
    • #21

    To communicate over DeviceNet with Fronius, there need to be DeviceNet slave interface that belongs to Fronius. There are two ways this is done according to what i experienced. Electrically both are identical but mechanically they are different:

    1. DeviceNet slave belonging to Fronius is installed at the welder (see my attachment). Then you run "long" DeviceNet cable to robot while RS485 network is very short (contained within box on the back side of the welder). This is usual setup. There would be one or two cables from Fronius to robot controller (usually two since power is separate but i was always combining them into one since only powering DeviceNet slave).

    2. DeviceNet slave belonging to Fronius is installed in the robot cabinet (your case). Then you run short DeviceNet cable to robot controller and there will be long external cable stretching RS485 interface from robot controller to Fronius. This is what you have. I think it is referred to as an economy version which is probably used as a retrofit when welder did not have DeviceNet slave interface from the start. The RS485 connections are individual wires, white or light gray. in second case they use Amphenol connectors and "long" cable that is obtained from Fronius. This comes in some standard lengths. On the robot controller one must remove one of the plates, drill holes to mount red interface connector that is prewired to EL6021 using those gray wires. This is all prewired, and there is no need to change anything.


    Either way - to create DeviceNet connection you need to connect DeviceNet cable from your robot controller to this bus coupler of the Fronius DeviceNet slave and make appropriate settings.

    Things to watch for:

    1. Fronius DeviceNet node need to be powered from robot controller

    2. shielding of DeviceNet cable, need to be grounded in one point only and that means at the robot controller end. if the DeviceNet slave is built into welder, this means disconnecting shield at that end (just pull away the spade and ZIP tie it or maybe put some tape on it.).

    3. if i recall default DeviceNet node address is 11 but this is easily changed.

    4. use same baud rate on both sides (KRC and DeviceNet slave nodes)

    5. different welders/strategies will need different size of IO map. check Fronius documentation or talk to Fronius support

    6. as with any DeviceNet bus, pay attention to terminating resistors and supply bus with 24V-ish (normally taken from 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

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
  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