Jump to content

Welcome to eMastercam

Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.

Use your display name or email address to sign in:

Need help with a post.


Jon @ NOWHERE
 Share

Recommended Posts

I just had an operator crash the machine because our post does not put the A(indexer) position with each tool if it is not changing. The operator started up in the middle of the program and just plowed my thread mill into the part. Is there a simple change I can make to our post to fix this?

 

Any help is greatly appreciated.

Link to comment
Share on other sites

This should be a simple post edit, although I can't tell you for sure how to do it. redface.gif

 

My post editing skills involve changing something in the post and then see what happens. It either worked or I try something different. I only have to make post edits every couple of years, so I forget what I learned the last time.

 

Anyway, I recall setting up posts and having to REMOVE what you're looking for. Without having MC at home, I can't use my usual methods to test it. Here's where I would start.

 

code:

ptlchg$          #Tool change                                        

pcuttype

toolchng = one

if mi1$ = one, #Work coordinate system

[

pfbld, n$, *sg28ref, "X0.", "Y0.", e$

pfbld, n$, "G92", *xh$, *yh$, *zh$, e$

]

pbld, n$, "M01", e$

pcom_moveb

c_mmlt$ #Multiple tool subprogram call

ptoolcomment

comment$

pcan

result = newfs(15, feed) #Reset the output format for 'feed'

pbld, n$, *t$, "M6", e$

pindex

sav_absinc = absinc$

if mi1$ > one, absinc$ = zero

pcan1, pbld, n$, *sgcode, *sgabsinc, pwcs, pfxout, pfyout,

-----> pfcout, *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

Here's the tool change section of the MPFAN post. I would make sure you have a "pfcout" on the pcan1 line. Make the change, post, and see what you get. This is my un-expert opinion, but worth a try since no one else has replied yet.

 

Remember, always back up your post before making any edits.

 

Thad

Link to comment
Share on other sites

if you are running an mpmaster based post

 

setting this switch to 1 will do it

 

frc_cinit : 1 #Force C axis reset at toolchange

 

 

you can also try putting a * in front of pfcout

in the line Thad posted

 

-----> *pfcout, *speed, *spindle, pgear, strcantext, e$

Link to comment
Share on other sites

.

 

I can't test at home but,

 

quote:

you can also try putting a * in front of pfcout

in the line Thad posted


I think that's the answer. That should force the A-axis callout at the start of the tool.

 

quote:

frc_cinit : 1 #Force C axis reset at toolchange


I think this will force the reset at the end of the tool.

 

.

Link to comment
Share on other sites

Ok adding the pfcout didn't work. Here is what our toolchange section looks like:

 

quote:

ptlchg$ #Tool change

pcuttype

toolchng = one

softc = 1

if wcs_mode = one, #G92 block output (on EACH tool)

[

pfbld, n$, sg92, *xh$, *yh$, *zh$, e$

]

if prog_stop = 1, pbld, n$, *sm01, e$

if prog_stop = 2, pbld, n$, *sm00, e$

pcom_moveb

pcheckaxis

pbld, n$, *sgcode, *sgplane, scc0, sg70, sg80, *sgabsinc, e$

n$ SG08 e$

c_mmlt$ #Multiple tool subprogram call

ptoolcomment

comment$

pcan

result = newfs(15, feed) #Reset the output format for 'feed'

pbld, n$, *t$, sm06, e$

 

sav_absinc = absinc$

if wcs_mode = two, absinc$ = zero

if opcode$ = 3 & nextdc$ = 7, #Check for rigid tap

[

tap_dir = fsg1(-ss$)

tap_speed = speed

pcan1, pbld, n$, *sgcode, *sgabsinc, *tap_speed, sm05, "M90", pwcs, pfxout,

pfyout, pcout, strcantext, e$

pbld, n$, *sgtap_prep, e$

]

else,

[

pcan1, pbld, n$, *speed, *spindle, e$

n$ scoolant, e$

pbld, n$, *tlngno$, pwcs, pfxout, pfyout, pfzout, pindex, e$

# pcan1, pbld, n$, *sgcode, *sgabsinc, *speed, *spindle, pwcs, pfxout,

# pfyout, pcout, pgear, strcantext, e$

]

#pindex

# pbld, n$, *tlngno$, pfzout, scoolant, pstagetool, e$

absinc$ = sav_absinc

#pcom_movea

toolchng = zero

c_msng$ #Single tool subprogram call

I noticed the pindex which I am assuming is a sub-program callout. And here it is:

 

quote:

pindex #Index output

if index & rot_on_x,

[

if softc = 1,

[

if (prv_indx_out <> fmtrnd(indx_out)) | (prv_cabs <> fmtrnd(cabs)),

[

[if use_rotmcode, `sindx_mc], *indx_out

!cabs, !cinc

]

]

else,

[

if (prv_indx_out <> fmtrnd(indx_out)) | (prv_cabs <> fmtrnd(cabs)),

[

if rot_lock, pbld, n$, *sunlock, e$

pbld, n$, [if use_rotmcode, `sindx_mc], *indx_out, e$

!cabs, !cinc

if rot_lock, pbld, n$, *slock, e$

]

]

softc = 0

]


Hope this makes sense to you guys because I am lost.

Link to comment
Share on other sites

.

 

The pindex is for the 4th axis angle callout.

 

I don't see the pfcout in your post. I only see the pcout. Having the "f" in the code forces the callout. You don't need the *

 

search for pfcout in your post and down around line 1800 you'll find these:

quote:

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

]


They'll explain to you the difference.

 

I assume you're using the mpmaster or similar post.

 

.

Link to comment
Share on other sites

Unless I am mistaken I am thinking the # denotes a comment.

 

Here is our posts' section of what you are talking about.

 

quote:

pfcout #Force C axis output

if index = zero & rot_on_x,

[

if use_rotmcode & cabs <> prv_cabs, *sindx_mc

if absinc$ = zero, *cabs, !cinc

else, *cinc, !cabs

]

 

pcout #C axis output

if index = zero & rot_on_x,

[

if use_rotmcode & cabs <> prv_cabs, *sindx_mc

if absinc$ = zero, cabs, !cinc

else, cinc, !cabs

]

From what little I understand it seems that we are using the pindex component to output the Indexer position. So should I take the pindex out and replace it with pfcout?

 

Looking at it further it appears to be checking the current position against the previous position and if they are equal it does nothing. So should I remove this statement here:

if use_rotmcode & cabs <> prv_cabs, *sindx_mc

Link to comment
Share on other sites

.

 

The # blocks out that line of code. You can use it for comments but also for code you want to keep in place but not activate it.

 

quote:

From what little I understand it seems that we are using the pindex component to output the Indexer position. So should I take the pindex out and replace it with pfcout?


That's correct. You don't want to mess with that or the section quoted in your last post.

 

Where you want the callout is here:

quote:

[

tap_dir = fsg1(-ss$)

tap_speed = speed

pcan1, pbld, n$, *sgcode, *sgabsinc, *tap_speed, sm05, "M90", pwcs, pfxout,

pfyout, p
f
cout, strcantext, e$

pbld, n$, *sgtap_prep, e$

]


Add the "f" to the pcout. You'll find a couple of those in the ptoolchange areas.

 

BTW, did you back-up your post before you started editing?

 

.

Link to comment
Share on other sites

code:

if opcode$ = 3 & nextdc$ = 7, #Check for rigid tap

[

tap_dir = fsg1(-ss$)

tap_speed = speed

pcan1, pbld, n$, *sgcode, *sgabsinc, *tap_speed, sm05, "M90", pwcs, pfxout,

pfyout, pcout, strcantext, e$ #<<<<<<<<<<<<<<<<<<<<< pcout

pbld, n$, *sgtap_prep, e$

]

else,

[

pcan1, pbld, n$, *speed, *spindle, e$

n$ scoolant, e$

pbld, n$, *tlngno$, pwcs, pfxout, pfyout, pfzout, pindex, e$ #<<<<<<<< pindex

# pcan1, pbld, n$, *sgcode, *sgabsinc, *speed, *spindle, pwcs, pfxout,

# pfyout, pcout, pgear, strcantext, e$ #<<<<<<<<<postline with pcout turned off

]

Is this shown after some editing? The last two postlines would have me concerned.

 

I don't have much to go by but my thoughts would be to turn the postline(s)

with the pcout on, change pcout in both places to pfcout, turn the postline

with the pindex off, and add

pbld, n$, *tlngno$, pfzout, e$

after the X,Y move;

 

code:

      if opcode$ = 3 & nextdc$ = 7, #Check for rigid tap

[

tap_dir = fsg1(-ss$)

tap_speed = speed

pcan1, pbld, n$, *sgcode, *sgabsinc, *tap_speed, sm05, "M90", pwcs,

pfxout, pfyout, pfcout, strcantext, e$

pbld, n$, *sgtap_prep, e$

]

else,

[

pcan1, pbld, n$, *speed, *spindle, e$

pbld, n$ scoolant, e$

pcan1, pbld, n$, *sgcode, *sgabsinc, *speed, *spindle, pwcs, pfxout,

pfyout, pfcout, pgear, strcantext, e$

pbld, n$, *tlngno$, pfzout,e$

]

Link to comment
Share on other sites

Everything I have posted is from our original post not the one I have saved to modify. And yes I think this is a version of the mpmaster. The thing is I am sure some of the post was modified by our reseller and some by an engineer who is no longer here. I don't want to send it to our reseller because I don't think this should be too complicated, but with all the mods that may have been done already it doesn't appear to be an easy task. Plus it could have been the reseller who have done the commenting out of the lines which has only made it harder to understand. I've asked my boss about sending me to the basic post editing class and he seems interested in doing so, but at the moment we are swamped with work and behind so no time to make a trip. Either way I will look at this more when I have some time.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.

Join us!

eMastercam - your online source for all things Mastercam.

Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.

Follow us

×
×
  • Create New...