Manipulating the Post's WCS

[Randy Morton @ Clem Industrial]

I have a partially hypothetical situation; If I wanted to maniplulate the WCS inside of the post and change it to something else and re-post, how abouts would I do that?

 

The thought I am having stems from the thread about what would be nice for the future release. I made mention of the WCS being set at -1 (default) taking on the same identity as the previously used WCS. Persay it had been set to G55 in the op before but I forgot to change the Co-ords WCS to 1, the -1 would look back and take on the G55.

 

What I had done to trial this was create a new variable called r_wcs, formatted the same as g_wcs and told it, before the callouts inside of pwcs, r_wcs = g_wcs, then run all the callouts. It did not work (obviously, if I am writing here...)

 

This is the jist of my code;

code:

---

pwcs            #G54+ coordinate setting at toolchange

r_wcs = g_wcs

if use_wcs = 1,

[

sav_frc_wcs = force_wcs

if sub_level$ > 0, force_wcs = zero

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

[

if sub_level$, result = mprint(swrkserror)

if workofs$ < 6,

[

g_wcs = workofs$ + 54

if workofs$ < 0, g_wcs = r_wcs #***added to prevent redundant G54 when offset is left at default******

*g_wcs

]

else,

[

p_wcs = workofs$ - five

"G54.1", *p_wcs

]

]

]

force_wcs = sav_frc_wcs

!workofs$

]

---

[crazy^millman]

Nope you need to keep it in a buffer I think and check it against that variable to get what you are looking for to work since this section of the post has the information wiped out and check for every operation if you have the post set-up that way. Could be wrong but I think that is what is happening.

 

HTH

[Randy Morton @ Clem Industrial]

How does one store the info into a buffer?

[calnet42]

Try this link..

 

http://www.emastercam.com/ubb/ultimatebb.p...t=010449#000000