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.7k
    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.
    • 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
                                  • jamaicarastaundefined
                                    jamaicarasta @jay_s_uk
                                    last edited by

                                    @jay_s_uk What do you mean?

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

                                      @jamaicarasta send M122 on the console tab ans post here whats spat out

                                      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 Ok 1 min

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

                                          @jay_s_uk M122
                                          === Diagnostics ===
                                          RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus WiFi (standalone mode)
                                          Board ID: YHJ3Q-U296U-D65J0-40KMS-0K03Z-ZGYPZ
                                          Used output buffers: 3 of 40 (13 max)
                                          === RTOS ===
                                          Static ram: 102724
                                          Dynamic ram: 107620 of which 28 recycled
                                          Never used RAM 33332, free system stack 130 words
                                          Tasks: NETWORK(ready,16.0%,216) HEAT(notifyWait,0.0%,348) Move(notifyWait,0.1%,283) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,357) CanClock(delaying,0.0%,338) TMC(delaying,1.2%,115) MAIN(running,81.9%,412) IDLE(ready,0.0%,29) AIN(delaying,0.8%,264), total 100.0%
                                          Owned mutexes: WiFi(NETWORK)
                                          === Platform ===
                                          Last reset 00:42:50 ago, cause: software
                                          Last software reset at 2022-02-16 16:05, reason: User, GCodes spinning, available RAM 33764, slot 1
                                          Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
                                          Error status: 0x00
                                          Aux0 errors 0,0,0
                                          MCU revision 3, ADC conversions started 2570411, completed 2570409, timed out 0, errs 0
                                          Step timer max interval 1463
                                          MCU temperature: min 25.4, current 25.8, max 27.6
                                          Supply voltage: min 23.9, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
                                          Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
                                          Driver 0: position 28000, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 159, reads 37031, writes 9, timeouts 0, DMA errors 0
                                          Driver 1: position 0, standstill, SG min/max 0/486, read errors 0, write errors 1, ifcnt 203, reads 37020, writes 20, timeouts 0, DMA errors 0
                                          Driver 2: position 1436, standstill, SG min/max 0/470, read errors 0, write errors 1, ifcnt 203, reads 37020, writes 20, timeouts 0, DMA errors 0
                                          Driver 3: position 0, standstill, SG min/max 0/468, read errors 0, write errors 1, ifcnt 203, reads 37020, writes 20, timeouts 0, DMA errors 0
                                          Driver 4: position 0, standstill, SG min/max 0/502, read errors 0, write errors 1, ifcnt 203, reads 37020, writes 20, timeouts 0, DMA errors 0
                                          Driver 5: position 0, standstill, SG min/max 0/508, read errors 0, write errors 1, ifcnt 203, reads 37020, writes 20, timeouts 0, DMA errors 0
                                          Driver 6: position 0, standstill, SG min/max 0/502, read errors 0, write errors 1, ifcnt 203, reads 37020, writes 20, timeouts 0, DMA errors 0
                                          Date/time: 2022-02-16 16:47:53
                                          Cache data hit count 4294967295
                                          Slowest loop: 23.40ms; fastest: 0.11ms
                                          === Storage ===
                                          Free file entries: 10
                                          SD card 0 detected, interface speed: 22.5MBytes/sec
                                          SD card longest read time 3.9ms, write time 6.2ms, max retries 0
                                          === Move ===
                                          DMs created 83, maxWait 850021ms, bed compensation in use: none, comp offset 0.000
                                          === MainDDARing ===
                                          Scheduled moves 151, completed moves 151, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 4], CDDA state -1
                                          === AuxDDARing ===
                                          Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                                          === Heat ===
                                          Bed heaters = 0 -1, chamberHeaters = -1 -1
                                          === GCodes ===
                                          Segments left: 0
                                          Movement lock held by null
                                          HTTP is idle in state(s) 0
                                          Telnet is idle in state(s) 0
                                          File is idle in state(s) 0
                                          USB is idle in state(s) 0
                                          Aux is idle in state(s) 0
                                          Trigger is idle in state(s) 0
                                          Queue is idle in state(s) 0
                                          LCD is idle in state(s) 0
                                          SBC is idle in state(s) 0
                                          Daemon is idle in state(s) 0
                                          Aux2 is idle in state(s) 0
                                          Autopause is idle in state(s) 0
                                          Code queue is empty.
                                          === CAN ===
                                          Messages queued 23194, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 17 (min 17), ts 12852/0/0
                                          Tx timeouts 0,61,12851,0,0,10279 last cancelled message type 30 dest 127

                                          === Network ===
                                          Slowest loop: 76.53ms; fastest: 0.00ms
                                          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
                                          HTTP sessions: 1 of 8

                                          • WiFi -
                                            Network state is active
                                            WiFi module is connected to access point
                                            Failed messages: pending 0, notready 0, noresp 0
                                            WiFi firmware version 1.26
                                            WiFi MAC address d8:bf:c0:14:e8:2c
                                            WiFi Vcc 3.30, reset reason Power up
                                            WiFi flash size 2097152, free heap 25040
                                            WiFi IP address 192.168.178.28
                                            WiFi signal strength -52dBm, mode 802.11n, reconnections 0, sleep mode modem
                                            Clock register 00002002
                                            Socket states: 0 0 0 0 0 0 0 0
                                          jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                                          • jay_s_ukundefined
                                            jay_s_uk @jamaicarasta
                                            last edited by

                                            @jamaicarasta can you post your full config, full bed file and full mesh.g file

                                            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