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. Yaskawa Motoman 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

Shock sensor - collision detection - OFFSET problem

  • msklorz
  • October 26, 2017 at 1:57 PM
  • Thread is Resolved
  • msklorz
    Trophies
    3
    Posts
    11
    • October 26, 2017 at 1:57 PM
    • #1

    Hi, I have some doubts about that and that's why i'm asking.

    To detect collisions during operations of robot we are using SHOCK DETECTION, levels of that detection are set in few condition files. I don't have problem with that. My problem is OFFSET which is added to that levels by robot.

    What I found in Yaskawa manuals, quote :

    "To adjust to the change in the grease viscosity at a cold
    start, the offset value is automatically added to DETECT
    LEVEL until the robot has operated for a certain period of
    time.
    Thus, at a cold start, the shock detection will be performed
    only when the value is more than or equal to the sum of
    DETECT LEVEL and the offset value.
    The offset value varies depending on the manipulator type."

    165292-1CD, rev 12 , page 170


    I totally understand why it is necessary and it's normal.

    I'm checking robots on line for some time and from my observations I can tell you that every time after we start first shift robots are working with offset. It's easy to confirm by comparing shock detection condition files with current detection level on EACH AXIS LEVEL (CURRENT) window .

    My questions are:

    1. We are working only two shifts per day, is it possible that robot is adding offset because of 8 hours brake(no operation, movement during night)?
    2. If no.1 is true - after how many hours(min.) without operations, restart of robot is consider as COLD START?
    3. How long manipulator needs to work with offset, what is that "certain period of
    time"? (manipulator type: MS165)

    Thanks in advance!

  • dannyadams27
    Trophies
    1
    Posts
    3
    • April 16, 2024 at 3:30 PM
    • #2

    can shock sensor going bad cause collision detection alarm. having issues with both alarms coming up

  • 95devils
    Reactions Received
    234
    Trophies
    8
    Posts
    1,949
    • April 17, 2024 at 11:44 PM
    • #3

    Out of a Yaskawa manual.

    The cold grease factor applies when the controller is turned on and the robot has stopped for 30 minutes or longer.

    It gets canceled after 60 minutes of operation.

    I know a thing or two, because I’ve seen a thing or two. Don't even ask about a third thing. I won't know it.

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