Finally after many many months, I am back to working with my cnc and cutting parts for my 3D printer build. I can def up my federate with this 3mm endmill.
Very nice!
Use less stick out on your tool it reduces rigidity as a cube, so half your stick out 8 x the rigidity. Especially with a small tool like that it’ll help you go faster.
I am curious to know the feed rate. I’ve got some 1/8 in aluminum I would like to cut some mounting brackets out of.
I’ve found something interesting with this flat stock. Different pieces of the same stuff cut VERY differently. The first few I did I was able to do 150mm feedrate, with 100mm lead in/out… but the last couple I did I had to constantly lube to avoid melting and dragging. I even tried different bits. I’m moving from a 2 flute 3mm to a 4 flute 4mm flat end mill to do the rest. Will let u know how that goes.
I think you are not doing enough chipload and the Bit is going dull?
Your Chips are very fine, so the endmill may Pack up.
Maybe try dropping rpm?
I could do 500-700 mm/min feedrate at about 10.000 rpm and 1mm depth of Cut.
With a China 2 flute 1/8 Flatrate endmill.
Done in my small (340mm) self made mill Router.
Then i get some nice small Chips flying around. But you will get some decent deflection and you May want a finishing pass with a 2/10 mm full depth or so.
Ok, i see where i need to start testing. Ive broken a few bits (thankfully I have a LOT of these 3mm end mills). Still hitting points where it will gum up, but at least Im on the right track, thanks @Andre_S !
Im experiencing some gcode widget weirdness now, it wont reset correctly, and sometimes it just holds on to the last loaded gcode when you load a new one. It may be a CPU related thing due to the rendering in the 3d viewer… but I cant quite tell, I will be debugging this more. Right now I have to power cycle both the pi and tinyg after each test, otherwise chilipeppr ends up in a weird state when it doesnt finish a run (ie. I freehold+reset).
Great success, this is what ended up working without issues for me. I had to drop the step down to 0.5mm, anything more would snap the bit.
missing/deleted image from Google+
In the past one potential reason for new gcode not loading in gcode widget but loading in 3d viewer had been weird gcode crashing during the load process. You should be able to see the error in the JavaScript console of your browser if that’s the reason. Just a guess though
@jlauer more often than not it ends up showing the gcode lines shown in this screenshot. I may dig in to the code next week to see what I can find.missing/deleted image from Google+