Search:

Thank you so much for the reply Mitch. As per you suggestion, I recalculated the toolpaths, each time redirecting it to the cutters named in the toolpaths. It works now.

Mitch, Can you elaborate on this. I just switched pc and returning to this work and ran into the same message "This tool path contains no valid search path to the cutter tool! Unable to simulate this...

Hi Mauri,

I only have a 4-core CPU, do you know how much improvement one might expect going to an 8-core CPU? Initially I was thinking it's painful to fully upgrade (not the cost but the extra...

This explains why my changing from the stock graphics card that came with the PC to a high end NIVIDIA graphics card made no difference.

Thanks Mauri. Wire cutting and processing individually is a good option. I might still need to simulate separately in order to verify but I certainly can post the toolpaths together.

Mauri,

I ran your toolpath and got the same result you did. However I did not explain the problem well. My stock is not uniform hence the problem. I am attaching a pdf file to explain better.
...

Mauri,

I might as well report another problem. Perhaps you have time to check. Model stock is not properly simulated in this version.

Thanks,
Trung

Hi Sven,

I am attaching a pdf with actual screen shots and links to hardware used.

Basically a PC with a 4-core i7-4790 with 24GB of RAM, an NVIDIA Quadro M2000 graphics card, a Dell Ultra...

Hi Mauri,

I am attaching a pdf file. Basically duplicating your findings except for the last one, changing voxel on the fly with the large cube.

Thanks,
Trung

Wow! How interesting. I selected all objects together as you did, using Fine resolution with Voxel=.19 and Draw Stock does work! Voxel=.5 not as smooth but goes faster. Voxel=0 and it's ragged again.

Hi Mauri

I changed simulation setting to Fine and it did have an effect this time (only with the cubes). I have tried voxel size before as well. I updated the pdf file to reflect additional...

Hi Mauri,

I tried so many things, wasn't sure anymore so decided to redo the tests. This time no crash but it sure did not behave normal. I notice results varies, sometime it works. I am...

Thank you Mauri.

You are right that it does allow the stock option. I created a simple file with a cube and a hole and tried it again however MadCAM 6 crashed with errors CutStockBox & ...

The 2017 simulator version I had been using finally came to an unusable crawl - I assume due to Windows updates, so I attempted to update - both Rhino/MadCAM 5 & 6. The simulator in the 2019 MadCAM...

Not trial related. I have version 5 and 6. Extremely poor for me as well, I am waiting for updates, see other related posts in this forum. For how well it can work see older YouTube videos.

Sven, Thank you very much for the update. If a pre-release with just the simulator options can be made available it would be enormously helpful. Besides being glacially slow my simulator has very...

You are not alone. You can search the forum for simulator issues. As of today at least there are 2 of us. Apparently a Windows 10 update back in early 2017 broke the simulator. The latest Madcam...

Thank you Mauri. I am still running MadCAM5 with the simulation problems. I have Rhino6 and MadCAM6 but am at a critical juncture of a project and have not installed for fear of further messing...

Hi Mauri,

What are your overall experience with madCAM 6?

Thanks,

Mauri,

It's disconcerting that we are not all seeing the same thing although you did say there are still artifacts. The file I was working with was 138M but based on your comments I created a...

I tried out briefly the March 2018 SR15 for madCAM5 and it does not work for me either. The stock block is still green with black blotches same as the old version. With one toolpath it does run much...

I am still using the pre-release 2017-10-31 version with problems drawing stock. Do we have a rough target date for a fix?

Thank you,

Right. My bad, 4.763mm is the radius to provide a 3/8" hole.

Hello Roger, I hear you :-) Metric is my system of choice. I did not realize there was a problem with imperial units until this project since everything I had done with Rhino/MadCAM uses metric....

I think you are right that the controller does not support G20/G21. I looked up the meaning of G70/G71 they don't seem related to units so not sure how to use that. In my answer to Sven I described a...

My model is in imperial. As Dan alluded in his post, I suspect that even though this series of Axiom machines is brand new (2015) the controller ignores G20/G21. It expects everything in metric. I...

Thank you Louis. As a test I tried to execute a pocketing of a 2" hole .5" deep. I tried with a G20 only but the numbers are small and nothing moves.

(I added G20 for inches here)
N1 G20
N2...

I was doing a simple job using imperial units but when posting the machine barely moves, it interprets inches as mm it seems. The post processor I am using is Axiom-MADcam-Postv5_2.txt. There is a...

Some useful detailed instructions can be found below. Most are in Chinese English, so you will have to guess what they are trying to say.

* MOTION
search: MO-CON501 pendant controller manual ...

Thx. For those interested it's through the MadCAM options not the Rhino options.