Posts by fmiroslav

  • Edit Field in AWE1WP01 file from KAREL + TPP

    Third parameter was important, this code work for me

    Code
    CNV_INT_STR(arg2,1,0,temp_a2)
temp_a2 = SUB_STR(temp_a2,2,1)


    Not a piece of artwork but...

    TPP program

    Code
    CALL SET_FA_WPP(6,3,1,22,181,100,30,23,181,101,31,24,182,102,32,2,50)

    Description of parameters

  • Edit Field in AWE1WP01 file from KAREL + TPP

    Quote from dha

    For reading welding parameters from arguments you use:

    Code
    GET_TPE_PRM(arg_num, data_type, int_value, real_value, str_value, STATUS)

    Something like this, it's working but there is some another problem :frowning_face:

    I would like to add (arg1) or insert (arg2) some value to string.

    For that purpose I want to convert Integer value to string (temp).

    Code
    CNV_INT_STR(arg1,1,1,temp)
    Code
    CNV_INT_STR(arg2,1,1,temp)

    and then to add and insert to string

    Code
    fname = 'AWE1WP0' + temp
    Code
    sch_num = 'SCH[' + temp + ']'
sch_num_v = sch_num + '.$CMD_VOLTS'

    Trouble is temp is empty!


  • Fanuc CRX

    Quote from adis

    do you have some explanation of how to work with the drop and drag?

    External Content youtu.be
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

    Pretty easy. Program created in Drag & Drop mode is not visually vertical compatible with TP program and vice versa. If you edit/change some commands in TP they became TEXT CODE in D&D mode.

    Weld C command from D&D haven't available speed parameter (you can touch mid and end point of circle), if you edit program on TP and change WELDSPEED to desired value (5 mm/sec for example) and again open in D&D mode that command become TEXT CODE and you can't retouch mid and end point of circle.

  • CALL SETWP() - passing welding parameters

    Quote from dha

    This is probably KAREL program that someone made it.

    Go to DATA > Weld Procedures and observe which parameters change ...

    Exactly. In roboguide, I saw SETWP among the variables, so I started thinking in the wrong direction. I was later suggested that it could be the Karel program. And unfortunately with a bug.

    Since the voltage is defined in the range 5-55 V, speed of 0.5-25 m / min, ... 17 parameters are forwarded, of which the first three are OK,

    CALL SETWP(6,1,4,5,.5,0,20,20,.5,0,20,5,.5,0,20,.1,20)

    1. parameter - 6 - Weld Procedure

    2. parameter - 1 - Schedule

    3. parameter - 4 - Heat wave mode (1 - None, 2 - Step with weaving, 3 Ramp with weaving, 4 - Pulse (no weaving))

    the other 14 can be forwarded only if the value is in the range of 0 -0.99, values equal to 1 and greater in the desired Schedule will set the value to 0.00. Unfortunately, the developer is not in the mood to share buggy code.

    That 14 parameters depending on the 3rd parameter will change values in Schedules.

    Thank you for your interest. If I draw something useful on this issue, I will share it with you. Greeting.

  • FANUC ROBOT RUN circular

    It's much better to do circle in 3 segment by 120 deg approx. if you make more than 180 deg error will be happen.

    first segment

    P[1] start point

    P[2] mid point

    p[3] end point

    second segment

    P[3] start point

    P[4] mid point

    P[5] end point

    third segment

    P[5] start point

    P[6] mid point

    P[1] end point

  • Search [X], [-X], [Y], [-Y], [Z], [-Z], Simply task a lot of Obstacles

    Program in action, Mastered position, offset and rotated position, program

    will execute movement by corner of cube in both case, second time movement is

    offset in X and Y axis and rotated by Z axis.

    External Content youtu.be
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

  • Search [X], [-X], [Y], [-Y], [Z], [-Z], Simply task a lot of Obstacles

    After RFM and FRFM Method, try, change, try, change, try... , and finally solving,

    Here is a full code, it is different from code in F Manuals, have extra lines :smiling_face: and extra reactions :winking_face_with_tongue:.

    At first You need to Mastering Part, for that You turn ON Master Flag for selected

    Touch Schedule (in my case #4), at screenshot you can see parameters.

    When You Mastering Part, remove Remark from line 14 and 23, when run program back Remark.

    At line 15 and 24 get Error THSR-025 Nested search start, step up for one line (to line 14 and 23)

    press RESET to remove error message, press SHIFT + FWD keep SHIFT pressed.

    Program will be executed search and retract.

    At line 29 Error THSR-013 Illegal number of search, Just ignore because You CAN, RESET.

    Look up for PR[10] values, You will see something like

    X -.153 mm W .000 deg

    Y .514 mm P -.000 deg

    Z .000 mm R -0.038 deg

    Then teach positions.

    When You finished Mastering Part, in DATA Touch Schedule for Master Flag set OFF.

    RUN code, move part or turn around Z (R value) and RUN code again, look up for PR[10] values again

    You will see something like

    when you move

    X 10.555 mm W .000 deg

    Y 2.650 mm P .000 deg

    Z .000 mm R 0.005 deg

    move and rotate

    X 8.234 mm W .000 deg

    Y 1.876 mm P .000 deg

    Z .000 mm R 5.354 deg

  • Search [X], [-X], [Y], [-Y], [Z], [-Z], Simply task a lot of Obstacles

    Quote from GallusRoboticus

    Yes, I believe Search End will turn off the Master flag automatically. You can also turn it off manually in the Touch Schedule in the same way that you turned it on.

    When you run a search with the Master flag off, it will store the offset in the PR you specify in the Search Start command, which in your case would be PR[1].

    DATA / Touch Schedule

    Master Flag must be manually turned ON and OFF

  • Search [X], [-X], [Y], [-Y], [Z], [-Z], Simply task a lot of Obstacles

    Master Flag

    Default=OFF

    This item enables the search routine to be used as a mastering routine for those touch

    sensing programs that generate positional offset information. If set to ON, when the

    search routine is executed, the touched positions are recorded on TP program internally

    as the reference positions to be used by future searches. This flag must be set to OFF

    after the master search is completed in order to generate the information of position offset

    on the objects to be searched. When the search is performed with Master Flag ON, the

    information of position offset in the position register is set to all zero values.

    The Master Flag condition has no effect on simple search pattern.

    Quote

    If set to ON, when the search routine is executed, the touched positions are recorded on TP program internally as the reference positions to be used by future searches.

    Will be recorded to Position Record PR defined in DATA Touch Sched.

    Quote

    This flag must be set to OFF after the master search is completed in order to generate the information of position offset on the objects to be searched.

    How from TP set this flag OFF?

    Does Search End do this, setting Master Flag OFF?

    Where is placed (generated) offset position? In PR register (defined in DATA Touch Sched) will be placed information of touched position in absolute coordinate.

    Quote

    When the search is performed with Master Flag ON, the

    information of position offset in the position register is set to all zero values.

    The Master Flag condition has no effect on simple search pattern.

    Search Start [1] PR[1]  Will reset X, Y, Z, W, P, and R values to 0,000.

  • Search [X], [-X], [Y], [-Y], [Z], [-Z], Simply task a lot of Obstacles

    Quote from GallusRoboticus

    The first time you run a program with touch sensing you will need to master the part by turning on the master flag in the touch sense schedule you are trying to use. It should automatically turn off after you execute the program the first time.

    Thanks GallusRoboticus :thumbs_up::beerchug:

    In DATA Touch Sched for Master flag must be ON then program will work.

    What doesn't work

    Search Start [1] PR[1]

    doesn't write to Position Register PR[1], only Contact record PR from DATA Touch Sched

    is updated with contact position, in my case PR[32].

    Why is Position Record from Search Start command ignored?


  • Search [X], [-X], [Y], [-Y], [Z], [-Z], Simply task a lot of Obstacles

    DO[66] - Touch Sensing at Welding machine, ON activate this function

    DI[73] - Arc detect from Welding machine, ON - wire is in contact with part

    3 line of Code, 4 THSR errors

    After line 8,

    Error THSR-025 Nested Search Start

    R.: Add a search_end instruction in appropriate place or delete extra search start.

    ???

    Reset

    At line 10,

    Error THSR-006 Search Without Search Start

    R.: Add Search start instruction.

    Reset

    I execute again program from line 7

    Line 10,

    Error THSR-022 Part is not mastered

    R.: Mastering the part first.

    Only place where you can find Mastering the part first is list of errors!?

    Mastering the Part? Where we can find something about it?

    If I slightly move part by -X I get Arc detect DI[73] ON

    When robot reach position P[3]

    error appear THSR-023 No Search Start

    R.: Add Search Start before Search.

    Very often in manuals missing precondition for Tasks, maybe they are somewhere taxably noted,

    but we need manual where all steps is described in real World.

    Any Idea?

    Thanks!


Advertising from our partners