I’m very torn. I bought the full Primo kit to build from scratch, then I’m turning my Burly into a LR. Not sure if I would abandon the printed parts, or just go with the SS since I only plan on doing 2x2 max. I can’t see the conduit being that much stronger than 1" OD at those lengths.
2 Likes
You have no idea… 
1 Like
I know you struggle with your filter a bit. I had no idea it was working so well.
3 Likes
I struggle with a lot of things, the filter is just one of a legion of idiosyncrasies, neuro-atypical behaviors and outright character flaws I beat back on a daily basis… 
1 Like
What do you mean it has been well documented? I don’t really care, it’s the original creator’s decision how to handle releases, I just thought it would solve a world of issues and I personally don’t need it since I’m fine with the 25mm stainless.
How tall would the Primo core be? will most printers be able to manage it? Up thread I think people were saying 180mm tall for the J(umbo), and if the H(uge) is 16% larger that is 209mm.
No, no, no… It’s M(ammoth). Otherwise, you can’t alphabetize them…
I know I am:stuck_out_tongue_winking_eye:
1 Like
It is a bit early to say which one will actually be the best. Ryan may just scrap the whole 1" thing for something none of us are thinking about (and we won’t see first, because it will happen in his garage). But I suspect the 1" is going to give the DOM a run for it’s money. It is far from a forgone conclusion that DOM will be the best or 1" will be the best. We will just have to wait and see.
And until they are all gone, I think everyone interested in a 3/4" kit should check the #leftovers section. There have been a few people who feel guilty tossing their beloved parts in the trash when upgrading to primo, and you can easily get a full set, run with it for a few months, break some stuff, and wear out your conduit. I think that is a great solution.
5 Likes
Why would I want 30mm? 25 is fine. 
1 Like
Projecting the American ideal of Bigger is Better… Heck, just look at our COVID numbers! 
2 Likes
The discussion abouth releasing the parametric files comes up often on this forum. It was especially vocal during Thomas Sanlanders MPCNC build. Ryan has stated that he want’s to keep the drawings to him self, to limit chaos related to possibility of thousands of iterations and a chaos with troubleshooting and limiting cheap know offs. I think that he should be respected for that, it’s his intellectual property and I fully understand his reasons.
3 Likes
Yeah, that’s the problem if you know too many words.
1 Like
Can I get a TLDR of the Thomas Story? I think I watched one of his videos being whiny about Ryan not wanting him to make the design better.
I hate writing work emails. I always find myself re-writing them with simpler vocabulary and syntax. Unless it’s one of those “fun, team-building exercises”, in which case I revel in the bafflement of my lesser-read co-workers who have allowed their literary wanderings to languish in disuse and get scoured away by the rapid-fire monosyllabic tripe funneled into their brains by a monopolistic television hegemony and vapid publishing industry. Plus, my “pop culture” references are all 20-30 years out of date, and not all that “popular” to begin with…
2 Likes
It’s brand protection. if someone goes in and messes with a file and then tries to sell them or provide under the v1Engineering name and it has issues, that looks bad on Ryan and tons of support calls/questions. Then he is spending time to try and figure out what is wrong when it isn’t even his issue to begin with.
From the perspective of someone only aware of this ‘hobby’ CNC world for 4-5 months I think he’s extremely generous with the files allowing folks to print their own parts if they’d like and completely agree about things being his intellectual property and his reasons.
2 Likes
Tom tries to build MPCNC. Tom screws it up. Tom never asks for help. Tom blames zip-ties. Tom blames design. Tom designs corner piece with belt clamp. Tom gets preachy about open source licencing and pulls kindergarten stunts about being “inspired by” and “compatible with” and threatening to basically “create” a whole MPCNC, but Open Source instead of CC-NC-SA. Tom’s followers bash Ryan in YouTube comments and on Twitter (although why anyone ever reads YouTube comments is beyond me). Meanwhile, Ryan is frantically trying to deal with a fair amount of backlash, including, I believe, some truly unpleasant hate mail, and tries to reach out to Tom to try to reach some sort of understanding. Eventually, Tom rolls his eyes for the camera (remember, he lives and dies by viewership, Ryan lives and dies by sales), and sort of drops the whole topic with a dissatisfied “harumph”. I will point out that at no time did I mention that the V1 crew went over there and raised any sort of ruckus. This is not an omission, but a testament to the civility of this crowd. There were some heated words here, and many a ruffled feather needed to be soothed.
I will also add that we had high hopes when he started his build. And there was a collective gasp when he started running in to trouble, and much gnashing of teeth when he started re-engineering things rather than just asking for help, which he would have gotten freely and quickly had he reached out.
5 Likes
Thanks. Seems like Tom thought he was good at what he does. As a teacher I know a few people who get mad when they can’t get sth. done they usually should be able to.
One of the worst parts is that people come out of it thinking that Ryan, or V1, or the community isn’t ok with modifications, and everyone is totally OK with modifications. It’s just that direct copies (even with modifications) need to be released CC-SA-NC. New parts (like a new tool mount) can be CC0, and you can modify and share (please share) any parts from Ryan, just release them with the same license as the original.
It’s water under the bridge now though. We’ve moved on, Tom has moved on. Just a few people somehow get their feathers ruffled and try to pick fights every once in a while. It would be great if we didn’t bring that all back up again. Oops, here I am talking more about it.
5 Likes