Navigation

    Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Triggers within homing files

    General Discussion
    2
    12
    113
    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.
    • Ntrack
      Ntrack last edited by Ntrack

      I am trying to write a homing file which will home the axis if an endstop is not triggered. It homes the axis but it also gives an error in the console : G28 U Error: Homing failed . The relevant files are:
      HomeU.g

      M574 V2 S1 p"zstop"			; configure mmu2 filament feeder endstops at max end active-high
      M574 A2 S1 P"!e0stop"	                ; configure false extruder axis endstop at max end active-low
      
      M581 P"!zstop" T8 C0
      M582 T8
      M581 P"nil" T8 C0	
      
      M581 P"zstop" T11 C0			        ; activate trigger 11 on rising edge 
      M582 T11			 	        ; check filament sensor to confirm selector is unloaded
      M581 P"nil" T11 C0		 		; deactivate trigger 11
      
      ;M581 P"!e0stop" T12 C0		                ; activate trigger 6 on rising edge 
      ;M582 T12			 	 	; check filament sensor to confirm extruder is unloaded
      ;M581 P"nil" T12 C0		 		; deactivate trigger 6
      

      Trigger8.g

      M913 U50              		 ; reduce motor current to 50% to prevent bad noises
      M915 U S5 F0			; set stall parameters
      G91                   		 ; use relative positioning
      G1 H1 U5 F2000            	  ; move out 5mm
      G1 H1 U-100 F1000       	     ; move carriage to home
      G90                 		   ; back to absolute positioning
      M400               		     ; make sure everything has stopped before we reset the motor currents
      M913 U100       		    ; motor currents back to normal
      

      Trigger11.g

      M584 P3
      M291 P"Stuff happens. homing axis not allowed" S2
      

      I am running RepRapFirmware for Duet 2 WiFi/Ethernet 3.01-beta1+1 (2020-01-15b2) so it may be a bug but also it might be something wrong in these files.

      1 Reply Last reply Reply Quote 0
      • Danal
        Danal last edited by

        What are the mechanics, and what is the Goal?

        1 Reply Last reply Reply Quote 0
        • Ntrack
          Ntrack last edited by Ntrack

          I'm running prusa's mmu2 on a cartesian printer with the duet. The goal is to disallow the homing of the selector axis if filament is fed through the selector.

          First M581 command will home the axis if the filament is not detected, the second M581 will hide the mmu axes and send the message.

          1 Reply Last reply Reply Quote 0
          • Danal
            Danal last edited by

            Got it. Thank you.

            Have you seen the new RRF3 conditional gcode? I believe it would be perfect for this.

            https://duet3d.dozuki.com/Wiki/GCode_Meta_Commands

            1 Reply Last reply Reply Quote 0
            • Ntrack
              Ntrack last edited by

              Yes, that's the ultimate goal but it will be a steep learning curve for me. Last time I checked I couldn't find anything related to endstops states.

              1 Reply Last reply Reply Quote 0
              • Danal
                Danal last edited by

                Fair point, it is very early in the release of conditionals.

                The endstops will (should?) be in the object model. I don't have a machine accessible right now, but I believe they are down the "machine" > "sensors" part of the tree.

                1 Reply Last reply Reply Quote 0
                • Ntrack
                  Ntrack last edited by

                  I can't see any machine part of the tree. I might be doing it wrong, I'm just running M409 in DWC and paste the return here .

                  1 Reply Last reply Reply Quote 0
                  • Danal
                    Danal last edited by

                    M409 F"V" will get a much larger result.

                    1 Reply Last reply Reply Quote 0
                    • Ntrack
                      Ntrack last edited by

                      No luck either, M409 F"v" returns:

                      {"key":"","flags":"V","result":{"boards":[{"firmwareFileName":"Duet2CombinedFirmware.bin","firmwareVersion":"3.01-beta1+1","iapFileNameSD":"Duet2CombinedIAP.bin","mcuTemp":{"current":43.0,"max":43.4,"min":42.2},"name":"Duet 2 WiFi","shortName":"2WiFi","vIn":{"current":24.2,"max":24.3,"min":24.1}}],"heat":{"coldExtrudeTemperature":160.0,"coldRetractTemperature":90.0,"heaters":[{"current":25.0,"sensor":0,"state":"Off"},{"current":25.0,"sensor":1,"state":"Off"}],"sensors":[{"lastReading":25.0,"name":"","type":"Thermistor"},{"lastReading":25.0,"name":"","type":"Thermistor"}]},"job":{"file":{"filament":[],"firstLayerHeight":0.0,"generatedBy":"","height":0.0,"lastModified":"28115-10-29T03:41:51","layerHeight":0.0,"numLayers":0,"printTime":0,"simulatedTime":0,"size":0},"lastFileName":"","layer":0,"timesLeft":{"filament":0.0,"file":0.0,"layer":0.0}},"move":{"axes":[{"homed":false,"letter":"X","max":247.0,"min":0.0,"userPosition":0.000,"visible":true},{"homed":false,"letter":"Y","max":210.0,"min":0.0,"userPosition":0.000,"visible":true},{"homed":false,"letter":"Z","max":200.9,"min":0.0,"userPosition":0.002,"visible":true},{"homed":false,"letter":"U","max":75.0,"min":0.0,"userPosition":0.000,"visible":true},{"homed":false,"letter":"V","max":1000.0,"min":-1000.0,"userPosition":0.000,"visible":true},{"homed":false,"letter":"W","max":78.0,"min":0.0,"userPosition":0.000,"visible":true},{"homed":false,"letter":"A","max":1000.0,"min":-1000.0,"userPosition":0.000,"visible":true}],"calibrationDeviation":{"deviation":0.000,"mean":0.000},"currentMove":{"requestedSpeed":0.0,"topSpeed":0.0},"daa":{"enabled":false,"minimumAcceleration":10.0,"period":0.0},"idle":{"factor":0.3,"timeout":50000},"initialDeviation":{"deviation":0.000,"mean":0.000},"meshDeviation":{"deviation":0.000,"mean":0.000},"printingAcceleration":600.0,"speedFactor":100.0,"travelAcceleration":3000.0},"network":{"interfaces":[{"actualIP":"192.168.0.12","firmwareVersion":null,"gateway":"0.0.0.0","subnet":"0.255.255.255","type":"wifi"}]},"state":{"currentTool":-1,"machineMode":"FFF","status":"Idle","upTime":42}}}
                      
                      1 Reply Last reply Reply Quote 0
                      • Danal
                        Danal last edited by

                        Hmmm.... I'm near a machine now, and I don't see any signs of endstops in the object module either.

                        Let me keep looking.

                        1 Reply Last reply Reply Quote 0
                        • Ntrack
                          Ntrack last edited by

                          I found them running the latest beta.

                          1 Reply Last reply Reply Quote 1
                          • Ntrack
                            Ntrack last edited by Ntrack

                            I am almost there with the homing file using conditional code.

                            if sensors.endstops[4].triggered && state.status.idle
                            	M291 P"MMU loaded. Selector homing not allowed.Please unload MMU manually." S2
                            
                            if sensors.endstops[4].triggered && state.status.printing
                            	M25
                            	M291 P"MMU loaded. Selector homing not allowed.Please unload MMU manually." S2	
                            
                            else
                            	M913 U50              		 ; reduce motor current to 50% to prevent bad noises
                            	M915 U S5 F0			; set stall parameters
                            	G91                   		 ; use relative positioning
                            	G1 H1 U5 F2000            	  ; move out 5mm
                            	G1 H1 U-100 F1000       	     ; move carriage to home
                            	G90                 		   ; back to absolute positioning
                            	M400               		     ; make sure everything has stopped before we reset the motor currents
                            	M913 U100       		    ; motor currents back to normal
                            

                            But , obviously is not working because state.status.idle is not the correct way of expressing the value of state.status.

                            Here is the state tree. Surely this is trivial for anyone who is used to any type of coding, not for me unfortunately.

                            Edit: state.status == "Idle" .

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