Quote
I have a second hand folgertech 2020. But I don't think that matters. .
That is a great machine. That is what I used to develop the UBL Bed Leveling system. If you turn that on, I can answer any question you have.
And if you insist on doing a Manual Bed Leveling within the UBL system... The first probe sets the shim thickness. and the subsequent probes measure the points you are probing. But there are better paths for you to follow.
I'm kind of down on manual probing. It is too slow. You are better off just doing a few points that way in different areas of the bed so you know how badly warped your bed is. And then manually fill in the near by points.
And then jump to the G26 Mesh Validation tool to see what needs to be corrected and by how much.
If you switch systems... I'll help you get your system configured so it has 100% adhesion across the entire bed every time you print. That FT-i3-2020 will be a pleasure to use! (And I also have a bunch of add on parts designed that make it even a better printer if you want them. Z-Probe (and servo holder), Ball Bearing rollers for the filament spool, Better end stops... Etc. Etc.
Quote
I'm over here because, unlike the lead developers, I think github issues are for bugs, not support, and I can't find an official Marlin forum/mailing list.
Yes, GitHub issues are for bugs. But they are also for people having a hard time using the software hosted on GitHub. As a 'Lead Developer' I don't want stupid questions being asked because a person is too lazy to spend 30 seconds looking for an answer. But the firmware needs to be easy to use. So, answering questions is part of the development process. It forms a Checks & Balance. If a new feature generates too many questions... It needs to be made more intuitive. Or more automatic... Or something else that makes the questions go away. If you decide to take me up on my offer to help you bring up the UBL system on the FT-i3-2020, we will walk through the various Phase commands to generate the mesh. You will see there was an attempt to simplify things as much as possible.
Quote
I suspect software end stops prevents me from positioning below where the Z end stop triggers
Probably you want these values configured this way. If you have any dips (or warps) to your bed, you need to be able to position the nozzle below 0.000 mm
// If enabled, axes won't move below MIN_POS in response to movement commands.
//#define MIN_SOFTWARE_ENDSTOPS
// If enabled, axes won't move above MAX_POS in response to movement commands.
#define MAX_SOFTWARE_ENDSTOPS