Bed leveling mesh calibration not working

Mythbear74

Heres the others

; config-override.g file generated in response to M500 at 2024-02-19 18:43
; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 R2.000 C140.000:140.000 D65.00 S1.00 V0.0 B0 I0
M307 H1 R3.192 C111.500:105.000 D6.72 S1.00 V24.0 B0 I0
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.1.10+4-LPC on Tue Jan 19 2021 17:25:01 GMT+0800 (中国标准时间)
M561 ; clear any bed transform
G29  ; probe the bed and enable compensation

Screenshot 2024-02-25 121347.png
Screenshot 2024-02-25 121543.png

I don't have a mesh.g

soare0

@Mythbear74
I see you have no ideea what you are doing there. Dont know why you used R parameter. I think that is for a delta printer.
If you understand what I am saying (as I think you are translating online from chinese), try something like this:

M557 X10:180 Y10:180 S40

You will have a 16 point mesh bed.
However,

M557 X10:180 Y10:180 S4:4

may cover better the area, also, with 16 points mesh bed.

Mythbear74

No I’m not from China. It’s just this thing is actually a gift to me and I can just got thrown it after they set it up. I will try putting in that code and then give you an update. thanks

Mythbear74

All right, so I tried both those inputs, but it did the same problem. Is there any more information you need?

soare0

@Mythbear74
If you will put here the files, either as code or copy pasted, as well as a short clip with the problem, I am sure that they will be many to help much better than me. I am sorry, but it is difficult otherwise.
PS. It is not a problem if you eventually are from China, I just expressed the feeling that you do not understand what we are saying, wich is usually because a language barrier.
PS2. Do not insert those files as images/screen captures, as probably some of them will not fit on your monitor (I see that your config files start at line 46). Unless ... you will rotate the monitor to portrait, if you insist with screen captures.
PS3. There is also the possibility that the printer has an hardware issue, so.... files and clip needed.
PS4. Normally, it should have been a difference between your M557 and mine. Maybe you can show how the original M557 was (assuming it was the original).
PS5. If you do not try to do mesh, the printer works right?

Mythbear74

Honestly at this point I’d rather like to know how to completely eradicate the height map system so it forgets about it.
PS, I am not from china I am in the US and I am quite new to this

droftarts

@Mythbear74 said in Bed leveling mesh calibration not working:

Honestly at this point I’d rather like to know how to completely eradicate the height map system so it forgets about it.

At the end of your config.g are these three lines:

...
T0 P0
G29 S1
M501

The G29 S1 loads the mesh file called /sys/heightmap.csv, which is usually the last mesh created. If you comment that out (ie put a semicolon like ; at the beginning of the line) or just delete it, no mesh will be loaded.

However, I think the original problem of your bed mesh probe starting "in an area without anything under it" is caused by your probe offset. This is defined by the G31 command in the probe section, and more specifically I think the X and Y coordinates are incorrect. Currently you have:

; Z-Probe
M950 S0 C"Servo0"                               ; create servo pin 0 for BLTouch
M558 P9 C"^probe" H5 F800 T20000                ; set Z probe type to bltouch and the dive height + speeds
M557 X10:180 Y10:180 R-1 P2:2                      ; define mesh grid   
G31 P500 X-40 Y10 Z4.3                           ; set Z probe trigger value, offset and trigger height

To get them correct, see https://docs.duet3d.com/User_manual/Connecting_hardware/Z_probe_testing#measuring-probe-x-y-offset. The whole page is worth a read.

I've taken the liberty of adding your config.g, config-override.g and bed.g to your posts as text (cut and pasted from the files on Google Drive). We couldn't see the full config.g in your screenshots.

Ian

soare0

@droftarts said in Bed leveling mesh calibration not working:

However, I think the original problem of your bed mesh probe starting "in an area without anything under it" is caused by your probe offset. This is defined by the G31 command in the probe section, and more specifically I think the X and Y coordinates are incorrect.

Indeed, -40 it is much, but if the printer is something like a ”classic” Ender:

this may be it. Y=10 is almost sure ok, this is why I asked for some clip/photo.
Probably erasing G29 is the best Ideea, anyway...

Mythbear74

@soare0 yes but do you have a way of actually achieving the erase of the height map/G29

soare0

@Mythbear74 Del or Back keys on your keyboard?
And if you are not able at least to submit a photo with your printer or a clip with its behaviour, I am very doubtful that anybody will be able to help you with this.
Maybe Deanna Troy's mother, as she is a good mind reader ...

droftarts

@Mythbear74 The default heightmap is stored in the /sys folder with the name 'heightmap.csv'. In DWC, go to Files > System > System Directory, right click heightmap.csv, and select Delete.

But it is unnecessary, really. If you remove the G29 from config.g, it just won't load, and won't be used. RRF will report 'None' for 'Compensation in use'. If you send G29, it will try to create a new mesh based on the M557 command in config.g, so if you don't want that, delete that too.

However, all of this means that you won't be able to compensate for the bed not being perfectly flat.

Ian

Mythbear74

@droftarts thank you I will try that

Mythbear74

Is there a way I can send you guys a video of the print issue?

soare0

@Mythbear74
The last to the right button on the button row. It is true that I do not know maximum size, so maybe you will do mp4 or such?
I selcted it, to be more clear...

Mythbear74

All right, I finally found a way to send A video. https://discord.gg/G3X9ha9B

soare0

@Mythbear74 Then please send a video with the issue

Mythbear74

@soare0 are you not able to see the video?

oliof

@Mythbear74 requires joining a random discord server.

soare0

@Mythbear74 I did, it seemed for me not at all relevant for your issue. Maybe try to explain here, I do not see why continue to talk on Discord...