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

    My printer is crazy

    Scheduled Pinned Locked Moved
    General Discussion
    2
    3
    224
    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.
    • Michael Subergundefined
      Michael Suberg
      last edited by

      After felt 10 rolls of filament my printer starts to do strange things.
      After the temperatures are reached, homing begins. The Y-axis moves normally to the limit switch and the X-axis literally creeps there (very slowly). Then the print head moves in the middle and Z-homing starts. Now the pressure starts in the middle and sometimes by a few centimeters next to it.
      The printof the part is absolutely normal. The X. axis also moves at normal speed.
      At the end of the print, however, the bed moves to the print head and crushes the finished print part.
      Can someone help me?

      Firmware 2.02 (RTOS)
      WIFI Server Version 1.22
      Web Interface 1.22.6

      Config.g :

      ; Configuration file for Duet WiFi (firmware version 1.21)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v2 on Sun Dec 02 2018 19:51:47 GMT+0100 (Mitteleuropäische Normalzeit)

      ; General preferences
      G90 ; Send absolute coordinates...
      M83 ; ...but relative extruder moves

      ; Network
      M550 P"Subis X400" ; Set machine name
      M552 S1 ; Enable network
      ;*** Access point is configured manually via M587
      M586 P0 S1 ; Enable HTTP
      M586 P1 S0 ; Disable FTP
      M586 P2 S0 ; Disable Telnet

      ; Drives
      M569 P0 S0 ; Drive 0 goes forwards
      M569 P1 S0 ; Drive 1 goes forwards
      M569 P2 S1 ; Drive 2 goes forwards
      M569 P3 S1 ; Drive 3 goes forwards
      M584 X0 Y2 Z1 E3 ; Apply custom drive mapping
      M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
      M92 X66.66 Y66.66 Z2400.00 E492.0 ; Set steps per mm
      M566 X900.00 Y900.00 Z12.00 E120.00 ; Set maximum instantaneous speed changes (mm/min)
      M203 X5000.00 Y5000.00 Z220.00 E1200.00 ; Set maximum speeds (mm/min)
      M201 X500.00 Y500.00 Z20.00 E250.00 ; Set accelerations (mm/s^2)
      M906 X1000.00 Y1000.00 Z1400.00 E1200.00 I30 ; Set motor currents (mA) and motor idle factor in per cent
      M84 S30 ; Set idle timeout

      ; Axis Limits
      M208 X0 Y0 Z0 S1 ; Set axis minima
      M208 X390 Y390 Z340 S0 ; Set axis maxima

      ; Endstops
      M574 X2 Y2 Z0 S1 ; Set active high endstops

      ; Z-Probe
      M574 Z1 S2 ; Set endstops controlled by probe
      M558 P1 H4 F120 T6000 ; Set Z probe type to modulated and the dive height + speeds
      G31 P500 X35 Y10 Z1.8 ; Set Z probe trigger value, offset and trigger height
      M557 X30:370 Y30:390 S40 ; Define mesh grid

      ; Heaters
      M305 P0 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 0
      M143 H0 S120 ; Set temperature limit for heater 0 to 120C
      M305 P1 X200 ; Set thermistor + ADC parameters for heater 1
      M143 H1 S280 ; Set temperature limit for heater 1 to 280C

      ; Fans
      M106 P0 H-1 ; Set fan 0 value, PWM signal Thermostatic control is turned off
      M106 P2 T45 H1 ; Set fan 1 value, Thermostatic control is turned on

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

      ; Automatic saving after power loss is not enabled

      ; Custom settings are not configured

      ; M557 X10:300 Y10:300 S25

      1 Reply Last reply Reply Quote 0
      • Vetiundefined
        Veti
        last edited by

        please post the end of a g code file where the crushing has occured

        1 Reply Last reply Reply Quote 0
        • Michael Subergundefined
          Michael Suberg
          last edited by

          Hello,
          problem found, cable from the limit switch is broken, therefore wrong switching states to the controller.

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