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

Program can't run in AUT mode [Even with safety circuit is ok]

  • masant
  • February 9, 2017 at 3:34 PM
  • Thread is Resolved
  • masant
    Trophies
    3
    Posts
    22
    • February 9, 2017 at 3:34 PM
    • #1

    Hi everybody!

    Well, I have KUKA KR sixx R700 Agilus, using KUKA C4 Compact. I'm trying to put it in AUT Mode again. The robot worked well in this mode but, recently, I've configured some I/Os in WorkVisual to active a gripper. So, when I downloaded the program from WorkVisual to C4 Compact, some configurations, apparently, have undone. So, when I select the program and press start, in AUT mode, nothing happens. "All Commands inhibited".

    It's strange, because, this message, generally, occurs if is something wrong with the safety circuit, but it is working very well (I'm using x11 interface). I can trigger everything to run the program but the robot continues blocked. Why? I really do not know what happened, what can be unconfigured when I send the project from WorkVisual to C4. The project looks Ok, so, what errors can cause this, besides problems with safety circuit?

    I took some prints to explain and expose better the problem.

    Images

    • program_autmode_afterpress_start.png
      • 150.99 kB
      • 1,024 × 768
      • 53
    • program_autmode.png
      • 154.17 kB
      • 1,024 × 768
      • 36
    • driver_status.png
      • 37.06 kB
      • 528 × 330
      • 49
    • autext_inputs.png
      • 29.15 kB
      • 549 × 307
      • 53
    • safety_signals.jpg
      • 69.4 kB
      • 462 × 326
      • 46

    Files

    program_autmode_afterpress_start.png_thumb 17.66 kB – 52 Downloads program_autmode.png_thumb 17.62 kB – 51 Downloads driver_status.png_thumb 13.88 kB – 51 Downloads autext_inputs.png_thumb 14.74 kB – 51 Downloads safety_signals.jpg_thumb 22.85 kB – 51 Downloads
  • Schilberg
    Trophies
    3
    Posts
    40
    • February 9, 2017 at 4:28 PM
    • #2

    Try to change the signal $MOVE_ENABLE to 1025

  • panic mode
    Reactions Received
    1,300
    Trophies
    11
    Posts
    13,144
    • February 9, 2017 at 10:32 PM
    • #3

    yes.. and also enable drives.

    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

  • masant
    Trophies
    3
    Posts
    22
    • February 14, 2017 at 1:35 PM
    • #4

    I changed $MOVE_ENABLE, $DRIVES_ON and $I_O_ACT from 1026 to 1025. $DRIVES_OFF and $CONF_MESS I changed to 1026. When I did it, I thought the robot would activate. But, nothing happens. When I saw the Outputs, $STOP_MESS and $ALARM_STOP is activated. So, something is wrong.

    So, what is disturbing the robot activation? I really do not know...

    I am trying to run the program in AUT mode, but, in the future, will run in AUT EXT mode.


    Thanks!

    Images

    • IMG_20170214_092159940_HDR.jpg
      • 302.39 kB
      • 1,446 × 753
      • 31

    Files

    IMG_20170214_092159940_HDR.jpg_thumb 23.29 kB – 51 Downloads
  • panic mode
    Reactions Received
    1,300
    Trophies
    11
    Posts
    13,144
    • February 14, 2017 at 2:16 PM
    • #5

    working with robots requires certain skillset. this is why there are manuals, training etc.

    to run robot program following has to happen:
    1. select program
    2. power up drives
    3. ack. messages (this does not work on status messages, and you have four of them)
    4. issue start command

    this always applies, regardless of operating mode. you are failing to power up drives because you have problems and robot is displaying messages that need to be taken care off.

    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,300
    Trophies
    11
    Posts
    13,144
    • February 14, 2017 at 2:46 PM
    • #6

    i suggest getting System Integrator manual as a start. It was included with your robot but you may also download it from
    https://www.robot-forum.com/robotforum/man…software-cad-)/

    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

  • masant
    Trophies
    3
    Posts
    22
    • February 15, 2017 at 1:21 PM
    • #7
    Quote from panic mode


    working with robots requires certain skillset. this is why there are manuals, training etc.

    to run robot program following has to happen:
    1. select program
    2. power up drives
    3. ack. messages (this does not work on status messages, and you have four of them)
    4. issue start command

    this always applies, regardless of operating mode. you are failing to power up drives because you have problems and robot is displaying messages that need to be taken care off.

    I don't think this messages are the cause of the problem. The robot already run in AUT mode with this messages.
    This problem (robot isn't running in AUT mode) has come up when I was mapping I/Os to the gripper of my robot in WorkVisual. When I sent the project from WorkVisual to C4 compact, probably some configuration has lost. But I really do not know what can be.
    Anyway, I'll attach a print with the ack messages. But I think, that messages are about another problems that I'll resolve, not about AUT mode. [x44 has not been used and EIP is not configured totally yet.].


    I really puzzled about it because AUT mode, before IO mapping, run normally and comparing both projects, I really don't find the differences. I really confused about it.

    Images

    • ack_messages.png
      • 18.47 kB
      • 485 × 162
      • 32

    Files

    ack_messages.png_thumb 8.82 kB – 50 Downloads
  • panic mode
    Reactions Received
    1,300
    Trophies
    11
    Posts
    13,144
    • February 15, 2017 at 2:34 PM
    • #8

    you can activate previous project and be back in business.
    WoV also has compare function though i don't think it shows details for things like I/O mapping.

    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

  • masant
    Trophies
    3
    Posts
    22
    • February 16, 2017 at 3:25 PM
    • #9

    The problem has solved. Some error occurred when I tried to activate the project in WoV in the last time. So, i re-sent the project and the robot works fine again.

    Thanks for your help!

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
  • krc5
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • 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
  • krc5
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • 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