Sunteți pe pagina 1din 48

Mastercam 8.

1
Beta 4

This document contains all of the up to date information concerning Beta 4. Follow the
links below to get specific details.

- New Verification Engine in Beta 4! Faster processing and better graphics!

- Sub-programs – Changes and additions

- Post changes – New variable checking

- 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

- Instructions and requirements for running the Nethasp. Mastercam Network


Licensing

- 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.

- STL compare is now free.


- 4 and 5 axis verification in Standard mode (True Solids turned off) is now free.
- Image quality is improved so that toolpaths that were run with the Speed/Quality
switch at the 3rd position can be run at the 1st or 2nd position with equal results.
- Verification with both Solid and Wireframe tools supports all tools definable in
Mastercam. (Turbo mode still supports just Flat, Ball, and Bull Nose tools)
- The speed of using of STL stock for Verification is improved.
- Verification support for Wire is included
- “Chip removal”, the ability to select and remove solids created during the
verification process is now available in Wire and Mill.

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.

Post Changes Top

"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

What’s New in Version 8.1

All Products:

- NetHasp support for Network Licensing.

- New command line switches to control the level of the software running.

Design:

- Create/Point/Perp/dist - Makes a point perpendicular to an entity at a specified


distance. This originated as a Wire request.

- Create/Point/Small arcs - Makes points at centers of arcs that can be selected


by their radius. This originated as a Wire request to create start points at the
center of small circles.

- Create/Surface/Trimmed/Fill holes - Makes trimmed surfaces using internal


boundaries, and sections of outer boundaries, of trimmed surfaces.

- Create/Surface/Draft/To Plane - Allows users to specify a plane to end the draft


surface at, rather than requiring them to enter a distance.

- "Group Colors" dialog added to Screen/Config/CAD Settings so user can


control the default Group coloring.

- Output of 1 or more Solids in File/Convert/Parasld/Write

- Improvements to Create/Surface/Trimmed/Remove bndy - Users can remove


all internals at once, and can modify a section of outer boundary to match the
untrimmed boundary.

- Update to Parasolid V12.0 Solids kernel

- Update the ACIS libraries to V6.2 from V6.0.

- File/Convert/SAT/Write and Write dir - Output 1 or more Solids to ACIS' .SAT


format.

- Analyze/Surfaces/Check model - We've added the ability to detect internal


sharp ridges on surfaces. These give the surface machining algorithms fits, and
need to be identified so the user can split them.

- 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.

- Added "gouge check entry/exit" checkbox to Toolpath/Contour's Leadin/Leadout


dialog box.

- Toolpaths/Surface - Add ability to machine ALL displayed surfaces/solids by


setting a switch on the first Surface Toolpath menu.

- 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.

- Added a switch to Job Setup to warn users of duplicate tool numbers.

- 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.

- Remaining Stock - Intelligent stock management for Roughing, Finishing, and


Grooving. New operations now have knowledge of stock leftover from previous
operations. The switch labeled “Use Stock for Outer Boundary” on the parameter
pages activates this option. V-8 Lathe just got easier!

- 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:

- Automatic break up of geometry perpendicular to the Thread point and/or Cut


point when using Window chaining.

- NCI Flags for different types of contours: Punch, Die, Open.


- Single operation per contour generated when window selecting to allow
changing order of operations.

- Window selections now have sorting patterns just like drilling.

- Wire frame shading of the initial toolpath to give a quick look at the results.

- No Core improvements to eliminate slugs and dropouts.

- The user is now able modify the STCW setting from the NC parameters page.

- Full Associativity!

What’s fixed in 8.1 Beta 3 Top

Bugs and Requests addressed in 8.1 Beta 3


Design:

Bug 15348 10/10/2000 High


File, Save - This IGES file creates an MC8 file that will not load into 8.0 if it is converted into 8.1
and saved. It looks like a
Trimmed surface problem from before.

Bug 15358 10/11/2000 Medium


STEP: Seems to convert file but no entities are created.
Bug 15296 10/04/2000 Medium
Screen, Endpoints - When trying to create the points in this file, Mastercam crashes. There are
18000 lines that require points to
be created.

Bug 15375 10/12/2000 Medium


File/Convert/STEP does not do a good job with this file
Bug 15273 10/03/2000 Medium
IGES: SolidWorks part to IGES to MC7 to IGES to MC7 crashes the program after errors. MC7 to
IGES to MC8 OR MC7 to MC8
to IGES to MC8 gets: Cannot make trimmed surface - surface curve not created -entity number
1489, 1499, continues by
increments of 10 through 2639. 2641, type 126: Error reading from IGES temporary file - 5 times,
then original error again for 2089.

Req 15109 09/18/2000 Medium


Screen, Configure - The option for having the main level always displayed is not available for the
user to set. This means it is on all
of the time, if the user likes it off they have to set it every time they start Mastercam. We should
just have a button in Config for
Levels that the user can set it up the way they want similar to the Job Definitions.
Bug 15239 09/28/2000 Low
Create, Surface, Trim Extend, To Curves - When trimming this simple surface to the line, the
portion of the surface that you try to
keep is the portion that disappears. This occurs in both the release and the daily.

Req 15235 09/28/2000 Low


Levels: Wants to be able to default "make main level always visible" to OFF.
Bug 15076 09/14/2000 Low
Create, next menu, letters, file, box or block that the character "&" is not found.

Req 14307 06/23/2000 Low


Levels: Would like "Make main level always visible" an option that can be defaulted under
Screen, Configure or that remains the
last way it was set so when you restart Mastercam you don't have to reset it again.

Bug 13760 04/18/2000 Low


Create, Surface, Trim to curves - If you trim this surface to the curve and pick at the very top of
the surface you get the inverse
results.

Mill:

Bug 15259 10/02/2000 High


T/C Plane - In this file when you go into the T/C Plane dialog and try to exit the dialog by
choosing OK an error is displayed saying
the value for Work Offset must be -1 to 32767. When first entering the page the Work Offset
value was set to AUTO. Trying
to enter a value of -1 returns an error. The only option is to choose the SELECT option and
choose OFF from the menu. Tested
with 8.1 Beta 2

Bug 15175 09/22/2000 High


Operations Manager - If you lock an Operation and then delete the geometry you can still
backplot it, but if i post it nothing but the
1050 line is written to NCI producing an empty NC file. Since the Operation can still backplot it
should Post. If i save the file and
reload it the NCI is wiped out. Since it is locked shouldn't the NCI stay in the Op Mgr?

Bug 15231 09/27/2000 High


Scale don't work. When scaling an MC8 file - specifically with arcs, they seem to scale in the
wrong direction.
Bug 15233 09/28/2000 High
Ctour8.dll (9/12/00 version) - When generating a contour toolpath with Axis Substitution causes
Mastercam to crash.
Bug 15253 10/02/2000 High
File, Converters, STEP, Read - This file is from Catia and crashes Mastercam when trying to read
it in. Dealer reports that Solid
Edge does read the file correctly.

Bug 15284 10/03/2000 High


NCI - V8.1 is writing the 1050 line like:
1050
8 33 9/29/2000 13:49:10 C:\MCAM8\MILL\MC8\V81_TRN.MC8
This is the spec for it:
g
123456789
g 1050: Define NCI version header (gcode)
1 Mastercam version number (vers_no)
2 Mastercam minor version number (m_vers_no)
3 Mc8 time stamp day (mc_day)
4 Mc8 time stamp month (mc_mon)
5 Mc8 time stamp year (mc_year)
6 Mc8 time stamp hour (mc_hour)
7 Mc8 time stamp minute (mc_min)
8 Mc8 time stamp second (mc_sec)
9 Mc8 filename (smcname)

Bug 15287 10/03/2000 High


Contour Ramp dialog locking Mastercam if the right click menu is used in the Depth box
Bug 15363 10/11/2000 High
File, Get- i receive an incompatible error message when i try to load this file that was created in
8.1 back into 8.0. When it does
come in there are no toolpaths. There are no trimmed surfaces in this file.

Bug 14882 08/23/2000 High


curve 5 axis/ output format 5 axis/ curve type surface edge all/ backs up along the path of a
trimmed surface when radial offset is
not used. Violated part geometry with a radial offset. Daily version dated 8-23

Bug 15240 09/28/2000 Medium


File, Get - If you are in the new style dialog it is possible to create dozens of new sub-directories
without knowing it.

Bug 15137 09/19/2000 Medium


Toolpaths, Multiaxis, Swarf5ax - Op 1 and Op 2 are the same with the exception of the max step
(.1 and .05 respectively). Op 2
has some funny gouging in the corners. Could be the we aren't applying the right toolpath, but
Swarf5ax as all the nice lead
in/outs, depths cuts, etc, etc.

Bug 15112 09/18/2000 Medium


Post - When entering a directory in a post in answer to question 90, the name is compacted if it
contains spaces. C:\Program
Files becomes C:\ProgramFiles and causes errors.

Bug 15170 09/22/2000 Medium


Operations Mgr, Save to Library: Click on Export operation's geometry: "Operations that
reference solid geometry cannot be
imported/exported." No solids are in the file. It was converted from DWG to Mastercam.

Bug 15181 09/25/2000 Medium


Toolpaths, Transform - The NCI filename assigned to the Transform toolpath is being set to the
last used NCI name instead of the
source operations NCI File name.

Bug 15184 09/25/2000 Medium


NC Utils, Backplot: Backplotting a v7 drill NCI file shows the tool in various orientations and the
coordinates display $$$$$$.
Bug 15203 09/26/2000 Medium
Toolpaths, Swept2D - If you backplot the swept toolpath you will notice the tool is not offset to the
left or right. If you regen the
undirty toolpath it will backplot correctly and post correctly. You would think running this program
that half of the tool would be into
the part. But the tool only cut .125 to far into the material. So the backplot doesn't even match
the Gcode file. I sent another file up
a month or so ago. It was doing the same thing. I was told there was a bug back plotting bullnose
tools sometimes. I don't know
what the problem is but I have a customer that has spent about $5000.00 fixing blocks and is very
unhappy. If you can tell me
what's going on or if there is a fix for this it would be appreciated.

Bug 15216 09/26/2000 Medium


In this open pocket, the islands seems to be ignored.
There is no comment in the help file about 'open pocket' not supporting islands, and no warning
when the toolpath is created or
regenerated, so I would think this is a error.

Bug 15088 09/15/2000 Medium


This file originated in v7. When you first call up the file and go to the op mgr, all the ops must be
regenerated. after that you can
backplot and post. Now save the file and call it back up. It is right back to where it started and you
must regen all over again.

Bug 15370 10/12/2000 Medium


Toolpath, Circmill - Circmill handles Tplanes differently than Contour. This file has 2 operations
on each circle, one was the
defaults, the second has a tplane of 0,0,-1. The circmill done with the 0,0,-1 Tplane is incorrect.

Bug 15349 10/10/2000 Medium


I imported the file as surfaces, saved it, and then couldn't read the MC8 file back in to Mastercam.
I got the 'Wrong MC8 file type,
run
converter' error message. I removed all of the 'outer' surfs and created some edge curves. While
creating edge curves, Mill would
SOMETIMES crash, not always at the same spot every time.

Bug 14170 06/06/2000 Medium


While in the Sirius Verify module, it is possible to select the FILE icon from the toolbar and get
another MC8 file. It will display on
top of the verified toolpath but as soon as you exit from Verify, Mastercam crashes (Dr. Watson).

Bug 14777 08/10/2000 Medium


5-Axis Entry / Exit Feedrates: There is a -1 feedrate coming out after a rapid move in the
BUG14777.MC8 file. ALL rapid moves
should have a -2 feedrate. I think the plunge feed from the third G11 line belongs on the second
one and the -1 belongs on the
third line.

Bug 15309 10/05/2000 Medium


Version 81b2 will not open this v5.5 file. Get a error message "Incompatible version numbers.
Run MC8 file converter" Version 8.0
will open it successfully.

Bug 14716 08/03/2000 Medium


Toolpath, Filter - When creating a new toolpath, the Filter option is toggled off even though the
Operation Defaults are configured
for it to be active.

Bug 15324 10/09/2000 Medium


Toolpaths, Surface, Rough, Pocket (SOLIDS) - When trying to create the toolpath on this part, the
bottom section of the solid is
ignored. When analyzing the part, if you attempt to create a surface from the top solid face, an
anomaly in the surface is
displayed corresponding to the area that the toolpath has skipped.

Bug 15232 09/28/2000 Medium


Toolpaths, Import NCI - When importing this nci file, the system doesn't prompt to add the tools to
the current library, instead it
asks that you select another library, since we don't have the original library we choose no, and
the NCI isn't imported. The NCI
does backplot and has 2 bull mills in it.

Bug 15332 10/09/2000 Medium


Create, Surface, Draft, To Plane, - The surface is created in the wrong direction. In the attached
file if you choose to Create,
Draft, To Plane, Z Const and choose a value of 2, the surface should proceed in the positive Z
direction, however it goes in the -Z
direction.

Bug 14499 07/13/2000 Medium


Set : screen , configure ,NC settings Select under NCI path : When to prompt for NCI path:
On first operation only
Initialize NCI path to : Last created operation Create toolpath on first operation ask for
NCI path and I am giving path
different than default one. For the second operation saving the NCI file at default path, not at the
path direction selected with the
first operation , which is not right according to the settings should keep all following operations in
the directed folder on first
operation

Bug 14810 08/15/2000 Medium


NC File Location - The Directory defined in Question 90 of the post is not being used initiallly
upon entering a new file. The default
NC directory is used instead.

Bug 15224 09/27/2000 Medium


Cannot recover mc8 file gracefully after filtering operations.
Bug 15333 10/09/2000 Medium
Pocket: Op 2 seems to hang when being regenerated. Tool diameter is 1 and pocket width is 1.
Maybe it cannot create a toolpath,
but it needn't hang.

Bug 15116 09/18/2000 Medium


Create, Next, Letters, Box - Special characters that are included in the set of MC8 files for the
font are not being created. The &,
!, and other characters report errors.
Bug 15075 09/14/2000 Medium
Rename the toolpath group name with an 80 char name and Mill crashes

Bug 15106 09/15/2000 Low


If you have a simple contour and transform it and then in op mgr delete the original operation, it
asks you if you want to delete the
associated transform also. If you say 'no', you end up with a red X'd transform operation. If you
try to regen this, the first time you
get no warning, but it remains red X'd, the second time you regen it asks you 'select geometry
now?'. Saying 'yes' is no different
than saying 'no', it just goes back to op mgr with red X'd transform.

Bug 14741 08/07/2000 Low


There seems to be a problem with the filter when mirroring a surface toolpath. If the create arcs
check box is selected the toolpath
doesn't come out correctly, it almost looks like the arcs aren't coming out as segments but whole
arcs.

Bug 14637 07/26/2000 Low


Toolpath Xform translate: change X steps to 1. It gives proper message and sets it to Between
Points as it should but it resets
Steps to 2 instead of leaving it at 1 and it sets Y Steps to 1 before graying out instead of leaving it
at 2 (since it's not available
anyway)

Bug 14783 08/10/2000 Low


Inputting the 4-Axis or 5-Axis access code when starting Sirius Verify will save out the
sirius4x.acc file but when you try to run
Verify again you are asked for the code again. I 've found that you can still get into Verify without
inputting the code again by just
pressing the Enter key or by clicking the mouse in the graphics area.

Bug 15133 09/19/2000 Low


Toolpaths, Multiaxis, Swarf5Ax - Toolpath is creating a strange move in corners where the radius
of the tool is larger than the
radius of the geometry. Even though "Minimize Corners" is enabled.

Bug 15165 09/21/2000 Low


I have a question about Operation Manager Function.
Re. Lock function of NCI, data can not be output even NCI is Locked when the
geometry referred is modified.
I think this is because X mark is given priority.
Is the LOCK function of NCI is valid ONLY when NCI is modified?
I would like NCI Lock is given priority.

Bug 14103 05/30/2000 Low


Operations Manager, Edit Common Parameters - If you try to set the Rotary Axis switch to On
using Edit Common Parameters it
isn't having an effect. The Operations are not changed. You have to do this manually. It does
work if you do one op at a time

Bug 15228 09/27/2000 Low


When using the box letters you can't get the !,#,$,^,&,(,) symbols in version 8 but you can use
them in version 7.
Bug 15243 09/29/2000 Low
Daily 9/29 - On the T/C plane dialog the work offset has problems.
Bug 15251 09/29/2000 Low
Morph pocket - If you use an entry point to enter outside the part, chaining that point affects the
morphing shape and makes it
basically unusable.

Bug 15263 10/02/2000 Low


Operations Manager, Edit Common Parameters: Select all operations. Edit common parameters
and change Rotary axis to Axis
Substitution, Y axis, Diameter=3.075. OK, OK. Select individual operation's Parameters and the
rotary axis changes are not
reflected.

Bug 15267 10/02/2000 Low


Toolpaths, Circle Tlpths, Thread Mill - The thread mill toolpath will crash Mastercam if the
entry/exit arc clearance is set to a value
larger than the radius of the thread to be cut.
The bug is that Mastercam should warn you not Crash.

Bug 15279 10/03/2000 Low


Operation manager: Trying to edit parameters, geometry, or backplot an operation from another
product (Wire, Router, etc.)
results in 3 or 4 error messages instead of just one. Operation manager should bail after the first
error message instead of trying
to continue.

Bug 15285 10/03/2000 Low


T/C Planes: From the Op Manager, Parameters, T/C planes. Turn on Tool Plane. Work Offset is
set to Auto and does not appear
to be able to be changed. 10/02/00 daily build.

Bug 15293 10/04/2000 Low


Create, Surface, Draft, Set the length to -2.0, To plane=Y, plane =z-const 2.0 Alt-U and "Do it"
again, yields correct surfaces. It
appears that when the length is set in the negative direction even if a positive value is set for the
plane height a negative value is
applied BUT, only the 1st time the function is selected.

Bug 15307 10/05/2000 Low


Toolpath/surface/rough/pocket gouges with cut tolerance of 0.08 but not with cut tolerance of
0.02. Gouge occurs in a move
between regions. Constant overlap pocket cut method is used.

Bug 15319 10/06/2000 Low


Create Point Next menu Small Arcs can't use Backup or ESC to get out
Bug 15342 10/10/2000 Low
Levels Manager - User is requesting that the" Make Main Level Always Visible" option be a
configurable option in screen configure.
They would like it to default to off.

Bug 15227 09/27/2000 Low


Contour: The lead out on the first operation is not included in the toolpath. This happens
randomly to this customer. The first op
does not show the line for the lead out but the second op does. They are posted this way
causing the comp to cancel on the arc
move for the first op. This causes a small gouge in the part.

Req 14996 09/05/2000 Medium


Toolpath, Swarf5ax - With the 4-Axis option enable, I still get 5-Axis moves in the undersized
corners on this part. I know that the
rads should be big enough to fit the tool in, however it would be great is it just worked. I few
strange moves appeared after
changing the number of floor passed in op2 from 3 to 6. Check out the part in verify using a 2.75
diam cylinder along X from -3.0 to
0.0. The third or so pass on the second tool starts to really gouge the corners.

Req 15383 10/13/2000 Low


File, Get - Randy and his coworkers keep their files on Network drives exclusively. When using
File Get the are required to double click the folder to open it and move to the next level. He
would prefer that the OPEN button function the same as double clicking. Choosing Open while a
directory is selected Opens the directory and if an MC8 file is selected, then the Open button will
open the file. The problem they are running into is that users are often moving entire directories
by mistake due to improper double clicking.

Req 14983 09/01/2000 Low


No way to unselect "Make main level always visible" as a default
Req 14623 07/25/2000 Low
add a configuration switch to choose active/inactive for the Levels "Make main level always
visible" which is always active on start
up as is

Lathe:

Bug 15413 10/16/2000 Medium


Using Demo part FaceDrill81 and running Backplot on Operation #3 it's supposed to Rapid into
the larger hole then Drill. But with
Tool Display on you'll notice that the Drill doesn't rapid into the larger hole. Selecting Step twice
will not show the tool moving into
the larger hole it remains stationary then drills all the way through.

Bug 15391 10/13/2000 Medium


Operations Manager - If i try to backplot the last operation by clicking on the NCI file i get an
message error in assoc 262. If i pick
backplot from the dialog box no such message occurs.

Bug 15359 10/11/2000 Medium


In Verify for 8.0, the stock boundaries were defined by Job Setup or, if no boundaries were in Job
Setup, by the NCI file. To match
the 8.0 functionality, the Job Setup radio button in the Initial stock size source section of the
Verify Configuration dialog box should
be the system default.

Bug 15351 10/10/2000 Medium


I set home position for each tool then posted the NCI file but NCI file has the default value not the
value I set. What I have seen is
that after setting the home position for two tools for two rough ops then going back into the
parameter page and noticing that the
home position displayed is the default not the tools. I must click on the tool to get the correct
home position value.

Bug 15299 10/05/2000 Medium


While looking at Rough with a defined Stock boundary, I noticed that it will take 20 seconds
before the Rough parameter dialog
box appears. Then it will take 10 seconds if you select a different Tab. This occurs if you have a
spline entity that you want to have
the Rough toolpath assigned.

Bug 15249 09/29/2000 Medium


This is something I ran into while trying to duplicate a customer's problem where he told me the
COLORS displayed were wrong
after a File -> New. I could not see that problem until I created the sample MC8 for you. When I
created the LABEL the main color
was set to White (15) But MC shows is as GREEN on the screen ? AND the GROUP MEMBER
reference went away when I
created the label (I had selected that line entity at it's mid-point when defining the leader)

Bug 15248 09/29/2000 Medium


Loading a DXF file then File-New then reloading DXF and Analyzing a line will say that the line is
grouped. But selecting Groups
button show that there are no group entities.

Bug 15156 09/20/2000 Medium


Home positions stored with the tool are not being output to the NCI for multiple operations.
Bug 14850 08/21/2000 Medium
Rough: Gouges part in area indicated by red circle.
Bug 15308 10/05/2000 Low
Rough: Last pass does not do the angled retract move.
Bug 15207 09/26/2000 Low
I created a rectangular quick groove toolpath. When the toolpath was done generating, there was
no final move to the home
position shown. But when I backplot the toolpath, this move is shown. Why doesn't it show up
when the toolpath is first
generated?

Req 14927 08/28/2000 Low


When you enter the Chain Manager in Lathe and choose Add chain, you start out in Full chaining
mode. Instead, could it default to
Partial mode? When you are chaining during toolpath creation, you are defaulted to Partial mode
because this is used more often
on lathe parts.

Bug 14832 08/17/2000 Low


Batch: Does not display batch operations on right side list. Using the => button to move selected
operations to the list does not
show them either. Tested on daily (8/17/00).

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'.

Bug 14484 07/12/2000 Medium


In the Chain Manager if you Change Thread/Cut position and then use Step in backplot the new
Thread position will not be used.
But if you use Run in Backplot it will show the new Thread point.

Bug 14512 07/14/2000 Medium


Backplot - There needs to be a way to filter out the Steps in backplot that don't change settings or
show motion. In today's daily
you can hit S a couple of times and the prompt line is blanked.

Bug 14550 07/18/2000 Medium


4axis: doesn't correctly show the user when a wirepath is correct or incorrect (red display in
wirepath even though it backplots
okay)

Bug 14570 07/20/2000 Medium


When wirepath generation fails, whether I hit Yes or No to the dialog question, it always saves the
wirepath
Bug 14611 07/24/2000 Medium
In the Wire Contour Parameters page when you select the -Change NCI- button the 'Select
output NCI file' dialog appears and if
(A:) is your 'Look in:' directory, it will show the directories of C: drive NOT the contents of your (A:)
Floppy drive.

Bug 14752 08/08/2000 Medium


When lead out is set to radius only (lead in is set to line) and wire compensation set to Off for
both computer and control, wirepath
generation fails with the following error: Error location 1 wire compensation not successful.

Bug 14116 05/31/2000 Medium


No Core op has weird graphical display -- arcs/circles going everywhere
Bug 14993 09/01/2000 Medium
No Core using True Spiral gives no Preview if you select a circle. An obround will give a donut
shaped preview. AS the distance
between the two arc sections gets closer the donut gets narrower until it disappears at a full
circle.

Bug 15021 09/07/2000 Medium


Running Backplot with the Display setting 'Fit Toolpath' enabled will show incorrect wirepath.

Bug 15212 09/26/2000 Medium


Backplot No Core has erroneous rapids
Bug 15241 09/29/2000 Medium
4axis direct wirepath just shows one rapid move when created, regened, or in wirepaths. When
you go into backplot from op mgr,
it shows the whole wirepath. Also, seems first step position isn't properly initialized in step mode.

Bug 15274 10/03/2000 Medium


Wire V8.1 Wirepaths/4/axis, select "Cutting Method Reverse" at "SkimCUT", set "3 times CUT",
then create Wire Paths with
Compensation in Control Left". The NCI data outputs incorrect G Code #1013. If it outputs
properly, the compensation code which
is at the line of 1013 should be (the first #1013=41), (second #1013=42), (third #1013=41).

Bug 15344 10/10/2000 Medium


I GOT A WARNING THAT SAID (MESSAGE 7253 IN BACKPLOT WARNING MESSAGES NOT
FOUND) WHEN I WENT TO DO
A BACK PLOT AND WHEN I WENT TO WIREPATH OPERATIONS

Bug 14898 08/24/2000 Medium


Why is there a stop point and information at 0,0 when you backplot run?
Req 15364 10/11/2000 Low
Modify, Break: Stcw pos should probably be STCW pos
Bug 15294 10/04/2000 Low
In chg-at-pt, if you are not close enough to the desired point and get the 'try again' message,
redraw or zoom and you don't get the
points displayed.

Bug 15295 10/04/2000 Low


As soon as you go into backplot, openGL is force on, even if you are not using verify with
backplot and its original state is not
reset when you exit backplot.

Bug 14444 07/07/2000 Low


When I receive the Warning: ' Toolpath generation failed. Do you want to save operation? ', if I
click on No you still have the
operation recorded in the Operations manager.

Bug 14324 06/27/2000 Low


If I set Lead Out to 'Radius Only' I receive an error message reading 'Error Location: 1 Wire
compensation error'. Why get a Wire
Comp error associated to a lead out move?

Bug 15306 10/05/2000 Low


Using the 'Change NCI' in the NC parameters dialog causes a system crash when using the
mouse. The default comes up with
drive A: instead of the NCI path.
Bug 15057 09/12/2000 Medium
Window chaining does not properly pick-up the thread point and the contour associated with that
point.
Bug 15107 09/15/2000 Medium
Verify this Wire 4axis part and it is really ugly -- the straight lines aren't even straight
Bug 15204 09/26/2000 Medium
Curious as to why the backplot works like is does.... Do a backplot on the attached EDM2 file
using STEP mode. Why does it
take until the 7th click on STEP until any wirepath is actually shown on the screen ?
What’s fixed in 8.1 Beta 4 Top

Bugs and Requests addressed in 8.1 Beta 4


Design:

Bug 15676 11/08/2000 High


Create/Surface/Trimmed/FillHoles crashes Mastercam when used on this part
Bug 11284 09/28/1999 High
PLOT: Program aborts when this file is plotted. Sometimes takes a little while. (Illegal operation.)
Bug 15759 11/16/2000 Medium
STEP - If the user inputs the code for the ACC file on the prompt line it creates the ACC file in
MCAM8\Common\Stepdata instead of in MCAM8 like all of the other ACC files.

Bug 15564 10/30/2000 Medium


Xform, Mirror - (Surfaces) - When mirroring the red surface across the line in this file, the
resulting surface is bad when analyzed.

Bug 15387 10/13/2000 Medium


Create, Drafting, Point Dimension - In this file the Cplane is set to 3D however when you choose
Create, Drafting and select one of the dimensions to reposition, the Cplane gets reset to T not
3D. Also when you select one of these dimensions, the dimension disappears and doesn't
reposition when you select a new location.

Bug 15602 11/01/2000 Medium


Point dimensioning: If you use a hotkey (for example C for center) it only works the first time, then
it bounces back to the Dimensioning menu

Bug 15726 11/14/2000 Medium


STEP: Produces no entities. User says AutoCAD and Mechanical Desktop can read the file.
Produced by AutoCAD.
Bug 15746 11/16/2000 Medium
Create, Surface, Trimmed, To Curves - Cannot create a trimmed surface in the front view using
Construction View option for direction of trim. Systems reports "selectec curves do not form a
closed boundary" however they do form a closed boundary. If you use the Normal to Surface
option for direction it does work.

Bug 15568 10/30/2000 Medium


SAT: File conversion gets "Body Fault error - RTTOFP - too few parents" and two get "PK Error
999 - geometry fails to pass checks". (AutoCAD 2000 reads them in without messages. Output to
DWG gives same results when converting the SAT part.)

Doc 15222 09/27/2000 Low


In case it was not already documented, File/Convert/SAT now has additional menu choices for
writing a file and writing a directory. It also (as of last night) has a 'version' choice in the menu -
this controls what SAT Version file is written. (Someone who wants to read our .SAT files may
not have the same version SAT kernel that we have). Also, this same version flag is controlled by
a new combobox in Screen/Config/CADSettings/Solids.

Bug 15553 10/27/2000 Low


CVTOLD: Unable to convert this v3 file. Gives zero length line errors then hangs. (V7 able to
convert file.)
Doc 15138 09/19/2000 Low
A couple of changes to glossary definitions: flat boundary - Change the term to 'flat boundary
surface'. The definition of this term is: A trimmed NURBS surface that is created within the
boundary defined by a closed, flat chain of curves or surface edges. To access the Flat Boundary
function, choose Main Menu, Modify, Trim, Surface, Flat bndy. Base surface - update the
definition to: The untrimmed parent surface of a trimmed surface.

Doc 14968 08/31/2000 Low


A new option "Import unbounded planes (108, form0) as lines" has been added to the
File/Convert/TGES/Read "Masking" dialog. This allows the user to control whether or not he
wants "unbounded" planes to come in as a set of lines depicting its position and orientation. In
V7 we ignored these, and in V8 we always brought them in, causing a few customer complaints
(like bug 14911)

Bug 14814 08/15/2000 Low


Hardcopy, Shaded Y: "Using Hardcopy to print a shaded image to a Cannon BJC330 (B/W)
printer result in a blank page. This happens in V7 and v8. Hardcopy of wire frame is O.K. I had
no problem printing from any other software.."

Bug 15651 11/06/2000 Low


When you run one CHook inside of another, the first CHook loses it's dialogs
Bug 15321 10/09/2000 Low
Create a note in V8.1 and then go back and edit text of that note. You can do that by going
Create, Drafting, click on the note and move the mouse and hit T, make a change to a word in
the note. This note and every dimension you create becomes a box. If you exit Mastercam and
read the file back in then it is ok.

Bug 15425 10/17/2000 Low


SAT: V8.0 from CD converts this SAT file better than v8.1 beta 2. Two solids are created in v8.0.
In v8.1 beta, it gives "PK error code 1 - angle out of range". SAT and both MC8 files included.

Req 14278 06/21/2000 Low


File - Hardcopy - settings / properties, are not being saved during each MCAM session.
Doc 15540 10/26/2000 Low
A new option has been added to Create/Fillet/Chain. It now incorporates the functionality of the
'filchain' C-Hook in that it can,
when a chain has been selected, make fillet arcs on, optionally, clockwise or counter-clockwise
corners. A single menu item has
been added "CW/CCW", and it is a 3-way toggle (CW/CCW/ALL), and the default is ALL.

Bug 15592 10/31/2000 Low


Current Configuration File: Email: "There seems to be a problem in getting Mastercam 8 to use a
new Config file. Get yourself an MC8 with a simple toolpath first. What I did was to go into
Screen, Configure. I made a minor change, like setting the "Max no. of entities to undelete" from
500 to 600. I used Save As to give the config. file a new name. (This next bit is besides the point,
but sometimes it then puts my new file into the "Current config. file" box. Sometimes it doesn't,
and I have to either select it from the drop-down list, or I can't see it at all and have to press the
File button to the right and select it manually) After I have my new file in the "Current config. file"
box I press OK.Then, I press Configure again, and the "Current..." is set back to MILL8M.CFG.
It's not quite as simple as it sounds though. First of all, even though it says MILL8M.CFG, my
"Max no. of entities to undelete" is still set to 600. Secondly, if I change the "Current..." back to
my new config. file, and press OK, and I then try to post out a toolpath from the Operations
Manager, nothing happens. Try it again straight away and it works (I guess that it's using
MILL8M.CFG again) This happens in a customers copy of Mill 8.0 ( who has set up three
seperate config. files and finds that he can't use them), a collegues copy of Mill 8.0 (C:\MCAM8),
my copy of Mill 8.0 (C:\MCAM8) and my copy of Mill 8.1b3 (D:\MCAM81)"

Bug 15706 11/13/2000 Low


File, Get: With bitmap displayed, cannot open a Shortcut file. Gives error message. Able to open
it if bitmap not displayed, just the list of files.

Bug 15708 11/13/2000 Low


File, Get, with bitmap displayed: Try to open a Shortcut file. OK error message. Cursor does not
display on Mastercam area. Windows menu, at bottom of screen shows arrow cursor.Must atrl-
alt-del to end Mastercam.

Bug 15724 11/14/2000 Low


Cannot Modify/Extend this spline. User says Analyzing it with Edit ON will stop Mastercam but I
cannot duplicate it. Tested on 11/11/00 daily.

Bug 15742 11/15/2000 Low


IGES: Doesn't convert all the surfaces. Dealer is in dire need of getting this fixed.
Doc 15466 10/20/2000 Low
I don't know if this really needs to be documented, but File/Convert/DXF/Read now handles
'binary' DXF files. This type of output is an option in AutoCAD and is also the only way our
"Advanced ACAD" translator outputs DXF.

Mill

Bug 15632 11/02/2000 High


Toolpath, Pocket - This part crashes when finish passes are turned on. The circle is .3125
diameter, the tool is .25, the stepover is 75%. If i change the stepover to 10% it works without
crashing. I just shouldn't crash. It doesn't crash in 7.2c.

Bug 15524 10/25/2000 High


Toolpath, Transform - This file created in 8.0 will not regen in 8.1 because the rules for transform
seem to have changed. You used to be able to translate 2.6 and 0 in X and Y with copies of 2 in
X and 0 in Y.

Bug 15764 11/16/2000 High


File, Get - Somewhere between Beta 3 and the daily we lost the ability to see files in Preview
mode. I can switch to Bitmaps and see them if they have been saved. But if i switch to Preview
only the Mill icon is shown. I called this high because everyone is going to report this as a bug in
Beta 4.

Bug 15554 10/27/2000 High


Sim Checking - When using a /e on a Dealer Sim to simulate Entry it only stays as an Entry until
the first time it checks the Sim, then it resets back to the Sim programmed level. Satrt it as
Entry and go to Toolpaths, there are no Surfaces options, then go back to the mani menu and
wait a few minutes.

Bug 15572 10/30/2000 High


please try to regen the toolpath. I test it in v8 and v8.1 beta 3. Both systems hang up at:
Creating tool restriction boundaries at z level 49.027665, cut 23(/222) When I change the cut
tolerance for example to 0.005 it works fine.

Bug 15580 10/30/2000 High


If you try to write OUT an IGES of these 3 (customer) MC8s, You are greeted by Dr. Watson.
(Same result in BETA 3) If you delete ALL drafting - it WILL output an IGES.

Bug 15591 10/31/2000 High


Toolpath, Pocket - In this case in both 8.0 and the daily the tool cuts well below the set depth of -
.01 absolute if the option in finish passes to cut finish passes after all roughing passes is used.
Turn that option off and it only cuts to -.01.

Bug 15607 11/02/2000 High


Toolpath Editor: Crashes when using Del Section. Pick a point then Done.
Bug 15475 10/23/2000 High
Regen then Verify the last operation and sncapi.dll blows up (Beta 3)
Bug 15633 11/03/2000 High
Toolpath, Pocket - When the island is selected no toolpath is produced. It cuts fine when the
island is removed. Even if you change the tool from .75 to .25 it still will not produce the toolpath.

Bug 11343 09/30/1999 High


Run a multi surface toolpath with a negative stock to leave value set. Then use stl verify to view
the results. What you will see is that verify compensates for the negative stock in only the "z"
direction. It should compensate in a direction that is normall to the surface.

Bug 15650 11/06/2000 High


Toolpaths/ Drill/ Manual always defaults to sketch, regardless what is set in Screen/ Configure/
Default point entry mode. It then overwrites Default point entry mode to sketch until you restart
Mastercam

Bug 15669 11/08/2000 High


Custom tool creation loops and CTRL/ ALT / DELETE is the only way out. I selected Profile
Custom with the diameter = 0.0 and can not get out of Warning loop.

Bug 14858 08/22/2000 High


Under Screen, Configure, CAD settings, Drafting settings, Delete. I cannot set an option other
than Delete all associated drafting entitiies as my default

Bug 14781 08/10/2000 High


In Sirius Verify Standard mode running this Rotary 4-axis operation then Stopping it about quarter
of the way thru then selecting Verify Config button will cause Illegal Page Fault in smodapi.dll.
This only happens in the Daily V8.1 not the released version.

Bug 15751 11/16/2000 High


Toolpaths, Surface, Finish, Parallel - In this file the toolpath generates properly with a cut
tolerance of 0.01 (part is metric). If you change the tolerance to 0.02 Mastercam Crashes.

Bug 15200 09/26/2000 High


When you xform translate move drafting labels the labels are some how duplicated.

Bug 15461 10/19/2000 Medium


Get Memory Table Message when editing a label
Bug 15465 10/20/2000 Medium
Toolpaths, Contour - In this file the contour is not correct unless the linearaization tolerance is set
very fine (.001 vs .01). Andreas thinks this is a bug.

Bug 15471 10/23/2000 Medium


File, Converters, Parasolid, Read (.PAR file) - When attempting to read this Solid Edge .par file,
Mastercam reports "Cannot find parasolid

Bug 14794 08/11/2000 Medium


Backplot this Curve 5ax toolpath with Interpolate and the results are really bad
Bug 14588 07/21/2000 Medium
Toolpaths, Pocket, Constant Overlap Spiral - In this file only one region of the pocket is being
machined. If you create a pocket toolpath with a 2mm flat endmill and use either Constant
Overlap or zig-zag, the system will only see the left portion of the pocket. If you change to the
other cutting methods it will see both regions of the pocket.

Bug 15432 10/17/2000 Medium


Toolpath, Pocket - This toolpath violates the boundary at the top of both sections of the "M".
Bug 15473 10/23/2000 Medium
Toolpaths, Surface, Finish, Contour - This toolpath will not machine to the bottom of the part.
Bug 14422 07/06/2000 Medium
Toolpaths, Multi Axis, Swarf5ax - In this file, one end has a strange angle applied to it. The
toolpath seems incorrect
Bug 13515 03/30/2000 Medium
Sirius - If you verify the second op the tool definition is incorrect. It looks like a flat end mill but it
is a drill, so the bottom of the cut
is wrong.

Bug 15486 10/23/2000 Medium


In the matter of the surface/finish/contour cut regen does nothing. The stepdown is erratic with
levels missed, on the two smaller gaps it can't make up it's mind if it wants to do both walls at
once. Thats why I sent the nci file generated in version 7 totally (un?)acceptable.

Bug 15489 10/23/2000 Medium


File, converters, SAT, Read - This .sat file from Mechanical Desktop doesn't read into V8.1 beta 3
properly. An error that "too few parents..." is displayed and only the edge curves are read in. V8
release does read it properly as does Mechanical Desktop.2

Bug 12923 02/10/2000 Medium


Verify - If you look at this in true Solids turbo it is bad, in tool simulation it is ok. Are tool changes
happening in Turbo correctly?
Bug 15335 10/09/2000 Medium
A)Toolpaths, Surface, Rough, Pocket - The Ramp is failing if you chose to use a Bull Mill but
works correctly if you use a flat endmill with the same diameter. B) After anayzing the problem it
seems that the Tool definition of the Bull Mill is the issue. When looking at the defintion the Tool
Length is very small compared to the diameter and in V8.1 I get a "Corner Radius too short for
Length" error. The values for the tool definition should work unless there is a rule that the length
can be no shorter than 1/2 the diameter or similar.

Bug 15435 10/18/2000 Medium


Toolpath, Transform, Mirror - The toolpath is getting messed up when mirroring.
Bug 10778 07/07/1999 Medium
Verify, STL Compare - No matter what color settings or values I use the compare always shows
the same results. I change the color map and it does not change the results.

Bug 15419 10/17/2000 Medium


Verify - If in 8.1 we continue to require an ACC code for 4 and 5 axis verification we should
change the name of the files from sirius5x and sirius 4x to verify5 and verify4 acc. Sirius is dead.

Bug 15402 10/16/2000 Medium


Toolpath, Contour, Comp in Control - If you load this file and Regen the toolpath the multiple
depth cuts appear as multiple XY cuts instead. Depending on how questions 159 and 160 are
set you get different results. Backplotting shows it correctly, only the initial toolpath after creation
or regen shoiws it wrong.

Bug 15360 10/11/2000 Medium


Toolpaths, Surface, Rough, Pocket - This toolpath causes 2 significant gouges when using the
collision check tool. Checked in release and 8.1

Bug 15503 10/24/2000 Medium


The post dialog configuration is not set. Setting the post dialog settings in screen/configure,
exiting and restarting does not restore the setting.

Bug 14924 08/28/2000 Medium


Toolpath/pocket/zigzag fails to produce nci motion.
Bug 15151 09/20/2000 Medium
Toolpaths, Pocket, Roll Cutter Around Corners - In this file, when set to Roll Around No corners
(NONE), the toolpath fails to generate. If you select SHARP the toolpath is created. This worked
with NONE in version 7.

Bug 15334 10/09/2000 Medium


Toolpaths, 2D Swept - This toolpath starts out on the inside of the geometry and finishes on the
outside. Shouldn't the toolpath be consistently on one side or the other?

Bug 15300 10/05/2000 Medium


I uncovered a spline tolerance bug while testing Lathe. Attached is a toolpath made in Mill on a
spline. Note the large toolpath error in the circled area. The linearization tolerance is .0004. If I
change it to .0003, the problem goes away.

Bug 15256 10/02/2000 Medium


Toolpaths, Surface, Project - In this file a Circle in View 9 is to be projected to the surface as a
toolpath, but the result is not correct. When backplotted while viewing View9 you will see that the
toolpath is in the wrong position.

Bug 15266 10/02/2000 Medium


Toolpaths, Surface, Finish, Contour - In this file the tool is showing a strange move (Blue Line)
when backplotting. If I set Ramp length to under 1.0 and use "check transition motion for gouge"
in Gap settings, this problem does not happen.

Bug 10876 07/21/1999 Medium


In Sirius Verify - One important thing still missing is gouge checking of the holder.
Bug 15455 10/19/2000 Medium
Toolpaths, Contour, (Retract) - This file has a Toolplane of 4 set and a Cplane of 4 as well. All
values for Retract, Clearance, Depth, etc are set to absolute values. The resulting toolpath is
using incremental heights instead. If you turn the T/C planes off, the toolpath moves absolute.

Bug 15709 11/13/2000 Medium


DWG Convert: If you look at the file I attached you will see that when you convert it with the MC
8.1 beta 2 version. It creates lines in the form of a wagon wheel on the drawing. I get the same
error in version 8 but not in version 7, cadkey or SolidWorks.

Bug 15600 11/01/2000 Medium


if you look under the third parameter tab of the second pocket you will see it is a remachine
operation and the finishing is turned off, but it still errors out on regen and it is outputting a G41
cutter comp command when you post it out. There should not be any cutter comp command
output while the finishing has been turned off...

Bug 15603 11/01/2000 Medium


Toolpath editor allocates memory but never frees it.
Bug 15605 11/02/2000 Medium
Can't xform offset a line that was converted to a spline
Bug 15509 10/24/2000 Medium
You are not able to reposition Point dimensions, once selected the dimension will disappear.
Click again but dimension stays in original location.

Bug 15646 11/06/2000 Medium


Operation Mgr: The mouse/cursor will disappear if you hit Esc while dragging an operation
Bug 15472 10/23/2000 Medium
Toolpaths, MultiAxis (Graphical Editor) - When editting a 5 axis toolpath using the Graphical
Editor to change feedrate, the change doesn't get outputted to the NCI file.

Bug 15596 10/31/2000 Medium


Toolpath, Contour, Remachine - In this case the exit move is supposed to be perpendicular, but it
looks to be tangent. If you make a copy of this operation and Regen it the results totally baffle
me.

Bug 15707 11/13/2000 Medium


Toolpath, Contour, Ramp - When using Ramp the exit move of just a line perpendicular to the
contour is missing.
Bug 15641 11/06/2000 Medium
Toolpaths, CircleMill - In the attached file the first operation has the Top of Stock set at -.53
absolute and the the Depth set to -.415 Incremental and the toolpath has a single depth cut. The
second toolpath has the the Depth set to -.945 (-.53 + -.415) Absolute and the toolpath has two
depth cuts. The absolute and incremental setting are the only differences in the toolpaths, you
would expect the result to have 2 passes regardless of the absolute incremental setting.

Req 15713 11/13/2000 Medium


Files, Converters, IGES, Read - User is reporting that this file is coming in with Untrimmed
surfaces, while it comes in fine with "other" products. I checked it in Mechanical desktop and got
similar results, Mastercam had 3 more untrimmed surfaces than Autodesk.

Bug 15768 11/16/2000 Medium


Analyze Area does not give any results. I tried both profiles with no results.
Bug 15741 11/15/2000 Medium
Toolpaths, Face - The depth cuts don't seem to be used when the Top of Stock is set to
Incremental. In this file the depth is 0.6392 absolute and the Top of stock is 0.5 incremental. I
would expect 5 depth cuts. IF the top of Stock is set to (0.6392+.5) absolute, it works correctly.

Bug 15750 11/16/2000 Medium


NcUtils, Def. Tools, Face Mill - When defining a Face Mill, the parameter for Angle cannot be 90
degrees however, face mills do come in 90 degree forms..
Bug 15761 11/16/2000 Medium
File Get, - On my windows 2000 machine, the images will not appear in "Preview" mode, but they
do appear in "Bitmap" Mode. My MCBitmap is dated 9/29/00 and MCListCtl is dated 10/03/00.

Bug 15763 11/16/2000 Medium


When I offset/copy a spline and then delete it it leaves a copy of it blanked and colored the
screen color. When I then save and re-open the file I get the error message about entities in the
backgroung color. As a weird side effect if I then proceed by mouse clicking on the screen rather
than hitting enter to acknowledge the error message and then try to import a NCI into the
operations manager it does not come in fully.

Bug 15683 11/09/2000 Medium


File, Convert, Adv ACAD (DWG): When converted, the summary says "Part of your drawing was
in Paper Space and is now on level 758395703 which may not be visible." Note the level
number it refers to. Actually the entities are on level 255.

Bug 15520 10/25/2000 Medium


Toolpaths, Contour - This contour is made up of two lines and a 3D Spline but when you create a
contour toolpath on it, Mastercam considers it a 2D contour.

Bug 15595 10/31/2000 Medium


Toolpath, Contour, Remachine - When using comp in control with a perpendicular lead in/out
move the system reports an arc is being created that is smaller than the tool, but there should be
no arcs at all because they are at 0.

Bug 15547 10/27/2000 Medium


Attached are 2 files. The customer needs to define in v8 the same tool as defined in v7.
Somehow, somebody decided to limit the tool taper angel to be 0.1 to 89.9. In v7 it was 0 to 90.
BTW, this is a standard Iscar tool F90A D 50-22-M.

Bug 15521 10/25/2000 Medium


V8 B3 : When I backplot the peck drill operation, I get the message "Warning - zero line length".
This only happens if show tool is yes. The first rapid move looks incorrect.

Bug 15681 11/09/2000 Medium


File, Convert, Adv ACAD (DWG): Trying to convert this file, it gives an application error in 8.1 B3
and yesterday's Daily but converts fine in 8.0

Bug 15025 09/08/2000 Low


Mill8.txt - If you choose under Opertaion Manager Display Options "Tool plane numbers" The list
will show View # Should the text line 37. "View #" be 37. "Tool plane #" ?

Bug 15010 09/06/2000 Low


Fix 1st surface interaction for Surface edge. Fix 'select start position'.
Bug 15725 11/14/2000 Low
Toolpath/surface/contour/restmill isn't correct for "use prev op's regen file" setting.
Doc 14910 08/25/2000 Low
For version 8.1, surface machining operation recut files (.rec) have been renamed to regen files
(.rgn). Also, the screen/config "delete regen files" dialog has been reworded.

Doc 14878 08/23/2000 Low


STEP and SAT translators - make it clear that unless Solids in enabled, the Solids option is not
available. See the Parasolid converter documentation for a good example.
Bug 15487 10/23/2000 Low
Blanking: When Unblanking entities that are already a "result", the entities don't clear from the
screen they just sit there so you can't tell if you've already unblanked them. Blanking first, in older
versions you do not have to clear colours, which means you could use that icon that I so dearly
desire,screen change levels and change the result to another level. eg the main level you've
preset. At the moment you can't change the level of blanked surfaces without unblanking them. If
you have the icon you can go blank / unblank then pick the screen change levels icon and
change the blanked item to your preset main level.

Bug 14691 08/01/2000 Low


Point dimension: If you try to create a point dimension by using one of the letters from the point
selection menu, you do not get a dimension.

Bug 15173 09/22/2000 Low


Changing the length of the tool in a curve 5-axis toolpath and regen'ing it causes the toolpath to
behave differently (and incorrectly). Note: The part is one of the v8 sample parts.

Bug 14641 07/27/2000 Low


Tool definition: Can not input 90 or 0 degree taper angle for face mill. Told dealer to use flat
endmill, but he said it can be done in V7. Verified in Daily build 7-27

Bug 15752 11/16/2000 Low


Toolpath/Transform/Mirror: the reverse toolpath checkbox has no effect. The goal is to mirror the
operation with reversal to maintain climb cut.

Doc 14462 07/11/2000 Low


Macros: From the topic "About manually editing macros," click on the link "Mastercam function
call" This topic mentions MILL7.TXT. It should be replaced with MILL8.TXT. (CEC) Also, should
this topic have a heading?

Bug 15491 10/23/2000 Low


Curve 5 axis: toolpath violates part geometry at seam when applying radial offset (3,4 and 5 axis
output). Tool goes to start position

Bug 14335 06/28/2000 Low


curve 5 axis: 2d Contour projected on a single surface generates a move through the part at the
surface seam.
Bug 14079 05/24/2000 Low
Verify, TurboTrueSolid, zoom, accurate zoom isn't so accurate.

Bug 13940 05/08/2000 Low


In toolpath_next menu_transform if you specify number of steps 1 and include original it doesn't
transform. If you say number of steps 2 it will, but in rotate you can specify number of steps 1
and include original it works. So there is a little inconsistency.

Bug 15494 10/23/2000 Low


Toolpath/surface/leftover zigzag fails to yield toolpath with appmc8.dll (version 10/17)
Bug 13429 03/24/2000 Low
Toolpath/pocket & contour, Xform/Offset ctour - compensation fails on this part with a small gap
when a (larger) tool is used and when roll is set to NONE.

Bug 14769 08/10/2000 Low


2D contour comp in control only: in v7 it displayed the tool as offset so the edge touched the
geometry. In v8, the center of the tool displays directly over the geometry. However, it backplots
the same in both.
Bug 15305 10/05/2000 Low
5 Axis: "Go into the toolpath parameters, and, one at a time, set the tool origins' X, Y, or Z to
some arbitrary value (I used +10). Regen the toolpath each time. Looks very strange, don't you
agree? This has been found by a customer, and we suggested moving the geometry, so that the
job datum is at Mastercams' 0,0,0. Although that's a preferable way of working anyway which
gets him out of a hole, he plans to use multiple datums in upcoming work, so we need to get to
the bottom of this problem as soon as possible."

Bug 15459 10/19/2000 Low


Pocket: Island facing does not overlap correctly. I talked this over with Pat and it seems that the
finish pass spacing is being offset in the wrong direction. In the corners, it seems to offset in the
wrong direction twice.

Bug 15601 11/01/2000 Low


T/C plane dialog: Work offset keeps showing -1 to 32767 when it's set to Auto and you try to edit
the origin.
Bug 15414 10/16/2000 Low
Verify - Using an STL model for stock is giving very poor results. When i first load in the STL
model it is speckled with black areas, when it begins cutting i don't see any material, just black
space. The surface i used to create the STL file is on level 2, create the STL file at .001.

Bug 15409 10/16/2000 Low


Operations Manager - When operations are present and the "+" key is depressed on the key
board on the operation that is highlighted it expands the operation like it should, but if you
continue hitting the "+" key it looks as if the system is duplicating the toolpath. Upon reload of
the file it hasn't duplicated the operations.

Bug 15585 10/31/2000 Low


Leftover - Zig/Zag/One Way cut method - two problems (1) fails to find a valid leftover zone dur
to a 'File Read error' (2) fails to properly clip the data to Z depth limits when this option is turned
on.

Bug 15373 10/12/2000 Low


Revolved toolpath: Backplot shows "illegal arc at X-0.6243, Y-0.6243" on first arc move.
Bug 15464 10/19/2000 Low
Verify: does not display the toolholder
Bug 15625 11/02/2000 Low
Verify: Does not show tapered end mill when that is the tool selected. Shows a flat end mill.
(Tested on 11/2/00 daily.)

Req 15063 09/13/2000 Low


It would be useful to use an STL for stock definition for surface toolpaths (forgings and castings)
or to use an STL in place of a NCI pre-rough for the Highfeed option. I think we've request this
before, but not sure where you stand on it. Gibbs promotes some sort of STL stock functionality.

Bug 15313 10/05/2000 Low


Toolplane dialog - work offset is "Auto" but if you change X,Y, or Z and try to leave, complains
that work offset must be -1 - 32767.

Bug 15481 10/23/2000 Low


Job Setup, Material - When in job setup and you select Material and right click and choose Doc
File, after typing the name an error message appears "Message 11 in (Matldef) not found. The
Doc file is created however.
Bug 15562 10/30/2000 Low
Operations Manager - This file takes over 2 minutes to display the Operations Manager. The file
is 9 meg and has 250 operations in 3 groups. User believs this is too long. Part is Metric

Bug 15468 10/20/2000 Low


Verify in mill - Cylindrical stock definition is not available with Truesolid in Turbo mode. If I have
my stock set to box, enable Truesolid, enable Turbo, and then set my stock to Cylinder, it allows
me to do that and later (when I say ok to configuration) it gives me a message that says "Failure:
In stock definition". At this point, I have no idea what the problem is, other than it is related to
stock definition. It should either check for Truesolid, Turbo, Cylindrical conditions when any of
those three are changed, or give a more detailed warning message describing the problem
better.

Bug 15560 10/27/2000 Low


New file save dialog doesn't switch to the specified directory if you type in the directory path and
hit enter, it saves the file with the directory name.

Bug 15555 10/27/2000 Low


Toolpath, Wireframe, Swept 3D: Help says you can create it with 1 across and 1 along contour
but it you choose just that, you get "Swept 3D toolpaths must contain 3 contours". V7 allowed it.

Bug 15704 11/10/2000 Low


Toolpath, Pocket - Using a stepover of %5 creates only the finish pass. Set it to 5.1% and it
works.
Bug 15548 10/27/2000 Low
Screen, Configure, NC Settings - Beta 3 -The option to "Include all solids/surfaces in surface
operatio" has the n missing from operation. It should be shortened.

Bug 15250 09/29/2000 Low


Pocket: The islands in the pocket are being ignored when the tool size increases.
Bug 15230 09/27/2000 Low
Screen, Config, NC Settings: "Include all solids/surfaces in surface operatio" is missing the end of
"operations"

Bug 15638 11/03/2000 Low


Pocket island facing faces islands before removing material around island 10-31 Beta3

Lathe

Bug 15731 11/15/2000 High


Verify True Solids or Standard mode, both will lock up 'Not Respond' in program manager, the
Display coordinates shows Z$$$$$$$$$$ at 45% done in all modes.

Bug 15701 11/10/2000 High


Verify, True Solids, Operation 10, ID Groove causes Illegal Op in smodapi.dll. Hint: Groove has
Chamfer and if you turn off chamfer it will verify.

Bug 15355 10/11/2000 High


Remaining Stock is nice feature. But there are some small things. Have look into the attached file.
I chained the red geometry and made a rough operation (no plunge) Then i copied the operation.
I took a new tool and use the parameter: Allow plunge and Use Stock for Outer Boundary Look
at the result: -no overlap cut -the first lead in crashes the contour -stock boundary error

Bug 15515 10/25/2000 High


The canned cycles only work if we let mastercam set the entry/exit vectors. If we use point -
chain - point toolpath with entry/exit disabled, the post goes into a "not responding" condition and
locks up the system. Have to use CTRL+ALT+DEL and end task, which bounces us out of
mastercam. It is very important to several of our customers to be able to control the EXACT
POINT for rapid in and return before rapid home. (Tested with B3 MPLFAN.PST and still locks
up when posting NC) Tom

Bug 15577 10/30/2000 Medium


Regenerating Operation #9 causes Tool Clearance Violation, so choose to 'Select new position' ,
the wait state icon remains instead of crosshair icon and any new position selected will get the
same violation message.

Bug 14037 05/18/2000 Medium


If you use a non-Quick toolpath and activate the Tool Filter, the tools are still filtered in a
subsequent Quick toolpath, without the ability to enable all tools. All tools should be enabled in
the Quick toolpaths by default.

Bug 14356 06/29/2000 Medium


I can not seem to get "Tool Renumber" to work on any file in lathe 8.0. I have tried different
formats for starting number and increment 1,1 or 101,101 or 0101, 0202 and I can not seem to
get anything to renumber.

Bug 15101 09/15/2000 Medium


Verify: With gouge check on, using Standard stops at gouges. Using True Solid does not stop at
gouges. Which is correct?
Bug 10838 07/15/1999 Medium
Sirius Verify True Solids with Stop on Gouge enabled will not pause on each gouge. Using
Standard mode Stop on Gouge will work.

Bug 15288 10/03/2000 Medium


If you go into Op #1 Lathe Face parameters dialog but don't change any parameter and just
select OK you'll cause ALL operations to become dirty.

Bug 15452 10/18/2000 Medium


When "Equal Steps" is turned off the last pass is skipped, it has nothing to do with the step
amount.
Bug 15534 10/26/2000 Medium
The attached groove toolpath I use only the finishing cut with auto compensation in control. But i
think i get the wrong coordinates. Look in the nci it is better with g41 for the first cut and g42 for
the second cut.

Bug 15781 11/17/2000 Medium


It looks like the "top of stock" is always absolute even when it's set to incremental. This happens
in regular contour as well as c-axis contour.

Bug 15588 10/31/2000 Medium


Lathe, Entry - If you start Lathe up with a /e so it is Entry only you can still get Mill toolpaths. If i
change my Sim from a Dealer Sim to an industrial Entry Sim you can't get into Mill toolpaths.

Bug 15628 11/02/2000 Medium


In lathe 8.1b3 - Selecting a named view (using the "Coordinates" button on parameter page),
does not bring in the work offset that is saved with that view.

Bug 15702 11/10/2000 Medium


Verify, True Solids, of Mill Turn operation will take the last tool used and verify incorrectly instead
of skipping operation.
Bug 15712 11/13/2000 Medium
Xform, ScaleXYZ, Select to move in Z axis direction but no change. Cplane is +DZ but must
change to 3D cplane and scale X axis to get wanted results. Ver 7.2 C Xform in Z works correctly
don't have to change Cplane.

Bug 14025 05/17/2000 Low


In Sirius Verify True solids this lathe rough toolpath will show a couple red gouge warnings in the
middle of the toolpath even though the toolpath is correct.

Bug 15693 11/10/2000 Low


Verify, True solid: Sample file Lathe1.mc8 crashes on the ID groove operation.
Bug 15694 11/10/2000 Low
Verify, True solid: I can't verify in three quarter view the first time but I can the second time.
Bug 15695 11/10/2000 Low
Verify, True Solid: Verify crashes when switching to three quarter view on sample file lathe6.mc8.
Bug 15517 10/25/2000 Low
After using Filter in Op Man, I selected all Ops to be Regened and when the Lathe Finish Face
and Groove regened the tool displayed like Static was enabled. I checked the Tool Display and
Run - Animated - Endpoints were enabled not Static.

Wire

Bug 15576 10/30/2000 High


Nocore crashed when I tried to create a nocore wirepath using L shaped filleted geometry and
default settings for everything. Tested on WIn98, WinME, WinNT and it crashed every time as
soon as I hit OK from the parameters.

Bug 15673 11/08/2000 Medium


Try programming to wire cut the green circles using window, CCW. For some reason I can't
figure out why the bottom right three circles get cut CW. This of course scraps these holes since
our offset is left.

Bug 15571 10/30/2000 Medium


Backplot not showing UV arcs sometimes
Bug 15504 10/24/2000 Medium
Can't get no core to cut this part without slugs.
Bug 15485 10/23/2000 Medium
Why is it that when you do tab cuts it automatically cuts wire before it starts cuts on tabs? Is
there anyway to keep this from happening? This is still a bug, we should eliminate the extra cut
and thread before the tab cut but we're not.

Bug 15484 10/23/2000 Medium


I'm going to have to rename 'tab height' to something else, maybe 'thread point height'? In v7 it
worked the same and was called tab height, but it was only enabled if you didn't give me a thread
point, then it was enabled to allow the program to determine the
thread point as a distance from the start of contour. But dealers complained that customers were
confused as to how to enable 'tab height' and they wanted it to always be enabled and if the user
wanted to use it, they'd enter something other than zero. But now its getting confused with 'max
lead out length' which is what he wants to use limit the length of his lead out (I can see how
you might think this would be tab height - that's why I've got to come up with a better name)
Bug 12062 12/13/1999 Medium
Windowing the holes causes the start of the large hole to be in the small hole to the left, even
though you have points created for the start.

Bug 15674 11/08/2000 Medium


No Core doesn't follow the medial axis between the start point and the first point in the pocket,
leading to drop-outs.
Bug 14511 07/14/2000 Medium
Wirepath, Contour - There is not a None option in the Lead in/out tab
Bug 15729 11/15/2000 Low
Trying to convert a directory full of v7 wtl power libraries, multiple file select seems to limit you to
only converting 20 files at a time, we have directories with over 100 wtl files.

Bug 14658 07/27/2000 Low


In the Backplot Wire Display Parameters dialog, the 'Erase toolpath in Repaint' check box will not
stay checked.

Mastercam Network Licensing Top

Introduction to Mastercam® Network Licensing with the NetHASP


October 18, 2000

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:

1. A full-time network administrator must be available. The network administrator


must be able to recover from a network crash in a reasonable amount of time,
since network licensing depends on a stable network.
2. The network administrator must be able to configure the network as required by
this document and the nethasp.txt document.
3. The network administrator must be proficient with a text editor.
4. The network administrator must be able to understand and edit command line
parameters.
5. The network administrator needs to learn enough about Mastercam to understand
which licenses are checked out when each of the Mastercam products starts up.
6. The network administrator needs to learn the Mastercam nhasp80.exe utility.
7. The network administrator must agree to install Mastercam on every computer on
which the customer wants to run Mastercam. Although this may seem blindingly
obvious, the point is that attempting to run Mastercam from a common directory
on a network drive will not work.
8. It is recommended that the NetHASP device be kept in a physically safe place. It
should be obvious that all Mastercam users on the network are vulnerable to the
loss of the NetHASP device.

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.

Setting up the NetHASP server for Windows 95 / 98 / NT / 2000:

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.

Setting up Mastercam for the NetHASP:

1. Install Mastercam version 8.1.


2. Run the latest version of hinstall.exe.
3. Install the appropriate network protocol such as TCP/IP if not already installed.
4. Run the nhasp80.exe utility and set the SIM type to NetHASP.
5. Copy the nethasp.ini file to the main Mastercam directory (e.g., c:\mcam8). Edit
nethasp.ini to use the appropriate network protocol and to limit searching to the
computer(s) that are being used as the NetHASP server(s). If this step is omitted,
when Mastercam executes and checks for network licenses, it may take an
unreasonably long time (30 seconds or more) for Mastercam to find a NetHASP
server. It may take an especially long time in the event that all licenses have been
checked out by other Mastercam users on that network. Configuring nethasp.ini to
look for the NetHASP server at a specific address will drastically reduce this
delay.
6. Create or edit shortcuts for running Mastercam with command line switches as
described below.
Command line switches:

The options that will be enabled for each Mastercam product are specified with command
line switches. The switches are:

Switch: Products: Allowed in:

/E Entry Mill and Lathe


/1 Level 1 Mill and Lathe
/2 Level 2 Mill
/3 Level 3 Mill
/C5 Curve5ax / Drill5ax add-on from Mill level 1 or level 2
/ME Mill entry Lathe
/M1 Mill level 1 Lathe
/M2 Mill level 2 Lathe
/M3 Mill level 3 Lathe
/S Solids Mill, Lathe, Wire, Design

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

causes Mastercam to request a Mill Entry license when it starts up.

The following command line:

C:\mcam8\mill8.exe /3 /S

requests two licenses: Mill level 3 and Solids.

The following command line:

C:\mcam8\lathe8.exe /1 /M1 /S

requests three licenses: Lathe level 1, mill level 1 and Solids.

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:

“c:\mastercam version 8\mill8.exe” /3

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:

Error checking out a [product name] license. No licenses


have been purchased for this product.

This message is obvious. Contact your dealer and purchase the necessary options.

Active NetHASP server not found.

Indicates that the NetHASP license manager is not running.

All available licenses are in use.

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:

The SIM has become disconnected. Mastercam will


automatically shut down. You will get one chance to save your file.

This message should be taken very seriously.

Monitoring NetHASP users:

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.

Product list (untitled)

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

Only available when Active licenses is reporting licenses.

User type

This read-only field displays the user type: Industrial, Educational, etc.

Serial number

This read-only field displays the NetHASP serial number.

Start date, End Date

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 = Enabled; ; Use the TCP/IP protocol

[NH_TCPIP]

NH_SERVER_ADDR = 192.114.176.65, 192.114.176.3;


; IP addresses of all the NetHASP
; License Managers you want to search.
; Unlimited addresses are possible.
;
; Possible address format examples:
; IP address: 192.114.176.65
; Local Hostname: ftp.aladdin.co.il
NH_TCPIP_METHOD = TCP; ; Send a TCP packet or UDP packet
; Default: UDP
NH_USE_BROADCAST = Disabled; ; Use TCPI/IP Broadcast mechanism.
; Default: Enabled

Bundling and limitations of the NetHASP-20 and NetHASP-50

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.

Normally, either a NetHASP-20 or NetHASP-50 will be supplied to the customer. The


NetHASP-20 allows up to 20 stations for each product to be used. The NetHASP-50
allows up to 50 stations for each product to be used. A total of 160 stations (simultaneous
users) can be authorized with a NetHASP-20: 20 Mill Entry, 20 Mill level 1, 20 Mill
level 2, 20 Mill level 3, 20 Lathe Entry, 20 Lathe level 1, 20 Wire and 20 Design stations.
A maximum of 400 stations can be authorized with a NetHASP-50. There is no way to
limit the total number stations except by limiting the number of stations for each product.

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

Lathe V8.1 Enhancements / Interface changes

1. The stock boundary geometry can be utilized with rough, finish,


groove, face, drill.

a) Rough, Quick Rough

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.

Use stock for outer boundary check box

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.

End To Adjust Radio Buttons


These buttons allow you to select which end of the chained
contour is to be adjusted when pressing other buttons. If one of
the radio buttons is disabled, that end of the chained contour
cannot be adjusted, as it lies on or outside the stock boundary.

This button resets the lines used to extend the chained


contour back to the state they were in prior to selecting
the Adjust Stock… button then re-computes the area of
remaining stock.

This button re-computes the lines used to extend the


chained contour to the stock boundary using the system
default settings then re-computes the area of remaining
stock.

This button makes the line from the start/end of the


chained contour perpendicular to the cut direction
(one of OD/ID/Face/Back) for the operation.

This button makes the line from the start/end of the


chained contour parallel to the cut direction (one of
OD/ID/Face/Back) for the operation.

This button makes the line from the start/end of the


chained contour tangent to the first/last entity in
the chained contour. If the tangent entity in the
contour is a line, the contour line is extended, rather than a
tangent line being added. The tangent lines are created/extended
such that the tool will be away from the stock by approximately
the entry/exit clearance at the start/end of each cut.
Auto-hide check box
Selecting this check box hides the button bar when the cursor
moves outside of the button bar, enabling you to view more of the
graphics screen.

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.

c) Finish, Quick Finish

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.

Extend contour to stock check box

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.

Adjust Contour Ends… button


This button functions exactly like the Adjust Stock… button for
roughing with one addition. There is also a check box which
controls whether or not the lead out line from the end of the
chain to the stock boundary is actually added to chained contour.
This box should be checked if you want to finish to the end of
the last entity in the chain. (ex. finishing the OD of a
cylinder/cone) It should generally not be checked when finishing
up to a shoulder.

d) Groove, Quick Groove

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.

Use stock for outer boundary check box


If this box is checked the features previously described will be
enabled. If it is not checked, a line, which is perpendicular to
the groove angle and connects the groove corners, will be used as
the outer boundary. If a chain is used to define the groove
outer boundary, this check box (and the related functionality)
will be disabled.

Extend groove to stock radio buttons


These buttons allow you to select whether to extend the groove
walls parallel to the groove angle, or tangent to the groove
walls. They are only enabled if the Use stock for outer boundary
check box is checked.

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:

You are no longer immediately prompted to define the corners of the


rectangle when creating a facing toolpath. On the Face parameters
page there is a new set of radio buttons, which allow you to either
select the rectangle corners as in Lathe 8.0, or use the stock
boundary and have the software compute the start and end points for
each cut. If you select the Use stock radio button, you must only
supply the Z coordinate of the face of the part using the Finish Z
edit box. When you select the Use stock option, and the stock
changes, regenerating the facing operation will automatically update
the start / end points of each facing pass.

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.

2. Vertical turret lathes are now supported.

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:

VTL programming is selected by selecting the Spindle / Turret button


in Job Setup, then selecting the Vertical turret lathe radio button.

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.

Note: The dimensioned bitmaps for operation specific parameters (ex.


Rough cut depth, overlap amount, stock to leave, etc.) have NOT been
rotated to VTL view.

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.

5. The Plunge Parameters dialog for Rough/finish operations has new


options to control the tool’s plunge capability independently in
both the X and Z directions. In Lathe v8.0, both X and Z plunging
were controlled with the same selection. Both were either enabled
or disabled.

6. Zigzag threading has been added to the NC code format drop-down list
on the Thread cut parameters page.

7. Home position can be set to System default, User defined or From


tool using a new drop-down list on the Tool parameters page and
Common Parameters dialog. This drop-down list replaces the check box
in Lathe v8.0. The Home Pos… button has been replaced with a
Define… button. This button is only active if User defined is the
current method of defining the home position.

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)

No other parameters (especially those in the Lathe Tool Setup


dialog) control how a custom tool will be displayed/used. It is
advantageous to set all of the Lathe Tool Setup parameters, even for
a custom tool, as the information is stored in the database and
output to the NCI file.
Note: These tool definition rules are no different than those for
Lathe v7.x or Lathe v8.0.

Custom Tool interface changes include the following:


• The tool orientation icons have been updated to more closely
reflect how the software interprets tool orientation. This
should eliminate the (erroneous) selection of orientation 8 for
boring bars in the top turret which occurs because the Lathe 8.0
icon for orientation 8 looks like a boring bar.
• The radio buttons and graphics indicating whether the current
tool is used for OD/ID/Face/Back operations have been removed due
to the confusion they created by changing the tool orientation in
the turret when the user altered the tool type.

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.

13. When Verify is selected when backplotting an operation other than


the first one, the stock from the previous operation, rather than
initially defined stock will be used.

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.

17. Lathe toolpath C-Hooks are supported. (Extent of 3rd party


developer access to be determined)

18. There is a C-Hook, Threadc, for threading on a contour.

Lathe 81 Demo Files Top

Lathe 8.1 Demo Files

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 #1 - finish up to a shoulder, with an undercut


In this case, adding the lead-out line to the contour would be disastrous, as it would either
lead to the tool dragging up the face of the part, or chopping the shoulder right off. Edit
the operation and change the 'Add lead-out to contour' setting to see what happens.

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:

1. Edit the operation


2. Select Adjust Contour Ends… and un-check ‘Add lead-out to contour’.
3. Save the changes to the operation and regenerate it.

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.

Notes on this feature:


If the groove is OD or ID, the groove rough Z stock amount will be added to the
groove width. If the groove is a face or back groove, the groove rough X stock
amount will be added. If the groove is at any other angle, stock amounts will not be
added to the groove width.

VTL81.mc8

This file demonstrates the new VTL specific interface.

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.

Demonstrating the new custom tool and tool clearance interface


1. Click on NC Utils -> Define Tools->Current and create a new tool.
2. Select the Custom button.
3. Note the new tool orientation bitmaps. Leave the geometry and turret in
orientation 1
4. Click on the Tool Geometry button and select O1ODTOOL.MC8.
5. Select the insert corner radius and tool center from this parameter page.
6. Click on the Tool Type tab. Note that the OD/ID/Face/Back radio buttons and
icons are not there. They have been removed.
7. Click on the Parameters tab and click on the Tool Clearance Button. Note the
new tool clearance dialog.
8. Cancel out, switch back to the geometry tab and change the turret orientation
to 5, then return to the Tool Clearance dialog, as per Step 7. Note that the
icon has changed to reflect the new tool orientation.
9. Try out different options in the dialog.

Top

S-ar putea să vă placă și