Duet 2 wifi axis homing issue (SOLVED??)



  • Hello all,

    I do apologize ahead of time if I have posted this in the wrong place but I am in need of some help from someone smarter than I in these matters. The problem seems to be when I try to home the x axis. When I try to do a homeall or homex, the endstop stops the motor -or printhead I should say- but I can hear either the driver or motor keep making a noise and the machine does not seem to continue on to run the next gcode command. It hangs after it hits the endstop (or when I manually trigger it) when running G1 S1 X-240 F1800. It does not back off to prepare for the next homing pass (G1 X5 F6000), the next gcode command in the macro. The machine stays busy as I cannot send it any gcode commands manually either. The endstop does show triggered in dwc when I trip it and I have tried a new endstop and that does not change anything. Any ideas on what I can try next in order to diagnose the problem? Thank you in advance!

    Here is my homex.g:

    ; homex.g
    ; called to home the X axis
    ;
    ; generated by RepRapFirmware Configuration Tool v2 on Fri Apr 05 2019 03:54:10 GMT-0500 (Central Daylight Time)
    G91 ; relative positioning
    G1 Z5 F6000 S2 ; lift Z relative to current position
    G1 S1 X-240 F1800 ; move quickly to X axis endstop and stop there (first pass)
    G1 X5 F6000 ; go back a few mm
    G1 S1 X-240 F360 ; move slowly to X axis endstop once more (second pass)
    G1 Z-5 F6000 S2 ; lower Z again
    G90 ; absolute positioning

    If needed, here is my config.g:

    ; Configuration file for Duet WiFi (firmware version 1.21)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool v2 on Fri Apr 05 2019 03:54:10 GMT-0500 (Central Daylight Time)

    ; General preferences
    G90 ; Send absolute coordinates...
    M83 ; ...but relative extruder moves

    ; Network
    M550 P"" ; Set machine name
    M551 P"" ; Set password
    M552 S1 ; Enable network
    M587 S"" P"" ; 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

    ; Drives
    M569 P0 S1 ; Drive 0 goes forwards
    M569 P1 S1 ; Drive 1 goes forwards
    M569 P2 S0 ; Drive 2 goes backwards
    M569 P3 S1 ; Drive 3 goes forwards
    M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
    M92 X80.00 Y80.00 Z400.00 E93.00 ; Set steps per mm
    M566 X900.00 Y900.00 Z12.00 E120.00 ; Set maximum instantaneous speed changes (mm/min)
    M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; Set maximum speeds (mm/min)
    M201 X500.00 Y500.00 Z20.00 E250.00 ; Set accelerations (mm/s^2)
    M906 X800.00 Y800.00 Z800.00 E800.00 I30 ; 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 minima
    M208 X235 Y235 Z250 S0 ; Set axis maxima

    ; Endstops
    M574 X1 Y1 S1 ; Set active high endstops

    ; Z-Probe
    M574 Z1 S2 ; Set endstops controlled by probe
    M558 P5 H5 F120 T6000 I1 ; Set Z probe type to switch and the dive height + speeds
    ;G31 P1000 X45 Y0 Z.825 ; Set Z probe trigger value, offset and trigger height (buildtak)
    G31 P1000 X45 Y0 Z.798 ; Set Z probe trigger value, offset and trigger height (glass)
    M557 X25:225 Y25:225 S25 ; Define mesh grid
    G29 S1 ; Load default height map file (/sys/heightmap.csv) and activate bed compensation

    ; Heaters
    M307 H0 B0 S1.00 ; Disable bang-bang mode for the bed heater and set PWM limit
    M305 P0 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 0
    M143 H0 S120 ; Set temperature limit for heater 0 to 120C
    M305 P1 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 1
    M143 H1 S280 ; Set temperature limit for heater 1 to 280C

    ; Fans
    M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off (print cooling fan #1)
    M106 P1 S0 I0 F500 H-1 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off (print cooling fan #2)
    M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on (hotend heatsink fan)

    ; Tools
    M563 P0 D0 H1 F0:1 ; 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

    ; Automatic saving after power loss is not enabled

    ; Custom settings are not configured



  • Hi,

    When I am setting up a new machine I verify things step by step.

    As you have observed you can see the state of end stops in DWC.

    Once I know end stops are being seen I then test my various homing macros.

    I position the printhead well away from either end stop and invoke each homing macro in turn.

    But I don't wait for the printhead to trigger the end stop, I trigger it by hand so I can easily confirm the correct homing behavior.

    If for some reason the end stop is not working or configured wrong when I trigger it the first time the printhead will keep right on moving.

    I don't have to worry about the printhead being physically stopped from moving by the end stop and possibly damaging something.

    Frederick



  • Ok.. after knocking my head into a wall over this and getting to the point of pulling my hair out, I eventually put in the right search information to find this post:

    https://forum.duet3d.com/topic/789/something-odd-going-on-sudden-homing-problems-solved-unknown-cause

    My issue was really similar so this got me thinking and remembering that these problems came about when I, too was messing with mesh grid compensation settings. After trying a bunch of stuff to try and force the machine to start a new auto mesh grid compensation, I eventually was able to just disable mesh grid compensation altogether in the dwc. After that, problem seems to be fixed..

    I am relieved but also feel really dumb. I am sorry to have wasted anyone's time but appreciate it greatly nonetheless.

    I am wondering though, to anyone who understands the inner workings of how these things are handled, what exactly do you think happened here? Seems there is some way an unfinished auto mesh grid compensation can gum up the works ..or perhaps it was something to do with trying to save that corrupted heightmap data to file??



  • Hi,

    Glad to hear you got it sorted out.

    What version of firmware are you running?

    Frederick



  • Can you post a picture of your heightmap as well?


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.