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

Questions About the Path Recorder

  • gmumaugh
  • September 7, 2022 at 4:47 PM
  • Thread is Resolved
  • gmumaugh
    Reactions Received
    13
    Trophies
    2
    Posts
    65
    • September 7, 2022 at 4:47 PM
    • #1

    RW6.12, IRC5

    My company is rewriting our standard Rapid templates for ABB robots, and one of the biggest things I want to improve is recovery and auto-homing. Right now, we use MoveJSync/MoveLSync to count steps as the robot moves through each position. The step number and current program are stored in persistent variables because with IFWC homing always requires a start @ main command and we need some way to remember where the robot was. This is a huge pain because if a corner path failure occurs, the sync instructions can be missed. The old template even used MoveXSync with fine points, which was another issue. If the step is not correct, the robot will not recover correctly.

    I would like to use the path recorder to make recovery easy. I've already set up some tests with it and have had success, but I have some questions I haven't been able to find answers to or test:

    1.) Since recovery means the program pointer gets reset, does this also destroy any recorded paths? If so, this whole idea is mute unless I can do something in the UNDO handler.

    2.) Can PathRecMoveBwd be used even if the robot deviates from the programmed path, say for example with a SearchL \Stop instruction? I think that as long as a PathRecStop \Clear hasn't been executed then it should work and the recorded path will be a little different than the programmed path, but the wording in the documentation is causing some doubts.

    3.) Can multiple PathRecMoveBwd's be executed in a row? The idea is that if the robot does deviate from the programmed path, I would first like to move backwards to the closest point along the path, then move backwards all the way back. I have multiple path recorder ID's set up, and IFWC comes with a handy little CheckLocation function, so the process would be to check which location I am closest to, see if a valid backwards path exists to that ID, execute a PathRecMoveBwd to that ID, see if a valid backwards path exists to the first ID, then execute another PathRecMoveBwd to that ID at the start of the path. Nothing in the manual says that this isn't possible, but there also aren't any examples where they do this.

    Here's an example of what I'm trying to do:

    Code
    IF (bHoming = TRUE) THEN
        IF (CheckLocation(20,p50,tGripper) = TRUE) THEN
            IF (PathRecValidBwd(\ID:=pathInStep4) = TRUE) THEN
                StorePath;
                PathRecMoveBwd \ID:=pathInStep4;
                IF (PathRecValidBwd(\ID:=pathInStep1) = TRUE) THEN
                    PathRecMoveBwd \ID:=pathInStep1;
                ENDIF
                PathRecStop \Clear;
            ENDIF
        ENDIF
    ENDIF
    
    MoveJ p10,v1000,z200,tGripper;
    PathRecStart pathInStep1;
    MoveL p20,v800,z30,tGripper;
    PathRecStart pathInStep2;
    MoveL p30 v200,z20,tGripper;
    PathRecStart pathInStep3;
    MoveL p40,v200,z20,tGripper;
    PathRecStart pathInStep4;
    SearchL \Stop,di2,sp,p50,v50,tGripper;
    Display More
  • Lemster68
    Reactions Received
    301
    Trophies
    9
    Posts
    2,493
    Blog Articles
    7
    • September 7, 2022 at 5:00 PM
    • #2

    Sorry, but I have bad news for you. I experimented years ago when IFWC was newer. I had the same endeavor, pretty much, as you do. So, the bad news is that the PPtoMain erases completely the recorded paths. It would work great if they had instead chose to use an input to initiate recovery, but Nooo, they use PPtoMain system input. You would think that, of all the programmers out there, that ABB would be doing things the best. I threw out that opinion years ago. Tell me please, if you would do a simple test for me, can you still block the output for IOBlockedinAuto? That would help to demonstrate my point.

  • gmumaugh
    Reactions Received
    13
    Trophies
    2
    Posts
    65
    • September 7, 2022 at 7:11 PM
    • #3

    That was my biggest fear. The more I work with IFWC, the more I begrudgingly understand what its purpose is though. Ford didn't want every single integrator to have their own recovery strategy, PLC handshakes, etc.. I was really hoping the path recorder would be a foolproof way to recover, but I'll keep brainstorming.

    Unfortunately I don't have access to an RC right now, I created a quick and dirty VC but I don't see anything about IOBlockedinAuto.

  • Lemster68
    Reactions Received
    301
    Trophies
    9
    Posts
    2,493
    Blog Articles
    7
    • September 7, 2022 at 7:15 PM
    • #4

    In my trials it worked really well if I got to it before there was a PPtoMain issued.

    You said that you were using MoveLSync, why not TriggL?

  • gmumaugh
    Reactions Received
    13
    Trophies
    2
    Posts
    65
    • September 7, 2022 at 8:38 PM
    • #5

    The program standard used MoveLSync well before I was hired, I couldn't tell you why they were being used over TriggL. Really MoveLSync is just a condensed version of using TriggInt and TriggL though so ultimately using MoveLSync accomplishes the same thing, which is pretty much just incrementing a persistent variable.

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

Tags

  • abb
  • RAPID
  • irc5
  • Path Recorder

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