Duet3D Logo

    Duet3D

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

    New edge firmware 1.17dev8 (replaces 1.17dev7)

    Firmware wishlist
    7
    28
    3815
    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 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
      • auser
        auser last edited by

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

                                      Ok.. What is the max limit of points?

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

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

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

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

                                              @dc42:

                                              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.

                                              You mean that G29 should have the same X Y Z offsets as G31 in config.g?

                                              If Z probe section in config.g looks like this,
                                              [c]; Z probe section
                                              M558 P1 X0 Y0 Z1 H3 F100 T5000 ; Smart IR Z probe, used for homing Z axis, dive height 3mm, probe speed 100mm/min, travel speed 5000mm/min
                                              G31 P500 X-60.0 Y0.0 Z1.30 ;Set the probe height and threshold
                                              [/c]

                                              then bed.g should look like this for Auto bed compensation?
                                              [c]; bed.g
                                              ; M561 ; clear any bed transform, otherwise homing may be at the wrong height
                                              G28 ; home the printer

                                              M557 X10:275 Y15:190 S25 ; define a grid covering the XY area indicated with 25mm grid spacing
                                              G29 X-60.0 Y0 Z1.30 ;probe levelling grid with prob offsets from config.g
                                              [/c]

                                              Edited. Removed .1 from G29

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

                                                No, I mean set up the XYZ offsets in your G31 command, and G29 will use them.

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

                                                  is there a way to fade the grid correction after a certain amount of layers. I noticed that its still adjusting Z height even after 50mm of print height.

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

                                                    Hello,

                                                    I am trying to run the new grid correction and running into an issue. I have this in my config.g
                                                    G31 X0 Y0 Z19.4 P500

                                                    and the bed file

                                                    G30 P0 X0 Y0 Z-99999

                                                    ; Probe the bed and do 6- or 7-factor auto calibration
                                                    G30 P0 X-73.6 Y-42.5 Z-99999 ; X tower
                                                    G30 P1 X0 Y-85 Z-99999 ; between X and Y towers
                                                    G30 P2 X73.6 Y-42.5 Z-99999 ; Y tower
                                                    G30 P3 X73.6 Y20 Z-99999 ; between Y and Z towers
                                                    G30 P4 X0 Y67 Z-99999 ; Z tower
                                                    G30 P5 X-73.6 Y20 Z-99999 ; between Z and X towers
                                                    G30 P6 X-36.8 Y-21.25 Z-99999 ; half way to X tower
                                                    G30 P7 X36.8 Y-21.25 Z-99999 ; half way to Y tower
                                                    G30 P8 X0 Y42.5 Z-99999 ; half way to Z tower
                                                    G30 P9 X0 Y0 Z-99999 ; centre, and auto-calibrate 6 factors
                                                    G30 P10 X0.00 Y40.00 Z-99999 ; Z tower
                                                    G30 P11 X-34.64 Y20.00 Z-99999 ; between Z-X towers
                                                    G30 P12 X0 Y0 Z-99999 S6

                                                    M557 R90 S20
                                                    G29

                                                    The auto calibration works fine for my delta. When it runs the G29 command the zprobe doesn't report/trigger properly (it is 19.4mm) above my bed. It pushes my probe out of the way down and gives the message

                                                    "Zprobe triggered before probing move started" (if the printer is not homed to top)
                                                    OR
                                                    "Zprobe was not triggered before probing move" (if the printer is homed before running)

                                                    I assume the G31 isn't being read for G29? what option do I need to set for the probe to trigger correctly? Sorry if this has been answered for a delta, haven't found it in the threads.

                                                    Thanks,
                                                    Jim

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

                                                      I think that your very large Z probe trigger height has exposed a bug in the G29 probing, which I will fix in today's 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
                                                      • First post
                                                        Last post
                                                      Unless otherwise noted, all forum content is licensed under CC-BY-SA