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

collision situation

  • Mr.Pavel
  • January 20, 2020 at 4:30 PM
  • Thread is Unresolved
  • Mr.Pavel
    Trophies
    3
    Posts
    18
    • January 20, 2020 at 4:30 PM
    • #1

    On one of our robots we had a collision while operation.

    In the error log, a collision error was found (photo 3). You can see that step 0 in the program "new_tool" when a collision situation occurred.

    We want to get an answer which describes meaning about step 0. Can you say which step was when collision situation occurred? (backup attached)

    Files

    backup_and_photo.zip 253.14 kB – 22 Downloads
  • kwakisaki
    Reactions Received
    694
    Trophies
    11
    Posts
    4,770
    • January 20, 2020 at 7:36 PM
    • #2

    From what I know:

    STEP: is usually where program cursor is at (step under execution).

    CURRENT STEP: is usually the step that is being processed.

    (If CURENT STEP is a position, this usually links to the END POSE values).

    For example:

    If the Robot had just started/during/finished to execute STEP 3, and discovered a problem further down the processing list, lets say STEP 9.

    Then usually you would see:

    STEP: 3

    CURRENT STEP: 9

    I have never come across instances of STEP 0: and to compound that the CURRENT STEP: 124, this has many motion steps leading upto this, so I would expect the STEP: to be showing one of those step no.s.

    But your error appeared to occur when the Controller was in a STOP condition.

    Which could be attributed to one of your PC Program...….however, maybe looking through the error logs, operation log and exec program log may yield potentially why...………SAVE/FULL xxxx would have included this information.

    From your log:

    - There were some modifications at around 7:14 and before.

    - Main was then primed.

    - 5 minutes later motor power and teach=> repeat were set (appears you turn motor on with repeat)

    - 2 minutes later an error reset was carried out.

    - 6 s later cycle start was applied.

    - 28s later collision detected for JT2 was triggered.

    I feel there is further information that is missing, that would be relevant to finding an answer to this.

    View my channel at Industrial Robotics Consultancy Limited - YouTube

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

Similar Threads

  • Problem Line tracking Fanuc P200 RJ2

    • Piloto
    • January 11, 2020 at 10:31 PM
    • Fanuc Robot Forum
  • Get out of collision situation on SmartArc 4

    • Silverstamp
    • December 11, 2019 at 12:57 PM
    • Comau Robots
  • Problem with points after a collision or after a period of time

    • ocj
    • November 27, 2018 at 5:37 PM
    • Fanuc Robot Forum
  • How to Monitor Position Sensor (A1 ~ A7) State

    • Debu
    • November 19, 2018 at 3:35 AM
    • KUKA LBR IIWA
  • SMART 5 - NJ 110 ROBOTPRECISION

    • IlFincoITA
    • April 25, 2018 at 12:13 PM
    • Comau Robots
  • Edit Logs on KRC4

    • manhunt
    • May 15, 2017 at 4:37 PM
    • KUKA Robot Forum
  • Collision or torque

    • Casius
    • April 20, 2017 at 1:23 PM
    • KUKA Robot Forum
  • Collision detection

    • Plc_User
    • February 9, 2017 at 11:19 PM
    • Fanuc Robot Forum
  • Help : Collision Detection due to Camera attach !

    • trkfsch
    • July 26, 2016 at 1:42 PM
    • KUKA Robot Forum
  • SRVO-045 upon collision

    • dowmace
    • April 14, 2016 at 6:51 PM
    • Fanuc Robot Forum

Tags

  • collision situation
  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