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

    Stuttering Duet Board

    Scheduled Pinned Locked Moved
    General Discussion
    2
    16
    1.6k
    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.
    • Gregcundefined
      Gregc
      last edited by

      Thanks. I changed the wiring and I am still getting the same error. I am going to take my Duetwifi from my DC42 Delta and will try it on my CoreXY, and visa versa.

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

        Does your M122 report list any I2C errors when this problem occurs?

        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
        • Gregcundefined
          Gregc
          last edited by

          i'll check tonight and will report back tomorrow.
          Thanks again.

          1 Reply Last reply Reply Quote 0
          • Gregcundefined
            Gregc
            last edited by Gregc

            Here are the before and after M122 reports.
            After has a "DueX I2C errors 2462"

            11:16:36 PM
            M122
            === Diagnostics ===
            RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01(RTOS) running on Duet WiFi 1.02 or later + DueX5
            Board ID: 08DGM-956GU-DJMSJ-6J1FA-3SJ6J-TAQVF
            Used output buffers: 1 of 20 (9 max)
            === RTOS ===
            Static ram: 28476
            Dynamic ram: 96240 of which 16 recycled
            Exception stack ram used: 320
            Never used ram: 6020
            Tasks: NETWORK(ready,400) HEAT(blocked,1192) MAIN(running,3540)
            Owned mutexes:
            === Platform ===
            Last reset 00:01:17 ago, cause: reset button or watchdog
            Last software reset at 2018-08-17 17:19, reason: User, spinning module GCodes, available RAM 5976 bytes (slot 3)
            Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
            Error status: 0
            Free file entries: 10
            SD card 0 detected, interface speed: 20.0MBytes/sec
            SD card longest block write time: 0.0ms, max retries 0
            MCU temperature: min 28.8, current 31.3, max 31.6
            Supply voltage: min 24.4, current 24.5, max 24.8, under voltage events: 0, over voltage events: 0
            Driver 0: standstill, SG min/max not available
            Driver 1: standstill, SG min/max not available
            Driver 2: standstill, SG min/max not available
            Driver 3: standstill, SG min/max not available
            Driver 4: standstill, SG min/max not available
            Driver 5: standstill, SG min/max not available
            Driver 6: standstill, SG min/max not available
            Driver 7: standstill, SG min/max not available
            Driver 8: standstill, SG min/max not available
            Driver 9: standstill, SG min/max not available
            Expansion motor(s) stall indication: no
            Date/time: 2018-08-18 23:16:35
            Slowest loop: 28.78ms; fastest: 2.96ms
            === Move ===
            Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
            Scheduled moves: 0, completed moves: 0
            Bed compensation in use: none
            Bed probe heights: 0.000 0.000 0.000 0.000 0.000
            === Heat ===
            Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
            Heater 1 is on, I-accum = 0.0
            === GCodes ===
            Segments left: 0
            Stack records: 1 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
            autopause is idle in state(s) 0
            Code queue is empty.
            === Network ===
            Slowest loop: 16.05ms; fastest: 0.01ms
            Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
            HTTP sessions: 1 of 8

            • WiFi -
              Network state is running
              WiFi module is connected to access point
              Failed messages: pending 0, notready 0, noresp 0
              WiFi firmware version 1.21RC4(08b3)
              WiFi MAC address 60:01:94:73:54:18
              WiFi Vcc 3.37, reset reason Turned on by main processor
              WiFi flash size 4194304, free heap 17136

            WiFi IP address 192.168.86.35
            WiFi signal strength -49dBm, reconnections 0, sleep mode modem
            Socket states: 0 0 0 0 0 0 0 0
            === Expansion ===
            DueX I2C errors 0

            11:18:25 PM
            M122
            === Diagnostics ===
            RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01(RTOS) running on Duet WiFi 1.02 or later + DueX5
            Board ID: 08DGM-956GU-DJMSJ-6J1FA-3SJ6J-TAQVF
            Used output buffers: 1 of 20 (16 max)
            === RTOS ===
            Static ram: 28476
            Dynamic ram: 96276 of which 16 recycled
            Exception stack ram used: 484
            Never used ram: 5820
            Tasks: NETWORK(ready,400) HEAT(blocked,1192) MAIN(running,3540)
            Owned mutexes:
            === Platform ===
            Last reset 00:03:06 ago, cause: reset button or watchdog
            Last software reset at 2018-08-17 17:19, reason: User, spinning module GCodes, available RAM 5976 bytes (slot 3)
            Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
            Error status: 0
            Free file entries: 9
            SD card 0 detected, interface speed: 20.0MBytes/sec
            SD card longest block write time: 0.0ms, max retries 0
            MCU temperature: min 31.3, current 32.9, max 32.9
            Supply voltage: min 24.4, current 24.5, max 24.7, under voltage events: 0, over voltage events: 0
            Driver 0: standstill, SG min/max 0/214
            Driver 1: standstill, SG min/max 0/124
            Driver 2: standstill, SG min/max 0/0
            Driver 3: standstill, SG min/max not available
            Driver 4: standstill, SG min/max not available
            Driver 5: standstill, SG min/max 48/240
            Driver 6: standstill, SG min/max 43/229
            Driver 7: standstill, SG min/max 51/241
            Driver 8: standstill, SG min/max not available
            Driver 9: standstill, SG min/max not available
            Expansion motor(s) stall indication: yes
            Date/time: 2018-08-18 23:18:24
            Slowest loop: 232.36ms; fastest: 2.96ms
            === Move ===
            Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 236, MaxWait: 122958ms, Underruns: 0, 0
            Scheduled moves: 13, completed moves: 13
            Bed compensation in use: none
            Bed probe heights: 0.000 0.000 0.000 0.000 0.000
            === Heat ===
            Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
            Heater 1 is on, I-accum = 0.0
            === GCodes ===
            Segments left: 0
            Stack records: 2 allocated, 1 in use
            Movement lock held by aux
            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 5
            daemon is idle in state(s) 0
            queue is idle in state(s) 0
            autopause is idle in state(s) 0
            Code queue is empty.
            === Network ===
            Slowest loop: 234.35ms; fastest: 0.08ms
            Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
            HTTP sessions: 1 of 8

            • WiFi -
              Network state is running
              WiFi module is connected to access point
              Failed messages: pending 0, notready 0, noresp 0
              WiFi firmware version 1.21RC4(08b3)
              WiFi MAC address 60:01:94:73:54:18
              WiFi Vcc 3.38, reset reason Turned on by main processor
              WiFi flash size 4194304, free heap 15672
              WiFi IP address 192.168.86.35
              WiFi signal strength -50dBm, reconnections 0, sleep mode modem
              Socket states: 0 0 0 0 0 0 0 0
              === Expansion ===
              DueX I2C errors 2462
            1 Reply Last reply Reply Quote 0
            • Gregcundefined
              Gregc
              last edited by

              David,
              Does my DueX I2C errors 2462 mean my DueX 5 board is dead?
              Thanks

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

                Please try firmware 2.02beta1. It fixes I2C errors caused by task switching in the middle of an I2C transaction.

                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
                • Gregcundefined
                  Gregc
                  last edited by

                  Thank you David. I will give it a try.

                  1 Reply Last reply Reply Quote 0
                  • Gregcundefined
                    Gregc
                    last edited by

                    Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
                    Firmware Electronics: Duet WiFi 1.02 or later + DueX5
                    Firmware Version: 2.02beta1(RTOS) (2018-08-12b5)
                    WiFi Server Version: 1.21RC4(08b3)
                    Web Interface Version: 1.22.1

                    Unfortunately my latest M122 contains "DueX I2C errors 9602"

                    7:42:48 PMM122
                    === Diagnostics ===
                    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02beta1(RTOS) running on Duet WiFi 1.02 or later + DueX5
                    Board ID: 08DGM-956GU-DJMSJ-6J1FA-3SJ6J-TAQVF
                    Used output buffers: 1 of 20 (14 max)
                    === RTOS ===
                    Static ram: 28476
                    Dynamic ram: 98316 of which 0 recycled
                    Exception stack ram used: 460
                    Never used ram: 3820
                    Tasks: NETWORK(ready,400) HEAT(blocked,1192) MAIN(running,3476)
                    Owned mutexes:
                    === Platform ===
                    Last reset 00:03:56 ago, cause: power up
                    Last software reset at 2018-08-20 17:31, reason: User, spinning module GCodes, available RAM 3740 bytes (slot 0)
                    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
                    Error status: 0
                    Free file entries: 10
                    SD card 0 detected, interface speed: 20.0MBytes/sec
                    SD card longest block write time: 0.0ms, max retries 0
                    MCU temperature: min 26.9, current 32.8, max 33.0
                    Supply voltage: min 24.4, current 24.5, max 24.7, under voltage events: 0, over voltage events: 0
                    Driver 0: standstill, SG min/max 0/1023
                    Driver 1: standstill, SG min/max 0/1023
                    Driver 2: standstill, SG min/max 0/0
                    Driver 3: standstill, SG min/max not available
                    Driver 4: standstill, SG min/max not available
                    Driver 5: standstill, SG min/max 65/219
                    Driver 6: standstill, SG min/max 59/202
                    Driver 7: standstill, SG min/max 65/200
                    Driver 8: standstill, SG min/max not available
                    Driver 9: standstill, SG min/max not available
                    Expansion motor(s) stall indication: yes
                    Date/time: 2018-08-20 19:42:47
                    Slowest loop: 180.60ms; fastest: 3.09ms
                    === Move ===
                    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 236, MaxWait: 14990ms, Underruns: 0, 0
                    Scheduled moves: 24, completed moves: 24
                    Bed compensation in use: none
                    Bed probe heights: 5.000 5.000 5.000 0.000 0.000
                    === Heat ===
                    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
                    Heater 0 is on, I-accum = 0.0
                    Heater 1 is on, I-accum = 0.3
                    === GCodes ===
                    Segments left: 0
                    Stack records: 2 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 ready with "M408 S0 R11" in state(s) 0
                    daemon is idle in state(s) 0
                    queue is idle in state(s) 0
                    autopause is idle in state(s) 0
                    Code queue is empty.
                    === Network ===
                    Slowest loop: 196.78ms; fastest: 0.01ms
                    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
                    HTTP sessions: 1 of 8

                    • WiFi -
                      Network state is running
                      WiFi module is connected to access point
                      Failed messages: pending 0, notready 0, noresp 0
                      WiFi firmware version 1.21RC4(08b3)
                      WiFi MAC address 60:01:94:73:54:18
                      WiFi Vcc 3.37, reset reason Turned on by main processor
                      WiFi flash size 4194304, free heap 15672
                      WiFi IP address 192.168.86.30
                      WiFi signal strength -53dBm, reconnections 0, sleep mode modem
                      Socket states: 0 0 0 0 0 0 0 0
                      === Expansion ===
                      DueX I2C errors 9602
                    1 Reply Last reply Reply Quote 0
                    • dc42undefined
                      dc42 administrators
                      last edited by

                      The most likely causes of all those I2C errors are:

                      1. Inadequate ground connection between the Duet and the DueX5. If this is the cause, there will probably be no I2C errors until you start moving the motors.
                      2. Faulty DueX5
                      3. Faulty ribbon cable.

                      Please test whether you get I2C errors when the motors haven't moved since power up, or after you send M18 to turn them off. Also please post a photo showing how you have connected the grounds of the Duet and DueX5 together.

                      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
                      • Gregcundefined
                        Gregc
                        last edited by Gregc

                        David, the DueX I2C errors 20094 occurred after printing about eight layers of a 40x40 test cube. I cancelled the print and sent an M18 command, but the error remained. Here is a photo of my wiring. I am using 14 AWG silicon covered wires for the VIN terminals. I also tried another ribbon cable.

                        0_1534878574540_IMG-0870.JPG

                        2:55:59 PMM122
                        === Diagnostics ===
                        RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02beta1(RTOS) running on Duet WiFi 1.02 or later + DueX5
                        Board ID: 08DGM-956GU-DJMSJ-6J1FA-3SJ6J-TAQVF
                        Used output buffers: 1 of 20 (18 max)
                        === RTOS ===
                        Static ram: 28476
                        Dynamic ram: 98316 of which 0 recycled
                        Exception stack ram used: 484
                        Never used ram: 3796
                        Tasks: NETWORK(ready,400) HEAT(blocked,1192) MAIN(running,1660)
                        Owned mutexes:
                        === Platform ===
                        Last reset 00:21:44 ago, cause: power up
                        Last software reset at 2018-08-20 17:31, reason: User, spinning module GCodes, available RAM 3740 bytes (slot 0)
                        Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
                        Error status: 0
                        Free file entries: 10
                        SD card 0 detected, interface speed: 20.0MBytes/sec
                        SD card longest block write time: 0.0ms, max retries 0
                        MCU temperature: min 36.4, current 36.5, max 36.9
                        Supply voltage: min 24.4, current 24.5, max 24.7, under voltage events: 0, over voltage events: 0
                        Driver 0: standstill, SG min/max not available
                        Driver 1: standstill, SG min/max not available
                        Driver 2: standstill, SG min/max not available
                        Driver 3: standstill, SG min/max not available
                        Driver 4: standstill, SG min/max not available
                        Driver 5: standstill, SG min/max not available
                        Driver 6: standstill, SG min/max not available
                        Driver 7: standstill, SG min/max not available
                        Driver 8: standstill, SG min/max not available
                        Driver 9: standstill, SG min/max not available
                        Expansion motor(s) stall indication: yes
                        Date/time: 2018-08-21 14:55:58
                        Slowest loop: 180.64ms; fastest: 97.54ms
                        === Move ===
                        Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
                        Scheduled moves: 0, completed moves: 0
                        Bed compensation in use: none
                        Bed probe heights: -0.015 -0.010 -0.012 0.000 0.000
                        === Heat ===
                        Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
                        Heater 0 is on, I-accum = 0.0
                        Heater 1 is on, I-accum = 0.4
                        === GCodes ===
                        Segments left: 0
                        Stack records: 2 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 ready with "M408 S0 R50" in state(s) 0
                        daemon is idle in state(s) 0
                        queue is idle in state(s) 0
                        autopause is idle in state(s) 0
                        Code queue is empty.
                        === Network ===
                        Slowest loop: 196.77ms; fastest: 0.08ms
                        Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
                        HTTP sessions: 1 of 8

                        • WiFi -
                          Network state is running
                          WiFi module is connected to access point
                          Failed messages: pending 0, notready 0, noresp 0
                          WiFi firmware version 1.21RC4(08b3)
                          WiFi MAC address 60:01:94:73:54:18
                          WiFi Vcc 3.37, reset reason Turned on by main processor
                          WiFi flash size 4194304, free heap 15752
                          WiFi IP address 192.168.86.30
                          WiFi signal strength -51dBm, reconnections 0, sleep mode modem
                          Socket states: 0 0 0 0 0 0 0 0
                          === Expansion ===
                          DueX I2C errors 20094
                        1 Reply Last reply Reply Quote 0
                        • Gregcundefined
                          Gregc
                          last edited by

                          David,
                          Is it time for me to order a new Duex5?
                          Thanks

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

                            If you are certain that the ground connection between the two is good then I think there is a possibility that your DueX5 has an intermittent fault, and you should ask your supplier to replace it under warranty. https://www.duet3d.com/warranty

                            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
                            • First post
                              Last post
                            Unless otherwise noted, all forum content is licensed under CC-BY-SA