Hot answers tagged

3

I'm pretty sure something is wrong with the firmware I downloaded. I flashed the 3/5/21 version of Marlin firmware from https://marlin.crc.id.au/ and it is somehow working better with the LCD firmware (which I got from TH3D), the Z offset is working as it should, and the leveling process has more points and goes faster.


2

Looking at your prints, the problem is possibly related to the fade out height of the BLTouch functionality. If you look closely at the 20x20x20 mm cube: half the print is fine (top half of the original correct cube) the bottom "half" (not really half as it is stretched) is porous (grey, indicating more space allowed than the correct layer height ...


2

A BLTouch doesn't level the bed, it compensates for the geometry and adjusts print head movement, it is always required to tram (level) the bed with respect to the nozzle X-Y plane (of which the Z is perpendicular to this plane). If the build plate is skew, the bottom of the print will be skew, the top will be square with the head movement plane (the default ...


1

It seems the DEFAULT_LEVELING_FADE_HEIGHT of the TH3D firmware was causing the issue, which was something I was aware of but didn't think that it would cause this. I set it to zero and then re-printed the calibration cube. It came out with the dimensions of 20 mm x 20 mm x 20.1 mm, which was incredibly accurate for the setup I have. Related: Creality Ender 3 ...


1

Initializing After changing your firmware, you always need to overwrite the old values in the SRAM and EEPROM with those from the Firmware. Which you do with M502 & M500: Installing firmware does not by itself alter the EEPROM, so these settings needed to be seeded into SRAM via M502 and then saved into EEPROM via M500. You could also run a G-code ...


1

After setting up the BLTouch in firmware, you need to activate the leveling function for every print by inserting the leveling G-code 'G29' in the start G-code script of your slicer. The code should be placed directly after command G28. Note that you can test the working of the sensor from the printer display: sensor can be deployed, stowed, reset and tested....


1

There are multiple ways to achieve this: In G-code You don't necessarily need to do that in firmware, TH3D is based on Marlin firmware and is just a monolithic implementation for most popular printers and boards that helps novice users to easily configure their printer, but in the meantime it hides other options from plain sight. Being a derivative fro ...


Only top voted, non community-wiki answers of a minimum length are eligible