[Corvus]

My Rhino5 64 bit with the latest service release starting crashing when trying to load madCAM after I updated Windows 10 with the following update:

2017-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4019472).

Uninstalling this update fixed the problem.

[grahamkirkland]

My Rhino5 64 bit with the latest service release starting crashing when trying to load madCAM after I updated Windows 10 with the following update:

2017-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4019472).

Uninstalling this update fixed the problem.

I have the same problem. Uninstalling the Windows 10 update is not a permanent solution. From a security point of view, I don't like not being up to date on Windows. There must be another way to fix this.

[Dan B]

Yup, same here. I'll let Joakim know. We're due for a service release anyway.

Dan

[Dan B]

Joakim has a fix already. The next service release isn't quite ready but he's going to provide a pre-release today for those who are unable to use madCAM in 1607. I've just tested it, and it's working for me.

Dan

[Corvus]

That's great that Joakim has a fix available already!

I see that he's made it available on his Downloads Page

[Dan B]

There are some new features for profiling included. There is now lateral step-overs, and helical profiling by defining the pitch. I usually help test these pre-releases before they go public, but the Win 10 issue has forced Joakim's hand, so if you find anything that isn't working right (besides material removal in the simulator) please speak up so it can get fixed.

Dan

[Corvus]

Thanks very much to Joakim for such a fast fix!

It's working really well here. I'm having to re-write my scripts but it's well worth it for the new profiling features.

I'm still having problems with changing feeds and speeds with the same tool which I posted about in more detail in this thread.

[Corvus]

Reviewing the problems I encountered in this thread from 2015

The problem with scripting the MC_Profiling command is fixed - Thanks Joakim!

However -MC_Box command is still not scriptable. I've found a way to work around this but I still want to bring it to Joakim's attention because the ability to script madCAM commands makes a huge advantage for any production environment where the user is applying the same tool path commands to parametric models which vary for each job.

[grahamkirkland]

There are some new features for profiling included. There is now lateral step-overs, and helical profiling by defining the pitch. I usually help test these pre-releases before they go public, but the Win 10 issue has forced Joakim's hand, so if you find anything that isn't working right (besides material removal in the simulator) please speak up so it can get fixed.

Dan

I will add my 2c here. I installed the update to fix the Win 10 problem and Madcam has now become quite unstable. It simply stops working after a while and I have to restart Rhino to get it working again. The time to fail is random and can be anything from a couple of minutes to maybe 15 minutes. Rhino continues to work fine.

[fishtriangles]

Joakim has a fix already. The next service release isn't quite ready but he's going to provide a pre-release today for those who are unable to use madCAM in 1607. I've just tested it, and it's working for me.

Dan

I have the installations up to date and madCAM is working again, but won't post error says my tool doesnt exist but the toolpath was created. Ideas?

[Dan B]

Go to the options and make sure that you're pointed to your proper template. The template should contain the machine model (if you have one), the tool library and the post.



Your files will most likely be in C:\ProgramData\5XCNC\madCAM\5.0.

Dan

[fishtriangles]

Go to the options and make sure that you're pointed to your proper template. The template should contain the machine model (if you have one), the tool library and the post.



Your files will most likely be in C:\ProgramData\5XCNC\madCAM\5.0.

Dan

Thanks for your help.

[Corvus]

I will add my 2c here. I installed the update to fix the Win 10 problem and Madcam has now become quite unstable. It simply stops working after a while and I have to restart Rhino to get it working again. The time to fail is random and can be anything from a couple of minutes to maybe 15 minutes. Rhino continues to work fine.

I am finding that Roughing is not working for me and destabilizes madCAM and requires restarting Rhino.

The same part using Z Level finishing takes about 30 seconds to generate, but Roughing with the same settings never finishes generating even if I leave it running for over an hour.


Edit: counter intuitively Roughing is working much better when I choose smaller step down and step over increments. Also setting stock to leave to zero is helping.


After further testing Roughing is hanging only when stock to leave is > 0.

[JOM]

What cutter tolerance are you using for your cutter tool? If set too fine, it will take longer calculation time. Nothing has been changed regarding the roughing or the Z-level finishing in the prerelease.

/Joakim

[Corvus]

Hi Joakim,
cutter tolerance was set to 0.0001 in all cases.

[gtrdavid]

I have had problems with the program crashing ever since the windows 10 update. I have so much work to do I have just worked very carefully saving my work every 5 seconds. I cannot run simulations at all. The program just locks up with the never ending spiral "Not Responding" it does this until the entire computer is locked up and I can not even get to Task Manager. I have to force a shut down and reboot. It dose not seem to matter how simple the file is that I want to simulate. Anybody and have ideas?

[cncmachineokk]

We are use mastercam Why do not you try it

[Dan B]

Did you download the latest pre-release?

[gtrdavid]

Yes, I am using version 5.0.2017.724