ptcuser.org is the place for info on ProE

I d/l file but all I see is 2 parts with .sldprt

extension... tried rename both to .mc9...but no luck

mross will probably chime in on this .. they liked them so much they bought 2

Post isssues ... Well what i saw at IMTS

MCAM finally in X has a program to create post

like about time !!

for sure back it up first.... and give it a try

Damn it's early

pheader area

you may be able to move the file name above the %

sign

if you change M30 to a M2 then edit at machine will it get past the server??

http://www.solidworks.com/pages/products/x...orks/index.html

is a good freebie

drw is Pro/e drawing file

but it's 2d

Rekd,

Totally agree.. done some of the same routines

VBS is okay but is really only a subset... why run on 4 cylinders when u can use 8.

Plus Mcam doesn't have to be running and hey most of the nccode tweaking works on our Pro/E files too

and if it doesn't you can just tweak your source a little

once it's posted...it don't matter...and then the operators can run your exe files and not have to get into the mc9 files

Seems I sent some source to ya once... have you check out instrRev... it's kind of cool works backwards... great for getting rid of extensions

Visual Basic is a real handy tool when doing things like this.. I program one part let VB ...not VBS do all the footwork... make multi's.. html setup sheets , load tool routines... send email to the operators to bag the nc code... I do use DoBitmapfile out of vbs.. but the rest is so much easier to control< less code> in true vb

I look at it a different way...

First thing to look at is how much more effectively can i use the software i have before I go out and get more

So I take the machine are reliable. Don't break down very often.

Real shame that where I work they really don't want to even check it out.. Have these part headed our way > could pair them up..bag the 2 edges, pairing makes 4 and 1 face.

would eliminate a good deal of fixturing also would give the mold people the 5 axis machine they have been wanting for quite some time.

But since they can get another Mori for 70k less thats what they are looking to do.Hmmm save 70k on the machine just to drop more on tooling, OT etc.

Alan,

I saw the 60t at ImTS... very impressive.

I'm looking at the 5 sided aspect of it more than the 5axis.. we may be picking up some work which would be ideal for it.

The sales team there pretty much says it's all in the control, no need for solid models or cam in general.. but then they are salesmen

Newcastle ehh.. I spent some time in East Anglia,

Go have a Nukie brown ale for me after work

Cheers

Anyone using this machine??

How does Mcam fit in the picture with it?

It's looks to me that the Heidenhain iTNC 530

takes care of it all.

I'm feeling the same way about the mori

The machine is nice in itself. But the controller

is user hostile, doesn't even show what tool is currently in the spindle from the tool offset page

The new model does but not our 6 month old one and not a software update option..

and Mr. Me-AGH-ee wasn't any help at IMTS either

the tall blonde chick was nice tho

I'd go for simple

Just hard code G0 G90 B0. and m-code if needed in the ptlchg_com routine of the post .After it has read the work offset , you may need to break that line into a couple of lines so you don't have 2 m-codes on the same line, just make sure it's before the "G43" line and after the w/o read

watch your commas and lil e's

And set your B offset in the work offsets of the machine, so it will B zero to that value, after all you are already there for your xyz offset values

hmm that leaves pallet check :)But then the machine can control that too.

From what I saw at IMTS 10 will have a program that helps one to setup a post now, instead of having to go thru all of this

We got 300+ work offsets, but no tooling

And lazy susaning the parts in and out is our current method

yes like robp says... you can M99 P(line number)

follow that sub with a M99 and it should return to line after the first call..works on our mori/makinos

you say,

but find no reference to this function in Fanuc manual.

Heck the mori manaul has more legal disclaimers than answers

So we got 3 Horz.<2-Makino A51 - 1 Mori NH5000>

We have some volume jobs on the Mak's , but it's been small lots on the mori. I feel and so do some of the others here that we really need a VMC to fill in the gap ... if nothing else remove some of the 2nd op stuff off the high dollar machines.

I want to submit a request to get us a vertical which is going to be met with some objections upstairs ... unless I have some bullet-proof points..... not my own

So if anyone has any links they would like to share or any type of good info in this direction... boy you make a lot of guys in the shop happy here

Looking at a VF-4 ....$80k

Tia

But maybe Bryan is on to something as it seems to work fine with just one op, as with the for/next

loop it gives the right value until you add another op then it takes a value z-.5 and makes it

-.9063....hmmm.....Oh Mick

Well the do loop gets the toolnumber fine

it doesn't return the zmax like before..picking up the r or initial plane

and the zmin kicks out a 16 place number to the negative umpteenth power

the for-next got all the other info ..

tlo, tdia, tlen, op type, tool comment,op comment

just weirded out when there is more than one op on the zmin

this is from the vbs script called getjobinformation that creates the html report

that came with the vbs update..I believe

Okay cool Bullines,

I just cut the code out the getjobinformation script and went from there.

Guess I owe you a cold one

I cut code to narrow it done and works fine if there is only one op but gives wrong value if more than one op.. if anyone want to gibe a try here is the script

--------------------------------------

' -- Start Script

Call Main()

Sub Main()

Dim intOperations, intOpCount, ToolNumber

' -- Get current files operation count

intOpCount = GetOperationCount(vbNullString)

' -- Iterate all operations

For intOperations = 1 To intOpCount

' -- Get our tool number

ToolNumber = GetToolNumberFromOperationID("",intOperations)

ShowString("tool# " & ToolNumber & " oper # " & intOperations & " zmin " & _

GetNciMinZFromOperationID("",intOperations))

ShowString("tool# " & ToolNumber & " oper # " & intOperations & " zmax " & _

GetNciMaxZFromOperationID("",intOperations))

Next

End Sub

oh yeah max seems to be doing right

I get min right if if I only have one operation.

And the vbscript help file shows only one parameter, but the source code(get job info) I have has two..... tryed it with just one and it bombed the script

I seem to be getting a different value than from the ops manager..any one else have this happen?

I can look at ops man and see that I am only going -.2 ... yet I get -.375 from the

GetNciMinZFromOperationID("",intOperations)

vbscode