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

    Stuck in spin loop, spinning module G-Codes

    Scheduled Pinned Locked Moved Unsolved
    Duet Hardware and wiring
    5
    30
    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.
    • Aitorundefined
      Aitor
      last edited by

      Hello,

      I would say yes, the Vin input is with a proper wire and both motherboards are connected directly to the outputs of a MeanWell source, the data bus is the one that comes with the duex5 electronics and during the operation it does not seem to heat

      The electronics restart if any temperature is reached?

      1 Reply Last reply Reply Quote 0
      • fcwiltundefined
        fcwilt
        last edited by fcwilt

        Hi,

        Just to give you another perspective.

        I took the idea about a direct power connection between the two boards rather literally.

        The black and red wires connecting the boards are solid 14 gauge.

        Connected in the middle of those two wires are stranded 14 gauge wires running to the power supply.

        Duet WiFi Power Wiring.jpg

        Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

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

          Yes I believe you will need to correct your power and ground connection between the duet and duex as shown by @fcwilt and described here: https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features#Section_Wiring

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • Aitorundefined
            Aitor
            last edited by Aitor

            I have made the changes in 4 machines (all of them identical) but two of them have already stopped, in one of which has stopped, I  put a power supply of higher capacity to test it and also stopped

            Could the problem be the G-code or something in Simplify??

            It does not always fail. If I reboot the printer, most of the time, the first printing works well but the next one has the problem. Working with the same G-Code.

            Thanks!

            Duet2Wifi+Duex5(2).jpeg

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

              It might be worth trying a fresh SD card.

              Z-Bot CoreXY Build | Thingiverse Profile

              Aitorundefined 1 Reply Last reply Reply Quote 0
              • Aitorundefined
                Aitor
                last edited by

                Hello,

                I have not tried to change the micro SD, but it is a bit extrange to have the micro SD card damaged in 4 duet in different machines, no?

                In one machine I introduce M122 and this is what appears: "hard fault, spinning module none". This worries me even more, since this one hasn't stopped for a few days.

                Any idea or recommendation to try to solve both problems (the stops and the last message)?

                M122
                === Diagnostics ===
                RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later + DueX5
                Board ID: 08DLM-996RU-N85T0-6J9FA-3SD6R-1VS3N
                Used output buffers: 3 of 24 (24 max)
                === RTOS ===
                Static ram: 27980
                Dynamic ram: 95924 of which 44 recycled
                Exception stack ram used: 592
                Never used ram: 6532
                Tasks: NETWORK(ready,268) HEAT(blocked,1124) DUEX(suspended,160) MAIN(running,1732) IDLE(ready,80)
                Owned mutexes: WiFi(NETWORK)
                === Platform ===
                Last reset 41:48:37 ago, cause: watchdog
                Last software reset at 2020-07-29 15:38, reason: Hard fault, spinning module none, available RAM 0 bytes (slot 3)
                Software reset code 0x4071 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00000803 BFAR 0x8688b5b0 SP 0x2001ff7c Task MAIN
                Stack: 00452be1 00401cc8 01030000 00000006 2001ffb8 00000000 200088b0 2000565c 004569cd 20000088 20005894
                Error status: 0
                MCU temperature: min 35.6, current 40.2, max 49.6
                Supply voltage: min 23.7, current 24.1, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
                Driver 0: standstill, SG min/max 0/1023
                Driver 1: standstill, SG min/max 0/1023
                Driver 2: standstill, SG min/max 0/580
                Driver 3: standstill, SG min/max 0/1023
                Driver 4: standstill, SG min/max 0/1023
                Driver 5: standstill, SG min/max 0/1023
                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
                Date/time: 2020-07-31 09:28:20
                Cache data hit count 4294967295
                Slowest loop: 207.17ms; fastest: 0.14ms
                I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
                === Storage ===
                Free file entries: 10
                SD card 0 detected, interface speed: 20.0MBytes/sec
                SD card longest read time 5.0ms, write time 160.3ms, max retries 0
                === Move ===
                Hiccups: 0(0), FreeDm: 169, MinFreeDm: 106, MaxWait: 59465336ms
                Bed compensation in use: none, comp offset 0.000
                === MainDDARing ===
                Scheduled moves: 465950, completed moves: 465950, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
                === AuxDDARing ===
                Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
                === Heat ===
                Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
                Heater 0 is on, I-accum = 0.0
                Heater 1 is on, I-accum = 0.5
                === GCodes ===
                Segments left: 0
                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
                USB is idle in state(s) 0
                Aux is idle in state(s) 0
                Trigger is idle in state(s) 0
                Queue is idle in state(s) 0
                Daemon is idle in state(s) 0
                Autopause is idle in state(s) 0
                Code queue is empty.
                === Network ===
                Slowest loop: 206.20ms; fastest: 0.00ms
                Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
                HTTP sessions: 2 of 8

                • WiFi -
                  Network state is active
                  WiFi module is connected to access point
                  Failed messages: pending 0, notready 0, noresp 0
                  WiFi firmware version 1.23
                  WiFi MAC address[0_1596182504353_My Config.zip](Uploading 100%)
                  WiFi Vcc 3.40, reset reason Unknown
                  WiFi flash size 4194304, free heap 20632
                  WiFi IP address 192.168.1.139
                  WiFi signal strength -73dBm, reconnections 1, sleep mode modem
                  Socket states: 0 0 0 0 0 0 0 0
                  === DueX ===
                  Read count 181584, 72.38 reads/min

                My SYS: (without firmware)

                bed.g
                cancel.g
                config.g
                config-override.g
                dwc2settings.json
                gfinal.g
                ginicioT0.g
                ginicioT1.g
                ginicioT2.g
                ginicioT3.g
                homeall.g
                homeu.g
                homex.g
                homey.g
                homez.g
                pause.g
                resume.g
                resurrect-prologue.g
                sleep.g
                stop.g
                tfree0.g
                tfree1.g
                tfree2.g
                tpost0.g
                tpost1.g
                tpost2.g
                tpre0.g
                tpre1.g
                tpre2.g
                trigger2.g
                trigger3.g

                1 Reply Last reply Reply Quote 0
                • Aitorundefined
                  Aitor
                  last edited by

                  Good morning,

                  I just saw that the command G92 E0 is not responding, could this be what's causing the problem?

                  Captura G92 E0.PNG

                  1 Reply Last reply Reply Quote 0
                  • Aitorundefined
                    Aitor @Phaedrux
                    last edited by Aitor

                    @Phaedrux said in Stuck in spin loop, spinning module G-Codes:

                    It might be worth trying a fresh SD card.

                    Four SD cards formatted and still stopping.
                    As soon as I have a new card, I will try it.
                    Any other ideas or suggestions?

                    Many thanks in advance!

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

                      Thanks for the additional information and config files. I haven't had a chance to dig into all of them yet. It may be beyond me to give you any resolution. DC42 may have to take a look when he returns next week. In the meantime please continue to report a M122 if it stops again.

                      Z-Bot CoreXY Build | Thingiverse Profile

                      1 Reply Last reply Reply Quote 0
                      • Aitorundefined
                        Aitor
                        last edited by

                        This machine hasn't stopped for two days, but it's already stopped

                        M122
                        === Diagnostics ===
                        RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later + DueX5
                        Board ID: 08DLM-996RU-N85T0-6J9FA-3SD6R-1VS3N
                        Used output buffers: 14 of 24 (24 max)
                        === RTOS ===
                        Static ram: 27980
                        Dynamic ram: 95524 of which 44 recycled
                        Exception stack ram used: 264
                        Never used ram: 7260
                        Tasks: NETWORK(ready,348) HEAT(blocked,1224) DUEX(suspended,160) MAIN(running,1848) IDLE(ready,80)
                        Owned mutexes: WiFi(NETWORK)
                        === Platform ===
                        Last reset 00:27:19 ago, cause: software
                        Last software reset at 2020-08-01 13:55, reason: Stuck in spin loop, spinning module GCodes, available RAM 6860 bytes (slot 3)
                        Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200042e4 Task IDLE
                        Stack: 00454cdd 0045570a 61000000 a5a5a5a5 00454cdd a5a5a5a5 20004308 200041f8 00000002 2000517c 04c78fb0
                        Error status: 4
                        MCU temperature: min 40.1, current 40.5, max 40.8
                        Supply voltage: min 24.1, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
                        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
                        Date/time: 2020-08-01 14:23:12
                        Cache data hit count 2746906569
                        Slowest loop: 6.07ms; fastest: 0.14ms
                        I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
                        === Storage ===
                        Free file entries: 10
                        SD card 0 detected, interface speed: 20.0MBytes/sec
                        SD card longest read time 3.7ms, write time 0.0ms, max retries 0
                        === Move ===
                        Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
                        Bed compensation in use: none, comp offset 0.000
                        === MainDDARing ===
                        Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
                        === AuxDDARing ===
                        Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
                        === Heat ===
                        Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
                        Heater 1 is on, I-accum = 0.0
                        === GCodes ===
                        Segments left: 0
                        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
                        USB is idle in state(s) 0
                        Aux is idle in state(s) 0
                        Trigger is idle in state(s) 0
                        Queue is idle in state(s) 0
                        Daemon is idle in state(s) 0
                        Autopause is idle in state(s) 0
                        Code queue is empty.
                        === Network ===
                        Slowest loop: 201.87ms; fastest: 0.09ms
                        Responder states: HTTP(2) HTTP(2) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
                        HTTP sessions: 2 of 8

                        • WiFi -
                          Network state is active
                          WiFi module is connected to access point
                          Failed messages: pending 0, notready 0, noresp 1
                          WiFi firmware version 1.23
                          WiFi MAC address
                          WiFi Vcc 3.39, reset reason Unknown
                          WiFi flash size 4194304, free heap 22376
                          WiFi IP address 192.168.1.139
                          WiFi signal strength -74dBm, reconnections 0, sleep mode modem
                          Socket states: 4 2 0 0 0 0 0 0
                          === DueX ===
                          Read count 0, 0.00 reads/min
                        1 Reply Last reply Reply Quote 0
                        • dc42undefined
                          dc42 administrators
                          last edited by dc42

                          There is an issue when inputs connected to the DueX endstop or GPIO inputs pick up noise. Your config.g file indicates that you are using two DueX5 endstop inputs. Try using shielded cable to connect the switches to those inputs, or add pullup resistors of around 2K between each of those inputs and +3.3V.

                          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

                          Aitorundefined 1 Reply Last reply Reply Quote 0
                          • Aitorundefined
                            Aitor @dc42
                            last edited by

                            Hello @dc42,

                            First of all, thank you so much.
                            I have made some tests with the changes that you recommend and everything is working well since I changed it.

                            I have changed the output "duex.e3stop" with "e1stop" , this endstop had 3 wires, but the "duex.e2stop" i have no change anything, this endstop (U axis) only has two wires, GND and "Z STOP" (input E2 STOP). Do you recommend to put the 2k resistance to the "Z STOP" although is not  failing?

                            Thanks a lot again!

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

                              2-wire normally-open endstop switches connected to a DueX are most likely to pick up noise and cause a problem. 2-wire normally closed endstop switches and 3-wire endstop switches connected to DueX would only be likely to pick up noise if they run very close to stepper motor cables for some distance and the cables are not twisted pairs.

                              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

                              Aitorundefined 2 Replies Last reply Reply Quote 0
                              • Aitorundefined
                                Aitor @dc42
                                last edited by

                                Hello @dc42,

                                The endstop that I still have in the duex is a two wire sensor, normally closed. But may be problem if wires go on a chain carrier with the wires of the motor (wires that are not braids), better if I put a 2k resistance to isolate the wires of the endstop?

                                Thanks again!

                                1 Reply Last reply Reply Quote 0
                                • Aitorundefined
                                  Aitor @dc42
                                  last edited by

                                  Hello @dc42,

                                  In the tests that i have done this days, i have seen that the machine did not stop printing as before, but now we have the problem with the endstop that is connected to the duex, sometimes it does not work well:
                                  Sometimes the machine thinks that is always pressed (the axis does not go to home position), others as if it was never pressed (so the motor hits against the endstop but nothing happens).
                                  Is happening in different machines equally assembled. I attached you a picture to show you how I put the 2k resistor. Any idea of what is happening or how to solve it?

                                  WhatsApp Image 2020-08-10 at 1.27.09 PM.jpeg

                                  I have seen in https://duet3d.dozuki.com/Wiki/Gcode#Section_M574_RepRapFirmware_Num_3:

                                  P"pin_name" Defines the pin name(s) that the endstop(s) for the specified axis are connected to, see Pin Names. Needed when S=1. May need it ! before pin name to invert signal, or ^ to enable the pullup resistor, for example on the Duex expansion board.

                                  M574 U2 S1 P"^duex.e2stop"
                                  

                                  Should I be using that way of the PIN output? If I do it, as soon as the machine touches the endstop, it gets blocked and does not recover until it stops touching the endstop. What is this for?

                                  Thanks a lot again!

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

                                    Can you try twisting the endstop wires?

                                    Z-Bot CoreXY Build | Thingiverse Profile

                                    1 Reply Last reply Reply Quote 0
                                    • Aitorundefined
                                      Aitor
                                      last edited by

                                      Good morning,

                                      I don't know what else to try, I've changed the endstop that was connected to the DUEX (U axis) and I put the Z endstop, but it still fails (Now, U axis that is in Duet 2 wifi, works well). This endstop is alone and is not near a motor wire. I tried to put it with a 2k resistor, also with the braided wires, but nothing, sometimes it does not detect it and others it thinks that it is always clicked (so the motor does not go to home position). Is a bit strange because the endstop is a normally closed sistem

                                      627f89bd-56b3-4cd4-b89a-22169c7f22b4.jpg

                                      Sometimes the limit switch doesn't detect it or it always does, the latter is the most common thing, which makes it stranger to me since it's a normally closed limit switch

                                      What else can I try? Any suggestions?

                                      Many thanks in advance

                                      droftartsundefined dc42undefined 2 Replies Last reply Reply Quote 0
                                      • droftartsundefined
                                        droftarts administrators @Aitor
                                        last edited by

                                        @Aitor I think your power wiring, both to the Duet and to the Duex, looks very thin. Is it of sufficient gauge to carry the current to supply the heaters, stepper motors and both Duet and Duex electronics? Also, you need a low resistance ground wire between the Duet and Duex to avoid crosstalk and the Duex using the ground wires in the ribbon cable for grounding (which may be causing your issue). So, ideally, use heavier gauge wiring on your power wiring, minimum 18AWG and preferably something bigger like 16 or 14AWG. Use the bootlace ferrules, too. See https://duet3d.dozuki.com/Wiki/Power_Wiring#Section_Main_power and https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features#Section_Wiring

                                        Also, it looks like you wired the 2K resistor in line (is it under your fingers in the shrinkwrap in your earlier picture?) rather than between the endstop input and +3.3V.

                                        Finally, it is not advisable to run wires near the Duet to Duex ribbon cable. The ribbon cable is unshielded, and can pick up interference.

                                        Ian

                                        Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                                        Aitorundefined 1 Reply Last reply Reply Quote 0
                                        • Aitorundefined
                                          Aitor @droftarts
                                          last edited by

                                          Hello @droftarts,

                                          The wire that I am using to feed the motherboards is 18AWG with the splints on. I am going to order a 14AWG wire to test it (https://es.rs-online.com/web/p/conductores-de-interconexion-cables-para-equipos/6877607/)

                                          9fb03fca-cca1-4084-90e3-5752731429f8.jpg

                                          How can I connect a ground wire between duet and duex? Can I use any free GND pin to connect them?

                                          I have also tried to connect the ground I have in the chassis with a GND (green wire that you see in the image below connected to GND of always on fans) of the Duet 2 Wifi electronics, only in this one since I assume that the GND of both boards are connected, something that the polymeter tells me is correct, but this has not worked either

                                          I have also removed the wire that was running through the flat wire in one of the machines, but others that didn't have it also fail. It doesn't matter what endstop I put in the duo that it will fail.

                                          I have also tried to correct the pull up resistor connection, is it correct now?

                                          9ace6426-f361-415e-be48-91d93f0741fb.jpg

                                          With all this testing and changes, is still not working well, any other suggestion, idea or recommendation?

                                          Many thanks in advance!

                                          fcwiltundefined droftartsundefined 2 Replies Last reply Reply Quote 0
                                          • dc42undefined
                                            dc42 administrators @Aitor
                                            last edited by

                                            @Aitor said in Stuck in spin loop, spinning module G-Codes:

                                            I tried to put it with a 2k resistor

                                            To be clear, the 2K resistor should be connected between the STP and 3V3 pins of the endstop connector on the DueX. Is that what you did?

                                            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

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