MC2026 Level manager

[gcode]

I'm using 2026.
Everything works for the most part, it just works differently and when some function I've been using for years clashes with my muscle memory and lizard brain autopilot, it can really throw me off my stride.

I remember how much people hated X. Many refused to use it for years.
I started here in 2007. I was using X2, everyone else was running the last release of V9
The lead programmer, a crusty old guy named Mike Wanke absolutely refused to move from V9

Years later, I was using X6 and he was still on V9 and failing miserably roughing a complex 3+2 part.
He was crashing, locking up and cussing up a storm.
This went on for a couple of days.
I finally asked him if I could show him something.
I opened his file in X6, spent several minutes building a 3D roughing toolpath using an STL file as stock.
It crunched for about a minute and produced a really sweet toolpath.
He looked at it a minute and said "Oh".
Then he went back to his PC and started learning to run X6.

The point of this story is
The new releases are always rocky and many people hate them just because they are different.
In the long run though our tools are steadily improving over time.

[neurosis]

Everything works for the most part, it just works differently and when some function I've been using for years clashes with my muscle memory and lizard brain autopilot, it can really throw me off my stride.

Is it easier to adjust to than it was to the ribbon interface?

[Newbeeee™]

Mike Wanke

Surely that's his p0rn stage name?

[gcode]

Is it easier to adjust to than it was to the ribbon interface?

yes.. I'm still not adjusted to the ribbon interface 

[JParis]

Is it easier to adjust to than it was to the ribbon interface?

IMNSHO, it's completely kludged up...a CF if I might....and I have expressed that opinion back to them

[Jeff]

it just works differently

If by differently you mean not at all,then I agree.
Specifically the file path fiasco. This is a deal breaker for me.
Can't copy/paste, can't edit it, nothing. Unless you want to use that stupid tree they implemented that takes 100 more clicks.

I have to post out to 2-3 different machines for every program, multiple times per day, this makes that SO much more difficult to do.

But hey, fret not..... they'll release an update in a few months, when they get around to it.

[gcode]

Can't copy/paste, can't edit it, nothing. Unless you want to use that stupid tree they implemented that takes 100 more clicks.

yes.. I hate that and I'm still pissed because I reported it almost 7 months before the release and they didn't fix it.

but

copy the path from Explorer, open the tree and paste
I have always done it this way, I just have to open the tree first now

[Jeff]

because I reported it almost 7 months before the release and they didn't fix it.

And that is why I refuse to use it, and have been more vocal about their incompetence and their IDGAF attitude.
They're pissing off way too many people and they don't seem to care as long as we keep paying maintenance.
Well that could end from us, it's my decision to make, and I'm getting closer and closer to retirement. 2025 could easily carry us that far.

[CNCAppsJames]

That's at least 2 versions that I've completely skipped because they were a dumpster fire.

I'm a dumpster fire... they work well for me.

Except for the file extension issue... that's bovine excrement... and we ALL know it.  

 

[CNCAppsJames]

IMNSHO, it's completely kludged up...a CF if I might....and I have expressed that opinion back to them

Ruh roh raggy.... you told 'em their kid was ugly. 


#NoSupportForYou

 

[CNCAppsJames]

yes.. I hate that and I'm still pissed because I reported it almost 7 months before the release and they didn't fix it.

but

copy the path from Explorer, open the tree and paste
I have always done it this way, I just have to open the tree first now

I keep my working folder(s) open for a variety of reasons. Copying the path from explorer is the way to retain what hair one has left. 

 

[JParis]

I have to post out to 2-3 different machines for every program, multiple times per day, this makes that SO much more difficult to do.

Just a different perspective....might you have a workflow problem instead?

I know from my point of view, I most certainly do not want multiple versions of the same program to maintain...

Now in my shop, this is somewhat easy to manage.....utilizing Cimco NCBase I will only maintain a "vertical" copy and a "horizontal" version, they are noted in the database what revision level they are currently....all the verticals can run the same program as can the horizontals.

I have implemented macros to handle on the HMC's the fact that some jobs run on several different tombstones. So I probe  hole on the tombstone to determine which tombstone is loaded and the G10 the correct set of offsets for the stone.

so I have

XXXXXVXX.eia

&

XXXXXHXX.eia

and with 14 vertcials and 27 horizontals they have access only the their respective programs...

Making sure setup people double check the revision is a harder issue but it is a work in progress.

I am working towards complete revision control of programs.

[neurosis]

and with 14 vertcials and 27 horizontals they have access only the their respective programs...

Do all of your machines have the same or similar controls?

[JParis]

Do all of your machines have the same or similar controls?

Yes... we're a 100% Mazak shop

If I had to, and had different controls, I would set up macro statements to handle everything in a single program

[gcode]

I keep my working folder(s) open for a variety of reasons. Copying the path from explorer is the way to retain what hair one has left.

I do that as well
copy /pasting file names/paths/part numbers/EDP #s/ etc is much faster and far less error prone that typing them in by hand