8 hours ago, cncappsjames said:

As a Machine Tool Dealer AE, I cannot stress this enough. SO many people will fumble their way through, find a way that works-ish, then get married to that. Then WHEN issues crop up they may find themselves painted in a corner. I've last count the number of individuals I've had to untrain and retrain. Personally I don't mind it, it's part of the job, but let's face it, sometimes there's some ego involved and that can make for a difficult training experience if one is not open to change.

So, before you go down the 5-Axis MACHINE side blind, call your builder/dealer and schedule some training. It'll be worth the effort.

If only we all had dealer AE's with as much talent............

3 hours ago, Aaron Eberhard said:

While you're waiting, if you feel like being IT, you can hit Start menu, start typing "computer management," then, go to Event Viewer > Windows Logs > Applications and see if there's any errors in there that might point you the correct direction.  For example, on my system, I know how to crash Cimco editor.  It's not Cimco's fault, but it looks like I need to reinstall the C++ redistributable, I just haven't gotten around to that yet...

That's really convenient, because that's the only app I have that I can get to crash reliably which made a great screenshot:

Look at the Faulting Module Path, and start a googlin'.

I'll check that out tomorrow.   Thanks!

19 hours ago, cruzila said:

KILL your one drive

No dice.   Still waiting on Mastercam support.  

10 minutes ago, JParis said:

If you unchecked it and it is re-checked again, something restored it...

That makes me ask if there is Microsoft One Drive running?

If it is, it is set to backup that config directory and you'll have to either turn it off or remove that directory from being backed up..

 

I chased the One Drive issue for several hours until I figgered it out

Crap, sorry, I meant to say it's still unchecked.   

1 hour ago, JParis said:

Did you reopen your config file to make sure it had not reverted back to be checked?

It's a strange one I have never seen unless that box was checked

Yup, I opened config back up, and it's still checked.  

28 minutes ago, gcode said:

Doesn't Windows have an auto restart after crash switch as well?

It may, but this isn't crashing.   Or at least I'm not getting the dialog box anyways.   

23 hours ago, JParis said:

I was so hopeful.  Unfortunately the issue persists, same as with the guy in the other thread.  Gonna shoot my reseller an email, although I'm sure I'll get the standard "You're gonna have to call Mastercam for that one" response.   

9 hours ago, JParis said:

THANK YOU!!!!

I've had a number of issues since I installed 2024.  But the one that I haven't been able to fix, is that every time I close an instance of MC, it reopens as soon as I close it.  Then once I close that one, it stays closed.  Any ideas what could be causing this?

On 1/29/2024 at 10:05 AM, Aaron Eberhard said:

Don't want to speak for Ron, but pretty much the only time I ever made a new machine group was when I had to switch machines. 

Now that the workflow has... er... improved... 

Interesting, thats how I've always done it.  I think the main reason is because the setup sheet we developed uses the "Comments" section for setup notes.  So creating a new machine group lets you make a new set of comments for each op.  

Is there an advantage/disadvantage for doing it "your" way vs "my" way?  I'm always open to learning a better way.  

On 1/26/2024 at 6:57 AM, crazy^millman said:

That is what is not good about the new Machine Group process. I get the dumbing down of the software to meet to needs to everyone that use it, but for experiences users this new must must must direction sucks. I can use the like I did, but seems to be more trouble that it is worth. Now I have 4-12 different machine groups in a file unless doing turning then because that like always has not got any love or attention is not working in 2024. I send in a bug report and get crickets. Past the point of even trying anymore to report issues. I will just keep my head down do what I do to feed my family and see what direction the future takes me.

Ron, did you previously not use multiple Machine Groups?  I ask because, that's how I've always done it.  I've always made a new machine group for each "setup", or operation.  Just curious what you use to separate operations?  Do you just make separate toolpath groups?

1 hour ago, Johnward Holmeson said:

Sounds like they milled the walls first leaving stock on the floor, and used the flat bottom drill to finish the floor.  Interesting.

That's what it sounds like to me, but I wouldn't think a flat bottom drill would cut like that.  Maybe because the corners of the tool never touch?

1 hour ago, Chally72 said:

This is the flow I always taught as well. 

I've always done it this way as well.   Not having to change sim options is a huge plus though.

On 1/22/2024 at 10:01 AM, SlaveCam said:

Did you find a solution?

Sort of.  It has been working all day today.  The last thing I did to fix it was this;

Close Mastercam then press the “Windows” button (at bottom left corner of screen), then type “reg” the search should show a result with “Registry Editor”. Open this item and navigate to “Computer\HKEY_CURRENT_USER\SOFTWARE\CNC Software, Inc.”

Expand this folder and highlight the “Mastercam 2023” folder, right click it and select “Rename”. Change the name to “Mastercam 2023 old”.

It came back after that, but it seems to be working all day today.  We'll see if it sticks.  

7 hours ago, Jasond0530 said:

I've used these for that exact feature. worked well although cutting force wasn't considered.

used an endmill for the walls first.

ADF | Drills | PRODUCTS｜OSG

 

What am I missing here?  You used a flat bottom drill, to mill a slot?

7 minutes ago, crazy^millman said:

Since I have always used a Stock model as my first operation in Mill i didn't notcie a difference when doing this in 2024. Guess it is about time the software caught up to what I was already doing.

They have cameras, watching your workflow.  Next year I hear they're changing the name to RonCam 2025.  Still no subgroups or folders in levels though.  

4 minutes ago, AHarrison1 said:

New to 2024

Nice, REALLY like that feature.  

37 minutes ago, SuperHoneyBadger said:

1 - Make a Stock Model

2 - Put it at the top of the Toolpath Group, it HAS to be the first item in the list you have selected for Verify (so top of the group is easiest).

3 - Verify the group, and any toolpath after it, and MC will use that model as your stock.

 

This way you only need your 'initial' settings in the Stock Setup menu proper, and you can daisy chain your stock models for multiple ops by using the previous OP results as stock. I like the way it works now, faster workflow for checking individual OPS, or finish routines.

 

Oh wow, that's really nice.  Thank you!!

That's new to 2024?  Or just a trick I've been missing out on?

With the new verify options in MC2024, its says you can use a stock model, and it will create a mesh and use that for your stock for simulation.  I used to often use a stock model, so I didn't have to run through all of the toolpaths in verify.  It doesn't seem to be working though.  I choose the stock model, but there's still no entities in my stock panel.  

What am I doing wrong?

2 hours ago, Zoffen said:

Could be something to do with the system or chaining tolerances. I have had issues that were linked to different users using different config tolerances and this had a big effect of things.

Hope this helps!

I'll check this out tomorrow.    I also realized I don't have the newest update, and something is up with our maintenance.    Showing expired even though it shouldn't be.   Hopefully an update fixes it.   

A coworker built a holder using the exact same model and it worked fine.  So it has to be something wrong with my install.  

1 minute ago, gcode said:

Are these toolpaths using some plane other than TOP??

Try right clicking inside the Tool Manager and select "Create Tool Assembly"

This is a much better way to build tools assemblies IMO

MY mistake, that IS how I've been doing it.  In the internal tool manager, then creating a new holder.  Because I was wanting to build them separate from an assembly.  Doesn't work either way.  For now I'm building them in 2023, and I'll just have to import them I guess.  

1 minute ago, gcode said:

These two files came in OK for me in 2024

For the tool holder I translated it so that the gage line of the holder was at the orign ( Translate to Origin)

then used Solids/ Trim tp Plane ( Top) to remove the taper 

 

How are you doing this

I use the Mill Assembly Designer in the Tool Manager

I'm doing it inside of the toolpath parameters, then creating a holder, and choosing to "use geometry from a file"  

I used those same files, and they made a holder just fine in 2023.  Maybe I have a setting wrong or something.  

18 minutes ago, SlaveCam said:

I absolutely hate that error message, having spent hours and hours looking for "gaps" and whatever with custom tools. This error message needs to be more precise. Step files have however always worked fine in 2023 for me. If this is broken in 2024, then it is a showstopper

I've downloaded multiple tools and holders today.  From Pioneer, schunk, lyndex, and made a few tools myself, and I can't get any of them to work. 

4 minutes ago, gcode said:

can you upload a file that is not working properly

CAT50-SX16-0413.stp

10MM GOLD TWIST PILOT.STEP

I just upgraded to MC2024 and seem to be having issues building tools and toolholders from step files.  I'm doing it exactly the way I always have.  Orienting them so that the origin is at the tip of the tool, with Z facing into the spindle, and every time I get this message.  What am I doing wrong?