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

RepRapFirmware 3.0 first official beta is out

Scheduled Pinned Locked Moved
Beta Firmware
15
132
9.0k
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.
  • undefined
    kraegar
    last edited by 21 Sept 2019, 13:06

    Updated, then had the thought to check M122. Once again it's showing I'm running 1.0.3.3 even though the pi reflects 1.0.3.5.

    apt list 2>/dev/null | grep duet | awk -F'[/ ]' '{print $1" "$3 }'
    duetcontrolserver 1.0.3.5
    duetruntime 1.0.3.5
    duetsd 1.0.2
    duetsoftwareframework 1.0.3.5
    duettools 1.0.3.5
    duetwebcontrol 2.0.0-4
    duetwebserver 1.1.0.0

    === Duet Control Server ===
    Duet Control Server v1.0.3.3
    Code buffer space: 2048
    Configured SPI speed: 1000000 Hz
    Full transfers per second: 220.03

    I'll force the full update.

    Co-Creator of the RailcoreII CoreXY printer
    https://www.thingiverse.com/thing:2407174

    undefined 1 Reply Last reply 21 Sept 2019, 13:28 Reply Quote 0
    • undefined
      T3P3Tony administrators @kraegar
      last edited by 21 Sept 2019, 13:28

      @kraegar stupid question but you are stopping the service and then restarting it?

      www.duet3d.com

      1 Reply Last reply Reply Quote 0
      • undefined
        kraegar
        last edited by 21 Sept 2019, 13:29

        I did not stop the service manually when I updated. If that's in the instructions I apologize, I winged it since I recall you'd said you were adding stopping the services to the apt scripts. 🙂

        Co-Creator of the RailcoreII CoreXY printer
        https://www.thingiverse.com/thing:2407174

        1 Reply Last reply Reply Quote 0
        • undefined
          kraegar
          last edited by 21 Sept 2019, 13:33

          For clarification, I'm doing an sudo apt-get update; sudo apt get upgrade

          Perhaps something odd is happening that's preventing it from upgrading for me?

          Co-Creator of the RailcoreII CoreXY printer
          https://www.thingiverse.com/thing:2407174

          1 Reply Last reply Reply Quote 0
          • undefined
            kraegar
            last edited by 21 Sept 2019, 13:54

            Just checked, doesn't look like that's in the instructions, so I didn't skip it 🙂

            I can provide more info on my pi, but literally the only thing I've installed has been the duet software. I've left it completely "stock" other than that. It's a pi4 running the "lite" install of Buster.

            Co-Creator of the RailcoreII CoreXY printer
            https://www.thingiverse.com/thing:2407174

            1 Reply Last reply Reply Quote 0
            • undefined
              gtj0
              last edited by 21 Sept 2019, 14:22

              @kraegar This should do it...

              sudo systemctl restart duetcontrolserver
              sudo systemctl restart duetwebserver
              undefined 1 Reply Last reply 21 Sept 2019, 14:32 Reply Quote 0
              • undefined
                T3P3Tony administrators
                last edited by 21 Sept 2019, 14:28

                yes its not in the instructions - fair one.

                www.duet3d.com

                1 Reply Last reply Reply Quote 0
                • undefined
                  kraegar @gtj0
                  last edited by 21 Sept 2019, 14:32

                  @gtj0 Sure. But using apt-get that shouldn't be necessary. Upgrade scripts should stop services if required. I have no problem doing it manually, either.

                  Co-Creator of the RailcoreII CoreXY printer
                  https://www.thingiverse.com/thing:2407174

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    kraegar
                    last edited by 21 Sept 2019, 15:45

                    Very strangely reprinting the same file today as failed yesterday, while it's running and looks like it will complete, has plummeted in print quality. The only change at all was to update the duetsoftware framework on the pi. Same spool of filament, etc.

                    I'll test some other slices, but that was unexpected.

                    Co-Creator of the RailcoreII CoreXY printer
                    https://www.thingiverse.com/thing:2407174

                    1 Reply Last reply Reply Quote 0
                    • undefined
                      smoki3
                      last edited by 21 Sept 2019, 15:51

                      Does it matter on RRF3 if I connect my Z Probe to Duet2Wifi or Duex5? I know on RRF2 there was a difference in the latency.

                      Is this still the same here?

                      1 Reply Last reply Reply Quote 0
                      • undefined
                        kraegar
                        last edited by 21 Sept 2019, 16:48

                        No changes other than updating the duet software and restarting the printer. The one from 1.0.3.3 on the right (that failed part way through), 1.0.3.5 on the left. I was tuning a new slicer (PrusaSlicer), so the first had some cooling issues, but the new one is something else entirely. I don't use pressure advance or firmware retracts, nothing like that.

                        5f5b04f6-85fd-4f13-883c-04aea53a0e88-image.png

                        Co-Creator of the RailcoreII CoreXY printer
                        https://www.thingiverse.com/thing:2407174

                        undefined 1 Reply Last reply 22 Sept 2019, 10:59 Reply Quote 0
                        • undefined
                          smoki3
                          last edited by smoki3 21 Sept 2019, 17:22

                          Seems there is a bug with the endstops on the duet2.

                          My Z probe (normal micro switch) is randomly not working.
                          On the one hand sometimes it is showing in DWC Z-Probe status 1000 even when then probe is not triggered. Without touching the printer I do a emergency stop than the probe status is 0.
                          On the other hand sometimes it is not detected if the probe is triggered and my printer is crashing.

                          The microswitch is connected to my duex5.

                          Its defined with this code:

                          ; Z-Probe
                          M574 Z0 C"nil" ; no Z endstop switch, free up Z endstop input
                          M558 P5 C"!duex.e2stop" H3 F180 T25000 ; Z probe connected to Z endstop input
                          G31 X-14 Y0 Z0.00 P500 ; Set Z probe offset + naher ran - weiter weg
                          M557 X0:300 Y0:190 S50:47.5 ; Define mesh grid

                          UPDATE: seems like it make a huge difference if I take the pins directly on the duet instead of the duex5.

                          1 Reply Last reply Reply Quote 0
                          • undefined
                            smoki3
                            last edited by 22 Sept 2019, 07:31

                            I also have another wire behavior with stall detection on my corexy machine with the duet2.

                            If I start homing the machine executes the homey.g (also happens for X axis) as it should. But the randomly I get the massage homing failed. But no crash or something else. Everything is as it should just the message homing failed and the axis is not marked es homes.

                            I tried so many stall parameters but I don't this it has something to do with this, because the stall is working fine and the home is done fine. Just the axis get not marked as home then I get homing failed.

                            Is there a way to debug?

                            undefined 1 Reply Last reply 22 Sept 2019, 07:47 Reply Quote 0
                            • undefined
                              dc42 administrators @smoki3
                              last edited by 22 Sept 2019, 07:47

                              The Homing Failed message means that the homing switch was not triggered before the move completed. If using stall detection, it means no stall was detected.

                              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

                              undefined 1 Reply Last reply 22 Sept 2019, 08:07 Reply Quote 0
                              • undefined
                                smoki3 @dc42
                                last edited by smoki3 22 Sept 2019, 08:07

                                @dc42 said in RepRapFirmware 3.0 first official beta is out:

                                The Homing Failed message means that the homing switch was not triggered before the move completed. If using stall detection, it means no stall was detected.

                                But it is detected because it move to the end position and then it do the rest of the script (move a bit away from the end position end so on). Otherwise the printer should crash normally because it have to go another 400mm if the stall is not detected

                                1 Reply Last reply Reply Quote 0
                                • undefined
                                  T3P3Tony administrators @kraegar
                                  last edited by 22 Sept 2019, 10:59

                                  @kraegar please try 1.0.4.0 @chrishamm believes this is fixed

                                  www.duet3d.com

                                  undefined 1 Reply Last reply 22 Sept 2019, 14:15 Reply Quote 0
                                  • undefined
                                    kraegar @T3P3Tony
                                    last edited by 22 Sept 2019, 14:15

                                    @T3P3Tony Will do, thanks for the quick update @chrishamm!

                                    Co-Creator of the RailcoreII CoreXY printer
                                    https://www.thingiverse.com/thing:2407174

                                    1 Reply Last reply Reply Quote 0
                                    • undefined
                                      kraegar
                                      last edited by 22 Sept 2019, 16:50

                                      Looking much better so far!

                                      Co-Creator of the RailcoreII CoreXY printer
                                      https://www.thingiverse.com/thing:2407174

                                      1 Reply Last reply Reply Quote 0
                                      • undefined
                                        smoki3
                                        last edited by 23 Sept 2019, 14:22

                                        @dc42

                                        As you can see here the drivers are detecting the stall very well.

                                        https://photos.app.goo.gl/DMTiBbvibGsSs42Y7

                                        But it looks like the signal get not processed correctly.

                                        undefined 1 Reply Last reply 25 Sept 2019, 06:21 Reply Quote 0
                                        • undefined
                                          kraegar
                                          last edited by 23 Sept 2019, 20:53

                                          Testing yesterday and today has so far shown 1.0.4.0 to be stable, and fixed the quality issue that cropped up in 1.0.3.5

                                          Co-Creator of the RailcoreII CoreXY printer
                                          https://www.thingiverse.com/thing:2407174

                                          1 Reply Last reply Reply Quote 1
                                          113 out of 132
                                          • First post
                                            113/132
                                            Last post
                                          Unless otherwise noted, all forum content is licensed under CC-BY-SA