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

    Incorrect print estimate DWC.

    Scheduled Pinned Locked Moved
    Duet Web Control
    2
    11
    629
    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.
    • Surgikillundefined
      Surgikill
      last edited by

      Hey guys. I upgraded my DWC. I need to update my duet, which I'll be doing this weekend. The issue that I'm having is that DWC isn't showing the correct file progress in the progress bar. I have my gcode set up to move the bed near the max limit (CoreXY so the bed lowers all the way) and it seems that this is messing it up. Before I upgraded DWC this worked fine, but now I have issues with it.

      Under software info it says:

      Firmware Version: 2.01 (RTOS)
      Wifi Server Version: 1.21
      Web Interface Version: 1.22.3

      Maybe if I update my duet this will all be fixed?

      1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        Can you post a sample gcode file? Or at least the first 50 lines or so? I'd like to see what your start gcode looks like. As you say, the large z move may be messing it up.

        What slicer are you using?

        If you upload this zip file to the settings tab on the DWC it should update your firmware, wifi server, and DWC to the latest stable release.
        https://github.com/dc42/RepRapFirmware/releases/download/2.02/Duet2Firmware-2.02b.zip

        I don't know that it will make a difference though. One work around that does work is to move the offending part of your startup gcode into start.g which gets run when a print starts before the slicer start gcode does, and since it's outside of the print gcode file the z move doesn't get parsed.

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 0
        • Surgikillundefined
          Surgikill
          last edited by

          Prusa Slicer, V2.00. Thanks for the link. I'll update that tomorrow.

          ; generated by PrusaSlicer 2.0.0+win64 on 2019-06-07 at 00:11:36

          ;

          ; external perimeters extrusion width = 0.45mm
          ; perimeters extrusion width = 0.45mm
          ; infill extrusion width = 0.45mm
          ; solid infill extrusion width = 0.45mm
          ; top infill extrusion width = 0.40mm
          ; first layer extrusion width = 0.22mm

          M107
          M190 S70 ; set bed temperature and wait for it to be reached
          M104 S255 ; set temperature
          G32 ;home and level

          G28 ;home
          ; Filament gcode
          M109 S255 ; set temperature and wait for it to be reached
          G21 ; set units to millimeters
          G90 ; use absolute coordinates
          M82 ; use absolute distances for extrusion
          G92 E0
          G1 Z0.200 F7800.000
          G1 E-2.00000 F2400.00000
          G92 E0
          G1 X132.187 Y142.191 F7800.000
          G1 E2.25000 F2400.00000
          G1 F1800
          G1 X133.980 Y140.562 E2.28568
          G1 X135.936 Y139.104 E2.32160
          G1 X138.156 Y137.770 E2.35973
          G1 X140.359 Y136.730 E2.39560
          G1 X142.657 Y135.906 E2.43154
          G1 X145.167 Y135.280 E2.46964
          G1 X147.583 Y134.928 E2.50558
          G1 X150.004 Y134.811 E2.54128
          G1 X152.436 Y134.930 E2.57712
          G1 X154.995 Y135.312 E2.61523
          G1 X157.362 Y135.911 E2.65119

          Phaedruxundefined 1 Reply Last reply Reply Quote 0
          • Phaedruxundefined
            Phaedrux Moderator @Surgikill
            last edited by

            @surgikill said in Incorrect print estimate DWC.:

            Prusa Slicer, V2.00

            That would explain it. There was a change in their formatting. It's been fixed in 2.03 RC4+
            https://github.com/dc42/RepRapFirmware/releases/tag/2.03RC5

            So you can either upgrade to the release candidate for 2.03 or wait a few more days for the final release.

            Z-Bot CoreXY Build | Thingiverse Profile

            1 Reply Last reply Reply Quote 0
            • Surgikillundefined
              Surgikill
              last edited by

              @phaedrux If I want to flash the release candidates, can I download the combined firmware for RC5, or should I only go to 2.02?

              1 Reply Last reply Reply Quote 0
              • Phaedruxundefined
                Phaedrux Moderator
                last edited by

                I'd probably start with 2.02 zip file so you have the right wifi server and DWC files. Then update to the 2.03 RC5 firmware.

                Z-Bot CoreXY Build | Thingiverse Profile

                Surgikillundefined 1 Reply Last reply Reply Quote 0
                • Surgikillundefined
                  Surgikill @Phaedrux
                  last edited by

                  @phaedrux I see you have a coreXY printer. I was reading that the core kinematics changed in 2.03. Any tips for swapping over?

                  Phaedruxundefined 1 Reply Last reply Reply Quote 0
                  • Phaedruxundefined
                    Phaedrux Moderator @Surgikill
                    last edited by

                    @surgikill for me everything just worked, nothing had to be modified in the config, so I didn't really dig into it further. But it's never a bad idea to take it slow when testing a new firmware update.

                    I have a macro that drops currents and allows movement without being homed so that I can test motor movement with a few small jogging moves before trying to even home the printer.

                    Z-Bot CoreXY Build | Thingiverse Profile

                    Surgikillundefined 1 Reply Last reply Reply Quote 0
                    • Surgikillundefined
                      Surgikill @Phaedrux
                      last edited by

                      @phaedrux Can I get that macro? I haven't delved completely into everything yet. The printer still isn't completed from the hardware side so I haven't bothered to customize the software too much.

                      Phaedruxundefined 1 Reply Last reply Reply Quote 0
                      • Phaedruxundefined
                        Phaedrux Moderator @Surgikill
                        last edited by

                        @surgikill I'm mobile right now but it was a pretty simple macro

                        M913 to drop the currents.
                        The mcode to allow movement without homing
                        Then a sequence of m291 commands to pop up axis jogging prompts one after the other just to make sure they move in the right direction.
                        Then another m913 to return current to normal.

                        Z-Bot CoreXY Build | Thingiverse Profile

                        1 Reply Last reply Reply Quote 0
                        • Phaedruxundefined
                          Phaedrux Moderator
                          last edited by

                          ; Quick motor testing
                          M913 X35 Y35 ; drop motor current
                          M564 S0 H0 ; allow movement without being homed and allow movement outside limits
                          M291 R"Test X axis" P"Slowly test movement of X axis with small increment of movement" S3 X1
                          M291 R"Test Y axis" P"Slowly test movement of Y axis with small increment of movement" S3 Y1
                          M400
                          M913 X85 Y85 ; return motor currents to normal
                          M564 S1 H1 ; restrict movement of unhomed axis and prevent movement outside limits
                          

                          If motors still move correctly, test homing.

                          Z-Bot CoreXY Build | Thingiverse Profile

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