Today I ran a program on a Mori Mill, I loaded the proven program, the part has been done many times before, and the work offsets (G55, G56) are recorded on the back of the print. So I input them, The part is a pre-manafactured fiberglass box done in a Hass rotary, (I cut a retangular cutout in the top, and two small holes in one side.

Pushed cycle start, it looked like everything was good. I measured the width and diameters of the cutouts, (needed to offset the tool -.005 to get the right sizes. I pushed cycle start (This time the toolpath in the top of the box ran out about a 1/4" in the Y axis, the tolpath on the side the box ran the same.

I had 20 parts to run. After that 1st part everything was good??? Any ideas why the 1st cycle cut 1/4" off. (I changed nothing!!!)

Is the decimal point after your R on line 140 causing it?

I worked at a shop where we had to polish portions of a part with a 10" grinder,(with a sanding disc followed by a scotch brite pad), the machine was a VTL with 14' table. The part was only about 8' in diameter, so we would lay on a platform held over the spinning part with the fork lift. It was the only way to do this. VERY DANGEROUS!!!

I'm glad I don't work with the large parts (up to 30 tons)anymore!

At the top of the operations manager between the locking and ghosting icon's is a toggle display switch for this.

(3 wavy blue lines).

I tried a quick similar shaped part in X5, and X4, with optimize cut order on and off. Same-Same. If you change the machining angle of cut from 90 degrees (Your tool path) to 0 degrees, theres a big difference in rapid moves.

I would like to know what you find out on this.

I think it depends on what type of work you do, and how the shop is tooled up. If you are doing a lot of drilling with different size holes I find it faster to use drill chucks.

All the shops I've worked in use HSS Drills, so what UParis said didn't apply.

Try doing a google search for cutting optimization software, or material yield software. There's many different ones to choose from "out there"

I plugged the holes, and used boolean remove.

Is this what your after? See attached file, (if I can figure out how to attach it)

Version 9 is NOT supported and will not run on Windows 7.

Help

 

I spilled water on my laptop and crashed my hard drive. I loaded Mastercam V9.1 on my new home computer(Window 7) and it says hasp not found when start Mill. The computer has the latest divers for the hasp loaded.

 

Thanks in advance

Are you creating a new toolpath group before you create the new WCS? You might try that.

I've found that it matters where the red arrow is in your toolpath groups.

Have you checked the system configuration under CAD Setting, Is there a check in (reset Cplane to Top in Iso Gview)?

All the machines have com. cables to them, and you can send programs both ways.

The only odd thing is that they have three separate com. cables coming from 3 separate ports on the back of the computer. I am fimiliar with building the com. wires, as I said earlier the computer is old, and running Windows 2000.

I will try changing the machine definition for the lathe. (I wondered if that would work).

Thanks everyone.

THANKS! That's what I needed to know. They need (and are willing) to get me a new computer,

so we will go from there.

This is a mom & pop job shop, The owner and his son are the only one's in the shop. They don't know anything about

the CNC's. They are not cheap owners. The owner was not aware of the lathe not functioning properly, as the previous programmer

failed to let him know.

They are trying to bring the shop up to date, and are willing to buy a new computer for me, etc. etc.

I do need to know if anyone has dnc the Fanuc controls that I mentioned above?

Again thanks for you advise.

X- is towards the back of the lathe, X+ is towards the center of the chuck.

Also G02 and G03 are inverse.

The MPG is marked accordingly. And to move it away from the machine home, you have to turn it opposite of other lathes.

And the worst part is that they had a board replace a couple of years ago that makes feed hold and single block mode inoperable.DANGEROUS

I just started working for a place that has "older" machines then I'm use too.

I will start with afew questions. Does anyone know if a 1986 Kitamura Mycenter 3b mill with a Fanuc 11M control can be DNC'ed?,

or the Mori Seiki MV-35 mill with a Fanuc 6M B control?

I will also need to know if anyone is willing to help with a post mod. for the Mori Seiki SL-1 lathe with a Fanuc 6T control.

this lathes x axis is backwards from all the other lathes I have programed. Also the tool offsets are from the center of your part.

They have been using Mastercam version 9 and a computer with Windows 2000. They are willing to buy a new computer, so I can run my seat of

Mastercam X5.

I have tried DNC'ing both mills with no succes. I put the machine in TAPE mode and pushed cycle start, and I was using mastercams communication

for sending. Did not work, on either mill.

Please help, and a big thanks to those of you who respone!!!

I would like to know if and with what version it is possible to save your toolbar states to a memory stick?

I'm starting a new job in about a week and would like to save my toolbar state from X MR2 on a memory stick and load it from the stick at my new job. Would this be possible?

In backplot the lead in and out are not showing up.

I just tried to do a pocket toolpath in x3 with a finish path with lead in and lead out, using a line tangent and arc for the lead in and out and it does'nt work now. In x2 it did.

Anyone else have this problem?

Roger

Steve, here is the section on ptap

ptap$ #Canned Tap Cycle

pdrlcommonb

if use_rigid = 1, result = newfs(12, feed)

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

prdrlout, strcantext, n_tap_thds$, *speed,",R1" e$

pcom_movea

pbore1$ #Canned Bore #1 Cycle

pdrlcommonb

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

prdrlout, dwell$, *feed, strcantext, e$

pcom_movea

pbore2$ #Canned Bore #2 Cycle

pdrlcommonb

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

prdrlout, *feed, strcantext, e$

pcom_movea

pmisc1$ #Canned Misc #1 Cycle

pdrlcommonb

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

prdrlout, shftdrl$, dwell$, *feed, strcantext, e$

pcom_movea

pmisc2$ #Canned Misc #2 Cycle (User Option)

Thanks, guys, BUT I need it simplified..Here are those lines in my current post. Is there a way you can highlight what needs changed?

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$

*progno$, e$

"(PROGRAM - ", sprogname$,")", e$

"(DATE=D-M-Y - ", date$, " TIME:", time$, ")", e$

pbld, n$, *smetric, e$

pbld, n$, *sgcode, *sgplane, "G40", "G49", "G80", *sgabsinc, e$

sav_absinc = absinc$

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

]

pcom_moveb

c_mmlt$ #Multiple tool subprogram call

pbld, "N", e$

ptoolcomment

comment$

pcan

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

pindex

if mi1$ > one, absinc$ = zero

pcan1, pbld, n$, *sgcode, *sgabsinc, pwcs, pfxout, pfyout,

pfcout, *speed, *spindle, pgear, strcantext, e$

pbld, n$, "G43", *tlngno$, pfzout, next_tool$, e$

pbld, n$, 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$

pspindchng

pbld, n$, scoolant, e$

if mi1$ > one & workofs$ <> prv_workofs$,

[

sav_absinc = absinc$

absinc$ = zero

pbld, n$, sgabsinc, pwcs, 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

ptlchg$ #Tool change

pcuttype

toolchng = one

if mi1$ = one, #Work coordinate system

[

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

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

]

pcom_moveb

c_mmlt$ #Multiple tool subprogram call

pbld, n$, "M01", e$

pbld, "N", e$

ptoolcomment

comment$

pcan

pbld, n$, *t$, "M6", e$

pindex

sav_absinc = absinc$

if mi1$ > one, absinc$ = zero

pcan1, pbld, n$, *sgcode, *sgabsinc, pwcs, pfxout, pfyout,

pfcout, *speed, *spindle, pgear, strcantext, e$

pbld, n$, "G43", *tlngno$, pfzout, next_tool$, e$

pbld, n$, scoolant,e$

absinc$ = sav_absinc

pcom_movea

toolchng = zero

c_msng$ #Single tool subprogram call

I'm trying to modify the standard hass post to output code for tapping. The following is the code I get now.

( 8-32 TAP RH DIA. - .168 )

T15 M6

G0 G90 G54 X-1.049 Y0. S500 M3

G43 H15 Z.25

M8

G99 G84 Z-.81 R.25 E32. S500 ,R1

X1.049 F15.625

G80

M5

Z.25

G91 G28 Z0. M9

G91 G28 Y0.

M30

%

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

Would like it to read the following.

( 8-32 TAP RH DIA. - .168 )

T15 M6

G0 G90 G54 X-1.049 Y0.

G43 H15 Z.25

M8

G99 G84 Z-.81 R.25 E32. S500 ,R1

X1.049

G80

M5

Z.25

G91 G28 Z0. M9

G91 G28 Y0.

M30

%

Don't need the S500 M3 or the F15.625

Thanks to those who respond. Roger

I gave it a try on my last job. It's extremly slow. Even creating simple geo.

Roger