What version of the setup sheet are you using - Milll.set?

I tested this out and it seems that you are quite right. I'll send this in to CNC Software's QC department. [This message has been edited by Dave Thomson (edited 08-02-2000).]

Sorry to hear about the gouge Gord. Did Metacut View show the problem once you knew exactly where to look? Using a containment boundary and recognizing that it is a "Tool center boundary" is really the easiest and most reliable way to handle this situation. The tool center boundary *never* works like 2D Pocket. The toolpath is always contained to the tool center. I believe this is the standard for surface work in CAM packages. Imagine having to offset curves on a core or boss just to get the tool to move to the edge of a piece when using a containment boundary. I typically create edge curves on the surfaces (unless my own wireframe was used to create the surfaces and is still there). I set the Z depth above the part and use the squash.dll C-Hook to create flat, easily chainable geometry for use as a tool center boundary.

In V8, if you successfully updated your post from earlier versions using the uptxt8.dll C-Hook, the line should have been added. If you are still using V7, you will have to go to Screen/Configure/NC Settings and enable 'Write toolpath parameters to the NCI file'. You'll have to Redo/Regen your toolpaths after making this change. [This message has been edited by Dave Thomson (edited 07-28-2000).]

Q: The plunge feedrate and the stock left on my V8 .set style HTML Setup Sheets read out 0. Any help or fixes? A: This relates to parameters that are stored (or not stored - as in your case) in the NCI file, or external .ops file. Whether or not these parameters are stored is entiredly based on settings in your own post. Change this line in your post to 'y': 1502. Write operation information to binary file (.ops)? y You'll have to change this line in your post, change your post (to refresh the settings), and Regen your toolpath before you can successfully run the Setup Sheet.

The In-House Solutions ColourSurf C-Hook has been updated for V8. (It's called ColourSurf - not ColorSurf - because we're Canadian, eh?) Mastercam V8's new AutoHighlight feature makes it easy to distinguish between adjacent surfaces of the same colour. ColourSurf varies surface colours in an array to a create a patchwork effect. This was certainly helpful in previous versions of Mastercam. If you used ColourSurf in V7 and would like to keep using it in V8, here's the download link: http://www.emastercam.com/tools/chooks/col...colrsurf_v8.exe [This message has been edited by Dave Thomson (edited 07-28-2000).]

I should mention that post help is available in a file named Mp.hlp. This can be launched from Mastercam V8 using a C-Hook called posthelp.dll. Both are post-release files available from the Add-ons files on the eMastercam.com Patches page - http://www.emastercam.com/info/patches/v8/index.html [This message has been edited by Dave Thomson (edited 08-15-2000).]

The variables are as follows: 1 Drill parameter 1 (drl_prm1). 2 Drill parameter 2 (drl_prm2). 3 Drill parameter 3 (drl_prm3). 4 Drill parameter 4 (drl_prm4). 5 Drill parameter 5 (drl_prm5). 6 Drill parameter 6 (drl_prm6). 7 Drill parameter 7 (drl_prm7). 8 Drill parameter 8 (drl_prm8). 9 Drill parameter 9 (drl_prm9). 10 Drill parameter 10(drl_prm10). To use these in the post, you would have to: -edit the post's .txt file to make the dialog box descriptions meaningful -format the variable for output -add the variable to the appropriate output line in the post

Based on an email from pds, I've learned that he is trying to machine multiple identical parts using multiple WCS values. I've recommended my Multiple Work Offset Post found in the Posts area of the eMastercam.com web site. The post efficiently programs multiple identical parts using subprograms and incrementing Work Coordinate System values (G54, G55, G56, etc.). Program a part once, and specify the number of required repetitions under Misc Values.

Unfortunately this is a great example of a fairly ambiguous post. Perhaps we can all learn from it. First of all, the Topic 'CAM' could be improved upon - say to 'Setup Sheet Problems'. Here are some questions that would really need to be answered before anyone could provide some for of feedback to Paresh: -What version of Mastercam are you running? -If you are using V8, which of the 2 two Setup sheet styles are you using? -If you are using the .set Post-style Setup sheet, is it 'out-of-the-box', the HTML product on this site, or customized? -What is the nature of the problem you are facing? Did you run out of paper at the printer? -What file size are we talking about when you say 'large'? -You have not stated a question. What is your question exactly? To me, this sounds like something you should send in to your reseller, or to CNC Software along with files to support your claims. If you want to upload your files to an FTP site, you can also paste a link into your post so that the Members here can investigate your problems for you. If you have found a bug, it would need to be repeated by your reseller and sent in to CNC Software, where it would again be tested for repeatability. Sending in your file is essential for this process. [This message has been edited by Dave Thomson (edited 07-24-2000).]

The way to set your work coordinate system (WCS) depends on your post. Before V7, the WCS was typically set using Misc Values, Misc Integer 1 in particular. With many newer V7/V8 posts, you select the Tool parameters tab 'T/C plane...' button and set the Work offset value.

CNC Software has a post for the ProtoTRAK LX2 on their BBS named Mpl-LX2. Ask your reseller to download it for you.

Solids were first released in V7.2, so V7.1 Demo wouldn't work unless you converted to surfaces. I just got my hands on V7.2 Demo. This would work for you as a viewer, without converting to an *.x_t Parasolid file. Contact your reseller to obtain a CD. The executable alone is almost 7 MB. -- from http://www.solid-edge.com "Solid Edge Origin is a FREE, limited-function version of our complete Solid Edge software. It includes 3D modeling of basic parts, a complete 2D drafting system, import and export of 2D CAD data, and demonstrations and tutorials to help you get up and running in record time." [This message has been edited by Dave Thomson (edited 07-20-2000).]

Mastercam Demo has been used in the past as a viewer due to the quality of the included translators. The only copy of Demo I have is V7.1, which does not have the Parasolid converter in the menu. V8 Demo, when it's released may be an answer for you. I installed Solid Edge SmartView from an Origin CD, and was able to view *.x_t Parasolid files written out from Mastercam V8. It looks like my verion of SmartView supports Parasolid V11, while Mastercam V8 writes out V11.1 files by default. Although this did not cause any problems in my test files, you can always change the output version of Mastercam's Parasolid files - say to V11 in this case. Solid Edge Origin also reads in Parasolid files to the best of my knowledge. [This message has been edited by Dave Thomson (edited 07-20-2000).]

A couple of quick points here: 1. Make sure that your surface toolpath "Cut tolerance" is tighter (smaller number) than your "Filter Tolerance". The "scratch lines" you mention point towards a tolerance issue. 2. Ensure that your machine can hold the feedrates that you have selected for the toolpath. Feedrate problems won't tend to produce the "scratch lines" you mention, but will produce oversized and/or undersized areas. The V8 help documentation for the High Feed product lists an arc feedrate test method: -------------------------------------------- Machine a circle inside a block of expendable material such as wood or foam. Use a low feed rate to ensure accuracy. Machine the same circle repeatedly at higher feed rates until you can hear the tool gouging the material. The gouging noise indicates that the machine’s servo lag is out of range due to excessive force, caused indirectly by an excessive feed rate. This test should give you a good idea of the highest feed rate that can be used at the circle’s radius without resulting in excessive servo lag. --------------------------------------------

The notes from the V7.2c version of the optional STEP translator list that the product supports the AP203 and AP214 protocols. [This message has been edited by Dave Thomson (edited 07-17-2000).]

[Alt +] Add entities to your current [Alt E] Hide selections [Alt -] Remove entities from your current [Alt E] Hide selections [Ctrl E] Toggles through Expand/Collapse options in the Operations Manager [This message has been edited by Dave Thomson (edited 06-22-2000).]

In the ptap postblock, the frplunge variable is usually used to output the tapping feedrate. This variable is used in other cycles, so you should set up another variable to output the tapping feedrate, and format it with a decimal place format statement: #in the format statement section fs 15 0.5 #Decimal, absolute, 5 place #in the format assignment section fmt F 15 frtap # Plunge feedrate #in the ptap postblock frtap = frplunge n, *drillref, *sgdrill, pdrlxyrot, *depthout, *refout, *frtap ->This is example of the steps you need to take. The actual code here is specific to another post, and will most likely not apply to you own post.

Solid Edge and SolidWorks files can be read into Mastercam V8 directly through the Parasolid converter. Use the drop down box to select the appropriate file type: [This message has been edited by Dave Thomson (edited 06-16-2000).]

Please research the Create-Point-Srf project function. Select "To file : A" for creating an APT file with XYZIJK points and vectors. [sample] GOTO/1.69049,-4.48550,1.04682,-0.22230,-0.51538,0.82763 GOTO/1.01596,-3.55527,1.12327,-0.30941,-0.10728,0.94486 GOTO/0.46846,-1.30488,0.76654,0.18875,0.11956,0.97472 GOTO/0.75575,-0.63332,0.54519,0.71234,0.01175,0.70174 GOTO/1.08080,-2.17059,0.72134,0.49324,0.60557,0.62451 GOTO/2.54652,-3.74617,1.43513,-0.17463,-0.02994,0.98418 You can always use Excel to massage your data into the correct file format.

An example of adding a G13 circle pocket cycle to a post can be found in the Haas post in our Educational Post Archive: http://www.emastercam.com/posts/v7/haas/haasvf.zip

You should research the High Feed C-Hook in V7/V8 to see if it meets your requirements. The file Hfapp.doc (or Hfapp_v8.doc) is helpful. In general, High Feed optimizes feed rates based on a constant volume calculation. Settings for Cornering Acceleration will also adjust feed rates on arcs and at sharp corners, thereby reducing servo lag error. Two more limited and tedious methods, for the record: 1. The Change at Point menu provides a method of modifying feeds on contour toolpaths. 2. In V8, the Graphical Toolpath Editor allows editing of feeds at individual lines in the toolpath. [This message has been edited by Dave Thomson (edited 06-05-2000).]

$20 in the mail Ambassador...

Using Toolplanes (Tplane) in Mastercam, you can lock in a tool vector for 5-Axis positional work. This toolplane can be set a variety of ways, including Normal to an existing line.

[Repost from old Mastercam Canada forum] Date: 03 May 1999 Time: 20:54:31 Remote User: simtech Message After doing extensive work with point cloud data obtained from mechanical probing and from laser scanning, there doesn't seem to be an easy solution. I've worked with Catia's Cloud to Geometry module which is nothing less than Imageware's Surfacer product and a tough job to get the edges of surfaces right. There is a company in Quebec City that produces a software for treating point cloud data that is worth to be looked at: InnovMetric Logiciels inc. at www.innovmetric.com They use bezier curves to create triangular patches from cloud data, generating very fast visualisation capabilities. The big question is Tolerance: you can fit a surface through millions of point data, but what deviation is acceptable and what is not! Almost a To Be or Not To Be kinda question! Simtech