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

DuetWiFiFirmware minor release 1.15c

Scheduled Pinned Locked Moved
Firmware installation
11
79
12.2k
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
    Toddimus
    last edited by 16 Sept 2016, 23:14

    @dc42:

    Those of you who are having Z probe trouble going from 1.15b to 1.15c, what probe type do you have set in M558, and how do you have the probe connected?

    Any more thoughts on this issue?
    I know you are quite busy, and hopefully have a life outside 3D printing, so I understand any delay. 🙂

    1 Reply Last reply Reply Quote 0
    • undefined
      dc42 administrators
      last edited by 17 Sept 2016, 04:28

      Sorry I won't be able to look at this for several more days. I've already looked at the code changes in 1.15c and I didn't find anything to explain it.

      If you wish, you could try connecting the fsr board to the Z probe connector instead of E0 and use probe type 5.

      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
      • undefined
        guywinslow
        last edited by 19 Sept 2016, 04:01

        Just code my board in the mail 1 week ago. had to print a Case. Got wired and mounted today.

        Improvements:
        Stepper control vast improvement.
        Temperature control wall much stabler, terns off when the gcode changes the temperature wall its printing.

        Working on reproducing it right now

        1 Reply Last reply Reply Quote 0
        • undefined
          guywinslow
          last edited by 19 Sept 2016, 04:09

          OK, Cant reproduse

          1 Reply Last reply Reply Quote 0
          • undefined
            mhackney
            last edited by 19 Sept 2016, 15:30

            David or anyone, is the comment about M301 in config.g relevant if upgrading from 1.15-beta3 release?

            My 3D Printing blog: http://www.sublimelayers.com
            Coming this summer: "3D Printing Strategies - the art of perfecting your designs and prints"

            1 Reply Last reply Reply Quote 0
            • undefined
              dc42 administrators
              last edited by 19 Sept 2016, 15:45

              Yes it is.

              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
              • undefined
                mhackney
                last edited by 19 Sept 2016, 15:51

                Thanks David. I'll upgrade now and know what to watch for.

                My 3D Printing blog: http://www.sublimelayers.com
                Coming this summer: "3D Printing Strategies - the art of perfecting your designs and prints"

                1 Reply Last reply Reply Quote 0
                • undefined
                  mhackney
                  last edited by 19 Sept 2016, 16:02

                  Firmware update to 1.15c went smoothly but DWC does not seem to be updating even after a power reset. Unless HTML: 1.11b-dc42, JS: 1.11b-dc42 is correct for the 1.15c tagged binary on git?

                  My 3D Printing blog: http://www.sublimelayers.com
                  Coming this summer: "3D Printing Strategies - the art of perfecting your designs and prints"

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    dc42 administrators
                    last edited by 19 Sept 2016, 16:35

                    Did you upload the DuetWebControl.bin file through the Settings page?

                    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
                    • undefined
                      mhackney
                      last edited by 19 Sept 2016, 17:55

                      David, yes I did and it appeared to upload correctly with no returned errors.

                      My 3D Printing blog: http://www.sublimelayers.com
                      Coming this summer: "3D Printing Strategies - the art of perfecting your designs and prints"

                      1 Reply Last reply Reply Quote 0
                      • undefined
                        dc42 administrators
                        last edited by 19 Sept 2016, 18:32

                        As you are running DWC 1.11 at present, you need to run M997 S2 after uploading it. The web interface will disconnect and you will need to wait about 3 minutes before you can reconnect it. If you have a PanelDue running firmware 1.14 or later connected, you can see the firmware update progress on it.

                        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
                        • undefined
                          mhackney
                          last edited by 19 Sept 2016, 18:35

                          Thanks David. I updated to the latest PanelDue firmware today too.

                          My 3D Printing blog: http://www.sublimelayers.com
                          Coming this summer: "3D Printing Strategies - the art of perfecting your designs and prints"

                          1 Reply Last reply Reply Quote 0
                          • undefined
                            mhackney
                            last edited by 19 Sept 2016, 19:19

                            Got it, plus I had to flush browser cache. I forgot about the M997. I updated the WiFI server too so this machine is on the latest and greatest of everything. Thanks!

                            My 3D Printing blog: http://www.sublimelayers.com
                            Coming this summer: "3D Printing Strategies - the art of perfecting your designs and prints"

                            1 Reply Last reply Reply Quote 0
                            • undefined
                              mhackney
                              last edited by 19 Sept 2016, 19:43

                              I should also add…

                              I had no problems with my FSRs and JohnSL connected to the E0 connector and I DO have G0 Z150 to terminate my bed.g file.

                              My 3D Printing blog: http://www.sublimelayers.com
                              Coming this summer: "3D Printing Strategies - the art of perfecting your designs and prints"

                              1 Reply Last reply Reply Quote 0
                              • undefined
                                Toddimus
                                last edited by 19 Sept 2016, 22:09

                                @dc42:

                                Sorry I won't be able to look at this for several more days. I've already looked at the code changes in 1.15c and I didn't find anything to explain it.

                                If you wish, you could try connecting the fsr board to the Z probe connector instead of E0 and use probe type 5.

                                I tried this and it worked! The signal line from the FSR board (Green wire) moved to "Z_PROBE_IN". Black to GND and Red to +3.3V.

                                It must have had something to do with the E0 endstop being used as the probe signal input.

                                I also tried firmware 1.15c with 18 bed probe points and that worked as well. So the only things I changed were going from E0 STOP to Z_PROBE_IN for the FSR probe board signal connection. This required changing the M558 parameter from P4 to P5.

                                For clarification, the G0 vs. G1 conversation that happened in the recent posts… I don't believe it has anything to do with the FSR probes not working. That was something to do with the reported object height on the DWC interface.

                                1 Reply Last reply Reply Quote 0
                                • undefined
                                  mhackney
                                  last edited by 19 Sept 2016, 23:20

                                  That's interesting then because my JohnSL is hooked to the the E0 STOP and works perfectly fine with 1.15c firmware.

                                  My 3D Printing blog: http://www.sublimelayers.com
                                  Coming this summer: "3D Printing Strategies - the art of perfecting your designs and prints"

                                  1 Reply Last reply Reply Quote 0
                                  • undefined
                                    guywinslow
                                    last edited by 20 Sept 2016, 03:22

                                    Ok, figured out why my bed temperature keeps faulting. One of the Sch-row terminals is froze in the housing. Dos anyone now where i can find a Replacement for the bed power Terminals?

                                    1 Reply Last reply Reply Quote 0
                                    • undefined
                                      guywinslow
                                      last edited by 24 Sept 2016, 21:33

                                      has anyone had any Extruder drive control issues, on my test print i am getting Blobs of plastic where it starts a new round in the outer shell.

                                      1 Reply Last reply Reply Quote 0
                                      • undefined
                                        guywinslow
                                        last edited by 25 Sept 2016, 04:20

                                        OK, tried another Slicer, just on the chance something in the gcode. Issue manifest itself after a z movement. it can be seen when i try to home xy. The z moves up and the y go's to the stop and stops. then the y jumps in the direction it was moving. Looks like the same thing when i am running a print, except the z moves up and the selected tool (Extruder) jumps. giving me a blob of plastic. any ways hop this makes some sens and is helpful for any one with a Debugger.

                                        Printer type: reprappro mendel
                                        Fermware: 1.15C

                                        1 Reply Last reply Reply Quote 0
                                        • undefined
                                          dc42 administrators
                                          last edited by 25 Sept 2016, 08:21

                                          @guywinslow:

                                          OK, tried another Slicer, just on the chance something in the gcode. Issue manifest itself after a z movement. it can be seen when i try to home xy. The z moves up and the y go's to the stop and stops. then the y jumps in the direction it was moving. Looks like the same thing when i am running a print, except the z moves up and the selected tool (Extruder) jumps. giving me a blob of plastic. any ways hop this makes some sens and is helpful for any one with a Debugger.

                                          Printer type: reprappro mendel
                                          Fermware: 1.15C

                                          That's an odd symptom. Can you post a video?

                                          Two notes:

                                          • When you home all, if you are using the standard homing files on a Cartesian printer, then X and Y are homed together. Whichever one homes first will stop until the other is homed. So if Y homes before X, then Y will stop until X has homed.
                                          • A common cause of an axis pausing for a moment when it should be reversing direction is a loose pulley.

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