X2 Remachine Problem

[MattMj]

I’m having a problem with Mastercam x2 when remachining large programs. I’m getting shutdown with the following error.

 

 

 

The instruction at “0x0bb652e0” referenced memory at “0x0bb652e0” . The memory could not be “read”.

 

 

 

This happens when I copy a pocket down and change the tool to remachine with a smaller tool. When I regin the program it locks up.

Also I tried reallocating memory in the toolpaths and it did no good. So I gave up and opened the same drawing in version X. I set it up the same way and remachine works fine. Just to satisfy my curiosity I then opened the (same working) drawing in X2 and regenerated the path and got the error in the message.

Also If the part is created in Mastercam the remachine works fine without the finish pass turned on. Only files brought in from Solid Works as parasolids seem to have this problem.

[Thad]

quote:

---

This happens when I copy a pocket down and change the tool to remachine with a smaller tool. When I regin the program it locks up.

---

Someone just asked about this last week. It is a bug that should be fixed in MR1. Until then, you could use Contour-Remachine.

 

Welcome to the forum!

 

Thad

[MattMj]

Thanks for the welcome Thad. I searched the topic and found I'm not alone. I changed back to version X to get the job done for now. I hope MR1 comes out soon because I use remachine allot.

Thanks Again,

Waiting not so patiently,

Matt

[mig]

This bug must be remove not in mr-xxx, is this really fare that people must pay for fixing BUGS?

[Thad]

quote:

---

It is a bug that should be fixed in MR1.

---

Correction...SP1.

 

BTW, any bug fixes that are in a MR will be included in the next SP. IIRC.

 

Thad teh acronym

[scooch8292]

I also have had this issue using pocket/remachining. MX2 locks right up and when I reopen the file, all my toolpaths need to be regenerated.

[Thad]

I just thought of something. Do you have use tool's, step, peck.... setting checked? This will change the machining parameters to match the new tool selected. Perhaps there is some setting in the new tool that conflicts with (or just plain freaks out) the remachine path and it craps out on you. Just a thought.

 

Thad

[Dan_AKA_ROY]

EDIT... Disregard this post. (pocket re-machine works fine)

 

[ 04-16-2007, 11:26 AM: Message edited by: R.O.Y. 23 ]

[Keith @ Solid Code Solutions]

Try setting the following field to say 15% and see what happens.