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

    Will not reliably home on Y - Broken cable?

    Scheduled Pinned Locked Moved
    My Duet controlled machine
    4
    12
    390
    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.
    • PaulHewundefined
      PaulHew
      last edited by

      Apologies, it does home but is picky when it is doing so, hence my thought about broken cable.
      As requested.

      ; Config file for RailCore II 300 ZL Paul Hewson
      ; Last Change LEDs 03/05/2020
      M111 S0                             	; Debug off
      
      ;Network
      M550 P"RailCore II"                       ; Set machine name
      M552 P192.168.0.7 S1                     ; Enable network and set IP address
      M553 P255.255.255.0                      ; Set netmask
      M554 P192.168.0.1                        ; Set gateway
      M586 P0 S1                               ; Enable HTTP
      M586 P1 S0                               ; Disable FTP
      M586 P2 S1                               ; Enable Telnet
      
      M575 P1 B57600 S1					; Comms parameters for PanelDue
      
      G21                                 	; Work in millimetres
      G90                                		; Send absolute coordinates...
      M83                                 	; ...but relative extruder moves
      
      ; Axis and motor configuration
      M669 K1								; CoreXY mode
      
      ; Drives
      M569 P0 S1                                     ; Drive 0 goes forwards (change to S0 to reverse it) X stepper (Rear)
      M569 P1 S0                                     ; Drive 1 goes backwards	Y Stepper (Front)
      M569 P2 S1                                     ; Drive 2 goes forwards Unused
      M569 P3 S1                                     ; Drive 3 goes forwards Extruder 
      M569 P4 S1                                     ; Drive 4 goes forwards Extruder (unused)
      M569 P5 S1			  	                       ; Drive 5 goes backwards	Front Left Z
      M569 P6 S1				                       ; Drive 6 goes backwards	Rear Left Z
      M569 P7 S1				                       ; Drive 7 goes backwards	Right Z
      M584 X0 Y1 Z5:6:7 E3			 		       ; Map Z to drivers 5, 6, 7. Define unused drivers 3,4,8 and 9 as extruders
      M84 S30                                        ; Set idle timeout
      
      ;Leadscrew locations
      ;M671 X-10:-10:333 Y22.5:277.5:150 S7.5  ;Front left, Rear Left, Right  S7.5 is the max correction - measure your own offsets, to the bolt for the yoke of each leadscrew
      ;M671 X-34:-34:380 Y22.5:274:155 S7.5
      
      ;New 4-2-21
      M671 X-1:-1:350 Y24:281:151 S7.5
      
      ;_positions:
      #	-10, 22.5	#Left Front = M671 X-34:-34:380 Y22.5:274:155 
      #  -34, 19 #Left Front
      #	34, 274	#Left Rear
      #	380, 155	#Right
      
      
      
      
      ; Axis and motor configuration
      M350 X16 Y16 Z16 E16 I1	                 ; set 16x microstepping for axes& extruder, with interpolation
      
      ;Endstop Configuration
      M574 X1 S1 P"xstop"			             ; _RRF3
      M574 Y1 S1 P"ystop"			             ; _RRF3
      
      ;Speeds
      ;M906 X1400 Y1400 Z1700 E700 I60	         ; Set motor currents (mA)
      M906 X1280 Y1280 Z1220 E700 I50              ; Johns and a bit of mine!
      ;M906 X1280 Y1280 Z1220 E860 I50             ; JOHNs Set motor currents (mA) and motor idle factor in per cent (docs say rounds to 100, but this is where I'd like them to be)
      ;M201 X4000 Y4000 Z100 E1500              ; Accelerations (mm/s^2)
      M201 X1750 Y1750 Z250 E1500              ; Set accelerations (mm/s^2) JohnOFCII
      ;M203 X24000 Y24000 Z900 E3600            ; Maximum speeds (mm/min)
      M203 X24000 Y24000 Z900 E3600                       ; Set maximum speeds (mm/min) JohnOFCII
      ;M566 X1200 Y1200 Z100 E1500              ; Maximum jerk speeds mm/minute
      M566 X600 Y600 Z200 E3600                ; Set maximum instantaneous (jerk) speed changes JohnOFCII
      M92 X200 Y200 
      M92 Z1600 
      M92 E412	             ; steps/mm
      ; 0.4 nozzleE412
      ;E407 TechOut PLA
      ;M204 P2000 T1700
      ;
      
      ;M208 X-10:310 Y-8:293 Z-0:550                 ; set axis minima and low homing switch positions (adjust to make X=0 and Y=0 the edges of the bed)
      M208 X-20:310 Y0:260 Z-0.5:500
      
      
      ; Thermistors
      ;Bed Configuration
      ;M308 S0 P"bedtemp" Y"thermistor" A"Bed-Top" T100000 B3950 R4700 H0 L0 ;A"Bed-Top"
      M308 S0 P"exp.thermistor6" Y"thermistor" A"Keenovo" T100000 B3950 R4700 H0 L0 
      M950 H0 C"bedheat" T0
      M140 H0
      M143 H0 S120
      M307 H0 A481.6 C758.5 D11.3 V24.2 B0
      
      ;HotEnd Configuration
      M308 S1 P"e0temp" Y"thermistor" A"Mosquito" T500000 B4723 C1.19622e-7 ; configure sensor 1 as thermistor on pin e0temp
      ;
      ;M308 S1 P"e0temp" Y"thermistor" A"E3Dv6" T100000 B4725 R4700 C7.06e-8 H0 L0	;Removed 19th June 2020
      ;
      M950 H1 C"e0heat" T1				;
      M143 H1 S280
      M307 H1 A461.0 C201.3 D3.6 V24.2 B0        ;
      
      
      ; Other Tempreture Inputs
      ;M308 S6 P"exp.thermistor6" Y"thermistor" A"Keenovo" T100000 B3950 R4700
      M308 S7 P"exp.thermistor7" Y"thermistor" A"Chamber" T100000 B3950 R4700
      M308 S0 P"bedtemp" Y"thermistor" A"Bed-Top" T100000 B3950 R4700
      
      ; Fans
      M950 F0 C"fan0"						;Part Cooling Fan
      M106 P0 H-1 				
      ;
      M950 F1 C"fan1" Q500                           ;Hotend Fan
      M106 P1 S1 H1 T50
      ;
      M950 F2 C"fan2"						;_RRF3_ define fan2
      M106 P2 H-1
      ;
      M106 P0 S0 				; turn off fans
      	
      ; Tool definitions
      M563 P0 D0 H1                       	; Define tool 0
      G10 P0 S0 R0                        	; Set tool 0 operating and standby temperatures
      
      ; Z probe and compensation definition
      M558 P9 C"^zprobe.in" H5 R1 F120 T6000 A5 S0.02  ;BLTouch connected to Z probe IN pin
      M950 S0 C"duex.pwm1"				             ;BLTouch Servo (S0) on duet pwm1
      G31 X-7 Y35 Z1.324 P25                            ; Customize your offsets appropriately - do a paper test, and put the probed value in the Z value here
      M557 X30:280 Y45:240 S20
      
      
      
      ;Lighting
      M950 F8 C"duex.fan8"
      M106 P8 S0 H-1 C"Front Lights"
      M950 F7 C"duex.fan7"
      M106 P7 S0 H-1 C"Red RGB"
      M950 F6 C"duex.fan6"
      M106 P6 S0 H-1 C"Blue RGB"
      M950 F5 C"duex.fan5"
      M106 P5 S0 H-1 C"Green RGB"
      
      
      T0					; select first hot end
      
      ;Let get some lights in the Build area!
      M98 P"0:/macros/Lights On"
      
      M702				;Unload Filament
      
      
      

      RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
      Voron 2.4 disassembled..... Waiting for the RailCore Mini....

      1 Reply Last reply Reply Quote 0
      • PaulHewundefined
        PaulHew
        last edited by

        I did a full power off, waited 20 secs, powered back on again.

        Re-watching my video, it doubled tapped X endstop but with Y did a 'ghost' tap then looks like it went to home Z, without performing the 2nd home.

        Further thinking, Going to disconnect Y endstop, put a voltmeter on it and see if the cable has a break in it, by gently moving the Gantry as if X had been homed.

        Pity RRF/DWC can not have a diagnose feature that basically you set to 'on' and it logs everytime an endstop is triggered with a time.

        2/3/2021 - 14:40:37 - X endstop triggered
        2/3/2021 - 14:40:40 - X endstop triggered
        2/3/2021 - 14:40:48 - Y endstop triggered
        ......
        

        If I cannot find anything, I will go back to 3.2 and 3.1 firmware if I need to.

        P.

        RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
        Voron 2.4 disassembled..... Waiting for the RailCore Mini....

        fcwiltundefined 1 Reply Last reply Reply Quote 0
        • Phaedruxundefined
          Phaedrux Moderator
          last edited by

          Can we see your homing files?

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • fcwiltundefined
            fcwilt @PaulHew
            last edited by

            @PaulHew I have three printers running 3.2.2 and they all home without any problems.
            So I don't think that is the cause.

            Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

            1 Reply Last reply Reply Quote 0
            • PaulHewundefined
              PaulHew
              last edited by PaulHew

              [0_1614722508972_PaulHew homing files.zip](Uploading 100%) PaulHew homing files.txt

              Rename to a .zip

              Thanks.

              P.

              RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
              Voron 2.4 disassembled..... Waiting for the RailCore Mini....

              1 Reply Last reply Reply Quote 0
              • Phaedruxundefined
                Phaedrux Moderator
                last edited by

                Can you walk me through what I'm actually seeing in the video? It's not obvious to me what is wrong.

                Z-Bot CoreXY Build | Thingiverse Profile

                PaulHewundefined 1 Reply Last reply Reply Quote 0
                • PaulHewundefined
                  PaulHew @Phaedrux
                  last edited by PaulHew

                  @Phaedrux Hope this finds you well.

                  1. the printer is not homed
                  2. I press home all button
                  3. it homes X - endstop in top left corner by linear rail.
                  4. 9 secs into video, It starts to home Y, stops then looks like it is going to home Z but I abort it, horrible noises will happen!
                    if you look at the toolhead, there is a green endstop holder, that is for Y. Just above the Magenta fan duct. (NO IT IS NOT PINK! LOL)

                  It does not even reach its proper homing point.
                  If you look at X, it fast homes, then homes a second time more slowly.
                  Y does not bother. for some reason it think it has homed.

                  Hope that helps.

                  Regards,

                  Paul.

                  RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
                  Voron 2.4 disassembled..... Waiting for the RailCore Mini....

                  1 Reply Last reply Reply Quote 0
                  • Phaedruxundefined
                    Phaedrux Moderator
                    last edited by

                    Does Y appears as homed at that point? or does it think it's still unhommed?

                    What kind of an endstop switch is it?

                    Z-Bot CoreXY Build | Thingiverse Profile

                    1 Reply Last reply Reply Quote 0
                    • PaulHewundefined
                      PaulHew
                      last edited by

                      @Phaedrux It is a Omron microswitch.

                      Update
                      Have not used the printer in a day or so.

                      Upgraded the PanelDue firmware. All good.
                      Homed from the Panel. fine.
                      Heated bed and left for 20 mins.

                      Homed, trammed, homed and trammed twice more.

                      Kicked of a print, test squares. Stopped it.
                      Cleaned bed.
                      homed all, Y homing is messing around again. E-Stop.

                      Home X - ok, home y - did not make it to the endstop, e-stop
                      homed axis manually again - all good.

                      Homed all Missed Y again, estop and it never recovered from that.

                      SD card is blank, but I have recovered most of my files using recovery software I have.

                      Just waiting for new cards - tomorrow.

                      Could the SD card being flaky cause my Homing issues?

                      P.

                      RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
                      Voron 2.4 disassembled..... Waiting for the RailCore Mini....

                      1 Reply Last reply Reply Quote 0
                      • Phaedruxundefined
                        Phaedrux Moderator
                        last edited by

                        @PaulHew said in Will not reliably home on Y - Broken cable?:

                        Could the SD card being flaky cause my Homing issues?

                        I suppose it's possible. Corruption of the homey.g files.

                        Could also just be a consequence of estopping so many times while the sd card was being access (reading the homing files?)

                        Pure speculation on my part.

                        Try a new card and try running a new wire for Y.

                        Z-Bot CoreXY Build | Thingiverse Profile

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