MpMaster Question

[gcode]

I'm working up a simple VMC post, starting with the latest MpMaster..

I'm getting an R output in every line

 

G00 G17 G90 G54 X.75 Y-3.9265 S600 M03

G43 H1 Z2. T2

M08

G94

G81 Z-.2021 R.1 F3.

X4.125 Y-3.875 R.1

X14.5 Y-2.125 R.1

Y-6.375 R.1

G80

M09

 

Is there a simple way to get rid of the extra R's

[Tim Johnson]

Does the format look correct?

 

From an updated v9 post;

code:

---

fmt  R  2   refht_a     #Reference height

fmt R 2 refht_i #Reference height

---

[Guest]

gcode,

 

what does the prdrlout section look like?

[gcode]

fmt Z 2 initht_i #Initial height

fmt R 2 refht_a #Reference height

fmt R 2 refht_i #Reference height

 

 

prdrlout #R drill position

if absinc$ = zero, refht_a, !refht_i

else, refht_i, !refht_a

 

Doesn't the ! mean "only output in R has changed??"

[Guest]

dumb question is there * in front of the prdrlout in the ptap section

[gcode]

no

 

prdrlout #R drill position

if absinc$ = zero, refht_a, !refht_i

else, refht_i, !refht_a

 

pdrlxy #Drill XY coordinates

if force_dpts, pfxout, pfyout

else, pxout, pyout

 

pdrill$ #Canned Drill Cycle

pdrlcommonb

pcan1, pbld, n$, *sgdrlref, *sgdrill, pdrlxy, pfzout, pcout, pindexdrl,

prdrlout, [if dwell$, *dwell$], *feed, strcantext, e$

pcom_movea

 

ppeck$ #Canned Peck Drill Cycle

pdrlcommonb

pcan1, pbld, n$, *sgdrlref, *sgdrill, pdrlxy, pfzout, pcout, pindexdrl,

prdrlout, *peck1$, [if haas, *peck2$, *peckclr$], *feed, strcantext, e$

pcom_movea

 

pchpbrk$ #Canned Chip Break Cycle

pdrlcommonb

pcan1, pbld, n$, *sgdrlref, *sgdrill, pdrlxy, pfzout, pcout, pindexdrl,

prdrlout, *peck1$, *feed, strcantext, e$

pcom_movea

 

ptap$ #Canned Tap Cycle

pdrlcommonb

#RH/LH based on spindle direction

if rigid_tap, pbld, n$, *sm29, *speed, e$ #Rigid Tapping

if use_pitch = 0,

[

pcan1, pbld, n$, *sgdrlref, *sgdrill, pdrlxy, pfzout, pcout, pindexdrl,

prdrlout, peck1$, *feed, strcantext, e$

]

else,

[

if met_tool$, pitch = n_tap_thds$ # Tap pitch (mm per thread)

else, pitch = 1/n_tap_thds$ # Tap pitch (inches per thread)

pcan1, pbld, n$, *sgdrlref, *sgdrill, pdrlxy, pfzout, pcout, pindexdrl,

prdrlout, peck1$, *pitch, !feed, strcantext, e$

]

pcom_movea

[gcode]

I emailed In House about this and just recieved a

reply..this post is new (07-30) so if you haven't

downloaded mpmaster in the last 3 weeks you can ignore this

 

quote:

---

>Attached is the revised issue of the post. It looks like we just missed

>this code when we were testing. We just left an extra line in the post.

>Thanks for catching that, I will update the emastercam site shortly.

>

>Regards,

>

>Chris McIntosh

>Post Processor Development

>In-House Solutions Inc.

---

[Guest]

I'd ask for a refund

 

 

 

 

j/k Guys

 

Keep up the good work

[Post dept]

I guess we can give back all that money given to us for mpmaster, oh wait!

 

Chris

[Colin Gilchrist]

Gcode,

 

Just FYI, that redundant R value would have come from the pcom_movea post block. The pdrill$ (and ppeck$, ect.) format the first line of a canned cycle output. The pcom_movea post block handles the output of additional points after the initial point in a canned cycle.

 

HTH,

[Colin Gilchrist]

Oh yeah,

 

And the exclamation point (!) forces the update of an internal variable value. The variables in question (refht_a and refht_i) are numeric variables and are modal by default unless forces with the asterisk symbol (*).

 

HTH,

[gcode]

Mpmaster is sweet

Chis emailed me the new file

that I'd been working up for a VMC.

I took that file and overwrote an HMC mpmaster

post I did a few months ago.

The toolplanes and B axis stuff were correct right from

the start since it gets all that from the machine definition.

A few minutes of tweaking and rigid tapping

was coming out perfect.

[crazy^millman]

Chris did you get my email about the Okuma Lathe??

[Post dept]

Yes Ron, I just have a couple other issues to work out first, I should get to look at it later today...