It looks like the issue may be with value of opcode$ or "comp_type".

With pocket, cutter comp is not on until the finish cut. This may be giving you unexpected value for comp_type.

There are probably many ways to do this, but the 2 methods that come to mind are

(1) subout$

(2) using buffers

I never got my head around using buffers, but with subout$ , you can direct the output to a 2nd file, and then merge it back in at eof$ using mergesub$ command.

Thanks for the help. I am able to get the job done using the field in the Control Definition.

I still do not understand why setting the value for "eob$" in the PST file does not give the same results.

Thanks for the tip about replacing the e$. There is also an option in the control def, but I am wanting to set this in the post file, but am not getting the results I would expect.

Can eob$ be set in the post file?

@ pprep, I have eob$ = 36

Expecting $ at end of each line, but no change. Also tried at pheader with same results.

The negative X value is most likely caused be the WCS location and not by the machine or post files.

Are all the other XY values correct?

Thanks for the info. Looks like SAE is the only option.

Parker has some very good info on their site for identify post type, but I have not found anything yet for inspection. I think it is available from sae.org, but it is very hard to tell what you are purchasing from them. They do not appear to give any preview of what you are buying. Look like they are geared up for large companies, and not into selling specific spec.

I would have thought these specs were published / open standards.

Where would a good source be for the specs for SAE ports.

In particular, I am looking for SAE AS5202D

The cad files are excellent, but I am needing something with tolerances that can be used for inspection.

I am looking at the sae.org website, but it is very unclear what you are purchasing.

Yes. Create a single variable to capture the 1st tool. This will be much less work than setting up buffer.

http://www.dmscncrouters.com

The "Slice" option may be what you are looking for.

If you click through the warning, I expect it to post code that is good.

I think this is caused by using window chain, and has been resolved with most current update.

Settings->configure

Look on start/exit page and change default editor to cimco.

If this corrects the problem, then the error is with the installation of mastercam editor.

Colin,

Your comments are well received, and appreciated.

In regard to changes to control def, my suggestions are:

1. Chance for only single page. (No need for prompt)

2. Remove file and path names from both machine and control files. Require that all 3 files simply be same name and located in same folder. Users can move them to any location, and rename without need to edit and link the 3 files back together.

I would be interested to know how many users maintain control definitions that have multiple pages.

I understand the attraction of a GUI interface to the posts, but we need to be careful that its implementation does not take away from stability.

 

 

Why not just set the Control Definition Default values, and never have a setting be wrong again?

Updates, moving files to different locations / computers.

It is my experience that the settings in the control file are easily lost.

Maybe I am the only one with this problem.

Tired of loosing your settings in the control def?

With the pprep post block, you can make certain that the settings are always correct.

pprep$ # overide setting from control def

usecandrill$ = 1 # Use canned cycle for drill

usecanpeck$ = 1 # Use canned cycle for Peck

usecanchip$ = 1 # Use canned cycle for Chip Break

arctype$ = 2 #Arc center 1=abs, 2=St-Ctr, 3=Ctr-St, 4=unsigned inc.

breakarcs$ = 0 #Break arcs, 0 = no, 1 = quadrants, 2 = 180deg. max arcs

arcoutput$ = 0 #0 = IJK, 1 = R no sign, 2 = R signed neg. over 180

do_full_arc$ = 0 #Allow full circle output? 0=no, 1=yes

helix_arc$ = 2 #Support helix arc output, 0=no, 1=all planes, 2=XY plane only

omitseq$ = yes$ #Omit sequence no.

bldnxtool$ = 1

Use the settings on your misc page to force rotaries to reverse.

Below is link to what I was thinking could be the problem.

The other issue that will cause this error is reading a swx file that is from version newer than your mastercam.

X6 = 2012

X6mu3 = 2013

http://www.emastercam.com/board/index.php?showtopic=61483&st=0&p=689510&hl=+cannot%20+find%20+parasolid&fromsearch=1entry689510

http://www.emastercam.com/board/index.php?showtopic=60219&hl=%2Berror+%2Bopening+%2Binsert.tbl

This leads to a good discussion

Cannot find Parasolid data in SolidWorks file" error.

Do a search on that string.

It is a common error and an easy repair

I expect x6 is compatible with six 2010

They are sample files with the install. Test mcam by reading sample file. If it reads them, then the install is good

Pfr is the post block for your feed output.

Keep in mind that forcing it to output dos not change it's value. It will simply repeat on every line.

Consider an enhancement where the NC file name would come from the group name, and not be tied to individual operations.

I understand all the current options for starting the process. What I am suggesting is a foolproof system where all operations in a group would only post to a single file.

The error indicates that the machine definition is bad/corrupt .

Delete it and do repair on install, or request a copy from your reseller.

Logic can be added to the post so that the correct "D" value is output.

This allows you to post to dissimilar machines, without modifying any tool settings.

Below is some examples.

Setting d_offset to 30 would output all "D" values as T + 30.

h_offset : 0 # Length offset method

# 0 = H value is always same as Tool number

# 1 = H value as set in Mastercam tool parameter (from NCI file)

d_offset : 0 # 0 = D value is always same as Tool number

# 1 = D value as set in Mastercam tool parameter (from NCI file)

# > 1 = D value is Tool number plus value of d_offset variable

p_tlngno # output tool length offset

if h_offset = 0, *h_num, !tlngno$

else, *tlngno$

p_tloffno # output tool dia offset

if d_offset > 1, d_num = t$ + d_offset

else, d_num = t$

if d_offset = 1, d_num = tloffno$ #set from NCI

d_num, !tloffno$