LEITZ Options

The entries in the LEITZ section in PC-DMIS Settings Editor are:

FDC does not do temperature compensation of positions. It only probes and scans.

If the firmware is new enough to support it and if this setting is set to True, the machine will use the PRBTYP command. If this setting is set to False (default), the machine will not use the PRBTYP command regardless of whether the firmware supports it or not. This setting has no effect on non-UHA machines.

0 = This value disables the attempted control of DISPCSY, which prevents any attempt to send the relevant controller commands to enable, disable, or define this coordinate system. A value of 0 should prevent errors if you use a machine that doesn’t recognize or support DISPCSY.

1 = This value forces the machine to Native Machine, which enables you to use the jog box keys to select the Machine or Workpiece coordinates. When you select Machine coordinates, the display is in the machine’s native coordinates regardless of whether or not axis re-assignment had been used in the setup.

2 = This value specifies that the machine is User Defined Machine, which enables you to use the jog box keys to select the Machine or Workpiece coordinates. When you select Machine coordinates, the display is in the machine coordinates as defined by the user’s setup. Note that this is different than Native Machine coordinates if axis re-assignment was used in the setup.

0 = This value disables attempted control of the units. This value prevents any attempt to send the relevant controller commands so the units remain unchanged.

1 = This value specifies the measurement routine units. When you open a measurement routine, the jog box display units are set to either inches or millimeters to match the units that the measurement routine uses.

2 = This value specifies millimeters. The display units are in millimeters regardless of the measurement routine units.

3 = This value specifies inches. This value specifies inches. The display units are in inches regardless of the measurement routine units.

0 = This value disables attempted control of JOYSTCSY, which prevents any attempt to send the relevant controller commands to enable, disable, or define this coordinate system. A value of 0 should prevent errors if you use a machine that doesn’t recognize or support JOYSTCSY.

1 = This value forces the machine to Native Machine, which enables you to use the jog box keys to select the Machine, Workpiece, or Probe coordinates. If you select Machine coordinates, the joystick motion is in the machine’s native coordinates regardless of whether or not axis re-assignment was used in the setup.

2 = This value specifies that the machine is User Defined Machine, which enables you to use the jog box keys to select the Machine, Workpiece, or Probe coordinates. If you select Machine coordinates, the joystick motion is in the machine coordinates as defined in the setup. Note that this is different than Native Machine coordinates if axis re-assignment was used in the setup.

For native Leitz systems, you can change the rotary table's maximum velocity with the MaxTableSpeed entry.

ROTABSPEED Command

When you define a Move/Rotab command, the command uses the speed value set in the Rotary Table tab of the Parameter Settings dialog box (Edit | Preferences | Parameters). You can override this value to slow down or speed up the rotary table with the ROTABSPEED command.

For example:

STARTUP=ALIGNMENT/START,RECALIBRATE:USE_PART_SETUP,LIST=YES

ALIGNMENT/END

MODE/DCC

MOVESPEED/ 96

FLY/ON

FORMAT/TEXT,OPTIONS,,HEADINGS,SYMBOLS,;NOM,TOL,MEAS,DEV,OUTTOL,,

LOADPROBE/X5HD

TIP/X5HD, SHANKIJK=0,0,1, ANGLE=90

MOVE/ROTAB,30,SHORTEST,

.

.

.

ROTABSPEED/ 72

.

.

.

MOVE/ROTAB,60,SHORTEST,

.

.

.

ROTABSPEED/ 20

.

.

.

MOVE/ROTAB,77,SHORTEST,

.

.

.

In this example, the last five lines show the insertion of the ROTABSPEED command. The first instance speeds up the rotary table to 72 deg/sec, possibly to speed up the measurement process for a small part. The second ROTABSPEED command slows the rotary table down to 20 deg/sec, possibly for a larger part.

 

If you use the default value of 0 (zero) for the ROTABSPEED command, the rotary table's speed is proportional to the value set for the MOVESPEED command. This is necessary for backward compatibility prior to the implementation of the ROTABSPEED command.

For systems with stacked rotary tables, you need to account for both tables in the ROTABSPEED command, ROTABSPEED <wspeed>[,<vspeed>] where <wspeed> is table one and the optional <vspeed> is table two.

ROTABSPEED/ 50,40

An example of a system with a stacked rotary table is the Optive CMM for vision systems.

 

0 = X,Y,Z,I,J,K

1 = X,Y,Z,I,J,K,W,A,B

2 = X,Y,Z,I,J,K,W

There are two different versions of the wcompens32 DLL. The older version supports a format for the compensation data map that a newer format has replaced. The newer version of the DLL supports only the newer data format.