Hi Colin Is before the first tool change in this instance, works fine if it is an operation after other operations, ie. face then centre then call the tailstock. In this instance the parts are pre faced and centred, but we would still like the program to control the tailstock entry. Anyway here is the nci stream for the start of the program through to the first tool change, any ideas ? 1050 20 74 17 4 2018 10 39 19 V:\DRAWINGS\DRAWINGS\C.N.C\TEST.MCAM 20600 3518 6A1B4B60-B7A7-11DB-9DF8-001422F4251F "" "" Machine Base 20600 3519 6A1B4B62-B7A7-11DB-9DF8-001422F4251F "Z" "Z" Lathe Right Spindle Z Axis (<--+) 20600 3520 6A1B4B64-B7A7-11DB-9DF8-001422F4251F "A" "A" Lathe Right Spindle C Axis 20600 3521 6A1B4B66-B7A7-11DB-9DF8-001422F4251F "" "" Lathe Chuck 20600 3522 6A1B4B68-B7A7-11DB-9DF8-001422F4251F "Z" "Z" Lathe Left Spindle Z Axis (-->+) 20600 3523 6A1B4B6A-B7A7-11DB-9DF8-001422F4251F "X" "X" Lathe Upper Turret X Axis 20600 3524 6A1B4B6C-B7A7-11DB-9DF8-001422F4251F "Y" "Y" Lathe Upper Turret Y Axis 20600 3525 6A1B4B6E-B7A7-11DB-9DF8-001422F4251F "" "" Lathe Upper Turret 20600 3526 6A1B4B70-B7A7-11DB-9DF8-001422F4251F "Z" "Z" Lathe Left Spindle Z Axis (-->+) 20600 3527 6A1B4B72-B7A7-11DB-9DF8-001422F4251F "X" "X" Lathe Lower Turret X Axis 20600 3528 6A1B4B74-B7A7-11DB-9DF8-001422F4251F "Y" "Y" Lathe Lower Turret Y Axis 20600 3529 6A1B4B76-B7A7-11DB-9DF8-001422F4251F "" "" Lathe Lower Turret 20600 3530 6A1B4B78-B7A7-11DB-9DF8-001422F4251F "A" "A" Lathe Left Spindle C Axis 20600 3531 6A1B4B7A-B7A7-11DB-9DF8-001422F4251F "" "" Lathe Chuck 20600 3532 84945F2A-683C-11E8-BA22-74D43583F18E "" "" Chuck Jaws (Left Spindle) 20600 3533 84945F2C-683C-11E8-BA22-74D43583F18E "" "" Stock 20600 3534 6A1B4B7C-B7A7-11DB-9DF8-001422F4251F "Z" "Z" Lathe Right Spindle Z Axis (<--+) 20600 3535 6A1B4B7E-B7A7-11DB-9DF8-001422F4251F "X" "X" Lathe Upper Turret X Axis 20600 3536 6A1B4B80-B7A7-11DB-9DF8-001422F4251F "Y" "Y" Lathe Upper Turret Y Axis 20600 3537 6A1B4B82-B7A7-11DB-9DF8-001422F4251F "" "" Lathe Upper Turret 20600 3538 6A1B4B84-B7A7-11DB-9DF8-001422F4251F "Z" "Z" Lathe Right Spindle Z Axis (<--+) 20600 3539 6A1B4B86-B7A7-11DB-9DF8-001422F4251F "X" "X" Lathe Lower Turret X Axis 20600 3540 6A1B4B88-B7A7-11DB-9DF8-001422F4251F "Y" "Y" Lathe Lower Turret Y Axis 20600 3541 6A1B4B8A-B7A7-11DB-9DF8-001422F4251F "" "" Lathe Lower Turret 20600 3542 5400FA3C-9E81-11E7-BEE9-74D43583F18E "" "" Tailstock 20600 3543 84945F2E-683C-11E8-BA22-74D43583F18E "" "" Center 20601 3560 6A1B4B9B-B7A7-11DB-9DF8-001422F4251F 0 Left/Upper 20601 3563 6A1B4BA6-B7A7-11DB-9DF8-001422F4251F 0 Left/Lower 20601 3566 6A1B4BB1-B7A7-11DB-9DF8-001422F4251F 0 Right/Upper 20601 3569 6A1B4BBC-B7A7-11DB-9DF8-001422F4251F 0 Right/Lower 999 218 0 1 1016 1 0 218 1 0. 0. 0. 41 -1 1 0 0 0. 0 0 0 1 0. 1 950 0 0 0 3560 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1025 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1020 135. 19.05 19.05 -67.5 0. 0. 0 0. 0. 0. 0. 0 0 ALUMINUM mm - 2024 911 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 912 0 0 0 0 0 0 0 0 0 0 904 1 100. -5. 999 60 0 2 1051 Mplmaster Generic 3/4 Axis Lathe - post testing 1053 Machine Group-2 1008 Rough 1011 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 1012 0 0 0 0 0 0 0 1 0 0 1013 0 0.8 0. 0 5 0. 0. 0. 101 MVJNR 2525M 16 - R08 1014 0. 1. 0. 0. 0. 1. 1. 0. 0. 1016 2 0 60 1 0. 0. 0. 42 0 1 0 0 0. 12 1 2 2 0. 2 1017 1. 0. 0. 0. 1. 0. 0. 0. 1. 950 0 0 0 3560 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1025 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1027 1. 0. 0. 0. 1. 0. 0. 0. 1. 0. 0. 0. 1020 135. 19.05 19.05 -67.5 0. 0. 0 0. 0. 0. 0. 0 4000 ALUMINUM mm - 2024 20010 Top 20011 20012 Lathe upper left 20013 20014 Top 20015 20016 ALUMINUM mm - 2024 20017 20018 Toolpath Group-2 20019 20001 MVJNR 2525M 16 - R08 20002 NONE 20100 2 0 1 0 0. 1 12 12 1 20101 Thanks

What would I need to add or change in my ptailstock post section here ptailstock$ #NCI code = 904 available variables: #tlstck_on, stck_init_z, stck_final_z if toolchng <> two, ptoolend$ toolend_flg = zero #Do not execute ptoolend again after xfer [ !spaces$ spaces$ = zero pbld, n$, "M01",e$ if prv_spaces$ > 0, " ",e$ if tlstck_on$ = 0, [ pbld, n$, "M05",e$ pbld, *sm26, "(Retract Tailstock)", e$ pbld, n$, "M712", "(Tailstock Interlock Off)", e$ ] if tlstck_on$ = 1, [ pbld, n$, "M05", e$ pbld, n$, "M625", "(Work 1)", e$ pbld, n$, "M434", "(Thrust 1)", e$ pbld, *sm25, "(Engage Tailstock)", e$ pbld, n$, "M713", "(Tailstock Interlock On)", e$ ] if prv_spaces$ > 0, " ",e$ spaces$ = prv_spaces$ ] To get it to output after my header section like this % O0000(TEST) (PROGRAM NAME - TEST) (DATE=DD-MM-YY - 01-06-18 TIME=HH:MM - 08:34) (MCX FILE - V:\POST DEVELOPMENT FOR CRAIG) (NC FILE - C:\USERS\MCCLAY\DOCUMENTS\MY MCAM2018\LATHE\NC\TEST.NC) (MATERIAL - ALUMINUM MM - 2024) (POST DEV - IN-HOUSE SOLUTIONS INC.) (TOOL - 12 - MVJNR 2525M 16 - R08 - OFFSET - 12 - INSERT - VNMG 16 04 08 - HOLDER - MVJNR 2525M 16) (TOOL - 2 - MVJNL 2525M 16 - R12 - OFFSET - 2 - INSERT - VNMG 16 04 12 - HOLDER - MVJNL 2525M 16) (TOOL - 4 - MVJNL 2525M 16 - R12 - OFFSET - 4 - INSERT - VNMG 16 04 12 - HOLDER - MVJNL 2525M 16) M01 M05 M625(Work 1) M434(Thrust 1) M25(Engage Tailstock) M713(Tailstock Interlock On) G21 (TOOL - 12 OFFSET - 12) (MVJNR 2525M 16 - R08 INSERT - VNMG 16 04 08) (ROUGH) G54 N12 T1212 M611 G0Y0 G18 G99 M46 G97 S56 M03 G0 Z-1.263 M8 G0 X254. G50 S4000 G96 S45 Is currently out putting above the % sign at the top of the NC code. Thanks

Finally got around to setting up the Fixtures utility. Excellent little utility. Thanks heaps for producing and sharing this Gunther.

Works a treat. Much appreciated Gunther. Thanks Mark

Hi Gunther Yes filling in the tool manufacturer name worked. Removing this from our selection to be displayed also worked. This did used to work fine in all the previous versions before MC2019 without the tool manufacturer being filled in, it would just leave the space blank and not cause a crash. For us we have a lot of tools in our library where the tool manufacturer was not filled out due to the very limited selection mastercam used to have. Anyway love the product and look forward to the fixed version when you get around to it. In the mean time I will just run without the tool manufacturer column Thanks Mark

Hi Gunther Trying to use the attached template file but it causes MC2019 to crash every time. This is a new template that I created through x+ in MC2019, but is laided out exactly the same as we have been using for the last few versions. default - McClay.template

great stuff , Thanks

Be careful though as you are now verifying potentially different to what the machine is doing !!

here http://forum.mastercam.com/Topic25936.aspx

now now, all machines have issues, some are just harder to swallow ;-)

Nope not dog legs , been tested and proven to be a software issue on the Control. But I here what you are saying about G0 vs G01

Hmm, Interesting. When we are doing surfacing work we have to either run it in Feed Mode (G01) for all rapids or manually set the rapid over ride to 5% or we get gouging on some of the rapid re-position moves.

Posted out your file with our Postability UMC750 post that is pretty dialed and the code looks very similar to yours, well certainly in the important areas. So sounds like you have a machine or machine setup error.

Hmm definitely an odd one. Something I think CNC software will have to take a look at.

As your probably aware there is a processing stage between NCI and NC code so there is potential for an error to come in at that stage but it is weird that Cimco pro didn't show the error if it is a bad code error. If you manually override the feed rate at the machine and slow the feed down does it still clip the corner , this would prove if it is bad code or the machine not following the code correctly.

Sounds to me like it's your machine not keeping up with itself on the back feed or rapid. HAAS will round a corner in G0 rapid mode by 60 thou according to there tech and as GF8er has stated they can also clip square corners if you are pushing them fast.

As he said ! Postability here. With some custom tweeks added including the HSM options, deep hole drilling cycle and some retract homing control. Generally pretty fast with response even going third hand through our reseller.

No the same thing. When you change tool numbers the op doesn't go dirty sometimes and retains the old tool number. I had this yesterday when I renumbered the tools in a file and then tried to use the Vericut to mastercam interface to generate my tool file for vericut. The posted code used the right tool numbers but the vericut file used the old numbers until I regened all the operations.

Safest way is to extend the line out from the surface (so towards where you want the cutter to come from) and then trim it back to the point at the start of the hole. Now when you select them choose points and lines and select the point at the end of the line. Now with the axis line only extending in one direction there is only one control direction possible. Use the linking page to get the required depth, clearance etc Apparently we will finally see the option to create these drill control lines "above" and only above the hole with the model prep hole axis function in a future release saving the laborious task of extending and trimming them back manually.

hmm, you are correct JParis, we do have that .lic file for the metric tools but there is only one "kennamet.toodb" file and this is all imperial tooling, so even with mertic sizing ticked in the tool manager we are getting converted imperial sizes ?

Old post but I am wondering if anyone has a copy of the X Kennametal Lathe Tooling(mm) ? The only version that is supplied with lathe these days is an inch one. Thanks

It's there, not simple but do-able , Thanks Colin

Is there an easy way to limit the number of output characters from these two post lines sopen_prn, "MCX FILE - ", *smcpath$, *smcname$, *smcext$, sclose_prn, e$ sopen_prn, "NC FILE - ", *spathnc$, *snamenc$, *sextnc$, sclose_prn, e$ thanks

What sort of path are you cutting ? I had a similar problem a couple of years back with an advanced 5 axis path (Module Works). It was a simultaneous path deep in a cavity with dynamic tilting collision avoidance. I had programmed the left hand side with no worries and had a nice path but when I tried to do the right hand side it just kept bugging out on me, spent hours trying to work it out. In the end I changed the step over by a few microns and it worked perfect, pretty much a mirror of the left hand one , go figure ! Oh and if I went too many microns either way from the original path it wouldn't work either, so there was a sweet spot of step over. So hopefully this might help you but I also think that there is no way you could train for this !! My two cents.

Standing will be better for your hemorrhoids Mike