V9 Mpmaster post question

[Rob @ Target Machine]

I am trying to get rid of two remaining annoyances from this v9 mpmaster post.

 

#1 - I would like to eliminate the "extra spaces" in my tool table.

 

#2 - I would like to capture the "z"'s in my custom drill cycles and get them to output with the (z min = z-.1234) lines.

 

Anyone up for this one?

[Rob @ Target Machine]

Couldn't upload files here(to Jay's ftp), but they are uploaded on Cnczone.com forum.

[Guest]

Well since I don't have V9 any longer I'll try from off the top of my head.

 

#1.)

In the tool table you may need to use the no_spc between things where you don't want any extra spaces.

 

#2.)

Maybe, maybe not, it depends HOW your setting Z depths in that custom cycle

[Rob @ Target Machine]

Setting z depths with drl_prm in custom drill cycle. I can't see how buffer 5 is capturing z depths.

 

No luck with spaces after tool comment.

[alma999]

I'm use spaces$ variable to set spaces:

...

spaces$ : 1 # Number of spaces to add between fields

...

pheader$ # File header

n$, sbeginpgm, sprogname$, smm,e$

spaces$ = 0

n$, " ; FILE-", *smcpath$, *smcname$, *smcext$, e$

n$, " ; ", *year2,".", *smonth, day$,". ", time$, e$

spaces$ = 1

...

[Rob @ Target Machine]

I found the space prob --> pspace...it adds extra spaces after tool comment

 

pspace # Creates spaces based on tool comment length

#" " <-----bye bye

""

counter = counter + 1

 

 

OK one down - one to go. Does anyone know how mpmaster post captures the z levels to make z min / z max comments ???

 

I see preadbuf5 and pwritbuf5 routines buffering the z's, but don't see how the routine is getting the z values. "min_depth" is what is outputting the comment until I do a custom drill cycle.

I am using drl_prm to pass the z to the custom cycle and the cycle is ouput as a sub.

[Simtech]

I'll give a shot at an answer for the z_min/z_max:

 

During execution of the post, the pwrtt section is being called out first, before the first operation is being output to the post.

 

It runs thru all operations and gets info for tooltable, tool planes, and x,y,z min/max limits by calling ptravel and writes out the info by calling pwritbuf5.

 

After this parsing is done, ptravel is re-called from the psof section.

 

hope this helps...

[Rob @ Target Machine]

I still don't see where the routine is getting the z value from. It looks to me like I can add my drl_prm(z depth variable) to ptravel postblock to add custom drill cycle's z depth to the z_min var. Am I on the right track?

[Simtech]

Exactly, it will populate in the buffer file and you can read them out when needed.

[Rob @ Target Machine]

Thanks it works fine.

 

 

ptravel # Tool travel limit calculation

if x_min < x_tmin, x_tmin = x_min

if x_max > x_tmax, x_tmax = x_max

if y_min < y_tmin, y_tmin = y_min

if y_max > y_tmax, y_tmax = y_max

if z_min < z_tmin, z_tmin = z_min

if z_max > z_tmax, z_tmax = z_max

# Custom drill parameters<------------

if depth_1 < z_min, z_min = depth_1

if depth_2 < z_min, z_min = depth_2

if depth_3 < z_min, z_min = depth_3

if depth_4 < z_min, z_min = depth_4

if depth_5 < z_min, z_min = depth_5

 

I only need to post for tool clearance. drl_prm values are assigned to depth_1-5 earlier in post.