First Layer

npm1

Hi,
I've shifted over from einsyrambo, and like my previous experiences with the duet it is awsome. However for the life of me the first layer seams the same issue as before it appears slanted on the bed as shown in the pictures below
alt text

Please Help, This is the same issue as with the pervious time.
alt text

npm1

This post is deleted!

Phaedrux

How are you leveling the bed?
If it's an i3 style X gantry how are you leveling each side of it?
Are you using mesh compensation?

dc42

It looks to me like a classic case of dual Z motors being out of sync. Does the printer have dual Z motors?

npm1

@Phaedrux
yes i am, and have just recently added G29 S1 straight after G29; in the gcode

@dc42
How would I sync the motors I forgot.

Phaedrux

https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors

npm1

Not to worry I think I've resolved the issue.

GUIDE & TIPS
-Ensure that axis minima on the Z axis is set up as a negative value especially for prusa style printers, as to avoid any premature errors
-Probe at intended heat and save height map.
-Reload the heightmap through G29 S1 after probing G32 in GCODE of all prints
-Run G29 every other day with a spacing range of 10-20.
-Include G29 S1 in the bed.g,
-reestablish the z=0 datum by using G30 F300

For any one looking out for config to work backwards from, DO NOT UPLOAD AND USE, use only for reference purposes.

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool on Mon Apr 09 2018 16:57:18 GMT+0100 (GMT Daylight Time)
M561 ; clear any bed transform
; Probe the bed at 4 points
G30 P0 X15 Y20 H15 Z-99999
G30 P1 X15 Y195 H15 Z-99999
G30 P2 X215 Y195 H15 Z-99999
G30 P3 X215 Y20 H15 Z-99999
G30 P4 X92 Y90 H15 Z-99999 s
G1 X92 Y90
G30 F300
G29 S1;

*; Axis Limits
M208 X0 Y-40 Z-2 S1 ; Set axis minima
M208 X250 Y210 Z200 S0 ; Set axis maxima
M564 S0 H0

; Z-Probe
M574 Z2 S2 ; Set endstops controlled by probe
M558 P5 H25 F360 I1 T6000 ; Set Z probe type to modulated and the dive height + speeds
G31 P500 X13 Y20 Z-0.5; Set Z probe trigger value, offset and trigger height
M557 X15:220 Y20:195 S10; Define mesh grid

Phaedrux

@npm1 said in First Layer:

G31 P500 X13 Y20 Z-0.5; Set Z probe trigger value, offset and trigger height

I find it strange that your trigger height is negative. That would imply that your nozzle is below the bed surface when the probe triggers.

npm1

@Phaedrux if I was to set to positive it drags through the PEI, this just gives me a chance to baby step on each print, this still being tweaked but the main thing for me is it not dragging through the sheet

npm1

So I've done further tweaking, and i might be onto something...
I ran M48.g as describe by this post: M48

M292
G32 bed probe heights: -0.024 -0.013 -0.021 -0.012 -0.025 -0.020 -0.025 -0.030 -0.022 -0.041, mean -0.023, deviation from mean 0.008

Before I did this i was tweaking my bed according to the heightmap.csv
01:25:46
G29 S0
9 points probed, min error -0.048, max error 0.136, mean 0.029, deviation 0.054
Height map saved to file heightmap.csv This was done when heated at PLA Temps

Its looks like the following:
RepRapFirmware height map file v2 generated at 2019-06-28 01:25, min error -0.048, max error 0.136, mean 0.029, deviation 0.054
xmin,xmax,ymin,ymax,radius,xspacing,yspacing,xnum,ynum
25.00,195.00,0.00,195.00,-1.00,70.00,70.00,3,3
0.063, 0.026, 0.043
0.064, -0.007, -0.048
0.136, 0.029, -0.043

When cold it looks like the following:
RepRapFirmware height map file v2 generated at 2019-06-28 01:14, min error 0.014, max error 0.267, mean 0.111, deviation 0.071
xmin,xmax,ymin,ymax,radius,xspacing,yspacing,xnum,ynum
25.00,195.00,0.00,195.00,-1.00,70.00,70.00,3,3
0.161, 0.090, 0.110
0.154, 0.051, 0.014
0.267, 0.101, 0.048

The question is, what do you reckon, do you see these tweaks improving my first layer...?

For any one interested in the files, visit the Github Page:
Github