Okuma mill post

[Superfly]

i have an okuma osp700 control.

does anyone have a post for that control?

i have one but i was playing around nd screwed it up a little bit.

also, if anyone can give me some pointers on how to make simple changes in the post i would appreciate it.

i just don't know the "language".

thx.

[postman]

Hi Superfly,

Sorry I don't happen to have a generic version of that post, but you might get lucky. As for advice on making simple changes that's pretty broad. The post language in similar in some ways to "C" but unique. Learning to use it just takes many hours of study and practice like anything else. However, if you have a specific question on a simple change you can usually get enough feedback to find a solution.

There are two schools of thought on setting up posts. One is that your interested and want to spend the time to learn. The other is you don't want to fuss with the post, you just want your code to come out right so you can concentrate on programming and getting parts made. If your the latter then the most efficient thing to do is outsource the problem to a post developer.

Oh, and by the way - did I mention that I happen to be a post developer? Drop me a line and I'll see what I can do. If your problem is something I can answer in a snap I'll be happy to send you the info gratis. If it's more of a project or if there are a handfull of things you'd like your post to do but have just been living with, I can give you an idea what it would cost to set you up. Often a very moderate fee can smooth out your post and make your life a breeze. No more editing the .nc file. Just post it and send it to the machine. What more could a fella want? 'cept maybe next weeks lotto numbers !!!

Keep on keepin on

 

[Sem001]

superfly I have a okuma post that has been modified by dealer that works treally well if ya like I email it to ya

[Tony]

Sorry ( My Boo,Boo, Not yours Postman)

I wish I had more time to experiment with post building, via trial and error.

[ 12-07-2001: Message edited by: Tony ]

[Trevor Bailey]

I do not think talking openingly about dealer price structures in any area of the world should carry on. Prices differ for many different reason's. Please take note and contact whomever you must in a private manner.

[postman]

Trevor,

I didn't mention any prices and I'm not a dealer. I'm an independant contractor. But your point is taken. I'll be more selective on what I say in public. OK

[Simtech]

Talk to your dealer for the MP Post Processor Guide CD. This is the best way to start, other than trial and error.

Luc

[mikhael gutman]

Hello Superfly!

I made two posts for okuma mill .

1. I using for DNC.

2. I using, whan i runnig from control, this one support sub's

Both working OK. Which one you need?

Regards Mike

[dnguyen]

Hi Sem001,

I have the same problem with the Okuma post too,

This is the problem I have:

 

G90G80G40G0

G15H00

G0G90X-1.9743Y.9112A0.

S3000M3

G56H1Z2.

G71 initht 2.

G83X-1.9743Y.9112Z-2.R.2Q.1F15.

how can I modify in the post to change the "initht" to "Z" and "G15H00" to "G15H1?"

Any suggestion or advise you can give me

will be helpful.

Dnguyen

[postman]

Ignore this one. I accidently posted twice. Hey, I gotta get to Senior member somehow!

[ 12-13-2001: Message edited by: postman ]

[ 12-13-2001: Message edited by: postman ]

[postman]

The initht problem is probably because there in no format assigned to it. Look for your format statements (fmt). Use the same format that is used to set up your Z.

eg.

fmt Z 1 z # Z Axis ***

copy it and change as follows

fmt Z 1 initht # Initial Z hight

As for the H00, my guess is that this is hard coded. It will need to be set up to use a variable, unless you always want it to be H01 then you can just change the H00 to H01 in the post.

If you can show us your "psof" code then someone can tell you what to change.

 

[ 12-13-2001: Message edited by: postman ]

[Superfly]

Thanks everyone for replying,

Sem001, if you can please email a copy to me at:

[email protected].

a big problem i have with my current post is that it doesnt support sub prgm's.

and i would like to have it go to a certain position before it outputs an M06.

kinda like this:

G00G80Z1.M09

X-20.Z20.

M01

M06

And at the end:

Y20.

M30

there is more that i would like to do with this post but my boss is on my arse and i gotta get back to work.

thanks again all.

[dnguyen]

Postman,

Thanks for quick reply,

I have already change the "Z initht" it work good

now.

 

once again thanks for help.

This is the Psof.

 

dnguyen

code:

---

psof0 #Start of file for tool zero

psof

psof #Start of file for non-zero tool number

pcuttype

toolchng = one

if ntools = one,

[

#skip single tool outputs, stagetool must be on

stagetool = m_one

!next_tool

]

"%", e

"(PROGRAM NAME - ", progname, ")", e

"(DATE=DD-MM-YY - ", date, " TIME=HH:MM - ", time, ")", e

pbld, n, *smetric, e

pbld, n, *sgabsinc, "G80", "G40", *sgcode, e

sav_absinc = absinc

if stagetool >= zero, pbld, n, *t, "M6", e

if mi1 <= one, #Work coordinate system

[

absinc = one

pfbld, n, sgabsinc, *sg28ref, "Z0.", e

pfbld, n, *sg28ref, "X0.", "Y0.", e

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

absinc = sav_absinc

]

else, pwcs

pcom_moveb

c_mmlt #Multiple tool subprogram call

ptoolcomment

comment

pcan

pindex

if mi1 > one, absinc = zero

pcan1, pbld, n, *sgcode, *sgabsinc, pfxout, pfyout, pfcout, e

pbld, n, *speed, *spindle, pgear, next_tool, strcantext, e

pbld, n, "G56", *tlngno, pfzout, scoolant, e

absinc = sav_absinc

pcom_movea

toolchng = zero

c_msng #Single tool subprogram call

 

ptlchg0 #Call from NCI null tool change (tool number repeats)

pcuttype

pcom_moveb

c_mmlt #Multiple tool subprogram call

comment

pcan

pbld, n, sgplane, e

if prv_spdir2 <> spdir2, pbld, n, *sm05, e

if prv_speed <> speed | prv_spdir2 <> spdir2,

pbld, n, *speed, *spindle, pgear, e

pbld, n, scoolant, e

if mi1 > one & workofs <> prv_workofs,

[

sav_absinc = absinc

absinc = zero

pbld, n, pwcs, e

pbld, n, sgabsinc, pfxout, pfyout, pfzout, pfcout, e

pe_inc_calc

ps_inc_calc

absinc = sav_absinc

]

if cuttype = zero, ppos_cax_lin

if gcode = one, plinout

else, prapidout

pcom_movea

c_msng #Single tool subprogram call

---

[ 12-17-2001: Message edited by: Dave Thomson ]