After homing printer returns to power on position and sets home there
-
I've just started setting up my new Duet WiFi in my delta printer and it is fantastic. Well above and beyond any control board I've used (I had a smoothieboard in it but just had way too many problems)
The one thing I'm confused about is the homing. When I Home All it moves up to the end stops as it should, double taps them correctly, but then it moves back to where ever it was before power on (or to where it was moved manually with the motors off) and set that position as X0 Y0 Z<homed height="" value="">. Even if that position is nowhere close to the center or the configured home height value. Even if the carriages are different distances from the endstop switches.
After this I can't move up from that position, as it thinks it's at the highest allowable point, even if it's near the bottom of the range close to the bed (if that's where it was when it powered on). And since it's always set to X0 Y0 Z <homed height="" value="">even if the print head is 10mm off the build plate, it will happily crash into the build plate when it moves down (like when trying to auto calibrate).
I started out with 1.19.2 stable release and have moved to Firmware Version: 1.20beta8+1 (2017-11-18) WiFi Server Version: 1.20b9 with the same results.
I generated my config files with the Configuration Tool and they are pretty standard. I did get the auto calibration to run by powering on the printer with the head all the way up, and added those values to my config
[c]M665 R105.11 L225.51 B100 H348.693 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X3.28 Y-2.85 Z-0.43 ; Put your endstop adjustments here, or let auto calibration find them
M208 Z0 S1 ; Set minimum Z[/c]My homedelta.g file is just the default
[c]; homedelta.g
; called to home all towers on a delta printer
;
; generated by RepRapFirmware Configuration Tool on Tue Nov 21 2017 15:00:31 GMT-0800 (Pacific Standard Time); Use relative positioning
G91; Move all towers to the high end stopping at the endstops (first pass)
G1 X400 Y400 Z400 F3500 S1; Go down a few mm
G1 X-5 Y-5 Z-5 F1800 S2; Move all towers up once more (second pass)
G1 X10 Y10 Z10 F360 S1; Move down a few mm so that the nozzle can be centred
G1 Z-5 F6000; Switch back to absolute positioning and go to the centre
G90
G1 X0 Y0 F6000
[/c]If I run the homedelta.g commands manually everything works fine until the G1 Z-5 F6000 call, then instead of moving relative down 5mm it moves straight down to what looks like the power on position minus 5mm. Then the G1 X0 Y0 F6000 call moves it up 5mm and over to the exact position the head was in at power on.
What am I doing wrong?
Thanks for your help.</homed></homed>
-
Please post your complete config.g file. Also post config-override.g if there is one.
-
[c]; Configuration file for Duet WiFi (firmware version 1.17 to 1.19)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Tue Nov 21 2017 15:00:31 GMT-0800 (Pacific Standard Time); General preferences
M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates…
M83 ; ...but relative extruder moves
M555 P1 ; Set firmware compatibility to look like RepRapFirmare
;M555 P2 ; Set firmware compatibility to look like MarlinM911 S19.5 R22 P"G91 M83 G1 Z3 E-5 F1000" ; Setup auto pause on power fail
;*** The homed height is deliberately set too high in the following - you will adjust it during calibration.
M665 R105.11 L225.51 B100 H348.693 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X3.28 Y-2.85 Z-0.43 ; Put your endstop adjustments here, or let auto calibration find them
M208 Z0 S1 ; Set minimum Z; Endstops
M574 X1 Y1 Z1 S1 ; Set active high endstops
M558 P4 X0 Y0 Z0 H5 F120 T6000 ; Set Z probe type to switch, the axes for which it is used and the dive height + speeds
G31 P600 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height
M557 R100 S20 ; Define mesh grid; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80 Y80 Z80 E408 ; Set steps per mm
M566 X1200 Y1200 Z1200 E1200 ; Set maximum instantaneous speed changes (mm/min)
M203 X30000 Y30000 Z30000 E1200 ; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z1000 E1000 ; Set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I45 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Heaters
M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
M305 P0 T100000 B4725 C7.060000e-8 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4725 C7.060000e-8 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S310 ; Set temperature limit for heater 1 to 310C; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X9 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C; Network
M550 PATOM2 ; Set machine name
M552 S1 ; Enable network
M587 S"xxx" P"xxx" ; Configure access point. You can delete this line once connected
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet; Fans
M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T60 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S0 I0 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off; Custom settings are not configured
[/c] -
There is no override file
-
The endstop switches on a delta are at the high end, so your M574 command should be:
M574 X2 Y2 Z2 S1
HTH David
-
Fantastic, that did it
Thank youI guess it hit the end stops on the "bottom" when it was going up, sensed the error and aborted setting the home position? Something like that. Makes sense now.
-
Yes, something like that. As you are running the 1.20 beta firmware, there may have been a "Homing failed" message on the GCode Console page of the web interface.
-
I don't see any error message listed. I changed it back and tested the Home All button as well as sending G28 manually from the G-Code Console page. It only logs the G28 call. Also, the notification message about the axis's not being homed disappears despite the homing having failed.
