Mastercam 8.1 Beta 4: New Verification Engine in Beta 4! Sub-Programs Post Changes
Mastercam 8.1 Beta 4: New Verification Engine in Beta 4! Sub-Programs Post Changes
Mastercam 8.1 Beta 4: New Verification Engine in Beta 4! Sub-Programs Post Changes
1
Beta 4
This document contains all of the up to date information concerning Beta 4. Follow the
links below to get specific details.
- A listing of all the new features to be included in Mastercam version 8.1 when it
is released. What’s new in version 8.1
- A complete list of bugs that have been addressed in Beta 3. Fixed in 81-b3
- A complete list of bugs that have been addressed in Beta 4. Fixed in 81-b4
- A description of the new Stock Recognition and VTL features in Lathe 8.1.
Lathe81 b3 Changes
- A simple guide for learning the new Lathe functions in version 8.1.
Lathe 81 Demo Files
New Verification Engine in Beta 4 Top
The long awaited change from Sirius to Lightworks for Toolpath Verification is now
available in Beta 4 of 8.1. The switch has been under development since the purchase of
Sirius by Lightworks early last summer. We have been very pleased with the speed and
quality of the results of all of the toolpaths we have run thus far. Here are some things to
keep in mind about this change.
Above all, we are very pleased with the relationship we have developed with
LightWorks. They have been very responsive and accommodating during this process,
which gives us great confidence that the Verification issues that have been with us since
version 7.0 will soon be a thing of the past.
Sub-Programs Top
Sub programs have been reworked in Mill and Lathe and are ready to be looked a more
extensively outside of CNC Software. Many of the changes affect Toolpath, Transform
which has created some changes in the transform functionality. There are still some
issues that need to be resolved with work offsets that are being worked on.
"Variable not defined: gear" In earlier versions of MP, this error would never have
been reported and may not cause a problem in most of them, but in some posts an un-
initialized variable in a string selector will cause major problems, It all depends. We
decided that we are better off trapping the error and flagging the user, but continue to
process anyway. This error warning should only occur in the newer DLL's shipping with
8.1 and shouldn't effect older version of Mastercam. That doesn't mean that the user may
not run into a problem with this in older versions, it just means the DLL won't catch it.
What’s new in version 8.1 Top
All Products:
- New command line switches to control the level of the software running.
Design:
- Create/Pattern - Bring in all the geometry from an existing Mastercam file. This
was limited in the past to only points, lines, arcs, splines, NURB & Parametric
surfaces, and notes.
Mill:
- Verification can now use an input file as the initial stock - any file with triangles,
solids, or surfaces can be used to describe the stock including IGES, X_T, MC8,
STL, etc.
- Verification can now save the result of a session to an STL file that can be
recalled as stock for future operations.
- Define Tools dialog added a display of the 'auto' or 'custom' tools to the dialog.
- Analyze Chain (Single & All) added to Chain Manager as a right-click option.
- Toolpath, Surface, STL – In future Beta releases this option will allow users to
create toolpaths directly on STL files. This is not active for Beta 2.
- Toolpath, Reference Point - This dialog has been modified to make it much
easier for user to control the tool motion before and after the current toolpath.
- A new option in Manual Entry to allow users to create file notes on the fly.
Lathe:
- VTL Support - Graphical support for Vertical Turret Lathes. The switch is made
in Job Setup under the Spindle/Turret Button.
- Backplotting will start with the stock results from the previous Operations.
- Home Position can now determined from the Tool, Defaults in Screen
Configure, or in an Operation specific dialog.
- Tool Clearance Definitions and Custom Tool Definitions have been modified to
make it simpler.
Wire:
- Wire frame shading of the initial toolpath to give a quick look at the results.
- The user is now able modify the STCW setting from the NC parameters page.
- Full Associativity!
Mill:
Lathe:
Wire:
Bug 15020 09/07/2000 Medium
Wire, Backplot - If you turn the wire display on it will not stay on the next time you go into
backplot.
Bug 14120 05/31/2000 Medium
Canned wirepath points display incorrectly
Bug 14242 06/20/2000 Medium
Selecting Parameters line in Op Manager, looking at Lead in/out page and notice that Auto
position cut point and Tab Cut Leads
are selectable but if you select the Cuts tab then go back to Lead in/out tab the Auto position cut
and Tab Cut Leads are 'grayed
out'.
Mill
Lathe
Wire
The concept behind network licensing is that a group of Mastercam users who are all
connected to the same network can run Mastercam from any station on that network
without moving any software protection device between computers. Instead of requiring
one HASP on each computer that will be used to run Mastercam, one NetHASP will be
installed on any station on the network. That station will be referred to as the NetHASP
server. It is not necessarily the network server – in fact, it’s preferable not to use the
network server as the NetHASP server.
Customer requirements:
Network requirements:
Although NetHASP supports most networks, we have only tested it with Windows 32-bit
operating systems. The IPX, TCP/IP and NetBIOS network communications protocols
are supported.
1. Select a computer that will be the NetHASP server. Again, it’s best not to select
the network server.
2. Optionally, configure the license manager with the nhsrv.ini file. The nhsrv.ini
file allows the network administrator to specify which workstations are served by
the NetHASP server.
3. Connect the NetHASP to the computer’s parallel port.
4. Run the Aladdin NetHASP License Manager for Win 32 utility (nhsrvw32.exe).
5. Check available licenses with the Mastercam nhasp80.exe utility.
The options that will be enabled for each Mastercam product are specified with command
line switches. The switches are:
To set command line options on a shortcut icon, select the icon with the right mouse
button. Select Properties. Select the Shortcut tab. Add the command line option to the
Target edit field. For example:
C:\mcam8\mill8.exe /E
C:\mcam8\mill8.exe /3 /S
C:\mcam8\lathe8.exe /1 /M1 /S
It is not a good idea to constantly edit command line options. Instead, icons for each
product and level that may be used should be set up. For example, the customer may want
to set up three icons labeled “Design8 with Solids”, “Mill8 Entry” and “Mill8 level 3”.
The user would simply select the appropriate icon and avoid editing command line
parameters every time he or she runs Mastercam.
Note on using command line options with directory names that contain spaces:
When the directory name contains spaces, quote marks must be used. The less obvious
point is that command line options must be placed outside the quote marks. Ex:
Enabling Solids:
The /S command line option must be used to enable Solids. There are numerous checks in
Mastercam for a valid Solids license. Solids creation, analyze, Parasolids file conversion,
STL file conversion, SAT file conversion, STEP file conversion and Xform will check
for a Solids license. If you need to create, import, export or transform a Solid, you need
to use the /S option.
Adding licenses:
The number of licenses for each product is stored in the NetHASP memory. The
maximum number of licenses allowed for each product is further limited by the type of
NetHASP. For example, the NetHASP-20 allows a maximum of 20 Mill Entry licenses,
20 Mill level 1 licenses, 20 Mill level 2 licenses, etc. Once the maximum number of
licenses has been reached, there are two ways to proceed. In this example, the NetHASP-
20 could be exchanged for a NetHASP-50 or NetHASP-100. Another option is to allow
the customer to keep the NetHASP-20 and send another NetHASP-20 or NetHASP-50
with additional licenses enabled on that device. In the latter scenario, the NetHASPs may
not be daisy-chained. A separate NetHASP server would need to be set up for the second
NetHASP.
Error messages:
When Mastercam starts up, it will attempt to get a license from the NetHASP server.
There are many reasons that this step may fail. Here are the most common reasons:
This message is obvious. Contact your dealer and purchase the necessary options.
Indicates that the maximum number of users that are allowed to license a product are
using it at the current time.
Approximately every five minutes, Mastercam verifies that the NetHASP server is still
running and the NetHASP is attached to the server. If this test fails, due to the NetHASP
server crashing, loss of power or theft of the NetHASP, etc., the following message will
be displayed from Mastercam:
In the nhasp80.exe utility, there is a button labeled Active licenses. Set Mode to Network
to enable this option. Click on Active licenses to show which products are licensed, the
number of active users, the maximum number of users and the number of available
licenses for each product. This function will run slowly if nethasp.ini is not present or is
set up incorrectly. Please note that nhasp80 does not report the licenses that are checked
out on the computer on which it is running.
The Aladdin monitor.exe utility displays a list of users logged into the NetHASP server,
but does not show which products they are using. To use this utility, double-click on the
appropriate protocol such as TCP/IP. When a server is found, double-click on one of the
servers. The list of users will then be displayed. Unfortunately, this utility tends to be
very slow.
The nhasp80.exe utility:
The nhasp80.exe utility, provided by CNC Software, Inc., will be needed to administer
Mastercam network licensing.
Sim type
Select HASP or NetHASP. The SIM type is written to the registry. When Mastercam
starts up, it reads the SIM type from the registry and decides whether to check the HASP
or NetHASP.
Mode
Local reads the NetHASP from the local computer. Network reads the NetHASP that is
connected to the NetHASP server, which may or may not be the local computer.
Read
Displays the product list that is programmed in the NetHASP. The NetHASP is read from
the local machine or NetHASP server according to the Mode setting.
Update Code
Selecting the Update Code button allows an update code file to be selected. The update
code file name may be entered directly in the adjacent field.
The list of products shows the number of stations authorized for each product followed
by the product name.
Update
The Update button allows the number of stations for each allowed product to be updated.
Update only works in local mode. Before selecting Update, enter the update code file
name.
Active licenses
Works only in network mode. Displays the number of licenses currently checked out, the
number of licenses authorized, and the number of licenses that are currently available for
each product.
Note: none of the licenses that are checked out from the local computer are reported by
Active licenses.
Stop
User type
This read-only field displays the user type: Industrial, Educational, etc.
Serial number
These read-only fields display the first and last date for which the NetHASP licenses are
valid or display “Unlimited” if the licenses are available permanently.
Sample nethasp.ini for TCP/IP:
[NH_COMMON]
;; This NetHASP.INI file is configured to TCPIP.
;; Please note that you will have to enter the address of the NetHASP
key station:
[NH_TCPIP]
Bundling does not exist with the NetHASP. This potentially makes the NetHASP much
more valuable than the HASPs that it replaces. A common scenario is that a school has
20 HASPs each programmed for Mill level 3 and Lathe level 1. When the school trades
in 20 HASPs for one NetHASP programmed for 20 seats of Mill level 3 and 20 seats of
Lathe level 1, it is now possible for 40 stations to be running simultaneously, whereas
only 20 simultaneous stations were possible with the HASPs.
Further information:
This document only provides a brief introduction to setting up network licensing for
Mastercam. See nethasp.txt for further information.
Lathe81 b3 Changes Top
If you have defined the stock boundary in Job Setup, you no longer
have to chain the outer boundary for roughing between boundaries.
The software will use a section of the stock boundary for the outer
boundary. It will also linearly extend the ends of the chained
contour to the stock, if the endpoints are inside the stock
boundary. This means that you no longer have to create the (usually
vertical) ‘tick’ line added to the end of the inner chained boundary
to indicate the height of the stock. This feature will virtually
eliminate the need to use lead in/out parameters for roughing
toolpaths.
Interface changes:
A Use stock for outer boundary check box and Adjust Stock… button
have been added to the rough parameter page. These controls will
only be enabled if only one contour is chained, stock for the
current active spindle is defined and the chained contour lies
within the stock boundary.
This check box controls whether or not the stock boundary will be
used as the roughing outer boundary. Checking it enables the
Adjust Stock… button.
Note 1: The software will linearly extend the ends of the chained
contour to the stock, whether or not this check box is selected.
The line added to the start of the contour will be parallel to
the cut direction if you are roughing a section or a ‘mountain’
(one end of contour higher than the other or the middle is higher
than either end). It will be perpendicular to the cut direction
if you are machining a ‘cavity’ (endpoints of the contour are
higher than the middle). The line added to the end of the contour
will always be perpendicular to the cut direction.
Note 2: You should not check Use stock for outer boundary for
zigzag roughing of pocket / groove geometry. If you are using
zigzag rough to remove a ‘mountain’ of stock, then you should
check this option.
Adjust Stock… button
Selecting this button allows you to view and adjust the area of
stock to be removed by the roughing operation. When selected,
this button activates the Adjust Stock button bar shown below and
highlights the area of ‘remaining stock’ between the stock
boundary and chained contour in red. A yellow point indicates
the start of the chained contour, while a red point indicates the
end of the chained contour.
You can adjust the lines used to extend the chain to the stock
boundary by left clicking on them and rotating them to the
desired angle and left clicking again. You may also use the
buttons on the button bar to orient the lines in a pre-defined
manner.
b) Canned Rough
If you have defined the stock boundary in Job Setup, the software
will linearly extend the ends of the chained contour to the stock,
if the endpoints are inside the stock boundary. This means that you
no longer have to create the (usually vertical) ‘tick’ line added to
the end of the chained contour to indicate the height of the stock.
This feature will virtually eliminate the need to use lead in/out
parameters for canned roughing toolpaths.
Note: The outer stock boundary is NOT used in computing the roughing
toolpath as CNC controls do not support roughing between boundaries
in their canned cycles.
Interface changes:
An Extend contour to stock check box and Adjust Contour Ends… button
have been added to the canned rough parameter page. These buttons
will only be enabled if stock for the current active spindle is
defined and the chained contour lies within the stock boundary.
Selecting the Extend contour to stock check box enables the Adjust
Contour Ends… button. The Adjust Contour Ends… button functions
exactly like the Adjust Stock… button previously described. If the
Extend contour to stock check box is not checked, the stock boundary
will not be used to extend the ends of the contour.
If you have defined the stock boundary in Job Setup, the software
can linearly extend the ends of the chained contour to the stock, if
the endpoints are inside the stock boundary. This feature will
virtually eliminate the need to use lead in/out parameters for
finish toolpaths.
Interface Changes:
An Extend contour to stock check box and Adjust Contour Ends… button
have been added to the rough parameter page. These controls will
only be enabled if stock for the current active spindle is defined
and the chained contour lies within the stock boundary.
This check box controls whether or not the chained contour should
be extended to the stock boundary. Checking it enables the Adjust
Contour Ends… button.
If you have defined the stock boundary in Job Setup, the software
can utilize the stock boundary as the groove outer boundary. If the
groove endpoints are inside the stock boundary the software can also
linearly extend the ends of the groove to the stock either parallel
to the groove angle, or tangent to the groove walls. This feature
eliminates the need for the Stock amount parameter on the Groove
rough parameters page.
Interface Changes:
A Use stock for outer boundary check box and Extend groove to stock
radio buttons have been added to the Groove shape parameters page.
The Quick groove shape parameters page only contains the check box.
e) Face
If you have defined the stock boundary in Job Setup, the software
can utilize the stock boundary to define the start and end positions
of each pass when facing a part.
Interface Changes:
f) Drill
If you have defined the stock boundary in Job Setup, the software
can automatically adjust the clearance and retract points to insure
that the tool will not crash into the stock, if the stock definition
is changed after the toolpath is created.
Interface Changes:
From stock check boxes have been added for the clearance and retract
points of the Lathe drilling parameters page. These buttons are
only enabled if the stock boundary is defined, and the Incremental
radio button is selected for the parameter. If you check From stock
for either the clearance or retract point, it will be computed from
the face of the part rather than from the drill point. If the stock
definition changes, these points will be re-computed when the
drilling operation is regenerated.
The Mastercam interface has been made more intuitive for programming
vertical turret lathes (VTL’s). This is accomplished through
virtually rotating the graphics screen 90 degrees counterclockwise
and appropriately modifying parts of the user interface. Toolpaths
can be switched from HTL to VTL mode and vice-versa by selecting the
appropriate mode in Job Setup -> Spindle / Turret. Operations do not
need to be regenerated after switching. Saving the file once the
appropriate machine type is selected will preserve the change. The
VTL job setup switch (which will be ‘off’ in all V8.0 files) is the
only addition to the database.
Interface changes:
When VTL mode is selected, the default system graphics views are
rotated accordingly. All common views will have 8 added to their
view number. (ex. When top view is selected, View 9 shows under
Gview.) To access the ‘normal’ views, the view number can be used.
(ex. To access the ‘normal’ Top view, select Gview, Number, and
enter <1>.)
Dialog box changes include:
• Tools shown on button faces image lists are shown in the VTL
orientation
• The terms Top and Bottom turret are replaced with Left and Right
respectively. The terms Left and Right spindle are replaced with
Lower and Upper respectively. All associated graphics are
rotated appropriately.
• A VTL specific Geometry parameter page has been added for
defining custom tools. On this page, the tool orientation is
shown with respect to the ‘normal’ top view, while the turret
orientation is show with respect to the ‘VTL’ top view.
• Any VTL/HTL specific icons/dials will show in the correct
orientation. Examples include the entry/exit vector, roughing
angle and groove angle dial pointers and the rough/finish cut
direction icons.
3. Rough plunge feed rate has been moved from the Rough parameters page
to the Toolpath parameters page. The Toolpath parameters page with
plunge feed rate is only used for Rough toolpaths. Also, a checkbox
has been added to this page to disable plunge feed rate, if desired.
4. The Quick Groove Cut parameters page has options for retract and
dwell in pecking as shown below. The dwell time is automatically
computed to insure that the tool dwells for at least one full
spindle revolution.
6. Zigzag threading has been added to the NC code format drop-down list
on the Thread cut parameters page.
8. The Custom Tool definition interface has been improved. Custom Tool
geometric display is controlled by 4 parameters:
• Tool orientation in the MC8 file (Custom Tool Geometry page)
• Tool orientation in the turret (Custom Tool Geometry page)
• Selection of the Reverse tool check box (Lathe Tool Setup dialog)
• Tool angle (Lathe Tool Setup dialog)
9. The Tool Clearance interface has been improved. The ‘mouse click
intensive’ menus have been replaced with a dialog, which allows the
user to see and edit all of the parameters on one page. The terms
‘back angle’ and ‘lead angle’ have been replaced with the more
correct terms ‘end clearance angle’ and ‘side clearance angle’.
Graphics are included in the dialog to avoid confusion as to what
the angles (as well as tool width and height) mean.
10. When defining tool clearance parameters for custom tools, tool
orientation and shift are no longer set by selecting Scan Geo…
Removing these parameters keeps tool orientation definition simple.
The orientation set on the custom tool Geometry page is what is
used (see item #8).
11. The Lead In/Out dialog for all canned toolpaths no longer
contains controls for defining entry/exit vectors. The entry/exit
vector moves defined in this dialog are shown in the Mastercam
backplot, but are NOT executed by the machine control when the
canned cycle is invoked. This discrepancy could lead the user to
believe they have programmed a safe toolpath, when in fact, it may
contain tool crashes
12. Groove width can be automatically set to the tool width. A Use
tool width check box has been added to the Groove, Quick Groove and
Canned Groove shape parameter pages. If this option is checked the
width of the groove will be set to the width of the tool insert. If
the groove is OD or ID, the Z stock amount will be added to the
groove width. If the groove is a face or back groove, the X stock
amount will be added. If the groove is at any other angle, stock
amounts will not be added to the groove width.
14. Auto cutter comp uses the stock boundary, if defined, so it will
work in more cases.
15. Cross contour uses the entire chain to set the tplane/cplane, so
it will work in more cases.
16. All 2-axis lathe toolpaths can be updated using apps. This will
facilitate bug fixes between releases similar to the fashion that
multi-surface machining is updated.
Face81.mc8
This file demonstrates the new stock recognition for facing toolpaths. From the
Operation Manager:
1. Edit the facing operation and show the new ‘From stock’ option for facing
rectangle definition. Change it to Select Points and click on points to show how
points may be selected from this page, if desired. Mention that the parameter
screen now comes up immediately, and you must select the points from this page,
if this is how you are going to define the operation. Change the facing option
back to ‘From stock’, or select Cancel so your changes aren’t saved.
2. Move the facing operation to the bottom of the operation list.
3. Regenerate both operations.
Note start and end of each pass in the facing operation are computed relative to the stock.
FaceDrill81.mc8
This file demonstrates the new stock recognition for facing and drilling toolpaths.
The facing operation is set up to use the stock, and the retract heights for the drilling
operation are set up to be incremental from stock. The default operation order in this file
is Face, Drill 1” dia. hole 1” deep, Drill ½” dia. hole through the part, with the retract
point incremental to the stock. To demonstrate this part:
1. From the Operation Manager, backplot all of the operations. Notice how, on the
third operation, the drill will rapid into the larger hole using the smaller diameter
drill. To accomplish this in v8.0, you would have to know exactly how deep to
set the retract height on the third operation.
2. Edit the first drilling operation and show the new ‘From stock’ check boxes.
These check boxes are only enabled if stock is defined, and the Clearance or
Retract height is set to ‘Incremental’.
To demonstrate the ‘stock recognition’ aspect: re-order the operations however you see
fit and regenerate them. You will always get an optimized toolpath and never get a tool
crash.
Notes on drilling:
1. The clearance height is turned on and set to ‘absolute’ in the file for both drilling
operations. Setting the clearance height to a known clear Z coordinate is good
programming practice for drilling, especially when canned cycles are used, as
more efficient NC code (2 less G0 moves) will be created.
2. The tool collision function for drilling works only from the drill diameter. If the
drill is too short to machine the hole, the software will try to program the drilling
operation, then give you a tool collision warning. (In this example, this situation
would occur if the 1” dia. hole was deeper than the length of the ½” dia. drill.)
RoughFin81.mc8
This file demonstrates the new stock recognition for facing toolpaths. From the
Operation Manager:
For roughing:
1. Backplot the roughing operation.
2. Edit the roughing operation, and check the Rough parameters page. Note that the
Lead In/Out parameters are off. This toolpath was created without extending any
geometry, either by creating it, or using Lead In/Out parameters as would be
required in Lathe 8.0. (In Lathe 8.0 you would have to extend the end of the
contour and add a lead-out line using the lead-out parameter page.
3. Click on the Adjust Stock button and show the users how the different ‘remaining
stock’ options work.
4. Click on the Plunge Parameters button, change the plunge options, and regenerate
the operation to show how you can control plunging in X and Z.
For finishing:
1. Backplot the finishing operation.
2. Edit the finishing operation, and check the Finish parameters page. Note that the
Lead In/Out parameters are off. This toolpath was created without extending any
geometry, either by creating it, or using Lead In/Out parameters as would be
required in Lathe 8.0. (In Lathe 8.0 you would have to extend the end of the
contour or add an exit vector using the lead-out parameter page.
3. Click on the Adjust Stock button and show the users how the different ‘remaining
stock’ options work.
4. Click on the Plunge Parameters button, change the plunge options, and regenerate
the operation to show how you can control plunging in X and Z.
FinishLeadOut81.mc8
This file demonstrates when to use, and when not to use the 'Add lead-out line to contour'
option in the Adjust Stock button bar for finish toolpaths. The tool nose radius has been
increased to exaggerate the effect of different options.
Operation #2 - finish across the top of the part. Part geometry is embedded in the stock.
In this case, adding the lead-out line to the contour enables you to finish the diameter
along the entire length of line, without using lead out parameters. If you turn off the 'Add
lead-out to contour' parameter, the tool will leave a chunk of material at the end of the
cut. To demonstrate this:
The effect of adding the lead out line CAN be accomplished using lead out parameters,
but this is a much easier way to accomplish the same thing, as the software computes just
how far past the stock the tool needs to go. The lead in/out dialog should only be used
for special cases where the user really needs to control tool motion.
Groove81.mc8
This file demonstrates the new stock recognition for grooving toolpaths. From the
Operation Manager:
1. Backplot the 1st two zigzag roughing operations. Note that these were also
programmed without lead in/out on, showing how the software uses remaining
stock to determine how to get the tool on and off the part.
2. Backplot the Operation #3 only, using Verify. This will show how the software
uses the stock from the previous operation for backplot. Note that the retract
moves are all relative to the remaining stock from the previous operation.
3. Edit the geometry for Operation #3. Have the users note that there is only 1 chain.
The stock is used as the outer boundary.
4. Edit the operation, un-check Use stock for outer boundary on the Groove shape
parameters page and regenerate the operation. This will demonstrate how the
software automatically puts in a line for the outer groove boundary, if one is not
supplied, and you don’t use the stock boundary.
5. Repeat steps 2 and 4 for the Operation #4.
6. Change ‘Extend groove to stock’ options (Groove shape parameters) for
Operation #4, and then regenerate it to show the different options for extending
the groove inner boundary to the stock.
1HitGroove81.mc8
This file demonstrates the new ‘From tool’ option for defining the groove width. To
demonstrate this feature:
1. Edit the operation and on the Groove shape parameter page, note that ‘From tool’
is checked and the groove width edit box is disabled.
2. Backplot the operation to show the 1 hit groove.
3. Edit the operation, change the tool to a grooving tool of a different width and
regenerate the operation. The result will be a new 1 hit groove with the width
equal to the width of the new tool.
VTL81.mc8
1. Load the file. Mention that it is in VTL position on the screen. It is actually
Lathe7.mc8 with Job Setup configured to VTL.
2. To show users this feature, click on the Spindle/Turret button from the Job Setup
dialog. Note the rotated icons in both dialogs.
3. Edit any Lathe tool and draw it. Note that it is be in VTL position also.
4. Edit the 1st roughing operation. Note that the tools are in VTL position in the
image list. Note that the dimensioned bitmap is NOT in VTL position. The
rough position bitmap IS, however.
5. Click on the Angle button. The roughing angle is in VTL position.
6. Click on the Lead In/Out button and select the Lead-out tab. Note that the angle
dial points in the correct VTL direction.
7. Cancel from editing this operation.
8. Edit the 1st grooving operation. This should be the angled groove. Select the
Groove shape tab and note that the groove angle is correct for a VTL. Note that
the dimensioned bitmap is NOT in VTL position.
O1ODTool.MC8.
Top