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

Can't home printer after upgrade

Scheduled Pinned Locked Moved
General Discussion
2
3
418
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.
  • undefined
    Sir printsalot
    last edited by 12 Aug 2018, 16:37

    I upgraded to 2.01 rtos and dwc 1.21.1 now I can't home. g0/g1 insufficient axes homed. I need z up 5mm as my first homing move no matter what axes or combo is being run. I g92 x0, y0, z0 and than hit home all and error still happens. It won't run homing routine at all. This is added to a very long list of other non functioning functions. I looked at the wiki trouble shoot #1 and theres nothing there to help. I've reset everything wiper it up loaded erased boot loaded everything and I got nowhere.

    1 Reply Last reply Reply Quote 0
    • undefined
      deckingman
      last edited by 12 Aug 2018, 16:43

      It's always a good idea to check the release notes when you upgrade the firmware. You'll find that you'll need to add M564 H0 either to your homing files or to config.g. But check the release notes as there may be other changes that you need to be aware of.

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

      1 Reply Last reply Reply Quote 0
      • undefined
        Sir printsalot
        last edited by 12 Aug 2018, 17:10

        I added them and it still does it.
        Java remembered gcode error with dwc 1.22 even though it was a startup from fresh boot burn install and different pc.

        probe deploys and retracts but after retraction blinks. no error found but won't redeploy.

        I can't get functionality useless using really old dwc. and firmware or dwc which ever let printer run print without homing even though i can make it home without an error? something is really wrong and I have no idea what.

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