I've never seen/used one.

I would think the intended application was thinner material to save a tool change (like a drill tap does), not for any accuracy concerns. IMHO

If you are concerned about center location:

On a mill spot drill, then reamer size drill ~.015" undersize, then circular interpolate about .25" deep to .001" undersize then ream.

On a lathe spot drill, then reamer size drill ~.015" undersize, then bore about .25 deep to .001" undersize, then ream, or just bore the whole thing depending how deep.

HTH

Allan

Looks like you are using the recieve file option.

The file it is creating is on your desktop called T.NC

I normally use the recieve option; this option opens the file in the editor.

You are only recieving 3 lines of code?

The default in Cimco is to stop recieving after not receving for 5 seconds.

I would double check that timeout setting.

Allan

BTW welcome to the forum.

Here is the word I recieved from CNC software when I asked about this:

 

 

I doubled checked with our programmer in charge of the security and he verified that nothing has changed between versions. One thing that may be tripping them up is some OS combinations appear to work via remote desktop while others do not. For example in my tests here:

 

 

 

∙ XP 32 remote into Win 7 64 - I was not able to run X5 or X6 off of a local HASP.∙ Win 7 64 remote into Win 7 64 - I was not able to run X5 and X6 off of a local HASP∙ Win 7 64 remote into XP 32 - I was able to run X5 and X6 off of a local HASP.

 

In either case remote desktop is not something we official support.

In your post processor there is a post block:

pl_retract #Retract tool based on next tool gcode, lathe (see ptoolend)
cc_pos$ = zero
if home_type = one,
[
xh$ = vequ(start_xh)
pmap_home #Get home position, xabs
ps_inc_calc #Set inc.
pbld, n$, psccomp, e$
if css_actv$ & css_end_rpm & not(lathe_stop | synch_flg | n1_gcode = 1003 | n1_posttype <> posttype$ | n1_spindle_no <> spindle_no$),
[
pspindle
prpm
]
pcan1, pbld, n$, *sgcode, pfxout, pfyout, pfzout, [if drop_offset, *toolno], strcantext, e$
if lathe_stop | synch_flg | n1_gcode = 1003 | n1_posttype <> posttype$ | n1_spindle_no <> spindle_no$,
[
pbld, n$, pnullstop, e$
]
]
else,
[
#Retract to reference return
pbld, n$, `sgcode, psccomp, e$
if home_type = m_one & drop_offset, pbld, n$, *toolno, e$
if css_actv$ & css_end_rpm & not(lathe_stop | synch_flg | n1_gcode = 1003 | n1_posttype <> posttype$ | n1_spindle_no <> spindle_no$),
[
pspindle
prpm
]
pcan1, pbld, n$, *sg28ref, "U0.", [if y_axis_mch, "V0."], "W0.", strcantext, e$
if lathe_stop | synch_flg | n1_gcode = 1003 | n1_posttype <> posttype$ | n1_spindle_no <> spindle_no$,
[
pbld, n$, pnullstop, e$
]
if home_type > m_one & drop_offset, pbld, n$, *toolno, e$
]

The home_type variable controls if G28 U0. W0. or if the values in the machine def define the home position.

Important point the values in the machine def are world co-ordinates so Z on the lathe is X on the home position and X on the lathe is Y in the home position setting (as a radius value)

The first setcion is retracting when X and Z values are used (home_type = 1)

The second is for retracting when G28 U0. W0. is used (home_type = any_thing_but_1)

Switching where the pfzout come out or the "W0." arround will affect the output

Example:

pl_retract #Retract tool based on next tool gcode, lathe (see ptoolend)
cc_pos$ = zero
if home_type = one,
[
xh$ = vequ(start_xh)
pmap_home #Get home position, xabs
ps_inc_calc #Set inc.
pbld, n$, psccomp, e$
if css_actv$ & css_end_rpm & not(lathe_stop | synch_flg | n1_gcode = 1003 | n1_posttype <> posttype$ | n1_spindle_no <> spindle_no$),
[
pspindle
prpm
]
pcan1, pbld, n$, *sgcode, pfxout, pfyout, e$
pcan1, pbld, n$, pfzout, [if drop_offset, *toolno], strcantext, e$
if lathe_stop | synch_flg | n1_gcode = 1003 | n1_posttype <> posttype$ | n1_spindle_no <> spindle_no$,
[
pbld, n$, pnullstop, e$
]
]
else,
[
#Retract to reference return
pbld, n$, `sgcode, psccomp, e$
if home_type = m_one & drop_offset, pbld, n$, *toolno, e$
if css_actv$ & css_end_rpm & not(lathe_stop | synch_flg | n1_gcode = 1003 | n1_posttype <> posttype$ | n1_spindle_no <> spindle_no$),
[
pspindle
prpm
]
pcan1, pbld, n$, *sg28ref, "U0.", [if y_axis_mch, "V0."], e$
pcan1, pbld, n$, "W0.", strcantext, e$
if lathe_stop | synch_flg | n1_gcode = 1003 | n1_posttype <> posttype$ | n1_spindle_no <> spindle_no$,
[
pbld, n$, pnullstop, e$
]
if home_type > m_one & drop_offset, pbld, n$, *toolno, e$
]

The approach is a similar edit in the ltlchg postblock.

Look for this line:

pcan1, pbld, n$, *sgcode, pfxout, pyout, pfzout, pscool, strcantext, e$

Allan

I programmed it manually and this is some of the code that worked (cut geometry correctly/no arc error alarms):

"Correctly" would be open to interpertation, your code looks like this in a backplot:

Hardly matches your geometry in Mastercam, looks like 4 line segments.

There is a chook called arc3d it will attempt to filter for helixes, but with the file you have there is no way a helix will fit to an arc drawn in the side view rotated 22.5 degrees in the top view, no way ever.

That is a .134" dia hole 8 inches deep with a .006" tolerance

And there are 11 of them..oh my.

Best to sub the job out to someone with a gundrill IMHO.

Can you even buy a .134 drill 8" long?

Your Red arc is parallel to the Y axis that is why you are able to filter for an arc in YZ.

The Blue arc is not parallel to any axis and will never produce an arc with Mastercams arc filter.

This type of arc could be cut but only on a control that would allow you to define the arc plane like a Siemens 840, then you would also require a 3rd party filter like Metacut.

BTW:

Your cut parameters are a little strange as well, stock to leave is set to minus half of the tool; why not just turn cutter compensation off?

Allan

I have had no issues with the Nvidia GTX cards, best to get one that has a 192 bit memory bus like a 1.5Gb or 3Gb version of the GTX

Allan

Your paint example is the same as create spline!

Set up sheet uses active reports, the post has no access to those files, so not possible, sorry.

Allan

If multi line and or spline will not work for you... forget about X+ it is just multi line.

Create line multi?

Create spline?

The X+ that was mentioned allows you to create lines with the visulation of the tool size.

Allan

There is a project manager option in the file tab of Mastercam.

This will allow you to do what you are asking...open your .MCX-6 file and the run the project manager set the NC files option and when you post it will go there.

Allan

Disable openGL in the system configuration....that will allow your arrows to work.

Would 'xform_op_id$' work for you?

Exactly...the X Y co-ordinates will be the same...the only diffrence will be that with wear there will be a G41 or G42

The intent is that you will have a small offset in your dia offset table..

The code would be Identical....except for the inclusion of the G41 or G42.

Check the edit key..if it is off..loading a program will only compare it to one in memory...not actually load it.

Allan

The W is incremental of Z the U is incremntal of X.

B? not sure sometimes a bar feed axis, in your case looks like a programmable tail stock.

The G71 is od turning roughing G72 is face.

Allan

I need a lower profile system than the Jergens zero point. These have to be surface mounted to my tombstone and I only have about an inch to work with for thickness.

Here is what I am referring to.

 

Are the gripping plungers in this unit that act on the pull studs hydraulically actuated, or mechanically?

According to their website http://www.lang-technovation.com/en/artikel/gruppen/51207.quick-point-0-point-clamping.html.

It is 27mm thick and is "manual clamping"...read mechanical.

Allan

I'm not a Solidworks guru.

What I see most often used is part configurations in the Solidworks files.

"We use solidworks, but sometimes suppressing features blows out others, and showing positive stock amounts for rough parts can be time consuming"

I'm assuming that you are talking part configurations here...I dont think it should be that difficult...IMHO the 6k would be better spent on some Solidworks training.

The line that says insert.tbl not found is concerning.

This indicates to me that the shared data folder has been changed manually and points to a location that does not contain the basic files that Mastercam needs. example operation defaults, cnc_machines, material lib ect...

Create curve slice?

The issue is most likely something hard coded in your chook, or it could be the space in the "Program Files" causing the issue.

Usually the fix in dos commands is to include the path in quotations.

As an example c:\Program Files\Mcamx6\chooks should be "c:\Program Files\Mcamx6\chooks"

HTH

Allan

Is it alarm #28?

For Fanuc 16i

Check parameter 8485 bit 2. If it is zero helical interpolation is disabled in hpcc mode. Change it to a 1 to enable it.

HTH

Allan

From the Fanuc Manual:

NOTE

1 G00, auxiliary functions, subprogram call (M98, M198), and macro

call M and T codes can be specified in the HPCC mode only when

bit 1 of parameter MSU No. 8403 is 1. If these codes are specified

when MSU is not 1, an alarm is issued.

(Alarm No.5012 for G00 and alarm No.9 for auxiliary functions and

subprogram calls)

2 To specify the following functions in HPCC mode, the following

parameters are required. Specifying any of the following functions

without setting the corresponding parameter causes an alarm.

Helical interpolation : Parameter G02 (No.8485*)

(Alarm to be issued: No.28)

Involute interpolation : Parameter INV (No. 8485)

(Alarm to be issued: No.10)

Scaling, coordinate rotation : Parameter G51 (No. 8485)

(Alarm to be issued: No.10)

Canned cycle, rigid tapping : Parameter G81 (No.8485)

(Alarm to be issued: No.5000)