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

Fanuc Intelligent Interference Fixture Question

  • dohlfhauldhagen
  • October 19, 2018 at 8:20 PM
  • Thread is Resolved
  • dohlfhauldhagen
    Reactions Received
    7
    Trophies
    3
    Posts
    59
    • October 19, 2018 at 8:20 PM
    • #1

    Hello all. So the customer I am working with would like me to use the intelligent interference function on three separate controllers to set up fixtures and critical zones. All of the robots have been updated to the exact same version. I've got all three robots communicating with RIPE on their own VLAN, and I have them all calibrated with each other. They can all see each other in the 4D graphics display and the check combinations between all of them are working. My issue is with the fixtures. If I draw in a fixture for one robot, none of the other robots can see it. Is this intended? The manual states that for the check combination setup for this, you can only set the robot's own controller as a host name when doing a combination check with a fixture. So I can't have Robot 2 have a check combination with a fixture on Robot 1 and vice versa. The manual ALSO states that the robots should be able to see each other's fixtures as quoted here:

    "The position of a fixture has to refer to the world frame of a robot, so interference check can establish the spatial relationship between the fixture and all robots. Since all robots are calibrated within the cell, even if a fixture uses robot 1 as its reference, Interference Check still can check possible collision between the fixture and robot 2, for example."

    But there is ZERO indication for robot 1 that robot 2 is in its fixtures that I set up. If I set up a critical zone box on robot 1, and set up a check combination between robot 1 + hand and that CZ, if robot 2 is in that fixture and I tell robot 1 to move into that same fixture, Robot 1 doesn't care at all that robot 2 is sitting there already, and it will drive into the fixture until it get's close enough to trigger the robot to robot interference check.

    What am I doing wrong here? Am I supposed to draw in the same fixture for robot 2 manually and then set up cross connections between the two robots that tell each robot when they are in a zone? If so, doesn't that completely defeat the purpose of IIC doing that work for you? Shouldn't each robot know when the other robot's are in their fixtures without setting up a cross connection IO bit with a PLC? I appreciate any help I can get on this. It's been driving me crazy the last few days haha. Thanks!

  • mcetinkaya40
    Trophies
    1
    Posts
    5
    • November 4, 2023 at 10:12 AM
    • #2

    Hello mate, did you find answer to your question ?

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