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

New edge firmware 1.17dev8 (replaces 1.17dev7)

Scheduled Pinned Locked Moved
Firmware wishlist
7
28
5.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
    dc42 administrators
    last edited by 7 Dec 2016, 14:44

    I have just released firmware 1.17dev7 on GitHub. From the WHATS_NEW file:

    • Implemented G29 S1 (load bed height map from file)
    • Long moves are now segmented when grid compensation is in use so as to follow the contours of the bed
    • Default max temperature excursion increased to 15C
    • M571 now accepts a P parameter to select the output pin (edit: M571 isn't working correctly in this release)
    • Removed Duet WiFi prototype 1 build configuration and added RADDS build configuration
    • M104 and M109 default to tool 0 if no tool selected and no T parameter provided
    • M109 now selects the tool after setting the active temperature if it was not already selected
    • M558 now uses the R parameter to set the Z probe recovery time
    • Fixed an issue in earlier 1.17dev builds when macros were run concurrently with printing

    This release completes all the planned new features for the 1.17 release, but I may implement some minor bug fixes before the official release.

    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
      auser
      last edited by 7 Dec 2016, 15:45

      Removed Duet WiFi prototype 1 build
      Please excuse my ignorance: does this impact the duetwifi beta boards?

      1 Reply Last reply Reply Quote 0
      • undefined
        dc42 administrators
        last edited by 7 Dec 2016, 17:13

        No, prototype 1 was for internal testing and only 2 boards were ever made.

        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
          dc42 administrators
          last edited by 7 Dec 2016, 17:14

          I just found a bug in 1.17dev7: after you have printed a file from SD card, you need to reset the printer before you can do any further movement. Will be fixed soon.

          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
            heathmanc
            last edited by 12 Aug 2016, 16:36 8 Dec 2016, 16:11

            Maybe I don't know how to use this new feature, but I homed my printer, did an autocalibrate and put the settings in the config file, did a G29 and then reset the controller. I put the G29 S1 into my startup script, but when I went to print, everything was WAY skewed, like not even resembling the part.. So, at this point, I rehomed, autocalibrated, ran a G29, and the print the file without the G29 in the beginning of it, same result. What am I doing wrong? Grid is defined with M557 R70 S20.

            Charles

            1 Reply Last reply Reply Quote 0
            • undefined
              dc42 administrators
              last edited by 8 Dec 2016, 17:16

              Can you post the heightmap.csv file generated by a G29 that giving you bad results?

              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
                heathmanc
                last edited by 8 Dec 2016, 17:43

                RepRapFirmware height map file v1 generated at 2016-11-08 16:06
                xmin,xmax,ymin,ymax,radius,spacing,xnum,ynum
                -60.00,60.10,-60.00,60.10,70.00,20.00,7,7
                0,0,0.119,0.070,0.194,0,0
                0,0.012,0.088,-0.040,0.056,0.037,0
                0.044,-0.005,-0.044,0.182,0.068,0.008,0.013
                0.037,-0.010,-0.007,0.140,0.025,-0.023,-0.007
                -0.018,-0.088,-0.057,0.138,0.036,-0.082,-0.181
                0,0.050,-0.087,-0.075,-0.006,-0.038,0
                0,0,-0.024,0.025,-0.049,0,0

                1 Reply Last reply Reply Quote 0
                • undefined
                  dc42 administrators
                  last edited by 8 Dec 2016, 18:52

                  I can't see anything wrong with your height map, although you have a couple of fairly large errors at y=-60 and X= +/- 20mm. What sort of skew are you getting?

                  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
                    heathmanc
                    last edited by 8 Dec 2016, 18:53

                    I haven't let it print more than a couple of perimeters, it's pretty wild and I can't even make out what the part is.

                    1 Reply Last reply Reply Quote 0
                    • undefined
                      dc42 administrators
                      last edited by 8 Dec 2016, 19:04

                      Is it just the Z height that is behaving wildly, or X and Y as well?

                      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
                        dc42 administrators
                        last edited by 8 Dec 2016, 19:12

                        OK, I think I found a problem that could explain what you are seeing. I suggest you roll back to dev6 until I have dev8 ready.

                        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
                          heathmanc
                          last edited by 12 Aug 2016, 19:39 8 Dec 2016, 19:22

                          Ok, done! Glad I'm not completely crazy. The x and y are really skewed, z axis does some crazy things as well, especially when pausing the print.

                          1 Reply Last reply Reply Quote 0
                          • undefined
                            dc42 administrators
                            last edited by 9 Dec 2016, 14:28

                            I have just released 1.17dev8, which fixes the issues I introduced in 1.17. I don't anticipate making any more major changes before 1.17 release, just fixes for any new bugs.

                            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
                              Adamfilip
                              last edited by 11 Dec 2016, 00:00

                              Cant seem to get it working

                              Updated. restarted several times

                              "No valid grid defined for G29 bed probing" is error
                              this is in my config.g

                              M557 X20:260 Y0:240 S10 ; define a grid covering the XY area indicated with the specified grid spacing

                              Sending G29 to activate

                              1 Reply Last reply Reply Quote 0
                              • undefined
                                Adamfilip
                                last edited by 11 Dec 2016, 00:02

                                hmm when i increased Spacing from S10 to S20 it started working.

                                1 Reply Last reply Reply Quote 0
                                • undefined
                                  dc42 administrators
                                  last edited by 11 Dec 2016, 00:49

                                  With your original M557 command, you should get an error message saying that there are too many probe points - except if the M557 command is in config.g then you won't see the message.

                                  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
                                    Adamfilip
                                    last edited by 11 Dec 2016, 03:47

                                    Ok.. What is the max limit of points?

                                    1 Reply Last reply Reply Quote 0
                                    • undefined
                                      Firebug24k
                                      last edited by 11 Dec 2016, 04:53

                                      DC42, on my delta I don't use any XY offset for your IR probe when running G30 autocalibration and it works fine. When I run G29 grid levelling after, should I have entered an XY offset via G31 first or not? My probe is offset about -40mm in the Y direction.

                                      1 Reply Last reply Reply Quote 0
                                      • undefined
                                        Adamfilip
                                        last edited by 11 Dec 2016, 05:57

                                        Grid leveling is working incredibly well. Never had such a good first layer over my entire bed.

                                        Thank you DC42

                                        1 Reply Last reply Reply Quote 0
                                        • undefined
                                          dc42 administrators
                                          last edited by 11 Dec 2016, 07:47

                                          I'm glad it's working well for you!

                                          The maximum number of points is currently 121 on the wired Duet and 441 on the Duet WiFi. However, the underlying grid is rectangular so when using a circular probing area the actual max number of points is about pi/4 times these values.

                                          You should configure the probe offset. During auto calibration the probe offset is ignored.

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