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

    Can't move the z axis in DWC more than 200

    Scheduled Pinned Locked Moved Solved
    General Discussion
    3
    7
    352
    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.
    • luka1952undefined
      luka1952
      last edited by luka1952

      Hi, Strangly i can't move z axis on my hypercube more than 200 in DWC. The z axis limit is 390. And before it was working ok.
      What can cause this?
      Is my board damaged?

      1 Reply Last reply Reply Quote 0
      • luka1952undefined luka1952 marked this topic as a question
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by Phaedrux

        Please share your config.g, homing files, bed.g, etc
        Also the results of M122 and M98 P"config.g"
        This will give us an idea of what is happening.

        When you say it won't move more than 200mm, what happens when it stops? What sequence of events is happening to lead up to this? Is it possible the Z axis is binding?

        Z-Bot CoreXY Build | Thingiverse Profile

        luka1952undefined 1 Reply Last reply Reply Quote 0
        • luka1952undefined
          luka1952 @Phaedrux
          last edited by

          @phaedrux
          Thanks for reply. This are my files you asked about.
          When my print has finished I wanted to juggle the bed down to remove it easer. I hit +50 on z axis in DWC (the part I printed was 180mm high) so the bed supposed to move 50mm down. But it stops at 200 and refuse to lower further. I repeated the command seweral times. But didn't work. Then I moved up a bit and try to lower it again. But still the same. Stops at 200.

          M122:
          18/02/2022, 07:20:51 M122
          === Diagnostics ===
          RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
          Board ID: 0JD0M-9P6B2-NJ4S8-6JKDD-3SS6M-9B5GJ
          Used output buffers: 3 of 24 (20 max)
          === RTOS ===
          Static ram: 23876
          Dynamic ram: 75636 of which 20 recycled
          Never used RAM 14884, free system stack 184 words
          Tasks: NETWORK(ready,13.7%,244) HEAT(delaying,0.1%,330) Move(notifyWait,0.1%,340) MAIN(running,85.7%,441) IDLE(ready,0.4%,29), total 100.0%
          Owned mutexes:
          === Platform ===
          Last reset 00:03:39 ago, cause: power up
          Last software reset at 2022-02-17 16:55, reason: User, GCodes spinning, available RAM 15264, slot 0
          Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
          Error status: 0x00
          Step timer max interval 0
          MCU temperature: min 25.1, current 31.4, max 31.6
          Supply voltage: min 24.1, current 24.1, max 24.4, 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 0, standstill, SG min/max not available
          Driver 1: position 0, standstill, SG min/max not available
          Driver 2: position 0, standstill, SG min/max not available
          Driver 3: position 0, standstill, SG min/max not available
          Driver 4: position 0, standstill, SG min/max not available
          Driver 5: position 0
          Driver 6: position 0
          Driver 7: position 0
          Driver 8: position 0
          Driver 9: position 0
          Driver 10: position 0
          Driver 11: position 0
          Date/time: 2022-02-18 07:20:51
          Cache data hit count 4294967295
          Slowest loop: 4.58ms; fastest: 0.17ms
          I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
          === Storage ===
          Free file entries: 10
          SD card 0 detected, interface speed: 20.0MBytes/sec
          SD card longest read time 3.5ms, write time 0.0ms, max retries 0
          === Move ===
          DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
          === MainDDARing ===
          Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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 -1 -1, chamberHeaters = 2 -1 -1 -1
          Heater 1 is on, I-accum = 0.0
          === 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
          Daemon is idle in state(s) 0
          Autopause is idle in state(s) 0
          Code queue is empty.
          === Network ===
          Slowest loop: 21.00ms; fastest: 0.00ms
          Responder states: HTTP(2) 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 e0:98:06:22:81:26
            WiFi Vcc 3.31, reset reason Turned on by main processor
            WiFi flash size 4194304, free heap 21080
            WiFi IP address 192.168.178.129
            WiFi signal strength -73dBm, mode 802.11n, reconnections 0, sleep mode modem
            Clock register 00002002
            Socket states: 0 0 0 0 0 0 0 0

          Bed.g

          ; bed.g
          ; called to perform automatic bed compensation via G32
          ;
          ; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Dec 13 2021 17:52:06 GMT+0100 (czas środkowoeuropejski standardowy)
          G28 ; home
          M401 ; deploy Z probe (omit if using bltouch)
          G30 P0 X0 Y185 Z-99999 ; probe near a leadscrew, half way along Y axis
          G30 P1 X330 Y185 Z-99999 S2 ; probe near a leadscrew and calibrate 2 motors
          M402 ; retract probe (omit if using bltouch)

          config.g

          G90 ; send absolute coordinates...
          M83 ; ...but relative extruder moves
          M550 P"Hypercube Evolution" ; 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
          M569 P0 S1 ; physical drive 0 goes forwards
          M569 P1 S1 ; physical drive 1 goes forwards
          M569 P2 S0 ; physical drive 2 goes backwards
          M569 P3 S1 ; physical drive 3 goes forwards
          M569 P4 S0 ; physical drive 4 goes backwards
          M584 X0 Y1 Z2:4 E3 ; set drive mapping
          M350 X16 Y16 Z16:16 E16 I1 ; configure microstepping with interpolation
          M92 X80.00 Y80.00 Z400.00:400.00 E693.00 ; set steps per mm
          M566 X2000.00 Y2000.00 Z50.00:50.00 E3000.00 ; set maximum instantaneous speed changes (mm/min)
          M203 X20000.00 Y20000.00 Z2000.00:2000.00 E15000.00; set maximum speeds (mm/min)
          M201 X10000.00 Y10000.00 Z50.00:50.00 E10000.00 ; set accelerations (mm/s^2)
          M906 X800 Y800 Z800:800 E600 I30 ; set motor currents (mA) and motor idle factor in per cent
          M84 S30 ; Set idle timeout
          M671 X0:400 Y185:185 S1 ; leadscrews at left (connected to Z) and right (connected to E1) of X axis

          M572 D0 S0.01

          ; Axis Limits
          M208 X0 Y0 Z0:0 S1 ; set axis minima
          M208 X390 Y375 Z390:390 S0 ; set axis maxima

          ; Endstops
          M574 X1 S3 ; configure sensorless endstop for low end on X
          M574 Y1 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
          M574 Z2 S2 ; configure Z-probe endstop for high end on Z
          M915 X R0 F0

          ; Z-Probe
          M950 S0 C"exp.heater7" ; create servo pin 0 for BLTouch
          M558 P9 C"^zprobe.in" H5 F120 T12000 ; set Z probe type to bltouch and the dive height + speeds
          G31 P500 X-28 Y-13 Z3.14 ; set Z probe trigger value, offset and trigger height
          M557 X0:350 Y10:360 S60 ; define mesh grid

          ; Heaters
          M308 S0 P"bedtemp" Y"thermistor" T100000 B4085 ; configure sensor 0 as thermistor on pin bedtemp
          M950 H0 C"bedheat" T0 ; create bed heater output on bedheat 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"spi.cs1" Y"rtd-max31865" ; configure sensor 1 as PT100 on pin spi.cs1
          M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
          M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
          M143 H1 S350 ; set temperature limit for heater 1 to 350C
          M308 S2 P"e1temp" Y"thermistor" T100000 B4066 ; configure sensor 2 as thermistor on pin e1temp
          M950 H2 C"e1heat" T2 ; create chamber heater output on e1heat and map it to sensor 2
          M307 H2 B1 S1.00 ; enable bang-bang mode for the chamber heater and set PWM limit
          M141 H2 ; map chamber to heater 2
          M143 H2 S80 ; set temperature limit for heater 2 to 80C

          ; Fans
          M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
          M106 P0 C"Filament Cooling Fan" S0 H-1 ; set fan 0 value. Thermostatic control is turned off
          M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
          M106 P1 C"Hotend Fan" S1.0 H1 T45 ; set fan 1 value. Thermostatic control is turned on
          M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its freqeuncy
          M106 P2 C"Filter Fan" S0 H-1 ; set fan 2 value. Thermostatic control is turned off

          ; Tools
          M563 P0 S"Sherpa/Dragon" D0 H1 ; 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

          ; Miscellaneous
          M501 ; load saved parameters from non-volatile memory
          M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
          T0

          homeall.g

          G91; relative positioning
          G1 H2 Z10 F12000 ; lift Z relative to current position
          G1 H1 Y-380 F3000 ; move quickly to Y axis endstop and stop there (first pass)
          G1 Y10 F6000 ; go back a few mm
          G1 H1 Y-380 F360 ; move slowly to Y axis endstop once more (second pass)
          M400
          M913 X60 Y70; drop motor current to 60%
          M201 X2000.00 Y2000.00
          G1 H1 X-400 F5000 ; move quickly to X axis endstop and stop there (first pass)
          G1 H2 X5 F12000 ; go back a few mm
          G1 H1 X-400 F4000 ; move slowly to X axis endstop once more (second pass)
          G1 X10
          G92 X0
          M201 X3000.00 Y3000.00
          G90 ; absolute positioning
          M400
          M913 X100 Y100 ; return current to 100%
          M400
          G1 X200 Y200 F12000 ; go to first bed probe point and home Z
          G30 ; home Z by probing the bed```

          homez.g

          G91 ; relative positioning
          G1 H2 Z5 F12000 ; lift Z relative to current position
          G90 ; absolute positioning
          G1 X200 Y200 F12000 ; go to first probe point
          G30 ; home Z by probing the bed

          M98 P"config.g"

          HTTP is enabled on port 80
          FTP is disabled
          TELNET is disabled
          Error: Z axis maximum must be greater than minimum
          Error: Z axis maximum must be greater than minimum
          Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 285C
          Warning: Heater 2 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C

          engikeneerundefined 1 Reply Last reply Reply Quote 0
          • engikeneerundefined
            engikeneer @luka1952
            last edited by engikeneer

            @luka1952 M98 P"config.g" shows your issue:

            Error: Z axis maximum must be greater than minimum
            Error: Z axis maximum must be greater than minimum
            
            ; Axis Limits
            M208 X0 Y0 Z0:0 S1 ; set axis minima
            M208 X390 Y375 Z390:390 S0 ; set axis maxima
            

            You have put in a double value for Z for both min and max. There should be only one value in both. My guess is that it fails to interpret this and so retains the default limits (zmax 200).

            Change it to

            ; Axis Limits
            M208 X0 Y0 Z0 S1 ; set axis minima
            M208 X390 Y375 Z390 S0 ; set axis maxima
            

            Same applies to all your other settings (steps, microsteps currents, accel, jerk, max speed). RRF only support one value per axis for each of these (apart from extruders)

            E3D TC with D3Mini and Toolboards.
            Home-built CoreXY, Duet Wifi, Chimera direct drive, 2x BMG, 300x300x300 build volume
            i3 clone with a bunch of mods

            luka1952undefined 1 Reply Last reply Reply Quote 1
            • luka1952undefined
              luka1952 @engikeneer
              last edited by luka1952

              @engikeneer
              I have dubbele z axis with two independent steppers/drivers.
              This make possible to adjust the two z axis screws apart from each other.

              engikeneerundefined 1 Reply Last reply Reply Quote 0
              • engikeneerundefined
                engikeneer @luka1952
                last edited by

                @luka1952 but they are one axis. If they were different, it just wouldn't work. They can't have different limits, acceleration rates etc if they move together as one axis.

                I say again, RRF only supports one value per axis for each of these (apart from extruders)

                E3D TC with D3Mini and Toolboards.
                Home-built CoreXY, Duet Wifi, Chimera direct drive, 2x BMG, 300x300x300 build volume
                i3 clone with a bunch of mods

                luka1952undefined 1 Reply Last reply Reply Quote 0
                • luka1952undefined
                  luka1952 @engikeneer
                  last edited by

                  @engikeneer
                  Thanks, I've changed it and it works 🙂
                  Thank you very much.
                  There is one more problem I have but that's in the other topic. Could you have a look? I can't solve it...

                  1 Reply Last reply Reply Quote 0
                  • dc42undefined dc42 has marked this topic as solved
                  • First post
                    Last post
                  Unless otherwise noted, all forum content is licensed under CC-BY-SA