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
Everywhere
  • Everywhere
  • Articles
  • Pages
  • Forum
  • Blog Articles
  • Products
  • More Options
  1. Robotforum - Support and discussion community for industrial robots and cobots
  2. Members
  3. ParametricGuy

Posts by ParametricGuy

  • Fanuc robot weld shedules , procedures and channel number query

    • ParametricGuy
    • June 11, 2025 at 5:53 PM

    Hello Dane534 , I’m no expert but I worked with welding before, my guess is:

    • 6 = the weld schedule number—basically loads a preset recipe on the pendant
    • 6.0 = a wire-feed multiplier, so it scales that base feed speed
    • 420.0 cm/min = torch travel speed
    • 25.00 = likely a voltage/current trim adjustment you apply over the schedule
    • –4.000 = probably a stick‑out or arc offset tweak

    Their relationship is pretty complex and varies by the system you have, say Fronius or others.

  • Help Needed: Issue with CALL SR[3] in Main Program

    • ParametricGuy
    • June 11, 2025 at 1:34 PM
    Quote from AnandTUD

    Could it be because of Capital letters? Please try writing TEST04_1 in SR[3] and try again.

    Shockingly enough, this seems to be the solution.. I'm confused though.

    The main code is Call Test04_1 which in roboguide shows as CALL TEST04_1 (all capital letters) and correctly calls the program file named "Test04_1.ls".

    Nevertheless if i Call SR[3] and SR[3] = Test04_1 it won't work unless I replace SR[3] with SR[3] = TEST04_1

    I need to dive deeper on how Fanuc handles case sensitivity, but it seems that String Registers are case sensitive while .ls programs names and calls inside of a program are not.

    Files

    image.png 9.51 kB – 19 Downloads
  • Help Needed: Issue with CALL SR[3] in Main Program

    • ParametricGuy
    • June 11, 2025 at 12:58 PM

    I checked several times for whitespaces in SR[3] as it happened to me before. I can't find anything wrong with the string though.

    The actual file name is now "Test04_1", here's a screenshot of SR window in roboguide:

    And here's the two lines of code in the main program (the first works, the second doesn't)

    Images

    • image.png
      • 16.28 kB
      • 511 × 60
      • 2
  • Help Needed: Issue with CALL SR[3] in Main Program

    • ParametricGuy
    • June 11, 2025 at 12:22 PM
    Quote from DS186

    I don't know the program structure of your programs, e.g. if you are using instructions in both programs that require a motion group

    The main program doesn't have any movement, just some calls and register operations.

    Quote from DS186

    If possible, deactivate the motion group in your calling program (main program) by setting the DEFAULT_GROUP from 1 to * and then try to run the program again.

    Tried but nothing changed unfortunately.

    :exclamation_mark:This morning I tried inserting a CALL TEST_1 right before CALL SR[3]. The main program successfully call TEST_1 and when finally jumping to the next line (CALL SR[3]) I get the same error as before.

    This doesn't really make sense, does it?

  • Help Needed: Issue with CALL SR[3] in Main Program

    • ParametricGuy
    • June 11, 2025 at 11:32 AM

    Isn't motion group related to external axis? I'm doing some research but I can't find anything useful on program calls issues.

    I can share the ATTR of the two pieces of code, are you talking about the "DEFAULT_GROUP" line?

    The main file starts as follow:

    Code
    !main program;
    
    /ATTR
    OWNER		= MNEDITOR;
    COMMENT		= "";
    PROG_SIZE	= 434;
    CREATE		= DATE 22-02-07  TIME 17:11:58;
    MODIFIED	= DATE 22-02-08  TIME 10:17:08;
    FILE_NAME	= ;
    VERSION		= 0;
    LINE_COUNT	= 19;
    MEMORY_SIZE	= 878;
    PROTECT		= READ_WRITE;
    TCD:  STACK_SIZE	= 0,
          TASK_PRIORITY	= 50,
          TIME_SLICE	= 0,
          BUSY_LAMP_OFF	= 0,
          ABORT_REQUEST	= 0,
          PAUSE_REQUEST	= 0;
    DEFAULT_GROUP	= 1,*,*,*,*;
    CONTROL_CODE	= 00000000 00000000;
    LOCAL_REGISTERS	= 0,0,0;
    Display More

    One of the called files (TEST_1):

    Code
    !TEST_1;
    
    /ATTR
    OWNER = SHIFT;
    PROG_SIZE = 29445;
    CREATE = DATE 00-00-00  TIME 00:00:00;
    MODIFIED = DATE 00-00-00  TIME 00:00:00;
    VERSION  = 0;
    LINE_COUNT = 453;
    MEMORY_SIZE = 95400;
    PROTECT  = READ_WRITE;
    DEFAULT_GROUP	= 1,*,*,*,*;
    CONTROL_CODE = 00000000 00000000;
    Display More
  • Help Needed: Issue with CALL SR[3] in Main Program

    • ParametricGuy
    • June 10, 2025 at 6:34 PM

    Hello everyone,

    I'm currently working on a large project that involves calling several programs from a main program. In this main program, I use CALL SR[3], where SR[3] is a string "TEST_1".

    The TEST_1 program works perfectly when run independently. However, when I try to call it from the main program, it fails. I've triple-checked the SR[3] reference, but Roboguide isn't providing any clues about the issue. The log simply shows a "call program failed" message, and the execution stops there.

    Has anyone encountered a similar problem or have any suggestions on what might be causing this issue?

    Thanks in advance for your help!

    Quote

    Solution Found:

    After thorough investigation and multiple attempts to resolve the issue, it has been determined that the problem was related to case sensitivity with String Registers. Even though the name of the program to call and the string register matched, the string register needed to be in all caps. It appears that every program is automatically "renamed" to an all-caps version of itself. Therefore, ensuring that the string register is in all caps resolves the issue.

    Solved - the only issue was case sensitivity with String Registers.

  • custom sub module ignoring "IF"

    • ParametricGuy
    • August 22, 2023 at 6:40 PM

    I figured out the issue, basically $STOPMESS is true whenever the Motion is not enabled (so also when you are in T1 and you are not pressing the deadman).

    I repeated the tests and that's the issue, as long as I start a program in AUT, or I press deadman in T1, $STOPMESS turn False as intended.

    I solved the issue by including a IF $PRO_ACT == TRUE THEN line of code before the SWITCH, this should prevent the switch to call programs when i'm not actually running any program.

    Quote from SkyeFire

    Also, I hope you're changing CLTYPE as soon as SOMEPROGRAM runs once, otherwise the SPS will keep running it, and posting the Notify message, as fast as it can loop. Doing this kind of thing in the SPS needs some sort of one-shot to avoid hammering the message window with thousands of messages in under a minute.


    Actually I'm not because I want the subprograms to be called continuously until the error gets solved, otherwise the user might bypass the system by acting on what the subprograms are acting upon.

    The msgnotify keeps getting posted, despite not being saved in any log this can actually be a minor issue that's true, the question here is how to run the msgnotify only once (but must get posted again after the issue is solved and the program resumed) while continuously running the subrpograms. :thinking_face:

  • custom sub module ignoring "IF"

    • ParametricGuy
    • August 22, 2023 at 12:17 PM

    Hello everyone,
    I really can't figure out a weird behaviour I'm experiencing with a custom .sub file.§

    I created a custom .sub file to perform some activities in background, basically how to react to errors and some other events (I/O).

    Here's a piece of code to look at:

    Code
    DEF   CUSTOM( )
        
        ;FOLD DECLARATIONS
        ENUM TYPE ASD1, ASD2, ASD3
        DECL TYPE CLTYPE
        ;ENDFOLD (DECLARATIONS)
        
        LOOP
            SWITCH CLTYPE
                CASE ASD1
                    IF $STOPMESS==TRUE THEN ;<----- ISSUE
                        msgnotify ("error detected")
                        SOMEPROGRAM()
                    ENDIF
                    IF ($IN[5]==TRUE) OR ($IN[23] == FALSE) THEN
                        OTHERPROGRAM()
                    ENDIF
    
                CASE [...]
                    [...]
    Display More

    The issue is in LINE 12, where despite having an IF $STOPMESS==TRUE THEN, the msgnotify and the SOMEPROGRAM lines are executed anyway each cycle.
    It seems that for some reasons $STOPMESS is always detected as TRUE.

    I'm not adding more info just because I believe this is purely code-related, as the robot was not in error state during the test I have done.

    Anyone has any insight on why it is ignoring the IF?

Advertising from our partners

IRBCAM
Robotics Channel
Robotics Training
Advertise in robotics
Advertise in Robotics
Advertise in Robotics
  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