Z Axis not adjusting for generated Bed Mesh
-
@Veti Yes they are LOL. I only changed the build surface "sheet" so no affect on X and Y offsets.
-
i am just trying to get more information out as you did not even post the bare minimum that is suggested
please post all relevant information.
see
https://forum.duet3d.com/topic/5909/guide-for-posting-requests-for-help/3 -
If you send M122 during the print does it show
compensation: meshin there?If i says
compensation: noneinstead, then it means the mesh hasn't been loaded yet with G29 S1 (or by creating a fresh mesh with G29)If it is loaded, do you have a M376 command anywhere to set a taper off height for the compensation?
Are the motors not moving at all?
The X Y offset is relevant, because if the probe offset from the nozzle isn't taken into effect, the resulting heightmap won't be accurate for the actual nozzle position. This can result in areas being low or high when they shouldn't be.
And post your files if you want help, without the configuration files we can only guess at what's happening.
-
@Phaedrux here is the reply from the M122. I don't see it but you said it was on before. M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 08DJM-9178L-L4MSJ-6JTD8-3S86L-K826N
Used output buffers: 3 of 24 (22 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 93912 of which 52 recycled
Exception stack ram used: 648
Never used ram: 8480
Tasks: NETWORK(ready,268) HEAT(blocked,1224) MAIN(running,1732) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 152:05:05 ago, cause: software
Last software reset at 2020-12-31 07:13, reason: User, spinning module GCodes, available RAM 8528 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 32.6, current 41.4, max 42.7
Supply voltage: min 23.7, current 24.0, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: ok, SG min/max 0/1023
Driver 1: ok, SG min/max 0/1023
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max 0/1023
Driver 4: standstill, SG min/max not available
Date/time: 2021-01-06 15:19:44
Cache data hit count 4294967295
Slowest loop: 219.38ms; fastest: 0.14ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 5.3ms, write time 45.1ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 162, MinFreeDm: 105, MaxWait: 37529363ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 165628, completed moves: 165597, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: 3
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X170.996 Y148.023 E2.0563" in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 208.03ms; fastest: 0.09ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 2
WiFi firmware version 1.23
WiFi MAC address bc:dd:c2:31:a5:92
WiFi Vcc 3.40, reset reason Unknown
WiFi flash size 4194304, free heap 25992
WiFi IP address 192.168.1.10
WiFi signal strength -55dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
@Phaedrux also here in my config. Not seeing the M376. I thought I hade a fade hight set but may be thinking of another build or something
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.7 on Thu Nov 19 2020 18:14:00 GMT-0800 (Pacific Standard Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"SK Dick" ; set printer name
M669 K1 ; select CoreXY mode; Network
M551 P"SK GO" ; set password
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S0 ; physical drive 2 goes backwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X200.00 Y200.00 Z400.00 E420.00 ; set steps per mm
M566 X600.00 Y600.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z360.00 E4800.00 ; set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z100.00 E10000.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E550 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y-28 Z-2 S1 ; set axis minima
M208 X310 Y300 Z320 S0 ; set axis maxima; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-26 Y0 Z1.5 ; set Z probe trigger value, offset and trigger height
M557 X5:290 Y6:290 S34 ; define mesh grid; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S100 ; set temperature limit for heater 0 to 100C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C; Custom settings are not defined
; Miscellaneous
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
M501 -
@Kwad3d said in Z Axis not adjusting for generated Bed Mesh:
Bed compensation in use: mesh
Well it shows mesh in use, so if that was during a print, it should be active.
Can you send M376 by itself in the console to see what it replies with? You can disable it with M376 H0.
Can you post a screenshot of your heightmap?
Also your homeall and slicer start gcode so we can see where it's being enabled?
-
@Kwad3d said in Z Axis not adjusting for generated Bed Mesh:
M566 X600.00 Y600.00 Z12.00
You should also increase your Z jerk to at least 60
-
@Phaedrux ok here is my homeall.g
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.1.7 on Thu Nov 19 2020 18:14:00 GMT-0800 (Pacific Standard Time)
G91 ; relative positioning
G1 H2 Z10 F6000 ; lift Z relative to current position
G1 H1 X-315 Y-341 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-315 ; home X axis
G1 H1 Y-341 ; home Y axis
G1 X5 Y5 F6000 ; go back a few mm
G1 H1 X-315 F360 ; move slowly to X axis endstop once more (second pass)
G1 H1 Y-341 ; then move slowly to Y axis endstop
G90
G1 X30 Y30 F6000 ; go to first probe point
G30 ; home Z by probing the bed
G90 ; absolute positioning
;G92 Z0 ; set Z position to axis minimum (you may want to adjust this); Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning;G91 ; relative positioning
;G1 H2 Z5 F6000 ; lift Z relative to current position
;G1 H1 X-315 Y-341 F1800 ; move quickly to X or Y endstop and stop there (first pass)
;G1 H1 X-315 ; home X axis
;G1 H1 Y-341 ; home Y axis
;G1 X5 Y5 F6000 ; go back a few mm
;G1 H1 X-315 F360 ; move slowly to X axis endstop once more (second pass)
;G1 H1 Y-341 ; then move slowly to Y axis endstop
;G1 H1 Z-325 F360 ; move Z down stopping at the endstop
;G90 ; absolute positioning
;G92 Z0 ; set Z position to axis minimum (you may want to adjust this) -
@Phaedrux S3d start G code. Guess I should try cura as I swear it worked on it.
G28 ; home all axes
G29 S1
G1 Z5 F3000 ; lift
G1 X10 Y10 F1500 ; move to prime
G1 Z0.2 F3000 ; get ready to prime
G92 E0 ; reset extrusion distance
G1 X120 E15 F600 ; prime nozzle
G1 X140 F5000 ; quick wipe -
@Phaedrux So looks like the majority of the mesh is under the 0 mark on the hight map. Could that be the issue?
-
@Phaedrux and then M376 came back with this
Bed compensation is not taperedDo I need to enter the M376 H0 Still?
-
@Kwad3d said in Z Axis not adjusting for generated Bed Mesh:
G1 X30 Y30 F6000 ; go to first probe point
G30 ; home Z by probing the bedPart of the problem could be that you're not probing the center of your bed. Try changing that X30 Y30 to place the probe at the center of the bed. Change homez as well.
Then home all again and redo your mesh.
@Kwad3d said in Z Axis not adjusting for generated Bed Mesh:
Bed compensation is not tapered
Do I need to enter the M376 H0 Still?No that means it hasn't been configured yet and the default is H0 (off)
-
@Phaedrux Ok I will do that. It there a setting limiting the Z travel from going into negative territory?
-
Yes, the M208 minima, which you already have set for -2mm so it should be able to go below 2mm below Z0. However that doesn't really affect mesh compensation because technically the mesh is adjusting the Z axis to maintain Z0 anyway it may have to go up or down, so it's not limited by M208. Baby stepping however will be limited to prevent people from crashing their head too badly.
-
can you post a picture of your hotend with the bltouch?
-
-
@Phaedrux So not sure exactly what it was but my guess is the low acceleration on the z axis as you pointed out should be raised to 60. I placed 3mm of carbon under the front to exaggerate the needed compensation and it seems to be following it pretty well. there are a few spots where it sill print just a little too high but I will try increasing the probe points to see if it improves on it. But overall its usable so im happy. thanks again for helping.
