Duet3 mini voron gantry level problem
-
@jay_s_uk
As I said, I'm completely new to RRF. I need a bit more until I understand everything. -
@jay_s_uk Gantry leveling is ok, Homing all axis is ok
-
@jamaicarasta it might be the format displayed and also possibly irrelevant but do you have the bed.g info inside the config.g file?
@jay_s_uk thanks for the link I`ve not got my head around conditional gcode yet but I'll just give it ago
-
@jumpedwithbothfeet How should that look then? I dont know...
-
@jumpedwithbothfeet
; 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 Fri Feb 11 2022 17:57:25 GMT+0100 (Mitteleuropäische Normalzeit); General preferences -------------------------------------------------------
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Duet Voron" ; set printer name
M669 K1 ; select CoreXY mode; Network --------------------------------------------------------------------
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives ---------------------------------------------------------------------
; ----+---- Z-Drives
; | 2 | 3 |
; ----+----
; | 1 | 4 |
; ----+----
; FrontM584 X5 Y6 Z1:2:3:4 E0 ; motor bindings
M671 X-55:-55:405:405 Y-25:390:390:-25 S2 ; belt positionM569 P0 S1 ; extruder motor direction
M569 P1 S1 ; Z1 motor direction
M569 P2 S0 ; Z2 motor direction
M569 P3 S1 ; Z3 motor direction
M569 P4 S0 ; Z4 motor direction
M569 P5 S1 ; X motor direction
M569 P6 S1 ; Y motor directionM350 X16 Y16 Z16 E16 I1 ; set microstepping
M92 X80 Y80 Z400 E426 ; set microsteps per mm
M566 X16000.00 Y16000.00 Z18000.00 E1200.00 ; set maximum instantaneous speed changes (mm/min)
M203 X24000.00 Y24000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min)
M201 X6000.00 Y6000.00 Z3000.00 E1500.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E300 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; thermal section ------------------------------------------------------------
M308 S3 Y"mcu-temp" A"Board" ; Board thermal sensor
M912 P0 S-2 ; MCU tempurature sensor correction (subtract 2°K); Axis Limits ----------------------------------------------------------------
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X350 Y350 Z340 S0 ; set axis maxima; Endstops -------------------------------------------------------------------
M574 X2 S1 P"io3.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io3.in
M574 Y2 S1 P"io4.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io4.in
M574 Z1 S2 "io1.in" ; configure switch-type (e.g. Probe) endstop for low end on Z via pin io1.in; Z-Probe --------------------------------------------------------------------
M558 K0 P8 A2 S0.05 C"^io1.in" H2 F300 T16000 ; set Z probe type to modulated and the dive height + speeds
G31 P500 X0 Y20 Z1.590 ; set Z probe trigger value, offset and trigger height
M557 X15:335 Y35:315 S10 ; define mesh grid; Heaters --------------------------------------------------------------------
M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; 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 B4138 ; 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 F0 C"out3" Q500 ; create fan 0 on pin out3 and set its frequency
M106 P0 S1 H1 T60 ; set fan 0 value. Thermostatic control is turned on
M950 F1 C"out4" Q500 ; create fan 1 on pin out4 and set its frequency
M106 P1 S0 H-1 ; set fan 1 value. Thermostatic control is turned off
M950 F2 C"out5" Q500 ; create fan 2 on pin out5 and set its frequency
M106 P2 S1 H-1 ; set fan 2 value. Thermostatic control is turned off
M950 F3 C"out6" Q500 ; create fan 3 on pin out6 and set its frequency
M106 P3 S0 H-1 ; set fan 3 value. Thermostatic control is turned off; 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 --------------------------------------------
M501 -
@jay_s_uk said in Duet3 mini voron gantry level problem:
stack overflow
What means stack overflow? So that I have a clue where the error could be.
-
@jamaicarasta if that`s your config.g it was just the way it was displayed as for the stack overflow issue...that is something beyond me at the moment, I think it has something to do how much information/data is held maybe @Phaedrux may have a clue?
-
@jumpedwithbothfeet
I don't have a temperature sensor on the extruder at the moment and it shows -270 degrees. can that be the problem? -
@jamaicarasta only if you want to print something! you could always ensure the heater is disconnected to be as safe as possible
-
@jamaicarasta said in Duet3 mini voron gantry level problem:
; mesh.g
; called to perform automatic bedmesh via G29
M561 ; clear any bed...
G29 ; bed mesh
G1 X175 Y175 Z50 F20000 ; go to bed middleThe overflow is likely because you have G29 inside of mesh.g. G29 calls mesh.g. Inside of mesh.g you must use G29 S0 to initiate the probing routine.
-
@jumpedwithbothfeet
I'm still waiting for my new mosquito Magnum with heating cartridge and temperature sensor. There is no extruder in it -
@phaedrux
Thanks man
I will Try it tomorrow morning.
I'll let you know tomorrow if it worked
Thanks in advance -
@phaedrux
Hey the Printer Starts the bed mesh But now he write "No valid grid defined for bed probing"… -
@phaedrux
ok was my mistake. too many measuring points. now it works -
@jamaicarasta thats mostly because your probe have an Offset..and as i had to learn...if you define your probe area it takes the coordinates from the probe and not from the nozzle...so if you define x10 y10 and probing start and your probe have an offset of x0 y25 ( Voron) then if it want to probe the point the nozzle would be at x10 y-15 so its off the valid area. so meshare start have to be at least at x0 y25 to work
have to learn so much from my change from a duet Delta to the duet Voron -
@barracuda72
yes exactly I puzzled for 2 days why my Y and X did not correspond to what I tell him. Then I set the offset X0/Y20 and now it fits. I already had the Voron but with a clipper.... It's a little different. But I love the duet -
@jamaicarasta you can't just set random offsets in G31 to make it fit. it has to be the physical measurements from the nozzle
-
Measure your offsets: https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_testing
Alter your grid size to take into consideration the physical offsets. Skipping points it can't reach isn't necessarily a problem, but it does mean you could have a more efficient usage of points. Though if you're not using the maximum 441 points, does it really matter?