Posting HAAS WCS G110 as default

[Guest]

I am trying to set up a post for a HAAS, it uses G110 and up. I am trying to make it so the default (-1) begins at 110.

 

I am scratching my head however, if I change the offset to 0, starting there I get G110 on up but when I use the default setting I keep getting G116, I cannot for the life of me figure out where it is picking up the number.

 

Where does the post draw the variable from when the workofs$ is set to -1?

[crazy^millman]

John what does the pwcs look like in the post? I might be tied all the way back the MP.dll and if that is the case it would seem to me you are getting the defualt +5 to your starting offset from there.

[Guest]

It's pretty stock with the one obvious change

 

code:

---

pwcs            #G54+ coordinate setting at toolchange

if wcstype = two | wcstype > three,

[

sav_frc_wcs = force_wcs

if sub_level$, force_wcs = zero

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

[

if workofs$ < 6,

[

g_wcs = workofs$ + 110

]

else,

[

g_wcs = workofs$ + 110

]

if workofs$ >= 0 & workofs$ <= 25, *g_wcs

else,

[

if mprint(swcserror, 2) = 2, exitpost$

]

]

force_wcs = sav_frc_wcs

!workofs$

]

---

[Tim Johnson]

Try adding a workofs$, e$ line before the work offset manipulation starts and post to make sure that workofs$ does equal -1 at that point. If it is try something like sav_workofs = workofs$ and replace ths manipulated workofs$'s with sav_workofs.

[Guest]

code:

---

G00 G90 G49 H13 S4500 M03

M08

workofs$ 6.

G116 G00 G43 X-1.3856 Y.666 Z2.

---

I can't isolate using if workofs$ = 6 or anything because when a hand typed 6 might get used, it will have the same reaction as the default setting.

 

I figured it out.

 

I use this file for different post testing and I had the offest set in the WCS manager to 6, that's why it was coming out the way it was.

 

I changed it to -1 and all was as I expected to get.

 

[ 08-06-2006, 06:20 PM: Message edited by: John Paris @ Kevlin ]

[crazy^millman]

Hey John Try this.

 

code:

---

    pwcs            #110+ coordinate setting at toolchange

if wcstype = two | wcstype > three,

[

sav_frc_wcs = force_wcs

if sub_level$, force_wcs = zero

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

[

if workofs$ < 25,

[

g_wcs = workofs$ + 110

]

if workofs$ >= 0 & workofs$ <= 25, *g_wcs

else,

[

if mprint(swcserror, 2) = 2, exitpost$

]

]

force_wcs = sav_frc_wcs

!workofs$

]

 

 

---

Not sure what it will do but I would do away with from the (else) there. Glad you got it but I would look at having my post this way if you are going to use G110 and greater.

[Guest]

Thanks Ron,

 

I was going to tweak that down next.

 

I gotta give them a call tomorrow and find out how many offsets they do have.

 

[Jack Neelands™]

i wont be able to dig up my haas post till tuesday john...that goes G125 P1 after you run out of offsets from G110 to G125

[crazy^millman]

Here is what I did in a MPMASTER V9 post for the HAAS where I was using the G154 PXX so from what I remember G110 is G154 P1 and when you get to G126 it becomes G154 P26 but could be wrong has been a couple years since working on the HAAS with these capabilites.

 

code:

---

pwcs            #G54+ coordinate setting at toolchange

if wcstype = two | wcstype > three,

[

sav_frc_wcs = force_wcs

if sub_level, force_wcs = zero

if sav_mi9 = 1, workofs = sav_workofs

if workofs < 0, workofs = 0

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

[

p_wcs = workofs

"G154.1", *p_wcs

]

force_wcs = sav_frc_wcs

!workofs

]

 

---

[Jack Neelands™]

yup I stand corrected ...tis G154 PXXX thanks Ron

 

 

Had change this to 106 so that i got G110 to come up though

g_wcs = workofs$ + 106