Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    X Axis not homeing

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    2
    10
    502
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • fragleundefined
      fragle
      last edited by

      Hello,

      i have an strange problem, because my core xy machine was already running, but now i can not home the x Axis.

      If i home X septeratly, the printhead goes one to+X not in the direction of the endstop ( on the left side )

      If i trigger the endstops manally M119 shows an trigged endstop
      If i move +X +Y everthing is working fine.

      config.g ```
      ; Configuration file for Duet 3 MB 6HC (firmware version 3.3)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.12 on Tue Aug 23 2022 15:15:36 GMT+0200 (Mitteleuropäische Sommerzeit)

      ; General preferences
      G90 ; send absolute coordinates...
      M83 ; ...but relative extruder moves
      M550 P"Duet 3" ; set printer name
      M669 K1 ; select CoreXY mode

      ; Drives
      M569 P0.0 S0 ; physical drive 0.0 goes forwards
      M569 P0.1 S0 ; physical drive 0.1 goes forwards
      M569 P0.2 S1 ; physical drive 0.2 goes forwards
      M569 P0.3 S0 ; physical drive 0.3 goes forwards
      M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping
      M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
      M92 X80.00 Y80.00 Z600.00 E415.00 ; set steps per mm
      M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
      M203 X8000.00 Y8000.00 Z780.00 E1200.00 ; set maximum speeds (mm/min)
      M201 X1500.00 Y1500.00 Z150.00 E1500.00 ; set accelerations (mm/s^2)
      M906 X800 Y800 Z1300 E900 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 X250 Y250 Z380 S0 ; set axis maxima

      ; Endstops
      M574 X1 S1 P"!io0.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io0.in
      M574 Y1 S1 P"!io1.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io1.in
      M574 Z1 S1 P"!io2.in" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin io2.in

      ; Z-Probe
      M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
      M557 X15:215 Y15:195 S20 ; define mesh grid
      ; Filament Sensor
      ;M591 D0 P3 C"io3.in" S1 A1 ; filament monitor connected to E0_stop
      ;M591 D0 ; display filament sensor parameters for extruder drive 0
      ; 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 B1 S1.00 R0.04 ; enable bang-bang mode for the bed heater and set PWM limit
      M307 H0 B0 S1.00 R0.4
      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 S280 ; set temperature limit for heater 1 to 280C
      M307 H1 R3.784 K1.110:0.766 D4.87 E1.35 S1.00 B0 V23.9

      ; Fans
      M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency
      M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
      M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency
      M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on

      ; Tools
      M563 P0 S"Hotend" 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

      homex.g
      

      ; homex.g
      ; called to home the X axis
      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.12 on Tue Aug 23 2022 15:15:36 GMT+0200 (Mitteleuropäische Sommerzeit)
      G91 ; relative positioning
      G1 H1 X-250 F1800 ; move quickly to X axis endstop and stop there (first pass)
      G1 X5 F6000 ; go back a few mm
      G1 H1 X-250 F360 ; move slowly to X axis endstop once more (second pass)

      G90 ; absolute positioning

      
      homey.g
      

      ; homey.g
      ; called to home the Y axis
      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.12 on Tue Aug 23 2022 15:15:36 GMT+0200 (Mitteleuropäische Sommerzeit)
      G91 ; relative positioning

      G1 H1 Y-215 F1800 ; move quickly to Y axis endstop and stop there (first pass)
      G1 Y5 F6000 ; go back a few mm
      G1 H1 Y-215 F360 ; move slowly to Y axis endstop once more (second pass)

      G90 ; absolute positioning

      homeall.g
      

      ; homeall.g
      ; called to home all axes
      ;
      ; generated by RepRapFirmware Configuration Tool v3.3.12 on Tue Aug 23 2022 15:15:36 GMT+0200 (Mitteleuropäische Sommerzeit)
      G91 ; relative positioning

      G1 H1 Z-380 F1800 ; move Z down until the endstop is triggered

      G91 ; relative positioning
      G1 H2 Z5 F6000 ; lift Z relative to current position
      G1 H1 Y-250 F1800 ; move quickly to Y axis endstop and stop there (first pass)
      G1 Y5 F6000 ; go back a few mm
      G1 H1 Y-250 F360 ; move slowly to Y axis endstop once more (second pass)
      G1 H2 Z-5 F6000 ; lower Z again

      G1 H2 Z5 F6000 ; lift Z relative to current position
      G1 H1 X-250 F1800 ; move quickly to X axis endstop and stop there (first pass)
      G1 X5 F6000 ; go back a few mm
      G1 H1 X-250 F360 ; move slowly to X axis endstop once more (second pass)
      G1 H2 Z-5 F6000 ; lower Z again
      G90 ; absolute positioning

      ; Uncomment the following lines to lift Z after probing
      ;G91 ; relative positioning
      ;G1 Z5 F100 ; lift Z relative to current position
      ;G90 ; absolute positioning

      
      best regards
      
      
      Chris
      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @fragle
        last edited by

        @fragle if you have the axis in the middle of the travel and send something like G92 X100, can you then jog the head to the left in the X axis using DWC?

        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

        fragleundefined 1 Reply Last reply Reply Quote 0
        • fragleundefined
          fragle @jay_s_uk
          last edited by

          @jay_s_uk Yes, i can move the print head in the machine movement sector of DWC

          jay_s_ukundefined 1 Reply Last reply Reply Quote 0
          • jay_s_ukundefined
            jay_s_uk @fragle
            last edited by

            @fragle thats a good first step then.
            I'm assuming when you command it to move in -x that it moves left?
            How far does it move to the right when you try and home X? Would you say roughly 5mm or more?

            Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

            fragleundefined 1 Reply Last reply Reply Quote 0
            • fragleundefined
              fragle @jay_s_uk
              last edited by

              @jay_s_uk , i can move to+- without problems at the dwc.
              Indeed if i press home X in the DWC, the printhead moves around 5mm.

              jay_s_ukundefined 1 Reply Last reply Reply Quote 0
              • jay_s_ukundefined
                jay_s_uk @fragle
                last edited by

                @fragle my guess is you're getting interference on your endstop wiring so the firmware thinks its homed. what type of endstop is it?

                Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                fragleundefined 1 Reply Last reply Reply Quote 0
                • fragleundefined
                  fragle @jay_s_uk
                  last edited by

                  @jay_s_uk mechanical omron endstops, if check M119, all endstop states are in the right condition

                  jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                  • jay_s_ukundefined
                    jay_s_uk @fragle
                    last edited by

                    @fragle i would change the wiring on the switch from NO (normally open) to NC (normally closed).
                    Although they may show as working fine using M119, that wouldn't stop interference.
                    If you can't change the wiring of the switch (which I would highly recommend (and if you do, remove the ! from the pin name)) then look at separating the endstop wiring away from everything else, especially stepper motor wiring.

                    Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                    fragleundefined 1 Reply Last reply Reply Quote 0
                    • fragleundefined
                      fragle @jay_s_uk
                      last edited by

                      @jay_s_uk i seperated the endstop wires a little bit from the stepper wires and now the endstop is back in normal service.

                      Thanks for the good idea, but i am wondering, where the problems came from.

                      now it is working and printing normally. Thank you very much for your help.

                      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                      • jay_s_ukundefined
                        jay_s_uk @fragle
                        last edited by

                        @fragle it comes from interference.
                        Normally open switches, in the untriggered state, don't provide a signal so any electromagnetic interference could induce a signal and give the appearance that the switch has been triggered.
                        Normally closed switches always send a signal unless triggered, so they are immune to electromagnetic interference, hence why they are recommended.

                        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA