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

Print becomes thinner when the heated bed is on

Scheduled Pinned Locked Moved
General Discussion
3
11
1.5k
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
    Hobsie
    last edited by Hobsie 20 Apr 2018, 21:08

    I have a pretty odd issue that I initially thought was z wobble and then potentially current being induced by close cables when the heated bed turns on, but I'm not so sure.

    I'm getting a very consistent change in print whenever the heated bed turns on - this seems to manifest as the print becoming slightly thinner while the bed is on. Over time this looks like very slight horizontal ripples in the print.

    I don't think it's z wobble as I can see it happen as the heated bed turns on and when printing a cylinder the radius reduces pretty uniformly rather than shifting in one direction. I don't think it's induction through the heat bed cable because I've separated the cables as much as possible and it's still happening. Leaving the heated bed off eliminates the issue entirely.

    Any ideas?

    I'm on a Duet Wifi firmware 1.20 with a CoreXY setup and 24V electronics - the heated bed is connected directly to the Duet.

    1 Reply Last reply Reply Quote 0
    • undefined
      Phaedrux Moderator
      last edited by 20 Apr 2018, 22:59

      PCB heat beds are known the change shape and flex during heating cycles.

      Are you using PWM or bang bang for the bed?

      Z-Bot CoreXY Build | Thingiverse Profile

      1 Reply Last reply Reply Quote 0
      • undefined
        dc42 administrators
        last edited by 21 Apr 2018, 06:57

        This is fairly common when using bang-bang control for the bed. When the bed heater turns on, the VIN voltage at the Duet drops. How much depends on the PSU, the resistance of the cables between the PSU and the Duet, and whether the VIN terminal block screws are tight. You should be able to see this drop by monitoring the Vin value displayed by DWC when you turn the bed heater on from cold. The reduction in voltage can cause a reduction in extruder heater power, which results in a drop in extrusion temperature until the PID catches up.

        Two suggestions:

        1. Send M307 with no parameters to check what heater model values you are using. If the V parameter is zero then heater voltage compensation is not being applied. So run heater tuning again and make sure you copy the V value across to the M307 command in config.g along with the A, C and D values.

        2. Run the bed in PID mode.

        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 21 Apr 2018, 09:42 Reply Quote 0
        • undefined
          Hobsie @dc42
          last edited by Hobsie 21 Apr 2018, 09:42

          @dc42 said in Print becomes thinner when the heated bed is on:

          M307

          Thanks for the info! I strongly suspect you're right and I'm printing a cylinder just now to make sure (I can already see the bed led flickering away instead of going on and off in longer intervals)

          However, when I ran M307 H0 to check the bed mode it came up with default values, which I thought was odd because I had definitely ran pid tuning on the bed and used M500 to save the results. So I checked config-override.g and could see the M307 values the pid tuning had spat out (including a voltage change value).

          M307 H1 brought up the hotted values in the override correctly but M307 H0 didn't bring up the bed?

          I've worked around this by copying the M307 H0 values into my config.g proper and that seems to work (calling M307 H0 now brings up the saved values).

          That's not intended behaviour is it?

          1 Reply Last reply Reply Quote 0
          • undefined
            Hobsie
            last edited by Hobsie 21 Apr 2018, 10:29

            That looks like it’s done the trick, thanks!

            Left cylinder printed with default bang bang for the heated bed and then with the Pid tuned values for M307 (and voltage compensation) on the right 🙂

            0_1524306499437_D7EFE4EB-392A-437E-927F-465D06A07168.jpeg

            1 Reply Last reply Reply Quote 1
            • undefined
              dc42 administrators
              last edited by 21 Apr 2018, 11:54

              I'm glad you solved it. Did M307 H1 show a V parameter when you ran 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

              undefined 1 Reply Last reply 21 Apr 2018, 12:46 Reply Quote 0
              • undefined
                Hobsie @dc42
                last edited by 21 Apr 2018, 12:46

                @dc42 M307 H1 shows 0 for the V parameter, while M307 H0 shows 23.7 (it sits at about 24.2 when the bed is off based on the machine status).

                Is that an issue?

                1 Reply Last reply Reply Quote 0
                • undefined
                  dc42 administrators
                  last edited by 21 Apr 2018, 18:35

                  The V parameter for H1 is the critical one. Without it, there is no extruder power compensation for variations in the supply voltage. With the correct compensation, even with bed heater bang-bang control there should be no banding.

                  So I suggest you run extruder heater tuning again. Last time you ran it, you must have been running older firmware that did not provide compensation of extruder heater power with variation in supply voltage.

                  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
                    Hobsie
                    last edited by Hobsie 21 Apr 2018, 22:38

                    Thanks for the follow up. I’ve run tuning again for the hotend and M307 H1 is showing a value for V now (24.2) - presumably that’ll improve things even further after ensuring the bed was running with pwm?

                    And I guess M307 H0 being ignored in the config override must be potential a bug?

                    1 Reply Last reply Reply Quote 0
                    • undefined
                      dc42 administrators
                      last edited by 22 Apr 2018, 07:09

                      I've just tested using M500 to save new M307 H0 values in config-override.g and then rebooting, and it's working for me.

                      Do you have M501 at the end of config.g, to invoke config-override.g?

                      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
                        Hobsie
                        last edited by 22 Apr 2018, 09:07

                        M501 /facepalm.

                        Yeah that was missing, and had it been there this whole time the OP issue wouldn't have happened 😛

                        Massive thanks, pid tuned values loading up from config-override.g correctly now and both H0 and H1 have voltage values in there now as well!

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