18.06.2013 Views

LIBRARY ı6ıul 0) - Cranfield University

LIBRARY ı6ıul 0) - Cranfield University

LIBRARY ı6ıul 0) - Cranfield University

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Although only linear joints were implemented in this work, it should be noted<br />

that non-linear joints could also be included for off-line programming by sub-dividing<br />

the non-linear curves obtained from the intersection between two adjacent surfaces<br />

into small linear segments and treating these as a series of successive linear joints.<br />

This could increase the application scope of the program to deal with, for example,<br />

fillet welds in pipe sections. It should also be noted that the currently available robots<br />

are limited to linear and circular interpolation. That is, they can only perform ruled<br />

paths either passing through specified points in the form of a line between two teach-<br />

points or an arc passing through a third teach-point located between the teach-points<br />

which define the start and end of the arc. Hence, a non-linear non-circular robot path<br />

can only be defined as a series of successive linear paths with the torch orientation<br />

changing linearly between the teach-points.<br />

The benefit of integrating the welding procedure generation and the<br />

geometrical data extraction for off-line programming into the CAD software is that<br />

the resulting welding data2 and the weld positional data3 can be stored in the same<br />

CAD drawing file in the form of data associated with the line segment which defined<br />

the weld joint. Therefore, if a different welding cell and robot is used, the only<br />

modification needed for generating the new robot teach-points would be the definition<br />

of the CAD-to-Robot transformation matrix. It should be noted that the definition of<br />

this transformation matrix depends on a set of points which are located using the<br />

robot. The orientation of the torch relative to the joint line was set by default as<br />

being perpendicular to the joint line at the point being defined (start or end point) and<br />

contained in the joint bisection plane. For example, for a 90 deg included angle flat<br />

position fillet joint, the default orientation would be parallel to the gravitational<br />

vector. This orientation could be changed by the user if required.<br />

Also, an offset for the position of the weld start and end points along the joint<br />

line was introduced to ensure that there would always be base material to receive the<br />

weld metal. No transversal tolerance was allowed, however this could be easily<br />

implemented. This could be necessary for welding steels with different heat sink<br />

characteristics in each side of the joint.<br />

The rules used to generate the orientation necessary for the welding torch to<br />

achieve different joint approach and withdrawing directions were devised from prior<br />

on-line programming experience of a welding robot with a specific torch<br />

configuration. Therefore, for a different robot/welding torch combination, a<br />

modification in the angles of the planes defining the different orientation regions<br />

would be necessary (see section 3.3.2.2).<br />

The teach-points defining the welding torch approach and withdrawing paths<br />

relative to the joint were generated based on the assumption that the component, once<br />

fixed in the jigging system, would not be moved until the completion of the welding<br />

operation. This implies that the component clearance box (see section 3.3.2.2) would<br />

also be fixed and, therefore, the approach and withdrawing points and vectors.<br />

However, different rules could be defined in situations where the component<br />

2 Required welding quality and chosen welding procedure<br />

3 Relative to the CAD coordinates frame.<br />

190

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!