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

I/O Clarification - Help needed

  • darth0
  • June 10, 2025 at 8:30 AM
  • Thread is Unresolved
  • darth0
    Reactions Received
    4
    Posts
    148
    • June 10, 2025 at 8:30 AM
    • New
    • #1

    Greetings !

    I tackled the System ladder of our robot as i want to learn how it actually functions.

    Im having some troubles understanding some adresses, what exactly they are.

    Lets take "Line 14" on the bellow picture as an example.

    Are adresses #70364 , #70267 and #70243 auxiliary relays which are used to map/save certain signals ( for example wire sticking checking) and are then further used as a signal.

    If i understand correctly, the parameters S4C080-S4C095 are used to clear/hold the statuses of theese relays upon powerup/poweroff.

    In this line, #70243 is the exit (Q). When the requirements are met does that turn the bit in #70243 into a 1 ?


    We would want to implement a signal that would tell us if a welding arc has been established. For example using something like a current Clamp to measure if there is actual current running and then map that signal to one of theese auxiliary relays and use the said signal in the ladder for producing an alarm & stopping the robot.

    Currently the problem is as follows: Robot will start a weld, the wire will sometimes get burned off and welded to the nozzle. The robot will continue through the program untill it gets to the next ARCON instruction where it then stops beacuse of alarm 9001 - Missing Arc start confirm ( signal logic that arc start cannot be performed).

    Then it is uppon the operator of the robot to guide the robot to the spot where the welding actually stopped and restart the program ( which is a problem because our operators arent really schooled to be doing that).

    Thats why we would like to implement a signal that would stop the robot immediately when there isnt an arc established when it should be.



    Ty for all the help and clarification on this topic.

    Edited once, last by darth0 (June 10, 2025 at 11:05 AM).

  • 95devils
    Reactions Received
    233
    Trophies
    8
    Posts
    1,946
    • June 10, 2025 at 7:12 PM
    • New
    • #2

    Why don’t you change the Restart Mode under your Arc Auxiliary Conditions?

    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.

  • darth0
    Reactions Received
    4
    Posts
    148
    • June 11, 2025 at 7:32 AM
    • New
    • #3
    Quote from 95devils

    Why don’t you change the Restart Mode under your Arc Auxiliary Conditions?

    Ty for the reply !

    Im new at the job ( about 8 months in) and im still learning the system, i had no formal yaskawa training and had to learn everything from pdfs myself.

    The problem with arc auxiliary conditions is they dont seem to work.

    Its been explained to me that our welder ( source) doesnt have a communication card ( not sure what a communication card actually does/what it is). So using Arc start files/ Arc end files has no effect, we use macros made by yaskawa to call welding jobs ( actual welding parameters) saved in our welder.

    When using arc start & end files, nothing set in there has an actuall effect on the welding parameters.

    This is how our arc auxiliary file is set up right now, yet it doesnt actually do anything. It doesnt shift when it comes on a spot with bad conductivity ( glass left over from a previous weld-dont know the word for it in english) , when wire sticking happens it does nothing.

    Should using and auxiliary cond file be specified in any special way in the program?

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

  • Help me understand the pulsecoder and mastering data

    • gpunkt
    • November 22, 2023 at 2:32 PM
    • Fanuc Robot Forum
  • Problems with WorkVisual 6.0. Incorrect operation when transferring files

    • Tat_Iron_Man
    • February 25, 2025 at 9:23 AM
    • KUKA Robot Forum
  • Kuka krc2 config question

    • DabLin
    • July 16, 2024 at 9:09 PM
    • KUKA Robot Forum
  • iRPickTool getting started and external vision system

    • PZoumpoulis
    • October 5, 2023 at 1:27 PM
    • Fanuc Robot Forum
  • Clarification of robot terminology Tool Frame vs TCP

    • Askic
    • November 2, 2022 at 12:34 PM
    • Robot Geometry, Linear Algebra, Forward and Inverse Kinematics

Tags

  • I/O mapping
  • I/O help

Users Viewing This Thread

  • 3 Guests
  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