Topics created by devleon

Yes that makes sense. You can do it, though your offset will need to be spot on since you won't be using the probe to home Z. Otherwise your heightmap could have a larger than expected offset. The trigger height of the switch would need to be offset to exactly where the nozzle would be touching the center of the bed.

You could find this offset with gcode as well. Touch the nozzle to the bed, use G92 to set Z0, You'll need to use M564 S0 to allow movement beyond the set axis limits and then jog the nozzle until it just triggers the switch and note the Z position. It'll be a negative value. This value would also change any time the bed was releveled. This is a disadvantage to not using the probe to home.

Your homeall.g could be modified to move the print head to where it needs to be, configures the endstop, and then triggers it setting the Z position with a G92. Then you'd have to return back above the bed surface and move to a safe location to start the print from.

For the probing of the mesh you could edit bed.g to configure the probe, prompt you to ensure it's mounted, and then execute a G29 to generate the heightmap, and then prompt you to reinstall the nozzle.

Hopefully that makes sense. Let me know if you want more detailed macro examples.

Thanks very much for the feedback!

I found another script on the linked github repo: https://github.com/T3P3/GcodeMacros/blob/master/Calibration and Tuning/Diagnostics/Probe_Repeatability_test

Works fine now, got a mean deviation of around 0.00759 mm, seems good to me!

Do we have a Z isolator designed specifically for Ender 3?

All the designs on Thingiverse seem to aimed at the Prusa or other models...has anyone actually made one for the E3?

Just wanted to add that after I had posted this issue on /r/3dprinting, a couple other people mentioned that this issue did not go away after upgrading to the meanwell psu.
Some people with an ender 3 pro (that has the meanwell psu) also have the same issue. This makes me to believe that this is simply an issue with the cheap ender 3 mainboard.

Why the noise is only on the X-Axis is unclear, but people that switched the X and Y connections had the noise and vibrations also switch to the the Y-Axis, so it has to do something with the X-Axis driver.

Anyways, I'll update this once I have converted to the Duet. For now I'll simply try to print with the bed off, or enable PID again, even if that noise and vibration will drive me insane...

@jay_s_uk AMAZING! Thank you so much

@vacalos I have no experience with the prometheus splitter
I have used this splitter for some time : https://www.thingiverse.com/thing:3039887 with a e3d clone
At the moment I am using no splitter as I have a new printer and want to get other stuff done first before playing a round with a splitter again.

My biggest issue with the splitter was changing the filament. I couldn't get good tips on the filament for PLA at all. It did work reliable with abs only and like 90% with petg. I have tried a lot of different settings to get better filament tips without having to adjust the settings all the time for different materials or brands without success.
Next time I will build a cutting mechanism into a splitter to get rid of that problem.

@devleon said in Upgrading Steppers for an Ender 3:

JK42HS34-1304

That motor would IMO be just perfect for the Bondtech extruder, unless you want to use a 0.9deg motor. I use it in the Titan extruder on my delta (soon to be replaced by a Bondtech). The problem with using a more powerful motor on a geared extruder is that it helps to have the torque low enough so that if the nozzle is temporarily obstructed, the extruder skips steps instead of grinding the filament. But if you start with a high torque motor and reduce the current to reduce the torque, not only do the microsteps become less even, but the high rotor inertia of the larger motor limits the acceleration.