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

    DUEX 5 V0.8 TO DUEX 5 V0.11

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    9
    283
    25.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.
    • droftartsundefined
      droftarts administrators @paolozampini1973
      last edited by

      @paolozampini1973 What exact thermistors are you using? You have set the default, which will not be correct, and probably why temperature is incorrect.

      M308 S0 P"bedtemp" Y"thermistor" T100000 B4138
      

      And you need to move Z2 from driver 9 on DueX to driver 0 or 1 on Duet 2. You DueX is being recognised as a DueX2, so probably driver 9 is not working. If it is using an external driver, don't do that; drives on a shared axis need to be identical.

      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

      paolozampini1973undefined 2 Replies Last reply Reply Quote 0
      • paolozampini1973undefined
        paolozampini1973 @droftarts
        last edited by

        @droftarts Yes I set it to DUEX2 because the axes moved when I turned on the electronics Now I can't on DUEX5 Thanks for the dictation problems but for now it is more important to solve the problem of pitch loss and axis movement

        1 Reply Last reply Reply Quote 0
        • paolozampini1973undefined
          paolozampini1973 @droftarts
          last edited by

          @droftarts Yes I know that the engines must be identical and are identical

          1 Reply Last reply Reply Quote 0
          • droftartsundefined
            droftarts administrators @paolozampini1973
            last edited by

            @paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:

            @droftarts Then send me the correct file as you think you are right and I will load it and do the tests you think that for this I lose the steps?

            at this point what do I do I reassemble the v08 or I leave the V 011 I am willing to do any test Thank you please fill in the config file for me and I will load it exactly as you give it to me and I will let you know

            It will have to be later, I have other things I must do.

            I'd keep the V011 in for now.

            Please show how you have wired the 74HC level shifters. Wiring diagram and/or photo.

            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

            paolozampini1973undefined 3 Replies Last reply Reply Quote 0
            • paolozampini1973undefined
              paolozampini1973 @droftarts
              last edited by paolozampini1973

              @droftarts Listen to the 74hc I have to take it apart Because it gives me more problems it practically skips the steps at the entrance I have to give it three times and 8 and it doesn't skip my steps but if I give it 5 volts it skips my steps it practically gets worse

              I did as you told me but the axes move by themselves without command Both X and Y

              droftartsundefined 1 Reply Last reply Reply Quote 0
              • paolozampini1973undefined
                paolozampini1973 @droftarts
                last edited by paolozampini1973

                @droftarts I would like to leave V 011 but the Y x move without giving it the command so it is useless to talk about other problems there is to solve the first This is the problem Okay I'll wait when you get free I'll publish the config file thanks

                21/3/2022, 15:38:13 Error: short-to-ground reported by driver(s) 7 8
                Error: over temperature shutdown reported by driver(s) 7 8
                21/3/2022, 15:38:08 Error: short-to-ground reported by driver(s) 7 8
                Error: over temperature shutdown reported by driver(s) 7 8
                21/3/2022, 15:38:04 Error: short-to-ground reported by driver(s) 7 8
                Error: over temperature shutdown reported by driver(s) 7 8
                21/3/2022, 15:37:59 Error: short-to-ground reported by driver(s) 7 8
                Error: over temperature shutdown reported by driver(s) 7 8
                21/3/2022, 15:37:55 Error: short-to-ground reported by driver(s) 7 8
                Error: over temperature shutdown reported by driver(s) 7 8
                21/3/2022, 15:37:50 Error: short-to-ground reported by driver(s) 7 8
                Error: over temperature shutdown reported by driver(s) 7 8
                21/3/2022, 15:37:49 M122
                === Diagnostics ===
                RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later + DueX5
                Board ID: 0JD0M-9P6M2-NW4SN-6J1DD-3SJ6K-KAURK
                Used output buffers: 3 of 24 (20 max)
                === RTOS ===
                Static ram: 23876
                Dynamic ram: 77448 of which 0 recycled
                Never used RAM 13092, free system stack 184 words
                Tasks: NETWORK(ready,10.4%,231) HEAT(delaying,0.1%,330) Move(notifyWait,0.1%,319) DUEX(notifyWait,0.0%,24) MAIN(running,86.5%,411) IDLE(ready,3.0%,29), total 100.0%
                Owned mutexes:
                === Platform ===
                Last reset 00:00:25 ago, cause: software
                Last software reset at 2022-03-21 15:37, reason: User, GCodes spinning, available RAM 13092, slot 1
                Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
                Error status: 0x00
                Aux0 errors 0,0,0
                Step timer max interval 0
                MCU temperature: min 29.3, current 30.0, max 30.3
                Supply voltage: min 25.6, current 25.7, max 25.8, under voltage events: 0, over voltage events: 0, power good: yes
                Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
                Driver 0: position 0, standstill, SG min/max not available
                Driver 1: position 0, standstill, SG min/max not available
                Driver 2: position 0, standstill, SG min/max not available
                Driver 3: position 0, standstill, SG min/max not available
                Driver 4: position 0, standstill, SG min/max not available
                Driver 5: position 0, standstill, SG min/max not available
                Driver 6: position 0, standstill, SG min/max not available
                Driver 7: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available
                Driver 8: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available
                Driver 9: position 0, standstill, SG min/max not available
                Driver 10: position 0
                Driver 11: position 0
                Date/time: 2022-03-21 15:37:49
                Cache data hit count 981081507
                Slowest loop: 6.48ms; fastest: 0.19ms
                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 1.0ms, write time 0.0ms, max retries 0
                === Move ===
                DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
                === MainDDARing ===
                Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                === AuxDDARing ===
                Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 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
                LCD is idle in state(s) 0
                Daemon is idle in state(s) 0
                Autopause is idle in state(s) 0
                Code queue is empty.
                === Filament sensors ===
                Extruder 0 sensor: no filament
                Extruder 1 sensor: ok
                Extruder 2 sensor: no filament
                Extruder 3 sensor: ok
                === DueX ===
                Read count 1, 2.36 reads/min
                === Network ===
                Slowest loop: 39.88ms; fastest: 0.00ms
                Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
                HTTP sessions: 1 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.26
                  WiFi MAC address 40:f5:20:0d:6b:49
                  WiFi Vcc 3.37, reset reason Turned on by main processor
                  WiFi flash size 4194304, free heap 20888
                  WiFi IP address 192.168.1.5
                  WiFi signal strength -64dBm, mode 802.11n, reconnections 0, sleep mode modem
                  Clock register 00002002
                  Socket states: 0 4 0 0 0 0 0 0
                  21/3/2022, 15:37:46 Error: short-to-ground reported by driver(s) 7 8
                  Error: over temperature shutdown reported by driver(s) 7 8
                  21/3/2022, 15:37:41 Error: short-to-ground reported by driver(s) 7 8
                  Error: over temperature shutdown reported by driver(s) 7 8
                  21/3/2022, 15:37:39 Connected to 192.168.1.5
                  config (18).g
                1 Reply Last reply Reply Quote 0
                • droftartsundefined
                  droftarts administrators @paolozampini1973
                  last edited by

                  @paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:

                  I did as you told me but the axes move by themselves without command Both X and Y

                  Is that in both DueX2 mode and DueX5 mode?

                  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

                  paolozampini1973undefined 4 Replies Last reply Reply Quote 0
                  • paolozampini1973undefined
                    paolozampini1973 @droftarts
                    last edited by

                    @droftarts As you can see the errors alone are only when AND IN DUEX MODE 5 DRIVER 7+ DRIVER 8 ARE OFF IN DUEX 2 MODE IT DOESN'T GIVE SHORT-CIRCUIT ERRORS SO IT IS NOT NORMAL IN MY MEETING

                    1 Reply Last reply Reply Quote 0
                    • paolozampini1973undefined
                      paolozampini1973 @droftarts
                      last edited by

                      @droftarts No in DUEX2 MODE they do not move by themselves they move only with the command IN DUEX5 MODE THE MOVEMENT HAS BEEN ALONE WITHOUT COMMAND

                      tekkydaveundefined 1 Reply Last reply Reply Quote 0
                      • paolozampini1973undefined
                        paolozampini1973 @droftarts
                        last edited by

                        @droftarts from my experience it tells me that this expansion has problems but I think they are more software problems and not hardware problems Tell me what you think
                        Also because I'm sorry if I always repeat the same thing but I find myself with so many problems that I did not have Maybe some of these problems are not aware I will tell you more I tried to disconnect everything on the problem outputs it gives the same so on all the drivers I am disconnected disconnected nothing is connected and it still gives problems in duex 5 mode

                        1 Reply Last reply Reply Quote 0
                        • tekkydaveundefined
                          tekkydave @paolozampini1973
                          last edited by tekkydave

                          @paolozampini1973 You need to run the Duex in Duex2 mode. In this way it will disable the internal drivers on 7,8,9 allowing you to have external drivers on 7 & 8 for your X & Y axes.
                          If you have it in Duex5 mode BOTH the internal and external drivers are connected which is causing the movement without commands.

                          ~ tekkydave ~
                          D-Bot: 300x300mm | Duet WiFi + Duex2 | 3 independent z motors | X,Y & Z linear rails | E3D Titan Aero + V6 | Precision Piezo z-probe
                          FreeCAD, PrusaSlicer

                          paolozampini1973undefined 1 Reply Last reply Reply Quote 0
                          • paolozampini1973undefined
                            paolozampini1973 @droftarts
                            last edited by

                            @droftarts Listen to me when I say something and before I say something I think about it I don't talk to Ugh the problem now that I still have to solve the problem But you have to understand you are a hardware problem or a software problem as I said before for me it is a software problem and obviously before I had a small problem now I have big problems so what I ask you and please please please at least try to understand if it is a hardware problem or a software problem because otherwise I am forced to upgrade to version 0.8

                            unless I could print with some pitch loss problem but at least I could print now I have practically the printer stopped

                            1 Reply Last reply Reply Quote 0
                            • paolozampini1973undefined
                              paolozampini1973 @tekkydave
                              last edited by

                              @tekkydave Excuse me but if I do as you say or three motors that I cannot use then I still have a big problem So what is the advantage of having bought the 011 version because I have these problems that I have with the 011 I did not have them so explain to me you this solution that you recommend me maybe I don't understand Thanks very kind

                              tekkydaveundefined 1 Reply Last reply Reply Quote 0
                              • tekkydaveundefined
                                tekkydave @paolozampini1973
                                last edited by

                                @paolozampini1973 @droftarts has already given the solution:
                                Move the Z2 axis from output 9 on the Duex to either 0 or 2 on the Duet.
                                Put the Duex in Duex2 mode.
                                Make the changes to config.g that he will be giving to you.

                                Once that is done lets see what remaining problems there are.

                                ~ tekkydave ~
                                D-Bot: 300x300mm | Duet WiFi + Duex2 | 3 independent z motors | X,Y & Z linear rails | E3D Titan Aero + V6 | Precision Piezo z-probe
                                FreeCAD, PrusaSlicer

                                paolozampini1973undefined 1 Reply Last reply Reply Quote 1
                                • paolozampini1973undefined
                                  paolozampini1973 @tekkydave
                                  last edited by

                                  @tekkydave my printer configuration:
                                  Z is configured with two INDEPENDENT motors FOR SELF-LEVELING one on Driver 1 = Z one on the driver 9 = Z then X = DRIVER 7 EXSTERNAL DM860H Y = DRIVER 8 EXSTERNAL DM860H then I have 4 driver instructors 3 TMC2660 + driver 4 TMC2660 + driver 5 TMC2660 + driver 6 TMC2660
                                  PROBLEMS WITH DUEX5 V0.11 IN DUEX5 OFF DRIVE MODE 7 AXIS X + DRIVER 8 AXIS Y WHY I NEED TO USE IT
                                  are engaged or four independent extruders in total there are 8 motors Now I am sending you how I configured the printer and This is how it must be then the solution of You tell me how I can do it if I have 8 motors

                                  tekkydaveundefined 1 Reply Last reply Reply Quote 0
                                  • tekkydaveundefined
                                    tekkydave @paolozampini1973
                                    last edited by

                                    @paolozampini1973
                                    I'll do it by means of a table:

                                    Driver      Axis
                                    ------      -----
                                    0           unused         
                                    1           Z1
                                    2           Z2
                                    3           E1
                                    4           E2
                                    5           E3
                                    6           E4
                                    7           X (external)
                                    8           Y (external)
                                    9           unused (external)
                                    
                                    

                                    This is all 8 motors. The Duex is in Duex2 mode.

                                    ~ tekkydave ~
                                    D-Bot: 300x300mm | Duet WiFi + Duex2 | 3 independent z motors | X,Y & Z linear rails | E3D Titan Aero + V6 | Precision Piezo z-probe
                                    FreeCAD, PrusaSlicer

                                    paolozampini1973undefined 2 Replies Last reply Reply Quote 1
                                    • paolozampini1973undefined
                                      paolozampini1973 @tekkydave
                                      last edited by paolozampini1973

                                      @tekkydave DRIVER 5 + DRIVER 6 in DUEX mode 2 they do not work they are disabled understood This is a test that I have already done they do not work only 7 8 and 9 works I think you don't know this thing you've never tried But they don't work

                                      tekkydaveundefined 1 Reply Last reply Reply Quote 0
                                      • paolozampini1973undefined
                                        paolozampini1973 @tekkydave
                                        last edited by

                                        @tekkydave I repeat then this is not a solution this is to turn the problem because as I repeat with the 0.8 these problems I did not have the 0.11 HAS problems Then honestly buying a version that should solve some problems but instead you create other problems this is not normal what I mean understood I Thanks for your kind attention Thank you but in this way you do not solve the problem it turns it creating even more problems

                                        1 Reply Last reply Reply Quote 0
                                        • tekkydaveundefined
                                          tekkydave @paolozampini1973
                                          last edited by

                                          @paolozampini1973 said in DUEX 5 V0.8 TO DUEX 5 V0.11:

                                          @tekkydave DRIVER 5 + DRIVER 6 in DUEX mode 2 they do not work they are disabled understood This is a test that I have already done they do not work only 7 8 and 9 works I think you don't know this thing you've never tried But they don't work

                                          Correct - I haven't tried it. I only have a duex2 in my printer as I only have one extruder and 3 Z motors plus X & Y. I am simply repeating the information that others have already given days ago. Good luck solving your issues. Now I am convinced this thread is a Turing Test đŸ™‚

                                          ~ tekkydave ~
                                          D-Bot: 300x300mm | Duet WiFi + Duex2 | 3 independent z motors | X,Y & Z linear rails | E3D Titan Aero + V6 | Precision Piezo z-probe
                                          FreeCAD, PrusaSlicer

                                          paolozampini1973undefined 1 Reply Last reply Reply Quote 1
                                          • paolozampini1973undefined
                                            paolozampini1973 @tekkydave
                                            last edited by

                                            @tekkydave Please Unfortunately, this version has problems that in the design phase it can happen that one does not notice it But in fact I now take down the 0:11 you were MonterĂ² from 08 However I do not recommend to buy the 011 Until proven otherwise it is that I now have 6 problems including 4 are very serious

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