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

Speed of servo spotgun

  • Tushar_Patil
  • February 7, 2016 at 8:29 AM
  • Thread is Resolved
  • Tushar_Patil
    Trophies
    3
    Posts
    90
    • February 7, 2016 at 8:29 AM
    • #1

    Friend, how to increase the spped of sevo gun while executing spot instruction. Currently in auto mode the spot execution is slow approx it requires 2sec for each spot and i had worked in kuka robot it requires only a second to take spit. What are the changes to be made in moc.cfg file?? Plz suggest or mail me the backup or moc file. Robot usef is 6700 with 6.2. Robotware

  • M.Ozkan
    Reactions Received
    22
    Trophies
    5
    Posts
    538
    • February 8, 2016 at 5:14 PM
    • #2

    You can change in System Configuration->Stress Duty Cycle->Speed absolute Max

    or in Moc.cfg key "Stress Duty Cycle"

    Speed absolute max=rpm

  • Tushar_Patil
    Trophies
    3
    Posts
    90
    • February 9, 2016 at 2:34 AM
    • #3

    Thank yoy fluke,
    Now it is 400 if i calculate it, it comes 523 rad/sec. I had increased acceleration & deceleration by 2 it is giving some result but still if we look the spot parameter the total cycle are 35 to 40 means it requires only 0.8 to 1. Sec yo execute a spot but robot holds the gun for approximately 2 sec. How it could be reduced? Any idea.

  • M.Ozkan
    Reactions Received
    22
    Trophies
    5
    Posts
    538
    • February 9, 2016 at 6:47 PM
    • #4

    I guess it is not speed problem.

    Which one weld controller to be used in robot?

  • Tushar_Patil
    Trophies
    3
    Posts
    90
    • February 10, 2016 at 8:40 AM
    • #5

    Obara with devicenet communication.

  • M.Ozkan
    Reactions Received
    22
    Trophies
    5
    Posts
    538
    • February 10, 2016 at 7:22 PM
    • #6

    Normally gun will open when "Weld Completed" signal comes from weld controller. If weld completed signal is delayed e.g cause of Squeeze or Hold parameter in weld controller, robot will stay closed position.

    General sequence of SpotWeld:

    Gun Close (Robot)
    Apply Force and optional measure thickness (Robot)
    Weld Start signal (To weld controller)
    Wait weld Complete signal (from weld controller)
    Open Gun (Robot)


    You can look spot parameter "Squeeze" and "Hold"

    Note: May be Obara has a different parameter name.

    Images

    • Untitled.jpg
      • 104.74 kB
      • 859 × 590
      • 132

    Files

    Untitled.jpg_thumb 14.33 kB – 23 Downloads

    Edited once, last by M.Ozkan (February 11, 2016 at 10:38 AM).

  • Tushar_Patil
    Trophies
    3
    Posts
    90
    • February 11, 2016 at 6:11 PM
    • #7

    My parameter are so nominal
    Highest parameters are
    Squezze time:, 1cycle
    Hold 5 cycle
    Wel1: 13 cycles
    Weld2: 15 cycles
    So we can see a spot is completed in 0.8 second, still it take time.

  • M.Ozkan
    Reactions Received
    22
    Trophies
    5
    Posts
    538
    • February 12, 2016 at 11:17 AM
    • #8

    Please post robot backup

  • Tushar_Patil
    Trophies
    3
    Posts
    90
    • February 12, 2016 at 12:08 PM
    • #9

    plz check the backup, the servo motor is MU200.

    Files

    6700-501223_Backup_20160204.rar 145.14 kB – 17 Downloads
  • Tushar_Patil
    Trophies
    3
    Posts
    90
    • February 12, 2016 at 12:12 PM
    • #10

    which method is good for tip wear compensation. MeasutrewearL or RecalTcp ?
    In my case i am using RecalTcp with 50 50% wear ratio. But it is not working properly.
    Also for modifying some spot we need to use new electrode (cap tip) or i can do the touch-up on same wear old cap tip?

  • M.Ozkan
    Reactions Received
    22
    Trophies
    5
    Posts
    538
    • February 13, 2016 at 11:52 AM
    • #11

    Robot backup seems normal. Please observe g1_weld_complete signal. When signal coming from weld controller?

  • Tushar_Patil
    Trophies
    3
    Posts
    90
    • February 13, 2016 at 1:50 PM
    • #12

    Issue solved by changing communication parameters

  • neel
    Trophies
    2
    Posts
    92
    • April 17, 2018 at 6:42 PM
    • #13

    Can you please tell me which parameter did you change in communication ?

    And also I'm facing an issue which is..
    Whenever I do tip wear calibration using MeasurewearL the "curr_wear_fix" value is coming always in negative.
    Can anyone support me on this and customer wants only MeasutrewearL instruction to be use.

    :help:

    Edited once, last by Neel (April 17, 2018 at 7:14 PM).

  • neel
    Trophies
    2
    Posts
    92
    • April 18, 2018 at 2:10 PM
    • #14

    Please 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
  • 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