Difference between revisions of "Program Examples: WorkSpace areas"
(Created page with "=Introduction= This feature limits robot movements inside defined WorkSpaces areas and at specific paths between them. Each WorkSpaces is modeled by users as a rectangular pri...") |
|||
| Line 2: | Line 2: | ||
This feature limits robot movements inside defined WorkSpaces areas and at specific paths between them. Each WorkSpaces is modeled by users as a rectangular prism in 3D space with entry and exit points, which defined in '''*.XML''' file. <br> | This feature limits robot movements inside defined WorkSpaces areas and at specific paths between them. Each WorkSpaces is modeled by users as a rectangular prism in 3D space with entry and exit points, which defined in '''*.XML''' file. <br> | ||
Robot is considered to be '''inside''' WorkSpaces if its TCP (Tool Center Point) is within the prism and '''outside''' WorkSpaces if its TCP is outside the prism. <br> | Robot is considered to be '''inside''' WorkSpaces if its TCP (Tool Center Point) is within the prism and '''outside''' WorkSpaces if its TCP is outside the prism. <br> | ||
| − | In case user tries to move the robot outside WorkSpaces using unauthorized path an error will raise and motion | + | In case user tries to move the robot outside WorkSpaces using unauthorized path an error will raise and motion won't be started. <br> |
{{Note | Robot segments are not considered}} | {{Note | Robot segments are not considered}} | ||
| Line 18: | Line 18: | ||
* H = O:#{0,0,WSCPH,0,0,0} | * H = O:#{0,0,WSCPH,0,0,0} | ||
When '''WSPCL''' = WorkSpace length, '''WSPCW''' = WorkSpace width, '''WSPCH''' = WorkSpace height. | When '''WSPCL''' = WorkSpace length, '''WSPCW''' = WorkSpace width, '''WSPCH''' = WorkSpace height. | ||
| + | To sets a proper WorkSpace one need to follow these rules: | ||
| + | # WorkSpaces are grouped in WorkSpace-sets. There will be maximum 16 WorkSpace defined in one WorkSpace-set when each WorkSpace-set belongs to only one robot. | ||
| + | # WorkSpace will be indexed by unique numbers 1, 2, 3, ... | ||
| + | # Only '''active''' WorkSpace is considered. | ||
| + | # WorkSpace areas won't be able to edit (change) while robot is enabled (powered-on). | ||
| + | # WorkSpace can be activated only when the robot is disabled (powered-off). | ||
| + | # WorkSpace areas won't be active during conveyer tracking. | ||
| + | # In the first phase, if there are active WorkSpace lined to a robot joint-interpolated motions (MOVE) will be not allowed! | ||
| + | # Each WorkSpace area will have a set of entry & exit points: (En1,En2, …) and (Ex1,Ex2, …) defining exit and entry paths from one workspace to another. | ||
| + | # Entry and exit points will be '''defined only''' by #{X,Y,Z} relative to the origin (O) of the related working space. | ||
| + | # Entry and exit points '''must lie on the surface''' of the WorkSpace (not inside the WorkSpace). | ||
| + | # Entry and exit points will be defined with a tolerance radius R meaning that if the robot TCP is at distance less then R from the given point it will be considered at this point. The tolerance will be described by half-sphere of radius R – meaning only the half that is inside given WorkSpace is valid. | ||
| + | # There will be only one exit and one entry path from one given pair of WorkSpaces | ||
| + | # User can move the robot from one WorkSpace area to another only if: | ||
| + | ## Movement is straight line movement (MOVES, MOVESKD), other interpolation types like: CIRCLE, MOVE, JOG are not allowed. | ||
| + | ## Movement starts from one of the exit points of the WorkSpace area (Exi) to the entry-point (Enj) of another WorkSpace area. | ||
| + | ## No other movement outside WorkSpace area are allowed. | ||
Revision as of 08:37, 3 May 2018
Introduction
This feature limits robot movements inside defined WorkSpaces areas and at specific paths between them. Each WorkSpaces is modeled by users as a rectangular prism in 3D space with entry and exit points, which defined in *.XML file.
Robot is considered to be inside WorkSpaces if its TCP (Tool Center Point) is within the prism and outside WorkSpaces if its TCP is outside the prism.
In case user tries to move the robot outside WorkSpaces using unauthorized path an error will raise and motion won't be started.
| NOTE | |
| Robot segments are not considered |
WorkSpace Properties
WorkSpaces are cuboids defined by its four vertex points:
- Origin (O)
- Width (W)
- Length (L)
- Height (H)
The cuboid can have any orientation in space. The coordinates of the cuboid are given in WorkPiece coordinates of the robot TCP (including tool).
Cuboid parameter defines relative to WorkSpace origin:
- O = #{X,Y,Z,Yaw,Pitch,Roll} - location
- L = O:#{0,WSCPL,0,0,0,0}
- W = O:#{WSCPW,0,0,0,0,0}
- H = O:#{0,0,WSCPH,0,0,0}
When WSPCL = WorkSpace length, WSPCW = WorkSpace width, WSPCH = WorkSpace height. To sets a proper WorkSpace one need to follow these rules:
- WorkSpaces are grouped in WorkSpace-sets. There will be maximum 16 WorkSpace defined in one WorkSpace-set when each WorkSpace-set belongs to only one robot.
- WorkSpace will be indexed by unique numbers 1, 2, 3, ...
- Only active WorkSpace is considered.
- WorkSpace areas won't be able to edit (change) while robot is enabled (powered-on).
- WorkSpace can be activated only when the robot is disabled (powered-off).
- WorkSpace areas won't be active during conveyer tracking.
- In the first phase, if there are active WorkSpace lined to a robot joint-interpolated motions (MOVE) will be not allowed!
- Each WorkSpace area will have a set of entry & exit points: (En1,En2, …) and (Ex1,Ex2, …) defining exit and entry paths from one workspace to another.
- Entry and exit points will be defined only by #{X,Y,Z} relative to the origin (O) of the related working space.
- Entry and exit points must lie on the surface of the WorkSpace (not inside the WorkSpace).
- Entry and exit points will be defined with a tolerance radius R meaning that if the robot TCP is at distance less then R from the given point it will be considered at this point. The tolerance will be described by half-sphere of radius R – meaning only the half that is inside given WorkSpace is valid.
- There will be only one exit and one entry path from one given pair of WorkSpaces
- User can move the robot from one WorkSpace area to another only if:
- Movement is straight line movement (MOVES, MOVESKD), other interpolation types like: CIRCLE, MOVE, JOG are not allowed.
- Movement starts from one of the exit points of the WorkSpace area (Exi) to the entry-point (Enj) of another WorkSpace area.
- No other movement outside WorkSpace area are allowed.