My tool list

[Bugzpulverizer]

Right now I have a post that I have edited a little and it has a tool list in the beginning. I've been successful in getting it to list correct tool numbers in order they are used, but would like it to print the comment for the tool that I give it in Mastercam. I would like it to go between the equal sign and the 2nd parantheses. Here is what I have:

 

(XXX )

(P/N:)

(BOGLINO - DATE:)

(********************)

( T03= )

( T07= )

( T11= )

( T12= )

( T10= )

( T09= )

( T14= )

( T15= )

( T16= )

( T01= )

(********************)

 

It is an Okuma post, from version 9. I use both 9 and x2, but when I get it right I will just update it for x2. Thanks in advance.

[Bugzpulverizer]

NUDGE, NUDGE!

[DavidSV]

I think that after you have it place the '=' you can add *strtool$ and it will post your tool comments.

[Bugzpulverizer]

I have put asterisks in post and succeeded in getting them around where I want tool comment to go. Here is what I am getting:

 

(XXX )

(P/N:)

(BOGLINO - DATE:)

(********************)

( T07=* *)

( T18=* *)

( T11=* *)

( T12=* *)

( T10=* *)

( T09=* *)

( T14=* *)

( T15=* *)

( T16=* *)

( T01=* *)

(********************)

 

Here are the two places I put the asterisks in the post:

 

fmt "T" 4 tnote "=*" # Note format

fmt "DIA. OFF. - " 4 toffnote # Note format

fmt "LENGTH - " 4 tlngnote # Note format

fmt "TYPE- " 11 tldia # Note format

 

This is toward beginning of post, and here:

 

pwrtt # Write tool table, scans entire file, null tools are negative

 

tnote = t

toffnote = tloffno

tlngnote = tlngno

if t >= 0, "(", tnote, "*)"

if t >= 0, tcnt = tcnt + 1

 

Which is the last thing before the # questions at the end of the post. As post is reading the tool numbers, and putting them in order at beginning of my program, I want it to read the coinciding tool comment I enter in Mastercam, and print it in the tool list. Thanks in advance for the help.

[crazy^millman]

Have you looked at MPMASTER which is free off of this web site which will problay do there very thing you are after since it seems calling your dealer for the 5 minute fix seems to be out of the question.

[Bugzpulverizer]

Sorry to have bothered you. Wow.

[Bugzpulverizer]

I don't understand. Did I do something wrong on this forum, or did I make somebody mad? I am just trying to learn like everyone else, but I just seem to attract people with attitudes, who act like I am annoying them by asking questions. Are my questions not up to par? WTF? Anyway, thanks to those who helped me in the past, I really appreciate it. BTW I am waiting on a reply from my dealer also. I just thought I'd pose the question here also.

[Dan@home]

About the 5 min fix I don't know. Some of us will learn from your thread, just keep it up.

[crazy^millman]

Not a bother to me, and why take it so offensively?

 

But since we seem to have the need to go down this road lets asks a few questions how much searching have you done on tool list.

 

Here is just a few I dug up with post examples:

 

Linky1

 

Linky 2

 

Linky 3

 

Linky 4

 

Linky 5

 

Linky 6

 

Now if you read some of those the same suggestions was made look at MPMASTER.

 

Why is that again so offensive to suggest that?

[Zoober]

Aw, don't mind him Bug.... He's crazy!

[htm01]

quote:

---

Not a bother to me, and why take it so offensively?

---

maybe you didn't mean to, but i took it the same way bug did.

[crazy^millman]

Ok then I will be sure to not post anything up from now on since so many where jumping in to help out. I have used MPMASTER for many things over the years and if you are a novice or even a seasoned post person MPMASTER is one of the best things to use Period for trying to figure things out with posts!!!!

 

Also it was not mentioned until after I said something he had contacted his dealer sorry I am not a mind reader.

 

Have a good weekend

 

Ron the pisser off of Men

[iowajim62]

BUG,

that's just Ron teh Crazy Millman flyin thru helpin and he doesn't mean to pi$$ anybody off.

He's Just CraZy

 

Ron,

Keep helpin bro, I learn alot from readin your posts.

[Thad]

I was wondering who pissed in Ron's Cornflakes myself. While using the MPMaster post is a good idea, and even suggested often, not everyone has time to stop programming and start learning the MP language via MPMaster, OR do a complete overhaul of their existing post by editing MPMaster.

 

If Ron says it wasn't meant to be offensive, then I believe him. That doesn't mean that others, including myself, didn't see it that way.

 

Thad

[mario]

my output is the better

 

(NOM : 1270#3 BRASS )

(Machine:Okuma)

 

( N1 - T1 - H1 - 3/8 SPOTDRILL )

( N11 - T2 - H89 - 3/4 SPOT DRILL PASTILLE 90° )

( N5 - T3 - H39 - 1/4 DRILL RT-100 GUHRING )

( N2 - T4 - H19 - 3.1mm DRILL XPM )

( N8 - T6 - H11 - 13/32 FLAT ENDMILL )

( N10 - T10 - H44 - 3/4 CHAMFER MILL S5 DORMER )

( N6 - T16 - H4 - 9/32 DRILL RT-1OO GUHRING )

( N7 - T17 - H2 - 11/32 DRILL RT-100 LIST 5515 )

( N9 - T18 - H17 - 1/2 endmill guhring list 3092 )

( N3 - T19 - H62 - DRILL 4.7MM LISTE 605 )

( N4 - T20 - H40 - 5.1 DRILL RT-100 GUHRING )

 

(HEURE : 10:51 )

(DATE: JUILLET - 24 - 08 )

(P:name of programer)

 

(OVERALL MAX Z2. )

(OVERALL MIN Z-1.2033 )

 

(MCX FILE - J:1GEO1 MTL PVC1270 1270 PERCAGE CAL .MCX )

[crazy^millman]

Bug point is a lot of people are using X and above, and V9 help is limited with regards to posts. Other point is I would recommend not updating the post from V9 to X2. I would recommend getting a good X2 post from your dealer if you are lacking in skills to modify a post to your needs. Time is money and money is time and the cost of doing yourself is worth something and sometimes getting someone more knowledgeable is time saving thus saving money. Explain to the powers at be that giving you the budget for such tools is like adding power to your programming toolbox. No one else is willing to step and offer, but send me your post and I will glad to assist you. You guys are ready to chime about what I am doing, how about chiming in and helping the person out I am not the only one around here that know a little something about posts, but I was the only one really offering some help wither you understood that or not.

 

Here are some thing to look at best I can remember sorry this is from MPMASTER do not and have not had V9 on a system in a long time since I doubt you will be sending the post my way:

 

1:The switch in the post which control the behavior of the tool table:

 

code:

---

tooltable   : 1     #Read for tool table and pwrtt - use tool_table to disable  

---

2: The format Statements related to the tools:

code:

---

# --------------------------------------------------------------------------

fmt "TOOL - " 4 tnote # Note format

fmt " DIA. OFF. - " 4 toffnote # Note format

fmt " LEN. - " 4 tlngnote # Note format

fmt " DIA. - " 1 tldianote # Note format

# --------------------------------------------------------------------------

fmt D 17 tldia # Note format

fmt R 17 tcr # Note format

---

3: The tool comment section relates to comments at each tool not the tool table:

 

code:

---

ptoolcomment    #Comment for tool

tnote = t

toffnote = tloffno

tlngnote = tlngno

tldianote = tldia

"(", pstrtool, *tnote, *toffnote, *tlngnote, *tldianote, ")", e

---

4: The pwrtt section does the output for the tool table and the format and way it looks comes from here:

 

code:

---

# --------------------------------------------------------------------------

# Tooltable Output

# --------------------------------------------------------------------------

pwrtt # Write tool table, scans entire file, null tools are negative

if rotaxis > 0 | rotary_type > 0 | mill5 <> 0,

[

rot_on_x = sav_rot_on_x

output_z = no

]

#if vmc = 0 & tlplnno <> 2, rot_on_x = sav_rot_on_x

#if vmc = 1 & tlplnno > 1, rot_on_x = sav_rot_on_x

if tlplnno > 1, rot_on_x = sav_rot_on_x

tlplnno = wbuf(3,wc3) #Buffers out tool plane values

t = wbuf(4,wc4) #Buffers out tool number values

if tool_table = 1, ptooltable

if tool_table = 2, ppredtool

if tool_table = 3, pmetatool

if t >= zero, tcnt = tcnt + one

ptravel

pwritbuf5

 

ptooltable # Write tool table, scans entire file, null tools are negative

tnote = t

toffnote = tloffno

tlngnote = tlngno

spaces=0

if t >= zero,

[

if tcr>0, "(", *t, ptspace, " | ", plistcomm, " | ", *tlngno, phspace, " | ", *tloffno, pdspace, " | ", *tldia, punit, pdiamspc, " | ", *tcr, " | ", popnote, ")"

if tcr=0, "(", *t, ptspace, " | ", plistcomm, " | ", *tlngno, phspace, " | ", *tloffno, pdspace, " | ", *tldia, punit, pdiamspc, " | ", " | ", popnote, ")"

]

#if t >= zero,

# [

# "(", *t, ptspace, " - ", plistcomm, ")"

# ]

#if t >= zero,

# [

# if tcr>0, "(", *tnote, " ", *toffnote, " ", *tlngnote, " ", *tldia, " ", *tcr, " ", popnote, ")"

# if tcr=0, "(", *tnote, " ", *toffnote, " ", *tlngnote, " ", *tldia, " ", popnote, ")"

# ]

spaces=sav_spc

 

punit # Tool unit

if met_tool, "mm"

else, 34

---

Now depending on what you do or do not want here it is all easily accessed using the again MPMASTER post. Now V9 would give you an error when things where not defined. So these things you see here are defined in the post and used in certain ways. This seems tricky, but it is not. The thing is pay attention to what each thing does. Best way I know of is to use the find function in Cimco.

 

Taking things out of one post and putting into another. I like to use the window vertical and have the 2 post next to each other. So in my exmaple again sorry, but I like MPMASTER and since I am the only one willing to help you and I am such a arse may not help you but may help someone else.

 

So we start searching the 1st thing I do it look for ptspcace. I find it and this is what it looks like in the post:

 

code:

---

# --------------------------------------------------------------------------

# Tool Comment / Manual Entry Section

# --------------------------------------------------------------------------

ptoolcomment #Comment for tool

tnote = t

toffnote = tloffno

tlngnote = tlngno

tldianote = tldia

"(", pstrtool, *tnote, *toffnote, *tlngnote, *tldianote, ")", e

 

pstrtool #Comment for tool

if strtool <> sblank,

[

strtool = ucase(strtool)

*strtool, " "

]

 

pcomment #Comment from manual entry (must call pcomment2 if booleans)

pcomment2

 

pcomment2 #Comment from manual entry

spaces = 0

scomm = ucase (scomm)

#1005 - Comment option 1

#1006 - Comment option 2

#1007 - Define comment with output line

#1008 - Define NC parameter comment

#1026 - ?

if gcode = 1005, pbld, n, pspc, "(", scomm, ")"

if gcode = 1006, pbld, n, pspc, "(", scomm, ")" #Comments

#if gcode = 1006, pbld, n, pspc, scomm #Codes

if gcode = 1007, "(", scomm, ")"

if gcode = 1008, pbld, n, pspc, "(", scomm, ")"

if gcode = 1026, pbld, scomm

if gcode <> 1007 & gcode <> 1026, e

spaces = sav_spc

 

ptoolcomm # Comments from tool library

spaces = 0

strtool=ucase(strtool)

if strtool<>snull, pspc1, "(", *strtool, ")", e

else, pspc1, "(", "DEFINE TOOL NAMES", ")", e

spaces = sav_spc

 

plistcomm # Comments from tool library

strtool=ucase(strtool)

if strtool<>snull, *strtool

else, "DEFINE TOOL NAMES"

 

if strtool=snull, stest1=snocomm+stilde

else, stest1=strtool+stilde

nstrlen = strstr(stilde,stest1)-1

counter = 1

while counter <= (25-nstrlen), pspace

 

pmetacomm # Comments from tool library

strtool=ucase(strtool)

if strtool<>snull, *strtool

else, "DEFINE TOOL NAMES"

 

pspace # Creates spaces based on tool comment length

" "

counter = counter + 1

 

ptspace # Creates spaces based on tool number

if t<10, " "

 

phspace # Creates spaces based on length offset number

if tlngno<10, " "

 

pdspace # Creates spaces based on diameter offset number

if tloffno<10, " "

 

pdiamspc # Creates spaces based on diameter offset number

if tldia<10, " "

 

pspc # Creates spaces based tool level setting

if sav_spc = one & omitseq = no, " "

 

pspc1 # Creates spaces based tool level setting

if sav_spc = one, " "

 

popnote # Operation note for tool table

if opcode = 3, *sdrnote

else, *sopnote

---

These sections are related to the buffers used to control these different things

 

code:

---

# --------------------------------------------------------------------------

# Buffer 5 Read / Write Routines

# --------------------------------------------------------------------------

pwritbuf5 # Write Buffer 1

b5_gcode = gcode

b5_zmin = z_min

b5_zmax = z_max

b5_gcode = wbuf(5, wc5)

 

preadbuf5 # Read Buffer 1

size5 = rbuf(5,0)

b5_gcode = 1000

min_depth = 99999

max_depth = -99999

while rc5 <= size5 & b5_gcode = 1000,

[

if rc5 <= size5, b5_gcode = rbuf(5,rc5)

if b5_zmin < min_depth, min_depth = b5_zmin

if b5_zmax > max_depth, max_depth = b5_zmax

]

# --------------------------------------------------------------------------

# Buffer 3 - Holds the variable 'tlplnno' for each toolpath segment

# --------------------------------------------------------------------------

rc3 : 1

wc3 : 1

fbuf 3 0 1 0 # Buffer 3

 

# --------------------------------------------------------------------------

# Buffer 4 - Holds the variable 't' for each toolpath segment

# --------------------------------------------------------------------------

rc4 : 1

wc4 : 1

fbuf 4 0 1 0 # Buffer 4

 

# --------------------------------------------------------------------------

# Buffer 5 - Min / Max

# --------------------------------------------------------------------------

b5_gcode : 0

b5_zmin : 0

b5_zmax : 0

rc5 : 2

wc5 : 1

size5 : 0

 

fbuf 5 0 3 0 #Min / Max

 

 

fmt X 2 x_tmin # Total x_min

fmt X 2 x_tmax # Total x_max

fmt Y 2 y_tmin # Total y_min

fmt Y 2 y_tmax # Total y_max

fmt Z 2 z_tmin # Total z_min

fmt Z 2 z_tmax # Total z_max

fmt Z 2 min_depth # Tool z_min

fmt Z 2 max_depth # Tool z_max

---

So as we look at this section some of may or may not be in your post. So copy what is not in your post and check what is and adjust to suit your needs. Not sure what your needs are well you will have to just keep trying to you find what works.

 

So next we go back to the pwrtt section and search out the other variables related to the tooltable. You will find that all of that is here everything related to the tooltable.

 

Again I am not great post person, but I could with the 2 post in front of me do all of what I just spent the last 30 minutes showing you I could do in about 5 minutes using MPMASTER.

 

Now comes the million dollar question what does this have to do with what you want. Everything since almost all of what you are looking for is coming out of the post it these section once you understand how this work and what goes where then changing something simple as the arrangement of what you want becomes very easy. Seems like a long way to get there, but if you understand the structure and the function of parts of the post then you can start breaking down the more complex functions and do it with the speed you need to get it done and move on the more important thing like making programs for parts.

 

Don't like my approach give me more facts and I will go in a different direction.

 

Oh guys why was everyone avoiding this one like the plague????

 

Oh and I know in my heart what I meant by it and if you guys knew my dry sense of humor you would see it that way, but guess what we are different and had Bug mentioned he spoke his dealer I would have left that off, but would still point him ni the direction of MPMASTER again due to the lack of what I seen as a lack of information.

 

 

HTH

[Kelly Burns]

quote:

---

Ron the pisser off of Men

---

Really, Ron? Tell em' how you really feel!

 

I think we all understand were Rons coming from with the redundancy of explanations, and it seems that most people dont do a search for questions before asking them. I wouldnt take it to personal; it just seems to be a trend lately.

[bigjohn]

Ron

Thanks for that interesting post. I do not need it now, but it's been archived for future use.

 

BTW I think the MPMaster and MPLMaster are great posts and very easy to tweak.

 

I have a lot of respect for Ron. He has given me lots of good help in the past.

 

Have a good weekend everyone

 

John

 

 

=========

[Bugzpulverizer]

Crazy Millman,

 

Thanks for all the info. I really didn't mean to start off on the wrong foot with you. You seem like you know your stuff, and I could learn alot from you. It's just that you seemed a little miffed by my question in the first place. I use V9 to program a burn table in our fab shop, and I use X2 to do my mill programming. I just hate drawing in X2. So I sometimes regress and go back and use V9 for my mill also. I figured if I got my V9 post the way I wanted it, I would just update it to my X2. Anyway, thanks again for trying to be patient.

Bug-z

[crazy^millman]

Ok guys I got his email and I can not be of assistance to him and could not be of assistance to anyone with this old of a post. I am not trying to pick on him, but I wanted to post up something for others to look before heading down this road to save you some trouble. The post is 1997 and it may have worked in V9, but I really do not know how. Look at this header:

 

code:

---

# -------------------------------------------------------------------------- 

#| MASTERCAM MP POST PROCESSOR | Always back up your post-processor |

#| CNC Software, Inc. | prior to making any changes. It's easy, |

#| Control Model: OSP5000 & 5020 | just put a floppy in drive a:, at DOS |

#| Machine Model: OKUMA MILL | type "COPY C:MILL6MPOKUMA.PST A:" |

#| PST File Name: MPOKUMA.PST/TXT | |

#| Executable : MP.EXE 3.12 | |

# --------------------------------------------------------------------------

#

# ---------------

#| REVISION LOG |

# ------------------------------------------------------------------------

# Programmers Note:

# CNC 5/12/94 - Initial post setup for Mill5

#$Lgb$

# 1.0 Jph 08/19/94 Initial source control check-in

# 1.1 jph 08/24/94 Correct coolant text

# 1.2 jph 09/02/94 Ques. 86. was 0.2 delay

# 1.3 pdr 09/06/94 Updated and corrected numbered questions

# 1.4 pdr 09/07/94 Updated reverse post name (q 93.)

# 1.5 jph 09/09/94 Updated drillcycle end Z pos.

# 1.6 jph 11/04/94 Remove question for cfg file

# 1.7 jpl 02/05/97 added vtol to system variable section for 4th axis accuracy

---

1st anything time your post is only 36K big red flag.

 

2nd Anytime the post exe says anything lower than V9 not a good sign either.

 

3rd Anytime the last time someone did anything to the post was 1997 a very bad sign.

 

Now I could have been wrong, but I was getting this feeling from the very beginning and again was not trying to be mean here, but been on this forum more than a couple days and you just get a sense when someone is creating more work for themselves than they need to. I again will point anyone to MPMASTER for Mill work and MPLMASTER for the Lathe work as these 2 post IMHO are very good starting points and have so much that I feel people can understand and use for all types of things.

 

As always I am trying to help, not trying to hurt and if you take it for face value that is what it is.