Dual Z - second stepper not moving for mesh leveling in 3.3rc2
-
I have a dual Z setup with M584 Z2:3. System running on 3.3rc2. It has been working correctly in FW 3.3 ß i think. Since 3.3rc1 when printing, only one stepper (Z2) is adjusting level according to mesh. The second stepper on Z3 is not doing any movement during print for mesh leveling. It works for next layer and other movements but not within the print for bed compensation. It is visible and checked that stepper Z2 works correct.
Does anyone have the same issue?
-
Can you share your full config.g, homeall.g, bed.g, slicer start gcode as well as the results of M122 and M98 P"config.g"?
-
@phaedrux here u go:
config.g:
; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.8 on Fri Nov 20 2020 10:23:05 GMT+0100 (CET); Adoptions:
; - Dual Z motors
; - Microstepping 256 for all motors
; - BLTouch config incl. Z Endstop with BLTouch
; - Optical endstop config for X and Y
; - Thermistor set to Trianglelab-K500Thermoelement
;
; Do autotune for PID using ;https://duet3d.dozuki.com/Wiki/Tuning_the_heater_temperature_control
; and add results to row 70 M307 command for heater sensor; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"SecKitGo2" ; set printer name
M669 K1 ; select CoreXY mode; Wait for 1LC to startup
G4 S1; Drives
M584 X0 Y1 Z2:3 E121.0 ; set drive mapping
M569 P0 S1 D3 V400 ; physical drive 0 goes forward X, StealthCoph2, V 400
M569 P1 S1 D3 V400 ; physical drive 1 goes forward Y, StealthCoph2, V 400
M569 P2 S0 ; physical drive 2 goes backward Z0 (left)
M569 P3 S0 ; physical drive 3 goes backward Z1 (right)
M569 P4 S1 ; physical drive 4 goes forward E0
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X200 Y200 Z3200 E395 ; set steps per mm (X,Y,Z = 0.9°, E = 1.8°)
M566 X400.00 Y400.00 Z3.8 E600.00 ; set maximum instantaneous speed changes (mm/min) (jerk)
M203 X30000.00 Y30000.00 Z600.00 E5000.00 ; set maximum speeds (mm/min)
M201 X1250.00 Y1250.00 Z1200.00 E6000.00 ; set accelerations (mm/s^2) (accelleration)
M906 X840 Y840 Z1050 E1200 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeoutM593 F28.65 ; set dynamic accelleration to compensate ringing
; Pressure Advance
M572 D0 S0.033; Axis Limits
M208 X-15:328 Y312 Z350 S0 ; Optimum axis limits; Z-Probe
M950 S0 C"121.io0.out" ; create servo pin 0 for BLTouch
M558 P9 C"^121.io0.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-26 Y-5 Z1.4 ; set Z probe trigger value, offset and trigger height
M557 X10:270 Y10:270 P5 ; define mesh grid (5 probe segments x and y); Endstops
M574 X1 S1 P"io1.in" ; configure active-high endstop for low end on X via pin io1.in
M574 Y2 S1 P"io2.in" ; configure active-high endstop for high end on Y via pin io2.in
M574 Z1 S2 ; configure Z-probe endstop for low end on Z;Filament sensor
M591 D0 P5 C"io3.in" R30:150 E3.0 S1 ; Duet3D laser sensor for extruder drive 0, connected to IO_3, tolerance 30 to 150%, 3mm comparison length, disabled;Bed Lead Screws (Dual Z)
M671 X-5:300 Y157:157 S5 ; dual z lead screws @ -5:157 and 300:157, max correction 5mm; Bed Temp Sensor
M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 Q100 ; create bed heater output on out0 and map it to sensor 0
M307 H0 R0.359 C1021.0 D6.13 S1.00 V23.9 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C; Hotend Temp Sensor (PT1000 E3D Sensor)
M308 S1 P"121.temp0" Y"pt1000" ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"121.out0" T1 ; create nozzle heater output on out1 and map it to sensor 1
;M307 H1 R2.816 C30.4 D7.51 S1.00 ; Heater parameters based on AutoTune
M307 H1 R2.815 C285.5 D7.60 S1.00 ; Heater parameters based on AutoTune
M143 H1 S300 ; set temperature limit for heater 1 to 300C; Fans
M950 F0 C"121.out2" Q500 ; create fan 0 on pin 121.out2 and set its frequency (PARTCOOLING_FAN)
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"121.out1" Q500 ; create fan 1 on pin 121.out1 and set its frequency (HEATBREAK_FAN)
M106 P1 H1 T60 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"out4" Q500 ; create fan 2 on pin out4 and set its frequency (DUET COOLING FAN)
M106 P2 S0.2 H-1 ; set fan 2 value. Thermostatic control is turned off; Toolboard 1LC @ address 121
M563 P0 D0 H1 F0 S"1LC" ; 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; Miscellaneous
M575 P1 S1 B57600 ; enable support for PanelDue; Allways load config-override.g
;M501 ; Load config-override.g; BLTOUCH PREP
G4 S1
M280 P3 S160 I1 ; Alarm Release and Push-Pin UP just in case it's in alarm and deployed
G4 S1
M402 ; Retract probe just in case it's down; Select first Tool
T0 ; select first toolhomeall.g:
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.1.8 on Fri Nov 20 2020 10:23:05 GMT+0100 (CET)
G91 ; relative positioning
G1 H2 Z10 F6000 ; lift Z relative to current position
G1 H1 Y310 F6000 ; home Y axis
G1 H1 X-328 F6000 ; home X axis
G1 X5 Y-5 F6000 ; go back a few mm
G1 H1 Y310 F360 ; then move slowly to Y axis endstop (second pass)
G1 H1 X-328 F360 ; move slowly to X axis endstop once more (second pass)
G90 ; absolute positioning
G1 X150 Y150 F6000 ; go to bed center and home Z
G30 ; home Z by probing the bed; Uncomment the following lines to lift Z after probing
G91 ; relative positioning
G1 Z5 F6000 ; lift Z relative to current position
G90 ; absolute positioningG29 S1 ; load ABL height map
bed.g:
; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.1.8 on Fri Nov 20 2020 10:23:05 GMT+0100 (CET)M561 ; clear any bed transform
G28 ; home
G1 Z10 F3000 ; move Z down 20mm
G1 X155 Y155 ; move to center of bed
G30 P0 X15 Y155 Z-99999 ; probe near a leadscrew, half way along Y axis
G30 P1 X275 Y155 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motorsslicer start code:
M104 S{material_print_temperature_layer_0} ;set hot end temp
M140 S{material_bed_temperature_layer_0} ;set bed temp
M109 S{material_print_temperature_layer_0} ;wait for hot end temp
M190 S{material_bed_temperature_layer_0} ;wait for bed temp
G28 ;Home
G29 L1 ;Load bed mesh from slot 1
G92 E0 ;Reset Extruder
G1 Z2.0 F3000 ;Move Z Axis up
G1 X4.1 Y20 Z0.28 F5000.0 ;Move to start position
G1 X4.1 Y200.0 Z0.28 F1500.0 E15 ;Draw the first line
G1 X4.4 Y200.0 Z0.28 F5000.0 ;Move to side a little
G1 X4.4 Y20 Z0.28 F1500.0 E30 ;Draw the second line
G92 E0 ;Reset Extruder
G1 Z2.0 F3000 ;Move Z Axis upM122:
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3RC2 (2021-05-11 14:55:28) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S4-6J1DJ-3S46P-9S46D
Used output buffers: 6 of 40 (19 max)
=== RTOS ===
Static ram: 150680
Dynamic ram: 62052 of which 308 recycled
Never used RAM 141152, free system stack 128 words
Tasks: SBC(ready,5.0%,270) HEAT(delaying,0.0%,299) Move(notifyWait,0.0%,267) CanReceiv(notifyWait,0.0%,773) CanSender(notifyWait,0.0%,373) CanClock(delaying,0.0%,341) TMC(notifyWait,7.3%,59) MAIN(running,87.7%,619) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:08:16 ago, cause: power up
Last software reset time unknown, reason: MemoryProtectionFault mmarValid daccViol, none spinning, available RAM 143492, slot 0
Software reset code 0x4172 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x00400804 BFAR 0xa5a5a5bb SP 0x204333f8 Task SBC Freestk 623 ok
Stack: 00000000 00000002 20420b58 00000000 2040e368 0043a9e7 0043a9ea 61000000 a5a5a5a5 a5a5a5a5 00000000 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
Step timer max interval 182
MCU temperature: min 19.1, current 35.6, max 35.7
Supply voltage: min 23.8, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.9, current 12.0, max 12.0, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 92200, standstill, reads 22327, writes 21 timeouts 0, SG min/max 0/569
Driver 1: position 28200, standstill, reads 22328, writes 21 timeouts 0, SG min/max 0/165
Driver 2: position 20323, standstill, reads 22330, writes 19 timeouts 0, SG min/max 0/221
Driver 3: position 0, standstill, reads 22330, writes 19 timeouts 0, SG min/max 0/223
Driver 4: position 0, standstill, reads 22338, writes 11 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 22338, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-05-20 15:09:57
Slowest loop: 175.21ms; fastest: 0.03ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 294529ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 20, completed moves 20, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 4413, send timeouts 0, received 5818, lost 0, longest wait 2ms for reply type 6049, peak Tx sync delay 6, free buffers 49 (min 48)
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 1ms ago
RX/TX seq numbers: 16915/16915
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x2c8c0
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.3-rc1
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 0.10
Codes per second: 0.00
Maximum length of RX/TX data transfers: 2724/720M98:
M98 P"config.g"
Error: M591: Filament monitor port must be on same board as extruder driver -
If you're using expansion boards can you also provide the M122 B# for those boards as well? (where # is the can address of the expansion board).
-
@cascade said in Dual Z - second stepper not moving for mesh leveling in 3.3rc2:
Duet 3 MB6HC version 3.3RC2
@cascade said in Dual Z - second stepper not moving for mesh leveling in 3.3rc2:
Duet Control Server v3.3-rc1
It also looks like your board is running 3.3 RC2 but your SBC is still only running 3.3 RC1.
Can you try running sudo apt update and sudo apt upgrade again?
-
@phaedrux I did run update and upgrade again and it updated everything:
=== Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.3RC2 (2021-05-11 14:55:28) running on Duet 3 MB6HC v1.01 or later (SBC mode) Board ID: 08DJM-956L2-G43S4-6J1DJ-3S46P-9S46D Used output buffers: 1 of 40 (18 max) === RTOS === Static ram: 150680 Dynamic ram: 61836 of which 524 recycled Never used RAM 141152, free system stack 178 words Tasks: SBC(ready,6.7%,321) HEAT(delaying,0.0%,321) Move(notifyWait,0.0%,300) CanReceiv(notifyWait,0.0%,798) CanSender(notifyWait,0.0%,373) CanClock(delaying,0.0%,353) TMC(notifyWait,7.1%,93) MAIN(running,85.8%,922) IDLE(ready,0.3%,29), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:00:35 ago, cause: software Last software reset at 2021-05-20 15:20, reason: MemoryProtectionFault mmarValid daccViol, GCodes spinning, available RAM 140728, slot 1 Software reset code 0x4963 HFSR 0x00000008 CFSR 0x001703c2 ICSR 0x0043c804 BFAR 0x00000001 SP 0x2041b180 Task MAIN Freestk 1663 ok Stack: 20419728 20419728 00000001 bfffbfff 003fffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff Error status: 0x00 Aux0 errors 0,0,0 Aux1 errors 0,0,0 Step timer max interval 127 MCU temperature: min 33.6, current 35.4, max 35.5 Supply voltage: min 23.9, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 11.9, current 12.0, max 12.0, under voltage events: 0 Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Driver 0: position 0, standstill, reads 65151, writes 16 timeouts 0, SG min/max 0/0 Driver 1: position 0, standstill, reads 65151, writes 16 timeouts 0, SG min/max 0/0 Driver 2: position 0, standstill, reads 65153, writes 14 timeouts 0, SG min/max 0/0 Driver 3: position 0, standstill, reads 65153, writes 14 timeouts 0, SG min/max 0/0 Driver 4: position 0, standstill, reads 65156, writes 11 timeouts 0, SG min/max 0/0 Driver 5: position 0, standstill, reads 65156, writes 11 timeouts 0, SG min/max 0/0 Date/time: 2021-05-21 07:09:12 Slowest loop: 1.17ms; fastest: 0.05ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 Movement lock held by null HTTP* is doing "M122" 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 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === CAN === Messages queued 305, send timeouts 0, received 348, lost 0, longest wait 2ms for reply type 6049, peak Tx sync delay 162, free buffers 49 (min 48) === SBC interface === State: 4, failed transfers: 0 Last transfer: 1ms ago RX/TX seq numbers: 1099/1099 SPI underruns 0, overruns 0 Number of disconnects: 0, IAP RAM available 0x2c8c0 Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.3-rc2 Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 34.18 Codes per second: 1.86 Maximum length of RX/TX data transfers: 3268/700Here is the M122 B121
Diagnostics for board 121: Duet TOOL1LC firmware version 3.3beta2+2 (2021-04-16 13:48:06) Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1) Never used RAM 2940, free system stack 0 words Tasks: Move(notifyWait,152) HEAT(delaying,80) CanAsync(notifyWait,66) CanRecv(notifyWait,78) CanClock(notifyWait,66) ACCEL(notifyWait,60) TMC(notifyWait,56) MAIN(running,339) AIN(delaying,63) Last reset 00:02:44 ago, cause: software Last software reset time unknown, reason: AssertionFailed, available RAM 3392, slot 2 Software reset code 0x0120 ICSR 0x00000000 SP 0x2000415c Task Freestk 129 bad marker Stack: 00000544 00022ffc 00019b65 20003134 00016cff 20003134 000163d1 20000ed0 00000000 00000001 00008275 200071c8 200071c8 200071e0 00000000 20000f50 00011647 000223b8 00022474 00021ac8 00019b05 200071c8 200071c8 20000f50 000083ed 200071d8 000009c7 Driver 0: position 0, 395.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 54, reads 16540, writes 12, timeouts 0, DMA errors 0, steps req 0 done 0 Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0 Peak sync jitter 10, peak Rx sync delay 198, resyncs 1, no step interrupt scheduled VIN: 24.3V MCU temperature: min 39.3C, current 39.4C, max 39.7C Ticks since heat task active 209, ADC conversions started 164204, completed 164203, timed out 0, errs 0 Last sensors broadcast 0x00000002 found 1 214 ticks ago, loop time 0 CAN messages queued 1922, send timeouts 0, received 1473, lost 0, free buffers 36, min 36, error reg 110000 dup 0, oos 0, bm 0, wbm 0 Accelerometer detected: yes, status: 00 I2C bus errors 0, naks 0, other errors 0Meanwhile i did install the LC 1.1 with the accellerometer. Will do new test for dual z after this upgrade of fw and board.
-
@Phaedrux also did upgrade the LC1. But still no luck. Only one z motor is compensating the mesh.
Heres the m122 b121 after upgrade:
Diagnostics for board 121: Duet TOOL1LC firmware version 3.3RC2 (2021-05-11 14:59:50) Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1) Never used RAM 2740, free system stack 0 words Tasks: Move(notifyWait,0.1%,99) HEAT(delaying,0.2%,81) CanAsync(notifyWait,0.0%,58) CanRecv(notifyWait,0.0%,77) CanClock(notifyWait,0.0%,66) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,2.9%,57) MAIN(running,91.8%,347) IDLE(ready,0.0%,26) AIN(delaying,5.0%,62), total 100.0% Last reset 01:00:58 ago, cause: software Last software reset time unknown, reason: AssertionFailed, available RAM 3392, slot 2 Software reset code 0x0120 ICSR 0x00000000 SP 0x2000415c Task Freestk 129 bad marker Stack: 00000544 00022ffc 00019b65 20003134 00016cff 20003134 000163d1 20000ed0 00000000 00000001 00008275 200071c8 200071c8 200071e0 00000000 20000f50 00011647 000223b8 00022474 00021ac8 00019b05 200071c8 200071c8 20000f50 000083ed 200071d8 000009c7 Driver 0: position 863711, 395.0 steps/mm, ok, SG min/max 0/244, read errors 0, write errors 1, ifcnt 109, reads 57315, writes 17, timeouts 0, DMA errors 0, steps req 1127409 done 1127166 Moves scheduled 9651, completed 9649, in progress 1, hiccups 0, step errors 0, maxPrep 720, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0 Peak sync jitter 10, peak Rx sync delay 223, resyncs 6, next step interrupt due in 2097 ticks, enabled VIN: 24.2V MCU temperature: min 36.5C, current 49.5C, max 49.8C Ticks since heat task active 200, ADC conversions started 3655788, completed 3655787, timed out 0, errs 0 Last sensors broadcast 0x00000002 found 1 205 ticks ago, loop time 0 CAN messages queued 44382, send timeouts 0, received 42993, lost 0, free buffers 36, min 35, error reg 110000 dup 0, oos 0, bm 0, wbm 0 Accelerometer detected: yes, status: 00 I2C bus errors 0, naks 0, other errors 0And btw, the accellerometer is not working. When trying to test it using
G1 X0 G4 S2 M956 P121.0 S1000 A0 G4 P10 G1 X150 F60000it results in "accellerometer not found"
-
Here's a few other things I noticed. Not sure if they will have an effect.
@cascade said in Dual Z - second stepper not moving for mesh leveling in 3.3rc2:
; Axis Limits
M208 X-15:328 Y312 Z350 S0 ; Optimum axis limitsYour M208 formatting looks a little odd. Missing minima values for Y and Z. Is the assumption that it defaults to 0?
@cascade said in Dual Z - second stepper not moving for mesh leveling in 3.3rc2:
M566 X400.00 Y400.00 Z3.8 E600.00 ; set maximum instantaneous speed changes (mm/min) (jerk)
Your Z jerk is very low. In fact, 3.8 mm/min is lower than the minimum value supported anyway. I suggest you set this to M566 Z60.
You have G29 S1 at the end of your homeall, meaning that the heightmap is going to be active during your bed.g routine, which you don't really want. I suggest you remove the G29 from your homeall and leave it in your slicer start gcode.
Which Z motor is working during the mesh and which is not? Is the motor shaft loose in the coupler preventing it from tuning or is the motor itself for sure not turning? Does it behave correctly during bed.g?
@cascade said in Dual Z - second stepper not moving for mesh leveling in 3.3rc2:
it results in "accellerometer not found"
the "Accelerometer not found" error is because you are running in SBC mode. That is fixed in the imminent 3.3RC3 release. However, you will still need to be in standalone mode to collect accelerometer data.
-
@phaedrux thx for recommendations. will change them. minima for y and z should be 0.
z motor 2 is not compensating. it works though in all other aspects (bed.g, probing, moving z) but not for mesh compensation. in prev versions both motors moved the same, now only 1st motor works. nothing loose btw. was the first thing i checked incl. cabeling etc. but as said, in all other modes z works well.
-
@phaedrux changed suggested values for z-jerk, axis limits and G29 (-> moved to slicer start code). but still no changes. same issue persists. motor 2 (left-z) works as expected, motor 3 (right-z) is not compensating. will try to record a video to visualize.
-
Finally found the problem:
It seemed, that my heightmap was corrupt. After deleting and recreating with mesh compensation, both z motors work again.
@Phaedrux thx for assisting and helping
-
Interesting. Glad you got it sorted. I guess in future I'll have to remember if in doubt, delete the map and try again.
