miim

### Machine Specific Options:

· InitFileName=PCD_***.txt - The name of the configuration text file you are using.

· JogBoxKey1=0…… JogBoxKey21=0 - This is how the jog box mapping takes place. For details, see the section below on Jog Box Macros.

· JOGSpeed=0.0 - For many Zeiss machine the jog speed in manual mode is affected by the speed set during a DCC program execution. This value can be used to establish a speed that will be set when returning to manual mode so that the jog speed will not depend on the last used DCC speed. If set to 0.0, it will have no effect at all rather than trying to set a jog speed of 0. This is input as a percent of maximum so the maximum allowed value is 100.0.

· MappedJogKeys=TRUE - Allows the jog box keys to be mapped differently than the default. See the section below on Jog Box Macros

· MinRotabMove=0.5 Any request to move the rotary table to a position that is less than this angle from the current position is ignored.

· PH9 = COM0 4800 N,8,1- The PH9 RS232 port and settings can be adjusted by changing these values. For example, if you wish to control the PH9 on comm 2 with settings of 9600 baud, Even parity, 7 data bits and 2 stop bits then you would enter PH9 COM2 9600 E,7,2.

· PH9ManualMode=1 - If a PH9 'pendant' hand controller box is present then you must make this option = 1. If you set this wrong, then you will get intermittent 'locking ups' before probe rotations.

· PreWaitendDelay=0.0 - This is a delay time (in seconds) that PC-DMIS will wait before checking to see if the movement is complete. When a DCC move is sent, Zeiss controllers do not explicitly send back an acknowledgment upon completion of the move. PC-DMIS has to poll the status to see if there is any motion in progress. On some machines, there is a definite lag time after a move command is sent before the machine starts moving. If PC-DMIS starts polling too quickly after sending the move, the status will indicate that there is no motion and it will appear as if the move is complete when in reality it hasn’t yet started to move. Setting this value to > 0.0 (a typical value might be 0.1) will give the machine time to begin the move before the status polling begins.

Note: The following few options that start with ‘remoteButton’ relate to a Remote Button utility that can be run on new Zeiss jog boxes that are real laptops running Win95/98 (Dialog I or II). This allows usage of three buttons that can communicate with PC-DMIS. These options are all set on the PC running PC-DMIS. The ones on the Dialog are set using the Setup dialog.

Version 1.79n adds EX, EY, EZ (error of the last measurement) to Remote button utility dialog. It can be enabled through Options->Setup.

Here is a picture of the Remote utility with the setup dialog (accessible through the Options menu.)

· remoteButtonActive=FALSE - This is set to TRUE if you are running the remoteButton application on the new Zeiss laptop jog box.

· remoteButton_LocalPort=7712 - Defines the local port on which to communicate with the remoteButton app.

· remoteButton_RemotePort=7714 - Defines the remote port on which to communicate with the remoteButton app.

· remoteButton_LocalAddress=””. - Defines the local IP address on which to communicate with the remoteButton app.

· remoteButton_RemoteAddress=”” - Defines the remote address on which to communicate with the remoteButton app.

· IP_Button_UDP_Timeout - Timeout for more reliable communication with the Remote button utility. This is new in version 1.79n.

· ScaleX=1.0, ScaleY=1.0, ScaleZ=1.0 - These values allow you to specify the scale factor for each axis. This is normally a value of 1.0.

· probe changer Options- For details on these options, see the Tool Changers section:

o TCDepthClearance=75

o TCLengthBackOutOfSlot=20

o TCLengthClearance=-55

o TCLengthInFrontOfSlot

o TCUsingCalibrationTool

o TCVerticalClearance=7.0

o TCVerticalDropToRealDropoff=66

o TCVerticalStroke=10.0

· TimerUpdateInterval=50 - This determines the polling rate for statuses and position updates. It should be in the range of 30-50 ms.

· ToolChangePreWait=2.5 - Defines the amount of time to wait after the move is complete before issuing the next move during the Tool Change. If some moves are premature, this should be set higher.

· VectorOffset=3 - Change this value if the vector from manual hits is not reliable. The allowable range is 1 to 6 inclusive.

· WaitEnd=0.20 - This is a delay time (in seconds) that the interface will wait after the controller motion has stopped before informing PC-DMIS that the machine has stopped. This check is necessary since it is feasible that a slight pause takes place between moves but this pause does not indicate that all commanded movements have been executed.

· WaitMoveTimeout=0.5 - This determines how long to wait from the time a motion command is issued until the motion starts. If the motion does not start in this timeframe we assume the CMM is already in commanded position and continue execution by sending the next queued command to the controller.