Drastic improvements with BL Touch disabled

[Phaedrux]

Can you do the G92 Z0 / G30 S-1 trigger height measurement test at different locations on the bed to see if the trigger height is varying with XY position?

[deckingman]

@ryanp To be clear, are you now saying something contrary to your first post which was (quote again)

"So I simply disabled all mesh bed compensation. Just home the hot end, level the corners, and print.
And now I have ridiculously smooth first layers, with no movement in the z axis."

So are you now saying that with mesh compensation disabled, your first layers are no longer "ridiculously smooth"?

[deckingman]

@ryanp said in Drastic improvements with BL Touch disabled:

Looking at this logically, and breaking things down a bit you said

..............................
So I disabled the mesh and when with manual leveling. It worked decently. In the mean time I was reviewing things about the BL Touch and mesh leveling to make sure I hadn't overlooked anything in the past. A refresher.

During the time my printer was constantly going. Not failures, great prints.

Then all of a sudden I was having first layer issues. ...................

So in nutshell, without mesh compensation things were going well then suddenly you had first layer issues. Therefore, logic would dictate that there is some sort of mechanical issue or hot end problem or layer adhesion problem which is leading to inconsistency. Mesh compensation will only mirror this inconsistency - it won't fix it.

[RyanP]

@deckingman

All of this I very much understood. This bed was never like this before this week. It is warpy, but not slanted. What I found at the beginning of the week was that the mesh seemed to over compensate for the warpiness lending to rough first layers.

Removing the mesh certainly helped at the beginning of the week. But something mechanical has obviously happened during the week to lend to this major slant problem.

What I can't wrap my head around is how the nozzle, which is a relatively fixed distance from the BL Touch pin, can be squared up and safely touching in each corner, and then the mesh turn out so slanted.

Sunken center, and warpy dips....fine. But the nozzle safely touches in all four corners and it is not represented as such in the mesh.

[RyanP]

@Phaedrux @deckingman

I have now disassembled the bed platform, turned it over, and re-secured it. removed and rotated the build plate, re-secured it.

Its amazing how much time you can lose on a mechanical issue.

@Phaedrux regarding the G92 Z0 / G30 S-1, I did this earlier today and started an excel spreadsheet to track the issues. I didn't finish it as it was immediately apparent that the bed was sloping downward at the front (Yaxis), just like the mesh shows. X Axis was relatively stable down to 0.015mm.

Still working on things.

[RyanP]

Its a start.

[zapta]

"Drastic improvements with BL Touch disabled"

I should get one for my printer and disable it.

[RyanP]

@zapta

Thanks for your input.

[o_lampe]

@ryanp said in Drastic improvements with BL Touch disabled:

What I can't wrap my head around is how the nozzle, which is a relatively fixed distance from the BL Touch pin, can be squared up and safely touching in each corner, and then the mesh turn out so slanted.

The only difference I see is the Z-offset. You align the bed manually with the nozzle touching the bed, but the mesh routine stops around 2.6mm above the bed. You already replaced the Z-nuts, but something (had) happen during the last 2.6mm.
Maybe Z-acceleration is too high? The same value applies for deceleration. That would get worse when you use multiple small moves to lower the nozzle.

Another thing I noticed is the 'bellows' like up and down along X-axis of your last heightmap. Why is every other probe point lower or higher?

[engikeneer]

@ryanp asking the silly questions, but was mesh compensation disabled when you did the nozzle height test? I ended going round and round in circles when I first started using auto bed levelling because I had mesh compensation enabled at the same time (so it was trying to level a compensated bed and the two things just fought each other).

[Hornetrider]

Hi @RyanP

I have had similar issues with my printer concerning the bed leveling.
Have you tried to mechanically align all axis to the bed?

What helped me was the following procedure:

1. Check with a digital Bevel box if the frame of printer is leveled (x, Y and Z Frame)
   -> If not, get it leveled
2. Check if the bed is leveled with digital Bevel Box
   -> use X & Y Frame as reference (zero bevel box to that reference)
   -> Level it out as good as possible
3. Check X and Y axis are leveled to the bed with a caliper and get this down to 0.1..0.2 mm
   -> It might be that axis are out of level to the frame

Funny thing though, even after mechanically aligning my printer I had a weird effect on the height map.
My finding is, that if the height map shows a clear deviation to one side (mostly X-axis) then the mechanical alignment to the bed might be poor.

[RyanP]

Still Working on it

Corner One Probe
4.309 mm
4.307 mm
4.306 mm

Corner 2 Probe
3.981 mm
3.983 mm
3.983 mm

Corner 3 Probe
3.380 mm
3.388 mm
3.385 mm

Corner 4 Probe
3.933 mm
3.929 mm
3.931 mm

[RyanP]

Im taking a break from it. I have other working machines and need to take a break from it. Get back to it tomorrow.

[Phaedrux]

Your probe results look consistent in one spot, which is good, but they also seem to vary with XY position a bit still. Dipping off to the back side by the looks of the map?

The fact that your adjustments and re-alignments are making a difference is a good sign though.

[RyanP]

@phaedrux

Well, I don't even know where to begin. As I previously posted on Saturday, I had gotten close to fixing my issue with my bed and probing, but was going to walk away for a few days (canadian long weekend).

I've come back to this machine now with a clear mind and a few ideas.

I turn the machine on and warm it up. This machine is using the Duet 2 Maestro, and 2.05 firmware.

I hit the home button:

Print head moves X and Y to their endstops, then to the center of the bed. The BL Touch probe is deployed properly, touches the glass surface twice and reports back the correct z-offset and moves the head up to the expected position:

But as soon as it stops its motion the head position for the Z-axis turns from 11.77 to this:

Now the machine is locked up and I cannot move the head with the DWC controls or macros.

I'm starting to think that the Maestro board is pooched, but I really have no idea. I have a backup Duet 2 Wifi board here that I can replace the Maestro with, but I would rather know for sure.

[droftarts]

@ryanp post your homeall.g file?

Ian

[RyanP]

@droftarts

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Tue Feb 18 2020 18:08:45 GMT-0500 (Eastern Standard Time)
G91                     ; relative positioning
G1 H2 Z5 F9000        ; lift Z relative to current position
G1 H1 X-240 Y-240 F3000 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X20 Y20 F3000      ; go back a few mm
G1 H1 X-240 Y-240 F1000  ; move slowly to X and Y axis endstops once more (second pass)
G90                     ; absolute positioning
G1 X110 Y80 F9000 	; go to center of bed  ; go to first bed probe point and home Z
G30                     ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
G91                   ; relative positioning
G1 Z5 F9000            ; lift Z relative to current position
G90                   ; absolute positioning
G29 S1                  ; absolute positioning

[Phaedrux]

I wonder if it's a problem from loading the heightmap. Can you try deleting the heightmap.csv file and recreating it fresh?

[RyanP]

@phaedrux
Will do.

[o_lampe]

@ryanp said in Drastic improvements with BL Touch disabled:

This machine is using the Duet 2 Maestro, and 2.05 firmware.

Did you go through 'known bugs' related to RRF 2.0x? Maybe there were unsolved issues with BLtouch?

I have checked an old SD-card image from RRF2.05 and there are retractprobe.g and unretractprobe.g in the /sys folder. I remember, they messed up my homing routine, because they contained some BS....
I didn't know, that 'G30' always calls them, if present...