Simulation unknown error

[So not a Guru]

When programming our 5X router, when we go to run verify, we get the error "An unknown error has occurred". close MC, restart the program, and verify works fine.
Anyone know what might fix this?

On a side note; can we not attach an image from our local drive on here?

[Dylan Gondyke]

In 2022 and earlier, a lot of verify issues can be solved by jumping into the Simulator Options button from the toolpath manager and just toggling the Machine selection to something else and then back to the proper selection again. (Or doing the same thing with Stock selection, to "jiggle the handle")

If this is happening in 2023, interested in the file or scenario where you see this.

[Jeff]

Which simulation? Mastercam's simulator or ModuleWorks simulator?
You might get a better explanation if you use Modulework's simulator. I had the exact same issue last night in 2023 and it pointed to the toolpath that was the problem child.

[Dylan Gondyke]

Jeff, I got your file by the way, thanks. That's a strange one. It looks to be solved already for 2024, but still exploring.

[So not a Guru]

In 2022 and earlier, a lot of verify issues can be solved by jumping into the Simulator Options button from the toolpath manager and just toggling the Machine selection to something else and then back to the proper selection again. (Or doing the same thing with Stock selection, to "jiggle the handle")

If this is happening in 2023, interested in the file or scenario where you see this.

Thanks Dylan, I'll give this a try today. We're still on 2022, have there been updates to 2023 yet?

[gcode]

have there been updates to 2023 yet?

2 updates so far

[Jeff]

Jeff, I got your file by the way, thanks. That's a strange one. It looks to be solved already for 2024, but still exploring.

I was hoping it was just a glitch, but since I saw this thread, I guess it's a bug.

[So not a Guru]

In 2022 and earlier, a lot of verify issues can be solved by jumping into the Simulator Options button from the toolpath manager and just toggling the Machine selection to something else and then back to the proper selection again. (Or doing the same thing with Stock selection, to "jiggle the handle")
is.

It has been working correctly lately, until just now. Toggling the simulation machine, nor changing the stock selection appears to work. Only shutting and restarting MC seems to fix it.

[MIL-TFP-41]

Is this in simulator or verify?
If its in verify, turn off collision checking.
I hoped to see this fixed in update 2, but it doesn't seem to be high priority.
I did a bug report on this on the initial release.....

[So not a Guru]

Is this in simulator or verify?
It its in verify, turn off collision checking.
I hoped to see this fixed in update 2, but it doesn't seem to be high priority.
I did a bug report on this on the initial release.....

Well that blows, collision checking is what I'm checking for with verify. And since we're still using 2022, we'll never see it fixed,

[MIL-TFP-41]

Well that blows, collision checking is what I'm checking for with verify. And since we're still using 2022, we'll never see it fixed,

Just saw that you are using 2022....I get his error in 2023, so disregard.....

[neurosis]

Well that blows, collision checking is what I'm checking for with verify. And since we're still using 2022, we'll never see it fixed,

One of my peeves with Mastercam is that they abandon old versions once a new version is released. If you're stuck with that version, you're stuck with all of the bugs that are left once their focus shifts to the new version.  Is that common with most cad/cam software?

This is one area that I have to give TopSolid some kudos.  We dropped our maintenance earlier this year before their new release came out.  They've moved on to the new version of TS and yet we still got and update with bug fixes for the previous release of TopSolid. Not sure how long they support the previous versions.  I guess I'll find out.