Scribd
Upload
679 views

Mpfan Post Processor Help File

The document provides instructions for making test edits to a post processor file by making copies of the original file and then making small incremental changes. It highlights specific areas to search for like "ptoolcomment" and lines marked with "#" that can be safely commented out or edited to test changes before implementing them fully. The goal is to help the reader begin understanding post processing by starting with simple editable elements and getting feedback from the sample output, with the author offering further assistance if needed.

Uploaded by

Ed lHigh
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
679 views

Mpfan Post Processor Help File

The document provides instructions for making test edits to a post processor file by making copies of the original file and then making small incremental changes. It highlights specific areas to search for like "ptoolcomment" and lines marked with "#" that can be safely commented out or edited to test changes before implementing them fully. The goal is to help the reader begin understanding post processing by starting with simple editable elements and getting feedback from the sample output, with the author offering further assistance if needed.

Uploaded by

Ed lHigh
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

Open mpfan in your editor. SAVE A COPY BEFORE MAKING CHANGES!!!! Call it stable or backup or whatever you choose.

Save backup copy. Now save a copy and call it testing or new, etc. Make only small changes at first until you begin to understand whatyou are doing ! Post an nci file with original post and new post. Note the changes: You are now on your way. Here are a few clues...... look through and edit the numbered questions within the post first: some basic things can be changed easily here such as rotary output "A" axis bein g posted or omitted can be changed in Numbered question 164 just change "yes" to "no" or "1" to "0"

Search for "ptoolcomment". An example of a common change is as follows: YOU CAN OMIT A LINE WITH # OR EDIT TEXT WITHIN QUOTES " " BEFORE: # -------------------------------------------------------------------------fmt "TOOL - " 4 tnote # Note format fmt " DIA. OFF. - " 4 toffnote # Note format fmt " LEN. - " 4 tlngnote # Note format fmt " DIA. - " 1 tldia # Note format # -------------------------------------------------------------------------# Tool Comment / Manual Entry Section # -------------------------------------------------------------------------ptoolcomment #Comment for tool tnote = t toffnote = tloffno tlngnote = tlngno "(", pstrtool, *tnote, *toffnote, *tlngnote, *tldia, ")", e AFTER: # -------------------------------------------------------------------------fmt "T - " 4 tnote # Note format fmt "D - " 4 toffnote # Note format fmt " LEN. - " 4 tlngnote # Note format fmt " DIA. - " 1 tldia # Note format # -------------------------------------------------------------------------# Tool Comment / Manual Entry Section # -------------------------------------------------------------------------ptoolcomment #Comment for tool

tnote = t toffnote = tloffno tlngnote = tlngno #"(", pstrtool, *tnote, *toffnote, *tlngnote, *tldia, ")", e "(", pstrtool, *tnote, *toffnote, ")", e ******************************************************************************** ************ LOOK FOR THE # WHERE I HAVE "commented out" several lines that would be "POSTED" : psof #Start of file for non-zero tool number pcuttype toolchng = one if ntools = one, [ #skip single tool outputs, stagetool must be on stagetool = m_one !next_tool ] "%", e *progno, e #"(PROGRAM NAME - ", sprogname, ")", e #"(DATE=DD-MM-YY - ", date, " TIME=HH:MM - ", time, ")", e pbld, n, *smetric, e pbld, n, *sgcode, *sgplane, "G40", "G49", "G80", *sgabsinc, e sav_absinc = absinc if mi1 <= one, #Work coordinate system [ absinc = one pfbld, n, sgabsinc, *sg28ref, "Z0.", e pfbld, n, *sg28ref, "X0.", "Y0.", e pfbld, n, "G92", *xh, *yh, *zh, e absinc = sav_absinc ] pcom_moveb c_mmlt #Multiple tool subprogram call ptoolcomment comment pcan if stagetool >= zero, pbld, n, *t, "M6", e pindex if mi1 > one, absinc = zero pcan1, pbld, n, *sgcode, *sgabsinc, pwcs, pfxout, pfyout, #pfcout, *speed, *spindle, pgear, strcantext, e *speed, *spindle, pgear, strcantext, e pbld, n, "G43", *tlngno, pfzout, scoolant, next_tool, e absinc = sav_absinc pcom_movea toolchng = zero c_msng #Single tool subprogram call

******************************************************************************** *********** There is way too much to teach someone about post editing so..............

Let me know how you do. If you still need help let me know. mastercamguru@comcast.net

You might also like