Adding g8 to fadal format1 post

[ATG]

I would like to add g8 to any milling operations to my Fadal Format 1 post. I'm Currenly running X4. Is there an easy way to edit my post to acomplish this.

 

thanks

 

Seth

[Thad]

Seth,

 

We hard coded a G8 in the post at psof and ptlchg. Then on drilling, tapping, and boring cycles, we hard coded a G9. You end up with a G9 that cancels a G8 from a few lines prior (messy code), but it works.

 

There's another way, but I can only give you limited guidance on how to do it since I'm not a post expert. When we tap, we don't want the spindle to turn on. Our post is configured to check the tool type and based on that (is it a tap, or not?) execute a certain line of code. You could use the same logic...anything other than a milling tool (reamer, drill, tap, boring bar, etc), then output a certain line of code (don't output G8). The problem is, I don't know the specifics behind the tool types. What tool type is what? Here is the code we used for tapping. You'll have to relate the logic to your situation. This will be in the tool change section of your post.

 

code:

---

if tool_typ$ > 3 & tool_typ$ < 6, n$, psg00, *xr$, *yr$, *rpm, !ss$, ptool_next, e$# output for tapping

else n$, psg00, *xr$, *yr$, *rpm, !ss$, *spdlon, ptool_next, e$# 1st position

---

In the above example, it looks like taps (right and left hand) are tool types 4 and 5, because if they are, there's no output for spindle on.

 

Do you see how this could be adapted to your situation?

 

I wish I could be of more help.

 

Thad

[ATG]

Thanks Thad I'll probly hard code it as you've done. I've seen outputs like that before it seem to work fine.

 

Thanks again.

[ATG]

Oh, can you show me a sample of how it looks hard coded.

 

 

Thanks

 

Seth

[Thad]

Here's a snippet of our psof

 

code:

---

      !spaces

spaces = zero

n, "(CREATED ON ", *month, "-", *day, "-", *year, " AT ", ptime, " )", e

spaces = prv_spaces

 

#pbld, n, *smetric, e

pbld, n, *sgcode, *sgplane, "G40", "G80", "G90", "H0", "E0", "Z0", e

sav_absinc = absinc

n,"G8", e <-------------Add here

if wcs_mode = zero | wcs_mode = one, # 'G92' output modes w/ 'G28' retracts

[

pbld, n, "G28", "Z0.", e

pbld, n, "G28", "X0.", "Y0."

if rot_on_x > zero, "A0."

e # end this block

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

]

pcom_moveb

c_mmlt #Multiple tool subprogram call

ptoolcomment

comment

---

Then each drilling/boring/tapping cycle gets a G9 (we also added positive approach; M46) like the example below.

 

code:

---

pdrill          #Canned Drill Cycle - G81/G82

pdrlcommonb

n, "M7", e

n, "G9", "M46", e <------Added here

pcan1, pbld, n, *sgdrill, *sgdrlref, pxout, pyout, pfzout, pcout,

prdrlout, dwell, *feed, strcantext, e

pcom_movea

---

It's not exactly clean, but it works.

 

Thad

[ATG]

Thanks again Thad I'll give it a try.

[svirfnebli]

Sorry to resurrect a super old post, but I found a slightly different way of handling this that worked really well for me and figured id post for posterity. I set up the G8 / G9 as a type of coolant in one of the unused slots. Now when I want G8 on a program I just go to coolant, and select "G8" on, and "Before". It turns G8 on for that operation and goes back to G9 at the end of the operation. This protects your drilling cycles as was a concern above..

In the post I altered the following lines

scool64 : "G8"    		#Coolant 8 on value
scool65 : "G9"			#Coolant 8 off value

and in Mastercam i go into Machine definition > General Machine Parameters > Coolant Commands and make sure both check boxes are NOT checked.

 

[Leon82]

Our Mastercam dealer did it using this line here

 

If nextdc<0,

[

G5.1q1

]

That's not the whole line but you can do it that way also

[pete_hull]

 

      if (opcode$ = three),
      pcan1, pbld, n$, *sgcode, *sgabsinc, "G9", pwcs, pfxout, pfyout,
        *speed, *spindle, pgear, strcantext, e$
      else,
      pcan1, pbld, n$, *sgcode, *sgabsinc, "G8", pwcs, pfxout, pfyout,
        *speed, *spindle, pgear, strcantext, e$

 

is how I do it.