You’re completely right, I forgot about that method. I’ve used it in the past, it works great and is far more controllable and safe.
You’re completely right, I forgot about that method. I’ve used it in the past, it works great and is far more controllable and safe.
True, I’ve seen many molten rolls of filament because of overly warm ovens. Make sure it doesn’t go over 60C and you’re good. Mine is good, has a little overshoot when heating up, but if you let it warm up first and then put the filament, it generally stays very close to 60C. I havent had problems. Other ovens - be careful. Food dehydrator is better, but if you don’t have it, you may as well buy an actual filament dryer. Desicant beads didn’t work for me. They do the trick of maintaining the dryness, but if you have ANY built up moisture in your filament, the beads won’t do much.
A little mini torch, similar to a regular gas lighter also can work wonderfully.
As others have mentioned:
Nothing wrong with Ender 3, if you thinker enough, you can get results as good as any other printer. But it may require tinkering. The model that you’re printing is difficult with FDM printers of any kind. It has thin, delicate parts with steep overhangs. It can look better, but it’s gonna be hard to achieve. Resin printers are definitely a better choice for this, but you use what you have.
Well, I’ve been a C/C++ dev for half of my career, I didn’t find Rust syntax ugly. Some things are better than others, but not a major departure from C/C++. ObjC is where ugly is at. And I even think swift is more ugly. In fact, I can’t find too many that are as close to C/C++ as Rust. As for logic… Well, I want to say you’ll get used to it, but for some things, it’s not true. Rust is a struggle. Whether it’s worth it, is your choice. I personally would take it over C++ any day.
In 2024? No, unless it’s a plus. Plus already has that support. E5 has an 8 bit board and no silent drivers. If I’d be buying today,I’d buy sovol sv08. It has everything already done to it while being open source and is able to be modded out of the box.
Oh, yes, it caused weird resonant vibrations at certain speeds. A terrible design and way too flexible bed. Some people print some struts, but I didn’t find them to be much of a solution. I ended up mirroring the far side and copying it to front. Now it’s very rigid and the quality has vastly improved especially at speed printing.
I did it and I’m very satisfied with the result. Though I went full diy and ordered parts individually. I did all of the printed parts from recycled PET from bottles which I recycled myself. The rest I ordered from aliexpress. I have a previous version, didn’t get around to update. I made an adaptor for herome gen 6 hotend holder and made it with mostly stock e3d v6 hotend. I just added a cht nozzle. Don’t need anything else. But the best mod IMO is the dual z axis which I recommend even without mercury conversion.
Edit: I did it on ender 5, have no clue what’s the difference on other printers.
Have you tried zed? Written in rust, has many extensions. I gave it a try, I quite like it. It’s blazing fast. But I haven’t tried on an old machine.
You could use just a regular 5 min epoxy. I frequently use CA glue, but depending on your use case, it might be too brittle.
So, not the droid we Are looking for… :(
From my small experience with Qualcomm in the past, I’m not too hopeful. In a company I used to work for, we wanted to use one of their SoC with Linux, which they claimed they supported. It was many years ago. But was full of closed binary blobs which even when signing NDAs, we couldn’t get the source for. We’re talking user-space drivers, sensors offloaded to a separate core with closed source firmware etc. It’s Linux, but it’s not Linux in spirit, it feels so closed and proprietary and secretive. They’re coming from Android, which google architecturally enabled vendors to close their drivers by utilizing HAL. It’s the single most significant blow to Linux by any corporation so far. It enabled thousands of vendors to close their removedty driver in user-space and not maintain it for newer kernels (kernel driver is just an IO proxy for user-space drivers). I get that without it, there wouldn’t be Android phones we have today, but I expected them to slowly open up. 10+ years later, almost nothing changed, in fact - things seem worse to me.
Compatibility is iffy on some of the newer ones. Here’s a list of what works for some of them: https://github.com/Dunedan/mbp-2016-linux
There is indeed multiple ways of doing anything in freecad. But over time, I prefer staying in Part design as much as possible as this makes it more modifiable and customizable and there are plenty of reasons more for me. But in the end - whatever works is good enough.
Shape binder is what you need. Shape binder can be used to reference geometry from another body. What I would do is I’d make one pocket on the main body. Then select another body and make it an active body. Then select the pocket you made (the surface or the edge) and create a shape binder (part design). This will effectively import the selected feature from the first body and you can reference it from second body. Make sure you hide the first body, as it somehow gets in the way of shape binder, for some reason. Repeat for third body.
If it works for you, don’t touch it, great. Manjaro mostly just works, but occasional headaches I kept getting, like packages being broken for days at a time, no easy place to look for solution (their repo being different to arch’s makes 99%of the difficulty) made me switch to arch/endeavorOs. Eventually, they may get stable enough to be acceptable, but I don’t think their way is the right way to do it and they may even harm or slow down arch development and community in the process. Just looks like arch with extra steps, so I always recommend endeavorOs, Garuda or plain Arch, before Manjaro. But that doesn’t mean Manjaro is trash and in some cases, it may even be the best solution.
Yes, that’s exactly it. You could try out and see what you prefer. I tried everything, but also tastes change over time. I used to use KDE cause it felt more like windows (we’re talking XP era), later I tried Gnome, Unity, xfce, fluxbox, but then I tried i3 and it is really minimal and tiling and I don’t need anything more. Not for beginners, but after some time, it might become your jam.
Kinda like that, but a bit more. Those are desktop environments, which differ in more than just styling. Most popular ones are gnome, KDE, xfce, but there are dozens of others. Most distributions come with one directly supported, but you can install others usually and pick at login.
This looks like heat creep and/or clog. Check the hotend fan (not the part cooling one). If it starts happening after a while, it’s either that or the nozzle has cooled too much. But if it happens with lower speed as well, then I wouldn’t say it’s that it’s the latter. Try increasing the temperature. I’m printing mine at 270°C. Also I keep the bed at 70°C but that’s not important. I’ve had issues like that with bad conducting nozzles (hardened/stainless steel) and thermistors not properly seated on the heat block. When this happens, pause the print, try feeding the filament by hand and see if there is any resistance (can you feel the clog). Try increasing the temperature, reduce the retraction distance to try and avoid it. I’m printing exclusively with petg for years now, never had issues like this due to moisture. You get more stringing, yes, but no failures on actual printing.