-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Galileo Extruder - Stealthy style? #14
Comments
The Stealthburner cooling system is already fully compatible with the Galileo Clockwork. That said I have some projects in the works as well, so we'll see what happens. |
Oj, that are great news! I was hoping for compatibility! Also im interested into your work obviously ... you can do a hint whitch quartal/season of 2022 you plan to release? So ill drop by? All the best, have a merry christmas and a good new year! |
Quick request, sorry that I come back to you. It appears to me that the bottom Part of the extruder is altered.- you are sure, or do you just estimate that the galileo will be compatible with the new toolhead? Might be that the screws have the same measurements, but the plastic guides/slides seem different. |
I have Stealthburner running on my Trident with Galileo as we speak. The Clockwork 2 module requires some changes, but the cooling ducts known as Stealthburner are a drop-in replacement. |
I understand you can only use the new Stealthburner front but you cannot yet use the new X carriage with extruder screws on the front or the new toolhead mounts, correct? |
That is correct. The existing Clockwork will not work with the new carriage. The next release of the Galileo Clockwork (GC2) will follow the Afterburner CW2 design and mounting. |
I am looking forward to Galileo 2. |
Any news on Galileo Clockwork 2? |
i'm waiting Galileo for Stealthburner day by day, will you upgrade it soon? |
At this time if you want Galileo extruder for the stealthburner you will need to stay with CW1 version of mounts and toolhead because that's what Galileo was designed against. |
Hello, curious to see if you will embark on Galileo Clockwork (GC2) with the RC1 CAD ? Also, I just wanted to campaign to keep the latching mechanism on the left of the extruder similar to CW1/2, rather than hiding it under the new cable shroud. |
I do actually have an updated mount for the CW2 carriage, it's just not published as it's a temporary fix. I will be working on cleaning up and updating my repository here soon and will manage this at that time.
Galileo Clockwork 2 will be a completely different set of parts, but will be "stealthy" to match the CW2 design. I will also be releasing a CW2 styled Galileo Clockwork 1 for those not wanting to move to Galileo 2. As far as the base for the design is concerned, I haven't decided yet whether to use RC1 as the base or wait for full release. Once there's an update, I'll update my repository. |
The stealthburner is finished, voron team has deployed the release. I can't wait for the new Galileo Jared. The mechanics (gears ecc) will be the same as Galileo 1? Thanks for your awesome job mate. |
It's at RC1, not full release yet. That said, I will be using it for the style upgrade for Galileo. The mechanics will be the same as Galileo 1, but there will be a Galileo 2 version eventually. |
@JaredC01 I understand the new orbiter 2.0 has different gears and proportions for the shaft ect.... Will the new CW2 Galileo use the original 1&1.5 internals or the new 2.0 internals ??? |
Galileo 2 is no longer based on the Orbiter internals, it's completely different. |
I guess my question is referring the the statement above. " CW2 styled Galileo Clockwork 1" Can i assume 1.0/1.5 internals for this? And that it will work with the new carriage? |
Ah, my apologies, yes that will be the case. Just the 1.0/1.5 parts will be compatible. |
@JaredC01 do you have any estimation when the Galileo update will be available? I'm close to finishing the mechanics of my V2.4 build and am currently considering waiting for your update or buying a bmg kit for CW2. |
Hi Jared. I'm curious if you felt the Galileo 1 had improved flexible handling over the orbiter 1.5? In a similar vein, do you think there will be improvements for flexibles handling between Galileo 1-CW2 & 2.0? |
I'd like to have something working by the end of August, but that's not a firm timeline at this point. I've got a few projects I'm working on currently, so I can't give a firm date. |
Galileo / Orbiter used the same core parts, but I'm not sure if the Orbiter 1.5 had as constrained of an output as Galileo does... that also said, the larger drive gears make flexibles worse in general unless you can constrain the output to as close to the drive gears as possible. My opinion is that Galileo 1 isn't great for flexibles overall, but the Orbiter 2.0 metal exit DOES make it work quite well with flexibles. I'm working with LDO on making the metal exit available for the Galileo 1 refresh, as well as Galileo 2. |
I have a 1.5 and from a bit of research people say its not well suited for flexibles. That is very interesting about getting the metal exit ( I know what you mean) as a part from LDO. Please ask him (if possible) to prevent triangle-labs, Mello, etc putting a shipping price of $8 on it, as is their usual scam. Also, I saw people were having good results with the 1.0 using PTFE as the exit tube. trimming it to fit as close as possible to the gears, for a constrained exit path. If its not to much trouble perhaps you can include a version that would also allow for the PTFE method. Thanks again! |
Hi,Thank you for your work. I love the Galileo that you design. I hope to see your Galileo design for cw2 soon. I've been waiting for it for a long time. |
Just curious if the Galileo 2 design will accommodate PCBs like the hartk stealthburner PCB |
Nah, that's still Galileo 1, it's just got a reworked rear plate to fit the CW2 carriage. Galileo 2 Extruder is getting awfully close to testing though. |
any news? |
I'm about to rebuild my Voron 2.4 gantry with MGN12H rail and Stealthburner, and was hoping to throw Galileo in the mix too - a shame to see this project has stalled out? I have all the Galileo hardware ready to go, but was hoping for updates to printed parts. @JaredC01 are you still planning to put something out here? |
@tomnz hey, there. A few people would be happy to see a release, but please don't be that pushy, shame is the wrong wording here. There is no obligation to release anything. |
Hey. Any word on when the Galileo clockwork 2 (GC2) is going to come out? And any chance it will support toolhead PCBs? Edit: Also, what gears will this extruder take? |
Galileo 2 (and the projects associated with it) are just now being tested in a closed group. The parts, as well as the drive gears are fully custom. Once I have more info available for release, it will be posted here. When release comes, the whole GitHub repository will be updated as well. |
does it use the gear set of the V2.0 orbiter? |
He mentions in the quote they are fully custom. |
so my orbiter is useless :( |
no news? |
Galileo 2 is my current focus, and should be released in the next couple of months. As mentioned previously, G2 is a completely new design, not associated with anything Orbiter. Once G2 is released, I'll shift my focus back to G1 in a CW2 style. There's a few major hurdles on G1 currently, which is why I have paused G1 development. -Jared |
Following :) |
Peripherally saw this in a builds video, excited to see the bom and test it out myself. Thank you for your work. |
@rcg94 Link pls |
hi @JaredC01 |
Good evening,
First of all, thank you very much for the current design, I'm building it currently and are quite impressed.
The Voron Team did just release a new toolhead assembly, do you have any plans into customizing the Galileo extruder so both work together? Since I'm only able to - narrowly - use freecad, I think that project would be to big for me.. But maybe I can assist a little.
I think planetary gears are superior to the normal assembly, I would very much enjoy using your extruder with the new fanduct designs.
Thanks!
The text was updated successfully, but these errors were encountered: