Navigation

    Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    DuetWiFiFirmware minor release 1.15c

    Firmware installation
    11
    79
    9133
    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.
    • dc42
      dc42 administrators last edited by

      I have just released this at https://github.com/dc42/RepRapFirmware/tree/dev/Release. Here is the change log:

      • Increased the maximum number of probe points to 64 on Duet WiFi and 32 on Duet 0.6/0.8.5
      • Added move debug facility
      • Added recording and reporting (via M122) of more types of move underrun
      • Use fabsf instead of fabs
      • M21 no longer re-mounts a drive that is already mounted and has open files on it
      • Added "volumes" variable in extended status response
      • Report card details after M21 is called to mount an SD card
      • After a heater gets to within 2.5C of its setpoint, the load-change PID parameters are used until the setpoint is changed. Previously the load-change PID parameters were used only while the temperature was within 1C of the setpoint.
      • Bug fix: corrected M37 reporting of simulation time
      • Bug fix: M220 speed changes were not being implemented as soon as they should be
      • Bug fix: lookahead was sometimes failing to join sequences of short decelerating moves together
      • Bug fix: at startup the thermistor readings were sometimes very high, which triggered a bug in strtod() called in PanelDue firmware 1.14 and earlier

      It's compatible with DuetWiFiServer 1.02 and earlier, and DuetWebControl 1.12.

      1 Reply Last reply Reply Quote 0
      • curieos
        curieos last edited by

        It seems you changed the way the E endstops work (using them for FSR board). I no longer have to have a jumper to change it to NC. Almost had an issue during a print just now.

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

          No, I haven't made any changes in that area.

          1 Reply Last reply Reply Quote 0
          • curieos
            curieos last edited by

            Then I'm not quite sure what happened. I made a print two days ago with auto calibration and it worked fine. I then loaded the new firmware yesterday, started another print, and it wasn't probing the bed anymore since it was already triggered. I didn't make any changes to my config file other than to adjust for the z offset.

            1 Reply Last reply Reply Quote 0
            • curieos
              curieos last edited by

              After a restart the behavior has reverted back to normal. Not sure what caused it.

              1 Reply Last reply Reply Quote 0
              • Toddimus
                Toddimus last edited by

                I just had the same problem with the FSR sensors (JohnSL board). With 1.15c when I try an auto bed calibration on my delta, it says the endstops are already triggered. No hardware change. Reverted back to 1.15b and it works again. I tried rebooting the duet wifi, but that didn't help.

                I do have a 17 point bed.g file. 10 points on perimeter and 6 points halfway in and one in the center. Don't know if that matters.

                I do have the jumper on the JohnSL board to make the board look like (I think) a normally closed switch. This didn't get changed between firmware.

                Not sure why but it is something different in 1.15c.

                1 Reply Last reply Reply Quote 0
                • Sakey
                  Sakey last edited by

                  Having the same problem, going from 1.15b to 1.15c . Worked fine with 1.15b but 1.15c bring up " Z probe warning: probe already triggered at start of probing move" .

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

                    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?

                    1 Reply Last reply Reply Quote 0
                    • Sakey
                      Sakey last edited by

                      Mines connected 3x fsr to JohnSL board to the duet via e0 endstop I think. Set at 4 on m558.

                      Worked fine in 1.15b, upgraded to 1.15c no longer working so downgraded again and back up and running. Hope that helps DC!

                      1 Reply Last reply Reply Quote 0
                      • Toddimus
                        Toddimus last edited by

                        Mine is connected to the E0 endstop.
                        Jumper on JohnSL board is set for NC

                        M558 P4 X0 Y0 Z0
                        M574 X2 Y2 Z2 S0 // hall effect switches at the top of each delta tower
                        G31 X0 Y0 Z0 P500

                        Thanks DC

                        1 Reply Last reply Reply Quote 0
                        • sga
                          sga last edited by

                          Do you ever sleep?Thx for the update!!!

                          1 Reply Last reply Reply Quote 0
                          • lignumaqua
                            lignumaqua last edited by

                            Not sure if this is a Duet WiFi firmware issue, or chrishamm's web page. Running 1.15c with web interface 1.12 on a brand new Duet WiFi on a brand new CoreXY. All is working fine, very quiet and no problems! 🙂

                            Very minor issue, the web page always reports that the build has 500 layers, no matter how many there really are. (This model actually has 236 layers.)

                            EDIT: The root cause is likely that the model height is incorrect

                            Always comes through as 100mm.

                            1 Reply Last reply Reply Quote 0
                            • deckingman
                              deckingman last edited by

                              I seem to remember reading something somewhere about the firmware finding the object height by reading the last G1 Z command in the gcode file. If you have a G1 Z at the end of your print to lift the head, that can screw it up. You can still lift the head but use G0 instead of G1 (does the same thing I think).

                              1 Reply Last reply Reply Quote 0
                              • lignumaqua
                                lignumaqua last edited by

                                @deckingman:

                                I seem to remember reading something somewhere about the firmware finding the object height by reading the last G1 Z command in the gcode file. If you have a G1 Z at the end of your print to lift the head, that can screw it up. You can still lift the head but use G0 instead of G1 (does the same thing I think).

                                Aha! Thank you, that is precisely the problem. I have a G1 Z100 in my ending script. I'll change that to G0 Z100.

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

                                  A workaround for that is to put a comment starting with upper case E on the end of that G1 line. I'm not sure that using G0 instead of G1 will make any difference.

                                  1 Reply Last reply Reply Quote 0
                                  • deckingman
                                    deckingman last edited by

                                    Found where I'd read that about G0 - it was here https://miscsolutions.wordpress.com/2014/06/11/five-tips-for-using-dc42-firmware-on-the-reprappro-ormerod/. No offence intended but if G0 doesn't work, maybe you should amend you blog David.

                                    1 Reply Last reply Reply Quote 0
                                    • lignumaqua
                                      lignumaqua last edited by

                                      Using G0 fixed the problem. Many thanks for the help.

                                      1 Reply Last reply Reply Quote 0
                                      • Toddimus
                                        Toddimus last edited by

                                        @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
                                        • dc42
                                          dc42 administrators last edited by

                                          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.

                                          1 Reply Last reply Reply Quote 0
                                          • guywinslow
                                            guywinslow last edited by

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

                                              OK, Cant reproduse

                                              1 Reply Last reply Reply Quote 0
                                              • mhackney
                                                mhackney last edited by

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

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

                                                  Yes it is.

                                                  1 Reply Last reply Reply Quote 0
                                                  • mhackney
                                                    mhackney last edited by

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

                                                    1 Reply Last reply Reply Quote 0
                                                    • mhackney
                                                      mhackney last edited by

                                                      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?

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