No need to apologise. Some of these guys here are from Southern  American states and I struggle to understand their English

The way I see it, is you either alter your autolisp program to output long code removing the G83 and replacing all with long hand code, or you change your machine parameter for the rapid. Changing the rapid, will also change for all rapids though. So it would be best, to alter your autolisp program....

1 hour ago, NdrGhi said:

It's waisting time if not using G83 that defines every thing just in one line.

With mastercam changed to output G1 long hand instead of  the G cycles, you still 'gram as you normally would.

No difference.

Post automatically outputs long hand so your process is identical.

Program loads to machine identical.

Machine processes identical.

So i don't understand the "wasting time" because all the 'gramming and processing is the same - and it's only a ix off so let it run

11 minutes ago, jstell said:

But for stuff like if the clearance plane is 2" or .1", or if the coolant turns on at machine Z zero or after it gets down to clearance plane, that needs to be on the same page so the folks on the floor don't have to keep spare shorts in their locker on set-up days, or spare everything if you have a machine old enough to run with the doors open and the coolant start is different.

SO much this!

That's what I was referring to - standardisation so the operators get an easier time

54 minutes ago, jstell said:

The machine and control are saved in the mastercam file.  But any tool/operation libraries that point local will now be pointed to that users machine, as will the post if it is local (with the same name).  So if the post is not the same on one users computer and they re-post your file, it will post with the local post on that computer.

The best solution I've found for hybrid network/local use is to have a master copy of the machine, control, post, and tool libraries on the network, and let the control def point to local operations libraries.  That way users can have their default preferences for clearance planes and depth cuts, multi-pass, etc. set up how they are used to, but the machine/control/post is the same for everybody (and backed up somewhere else on the network).

The problem with all 'grammers having their different preferences, is unless they prove the prog on the machine themselves, you've got the operators seeing different settings etc.... and "someone" really needs to be overall control of everything (control/machine/posts) to avoid meddling, and to lock out everyone else.

"standardisation is a wonderful thing, if only people would do it"....

17 hours ago, gcode said:

I know it shouldn't be this hard, but it is what it is 

 

More clicks = Better errrr....

5 hours ago, NdrGhi said:

G00 is applied inG83( Drilling Cycle)

G01 can not be used.

Thanks

The point is, you don't have to use G83.

You can long hand code the drilling with plain 'ol Z values and F values....

The machine won't care....

Well done for looking at all the thorough questions.

Your boss is actually looking only at the price, where you are looking at the overall cost!

As G said, trials is the only real answer as everyone has different parts, different machines, different holders, different coolant, and different strategies with their 'grammin.

"(mostly)"

IF you really want to reduce the rapid for the drilling cycle only, I would long hand the code with feed....

1 hour ago, JParis said:

Man, I hope he didn't wait nearly 5 years for that answer.

JP, you can't rush these things. Everyone is busy, lots to do....

6 hours ago, Colin Gilchrist said:

This is where your Post Processor can be edited to properly track what is active, cancel it, retract safely, allow you to inspect/change inserts, and then output a proper restart block, with speeds/feeds, spindle on, and Tool Length Comp reinstated. I would hesitate to use Tool Inspection feature combined with Lead In/Out, because Tool Inspection feature only forces a retract move, it does not "also output lead in/out".

Absolutely - had my post dialled for inspection tool check too and it worked a treat, except the calculation for the distance was "reasonably inaccurate".

But it did stop, retract properly, and get going again properly, so it worked well for visual or changing inserts on a facemill.

If swapping out a solid because the edge has gone, obviously reset tool length. was needed, which meant handwheel and "reset" gets hit and....

Although I didn't do it much, I always used what JP suggests - force tool change.

Becuase this gave 100% correct retract/spindle stop, and more importantly, correct re-start procedure with H+D calls and G43 (talking Fanuc).

"Usual code", nice and easy where everyone in the shop has seen it a million times before so no worries.

Where stopping mid prog for tool wear check with the M00 and then press the go button again can lead to all kinds of crasheroos depending what the operator did, and how the machine parameters are configured (from different machine to different machine).

52 minutes ago, Mr. Saturday said:

Somebody noticed. I'm so happy.  

Attention to detail is my middle name 

LMAO at "Programmer'

Is your machine correctly configured - should your new machine actually be C and A?

Had a VMC delivered with rotary configured as B instead of A. Also customer had a Hori delivered with it set as C instead of B.... :shrug: 

11 hours ago, Mr. Saturday said:

It says Cancel?

Submit an enhancement request to "rename cancel to close"....

I ran X+ from Gunther.

1x click and it would give "cycle time"  for each path. And overall part.

And what the G5X work offset was called for each op.

And whether coolant was called or not for each tool. 

And speed and feed for each tool called.

And H And D for that tool.

1x click and within a second it was all there on the screen, so no searching etc. Right in front of you.... 

3 hours ago, Mr. Saturday said:

I like to believe CNC Software forgot how to care about their customers, but it seems they never really did?

I've said it quite a few times but I cannot believe how the guys were ignored....and I maybe mis-remembering, but I believe this event was the reason the late great Tim M (RIP) returned his dongle....

As we know, back in the day, there were so many guys top of their game in all different fields driving all types of machines pushing the SW and making parts that most would no-bid, all that resource was available to CNC....more than likely at zero cost.... 

2 hours ago, crazy^millman said:

I was present at said event.

YOU are indeed, the Great AND the Good!

4 hours ago, Mr. Saturday said:

but they need to back up a few steps, take a very brief look around the room

Ima auld enough to remember back in the Halcyon days, when the forum's great and good, were invited to Tolland for a very early Mill Turn look see. 

I believe, all suggestions, were ignored....

46 minutes ago, cncappsjames said:

I'm thinking they were 0-80's or 2-56 . 

It was either M2.5 or M3 roll taps. Bright finish, 10% coolant, in 6082-T6.

Very impressive. VERY impressive. But as we ran multi machines, no one was ever on a machine that was running, so threads were always reeled back to a nice steady predictable S+F, so around S2000/S2500. And the drilling+threading was only ever a minute or two in our parts, so it wasn't a time issue. Roughing and especially finishing was the time and what got pushed.

8 hours ago, cncappsjames said:

Been there, done that.

My max was 4k....that was like a riveting machine in out next in out next in out next....

Have seen vids of 6 although it didn't look *that much faster* ....

Dang.

OP will busta blood vessel if he ever saw a robodrill rigid tapping at 6k RPM....

Back to OPs original Q....I would screen grab, into Paintshop Pro, erase the WCS, save, and continue my day.... 

On 12/19/2024 at 5:40 PM, Mr. Saturday said:

And be sure to find something that gives you purpose and drives you to use the talents God gave you. Stagnation is a terrible thing. The term use it or lose it applies to your physical self and especially your mental self.

+EleventyBillTrillion