My first month with the Shapeoko


(Julien Heyman) #1

Hi,

I documented my first month with the Shapeoko3, and thought it could be interesting to share with my fellow CNC/Shapeoko newbies:

http://jheyman.github.io/blog/pages/Shapeoko/

Very happy with my machine so far, a lot of learning happened, and lot more is coming up.

Cheers


Shapeoko3/CNC beginner journey, one year later
(Patrick Andersen) #2

Wow Julien! What a journal of your experiences. It must have taken you all of a month just to put this together. I haven’t read it all but what I have read is interesting and informative.


(William Adams) #3

Very nice!

Added to the front page of the wiki as:

Another user, Julien Heyman (Julien on the Carbide 3D forums) did an extensive writeup on his purchase and usage of a Shapeoko 3 which cannot be recommended highly enough: http://jheyman.github.io/blog/pages/Shapeoko/


(Jude Marleau) #4

Your feed rate testing is superb, thank you for that. I tested like that also but not that completely. I will copy your test procedures and collect samples from each cut to measure. I can’t read all the notes in the picture but your test is something every new operator should do on their own anyway. Terrific amount of info and a huge effort, thanks again.


(Julien Heyman) #5

Thanks. Right now I am experimenting with hard woods, and my next step is to automate the generation of test pockets of various depths and feedrates around what G-wizard or CC are telling me to use, so that I can have an experimental way to determine the sweet spot for a given piece of stock and endmill.


(Jude Marleau) #6

That will be a huge resource to new operators, especially those like me who just can not wrap their heads around all the variables in g-wiz. I cut by eye, what chips do I see and how does it sound as it cuts. Your results should not be taken as absolutes but they are a marvelous way to see what rates produce chip wise and will give an excellant starting point for their own rates testing. Even wood from different parts of the same tree can cut differently so all should do their own testing. Your testing proves (illustrates chip load wise) why it is so valuable, thanks again.


(Jude Marleau) #7

here’s an interesting question, off topic although, your logo on your page has a binary code at the bottom…is that a cryptic??? didn’t find anything with straight binary alphabet…


(Julien Heyman) #8

Nope, it’s just random 0’s and 1’s. But now that you mention it, it would have been a great idea!


(Jude Marleau) #9

try this one:
10011011100001110101111001011000001100101111010011100100100100011000011110000111000111100110000101110101110100111011001100100100000110101001101111111100111110011101001111010011010001010100110100011001011101101


(Dan Nelson) #10

Jude, you know of course there are only 10 kinds of people in the world right? Those who understand binary and those who do not.

Just something to keep in mind;-)

Dan


(Dan Nelson) #11

This is a great write up! Thank you for taking the time.

Dan


(Julien Heyman) #12

(continuing the off-topic discussion, sorry)
Jude, I’m intrigued now, I tried a few common decoding bases but the 209bit-long value puzzles me. Hints ?


(Stuart) #13

Julien, this is such a great write up, thank you!

I’m very interested in your python script, I’m just starting to teach myself python at the moment, and didn’t realise it could be used liked this… do you have any more info or tips you could share on writing scripts for CC?

thanks again! Can’t wait to see what you make with the shapeoko :slight_smile:


(William Adams) #14

If you’re interested in programming, we have a page of things at:

https://www.shapeoko.com/wiki/index.php/Programmatic_G-Code_Generators

I’ve actually worked up a couple of things to cut using METAPOST (and eventually am going to learn how to use METAFONT to finish up a typeface design I’ve been working on for decades now)

I’d also like to work up some sort of programming / charting / spreadsheet technique which would allow us to analyze and display feed and speed information — thoughts and feedback on that would be welcome.


(Julien Heyman) #15

Stuart,

If you are interested in using Python to generate G-code, the wiki resources that Will referenced will be a much better starting point that the quick & dirty Python script I cooked up for the cutter pack contest. If you specifically want to write scripts to generate CC files, my advice would be to learn to use the Python JSON module, then you’re all set.


(Julien Heyman) #16

Will,

Can you elaborate (forking the thread if needed?) on this idea of analyzing and displaying feeds and speeds programmatically ? I’m trying different things right now for my own needs, both through Python scripting and Excel VBA, and I would be happy to contribute to something useful to the community (though I’m pretty sure that all possible tools in all possible languages have already been developed by someone somewhere!)


(William Adams) #17

Can’t figure out how to do a reply as a new topic — anyway, I think it’d be nice to continue this at:

I’ll post some further thoughts there.


(Michael Dovesen) #18

Hi Julien

Thank you very much for your comprehensive documentation, your thoughts and the well written post.
I am a Nomad user but I read your Shapeoko experiences with interest!

Would you please tell more about the “Migrating to Fusion360” paragraph: …"I watched the 60-minutes worth of introduction videos from Adobe’s web site to get to know the features."
Where to find it?


(Julien Heyman) #19

Hi Michael,

The Fusion360 intro videos are here:

http://help.autodesk.com/view/fusion360/ENU/


(Michael Dovesen) #20

Thank you Julien for the link. Good set of videos there!

I am looking forward to read your next post. The “second month” perhaps? A special project?

Have enjoyable time discovering CNC world!

Michael
[Gold Coast, Australia]