search

MarlinFirmware / Marlin

Marlin is an optimized firmware for RepRap 3D printers based on the Arduino platform. Many commercial 3D printers come with Marlin installed. Check with your vendor if you need source code for your specific machine.
https://marlinfw.org
GNU General Public License v3.0
16.17k stars 19.21k forks source link

mesh leveling probing fail on btt skrm3v3+btt tftr35 v3 #25289

Closed jarvis710 closed 1 year ago

jarvis710 commented 1 year ago

Did you test the latest bugfix-2.1.x code?

Yes, and the problem still exists.

Bug Description

No matter what I do, it always fails at some point; although change the mesh 5x5, 10x10, 15x15. It also doesn't work if I change the dimensions of the bed; I have modified all the parameters and it always fails at some point, both on the board and on the screen. I know that in my configuration I have "unnecessary" things and taking up space, but even so, in the simplest mode the same thing happens. config.zip

Bug Timeline

i don't if it's an issue or a bug

Expected behavior

No response

Actual behavior

No response

Steps to Reproduce

No response

Version of Marlin Firmware

marlin-bugfix-2.1.x

Printer model

Voxelab aquila x2

Electronics

btt skr mini3 v3 + btt tft35 v3 + crtouch

Add-ons

No response

Bed Leveling

UBL Bilinear mesh

Your Slicer

None

Host Software

None

Don't forget to include

Additional information & file uploads

No response

Bob-the-Kuhn commented 1 year ago

I expect you're getting a probing failed error. That's usually caused by Z_PROBE_LOW_POINT beeing set too high. Try lowering it by 2 mm and see what happens.

It also might be your BLTouch. I stopped using them a couple of years ago because they just weren't reliable enough.

jarvis710 commented 1 year ago

Until now it worked perfectly for me, changing the motherboard does not take 15 days. The problem appears to appear in a certain percentage of mesh completion. (in 5x5 at point 21, in 10x10 at point 72 and in 15x15 at point 196). I had Z_PROBE_LOW_POINT at -3 and there was the problem and at -2 the same. NOZZLE_TO_PROBE_OFFSET { -44, -7, -2.23 } PROBING_MARGIN 10 Z_PROBE_LOW_POINT -2 Z_PROBE_OFFSET_RANGE_MIN -10

define Z_PROBE_OFFSET_RANGE_MAX 10

ellensp commented 1 year ago

Whenever there are homing or leveling issues, we now ask everyone to follow a standard procedure to gather more information so that we're not just taking stabs in the dark. Here is the boilerplate:

Repeat this procedure, if needed, to demonstrate inconsistencies. From these logs we should hopefully get a better idea of what's going on with your machine.

jarvis710 commented 1 year ago

These were the results of what you suggest to me; but as you can see g29 does nothing. Every time I've tried the same, same result. Connecting....txt

jarvis710 commented 1 year ago

from pronterface or cura that was the result just like from the screen console, it's as if it didn't accept the g29 command externally. if i run the g29 command from the screen interface, pronterface returns this. //action:notification Probing Point 194/225 //action:notification Probing Point 195/225 //action:notification Probing Point 196/225 //action:notification PIKA-SKRME3V3-BLTUBL-MPC Ready. //action:notification Doing G29 //action:notification PIKA-SKRME3V3-BLTUBL-MPC Ready. //action:notification Doing G29 //action:notification PIKA-SKRME3V3-BLTUBL-MPC Ready. //action:notification Doing G29 //action:notification PIKA-SKRME3V3-BLTUBL-MPC Ready. //action:notification PIKA-SKRME3V3-BLTUBL-MPC Ready. //action:notification PIKA-SKRME3V3-BLTUBL-MPC Ready. //action:notification PIKA-SKRME3V3-BLTUBL-MPC Ready. //action:notification PIKA-SKRME3V3-BLTUBL-MPC Ready

but on the printer screen, before, a probing failure sign jumped at least 2 times, placing the nozzle on the bed and then continuing, until reaching the same point that I attached before, which would be the end; but on the screen it notifies that: bed leveling complete. missing probe points have been smart filled

ellensp commented 1 year ago

@jarvis710 you have lots of 'crap' in your configs

you have #define SERIAL_PORT_3 1 but port 1 is on the cr10 display port, and you have a cr10 stock display enabled. Disable this serial port.

you have DISTINCT_E_FACTORS but only one extruder. Disable this

you have UBL_HILBERT_CURVE when have issue with UBL, disable this, it not what could be called essential

You have #define CONTROLLER_FAN2_PIN FAN0_PIN // Set a custom pin for second controller fan But FAN0_PIN = FAN_PIN which cannot be used as this is always the part cooling fan. Disable this.

You have #define INPUT_SHAPING_X #define INPUT_SHAPING_Y Probably not a good idea when you having issues, disable this for now.

You have #define SDCARD_CONNECTION This is just invalid, it needs a parameter 'LCD', 'ONBOARD', 'CUSTOM_CABLE'

You have #define MEATPACK_ON_SERIAL_PORT_2 But serial port 2 is the tft! No tft speaks meatpack to my knowledge. Disable this

Try these cleaned up configs

Cleaned_up_Configuration.zip

jarvis710 commented 1 year ago

@ellensp Sorry for not saying anything, but thank you very much. I have been busy these days and I have not been able to thank you. Although I think it is more of a bad calculation of the mesh since if I print it from the menu on the screen; this is not complete. There is a displacement of about 5cm according to the last time I was able to look at the printer.

github-actions[bot] commented 1 year ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.