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

Simplest programming of multiple part types

  • K-Sky
  • June 29, 2016 at 10:58 PM
  • Thread is Resolved
  • K-Sky
    Reactions Received
    4
    Trophies
    3
    Posts
    196
    • June 29, 2016 at 10:58 PM
    • #1

    I am working on an existing robot that was already setup and will now be needing to run a 2nd part type. New part is basically the same part, only a little longer and larger in diameter. I initially was told that only difference between them was the height so I was just going to use a z-offset when the input is on telling me that we are running the new part. Since it will not be that simple, I am thinking of either still going with an offset where basically at the top of the program I will say something like:

    IF DI[1] on PR[1,1]=10
    IF DI[1] on PR[1,3]=28

    IF DI[1] off PR[1,1]=0
    IF DI[1] off PR[1,3]=0
    Then my nest move will be to say PR[2] Tool_Offset, PR[1]

    Or I thought about trying something like:

    IF DI[1] on R[1]=5
    IF DI[1] off R[1]=6
    Then my nest move would be PR[R[1]]
    PR[5]=new part nest pos
    PR[6]=old part nest pos

    My main concern is that with the 1st example you would need the original part on hand to reteach a position because it is based on that part with a shift to the new part. The second example lets each part type have its own distinct position. Any thoughts or input would be appreciated.

  • HawkME
    Reactions Received
    570
    Trophies
    11
    Posts
    3,270
    • June 30, 2016 at 2:33 AM
    • #2

    Your 2nd method is definitely the better way to go.

    If you ever have to do many different parts I would replace the DI with a GI and set R[1]=GI[1].

    Sent from my VS985 4G using Tapatalk

  • K-Sky
    Reactions Received
    4
    Trophies
    3
    Posts
    196
    • June 30, 2016 at 8:54 PM
    • #3

    Thanks, appreciate the 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

Users Viewing This Thread

  • 1 Guest
  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