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

    RepRapFirmware 3.0 is released!

    Scheduled Pinned Locked Moved
    Firmware installation
    33
    131
    11.3k
    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.
    • zerspaner_gerdundefined
      zerspaner_gerd
      last edited by

      Hello everyone
      I just switched to RF3

      I would have the following questions

      • How can I convert M581 S-1 into RF3?

      • Why does my X homing fail?
        Y, Z and homeall work?

      ; homeall.g
G91							; relative positioning
G1 H1 Z215 F1600			        ; move Z up stopping at the endstop
G1 H1 X-235 Y235 F4800		; move quickly to X and Y axis endstops and stop there (first pass)
G1 X5 Y-5 F6000				; go back a few mm
G1 H1 X-7.5 Y7.5 F1300		; move slowly to X and Y axis endstops once more (second pass)		
G1 Z-5.0 F1400
G1 H1 Z7.5 F800				; move Z up until the switch triggers
G90							; absolute positioning

; homex.g
G91					; relative positioning
G1 H1 X-232 F4800	; move quickly to X axis endstop and stop there (first pass)
G1 X5 F6000			; go back a few mm
G1 H1 X-7.5 F1300	; move slowly to X axis endstop once more (second pass)
G90					; absolute positioning

; homey.g
G91              ; relative positioning
G1 H1 Y235 F4800 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y-5 F6000     ; go back a few mm
G1 H1 Y7.5 F1300  ; move slowly to Y axis endstop once more (second pass)
G90              ; absolute positioning

; homez.g
G91						; relative positioning
G1 H1 Z215 F1600		; move Z up until the switch triggers
G1 Z-5.0 F1400
G1 H1 Z7.5 F800			; move Z up until the switch triggers
G90						; absolute positioning

; Endstops
M574 X1 S1 P"!xstop"					; configure active-low endstop for low end on X via pin xstop
M574 Y2 S1 P"!ystop"					; configure active-low endstop for high end on Y via pin ystop
M574 Z2 S1 P"!zstop"					; configure active-low endstop for high end on Z via pin zstop

      If I write H2 in this sentence G1 X5 F6000 ; go back a few mm it works, but with Y, Z and homeall it is not necessary either?

      I'm totally keen on the meta commands, but first one by one

      greetings

      Board: Duet WiFi 1.03 | Firmware Version: 3.1.1 | WiFi Server Version: 1.23 | Web Interface Version: 3.1.1

      littlehobbyshopundefined 1 Reply Last reply Reply Quote 0
      • littlehobbyshopundefined
        littlehobbyshop @zerspaner_gerd
        last edited by

        @zerspaner_gerd You need that H2 in there as you described for the move back a few mm. My config has these and was generated by the config tool.

        BLV MGN Cube w/Hemera, K8200, Sunlu S8

        deckingmanundefined 1 Reply Last reply Reply Quote 0
        • deckingmanundefined
          deckingman @littlehobbyshop
          last edited by deckingman

          @littlehobbyshop said in RepRapFirmware 3.0 is released!:

          @zerspaner_gerd You need that H2 in there as you described for the move back a few mm. My config has these and was generated by the config tool.

          He shouldn't need to add that H2. If the first G1 H1 X- move works, then the axis will be flagged as being homed. So after that, he should be able to do any G1 moves without any H parameter.
          I suggest the OP steps through his homex one command at a time to check that the axis gets flagged as being homed after that first move. One thing that might be a clue is that in homeall, the move is X-235 but in home X it's - 232 (I think - but I'm typing this on my phone and can't scroll up).

          Ian
          https://somei3deas.wordpress.com/
          https://www.youtube.com/@deckingman

          zerspaner_gerdundefined 1 Reply Last reply Reply Quote 1
          • zerspaner_gerdundefined
            zerspaner_gerd @deckingman
            last edited by

            @deckingman said in RepRapFirmware 3.0 is released!:

            @littlehobbyshop said in RepRapFirmware 3.0 is released!:

            @zerspaner_gerd You need that H2 in there as you described for the move back a few mm. My config has these and was generated by the config tool.

            He shouldn't need to add that H2. If the first G1 H1 X- move works, then the axis will be flagged as being homed. So after that, he should be able to do any G1 moves without any H parameter.

            I agree with you. Why should it be necessary for X and not for Y, Z and homeall?

            I suggest the OP steps through his homex one command at a time to check that the axis gets flagged as being homed after that first move.

            The warning message disappears for the first time, so I assume that it is considered referenced.

            One thing that might be a clue is that in homeall, the move is X-235 but in home X it's - 232 (I think - but I'm typing this on my phone and can't scroll up).

            Well seen, I compared again and again and saw no differences.
            But nothing has changed.

            Since my english is not good here is a video of how the X axis behaves
            https://www.dropbox.com/s/b9ms5dav5o08n24/2020-01-27 16-06-58.ts?dl=0

            What I have found out is that this is completed without errors:

            G91					; relative positioning
G1 H1 X-235.0 F4800	; move quickly to X axis endstop and stop there (first pass)
G1 X10.0 F6000		; go back a few mm
G1 H1 X-7.5 F1300	; move slowly to X axis endstop once more (second pass)
G90					; absolute positioning

            Only the result is wrong.
            It seems to me that it ignores the second H1.
            Why?

            Board: Duet WiFi 1.03 | Firmware Version: 3.1.1 | WiFi Server Version: 1.23 | Web Interface Version: 3.1.1

            1 Reply Last reply Reply Quote 0
            • zerspaner_gerdundefined
              zerspaner_gerd
              last edited by

              This is also completed without errors:

              ; homex.g

G91					; relative positioning
G1 H1 X-235.0 F4800	; move quickly to X axis endstop and stop there (first pass)
G1 X5.0 F6000		; go back a few mm
G1 H2
G1 H1 X-7.5 F1300	; move slowly to X axis endstop once more (second pass)
G90					; absolute positioning

              One question should this not fail or complete successfully:

              ; homey.g

G91					; relative positioning
G1 H1 Y235 F4800	; move quickly to Y axis endstop and stop there (first pass)
G1 Y-50.0 F6000		; go back a few mm
G1 H1 Y7.5 F1300	; move slowly to Y axis endstop once more (second pass)
G90					; absolute positioning

              With RF2.05 I had no problems.
              And why only homex.g
              Can't be because of my config, right?
              Maybe in connection with low end and high endstop configuration

              ; Endstops
M574 X1 S1 P"!xstop"
M574 Y2 S1 P"!ystop"
M574 Z2 S1 P"!zstop"

              greetings

              Board: Duet WiFi 1.03 | Firmware Version: 3.1.1 | WiFi Server Version: 1.23 | Web Interface Version: 3.1.1

              stewwyundefined 1 Reply Last reply Reply Quote 0
              • stewwyundefined
                stewwy @zerspaner_gerd
                last edited by

                @zerspaner_gerd This is my homex.g

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

                hope this helps , works perfectly on 3.0,

                zerspaner_gerdundefined 1 Reply Last reply Reply Quote 0
                • matej1006undefined
                  matej1006 @dc42
                  last edited by

                  @dc42 Hello me again

                  i just got my noctua fan which as we talk i want to control by water temp.
                  so my code is now looking like that:

                  ;Water temp
M308 S5 P"e0temp" Y"thermistor" T100000 B4138 A"Water temp."                  ;configure sensor 5 as thermistor on pin e1temp

; Mesh  grid
M557 X20:420 Y104:384 40            
                                                          
; Fans
M950 F0 C"!Fan0+exp.pb6" Q25000 				; fan 0 is a 4-wire PWM fan so invert it, use high PWM frequency, tacho connected to PB6 on expansion connector
M106 P0 H5 T80

                  i with that code fan no matther water temp work with same speed.
                  i have Noctua 12V 1700 PWM fan that is connected yellow and black wire to 12v DC and blue wire to fan0- as i read.

                  and i want that this fan work's on Thermostatic mode what i am doing wrong please help?

                  Matej

                  dc42undefined 1 Reply Last reply Reply Quote 0
                  • zerspaner_gerdundefined
                    zerspaner_gerd @stewwy
                    last edited by

                    @stewwy Thanks

                    I now run it with H2, but it is very strange that this is only necessary at homex.
                    homeall, homez and homey no H2 is necessary.
                    With RF2, H2 was nowhere necessary.

                    Best regards

                    Board: Duet WiFi 1.03 | Firmware Version: 3.1.1 | WiFi Server Version: 1.23 | Web Interface Version: 3.1.1

                    1 Reply Last reply Reply Quote 0
                    • dc42undefined
                      dc42 administrators @matej1006
                      last edited by

                      @matej1006 said in RepRapFirmware 3.0 is released!:

                      @dc42 Hello me again

                      i just got my noctua fan which as we talk i want to control by water temp.
                      so my code is now looking like that:

                      ;Water temp
M308 S5 P"e0temp" Y"thermistor" T100000 B4138 A"Water temp."                  ;configure sensor 5 as thermistor on pin e1temp

; Mesh  grid
M557 X20:420 Y104:384 40            
                                                          
; Fans
M950 F0 C"!Fan0+exp.pb6" Q25000 				; fan 0 is a 4-wire PWM fan so invert it, use high PWM frequency, tacho connected to PB6 on expansion connector
M106 P0 H5 T80

                      i with that code fan no matther water temp work with same speed.
                      i have Noctua 12V 1700 PWM fan that is connected yellow and black wire to 12v DC and blue wire to fan0- as i read.

                      and i want that this fan work's on Thermostatic mode what i am doing wrong please help?

                      Matej

                      I don't see anything wrong with that configuration. What reading is sensor 5 giving in DWC?

                      Duet WiFi hardware designer and firmware engineer
                      Please do not ask me for Duet support via PM or email, use the forum
                      http://www.escher3d.com, https://miscsolutions.wordpress.com

                      matej1006undefined 1 Reply Last reply Reply Quote 0
                      • matej1006undefined
                        matej1006 @dc42
                        last edited by

                        @dc42 i figurit out i didn't connec 24V and 12V GND together 😉 Thanks anyway

                        Can i use this same sensor to contorl water pump with that code?

                        ;Water temp
M308 S5 P"e0temp" Y"thermistor" T100000 B4138 A"Water temp."                  ;configure sensor 5 as thermistor on pin e1temp

; Mesh  grid
M557 X20:420 Y104:384 40            
                                                          
; Fans
M950 F0 C"!Fan0+exp.pb6" Q25000 				; fan 0 is a 4-wire PWM fan so invert it, use high PWM frequency, tacho connected to PB6 on expansion connector
M106 P0 H5 T30   

;Water pump
M950 F0 C"!Fan1" Q25000 				             
M106 P1 H5 T30
                        1 Reply Last reply Reply Quote 0
                        • dc42undefined
                          dc42 administrators
                          last edited by

                          Yes, that should work.

                          Duet WiFi hardware designer and firmware engineer
                          Please do not ask me for Duet support via PM or email, use the forum
                          http://www.escher3d.com, https://miscsolutions.wordpress.com

                          1 Reply Last reply Reply Quote 0
                          • MrSteve920undefined
                            MrSteve920 @dc42
                            last edited by

                            @dc42 Did you ever get around to testing what the new maximum step rate in RRF3 is? I saw there was a change in one of the recent betas to get some of the max step rate back; do you think it's going to be possible to increase the max step even more in the future?

                            1 Reply Last reply Reply Quote 0
                            • dc42undefined
                              dc42 administrators
                              last edited by

                              Yes I did. On a Duet WiFi it was disappointingly low, around 45kHz to each of 3 motors moving simultaneously AFAIR. The changes I made helped somewhat, but more improvement is planned for release 3.02.

                              Duet WiFi hardware designer and firmware engineer
                              Please do not ask me for Duet support via PM or email, use the forum
                              http://www.escher3d.com, https://miscsolutions.wordpress.com

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