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

    DuetWiFi Issues

    Scheduled Pinned Locked Moved
    General Discussion
    2
    9
    1.0k
    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.
    • Vigneshundefined
      Vignesh
      last edited by

      I am new to the DuetWiFi board. I am using :

      Firmware Name: RepRapFirmware for Duet WiFi
      Firmware Electronics: Duet WiFi 1.0
      Firmware Version: 1.19.2 (2017-09-01)
      WiFi Server Version: 1.19.2
      Web Interface Version: 1.19.

      I followed the instructions on the website. I use a CoreXY configuration for the 3D printer. I have the following issues:

      1. When I home the printer it homes fine, after it finishes homing it says "Homing Failed". I get the same error on Pronterface and DuetWeb Control. I am not sure why this happens.

      2. I am not using any heated bed, but it shows it is at 2000 degrees. How can I remove it or make it 0?

      Thanks

      1 Reply Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators
        last edited by

        Regarding #1, please share your homing files. After homing, what colours are the homing buttons in DWC?

        Regarding #2, use M140 H-1 in config.g to specify that there is no bed heater.

        Duet WiFi hardware designer and firmware engineer
        Please do not ask me for Duet support via PM or email, use the forum
        http://www.escher3d.com, https://miscsolutions.wordpress.com

        1 Reply Last reply Reply Quote 0
        • Vigneshundefined
          Vignesh
          last edited by

          Thanks, M140 H-1 disable the bed temperature.

          The buttons stay in yellow colour after homing.

          My homing files is:```
          [[language]]G91 ; relative mode

          G1 Z10 F300 ; raise extruder nozzle

          G1 S1 X-240 Y-240 F3000 ; course home X or Y

          G1 S1 X-240 ; course home X

          G1 S1 Y-240 ; course home Y

          G1 X4 Y4 F600 ; move away from the endstops

          G1 S1 X-10 ; fine home X

          G1 S1 Y-10 ; fine home Y

          M84

          G1 Z150 F200 S1 ; course home Z
          G1 Z-4 F100 ; move away from endstops
          G1 Z10 S1 ; fine home Z

          G90 ; back to absolute mode

          G1 X25 Y25 Z20 F5000 ; send to (25,25,20)
          G1 Z10 F300 ; send to (0,0,10)
          G1 Z0 F200 ; send to (0,0,0)

          M84

          1 Reply Last reply Reply Quote 0
          • dc42undefined
            dc42 administrators
            last edited by

            The problem is the M84 commands. They disable the stepper motors, so the firmware assumes that the motor position is no longer stable. So remove them. The motor currents will be reduced to the idle percentage automatically after the idle timeout.

            Duet WiFi hardware designer and firmware engineer
            Please do not ask me for Duet support via PM or email, use the forum
            http://www.escher3d.com, https://miscsolutions.wordpress.com

            1 Reply Last reply Reply Quote 0
            • Vigneshundefined
              Vignesh
              last edited by

              Thanks, removing M84 fixed the issue.

              I have one last issue, the command M114 does not give any output in Pronterface but works in DWC. Do you know why this happens? is there a fix for that?

              1 Reply Last reply Reply Quote 0
              • dc42undefined
                dc42 administrators
                last edited by

                Pronterface is very picky about the response format it expects, and it chokes on an extra space character in the M114 response returned by RRF. This space character is removed in RRF 1.20beta2. BUT that version has a bug in the code for homing CoreXY printers, so please wait for the next beta release.

                Duet WiFi hardware designer and firmware engineer
                Please do not ask me for Duet support via PM or email, use the forum
                http://www.escher3d.com, https://miscsolutions.wordpress.com

                1 Reply Last reply Reply Quote 0
                • Vigneshundefined
                  Vignesh
                  last edited by

                  okay, thanks. Can I use the same drivers you have in the github link for MAC computers too, or do you have specific drivers for MAC?

                  1 Reply Last reply Reply Quote 0
                  • dc42undefined
                    dc42 administrators
                    last edited by

                    I don't think you need any drivers for Mac, same as for Linux.

                    Duet WiFi hardware designer and firmware engineer
                    Please do not ask me for Duet support via PM or email, use the forum
                    http://www.escher3d.com, https://miscsolutions.wordpress.com

                    1 Reply Last reply Reply Quote 0
                    • Vigneshundefined
                      Vignesh
                      last edited by

                      okay, thanks!

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