Triple-z G32 true bed level question
-
After it does the initial height measure in the middle, it moves to the home corner (X0, Y0) and crashes. I have set correct Z-probe offset and bed size. Not sure how to correctly set M671.
M584 X0.1 Y0.0 E0.2 Z0.3:0.4:0.5 ; set drive mapping M671 X1:1:271 Y269:43:167 S50 ; set z drive coordinatesThis how it set right and it crashes in the corner. I've entered the values in order from how the Z drivers are set up in M584.
-
@Velvia sys/bed.g file controls the bed levelling. M671 controls where the pivot point of the leadscrews are. See https://docs.duet3d.com/User_manual/Connecting_hardware/Z_probe_auto_levelling
Please post your bed.g file, firmware version and hardware version.
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
@droftarts I completely forgot about bed.g
; bed.g ; called to perform automatic bed compensation via G32 ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Sat Jul 16 2022 00:07:15 GMT+0200 (Central European Summer Time) M561 ; clear any bed transform. treat the bed as an ideal flat surface. ; Don't use parameter P of M558 here as it will reset probe offsets assigned in G31. M558 H20 F600 T12000 ; set a higher dive height H20 to prevent nozzle crash. G28 G30 P0 X3 Y10 Z-99999 G30 P1 X290 Y10 Z-99999 G30 P2 X157 Y280 Z-99999 S3 ; Don't use parameter P of M558 here as it will reset probe offsets assigned in G31. M558 H3 F600 T12000 ; set a low dive height H3 for faster mesh building. ; Mesh bed level M557 X5:300 Y35:300 S24It's a mess from previous bed design. How would I set it up, is there a guide?
M122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.4.1 (2022-06-01 21:06:56) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: ZNGJJ-3196U-D65J0-40KML-2G03Z-R300P Used output buffers: 3 of 40 (28 max) === RTOS === Static ram: 103684 Dynamic ram: 110520 of which 56 recycled Never used RAM 24260, free system stack 132 words Tasks: NETWORK(ready,15.0%,184) HEAT(notifyWait,0.0%,338) Move(notifyWait,0.0%,265) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,356) CanClock(delaying,0.0%,337) TMC(notifyWait,1.2%,71) MAIN(running,82.7%,404) IDLE(ready,0.2%,29) AIN(delaying,0.8%,264), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 02:52:19 ago, cause: software Last software reset at 2023-02-08 14:26, reason: User, GCodes spinning, available RAM 27376, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 MCU revision 3, ADC conversions started 10340125, completed 10340124, timed out 0, errs 0 Step timer max interval 955 MCU temperature: min 27.4, current 27.5, max 27.5 Supply voltage: min 23.9, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/4/4, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 71, reads 603, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 2, read errors 0, write errors 0, ifcnt 71, reads 603, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 10, read errors 0, write errors 0, ifcnt 39, reads 602, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 67, reads 603, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 67, reads 603, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 5: standstill, SG min 2, read errors 0, write errors 0, ifcnt 67, reads 603, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 19, reads 602, writes 0, timeouts 0, DMA errors 0, CC errors 0 Date/time: 2023-02-08 17:18:19 Cache data hit count 4294967295 Slowest loop: 11.62ms; fastest: 0.13ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 3.1ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 14, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 1198, completed 1198, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 1 is on, I-accum = 0.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 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 60, received 0, lost 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 33/0/0 Tx timeouts 0,0,33,0,0,27 last cancelled message type 4514 dest 127 === Network === Slowest loop: 200.66ms; fastest: 0.06ms 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 1 WiFi firmware version 1.26 WiFi MAC address f0:08:d1:03:81:45 WiFi Vcc 3.44, reset reason Power up WiFi flash size 2097152, free heap 25200 WiFi IP address 10.0.0.30 WiFi signal strength -88dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0Homegrown, grass fed and organically built 350mm delta
-
@Velvia When you say "it moves to the home corner (X0, Y0) and crashes" what actually crashes? Does it crash in X or Y, or is the nozzle too close to the bed already? I see you have G28 in bed.g. Does it lift Z at the end? Post your homeall.g as well.
Ian
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
@droftarts XY crashes, Z is fine I think. I reset the printer before anything else happens.
; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Sat Jul 16 2022 00:07:15 GMT+0200 (Central European Summer Time) G91 ; relative positioning G1 H2 Z5 F1000 ; lift Z relative to current position G1 H1 Y-350 F2500 ; move quickly to Y axis endstop and stop there (first pass) G1 Y5 F4000 ; go back a few mm G1 H1 Y-5 F200 ; move slowly to Y axis endstop once more (second pass) G1 Y1 ; move to Y1 for space G1 H1 X-350 F2500 ; home X axis (first pass) G1 X5 F1000 ; go back a few mm G1 H1 X-5 F500 ; move slowly to X axis endstop once more (second pass) G1 X1 ; move to X0.5 for space G90 ; absolute positioning G1 X150 Y150 F6000 ; go to first bed probe point and home Z G30 ; home Z by probing the bed G1 H2 Z2 ; move Z down 2mm G1 X1 Y1 F6000 ; move to the back -
Post your full config.g please.
-
; Configuration file for Duet 3 Mini 5+ (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.10 on Sat Jul 16 2022 00:07:15 GMT+0200 (Central European Summer Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"SK-Go2" ; set printer name M669 K1 ; select CoreXY mode ;M918 P1 E4 F2000000 ; configure direct-connect display ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0.0 S1 D2 ; XY 1 physical drive 0.0 goes forwards M569 P0.1 S0 D2 ; XY 2 physical drive 0.1 goes backwards M569 P0.2 S1 D2 ; E physical drive 0.2 goes forwards M569 P0.3 S0 ; Z 1 physical drive 0.3 goes backwards M569 P0.4 S0 ; Z 2 physical drive 0.3 goes backwards M569 P0.5 S1 ; Z 3 physical drive 0.3 goes forwards M584 X0.1 Y0.0 E0.2 Z0.3:0.4:0.5 ; set drive mapping M671 X1:1:271 Y269:43:167 S50 ; set z drive coordinates M350 X32 Y32 Z16:16:16 E16 I1 ; configure microstepping with interpolation M92 X400 Y400 Z800.00 E420.00 ; set steps per mm M566 X900.00 Y900.00 Z400.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X7500.00 Y7500.00 Z1000.00 E1200.00 ; set maximum speeds (mm/min) M201 X5000.00 Y5000.00 Z500.00 E250.00 ; set accelerations (mm/s^2) M906 X1400 Y1400 Z900 E800 I10 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minimum M208 X299 Y318 Z300 S0 ; set axis maximum ; TMC Trinamic Drive Tuning ; Tune tpwmthrs (V) so stealthchop runs at appropriate speeds ; and tune thigh (H) to avoid shifting into fullstep mode ; Tune stealthchop to 250mm/s, set coolstep to the same, and then limit the max speed to 120mm/s ; tpwmthrs = 12000000 / (<speed in mm/s> * 200 * 16) ; This keeps everything slow and quiet. ; Endstops M574 X1 S1 P"io5.in" ; configure active-high endstop for low end on X via pin "io5.in" M574 Y1 S1 P"io6.in" ; configure active-high endstop for low end on Y via pin "io6.in" ;M574 Z1 S2 P"io3.in" ; done under Z-probe instead ;M574 X1 S1 ; configure sensorless endstop for low end on X ;M574 Y1 S1 ; configure sensorless endstop for low end on Y ;M915 X S30 H140 R0 ; sensitivity of X and Y sensorless homing, R2 = pause print ;M915 Y S20 H140 R0 ; sensitivity of X and Y sensorless homing, R2 = pause print ; Z-Probe M574 Z1 S2 P"io3.in" ; configure Z-probe endstop for low end on Z M558 P5 C"io3.in" I1 H1 F4000:1000 T10000 A5 S0.03 ; set Z probe type as filtered digital (P5), dive height to 1 (H1), probe 5 times (A5), feedrate 3000 (F), Travel speed to and between probe points (mm/min (T10000)), mulitple probing tolerance (S) G31 P500 X21 Y10 Z1.50 ; set Z probe trigger value, offset and trigger height M557 X5:290 Y5:290 S40 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 B0 S1.00 ; 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 M308 S1 P"temp1" Y"thermistor" T100000 B3950 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S300 ; set temperature limit for heater 1 to 300C ; Fans M950 F1 C"out6" ; create fan 1 on pin out6 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on M308 S10 Y"mcu-temp" A"MCU" ; MCU temp on temp sensor 10 M950 F0 C"out5" ; create fan 1 on pin out6 and set its frequency M106 P0 S0.5 H10 T30 ; set fan 1 value. Virtual thermostatic control is turned on M912 P0 S-1.2 ; MCU temperature calibration ; Tools M563 P0 S"Volcano" 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 M501 ; load saved parameters from non-volatile memory M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss T0 ; select first tool -
@Velvia said in Triple-z G32 true bed level question:
G30 P0 X3 Y10 Z-99999
G30 P1 X290 Y10 Z-99999
G30 P2 X157 Y280 Z-99999 S3I think you just need to adjust your probe points.
I would suggest you manually jog your print head to place the probe where you want it and then note the current XY position and use that.
@Velvia said in Triple-z G32 true bed level question:
M574 Z1 S2 P"io3.in" ; configure Z-probe endstop for low end on Z
M558 P5 C"io3.in"This is also wrong. You can't use the pin name twice. Luckily for you Z1 S2 doesn't even take a pin name. I would suggest you just remove that M574 Z1 S2 line entirely as it's not needed at all.
-
@Phaedrux Thank you!! I'm now on the right track, just need to fine tune it.
