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

Standard Program Naming

  • swilliams13
  • December 20, 2021 at 10:19 PM
  • Thread is Unresolved
  • swilliams13
    Reactions Received
    4
    Trophies
    3
    Posts
    39
    • December 20, 2021 at 10:19 PM
    • #1

    Good afternoon all-

    So I recently changed companies, and I was brought here to start their robotic welding and automation department. Our first cell here will be an Arc World 2000 from Yaskawa. I have never worked with Motoman robots before, as most of my background is in Panasonic robots. I am trying to come up with some standardization around program names. Can somebody tell me the format in which the standard programs that will come on the robot are named? Are they a combination of letters and numbers? Or are they just letters or just numbers? I want to have this in place at least somewhat before the cell shows up in the next couple weeks. Thanks in advance.

  • 95devils
    Reactions Received
    230
    Trophies
    8
    Posts
    1,936
    • December 20, 2021 at 10:39 PM
    • #2

    Any combination of upper case letters, numbers, and certain symbols are available. Assuming a YRC controller up to 32 characters.

    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.

  • swilliams13
    Reactions Received
    4
    Trophies
    3
    Posts
    39
    • December 20, 2021 at 11:12 PM
    • #3

    thanks sir.

  • FishersMoto
    Trophies
    2
    Posts
    5
    • January 26, 2022 at 3:26 AM
    • #4

    Typically model number for part is standard. You’ll have your master stack then inside you’ll call your A and B side jobs (assuming it’s a turn table style of sorts). Within your A and B side jobs you can call a certain program. I like to use “if then” statements. You will have an HMI I imagine so I would link up each part with a number to a B variable. So if let’s say part A is inputted into the HMI a b variable will change value. Your stack will start, choose what side it will go to, check to see if any part present sensors are on, and then since part A is on then B000=1(or something). Then in your stack you will have something like If B000=1 then call “partAsideA7402” your job “partAsideA7402” will then be your weld for that specific part on that specific side of the table.

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

  • K-Roset: A beginner’s journey

    • Dave Hudnutt
    • January 23, 2019 at 5:31 PM
    • Kawasaki Robot Forum
  • Ford Kawasaki Standard

    • massula
    • February 5, 2020 at 11:39 PM
    • Kawasaki Robot Forum
  • Version Control and Naming conventions

    • BOTTECH
    • March 8, 2019 at 4:33 PM
    • KUKA Robot Forum
  • Fanuc VW (VAG system) 8.23 - position register problems

    • Malgosia
    • August 15, 2018 at 3:54 PM
    • Fanuc Robot Forum
  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