Upgrade from x2 to x6 mu2

[drafting3]

comparing some gcode from x6 to x2, i come up with the following differences:

 

 

X2 Code:

 

 

G0Z.25

M5

G49Z0.

G91G28Z0.M9

G28Y0.

M01

 

 

 

X6 code:

 

 

G0Z.25

M5

G49Z0.

G91G28Z0.M9

M01

 

 

So, I'm missing a G28Y0., but do I need it? Doesn't G28 return everything to Machine Zero (x, y, and z)?

 

I thought the coordinate supplied after G28 was just a "through point" on it's way back to machine x0, y0, z0.

[PeterM]

G28 only returns the axis, or axis's called home.

[drafting3]

just used MDI to confirm. I do need a G28Y0. call before any tool changes, and at end of program.

 

 

awesome... now to figure out why this line is being excluded in X6...

[drafting3]

Looks like I only have one error left to run down. Gcode being produced matches previous version, so it must not be that critical.

 

 

 

01 Oct 2012 03:47:48 PM - <2> - PST LINE (915) - The formula/boolean failed (general message)

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(134) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(6090) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(6274) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(7602) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(7948) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(9062) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(9598) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(10366) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(11260) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(12784) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(13066) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(14350) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(16704) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(18592) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(21342) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(22368) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(25048) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(31004) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(31188) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(32516) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(32862) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(33976) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(34512) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(35280) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(36174) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(37698) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(37980) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(39264) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(41618) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(43506) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(46256) - The math calculation/formula has an error

01 Oct 2012 03:47:48 PM - <2> - RUN TIME - PST(915), NCI(47282) - The math calculation/formula has an error

 

 

**************************Post File**********************************

 

 

 

 

# --------------------------------------------------------------------------

# Motion output components

# --------------------------------------------------------------------------

pbld #Canned text - block delete

if bld, '/'

 

pfbld #Force - block delete

"/"

 

pccdia #Cutter Compensation

#Force Dxx#

if prv_cc_pos$ <> cc_pos$ & cc_pos$, prv_tloffno$ = c9k

sccomp

if cc_pos$, tloffno$

 

pfxout #Force X axis output

if absinc$ = zero, *xabs, !xinc

else, *xinc, !xabs

 

pxout #X output

if absinc$ = zero, xabs, !xinc

else, xinc, !xabs

 

pfyout #Force Y axis output

if absinc$ = zero, *yabs, !yinc

else, *yinc, !yabs

 

pyout #Y output

if absinc$ = zero, yabs, !yinc

else, yinc, !yabs

 

pfzout #Force Z axis output

if absinc$ = zero, *zabs, !zinc

else, *zinc, !zabs

 

pzout #Z output

if absinc$ = zero, zabs, !zinc

else, zinc, !zabs

 

pfcout #Force C axis output

#if index = zero & rot_on_x,

#[

#if absinc = zero, *cabs, !cinc

#else, *cinc, !cabs

#]

 

pcout #C axis output

#if index = zero & rot_on_x,

#[

#if absinc = zero, cabs, !cinc

#else, cinc, !cabs

#]

 

pindex #Index output

if index & rot_on_x,

[

pbld, n$, `sindx_mc, indx_out, e$

!cabs, !cinc

]

 

parc #Select the arc output

if arcoutput$ = zero,

[

#Arc output for IJK

i$, j$, k$

]

else,

[

#Arc output for R

if abs(sweep$)<=180 | arcoutput$=two, result ? (<------------------------------------------------------------------------------------------------- LINE 915)

#CNC<<ORIGINAL>> if abs(sweep$)<=180 | arcoutput$=two, result = nwadrs(srrad, arcrad$)

#CNC<<MSG-ERROR(919)>> The formula/boolean does not terminate properly, The formula/boolean failed (general message), , Label has not been defined[*80]

else, result = nwadrs(srminus, arcrad$)

*arcrad$

]

 

ppos_cax_lin #Position the rotary axis before move - rapid

if index, pindex

else,

[

if fmtrnd(prv_cabs) <> fmtrnd(cabs) & rot_on_x,

[

sav_gcode = gcode$

gcode$ = zero

pbld, n$, sgcode, pcout, e$

!cia

ps_cinc_calc

gcode$ = sav_gcode

]

]

[Guest]

I am guessing this nwadrs(srrad, arcrad$)

 

should be

 

nwadrs(srad, arcrad$)

 

 

if abs(sweep$)<=180 | arcoutput$=two, result = nwadrs(srad, arcrad$)

[Guest CNC Apps Guy 1]

The messages/alarms you get now are a result of CNC tightening up. I liken it to what FANUC did to their 0i-TD controls. You can run a program (with a specific error in geometry) in a TC control that you cannot run in a TD control. Looking at the definiteion of the groove back on the TC, users were getting away with fudging it. Now you cannot fudge.

 

So, Mastercam used to not be so picky. Those errors have always been there, it just did not care before. Now it cares and we hear about it.

 

I've got an old V7 era post that's been updated, and updated, and updated, and updated, and updated, and updated, and updated, and updated. I still use from time (maybe once or twice per year at most) to time and it's loaded with errors. It gives me good code so I'm not really inclined to do anything about it.

 

:shrug:

[drafting3]

I am guessing this nwadrs(srrad, arcrad$)

 

should be

 

nwadrs(srad, arcrad$)

 

 

if abs(sweep$)<=180 | arcoutput$=two, result = nwadrs(srad, arcrad$)

 

 

thanks mr. paris.

 

if abs(sweep$)<=180 | arcoutput$=two, result ?

 

should have been

 

if abs(sweep$)<=180 | arcoutput$=two, result = nwadrs(srad, arcrad$)

 

 

not sure where the "?" came from, but it's fixed now.

 

No more errors.

 

Gcode matches previously acceptable gcode.

 

 

Thank you everyone for your help!