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

Kuka inline forms

  • NiNok
  • March 27, 2019 at 10:15 AM
  • Thread is Resolved
  • NiNok
    Trophies
    3
    Posts
    7
    • March 27, 2019 at 10:15 AM
    • #1

    Hello

    Can someone tell me what would be the equivalent in KRL of a kuka motion form?
    For example:

    ;FOLD PTP HOME Vel= 100 % DEFAULT;%{PE}%MKUKATPBASIS,%CMOVE,%VPTP,%P 1:PTP, 2:HOME, 3:, 5:100, 7:DEFAULT
    $BWDSTART = FALSE
    PDAT_ACT=PDEFAULT
    FDAT_ACT=FHOME
    BAS (#PTP_PARAMS,100 )
    $H_POS=XHOME
    PTP XHOME
    ;ENDFOLD

    How would I program this same motion (taking into acount all the parameters: base, tool, vel, acc...) without using the inline form?

    Btw, I would like to know how you program thees robots, are you using the in line forms or going through the all raw KRL?

    Thank you

  • Online
    Leon
    Reactions Received
    35
    Trophies
    5
    Posts
    472
    • March 27, 2019 at 1:11 PM
    • #2

    First of which control and kss version are you using, this matters as stated in "read first".
    Second find the expert programming manual in the manuals section. this is for a KRC2 but a lot is still relevant for the newer KRC4.

    I never use inline forms, so i cant explain all the commands but if wanted to go to home if would program it like so:

    Code
    $TOOL = TOOL_DATA[1] ;selecting right tool
    $BASE = BASE_DATA[2] ;selecting right base
    
    
    PTP XHOME ;point to point movement to home

    Every problem has a solution, that isn't the problem. The problem is the solution.

  • Online
    panic mode
    Reactions Received
    1,294
    Trophies
    11
    Posts
    13,126
    • March 27, 2019 at 1:36 PM
    • #3

    Don't forget load:

    Code
    $TOOL = TOOL_DATA[1] ;selecting right tool
    $LOAD = LOAD_DATA[1] ;selecting right tool
    $BASE = BASE_DATA[2] ;selecting right base
    PTP XHOME ;point to point movement to home

    but there is much more to it (speed, acceleration, approximation, interpolation mode etc.).
    This topic is covered in Kuka training "Programming2". To get there one must first go through "Progamming 1"

    1) read pinned topic: READ FIRST...

    2) if you have an issue with robot, post question in the correct forum section... do NOT contact me directly

    3) read 1 and 2

  • Online
    Leon
    Reactions Received
    35
    Trophies
    5
    Posts
    472
    • March 27, 2019 at 3:18 PM
    • #4

    Oops i always forget load data. my robots all have the exact same spindle mounted and since the difference between a 6 or 10mm mill is minimal. i never change my load data. :uglyhammer2:

    Every problem has a solution, that isn't the problem. The problem is the solution.

  • Online
    SkyeFire
    Reactions Received
    1,060
    Trophies
    12
    Posts
    9,456
    • March 27, 2019 at 5:03 PM
    • #5

    Briefly: in KRL, any line that begins with a ';' is treated as a comment and ignored by the compiler. However, the user interface treats ;FOLD and ;ENDFOLD as special cases that control how a line is displayed on the pendant, and in certain cases interact with the pendant menu system using inline folds.

    Everything that is between the ;FOLD and ;ENDFOLD lines is a simple KRL command. FDAT_ACT, PDAT_ACT, and LDAT_ACT are global variables that come as part of KRL, and the BAS subroutine uses those variables to set the system variables $TOOL, $BASE, $LOAD, $APO_DIST, etc. If you examine the .DAT file of your module, you will find various E6POS, PDAT, LDAT, FDAT variables that are created every time you create a new point, and are changed whenever you Touch Up a point (E6POS) or change the tool/base/approximation/etc parameters (xDATs).

    That KRL code you quoted basically sets PDAT_ACT, FDAT_ACT, and (for LIN motions) LDAT_ACT to match the variables in your module's DAT file, then BAS() loads them into the $ system variables that actually control the robot's motion.

    The folded code created by the inline forms is "bulky" -- a lot of that code isn't strictly necessary, if you write your own KRL, but in order to enable inline-form programming by people with only basic skills, the inline forms generate all that extra code for every motion command. But once you set $TOOL, $BASE, etc, they retain those settings indefinitely, until another command changes them (or someone does a Program Cancel or something similar, but that's a special case).

    If you were to write your own "raw" KRL, for a series of motions that would all have the same FDAT, PDAT, and LDAT parameters, you could simply set them once, at the top of your program, call BAS() once, then write a series of PTP and LIN commands. On the upside, this saves program memory (not a big issue, usually), but on the downside, you lose the ability to use the Touch Up button to update a point.

  • hermann
    Reactions Received
    410
    Trophies
    9
    Posts
    2,621
    • March 29, 2019 at 8:03 AM
    • #6

    One main problem with non inline motion commands:
    Without the option 'expert tech' it is not possible to "touch up" them :bawling:

  • Online
    panic mode
    Reactions Received
    1,294
    Trophies
    11
    Posts
    13,126
    • March 29, 2019 at 1:45 PM
    • #7

    Experts don’t need ExpertTech to touch up points. Variable monitor is sufficient....

    1) read pinned topic: READ FIRST...

    2) if you have an issue with robot, post question in the correct forum section... do NOT contact me directly

    3) read 1 and 2

  • Koppel
    Reactions Received
    19
    Trophies
    3
    Posts
    132
    • December 29, 2019 at 10:29 AM
    • #8

    I also want to evolve out of the inline forms.

    Do I understand correctly that I can specify the velocity, acceleration of the axis, the tool and the base in the DAT file and by using the command BAS() in the SRC file I load these values to be used... as long as the DAT and SRC filenames match?

    Now if I want some of the position changes to be faster than others I need to change the velocity values in the middle of the program again.

    Do I just add these rows in the middle of my program?

    Code
    FOR I=1 TO 6
    $VEL_AXIS[I] = 100 ;all axis velocities to 100%
    ENDFOR

    And if I want to change the base in the middle of my program I add this row?

    Code
    $BASE=BASE_DATA[2]

    There could be a risk there when moving back to points prior to this BASE changing line as these will be completely offset from their original position. Even home in BASE_DATA[1] is completely different from home in BASE_DATA[2].


    EDIT2: Splines in raw KRL.

    SPLINE … ENDSPLINE defines a CP spline block. A CP spline block may contain SLIN, SCIRC and SPL segments

    PTP_SPLINE … ENDSPLINE defines a PTP spline block. A PTP spline block may contain: SPTP segments.

    I don't really understand what the difference is between them.

    Code
    PTP_SPLINE WITH $VEL={CP 1}
    SPTP P1
    SPTP P2
    SPTP P3
    SPTP P4
    ENDSPLINE

    Edited 6 times, last by Koppel (December 29, 2019 at 6:30 PM).

  • Online
    SkyeFire
    Reactions Received
    1,060
    Trophies
    12
    Posts
    9,456
    • December 30, 2019 at 12:38 AM
    • #9

    In KRL, once the system variables for controlling motion ($APO, $VEL, $TOOL, $BASE, etc) have been set, their value is not changed until another command to change their value is executed. The only exception to this is that many of them can be set to "invalid" under special circumstances, like a Program Cancel. This means that those variables must be set to some valid value before the first motion command in a program.

    But, it would be possible to set those parameters once at the beginning of a program, then run a thousand motion commands without every touching those variables again.

    The downside is that, if someone Block Selects past a line that is setting something critical, like $BASE or $TOOL, the next motion command could behave unpredictably. This is one reason that every inline-form programmed motion contains a full set of commands (using BAS, FDAT_ACT, LDAT_ACT, PDAT_ACT, etc) to fully re-define the motion parameters for every motion.

    Home position should not be affected by $TOOL or $BASE, since it is normally declared as an E6AXIS position, and runs as a set of axis angles, not Cartesian coordinates in space.

  • AndrewWang
    Reactions Received
    6
    Trophies
    3
    Posts
    63
    • December 30, 2019 at 2:53 AM
    • #10
    Quote from Koppel

    I also want to evolve out of the inline forms.

    Do I understand correctly that I can specify the velocity, acceleration of the axis, the tool and the base in the DAT file and by using the command BAS() in the SRC file I load these values to be used... as long as the DAT and SRC filenames match?

    Now if I want some of the position changes to be faster than others I need to change the velocity values in the middle of the program again.

    Do I just add these rows in the middle of my program?

    Code
    FOR I=1 TO 6
    $VEL_AXIS[I] = 100 ;all axis velocities to 100%
    ENDFOR

    And if I want to change the base in the middle of my program I add this row?

    Code
    $BASE=BASE_DATA[2]

    There could be a risk there when moving back to points prior to this BASE changing line as these will be completely offset from their original position. Even home in BASE_DATA[1] is completely different from home in BASE_DATA[2].


    EDIT2: Splines in raw KRL.

    SPLINE … ENDSPLINE defines a CP spline block. A CP spline block may contain SLIN, SCIRC and SPL segments

    PTP_SPLINE … ENDSPLINE defines a PTP spline block. A PTP spline block may contain: SPTP segments.

    I don't really understand what the difference is between them.

    Code
    PTP_SPLINE WITH $VEL={CP 1}
    SPTP P1
    SPTP P2
    SPTP P3
    SPTP P4
    ENDSPLINE
    Display More

    The following code is for old motion,for each motion you can parameterize it differently based on your requirements.

    Code
    DEF Motion_Example( )
    DECL INT I
    ;------------Motion1------------------------------------------------
    BAS(#VEL_PTP,30)                         ;;Set PTP Axis Velocity
    BAS(#ACC_PTP,50)                         ;;Set PTP Axis Acceleration
    PTP{A1 0,A2 -80,A3 80,A4 50,A5 60,A6 90}
    ;-------------------------------------------------------------------
    ;------------Motion2------------------------------------------------
    FOR I=1 TO 6
     $VEL_AXIS[I]=40                         ;;Set PTP Axis Velocity        
     $ACC_AXIS[I]=70                         ;;Set PTP Axis Acceleration
    ENDFOR 
    PTP{A1 0,A2 -90,A3 90,A4 0,A5 0,A6 0}
    ;-------------------------------------------------------------------
    ;------------Motion3------------------------------------------------
    $BASE=BASE_DATA[1]                      ;; Set Base data
    $TOOL=TOOL_DATA[1]                      ;; Set Tool data
    $LOAD=LOAD_DATA[2]                      ;; Set Load Data
    $VEL.CP=0.3                             ;; Set CP motion Velocity
    $VEL.ORI1=100                           ;; Set CP Swivel Velocity
    $VEL.ORI2=100                           ;; Set CP Rotational Velocity
    $ACC.CP=2.0                             ;; Set CP Acceleration
    $ACC.ORI1=200                           ;; Set CP Swivel Acceleration
    $ACC.ORI2=200                           ;; Set CP Rotational Acceleration
    $APO.CDIS=0.5                           ;; Set Approximation Distance
    LIN {X 100 ,Y -100 ,Z 810 ,A -10 ,B -20 ,C 75 } C_DIS
    ;----------------------------------------------------------------------
    ;------------Motion4---------------------------------------------------
    BAS(#BASE,1)                            ;; Set  Base Data
    BAS(#TOOL,1)                            ;; Set Tool  Data
    BAS(#VEL_CP,0.5)                        ;; Set CP Motion Velocity
    BAS(#ACC_CP,80)                         ;; Set CP Motion Acceleration
    LIN {X 200 ,Y 210 ,Z 1010 ,A 10 ,B  10 ,C -75 }
    ;----------------------------------------------------------------------
    ;------------Motion5---------------------------------------------------
    $BASE={X 0,Y 0,Z 0,A 0,B 0,C 0}         ;; Set Base Data
    $TOOL={X 0,Y 0,Z 0,A 0,B 0,C 0}         ;; Set Tool Data
    $LOAD={M -1.0,CM {X 0.0,Y 0.0,Z 0.0,A 0.0,B 0.0,C 0.0},J {X 0.0,Y 0.0,Z 0.0}}
    $VEL={CP 0.3,ORI1 100,ORI2 100}         ;; Set CP Motion Velocity
    $ACC={CP 2.0,ORI1 200,ORI2 200}         ;; Set CP Motion  Acceleration
    $APO={CVEL 50,CPTP 50,CDIS 1,CORI 1}    ;; Set Approximation Data
    $IPO_MODE = #TCP                        ;; Set External TCP
    LIN {X 100 ,Y -100 ,Z 810 ,A -10 ,B -20 ,C 75 } C_DIS
    ;-----------------------------------------------------------------------
    ;------------Motion6----------------------------------------------------
    FDAT_ACT=FDEFAULT
    FDAT_ACT.TOOL_NO=1                    ;; Set Tool Data
    FDAT_ACT.TOOL_NO=1                    ;; Set Base  Data
    FDAT_ACT.IPO_FRAME=#BASE              ;; Set IPO Mode
    BAS(#FRAMES)                          ;; Set FDat data
    BAS(#TOOL,1)                          ;; Set Tool and activate load
    LDAT_ACT=LDEFAULT                      
    LDAT_ACT.VEL=0.5                      ;; Set CP Velocity
    LDAT_ACT.ACC=20                       ;; Set CP Acceleration
    LDAT_ACT.APO_DIST=5                   ;; Set Aproximation Distance
    LDAT_ACT.ORI_TYP=#VAR                 ;; Set Orientation type
    BAS(#CP_DAT)                          ;; Set LDAT  
    LIN {X 200 ,Y 210 ,Z 1010 ,A 10 ,B  10 ,C -75 } C_DIS
    ;-----------------------------------------------------------------------
    ;------------Motion7----------------------------------------------------
    FDAT_ACT=FDEFAULT
    FDAT_ACT.TOOL_NO=1                    ;; Set Tool Data
    FDAT_ACT.TOOL_NO=1                    ;; Set Base Data
    FDAT_ACT.IPO_FRAME=#BASE              ;; Set IPO Mode
    BAS(#FRAMES)                          ;; Set FDAT Data
    BAS(#TOOL,1)                          ;; Set Tool and activate load
    PDAT_ACT=PDEFAULT
    PDAT_ACT.VEL=50                      ;; Set PTP Velocity
    LDAT_ACT.ACC=20                      ;; Set PTP Acceleration
    LDAT_ACT.APO_DIST=5                  ;; Set Aproximation Distance
    BAS(#PTP_DAT)                        ;; Set PDAT Data
    PTP {X 100 ,Y -100 ,Z 810 ,A -10 ,B -20 ,C 75,S 2,T 8 } C_DIS
    ;-------------------------------------------------------------------
    ;------------Motion8------------------------------------------------
    PDAT_ACT={VEL 30,ACC 100,APO_DIST 50}           ;; Set PDAT Data
    FDAT_ACT={TOOL_NO 6,BASE_NO 1,IPO_FRAME #BASE}  ;; Set FDAT Data
    PTP {A1 5,A2 -90,A3 100,A4 5,A5 10,A6 -5,E1 0,E2 0,E3 0,E4 O,E5 0,E6 0}
    ;-------------------------------------------------------------------
    ;------------Motion9------------------------------------------------
    $BASE={X 0,Y 0,Z 0,A 0,B 0,C 0}         ;; Set Base Data
    $TOOL={X 0,Y 0,Z 0,A 0,B 0,C 0}         ;; Set Tool Data
    $LOAD.M=-1.0
    $LOAD.CN={X 0.0,Y 0.0,Z 0.0,A 0.0,B 0.0,C 0.0}
    $LOAD.J={X 0.0,Y 0.0,Z 0.0}
    $VEL={CP 0.3,ORI1 100,ORI2 100}         ;; Set CP Motion Velocity
    $ACC={CP 2.0,ORI1 200,ORI2 200}         ;; Set CP Motion  Acceleration
    $APO={CVEL 50,CPTP 50,CDIS 1,CORI 1}    ;; Set Approximation Data
    $IPO_MODE = #BASE                       ;; Set Robot guided TCP
    $ORI_TYPE = #CONSTANT                   ;; Set CP Orientation Mode
    $CIRC_TYPE = #BASE                      ;; Set CIRC Orientation Mode
    CIRC {X 5,Y 0, Z 9.2},{X 12.3,Y 0,Z -5.3,A 9.2,B -5,C 20}, CA 260 C_ORI
    ;-------------------------------------------------------------------
    ;------------Motion9------------------------------------------------
    PTP_REL {A2 -30}                           ;; Axis Relative Move
    PTP_REL {X 100,Z -200}                     ;; Base Relative PTP Move
    LIN_REL {X 100,Z -200}                     ;; Base Relative LIN Move
    LIN_REL {X -100} #TOOL                     ;; Tool Relative LIN Move
    CIRC_REL {X 100,Y 3.2,Z -20},{Y 50},CA 500 C_VEL    ;; Base Relative CIRC Move
    END
    Display More

    The diference between PTP spline block and CP spline block is like the diference between PTP and CP motion,they are just 2 diferent motion types.

  • Koppel
    Reactions Received
    19
    Trophies
    3
    Posts
    132
    • January 16, 2020 at 9:46 PM
    • #11

    Hi,

    I can create a DAT file with all my points. Make the DAT file public and also make the points GLOBAL

    Code
    DEFDAT MyDatFile PUBLIC
    
    DECL GLOBAL E6POS MyPoint1={X 100, Y 100, Z 100, A 90, B 0, C 180}
    DECL GLOBAL E6POS MyPoint2={X 200, Y 100, Z 100, A 90, B 0, C 180}
    DECL GLOBAL E6POS MyPoint3={X 300, Y 100, Z 100, A 90, B 0, C 180}
    
    ENDDAT

    But when I want to use "MyPoint1" in a new SRC file... like:

    Code
    PTP MyPoint1

    the robot tells me that it has no idea what the variable "MyPoint1" is ... its an undeclared variable or something similar.

    What am I missing here? The points are global and the DAT file is public... Why is the robot not recognizing my points?

  • Online
    panic mode
    Reactions Received
    1,294
    Trophies
    11
    Posts
    13,126
    • January 17, 2020 at 4:30 AM
    • #12

    Robot tells you that? Or work visual?

    1) read pinned topic: READ FIRST...

    2) if you have an issue with robot, post question in the correct forum section... do NOT contact me directly

    3) read 1 and 2

  • spiral
    Reactions Received
    2
    Trophies
    3
    Posts
    146
    • January 17, 2020 at 10:25 AM
    • #13

    Add S,T and E1-E6 to your points.They have form as frames not as E6POS in your case.

  • Online
    SkyeFire
    Reactions Received
    1,060
    Trophies
    12
    Posts
    9,456
    • January 17, 2020 at 3:03 PM
    • #14
    Quote from spiral

    Add S,T and E1-E6 to your points.They have form as frames not as E6POS in your case.

    That's strongly advised, but not actually required -- KRL will accept them as-is. The issue would be that they lack the S&T disambiguation. The E values can be left out entirely unless the robot actually has external axes. But leaving out those values is not what's causing Koppel's current issue.

    Koppel: are you trying to use those points in an inline form, or a "raw" KRL command? Inline forms automatically add an "X" prefix to the name of any point. But for raw KRL, what you have should work. Are there any linking errors?

  • Online
    panic mode
    Reactions Received
    1,294
    Trophies
    11
    Posts
    13,126
    • January 17, 2020 at 3:11 PM
    • #15
    Quote from AndrewWang

    The following code is for old motion,for each motion you can parameterize it differently based on your requirements.

    Code
    FDAT_ACT.TOOL_NO=1                    ;; Set Tool Data
    FDAT_ACT.TOOL_NO=1                    ;; Set Base Data

    nice example, should include units since for example CP acceleration is not same using BAS and $ACC

    also there seem to be some typos mixing tool and base

    1) read pinned topic: READ FIRST...

    2) if you have an issue with robot, post question in the correct forum section... do NOT contact me directly

    3) read 1 and 2

  • Koppel
    Reactions Received
    19
    Trophies
    3
    Posts
    132
    • January 26, 2020 at 6:23 PM
    • #16
    Quote from panic mode

    Robot tells you that? Or work visual?

    It must have been WorkVisual because my global point delcarations work fine on the physical robot.
    Does WorkVisual not check if the points are declared in some other DAT file !?

  • Online
    SkyeFire
    Reactions Received
    1,060
    Trophies
    12
    Posts
    9,456
    • January 27, 2020 at 2:44 PM
    • #17

    WorkVisual does cross-file variable checking, but I've noticed it's not 100% reliable. It's been getting better with progressing WV versions, but still has some potholes.

  • Online
    Mate_271
    Trophies
    2
    Posts
    121
    • October 8, 2021 at 7:33 AM
    • #18
    Quote from panic mode

    Don't forget load:

    Code
    $TOOL = TOOL_DATA[1] ;selecting right tool
    $LOAD = LOAD_DATA[1] ;selecting right tool
    $BASE = BASE_DATA[2] ;selecting right base
    PTP XHOME ;point to point movement to home

    Dear panic mode,

    I Made a movements folder with the following parameters and i got error message.

    Moreover, i determined several other lines... example.:$VEL.CP,ACC.ORI1,APO.CDIS... and so on.

    When the robot arrived to $ORI_TYPE=#VAR i got the same error message.(I could reach this, cause i commented out the $LOAD_DATA line. I know i should not, i just wanted to test it)

    Can you tell meg please why i get these messages?

  • Fubini
    Reactions Received
    282
    Trophies
    9
    Posts
    1,903
    • October 8, 2021 at 9:18 AM
    • #19

    And you set the data when and where? More of your context please. Submit maybe? Not everything can be altered from inside the submit.

    The message tells you under your current situation/system state the variable is write protected.

    Fubini

  • Online
    Mate_271
    Trophies
    2
    Posts
    121
    • October 8, 2021 at 9:37 AM
    • #20

    Thank you for your quick reply.

    AS i think right if i choose $TOOL=TOOL_DATA[1], i should choose $LOAD=LOAD_DATA[1] and this is my load data[1] probably:

    I just write the valuse into the system from CAD and this will be LOAD_DATA[1] if i am right.

    Thanks for your help in advance!

    Mate

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