Post - Additional points

[CAM-mando]

Good morning,

 

I have been overhauling our posts here since I returned about 6 months ago. My custom tapping Cycle for Rigid Tapping is here:

 

pmisc2 #Canned Misc #2 Cycle - RIGID TAPPING #ADDED DG

pdrlcommonb

rt_feed = (1 / n_tap_thds)

"G93", e

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

prdrlout, *rt_feed, e

pcom_movea

 

This worked great (til yesterday). I made a toolpath edit and added points to my toolpath geometry. All of a sudden I get the Feed output from the Feed Field on the Parameters Page for the additional points.

 

So I found the section further down in the post:

 

pmisc2_2 #Canned Misc #2 Cycle

I edited this section to remove the Feed output and all appears to be well. I’m trying to fully understand whats going on here so I can eliminate future suprises.

 

Question:

 

1) Is pmisc2_2 only called when points are added by editing the geometry ?

2) What is the reasoning behind this.

 

Dave

The “5.0 IPR Ouch”

[kccadcam]

This is how I am running my Yasnac machines:

 

code:

---

 pmisc2          #Yasnac Rigid Tap

pdrlcommonb

pbld, n, "G93", "(RIGID TAP)", e

feed = 1 / n_tap_thds

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

prdrlout, *feed, strcantext, *speed, e

pcom_movea

 

---

To cancel cycle:

 

code:

---

 pcanceldc       #Cancel canned drill cycle

if drillcyc = 7, pcancelrig

else, pcancelcdc

 

 

pcancelcdc #Cancel canned drill cycle

result = newfs (three, zinc)

z = initht

if cuttype = one, prv_zia = initht + (rotdia/two)

else, prv_zia = initht

pxyzcout

!zabs, !zinc

prv_gcode = zero

pbld, n, "G80"

 

 

pcancelrig #Cancel Yasnac rigid tapping cycle

result = newfs (three, zinc)

z = initht

if cuttype = one, prv_zia = initht + (rotdia/two)

else, prv_zia = initht

pxyzcout

!zabs, !zinc

prv_gcode = zero

pbld, n, "G80", e

pbld, n, "G94", e

---

Hope this helps.

[kccadcam]

Forgot this:

 

code:

---

 pdrill_2        #Canned Drill Cycle, additional points

pdrlcommonb

pcan1, pbld, n, pxout, pyout, pzout, pcout, prdrlout, dwell,

strcantext, e

pcom_movea

---

[CAM-mando]

Kevin,

 

Thanks for the quick reply.

 

The post in question is also for a Yasnak, and My cnacel sections are set up similar to yours.

 

quote:

---

Forgot this:

---

Yeah ... I really forgot it ...

 

Thats the section I'm asking about. Is that section only called by boints that have been added to existing toolpath geometry ???

[Roger Martin from CNC Software]

The 'canned_postblock_name_2' postblocks are

called after the call to the 'canned_postblock_name' is made.

 

ONLY if there is more than 1 point position to be drill/tapped/reamed/whatever.

 

Example:

 

PDRILL # Called for 1st point in the pattern

 

PDRILL_2 # Called for the 2nd thru last point.

 

Reason for this?

You are creating the Drill/Tap/Whatever cycle code in the PDRILL postblock. The PDILL_2 is to output the positioning code for the subsequent points - if they exist.

[CAM-mando]

Roger thanks,

 

I think what copnfused this for me was all the prior MC9's had the Feed parameter entered as the pitch (how our old post required it) now with the new post the MC9's were being toolpathed ignoring the Feed Parameter in MC since the post wasnt using it (So I thought).

 

So in the past it was outputing the first point with the calculated feed and with additional points with Feed from the parameters page which used to be the same number. In the newer toolpaths theyre different thats why this popped up now and not sooner. It had nothing to do with the editing of the points.

 

Duh !

 

Thanks Guys