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

Help with driver status change

  • vvelikov
  • June 3, 2022 at 5:46 AM
  • Thread is Unresolved
  • vvelikov
    Reactions Received
    6
    Trophies
    4
    Posts
    484
    • June 3, 2022 at 5:46 AM
    • #1

    Hello, i need help with a robot, who is changing by itself the driver status - the I on the bottom left of the screen.

    System is krc2 ed05, KSS 5.6.10 5.6.12, Safe Robot with SafeOp 2.2.6. The robot is KR150 L110

    The robot worked fine until yesterday - it asked for brake test. After it was done there was some errors - please see the attached screen.

    The problem we have is after that the robot started to change the driver status the I sign is going from red to green and back by itself.

    After we restart the robot, it is ok, can be moved by hand etc. When we execute a program in AUT mode it is starting and after a few movements stops with red I (IO status sign) and it is impossible to be moved even in T1.

    To me it looks like a bad connection somewhere, but not sure where to look exactly. We exchanged the KCP panel but the problem i still there.

    Anyone faced such situation?

    Thank you in advance!

    Images

    • braketest.JPG
      • 72.21 kB
      • 816 × 717
      • 11
  • hermann
    Reactions Received
    403
    Trophies
    9
    Posts
    2,593
    • June 3, 2022 at 9:17 AM
    • #2
    Quote from vvelikov

    .. After we restart the robot, it is ok, can be moved by hand etc...

    Can you perform a brake test after reboot?

    What are the messages after that brake test?

    Did you reboot with cold start?

  • vvelikov
    Reactions Received
    6
    Trophies
    4
    Posts
    484
    • June 3, 2022 at 9:48 AM
    • #3

    yes, we did cold start.

    The message after the breaktest you can see on my first post.

    I will try to do it again now.

    Thanks!

  • vvelikov
    Reactions Received
    6
    Trophies
    4
    Posts
    484
    • June 3, 2022 at 11:10 AM
    • #4

    after another braketest and the same message, i disabled the braketest in motiondrv.ini.

    For now it is working ok, hopefully that was the issue.

    One correction - the KSS is 5.6.12, not 5.6.10

  • hermann
    Reactions Received
    403
    Trophies
    9
    Posts
    2,593
    • June 3, 2022 at 11:21 AM
    • #5

    Normal behaviour, it seems that at least one of the breaks are worn out. Disabling the break test is only a workaround, your safety now isn't guaranteed anymore, if safemove is really neccessary.

  • vvelikov
    Reactions Received
    6
    Trophies
    4
    Posts
    484
    • June 3, 2022 at 12:15 PM
    • #6

    is that the reason the I (io drives) to change its state from green to red?

  • vvelikov
    Reactions Received
    6
    Trophies
    4
    Posts
    484
    • June 3, 2022 at 12:48 PM
    • #7

    i am looking at input 140 (Drives ON) and it is not coming even when the I is green.

    At the moment it is changing from green to red in AUT mode without a reason eben when the robot is not moving

  • hermann
    Reactions Received
    403
    Trophies
    9
    Posts
    2,593
    • June 3, 2022 at 12:56 PM
    • #8

    You are looking to an input, that comes from where? What should this input tell us about the robot state?

    You have to look for the outputs, only outputs can be controlled by robot.

  • vvelikov
    Reactions Received
    6
    Trophies
    4
    Posts
    484
    • June 3, 2022 at 1:10 PM
    • #9

    as i understand from Automatic external settings Drives on depends on input 140 by default, no?

  • hermann
    Reactions Received
    403
    Trophies
    9
    Posts
    2,593
    • June 3, 2022 at 1:21 PM
    • #10

    The input can be configured onto every input number. You can check in auto ext configuration.

    The status of drives doesn't depend only of the input drives_on. It also depends on internal status like safety controller, faults,....

    So, in your case, looking on the input doesn't make sense.

  • vvelikov
    Reactions Received
    6
    Trophies
    4
    Posts
    484
    • June 3, 2022 at 1:37 PM
    • #11

    so where i should look to fix the issue? Any direction?

    There are no errors or faults displayed ... thats the reason i struggle to find a solution :loudly_crying_face:

    Thanks for the help!

  • vvelikov
    Reactions Received
    6
    Trophies
    4
    Posts
    484
    • June 3, 2022 at 4:53 PM
    • #12

    that happens just by itself - going on and off in AUT mode :loudly_crying_face:

    Files

    VID-20220603-WA0000.mp4 7.72 MB – 16 Downloads
  • Online
    SkyeFire
    Reactions Received
    1,038
    Trophies
    12
    Posts
    9,371
    • June 3, 2022 at 6:13 PM
    • #13
    Quote from vvelikov

    is that the reason the I (io drives) to change its state from green to red?

    You mean the small icon in the bottom row of the pendant screen, that changes between a green I and red O? That's the motor power indicator, it has nothing to do with I/O drives. It turns red whenever the motors are off. I would assume that the Brake Test error caused the motors to be turned off.

    You have something causing the Safety Mode Not Possible error, that's probably blocking the drives in AUT mode. You need to fix whatever is causing that fault.

  • vvelikov
    Reactions Received
    6
    Trophies
    4
    Posts
    484
    • June 3, 2022 at 6:23 PM
    • #14

    i think the "Safety mode not possible" is caused of the disabling of SafeOp software - currently Safe monitoring is set to false.

    And as i said earlier - the robot has been working fine without an issue for more than 6 months.

    As per the red/green I - i named it drives on/of indicator as per the manual :winking_face: not sure what exacty it indicates, but usally it is green all the time after drives ON in Aut Ext or Aut or with deadman switch pressed in T1.

  • panic mode
    Reactions Received
    1,262
    Trophies
    11
    Posts
    13,027
    • June 3, 2022 at 6:35 PM
    • #15
    Quote from vvelikov

    i am looking at input 140 (Drives ON) and it is not coming even when the I is green.

    At the moment it is changing from green to red in AUT mode without a reason eben when the robot is not moving

    That is because PLC program does not check if drives are actually on. It keeps requesting drives on even when they are on. So change plc logic ...

    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

  • vvelikov
    Reactions Received
    6
    Trophies
    4
    Posts
    484
    • June 3, 2022 at 6:43 PM
    • #16

    there's no PLC connected... Just beckhoff devicenet bus coupler with some in outs.

    I just exchanged the ESC board with the same model (working for sure) but the problem is still there

  • panic mode
    Reactions Received
    1,262
    Trophies
    11
    Posts
    13,027
    • June 3, 2022 at 6:54 PM
    • #17

    Esc board has no effect on robot IO.

    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

  • vvelikov
    Reactions Received
    6
    Trophies
    4
    Posts
    484
    • June 3, 2022 at 6:58 PM
    • #18

    i am still trying to figure out where to look...

    changed it as suggested from kuka support.

    The idea was that may be a faulty esc board is throwing some errors and causing the robot to stop.

    Any idea what may cause that random red/green change of the io state?

  • panic mode
    Reactions Received
    1,262
    Trophies
    11
    Posts
    13,027
    • June 3, 2022 at 8:51 PM
    • #19

    i would start with messages. based on picture in first post, there may be a problem with value of $BRAKETEST_REQ_INT. and that value should be simply TRUE or FALSE.

    so i would collect fresh archive search for that signal. it should be in KRC MADA.

    also while there compare archive with older one when things were working. something did change and it seem to be that file was modified (intentionally or HDD corrupt).

    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

  • panic mode
    Reactions Received
    1,262
    Trophies
    11
    Posts
    13,027
    • June 3, 2022 at 9:02 PM
    • #20
    Quote from vvelikov

    there's no PLC connected... Just beckhoff devicenet bus coupler with some in outs.

    well SOMETHING is activating the input. is there a loose wire somewhere? i have seen plenty of problems due to loose connection or IO loosing power.

    also are there any devicenet communication errors?

    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