2024 Verify

[JParis]

IN my new position I haven't been programming in Mastercam since we installed 2024....

I am trying to run Verify on a part that's going on a 3 axis vertical....

Have we gotten to the point where you can't verify if you don't have a machine setup for it?

I keep getting a "Cannot Load the machine configuration files"...

I don't have any for this machine, I surely don't need any....

So 2024 can't run a simple verify or am I just missing the mark wide?

[neurosis]

Have we gotten to the point where you can't verify if you don't have a machine setup for it?

I keep getting a "Cannot Load the machine configuration files"...

I don't have any for this machine, I surely don't need any....

So 2024 can't run a simple verify or am I just missing the mark wide?

I think you asked that question a while back.  Same question? 


https://mastercamforums.com/forum/index.php/topic,2236.0.html

[JParis]

Like I said ain't done much grammin' lol

[Dylan Gondyke]

Just a note that verify uses elements of the machine config in the background, even if it doesn't seem like it needs them. This isn't a recent change, but it's probably most likely to occur on first use of migrated files/opening of older files and such where the machine data doesn't quite align.

[CNCAppsJames]

Just a note that verify uses elements of the machine config in the background, even if it doesn't seem like it needs them. This isn't a recent change, but it's probably most likely to occur on first use of migrated files/opening of older files and such where the machine data doesn't quite align.

So what's the solution/fix?

I rarely run Verify, but I wanted to on a new project for a machien fit check and no matter what, I was not able to run verify.

[Dylan Gondyke]

Very likely, there's something wrong with the machine definition. Invalid axis combo, etc etc. If you have a simple file that demonstrates the issue, please send it over and I can take a look. This is most prevalent with machine definitions created long ago and migrated many many times, as data that was once allowed/never checked now matters more and more to Verify and other areas of the software. If you reload the machine with the disk copy in a file that has these issues, you probably have a good chance of solving this as well.

[CNCAppsJames]

I'll create a new MD/CD from a default one from the install and check it out.

[JParis]

I've still been so busy with other stuff, I haven't even had a moment to get back to my issue...

I want to be a a manager I said, sure I'll take over the 3d printing dept I said, yeah, I can take care of writing the procedures for everything, sure I can get involved with the next generation of program and file retention, yeah, I can work with QC to determine better, more consistent inspection techniques and the list list goes on....

Thankfully my 2 guys are chewing through the programming, even the new guy is chewing through parts....

I think you get the point lol

[MIL-TFP-41]

So what's the solution/fix?

I rarely run Verify, but I wanted to on a new project for a machien fit check and no matter what, I was not able to run verify.

Machine Definition Manager - General Machine Parameters - Simulation Tab - check the box named "Use selected external machine" - pick whatever 5 ax machine you want.

I pick the 5AxHeadHead for all machines. It is the only one that doesn't bring up the annoying machine preview that doesn't look like any machine on the planet. And for simulation it doesn't matter.

[CNCAppsJames]

Machine Definition Manager - General Machine Parameters - Simulation Tab - check the box named "Use selected external machine" - pick whatever 5 ax machine you want.

I pick the 5AxHeadHead for all machines. It is the only one that doesn't bring up the annoying machine preview that doesn't look like any machine on the planet. And for simulation it doesn't matter.

That was the ticket!

Thanks!

[MIL-TFP-41]

Correction on my part

I pick the 5AxHeadHead for all machines. It is the only one that doesn't bring up the annoying machine preview that doesn't look like any machine on the planet. And for simulation verify it doesn't matter.

Correction on my part. For verify it doesn't matter. Where I think this is eventually headed is Mastercam will force people into using the eye candy stuff. I can see a day where user edit posts will be a thing of the past & things will be as clunky as mill-turn for everything.

[JakeL]

Just a note that verify uses elements of the machine config in the background, even if it doesn't seem like it needs them. This isn't a recent change, but it's probably most likely to occur on first use of migrated files/opening of older files and such where the machine data doesn't quite align.

If I understand this correctly, older machine / control definitions will need updates before running MC2024 verify? Most of our MD / CD are 15-20 years old and we update to MC24 on Jan 1st. It would be nice to know if this will be an issue before it becomes an issue.

Follow up question, are we referring to verify or simulate here, or both?

[CNCAppsJames]

@JakeL,

I was referring to Verify. I don't use MockSim. Ever. I have CAMplete.

[TSmcam]

@JakeL,

I was referring to Verify. I don't use MockSim. Ever. I have CAMplete.

LOL @MockSim....

[Dylan Gondyke]

Jake, MD/CD files are always migrated to the newest Mastercam version- there's nothing strange or extra going on. James sent me his file so I can take a peek later today.