Solved Warning: the height map has a substantial Z offset.
-
Hi
Im running a Modix 120Z and even though Modix support has been very helpful they are struggling to figure out this one. I have two issues:
-
I can run Z-offset, bed tilt and bed levelling and these functions also seem to be working but when I print I seem to have a constant tilt anyway. Front left seems high, complete rear seems low based on first layer test prints. I have since manually shimmed this and get good results but that wasn't the point right.
-
After running bed leveling I get the following error:
M98 P"0:/macros/Calibration Macros/04_Bed Compensation"
2. Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh.
2. 100 points probed, min error -0.329, max error 0.056, mean -0.174, deviation 0.086
2. Height map saved to file 0:/sys/heightmap.csvI have seen this error being discussed before but non of the posts really come to a conclusion. Any idea's?
-
-
Can you send
M122
andM98 P"config.g"
in the gcode console tab in DWC and copy and paste the results here?Can you grab a screenshot of the heightmap being displayed?
G31 P500 X-25.5 Y26.9
Your g31 appears to be missing a Z value. Unless it's hidden inside config_probe.g. Can you please share that macro as well?
-
Hi
Thank you for your reply. After M112 I can not really do much more?!? Machine Halted. If I restart the machine and do M98 it sais M98 P "config.g" Warning: Macro file "config.g" not found
Sorry, I'm not a gcode expert by no means.
-
@AllOnScale It's M122, not M112. M112 is the emergency stop gcode: https://docs.duet3d.com/User_manual/Reference/Gcodes#m112-emergency-stop
Easy mistake to make.
@Phaedrux The config.g is also included in the initial post
-
Oeps: sorry:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.2 (2022-09-13 15:11:16) running on Duet WiFi 1.02 or later + DueX5v0.11
Board ID: 0JD0M-9X6JA-JUNSN-6JTDL-3SS6L-KTPBS
Used output buffers: 1 of 26 (26 max)
=== RTOS ===
Static ram: 23860
Dynamic ram: 76728 of which 0 recycled
Never used RAM 8492, free system stack 132 words
Tasks: NETWORK(ready,12.6%,237) HEAT(notifyWait,0.0%,317) Move(notifyWait,0.0%,304) DUEX(notifyWait,0.0%,24) MAIN(running,86.7%,438) IDLE(ready,0.7%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:01:55 ago, cause: software
Last software reset at 2022-12-07 12:11, reason: User, GCodes spinning, available RAM 8524, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x0c
Aux0 errors 0,1,0
Step timer max interval 0
MCU temperature: min 26.2, current 27.1, max 27.3
Supply voltage: min 23.8, current 24.0, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/144/144, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 93
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min 0
Driver 6: standstill, SG min 0
Driver 7: standstill, SG min 0
Driver 8: standstill, SG min 0
Driver 9: standstill, SG min 0
Driver 10:
Driver 11:
Date/time: 2022-12-07 12:13:10
Cache data hit count 4004737535
Slowest loop: 22.14ms; fastest: 0.19ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 0.5ms, write time 3.3ms, max retries 0
=== Move ===
DMs created 83, segments created 6, maxWait 14218ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 20, completed 20, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 8], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle 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
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Filament sensors ===
Extruder 0 sensor: no data received
=== DueX ===
Read count 1, 0.52 reads/min
=== Network ===
Slowest loop: 15.88ms; fastest: 0.00ms
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 0
WiFi firmware version 1.26
WiFi MAC address c8:c9:a3:40:01:46
WiFi Vcc 3.42, reset reason Power up
WiFi flash size 2097152, free heap 25912
WiFi IP address 192.168.178.124
WiFi signal strength -57dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0 -
M98 P"config.g" is not giving me any feedback after M122
-
One change that may help would be to probe Z in the center of the bed rather than the corner. Also try and probe the same point as one of the mesh points.
In homeall.g
G1 X{move.axes[0].min+5} Y{move.axes[1].min+5} F6000 ; move to front left
For X and Y identify a point in the heightmap display and use it's X Y coordinate, adjusted for the probe offset, so that the probe is above that point.
-
I'm a little unsure why but after fiddling around with the bed structure and rerunning all of a suddenly my issue has disappeared. A wild guess is that it was over constrained and deforming. I only put 4 of the 16 screws back. Bed level is better now. Error disappeared. First layer print is successful.
Thanks for the help anyway.
-
-