In this article I will talk about 5 axes measurement. Until recently most CMMs measured using a combination of their X, Y & Z axes. This meant that the probe head remained static during the touch process. Although the head provided movement in order to orient itself for access, these moves were executed between those measurements and in most cases the head needed to lock into position prior to a measurement taking place. The CMM structure therefore has, up until now, been the limiting factor in controlling the speed at which measurements can be taken. 5 axes measurement adds the heads indexing capabilities to the CMM movement and in some cases replaces the CMM movement completely during the measurement process. Even if it is not possible to completely remove the CMM movement, 5 axes measurement reduces it considerably. Heads that provide 5 axes measurement, like Renishaw’s REVO and PH20 devices, are integrated into the DMIS language to allow them to move independently or in concert with the CMM during measurement and move sequences. Apart from the obvious speed and stability advantages of using the head as the primary control during the touch process there is also the added advantage of dynamic probe calibration. The heads come with built in calibration routines that effectively map all possible positions negating the need for calibration of individual index locations. This allows the head to turn to any position in its range without returning to the calibration artifact. DMIS has accommodated this new area of measurement by modifying some of its statements to include head orientation.

The GOTO statement:




DMIS GOTO statements were previously used to instruct the CMM to move to a Cartesian X, Y, Z or polar R, A, H position which moved the CMM only. The additional parameters give programmers the ability to not only move the machine but also the head axes simultaneously. The software will usually take care of making sure that all 5 axes arrive at the target point simultaneously which means that the head can be moved into areas previously only accessed with a great deal of trouble. This is especially true when the CMM is moving in FLY mode. The following example moves the machine to a Cartesian position of 100, 100, 0 while simultaneously rotating the head to the angles 90 and 180.



Those of you familiar with the polar head rotation of existing probe heads will recognize the angles in this example (note … the order is B then A). The angles are an easy way for existing programmers to create moves with built in head rotations. In this case the angles are considered absolute which means that a programmer must enter new angles to measure another feature in different orientation. The next example moves the CMM to a polar position of 30.5 (radius), 0 (angle) and a height in the current work plane (WKPLAN) of 76 while simultaneously rotating the head using Euler angles -9045 and 180.



Unlike the previous HEADCS angles which are familiar to us, Euler (pronounced ‘oiler’) angles are defined from the current axes system and as such can be reused by rotating the axes using the relevant DMIS statements. This makes it very easy to create code to measure a feature and then rotate the axes to measure a similar feature without having to modify the head orientation. This also means that the probe head will reorient to facilitate parts that are not perfectly aligned to the CMM axes. The downside to using Euler angles is that they are not trivial to calculate however a good inspection system will give you tools to create and manipulate these angles without resorting to your calculator. Renishaw’s own inspection software (Modus) provides tools to generate head angles based on part models and a means of converting the usual A and B angles into Euler angles. DMIS language statements have also been added to define touches that include head movement:

The PTMEAS statement:




As with the DMIS GOTO statement head orientation parameters have been added to the PTMEAS statement. It has also gained an option for ‘touch type’ (either HEADTOUCH or ALLAXESTOUCH) which defines whether the head should be used alone or with the CMM to touch the part.



This example measures a point at x=4.5 y=0 and z=0. The point has a negative Y normal and the measurement will be carried out using a combination of the CMM and head axes to touch the component. The following screen shot illustrates the process of generating PTMEAS touches using a model based tool set:

Each of the blue lines represents the head angle as it makes contact with the bore being measured. This means that the CMM can remain stationary while the head measures the circle. The resulting DMIS code is listed below:


The PTMEAS statement is generally considered a touch statement and although it can be used in some scanning statements it is generally recommended that scanning employ the DMIS PATH statement:

The PATH CURVE definition statement:

P(name)=PATH/CURVE,x,y,z,i,j,k,PTDATA,z,y,z,i,j,k,HEADCS,b,a …


P(name)=PATH/CURVE,x,y,z,i,j,k,PTDATA,z,y,z,i,j,k,PCS,z1,y,z2 …

The DMIS PATH statement when used with a CURVE parameter provides a position and plane for the CURVE but also allows the addition of multiple PTDATA parameters containing a touch definition (X, Y, Z, I, J, K) and the orientation of the head as relates to that touch. When multiple PTDATA parameters are strung together the CMM and head flow from one point to the next in a seamless scanning movement without the usual need for stops in order to reorient the head for access. The following illustration shows PATH generation for a CURVE using a rail tool. This example clearly shows that the head moves to access the curve while the CMM moves along the rail forming a 5 axes measurement.

The PATH statement provides similar functionality for surfaces:

The PATH SURF definition statement:

P(name)=PATH/SURF,PTDATA,x,y,z,i,j,k,HEADCS,b,a …


P(name)=PATH/SURF,PTDATA,x,y,z,i,j,k,PCS,z1,y,z2 …
The SURF version of the PATH statement is very similar to a CURVE but is not restrained to a plane and as such does not require position or plane definitions.

Other PATH statements have also been co-opted by Modus to implicitly include head orientations based on the definitions contained therein and it is expected that most DMIS based systems will provide DME measurement routines when in AUTO MODE making upgrading existing DMIS based systems relatively straight forward from a program modification point of view.

One final area of interest is the DMIS SNSLCT statement. Although the move and measurement statements talked about in this article make actual sensor selection virtually unnecessary there may be times when you would like to move the head without moving the CMM. The DMIS SNSLCT statement has been modified to allow this:

The SNSLCT statement:



By now you will be familiar with the head angles added to the end of the SNSLCT statement. When a SNSLCT is executed the DMIS system will use the name of the sensor to recall the relevant calibration map and decide whether to change to another rack position. The optional head angles can be used to rotate the head to a predefined position. If an independent head move is not required the programmer will typically use the DMIS RECALL statement to retrieve the sensor from the softwares database and then use the SNSLCT statement to install the relevant map at the start of the program after which no other selections will be necessary.

This article was designed to get you started with 5 Axes Programming, for more information on this subject you are encouraged to explore the DMIS Standard version 5.2 available at For more information about Renishaw products and the new technologies discussed in this article please visit

Stephen Horsfall specializes in DMIS programming, training and consulting and is the author of ‘Step by Step DMIS Programming’. He can be at contacted at