Slow Progress
The updates here have not been frequent lately but I’ve been making steady progress on the new finishing algorithm. Below are a few shots that show the current status. Here’s what they show:
1) The new finishing code will preplan the bulk of the path ahead of time rather than building it one the fly like the current versions. This means that the time intensive part, projecting the path onto the model, can be done in a parallel fashion using multiple CPU cores to speed it up.
2) The paths below are fit to the geometry plus a machining margin, .1″ (user definable) in the shots below. It will ignore the supports in this calculation so the minimum area is machined and the supports can be thinner since they don’t necessarily have to support long spans.
3) Preplanning the paths means that there can be much more efficient path linking with far fewer retracts. Note how few blue retracts you’re seeing below compared to the current system.
4) The shots below show that the supports now function for multiple part STL files. The old ones didn’t and would fail completely in a case like the one below.
5) The code to do this preplanning is very similar to a pocket algorithm so I think I can port it to roughing for much smoother paths there as well. This will be a big win because it will unify all of the toolpath code and remove any old ZMap-style code from the program. This eliminates a lot of legacy junk that requires tons of testing anytime I make toolpath changes.
There are still a few visible glitches to work out but it’s finally getting to a point that the whole thing can be tested together.
Note- The skewing of the overhead view is a function of the perspective view in MeshCAM. The paths are actually laid out with a perfect .1″ boundary.
Comments
11 Responses to “Slow Progress”
Thanks for the update Robert, I’ve been eagerly awaiting the next release and have been checking this news page every day. As a hobbyist with a Syil X3 and some ideas to prototype, I was over the moon to find MeshCAM with its price and perfectly intuitive interface, but I was put off by the very long cutting time from my first model, the path was clearly not optimal. I know there have been many changes since I bought MeshCAM 6 months or so ago - but the optimizations that you’re making to the tool path sound very significant (and exciting), plus I can’t wait to see what my new quad core PC makes of your multi-threading support!
Please keep up the good (steady) work, in the mean time - I’ll keep checking the news every day
Kevin.
Hi Robert,
What you’ve done so far looks really encouraging. Makes me glad that I chose Meshcam.
Can we expect that the next release will include a feature that lets us define toolpath strategies separately and specify the tool, feed and speed for each path?
Thanks,
Blake
Kevin-
I’ll be curious to hear you 4-core feedback. Until they make a 4-core laptop I’ll have to live vicariously through you.
Blake-
The ability to define speeds and tools will likely remain unchanged in the next release- the resulting toolpaths will be better though. I hesitate to show my hand on what I’m planning after that (too many promises already) but all of the new code that I’m writing here can be applied in lots of new ways. Once this is released and tested I can play with some new ideas.
-Robert
Robert,
As always, looking very good. Will the next release support multi cores? Just the anticipation is causing me to run denser stl files at tighter tolerances, cofee consumption is UP.
Interesting note on a new photo realistic render engine (VRay) for the Matrix jewellery plug in for rhino. I’ve just read about it, I don’t get to play with stuff that expensive ($$$^2). Their answer to the computational demands is “Distributed Network Rendering” . Spread the load over networked machines, maybe the latest quad core boxes are cheaper by the dozen
Jeff
The next release will have several functions that have been modified for multicore support. More will be added over time as I go back and rework different sections of the code.
You know, I could calculate the toolpath on every molecule of your wax and still you’d want more.
-Robert
Robert,
No, you must be refering to Randy’s pursuit of accuracy. I’m more interested in the artistic side, how photons bounce off and interact with the piece.
In all honesty I was quite pleased with the very early version 2 release I started with, it did all I needed at the time and would still fill most needs. You just have a propensity of spoiling us, and I’m not complaining. Watching and maybe even helping MC evolve is exciting and very enjoyable. Now about those photon refractions and reflections …
Jeff
Gee whiz, I miss a day in checking the blog and not only is there an update, I’m mentioned in it!
Rumors of my pickiness have been greatly exaggerated! Well, maybe not. 
I’m really happy with 6738. I’ll be really even more happy with the next release.
I’m just imagining Robert coding with one hand while rocking the new baby with the other…
Randy
Randy,
Not only rocking a baby while writing code he some how manages to conduct business half way round the world on a regular basis. A man with many skills.
Jeff
How about a few skills and a very understanding wife?
Amen to understanding wives. I would be in bad shape without mine. But the evolution of MeshCAM definitely shows your skills.
Do I understand properly that the roughing will also follow the part-plus-margin rather than roughing the whole rectangular envelope? That will indeed be a great time and cutter-wear reducing feature.
Randy
That’s right- the roughing and the finishing will both be fit to the part. It should be a huge time saver.
-Robert