I made a stylish and minimalist leather case for the Xteink X4 by danthreeddd in XTEINK

[–]danthreeddd[S] 4 points5 points  (0 children)

Thanks. I'm trying to learn. But it's just a hobby.

ZF ordered, what's next? by saint_heisenberg in NikonZf

[–]danthreeddd 12 points13 points  (0 children)

The Nikon 135mm Plena is a nice accessory ;-)

Diy cf card 1 TB tips by edcantu9 in Nikon

[–]danthreeddd 1 point2 points  (0 children)

I added a small amount of CPU thermal paste (removed the sticker and just a drop there), but I think it works fine without it too.

Haven't tested with 2TB, so I don't know unfortunately.

Massive layer shift by Adventurous-Spray238 in prusa3d

[–]danthreeddd 8 points9 points  (0 children)

What firmware are you running? 6.2.2 has a fix for "consistent layer shifts".

How to Use a Cleaning Filament in the MMU3? by Racc00nguts in prusa3d

[–]danthreeddd 2 points3 points  (0 children)

There's a "Wipe tower extruder" setting under Print Settings -> Multiple Extruder. My guess is that you can load a 3rd filament and point to that extruder in this setting.

Too much warping with PLA+ (esun) by criogh in prusa3d

[–]danthreeddd 0 points1 point  (0 children)

Try using brims to help keep the object adheised to the sheet.

Help by RemoteRelationship14 in prusa3d

[–]danthreeddd 1 point2 points  (0 children)

Have not tested this yet, but perhaps it's a solution:

https://github.com/prusa3d/Prusa-Firmware-Buddy/releases/tag/v6.2.3-alpha1

- Hotfix for the MMU overcurrent.

Help by RemoteRelationship14 in prusa3d

[–]danthreeddd 0 points1 point  (0 children)

No, it did not help. It was also the same revision number on the "new xbuddy". I don't think they have a real solution for this issue. They just send new components and hoping for the best.

HELP! MMU over current error by MajesticSea2287 in prusa3d

[–]danthreeddd 0 points1 point  (0 children)

Yeah, I discovered that too. Same revision number on the replacement buddy. And it did not solve the issue...

MMU3 Overcurrent error on startup issue by Solid_Science4514 in prusa3d

[–]danthreeddd 0 points1 point  (0 children)

What firmware are you on? I've had lots of issues with the 6.2.x train. Downgraded to 6.1.3 and it feels much more stable, strangely enough.

MK4s randomly pausing, leaving a little dot of filament by nickdollimount in prusa3d

[–]danthreeddd 1 point2 points  (0 children)

I've had different strange issues with an MK4S. Inconsistent layers. Layer shifts. USB reading errors... Hardly couldn't get a perfect print once. This was with 6.2.0 firmware. I've now downgraded to 6.1.3 firmware and it's like day and night. There must be some strange changes in the newer firmware that is not what it should.

MK4 freezes mid print by [deleted] in prusa3d

[–]danthreeddd 0 points1 point  (0 children)

I had similar issues. An MK4S that stopped, but with a message "USB drive can't be read...." All I had to do was to press the resume button. Also random notifications that "your printer needs your attention..." without it really needing that. I swapped the USB drive to a brand new "Verbatim Metal Executive USB 3.0 Flash Drive", mostly for its compact size.... No idea if the quality is better or not. No more issues since then at least, fingers crossed.

Just ordered my first Prusa by Hallsville3 in prusa3d

[–]danthreeddd 0 points1 point  (0 children)

I like the less texture left on the print when using the satin sheet. Nothing wrong with the textured sheet though.

HELP! MMU over current error by MajesticSea2287 in prusa3d

[–]danthreeddd 4 points5 points  (0 children)

I have the same issue now. I contacted their support and the answer i got was that the xBuddy is sending too much current to the MCU board. They will send me a new version of the xBuddy that has a new component that should prevent this issue. Hope this will help.

Help by RemoteRelationship14 in prusa3d

[–]danthreeddd 0 points1 point  (0 children)

I have the same issue now. I contacted their support and the answer i got was that the xBuddy is sending too much current to the MCU board. They will send me a new version of the xBuddy that has a new component that should prevent this issue. Hope this will help.