MPMaster editing question:

[ret5hd]

Fanuc, X4, MPMaster

 

One of the programming conventions at the shop where I am employed is to fomat a G43 line like this:

G43 H[#599]

 

rather than:

G43 Hxxx

 

What this does is set the length offset # to the current tool #. We do this because tool numbers are often (always?) edited at the machine and it insures that a length offset is not forgotten.

 

In the post, I edited this line:

pbld, n$, "G43", *tlngno$, pfzout, scoolant, next_tool$, e$

 

to this:

pbld, n$, "G43", "H["35"599]", pfzout, next_tool$, e$

 

info: 35 is the ascii character #

 

The output then looks like this:

G43 H[ # 599] (with a space on each side of the #)

 

Surprisingly (to me, anyway) this doesn't seem to affect how the code runs. BUT, is there a more elegant way to accomplish this? Also, the way MPMaster sets diameter offsets (G41 and G42) is more complex and it seems the best I can do is to get something like "G42 D0 Xx.xxx Yx.xxx as my output then do a global search and replace in a text editor to get this:

G42 D[#599] Xx.xxx Yx.xxx).

 

Thank you.

[CJep]

quote:

---

to this:

pbld, n$, "G43", "H["35"599]", pfzout, next_tool$, e$

---

There is no need to put the ascii character in quotes. Change the line to this.

 

pbld, n$, "G43", "H",91,35,"599",93, pfzout, next_tool$, e$

[ret5hd]

Well, I tried that and now get this:

G43 H [ # 599 ] (even more spaces)

 

Note: It isnt the 35 that is in quotes, it is the H[ on one side and the 599 on the other side that is in quotes.

 

Thank you for replying.

[Tim Johnson]

You don't need the ascii codes.

 

code:

---

     pbld, n$, "G43 H[#599]", pfzout, next_tool$, e$

---

[ret5hd]

Thank you Tim, that worked exactly as I wished. I had tried this exact thing on an X2 MPFan post and it treated the # as the start of a comment, so I just lived with the ascii workaround (complete with spaces).

 

We recently got X4, and I was tidying things up and thought I would ask here, and now it works. I didn't even re-try that option till you said it.

 

Now, got a fix for the G41 D[#599] prob? I think I will go try a variant of the above solution first.

[CJep]

+1 Tim,

I had used ascii 35 before to keep from commenting the line in the post out, but putting it inside the quotes overrides that, good to know

[Colin Gilchrist]

Being able to put the # sign in a user-defined string variable is new(er) functionality.

 

You are correct that pre-X4 you have to use the ASCII decimal number to output certain characters to the NC file.

[Tinhman]

For cutter comp. you may need this

 

Code

-----------------------------------

# Cutter compensation G code selection

scc0 : "G40" #Cancel cutter compensation

scc1 : "G41 D[#599]" #Cutter compensation left

scc2 : "G42 D[#599]" #Cutter compensation right

sccomp : "" #Target for string

-------------------------------------

 

and find cutter comp. section

 

code

-------------------------------------

 

pccdia #Cutter Compensation

#Force Dxx#

if prv_cc_pos$ <> cc_pos$ & cc_pos$, prv_tloffno$ = c9k

sccomp

if cc_pos$,#tloffno$

--------------------------------------

 

and just "Post and Go"

Hope it helps.

[Tim Johnson]

quote:

---

Being able to put the # sign in a user-defined string variable is new(er) functionality.

 

You are correct that pre-X4 you have to use the ASCII decimal number to output certain characters to the NC file.

---

You could use the # sign starting in X1.

[ret5hd]

Tinhman:

 

That worked exactly as advertised. Thnx.