pwcs -mcx

[HEAVY METAL]

for some reason my offsets are not posting out Ex. E1,E2.

my post has the pwcs on the tool change line for start of file and null and tool change. but it is being ignored. is there a reason why.

 

 

psof0$ #Start of file for tool zero

psof$

 

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$

]

 

n$, "(T)", sprogname$,"$", e$

pbld, n$, "(1)", *sgplane, '$', e$

sav_absinc = absinc$

pcom_moveb

c_mmlt$ #Multiple tool subprogram call

pstrtool,e$

comment$

pcan

pbld, n$, "(9)", sccomp, "M03", "S100", '$', e$

n$, "(9)", "M6", *t$, '$', e$

pcan1, pbld, n$, "(9)", *speed, *spindle, '$', e$

if mi1$ > one, absinc$ = zero

pbld, n$, '(9)',pwcs, '$', e$

pbld, n$, '(9)', scoolant, '$', e$

pbld, n$, *sgcode, pfxout, pfyout, pcout, pgear, strcantext, '$', e$

pbld, n$, *sgcode, pfzout, '$', e$

pindex

absinc$ = sav_absinc

pcom_movea

toolchng = zero

c_msng$ #Single tool subprogram call

[JG]

heavy metal,

 

what is in your pwcs postblock?

 

Jg

[Guest]

Does it post it at all, like on the first tool change and then not again?

 

Many posts have a switch in the top to output the wcs at alll toolchanges.

 

trying a *pwcs might have some effect as well.

[Guest]

*pwcs will not work. you can't force a postblock.

[Guest]

DUH,

 

You're right Mark.

[crazy^millman]

yeah you need to do the forcing of wcs inside of the pwcs. It is for a Fadal right so if this is the case have you contacted Dave at in-house to see if the MPMASTER_FADAL for X is out and ready. I would also ask how was the post updated for X??

[HEAVY METAL]

crazy i.m at home right now but i used the c-hook inside of mcx to update my post from v9

[HEAVY METAL]

hi jg

here is the post block

pwcs #G54+ coordinate setting at toolchange

if mi1 > one,

[

sav_frc_wcs = force_wcs

if sub_level, force_wcs = zero

if workofs <> prv_workofs | (force_wcs & toolchng),

[

if sub_level, result = mprint(swrkserror)

g_wcs = workofs + 1

*g_wcs

]

force_wcs = sav_frc_wcs

!workofs

]

[HEAVY METAL]

the fixture offset does get output with some tools but not the first one and after that it is intermitent.

[Colin Gilchrist]

Heavy,

 

You need to set the work offset number in the "Planes" button inside each toolpath. This is the offset that Mastercam reads and then outputs at the pwcs call. BTW, if the box is unchecked or if it is set to "-1" then Mastercam will assume that your work offset hasn't changed and will not output a new work offset number. The "-1" value tells Mastercam to ignore that feature (kind of like turning that switch off).

 

You can also assign a work offset to a WCS automatically if you go into the "View Manager". Use the attributes section to assign a work offset number to each plane.

 

In your pwcs postblock you have it set too:

 

g_wcs = workofs + 1

 

This means that whatever work offset number you enter in the work offsets data entry field will get the number 1 added to it. That means a work offset entry of "0" gets output as E1. I would change the g_wcs line to:

 

g_wcs = workofs

 

( just delete the + 1)

 

Then the number you enter in the work offset data entry field is the work offset you get. 0=E0, 1=E1, ect.

 

I don't know how much custom stuff you have in your post, but Mastercam X ships with two Fadal posts, a format 1 and a format 2. Both of these posts require almost no editing to get perfect Fadal code. You might consider just taking the new Fadal post for version X and making changes to it. Both post are already setup for the E series of work offsets, X style coolant options, ect. If you can't find it on the X install disk, contact your reseller. They should be able to send it to you.

 

HTH,

 

Colin Gilchrist

The Boeing Company

[HEAVY METAL]

i got something going on because it is not posting out a fixture off set with the first tool. my post worked fine in v9. i have been working with offsets since v8. here is what my post looks like

 

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$

]

 

n$, "(T)", sprogname$,"$", e$

pbld, n$, "(1)", *sgplane, '$', e$

sav_absinc = absinc$

pcom_moveb

c_mmlt$ #Multiple tool subprogram call

pstrtool,e$

comment$

pcan

pbld, n$, "(9)", sccomp, "M03", "S100", '$', e$

n$, "(9)", pwcs, "M6", *t$, '$', e$

pcan1, pbld, n$, "(9)", *speed, *spindle, '$', e$

if mi1$ > one, absinc$ = zero

pbld, n$, '(9)', scoolant, '$', e$

pbld, n$, *sgcode, pfxout, pfyout, pcout, pgear, strcantext, '$', e$

pbld, n$, *sgcode, pfzout, '$', e$

pindex

absinc$ = sav_absinc

pcom_movea

toolchng = zero

c_msng$ #Single tool subprogram call

[HEAVY METAL]

the two post one from v9 and on from mcx are the same i cant understand why mcx is not picking up the offset is this a bug in mr1 ??????????

[HEAVY METAL]

switch in the top to output the wcs at all toolchanges is checked

[HEAVY METAL]

i think i'm on to something the misc values have somthing to do with it

integers

Work Coordinates [0-1=G92, 2=E's]

set to (2)

[HEAVY METAL]

i want to force the fixture offset out here .this what i changed(if mi1$ => one & workofs$ <> prv_workofs$) but it is just posting a blank line with($) does anyone know what is wrong with this code. this whole problem started when i went to transform some ops to run on two pallets

 

 

 

 

ptlchg0$ #Call from NCI null tool change (tool number repeats)

pcuttype

pcom_moveb

c_mmlt$ #Multiple tool subprogram call

comment$

pcan

pbld, n$, '(1)', sgplane, '$', e$

if prv_spdir2 <> spdir2, pbld, n$, "(9)", *sm05, '$', e$

if prv_speed <> speed | prv_spdir2 <> spdir2,

pbld, n$, "(9)", *speed, *spindle, pwcs, pgear, '$', e$

pbld, n$, '(9)', scoolant, '$', e$

if mi1$ => one & workofs$ <> prv_workofs$,

[

sav_absinc = absinc$

absinc$ = zero

pbld, n$, "(9)", pwcs, "$", e$

pbld, n$, "(0)", pfxout, pfyout, pfcout, '$', e$

pbld, n$, "(0)",pfzout, '$', e$

pe_inc_calc

ps_inc_calc

absinc$ = sav_absinc

]

if cuttype = zero, ppos_cax_lin

if gcode$ = one, plinout

else, prapidout

pcom_movea

c_msng$ #Single tool subprogram call

[Post dept]

Heavy,

 

You're going to have to do more trouble shooting. The code itself as you posted doesn't look bad that I can see (hard to tell though). A couple of quick suggestions to fix these issues. Go into your control definition, under the files tab and set the keep error file to "On fatal and non-fatal errors" and set the message option to "All error messages to file". This will produce a .err file in your nci directory with all the errors encountered during posting. If you just updated the file there is a good possibility that something hasn't been defined properly in X or there is some other random error.

 

Also, try throwing in a:

"!", ~workofs$, prv_workofs$, e$

before the:

if mi1$ => one & workofs$ <> prv_workofs$,

line you just added. This will show you what the values are and let you know the post is at least getting to that point. If nothing is output, then the post isn't making it to this statement and you need to move the statement closer to the pwcs statement until you find the road block.