This cut took a lot longer than I expected, over 6 hours.
But the result is a 8" x 12" landscape with Mt Hood, Mt St Helens and Mt Adams to proper scale in one piece.
This was created from an STL file from https://touchterrain.geol.iastate.edu/ with 2.8 million vertices. The roughing was done with a downcut 1/4" inch bit (50ipm, 0.05" DOC and 1mm stock to leave), while the finishing pass was with a 1mm diameter tapered ballnose bit (50ipm feedrate, 16ipm plunge) and a small stepover.
The gcode file was 43 megabyte in size, which the new Carbide Motion had no trouble with, other than estimating 3 hours 40 minutes instead of > 6 hours.
Holy smokes that is an awesome topographical cut! The detail level is killer! Would you mind sharing the settings used on the terrain website to get such detail in the file it spits out? I am a little lost trying to pick the best parameters.
The two fields at the arrow I drew are key: Set the resolution of the 3D printer nozzle to 0.2mm and then set the tile width as large as you can get away with (the website has a size limit so need to pick the highest width to just be under that size)
Would I be correct in assuming your stl-to-png code/app would work with this level of detail? and that wonderful application is what you used to make the CC compatible png?
this was not made with CC… this level of detail is currently a bit beyond CC’s scope.
I wrote custom CAM software (https://github.com/fenrus75/FenrusCNCtools) that I used. The STL2PNG uses a lot of the same code, and if I get bored stuck at home I might port the whole thing to a web app …
The web tool can most certainly consume the STL (same code) obviously.
