search

j-be / AutoBim

A bed tramming utility for OctoPrint using ABL
Other
29 stars 3 forks source link

Ender 3 S1 Pro Can't reach coordinates #36

Open Ajiirtj opened 1 year ago

Ajiirtj commented 1 year ago

Hello!

I just installed TH3D's LCD screen and unified firmware on my s1 pro. In octoprint, when I send the command g0 x30 y30, the nozzle will move to that location but the probe is no longer on the bed. When I try to test that point in Autobim (after homing, first) it tells me that it cannot reach those very same coordinates.

When I try to manually change the coordinates, the max that I can reach in the autobim menu is still way off of the adjuster knob screws. I'm fairly new to modifying a printer this in-depth, and I have no idea how to fix the issue.

What are your thoughts?

Ajiirtj commented 1 year ago

I should also mention, that when I use different coordinates in the autobim menu that the probe will reach, the coordinates do not match up with what is on my printer's screen. The coordinate's on my printers screen DO match up with what I see in octoprint, however. For instance, right now in autobim I have x50 y60, but on both my printer screen and octoprint it is showing x82, y101

j-be commented 1 year ago

Hi, that all sounds like expected. In detail:

G0 moves the nozzle to the given coordinates, while AutoBim moves the probe to the given coordinates. Assuming your probe to nozzle offsets are right this is fine. To check that:

The probe should now touch down exactly at the marked spot. If not, see https://marlinfw.org/docs/gcode/M851.html.

As for the "cannot reach the far end of the bed": there are 2 settings in Marlin: BED_SIZE and MAX_POS (example see here ). Now, Creality sets both to same value, which makes no sense at all, as most printers can move beyond their bed, they just shouldn't print there. Unfortunately, this is a hard limit enforced by the firnware, there is no way around that, except for compiling your own firmware.

For completeness: there are other settings that could limit the area reachable by the probe, but in my experience the culprit is always MAX_POS.

TL;DR: The coordinates in AutoBim always refer to the probe's position, not the nozzle, and Creality makes shitty firmware.