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

    Duet3 mini voron gantry level problem

    Scheduled Pinned Locked Moved
    General Discussion
    voron2.4 gantry level problem
    6
    46
    1.8k
    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.
    • jumpedwithbothfeetundefined
      jumpedwithbothfeet @jamaicarasta
      last edited by

      @jamaicarasta in all but one probe point you have 2 X axis coordinates, change it too -

      bed.g
      4 M561
      5 G28
      6 G30 P1 X15 Y5 z-99999
      7 G30 P2 X15 Y315 z-99999
      8 G30 P3 X300 Y315 z-99999
      9 G30 P4 X300 Y5 z-99999 S4

      6HC Voron Trident based, 6XD CNC, Mini 5 polar printer

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

        @jamaicarasta your probe points to start at 0
        So P0, P1, P2 and P3, not P1, P2, P3 and P4

        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

        jamaicarastaundefined 3 Replies Last reply Reply Quote 0
        • jamaicarastaundefined
          jamaicarasta @jay_s_uk
          last edited by

          @jay_s_uk
          ok thanks i thought i have to start at p1 because my 4z motors are plugged into 1,2,3,4.
          I will Try it in a few Hours when I'm back at the printer.
          I'll let you know 👍🤝
          It's amazing how quickly you get an answer here.

          1 Reply Last reply Reply Quote 0
          • jamaicarastaundefined
            jamaicarasta @jumpedwithbothfeet
            last edited by

            @jumpedwithbothfeet
            where do i have 2 times x? don't quite understand. I gave correct points 4 times in my opinion.
            Thanks

            jumpedwithbothfeetundefined 1 Reply Last reply Reply Quote 0
            • jamaicarastaundefined
              jamaicarasta @jay_s_uk
              last edited by

              @jay_s_uk
              and one more question if i may. it does not go to my specified coordinates exactly. X15 stays at X40 on rehearsal. but if I drive normally with g1 then it drives exactly to x15. only at g32 is it off by 25.

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

                @jamaicarasta it applies the G31 offsets to that, so if your probe is -25 in X, the nozzle has to be at 40 for the probe to be at 15

                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

                jamaicarastaundefined 1 Reply Last reply Reply Quote 0
                • jamaicarastaundefined
                  jamaicarasta @jay_s_uk
                  last edited by

                  @jay_s_uk
                  ok i will check that i took a config from the internet from the beginning and maybe the value there is wrong for my probe

                  1 Reply Last reply Reply Quote 1
                  • jamaicarastaundefined
                    jamaicarasta @jay_s_uk
                    last edited by

                    @jay_s_uk
                    So the error is gone, now I have the next error. is that something in the config file?
                    G32
                    Error: This kinematics does not support auto-calibration
                    Config:

                    General preferences -------------------------------------------------------
                    M575 P1 S1 B57600 ; enable support for PanelDue
                    G90 ; send absolute coordinates...
                    M83 ; ...but relative extruder moves
                    M550 P"Duet Voron" ; set printer name
                    M669 K1 ; select CoreXY mode

                    ; Network --------------------------------------------------------------------
                    M552 S1 ; enable network
                    M586 P0 S1 ; enable HTTP
                    M586 P1 S0 ; disable FTP
                    M586 P2 S0 ; disable Telnet

                    ; Drives ---------------------------------------------------------------------
                    ; ----+---- Z-Drives
                    ; | 2 | 3 |
                    ; ----+----
                    ; | 1 | 4 |
                    ; ----+----
                    ; Front

                    M584 X5 Y6 Z1:2:3:4 E0 ; motor bindings

                    M569 P0 S1 ; extruder motor direction
                    M569 P1 S1 ; Z1 motor direction
                    M569 P2 S0 ; Z2 motor direction
                    M569 P3 S1 ; Z3 motor direction
                    M569 P4 S0 ; Z4 motor direction
                    M569 P5 S1 ; X motor direction
                    M569 P6 S1 ; Y motor direction

                    M350 X16 Y16 Z16 E16 I1 ; set microstepping
                    M92 X80 Y80 Z400 E426 ; set microsteps per mm
                    M566 X16000.00 Y16000.00 Z18000.00 E1200.00 ; set maximum instantaneous speed changes (mm/min)
                    M203 X24000.00 Y24000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min)
                    M201 X6000.00 Y6000.00 Z3000.00 E1500.00 ; set accelerations (mm/s^2)
                    M906 X800 Y800 Z800 E300 I30 ; set motor currents (mA) and motor idle factor in per cent
                    M84 S30 ; Set idle timeout

                    ; thermal section ------------------------------------------------------------
                    M308 S3 Y"mcu-temp" A"Board" ; Board thermal sensor
                    M912 P0 S-2 ; MCU tempurature sensor correction (subtract 2°K)

                    ; Axis Limits ----------------------------------------------------------------
                    M208 X0 Y0 Z0 S1 ; set axis minima
                    M208 X350 Y350 Z340 S0 ; set axis maxima

                    ; Endstops -------------------------------------------------------------------
                    M574 X2 S1 P"io3.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io3.in
                    M574 Y2 S1 P"io4.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io4.in
                    M574 Z1 S2 "io1.in" ; configure switch-type (e.g. Probe) endstop for low end on Z via pin io1.in

                    ; Z-Probe --------------------------------------------------------------------
                    M558 K0 P8 A2 S0.05 C"^io1.in" H5 F300 T16000 ; set Z probe type to modulated and the dive height + speeds
                    G31 P500 X0 Y10 Z1.590 ; set Z probe trigger value, offset and trigger height
                    M557 X15:335 Y15:335 S20 ; define mesh grid

                    ; 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 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
                    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 S300 ; set temperature limit for heater 1 to 300C

                    ; Fans -----------------------------------------------------------------------
                    M950 F0 C"out3" Q500 ; create fan 0 on pin out3 and set its frequency
                    M106 P0 S1 H1 T60 ; set fan 0 value. Thermostatic control is turned on
                    M950 F1 C"out4" Q500 ; create fan 1 on pin out4 and set its frequency
                    M106 P1 S0 H-1 ; set fan 1 value. Thermostatic control is turned off
                    M950 F2 C"out5" Q500 ; create fan 2 on pin out5 and set its frequency
                    M106 P2 S1 H-1 ; set fan 2 value. Thermostatic control is turned off
                    M950 F3 C"out6" Q500 ; create fan 3 on pin out6 and set its frequency
                    M106 P3 S0 H-1 ; set fan 3 value. Thermostatic control is turned off

                    ; Tools ----------------------------------------------------------------------
                    M563 P0 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 --------------------------------------------
                    M501

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

                      @jamaicarasta You need an M671 to set the pivot points of the gantry.
                      I would probably go with the point where it the belts attach

                      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

                      jamaicarastaundefined 1 Reply Last reply Reply Quote 1
                      • jamaicarastaundefined
                        jamaicarasta @jay_s_uk
                        last edited by

                        @jay_s_uk
                        ok m671… 😤 i forgot it. I read that yesterday. So measure again from the corner of the bed X0 Y0 and enter the minus value there?

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

                          @jamaicarasta yea, each one would typically sit outside the print area. the M671 should be in the order the Z motors are declared

                          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

                          jamaicarastaundefined 2 Replies Last reply Reply Quote 0
                          • jamaicarastaundefined
                            jamaicarasta @jay_s_uk
                            last edited by

                            @jay_s_uk
                            Ah ok. Xmotor1:motor2:motor3:motor4 Ymotor1:motor2:motor3:motor4
                            You are my hero 🙏
                            I hope I can ask you a few more questions in the near future. I still have a few things I don't quite understand.

                            1 Reply Last reply Reply Quote 1
                            • jamaicarastaundefined
                              jamaicarasta @jay_s_uk
                              last edited by

                              @jay_s_uk
                              I measured and found the values. Should I measure the values ​​from the probe points or simply add them to the entire coordinate system? Example X0Y0 as bett end x-55y-25 from bett end to my middle belt. Or measured from the probe coordinates I gave him.

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

                                @jamaicarasta the locations are in relation to X0 Y0

                                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

                                jamaicarastaundefined 1 Reply Last reply Reply Quote 0
                                • jamaicarastaundefined
                                  jamaicarasta @jay_s_uk
                                  last edited by

                                  @jay_s_uk
                                  Ok perfect 👍
                                  it works great now. Is there once enough or should he do it several times before printing. It's a very good probe now, I'm only asking because the red probe that came with it always took 4 rounds or more. I exchanged it because it melted at 285 degrees carbon printing defies cork and polyimide tape...

                                  1 Reply Last reply Reply Quote 0
                                  • jumpedwithbothfeetundefined
                                    jumpedwithbothfeet @jamaicarasta
                                    last edited by

                                    @jamaicarasta you had the X listed twice in each line instead of one X and one Y

                                    6 G30 P1 X15 X5 z-99999

                                    however I suspect @jay_s_uk hit the nail on the head with the probe numbering being the actual issue and flagging up the warning 🙂

                                    6HC Voron Trident based, 6XD CNC, Mini 5 polar printer

                                    jamaicarastaundefined jay_s_ukundefined 2 Replies Last reply Reply Quote 0
                                    • jamaicarastaundefined
                                      jamaicarasta @jumpedwithbothfeet
                                      last edited by

                                      @jumpedwithbothfeet
                                      Sorry that was a old file 😅
                                      I don’t saw this. Now is not x and x in one line 👊🏻

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

                                        @jumpedwithbothfeet you can get it to run until for so many iterations until a set value is obtained.
                                        we have an example here https://teamgloomy.github.io/useful_macros.html#bedg-file-for-g32 that can ne used with 4 locations as well

                                        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

                                        jamaicarastaundefined 1 Reply Last reply Reply Quote 0
                                        • jamaicarastaundefined
                                          jamaicarasta @jay_s_uk
                                          last edited by

                                          @jay_s_uk
                                          Thanks for the tip bro.
                                          Now I will make my mesh.g file.

                                          with an error: Push(): stack overflow

                                          ; mesh.g
                                          ; called to perform automatic bedmesh via G29

                                          M561 ; clear any bed...
                                          G29 ; bed mesh
                                          G1 X175 Y175 Z50 F20000 ; go to bed middle

                                          ; bed.g
                                          ; called to perform automatic bed compensation via G32

                                          M561 ; clear any bed transform
                                          G30 P0 X15 Y20 Z-99999 ; Probe links vorne
                                          G30 P1 X15 Y315 Z-99999 ; Probe links hinten
                                          G30 P2 X335 Y315 Z-99999 ; Probe rechts hinten
                                          G30 P3 X335 Y20 Z-99999 S4 ; Probe rechts vorne
                                          G1 X175 Y175 Z5 F20000

                                          ; homeall.g
                                          ; called to home all axes
                                          ;
                                          ; generated by RepRapFirmware Configuration Tool v3.3.10 on Fri Feb 11 2022 17:57:25 GMT+0100 (Mitteleuropäische Normalzeit)
                                          G91 ; relative positioning
                                          G1 H2 Z5 F6000 ; lift Z relative to current position
                                          G1 H1 X355 F6000 ; home X axis
                                          G1 X-5 F6000 ; go back a few mm
                                          G1 H1 X355 F360 ; move slowly to X axis endstop
                                          G1 H1 Y355 F6000 ; home y axis
                                          G1 Y-5 F6000 ; go back a few mm
                                          G1 H1 Y355 F360 ; move slowly to Y axis endstop
                                          G90 ; absolute positioning
                                          G1 X175 Y175 F20000 ; go to first probe point (Bettmitte)
                                          G30 ; home Z by probing the bed
                                          G90 ; absolute positioning

                                          ; Z-Probe --------------------------------------------------------------------
                                          M558 K0 P8 A2 S0.05 C"^io1.in" H2 F300 T16000 ; set Z probe type to modulated and the dive height + speeds
                                          G31 P500 X0 Y20 Z1.590 ; set Z probe trigger value, offset and trigger height
                                          M557 X15:335 Y35:315 S10 ; define mesh grid

                                          jay_s_ukundefined Phaedruxundefined 2 Replies Last reply Reply Quote 0
                                          • jay_s_ukundefined
                                            jay_s_uk @jamaicarasta
                                            last edited by

                                            @jamaicarasta not sure why you would receive a stack overflow. can you post an output of m122?

                                            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

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