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

    Duet Maestro skipping layers while printing

    Scheduled Pinned Locked Moved
    Duet Web Control
    duet maestro troubleshooting
    5
    16
    1.1k
    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.
    • jacobsundlesundefined
      jacobsundles
      last edited by

      Alright, here's the gcodes , except the backup gcode, and the picture of the new javascript error. Thanks so much for you help.

      0_1563647079305_config.g
      0_1563647122748_CFFFP_f094a0f4-815f-4efa-8e16-e975c668113f.gcode
      0_1563647176479_20190720_110515.jpg

      1 Reply Last reply Reply Quote 0
      • jacobsundlesundefined
        jacobsundles
        last edited by

        The JavaScript error code showed up again, but this time it showed up right after I tried to disable the mesh bed leveling.

        1 Reply Last reply Reply Quote 0
        • oliofundefined
          oliof
          last edited by

          Also try running M122 and copy the output here. If the web interface doesn't run reliably, try connecting with YAT or pronterface.

          <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

          1 Reply Last reply Reply Quote 0
          • jacobsundlesundefined
            jacobsundles
            last edited by

            M122
            === Diagnostics ===
            RepRapFirmware for Duet 2 Maestro version 2.02RC5(RTOS) running on Duet Maestro 1.0
            Board ID: 08D8M-9T8A2-MQNSS-6J9D2-3SD6R-967GY
            Used output buffers: 3 of 20 (18 max)
            === RTOS ===
            Static ram: 21236
            Dynamic ram: 96988 of which 0 recycled
            Exception stack ram used: 420
            Never used ram: 12428
            Tasks: NETWORK(ready,456) HEAT(blocked,1300) MAIN(running,3672) IDLE(ready,200)
            Owned mutexes:
            === Platform ===
            Last reset 00:47:24 ago, cause: power up
            Last software reset at 2019-07-16 13:02, reason: User, spinning module GCodes, available RAM 12468 bytes (slot 3)
            Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0400f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
            Error status: 0
            Free file entries: 10
            SD card 0 detected, interface speed: 15.0MBytes/sec
            SD card longest block write time: 0.0ms, max retries 0
            MCU temperature: min 34.6, current 34.7, max 35.1
            Supply voltage: min 23.9, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
            Driver 0: standstill, read errors 0, write errors 0, ifcount 15, reads 871, timeouts 0
            Driver 1: standstill, read errors 0, write errors 0, ifcount 15, reads 871, timeouts 0
            Driver 2: standstill, read errors 0, write errors 0, ifcount 15, reads 871, timeouts 0
            Driver 3: standstill, read errors 0, write errors 0, ifcount 11, reads 871, timeouts 0
            Driver 4: standstill, read errors 0, write errors 0, ifcount 8, reads 871, timeouts 0
            Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 871
            Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 871
            Date/time: 2019-07-20 11:48:46
            Slowest loop: 3.82ms; fastest: 0.07ms
            I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
            === Move ===
            Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
            Scheduled moves: 7, completed moves: 7
            Bed compensation in use: mesh
            Bed probe heights: 0.000 0.000 0.000 0.000 0.000
            === Heat ===
            Bed heaters = 0, chamberHeaters = -1 -1
            Heater 0 is on, I-accum = 1.0
            === GCodes ===
            Segments left: 0
            Stack records: 3 allocated, 0 in use
            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
            serial is idle in state(s) 0
            aux is idle in state(s) 0
            daemon is idle in state(s) 0
            queue is idle in state(s) 0
            lcd is idle in state(s) 0
            autopause is idle in state(s) 0
            Code queue is empty.
            === Network ===
            Slowest loop: 69.93ms; fastest: 0.02ms
            Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
            HTTP sessions: 1 of 8
            Interface state 5, link 100Mbps full duplex

            1 Reply Last reply Reply Quote 0
            • oliofundefined
              oliof
              last edited by

              Can you run M122 directly after the layer skips happen, before you got emergency stop?

              <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

              1 Reply Last reply Reply Quote 0
              • oliofundefined
                oliof
                last edited by

                Also, you're running an unsupported 2.02 rc release,ake sure you update to 2.03

                <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

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

                  It looks like your firmware and DWC are a bit out of date or mismatched. Please try updating everything to the 2.03 release.

                  https://github.com/dc42/RepRapFirmware/releases/tag/2.03

                  You should be able to simply upload this zip file as is to the settings page: https://github.com/dc42/RepRapFirmware/releases/download/2.03/Duet2Firmware-2.03.zip

                  Z-Bot CoreXY Build | Thingiverse Profile

                  1 Reply Last reply Reply Quote 0
                  • jacobsundlesundefined
                    jacobsundles
                    last edited by

                    Thanks. I'll update a little later today and give that a shot.

                    Here is the M122 code that appeared after the same issue.
                    M122
                    === Diagnostics ===
                    RepRapFirmware for Duet 2 Maestro version 2.02RC5(RTOS) running on Duet Maestro 1.0
                    Board ID: 08D8M-9T8A2-MQNSS-6J9D2-3SD6R-967GY
                    Used output buffers: 3 of 20 (20 max)
                    === RTOS ===
                    Static ram: 21236
                    Dynamic ram: 96988 of which 0 recycled
                    Exception stack ram used: 380
                    Never used ram: 12468
                    Tasks: NETWORK(ready,456) HEAT(blocked,1300) MAIN(running,3672) IDLE(ready,200)
                    Owned mutexes:
                    === Platform ===
                    Last reset 00:19:20 ago, cause: power up
                    Last software reset at 2019-07-16 13:02, reason: User, spinning module GCodes, available RAM 12468 bytes (slot 3)
                    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0400f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
                    Error status: 4
                    Free file entries: 9
                    SD card 0 detected, interface speed: 15.0MBytes/sec
                    SD card longest block write time: 63.0ms, max retries 0
                    MCU temperature: min 24.0, current 38.2, max 38.3
                    Supply voltage: min 23.0, current 23.2, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
                    Driver 0: standstill, read errors 0, write errors 0, ifcount 12, reads 46375, timeouts 0
                    Driver 1: standstill, read errors 0, write errors 0, ifcount 12, reads 46375, timeouts 0
                    Driver 2: standstill, read errors 0, write errors 0, ifcount 12, reads 46375, timeouts 0
                    Driver 3: standstill, read errors 0, write errors 0, ifcount 10, reads 46376, timeouts 1
                    Driver 4: standstill, read errors 0, write errors 0, ifcount 8, reads 46379, timeouts 0
                    Driver 5: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 46386
                    Driver 6: ok, read errors 0, write errors 0, ifcount 0, reads 0, timeouts 46386
                    Date/time: 2019-07-20 14:55:27
                    Slowest loop: 4581228.50ms; fastest: 0.06ms
                    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
                    === Move ===
                    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 130, MaxWait: 737781ms, Underruns: 0, 0
                    Scheduled moves: 594, completed moves: 594
                    Bed compensation in use: mesh
                    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
                    === Heat ===
                    Bed heaters = 0, chamberHeaters = -1 -1
                    Heater 0 is on, I-accum = 0.9
                    Heater 1 is on, I-accum = 0.2
                    === GCodes ===
                    Segments left: 0
                    Stack records: 3 allocated, 0 in use
                    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
                    serial is idle in state(s) 0
                    aux is idle in state(s) 0
                    daemon is idle in state(s) 0
                    queue is idle in state(s) 0
                    lcd is idle in state(s) 0
                    autopause is idle in state(s) 0
                    Code queue is empty.
                    === Network ===
                    Slowest loop: 4581228.50ms; fastest: 0.02ms
                    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
                    HTTP sessions: 1 of 8
                    Interface state 5, link 100Mbps full duplex

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

                      there was a problem in the 2.02 firmware with time keeping that caused layer shifts.

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

                        @veti said in Duet Maestro skipping layers while printing:

                        there was a problem in the 2.02 firmware with time keeping that caused layer shifts.

                        That issue was in some 2.02RC and earlier releases. I fixed it before the 2.02 stable 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
                        • Vetiundefined
                          Veti
                          last edited by

                          @dc42 said in Duet Maestro skipping layers while printing:

                          That issue was in some 2.02RC

                          yes. he is using 2.02RC5, which was affected.

                          1 Reply Last reply Reply Quote 0
                          • jacobsundlesundefined
                            jacobsundles
                            last edited by

                            Awesome. You guys have been a great help. I'll respond today or tomorrow after I've updated it. Thank you again.

                            1 Reply Last reply Reply Quote 0
                            • jacobsundlesundefined
                              jacobsundles
                              last edited by

                              It's working better than ever. Guess it just needed a firmware update.

                              Thanks a bunch for your fast and professional help. Even though the solution was simple, i likely wouldn't have ever fixed the issue since I was at the end of my rope. So, thanks again.

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